Related
The font size in my text message screen has grown out of control in the last week. I was typing a message about 4 days ago and the font in the thread started increasing as I tried to type.
This led me to believe it was some combo of keys I pressed that made it happen.
However I swear today it is even bigger. Easily a 14 and that is huge on this little screen.
I have the 08.14.09 Bloat Free Official HTC Fuze ROM Update and it has been fine since Nov. This only just happened recently and it happened while I was watching. No other changes have been made.
My searches keep pointing to utilities/downloads that let you control it, but I just want it back to normal. Do not want to add more software. This just happened...so there has to be a way to undo it.
Anyone know where the text font settings are controlled. (I also have registry editor and advanced donfig installed if those might have settings in em...have to go look.)
Oh damn, talk about breaking the rules. I guess I need to search ON this forum and not assume that Google knows all.
http://forum.xda-developers.com/showthread.php?t=536578&highlight=sms+text+size
Ok, text issues are controlled by the zoom feature same as images are. DOH!
(Flaming can now begin, I deserve it.)
Side note, I have been having issues with buttons sticking or not working on first press. Phone just about 1.5yr old. So not surprised that the main pad on front may have done stuff without me touching it. (Del button not work all time, space bar now up to 3 spaces occasionally, etc.)
sablesurfer said:
Oh damn, talk about breaking the rules. I guess I need to search ON this forum and not assume that Google knows all.
http://forum.xda-developers.com/showthread.php?t=536578&highlight=sms+text+size
Ok, text issues are controlled by the zoom feature same as images are. DOH!
(Flaming can now begin, I deserve it.)
Side note, I have been having issues with buttons sticking or not working on first press. Phone just about 1.5yr old. So not surprised that the main pad on front may have done stuff without me touching it. (Del button not work all time, space bar now up to 3 spaces occasionally, etc.)
Click to expand...
Click to collapse
I agree with you that he should use the search, but what would you search for if you didn't know the problem?
Anyway, when your typing a message, try moving your finger around the center of your device, You will see then how it works.
I have this weird small ring that makes my touch screen act very strange. What happens is when I try and do something on the screen, this weird ring will move around the screen instead. It does track my directions properly (when I move my finger to the right, it also moves to the right) but the actual location of the ring isn't under my finger. I need to know how to deactivate it. It is very hard to explain, so I attached a picture of it instead. This isn't the small dot that you can activate in Developer Options that follows your touch. I know that much.
I'm sorry if this was posted in the wrong forum, but bashing me and calling me a noob, or what have you, won't help me or you!
Doesn't seem to be an issue with the screen hardware. Please provide more details like which device and what model, which ROM and what all you did, when it started, etc.
check developer options
The device is an ancient Xperia X10 with PAC-man ROM JB installed.
This problem started when I installed CrossBreeder.
I flashed it through CWM, no problems. Booted and everything, but when I wanted to unlock the device, then this ring appeared.
I checked the build.prop to see if anything looks astray, but nothing looked out the ordinary (I can still navigate with great difficulty )
I already said that Show Touches isn't checked in Developer Options (and it doesn't have this type of effect anyway)
The ring works very similar to using a trackpad on a laptop (basically exactly like using a trackpad, just replace the mouse pointer with the ring!) My input area for actual screen selections is restricted to the ring. Where the ring is, is where I can make a selection.
I luckily had a newish nandroid backup, so I restored it. I just want to know what I can do so that this doesn't happen again, when I flash CrossBreeder for a second time (that is if I want to flash it )
I suggest you ask about this issue in the CrossBreeder thread here on XDA. See if some other members have had similar experiences.
No idea why I didn't think about that. Thanks a dozen
Remember, we all were a noob once. Maybe twice, but definitely once
Edit: I posted it here because I thought I would gain a larger audience (therefore problem would be solved faster)
Is there any way to decompile, edit, and recompile the MCU image file? I know it's risky and not for everyone. But wondering if the utility exists to make the later version HA a better fit for my JY unit.
Phredeee said:
Is there any way to decompile, edit, and recompile the MCU image file? I know it's risky and not for everyone. But wondering if the utility exists to make the later version HA a better fit for my JY unit.
Click to expand...
Click to collapse
There's no difference between ha and jy MCU. Im confused by what you mean by 'better fit' as all options configurable by factory settings.
It sure looks to me that there is a difference. One example would be the ability to adjust the panel LED color and brightness available on JY but not HA. Maybe there is some other setting or ? to enable the settings?
It works 99.5 % the same. BT is better. But there are minor differences. I suppose HA never marketed a unit with hard knobs or didn't care about it.
Going on recent first hand experience.
Phredeee said:
It sure looks to me that there is a difference. One example would be the ability to adjust the panel LED color and brightness available on JY but not HA. Maybe there is some other setting or ? to enable the settings?
It works 99.5 % the same. BT is better. But there are minor differences. I suppose HA never marketed a unit with hard knobs or didn't care about it.
Going on recent first hand experience.
Click to expand...
Click to collapse
Interesting, I came from JY and have latest HA. Did you realise that when LED type is correctly set in factory settings then led colour can be set in android settings menu?
So I can set LED brightness just fine. Ive analysed earlier HA and JY, they're identical per my thread. What is different is the factory settings config the resellers custom set in the MCU code.
Same for 'knobs' all - configurable via factory settings, in fact ive programmed my hard home button long press to turn off the display. All fully customisable. I had the same issues coming from JY, if you read my thread its all covered in the thread.
Youre welcome
Maybe custom settings in the MCU setting variables in the code rather than a different code per se. But different beyond the normal user settings none the less.
I am able to set day and night composite led brightness thru normal settings but not separate rgb as before in the JY settings.
This is not simple key mapping here as used for setting hard button short and long press. Nor is it selecting one of 3 full on colors.
You refer to a thread where you have information on this, but I have not read every post on xda nor did a search reveal any pertaining tags.
Perhaps a link would be worthy of thanks, only then maybe a "your welcome" would be deserved. Maybe not.
Phredeee said:
Maybe custom settings in the MCU setting variables in the code rather than a different code per se. But different beyond the normal user settings none the less.
I am able to set day and night composite led brightness thru normal settings but not separate rgb as before in the JY settings.
This is not simple key mapping here as used for setting hard button short and long press. Nor is it selecting one of 3 full on colors.
You refer to a thread where you have information on this, but I have not read every post on xda nor did a search reveal any pertaining tags.
Perhaps a link would be worthy of thanks, only then maybe a "your welcome" would be deserved. Maybe not.
Click to expand...
Click to collapse
Let's break it down. Two issues (1)led and (2) hardware button settings. No argument the issues you have are configurable and the mcu code is identical minus reseller specific customisation of settings.
See my signature or search for mcu cross compatability.
marchnz said:
Let's break it down. Two issues (1)led and (2) hardware button settings. No argument the issues you have are configurable and the mcu code is identical minus reseller specific customisation of settings.
See my signature or search for mcu cross compatability.
Click to expand...
Click to collapse
Your comments did cause me to try every factory setting for the LEDs. Since there is no real descriptions available it is the typical learn as you go. One setting did cause the elements setting field in the normal user settings area to appear so LED control is solved.
Most things are configurable as far as the hard controls go. On that topic...
The knob rotation function is not changeable. Not really a big deal
The long press option settings are off by one about 1/3 of the way thru. Once you know this, just select one lower than what you really want but the last option is not able to be selected.
I'm trying to revisit my wish list before buying the PX5 upgrade. Maybe a different unit is better?
Things I'm still working on:
I would like to be able to assign the music app to one that has playlists. I use MediaMonkey. The problem is the third party app does not take control of the audio stream so two things are active together.
Repairing my faulty SD card slot. Trying to explain this to Joying is impossible. All they know "is send the unit back to us" which is more costly than a new unit. Still searching for generic parts. I work around and can live with only one slot if needed.
A2DP interface is my next test. Ultimately, with the upgrade, I would not need to rely on my phone and this would be less important.
Thanks for prompting me to double check the LED settings.
Is it possible to change the video out (rca) to full android interface from (only) dvd-tv output by editing mcu?
My problem is:
https://forum.xda-developers.com/android-auto/android-head-units/informative-screen-t3650055/
Please help me
On my pixel 2 tap inputs occasionally don't register, I've had it happen in the android system menu, the android back/home buttons, chrome, etc. Is anyone else experiencing this?
My phone's basically on stock default settings, nothing unusual running. Not sure if it's only tap inputs getting dropped or the whole system locking up temporarily. Turning on "Show taps" in Developer options I can see there's no visual effect when a missed tap occurs.
Yes, this is me too exactly. Same thing with the dev option too. Not sure if I should wait for 8.1 or if it's hardware and RMA it. Frustrating because I like this phone.
I noticed this on my phone, clicking around in the settings and on the back and home buttons. I then did a factory reset (because of a separate issue where the location icon was always displaying in the notification area, even when not in use). After that the issue seems to have gone away. So it would seem to be software issue. I suggest trying a factory reset (though beware that this wipes everything on your device).
P.S. nonexistent, I'm impressed that you joined the XDA forums in Dec 2010 and never posted a comment until now. Of course, you might need to change your screen name to "existent," now that you're out in the open.
I have definitely noticed this as well, happy to know it wasn't just me
cb474 said:
I noticed this on my phone, clicking around in the settings and on the back and home buttons. I then did a factory reset (because of a separate issue where the location icon was always displaying in the notification area, even when not in use). After that the issue seems to have gone away. So it would seem to be software issue. I suggest trying a factory reset (though beware that this wipes everything on your device).
P.S. nonexistent, I'm impressed that you joined the XDA forums in Dec 2010 and never posted a comment until now. Of course, you might need to change your screen name to "existent," now that you're out in the open.
Click to expand...
Click to collapse
I tried a reset but the issue still showed up. In fact it happened twice on the first time setup stuff afterwards. I called Google and we went through the motions and reset it from recovery mode but it was still there when I was testing it the next couple hours. Anyway, we're doing the RMA thing. I'll let you guys know how it works out when I get my new phone.
Got my replacement and the problem still exists. It even happens just a couple screens into the initial setup after a factory reset from recovery mode.
I find that it occurs when I'm in a small room with the heat turned up. The sensitivity of the touch screen seems to depend a lot on moisture. If I keep my fingers moist (or wear a touch sensitive glove) it works a heck of a lot better.
ritzack said:
Got my replacement and the problem still exists. It even happens just a couple screens into the initial setup after a factory reset from recovery mode.
Click to expand...
Click to collapse
That's good and bad news I guess, hopefully just needs a software update. I have a replacement coming Monday, but I kind of expect no improvement and that this is just a common thing that a lot of people aren't noticing
I noticed that for a while in Google Play Books, in which I tap the screen frequently to turn pages. I tried a factory reset, which didn't help. I tried running in safe mode and testing on Maps and still had a problem, although less frequently (a higher percentage of taps worked). Then it started to work better. We'll see if that lasts.
I tried flicking as opposed to tapping and flicking always works.
I'd suggest posting on the Pixel product forum or calling support, so that Google becomes more aware of the issue. There are some threads on the subject on reddit and the product forum.
Out of interest are you noticing it any particular parts of the screen?
I've noticed it a few times but it's been on areas of the screen near the edges.
I assumed it was some sort of palm rejection thing going on it the background with it thinking I'm accidently mashing the display.
With me it was the right edge toward the middle, as that's where you tap to turn the page in Play Books.
I get it on the back button frequently, but it happened just now in the middle of the screen when I typed the text input box to start writing this
I think this is the whole OS hanging/freezing briefly actually, not a touchscreen input issue
- Pressing the hardware unlock button can get ignored (both locking/unlocking)
- Scrolling from a quick flick + release can suddenly stop (no additional inputs)
So most likely this is a software issue, hopefully fixed in an upcoming update? It's kinda annoying
Did you change the DPI or font size? I go back to default and it seems that everything is good now.
---
update: no it happens again…
nonexistent said:
On my pixel 2 tap inputs occasionally don't register, I've had it happen in the android system menu, the android back/home buttons, chrome, etc. Is anyone else experiencing this?
My phone's basically on stock default settings, nothing unusual running. Not sure if it's only tap inputs getting dropped or the whole system locking up temporarily. Turning on "Show taps" in Developer options I can see there's no visual effect when a missed tap occurs.
Click to expand...
Click to collapse
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Haven't changed the DPI or font size
LimitsX said:
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Click to expand...
Click to collapse
I can trigger the system hang/"missed input" most reliably by visiting m.reddit in chrome (any thread w/ comments) and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Haven't changed the DPI or font size
LimitsX said:
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Click to expand...
Click to collapse
I can trigger the system hang/"missed input" most reliably by visiting any m.reddit thread in chrome and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
nonexistent said:
Haven't changed the DPI or font size
I can trigger the system hang/"missed input" most reliably by visiting m.reddit in chrome (any thread w/ comments) and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Click to expand...
Click to collapse
So, I replicated what you told me, 3x. I didn't miss any taps, and no system hang/missed input..
hmm
Got my replacement and it has been much better so far. Still a few dropped inputs but I think those may be false positives because I am hyperfocused on it. Pretty sure I have always had to double click occasionally on all phones at various times.
nonexistent said:
Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Click to expand...
Click to collapse
Yeah, sometimes I see a tap register visually on the screen, but the intended action doesn't happen.
redandblack1287 said:
Got my replacement and it has been much better so far. Still a few dropped inputs but I think those may be false positives because I am hyperfocused on it. Pretty sure I have always had to double click occasionally on all phones at various times.
Click to expand...
Click to collapse
It's funny. I had the issue. Did a factory reset. Felt like it was better. But now that I'm thinking about it more I notice it a lot. So I can't tell if it's really different. Before I figured I'd made a mistake. Now I think it's the phone. Damn you phone!
Anyway, I notice that the issue tends to happen more or less randomly, at any position on the screen. Also, sometimes the same tap fails to register twice in a row, but once it's starts working all subsequent taps that come in a row work (say I'm clicking through a lot of menu items in some settings). So maybe that lends some credence to the idea that there is a system for registering the taps that is not waking up and once it does it works fine.
Perhaps related, I have my ambient display set to wake on double tap. Before the Nov update it hardly worked. Now it seems to be working reliably.
Ok, guys, I tried searching through the forums and I'm not seeing a thread related directly to this so here goes.
Last night my daughter had my phone and now when I'm in full-screen apps, (specifically I play summoners war) the nav bar won't auto minimize like it should. It's pretty annoying since it covers up my skills and nothing I can really do. There has to be a specific option I can't find but in settings>display, there is no navigation section. I am running totally stock pixel, no root. android 8.1.0. I don't want to get into any command line prompts because this had to have happened without it, so I hope someone can help me out here.
Not sure what could be, but if in adb you type "settings put global policy_control immersive.full=" (yes, with nothing after the "=") it will reset any kind of modifications made on navbar/statusbar immersive settings, reverting back to stock.
I know you asked a solution without commands, but since I don't know what could be the cause I don't have specific ideas. So if you want, give it a try.