Hello all, new here, hope this is the right place for this post...
I have looked everywhere and can't seem to find anything relevant, so maybe someone here may have some insight. To start, it is (Kingo) rooted stock ROM android 4.1.2, build M36UP61, kernel 3.4.0, just to avoid confusion... Here's the issues numbered so I can correlate answers for each:
1) WiFi will occasionally drop, but the issue is that after (I assume) 5 retries, it leaves the AP as "disabled", and I want it to never do that, like my kyocera hydro, which relentlessly retries until it gets a connection to a known AP. Essentially, to never give up on a known AP for any reason, even if having to connect at least once first. I can find nothing in build.prop or sysctl that seems to relate to this behavior, unless I missed something. Additionally, WiFi will drop despite >-72dB signal unless I am actually watching the WiFi AP settings screen for some reason. I have made minor tweaks to build.prop, however this behavior was occurring prior to rooting.
2) I am getting what appears to be OOM-related FCs (no toast ANRs, just a halt back to launcher), yet with what should be enough RAM and spare CPU at the time. This behavior also prior to rooting, and have tweaked some improvement, but it is apparently not enough. I have not messed around too much with DavlikVM settings, as it still is as intimidating as sysctl for me as a newbie at Linux. I have tried to logcat, but can't get a dump at all, it just doesn't seem to log in time. Am I looking at the wrong log?
3) Touch screen locks, and takes all hardware function with it, even just on the home screen. Hardware power and volume don't respond and touchscreen coordinates are locked in place (I have show touches enabled) with no change in anything else; game/app keeps running smoothly, but is convinced that I have frozen holding (or not holding) my touches in place. Recovers in anywhere between 15 seconds to never, requiring me to pull the battery. Persistent after factory reset (did prior to rooting), occurs only when cfq(?) governor is topped at 1001MHz regardless of CPU load. Occasionally multi touch (max 2) fails intermittently, or averages between them (hold both ends and it shows one touch in the middle).
Just to add, any way to kill autocorrect's tendency to put the wrong word in place of a correctly-spelled one in its dictionary? (Changed dictionary to functionary for no reason, both in database). Also, smaller functions drop out, like WiFi icon stops responding, autocorrect suggestions disappear at random, etc.
Related
Hi, all. I've had my Atrix for about two months and I love it. But I've had a problem since day one.
On occasion, the touchscreen input driver will freeze for a short period. I'm not sure about the frequency, but my guess is it happens once an hour, and the duration of the freeze tends to be between 0 and 10 seconds. The state of the screen input, at the instant the freeze begins, will persist throughout the duration. So if the freeze happens when I am touching it, it will continue to register the touch until the input mechanism returns to normal.
For instance, say I'm typing on the virtual keyboard and the freeze happens at the moment my finger happens to be on the backspace key. Even after lifting my finger off the screen, the backspace button will stay enlarged and I'll witness the cursor clear out all the text in the window. Touching other virtual keys during this period has no effect; there is none of the expected haptic or on-screen feedback. At some point, the touch interface will wake up and I can perform an "Undo," or else re-type everything.
Things I've tried:
Updating to the latest Atrix firmware
Various virtual keyboards. It actually doesn't have anything to do with the keyboard, because it happens when I'm doing other activities, such as paging around the home screen launcher or engaging with other apps.
Looking at the Watchdog app immediately after a freeze occurs, to see if something is hogging resources. Since it never reports anything out-of-the-ordinary, maybe it's something with the input driver.
Regardless of what the Watchdog said, I tried various ways to help performance, assuming it could be due to the device running out of memory or the CPU is getting too hot or overloaded. Whatever is the case about the use and misuse of task killers and system apps, the freezing behavior was going on from the moment I got the phone. Regardless, I uninstalled any third party apps I don't use and rooted the device so that I could install various memory management apps (e.g. disabling various 3rd party apps in Autostarts app, SetCPU app configured to max at 900 Mhz, Autokill app setting the system to be more aggressive about keeping unused apps out of memory, used supposedly best practices with the Advanced Task Killer app).
Any thoughts?
-Brandon
Sounds like you have some hardware issues. Looks like you have tried just about everything on a software level.
Maybe try flashing it back to 1.57 manually then OTA it back to a fresh stock 1.83.
If the problem is still there then get it replaced if you still can!
If your not familiar with Flashing, Go Here--> http://forum.xda-developers.com/showthread.php?t=991072
Thanks, I will try to get it returned, and if I can't then I will try flashing it.
-Brandon
I have this same problem ONLY when in the Google Search app. It doesnt matter if I open the app with an icon or the search hardkey, it hangs for several seconds when i try to type my first word. Im using Swype.
Noticing some unexplainable lag just now myself; ffs..
Are you perhaps noticing it while you're connected to a pc via usb? Mine is certainly acting up while on usb connection. I also just re-installed Watchdog tonight.. Try removing that & reboot and see what it does.
No, mine is definitely lagging when I plug it to a usb..
So up until today, I've had not one single issue with my flyer. It's been super speedy and very responsive. I left it last night on the charger uploading a video to YouTube. (WiFi only BTW.) When I woke up the upload was done and the battery was charged. But everything seemed super slugish. Just flipping between home screens was painfully slow. I restarted the tablet and was shocked to see the device hang on both shutdown and reboot. For much longer than normal. I've never seen it this slow. I went in and killed some un necessary services and processes ... No change. I restarted the tablet again and if seemed slightly faster. But not like before still. I haven't tried rooting I'm still 100% stock. Could it be a virus? If so does a factory reset take care of that. Is rather not have to do that but I'm willing If its sure to solve my issues. Any other ideas from anyone? My recent installs include Google+, VidTrim, xda, and soundcloud.
I'll post back here if things change or I find the culprit. In the meantime has anyone else run into similar slowdowns?
P.s. I was wondering if it was an HTC sense issue. It crashed on me once before rebooting the first time and seemed to take forever to load after powering on ... All the animations were laggy and the clock was off by about an hr..... Frustrating. I really like this device.
Hi,
I get a major slowdown on my Flyer when connecting to 'free' public wifi sites. These are sites that provide free wifi after you have signed in via a web page where you enter a username/password or checked a box to accept some terms and conditions etc.
The wifi at my home or via my HTC Desire hotspot is fine as are all other wifi hotspots where I connect directly using the name and credentials stored in my Flyer. It's only these ones that require the additional login that give me trouble.
When it hits, the Flyer becomes unusable for anywhere between 30 and 60 minutes. Hitting the home button generally shows a blank screen that gradually (and I mean g-r-a-d-u-a-l-l-y) redraws. A message stating that HTC Sense has stopped appears and you have the option to restart sense, wait or tell HTC. None of these help as the message box just disappears and then reappears about 30s later. In all cases I've noticed that the sync icon is showing in the notification bar.
It's a real annoyance, but I can mitigate it if I login to the sites before the sync starts. Unfortunately if I accidentally wander into range of one of these sites, and the Flyer finds it and decides it's time to sync then it stops again and I have to very patiently wait for the screen to respond, pull down the notifications, switch to the config settings and switch off wifi. There is still a delay until the sync realises that the wifi is no longer available.
As I said above I also have a HTC Desire that connects to these networks with no problem. This is not running sense however as I needed more application space so instead it's running gingervillain 2.7 (android 2.3.4) and has no problems with the connection.
So I suspect Sense and some synching operation its running. Will do some more investigation tomorrow as more users come online at work.
Cheers.
Haven't heard of any Android viruses that slow down the system like you are talking about, only malware that is disguised as an app. So if you haven't installed anything recently, I would say not any type of malware.
Factory reset may help. But of course, that means starting from scratch re-installing all your apps, setting up your home screens, etc.
I'm attributing it to the fact that the thing had been up and running for like a week. After a restart it seemed to have cleared up. Note to self .. power down and reboot every few days.
I had something very similar...
I installed "a bunch of stuff", then went traveling (across Europe), and tried to use the gps as I went. The flyer slowed to a crawl and became very temperamental. It felt like something was hogging the processor. Several reboots did not fix the problem.
Even sometimes the unlock screen could not get enough processor cycles to complete the unlock.
I started uninstalling the various apps I had installed, and eventually normal service was restored (and has continued fine).
Unfortunately, I was not rigorous about the uninstalling sequence, so I can't be sure what caused it.
My suspicion is that it was an Engine I installed for Text-to-speech settings. But it is only a suspicion. Like I said I installed a bunch of stuff (stupid really).
If someone can point me to an installation history howto, I'll try to be more precise.
Hello XDA,
Ever since I updated my rooted Captivate to 2.3 last month, I have been having a few weird problems.
The first problem is that my phone has a weird refresh issue. Basically, sometimes, when switching apps, the homescreen (launcher pro) and other running apps don't retain their display, icons, status, or information. For example, sometimes when pressing the home key, the app minimizes and the home icons all have to reappear and refresh, taking up to 5 seconds. Another example is when using task switcher to switch to and from Reddit is Fun, the program must reload whatever page it was on instead of just jumping back to it.
This gets very frustrating when dealing with anything that needs to stay idle such as web browsers and certain games. It's as if 2.3 is closing the programs and then relaunching instead of retaining them in memory, but it's not consistent.
The other perhaps more frustrating problem is that the speaker does not work all the time. The phone switches to headphone mode and cuts out all the sound. Smacking the top of the phone sometimes makes it come back. Headphones always work, but this is problematic for me since I use my phone as an alarm. I've tried plugging in phones repeatedly, battery pulls, and made sure all volume is up, to no avail.
Thank you,
Brian
RE: speaker failed
BrianZephyr said:
Hello XDA,
Ever since I updated my rooted Captivate to 2.3 last month, I have been having a few weird problems.
The first problem is that my phone has a weird refresh issue. Basically, sometimes, when switching apps, the homescreen (launcher pro) and other running apps don't retain their display, icons, status, or information. For example, sometimes when pressing the home key, the app minimizes and the home icons all have to reappear and refresh, taking up to 5 seconds. Another example is when using task switcher to switch to and from Reddit is Fun, the program must reload whatever page it was on instead of just jumping back to it.
This gets very frustrating when dealing with anything that needs to stay idle such as web browsers and certain games. It's as if 2.3 is closing the programs and then relaunching instead of retaining them in memory, but it's not consistent.
The other perhaps more frustrating problem is that the speaker does not work all the time. The phone switches to headphone mode and cuts out all the sound. Smacking the top of the phone sometimes makes it come back. Headphones always work, but this is problematic for me since I use my phone as an alarm. I've tried plugging in phones repeatedly, battery pulls, and made sure all volume is up, to no avail.
Thank you,
Brian
Click to expand...
Click to collapse
Brian, I'm actually in the same boat as you.
To fix the speaker issue (in order to get my alarms back) I've had to remove the back cover and apply a good press down on the simcard, and speaker itself. this has brought back the audio for me.
I've had the phone for 2 years though, so not sure if this is the issue/fix you need. But worth a try.
Hello, folks!
I have a rooted I9100 (Android 4.0.3 stock from Vivo, baseband I9100VILP3, kernel 3.0.15-I9100VJLP7-CL371396 [email protected] #3, compilation IML74K.VJLP7, CSC I9100UVILP3).
Sometimes I have problems turning on WiFi, it keeps always turning on and neither become active nor allow me to turn it off again. I then need to reboot phone to fix it (when it reboots, WiFi comes turned on and gets on normally).
Another problem I have with it is that sometimes (average of 4 - 5 times a day) phone loses registration with carrier. It completely loses* signal and shows a "prohibited" icon where signal strength is shown at status bar. (Edit) Sometimes it comes back again in a few seconds and sometimes it stays at that state, making me have to reboot it to fix the problem (turning on and off airplane mode doesn't work; in fact, with registration lost and trying to use airplane mode, it doesn't turn off and only fixes with reboot).
*Actually, it doesn't lose signal (can be seen in "settings - about phone - state" screen uploaded), but only unregisters from carrier.
(Edit: screen/phone language is Brazilian Portuguese)
I've downloaded another modem driver but never had time to test it.
I don't know if both problems can have the same cause, but both of them are very annoying (especially signal loss) and I'd like to make some tries to fix them, so if anyone knows what can I do (even data collection to investigate them), your help is very appreciated.
Thanks
Additional test (ServiceMode)
When I was in the forum to post this thread, I've noticed this other thread and I've decided to use ServiceMode code (*#0011#) to investigate further at the next time my cell lose signal. Unfortunately, it showed absolutely nothing. Literally nothing (just "ServiceMode" caption and no text on the screen below).
I just spent the time to post this because I know that, even if it has shown no information (on screen), maybe it still can be a clue for the cause of the problem.
Thanks
Pls help!
Does anyone have some light to shed on this case?
Please, I do really need to fix it, at least the signal loss problem.
Thanks.
Same Issue in the US on Tmobile
Mine started doing this just a day or two ago. Exact same issue. I can kind of operate on the EDGE network but 4G fails, only WiFi seems to work. T-mobile doesn't seem to have a fix for it.
Changed to MIUI
I've just changed to MIUI (reflashed modem also – now it is ZSLPE instead of previous VILP3).
I still have issues with carrier register loss, but until now it always reconnected after a few seconds. Maybe it is a carrier issue and not a phone one.
I don't turn on WiFi a lot, but all times I've tested it, it worked well.
Another thing I've noticed with this change is that battery temperature while charging used to reach 48°C (118°F) or even 50°C (122°F) while battery level was low (less than 50%), but now it stayed around 35°C (95°F), which is completely acceptable.
Howdy,
I'm currently running CM10 superlite http://forum.xda-developers.com/showthread.php?t=2180695 I have installed the bluesleep fix, but on reading all the information about that, this problem seems separate anyway.
Every time there is an active call, my screen locks as though the prox sensor has been tripped, and the screen will not unlock by any means other than battery removal. This is only while the call is active. If, say, the other person ends the call, I can unlock the screen with the power button as normal. The phone is not sleeping, the screen(and seemingly all input methods) is simply being disabled during the call. I had a call open for 2 hours this weekend because neither of us hung up. I only found out 2 hours later when I took the phone out of my pocket and heard him talking to his wife. hah!
It happens instantly when a call is picked up. No delay, no proximity activation required. When making a call, it happens the very moment you press the "send/call" button. I am trying very hard to remember if this has been happening since I installed the ROM, but can't be positive. I just installed it about a week ago, and can't for the life of me remember if I accessed my voice-mail during that time, prior to today(when trying to delete a message became an issue), but I'm 90% I didn't, meaning this has likely been happening since the install.
I have tried manually increasing the min cpu speed, but, this fix seems to be for a sleep problem, which this doesn't seem to be. It had no effect. All other threads that describe similar problems are either about different ROMs, and/or appear to be about actual sleep mode issues.
I am very happy with this ROM(this issue aside), and have spent a considerable amount of time tweaking and installing things that I really do not feel like doing again. I'm not the type of person who enjoys flashing their phone every other day.
Thanks in advance.
*updated info*
It seems that either using a headset or plugging one in will prevent/fix this problem. It keeps the screen from locking when making a call, and will unlock it if you are already on a call with the screen locked and unresponsive rear/volume buttons. Technically I used headphones, not a headset, but I am guessing it's the same mechanism.
I have tried adjusting any setting related to headsets and screen locking that I can find within the call settings, and anywhere else I can find one that looks related. No luck. Only workaround is plugging in my headphones... which I don't always carry.