Related
After rooting with Damagecontrol, anytime I go from an application back to the home screen, a White HTC shows up, then after 3 seconds goes away, a loading box comes up for about 3 seconds, and the home screen appears. Never happened before root. did I do something wrong? Did I change a setting by accident?
I hate this screen, slows everything down. Anyone have any ideas?
Thanks in advance
That white HTC screen is just the loading screen for Sense. Sounds like something is killing Sense while it's in the background so it has to reload when you go back to the home screen. Are you using any kind of app killer w/ auto kill turned on?
Nope, I had task manager installed, but I uninstalled it and it is still happening.
I'm bumping this to get a reply. I've searched the boards and having found much of anything besides this thread.
After I used rEVOked to root, I started getting this issue. I thought if I updated to the latest firmware, the problem would go away. I was wrong. Still getting this issue about 3-4 times a day which is pretty annoying.
I usually get this whenever I unlock my phone or going to a different home screen. Any help would be greatly appreciated.
jhawk2002 said:
I'm bumping this to get a reply. I've searched the boards and having found much of anything besides this thread.
After I used rEVOked to root, I started getting this issue. I thought if I updated to the latest firmware, the problem would go away. I was wrong. Still getting this issue about 3-4 times a day which is pretty annoying.
I usually get this whenever I unlock my phone or going to a different home screen. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Unrevoked does not unlock NAND. More than likely, not being fully rooted has something to do with your problem.
Well, I've "cleared storage" and I am still getting the same problem... Any other possible solutions?
You said, "not being fully rooted has something to do with your problem", so should I fully root my EVO and see if that works?
You should see that screen when coming from a different home screen. You know how when you start some PC applications there is a splash screen that comes up for a few seconds while it loads? That is exactly what that white HTC screen is.
The HTC launcher is a bit more resource hungry than some of the others, so it has to load some stuff into memory every time it starts. However it is supposed to stay in memory so you can open a music app/game/browser/etc. and then go back to home without waiting for it to load.
If you are seeing that screen something has killed the HTC Sense process since you were last on the homescreen. If you are not running something like a task killer, it is probably that whatever ROM you are running has settings that kill apps quickly, this is often done for performance or battery life, but yours is too aggressive.
Only other possibility I can think of would be if sense is crashing and has to restart every time.
I'm having this same issue. I'm running a stock EVO, and HTC Sense will reloading sometimes when unlocking/tapping home.
I have a feeling it might be related to WidgetLocker, as the only "task killer" app I have is System Panel which doesn't auto-kill.
Anybody else using WidgetLocker and having this issue?
Bump. Still having this issue regularly.... anybody else have this with or without WidgetLocker?
Hey guys, i need some advise here!
For weeks, i anxiously waited for the mailman to bring my my GNex and for a few days im very happy with it. Unfortunatly, the major plus of android, it never freezes, isnt true for my brand spanking new Gnex!
Seeming randomly, the phone freezes, refusing all input from the screen and the On/Off button. This happens about every 20 hrs.
Ususally i advise people with this problem to exchange their phone with a different one, but im afraid i wont get a stock 'yakju' build back in return, so want to try to fix (or at least determine) the problem first.
Can you guys give me some tips on how to get to the bottom of this?
Thanks in advance!
Info:
Model: Galaxy Nexus (GSM)
Android version: 4.0.1
Smalbandversion: I9250XXKK1
Kernel: [email protected] #1
Build: ITL41F (yakju)
And again, it's all stock
...
i had a lot of problems with the 4.0.1 fw, have you tried updating the phone to 4.0.2 it solves a lot of bugs!
I tried to update the phone through the system update menu in the settings, but it listed my phone as 'up to date'. I find this is odd, since i have a Nexus ánd the Google build
Is there a way of updating the phone without a lot of hassle?
I looked into it, in the Netherlands the 4.0.2 update should roll out in a few days. If it isn't, I'm going to flash it myself! Were your problems with 4.0.1 similar to mine e.g. crashes and freezes?
Sent from my Galaxy Nexus using XDA App
In my experience most of the time when that happened was caused by 3rd party apps that weren't ics optimized.
Sent from my Galaxy Nexus using XDA App
Well freezes and crashes maybe, but the whole phone unresponsive? Isn't there a try/catch somewhere which prevents this kind of 'dirty code' to crash the whole OS, anyway there should be.
Also, ( I forgot to mention this in #1) the phone reboots sometimes while its active as well as when its idle. The rebooting is always paired with a loud *click*
Sent from my Galaxy Nexus using XDA App
Same problem
Panatella said:
Also, ( I forgot to mention this in #1) the phone reboots sometimes while its active as well as when its idle. The rebooting is always paired with a loud *click*
Click to expand...
Click to collapse
That exact thing happened to me yesterday as well (running 4.0.1). I pulled down the notification bar, clicked on the email notification, and when the notifybar started collapsing again, the animation stopped, sound was caught in a loop, and two seconds later my phone rebootet with a clicking sound (I hope that it was just the speaker reacting strangely to the sudden signal loss...!)
The same day, the Nexus kind of crashed while I was streaming internet radio to my bluetooth speaker. The music kept on playing fine, but I wasn't able to turn on the screen. Even holding the vol+/- and power buttons only shut the phone down, but I couldn't restart before I removed the battery.
I really hope this is gonna be fixed with the 4.0.2 / 4.0.3 firmwares. This thing is crashing a little too often right now, for my taste
I'm getting the same problems as noted above. I've just picked up the nexus to move away from Apple's iPhones, but I'm left wondering I've made a serious mistake in doing so. An added problem is that the crash has also occurred when I've been recharging the battery while asleep- so the alarm I set did wake me.
Honestly, it's an unreliable product. I'm a customer, not a Samsung lab rat.
Got the same issue. 2 crashes in 4 days. Not a huge problem for me yet, but 4.0.3 better fix it.
Well most of my problems went away when i updated my phone. You should definitely try to update. Personalty I went straight for 4.0.3. The best ROM i've tested is definitely Android Open Kang Project :http://rootzwiki.com/topic/11455-rom-android-open-kang-project-maguro-build-13/
Everything just went so smooth and bugfree as far as i can tell. And i love the quick setting he put in notification bar.
You can see how to unlock your phone here using the gn toolkit :
http://forum.xda-developers.com/showthread.php?t=1392310
I had those kinds of crashes, too. My phone would crash maybe once every 3-4 hours on 4.0.1... doing anything. Whether it be idle, with no extra services (factory reset), or while composing messages. Anything would do it.
Anyway, I rooted the phone and I've been on Bigxie's ROM since V1 (AOSP 4.0.3) and the issue stopped, for the most part, except for an idle reboot every 18-28hrs. Suspecting it was kernel related, I swapped out the Apex kernel and threw on Franco's... since then, my phone can run for almost two days (of moderate usage) without a charge.
Any of you guys enabled 'force 2d hardware acceleration'? I don't know how relevant it is, but all my problems went away when I stopped to use this function.
Sent from my Galaxy Nexus using XDA App
Uv'ing too low can crashes also.
My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.
Well this is exactly what is happening to me on my phone, it reboots every 2 days or so. sometimes it becomes completely unresponsive, the keyboard doesnt open up or of it does, it doesnt accept any input
even the settings page starts crashing, i dont know what is going on
it works ok otherwise but this crashing and becoming unresponsive is really driving me crazy. i have 4.0.1 as i am in the UK and since they are not releasing 4.0.3 for such a long time here, it means the fixes available in it is not really for stability and maybe they are for LTE version available in the US
Also, I dont have the 2d acceleration checked off already, so not sure what else to do to fix it. should i return the phone???
dhruvraj said:
Well this is exactly what is happening to me on my phone, it reboots every 2 days or so. sometimes it becomes completely unresponsive, the keyboard doesnt open up or of it does, it doesnt accept any input
even the settings page starts crashing, i dont know what is going on
it works ok otherwise but this crashing and becoming unresponsive is really driving me crazy. i have 4.0.1 as i am in the UK and since they are not releasing 4.0.3 for such a long time here, it means the fixes available in it is not really for stability and maybe they are for LTE version available in the US
Also, I dont have the 2d acceleration checked off already, so not sure what else to do to fix it. should i return the phone???
Click to expand...
Click to collapse
U sure it's not a software u installed recently? For me changing back to the stock music player fixed the random crashing.
In general, I can say some apps are not stable at all.
I experience random crashes too, although they coincide with the sudden loss of signal, as described in these threads:
http://forum.xda-developers.com/showthread.php?t=1390816
http://forum.xda-developers.com/showthread.php?t=1387943
http://forum.xda-developers.com/showthread.php?p=20816554
I have started to make some logs to try to identify the cause of this problem. I use Log Collector for making a log and No Signal Alert to obtain a time stamp when the signal drops. What I see in the logs is that just before the signal drops I notice an entry in the log something like "process:com.lookout has died". Could this have something to do with the Lookout app I have installed or is it just coincidence that the app and a certain Android process have the same name?
By the way, does anybody know if there are websites or people who can analyze the logs I have created? Most of the content is mumbo jumbo to me and a knowledgeable person might be able to shed some more light on what happens inside the phone and what might trigger this problem.
I just upgraded to 4.0.2 on Thursday, but the problem persists.
Android version 4.0.2
Baseband Version: I9250XXKK6
Kernel Version: 3.0.8-gaaa2611
[email protected]#1
Build Number: ICL53F
ICS stock; non-rooted
Well i guess you tried already to remove the lookout app right?
My GSM Nexus with stock 4.02 (unrooted) freezes randomly too.
When it occurs i cannot switch the screen on using the power button. Only thing that helps in this state is pulling the battery.
Iam starting to get extremely annoyed by Google/Android because my previous smartphone the Nexus One was also buggy ever since the Gingerbread update while beeing perfect with Froyo.
It's definately my last Android device if this will not be fixed with 4.03.
The phones are way too expensive to be a happy participant of a perpetual Google beta.
b4cksl4sh said:
My GSM Nexus with stock 4.02 (unrooted) freezes randomly too.
When it occurs i cannot switch the screen on using the power button. Only thing that helps in this state is pulling the battery.
Iam starting to get extremely annoyed by Google/Android because my previous smartphone the Nexus One was also buggy ever since the Gingerbread update while beeing perfect with Froyo.
It's definately my last Android device if this will not be fixed with 4.03.
The phones are way too expensive to be a happy participant of a perpetual Google beta.
Click to expand...
Click to collapse
Are you sure it's the OS not some buggy/incompatible apps? I've had the phone since launch and it never froze even once. Stock 4.02 too.
And you should try out different OS. Then you will know what suits you.
Anyone else getting this error? After reading the two main errors seem to be faulty camera hardware and bar code scanning apps. I uninstalled my bar code scanner and the problem persists. There is a small dent next to my flash under the camera but this came with the phone and my camera worked for a while. Taking the battery out and putting it back in fixes the problem about half of the time, but only is good for one to two uses. I'm thinking of sending this in, but I'm waiting until the SGSII HD is out in case they offer to replace it with any phone. Wishful thinking, I know.
And here's the error:
Are you on the stock rom? I got that yesterday but a reboot fixed it.
HJZS2K said:
Are you on the stock rom? I got that yesterday but a reboot fixed it.
Click to expand...
Click to collapse
Stock ROM not rooted. No modifications what-so-ever.
8mileroad said:
Stock ROM not rooted. No modifications what-so-ever.
Click to expand...
Click to collapse
Try doing a factory reset. Sometimes an app installed on the phone might screw up with a hardware's function. For example, I've always use Screebl Pro on my phone to let it control how my screen turns off. I decided to try their new Beta version. A few days later, I cannot seem to manually turn off my screen by pressing the power button. Every time I press the power button, the screen will come back on on its own. I can try up to 4-5 times before it eventually goes off. I though my phone finally broke as I tried uninstalling and reinstalling apps, changing settings here and there to no luck. I finally realized about the beta Screebl I had installed, and decided to disable it. The moment I did that, the phone was back to normal, no weird things happening to it.
So try doing a factory reset first before sending it back.
Strangely enough uninstalling Reconage has seemed to fix this. Can anyone else confirm it breaks your camera? The comments don't say it does so it must be something with the Nitro.
I get it too on cm7 all the damn time. I can record 1 video then after I stop, it messes up and I have to reboot to record again.
Any more definitive answer on this issue? My wife's Nitro HD has started giving this error in the last few days and no amount of rebooting seems to be fixing it. She is stock plus a few apps. I uninstalled nearly everything that uses the camera, reboot the phone, and still have the problem.
Alternatively, is there a way to see what apps were installed/updated by date? The last photo she took was on 6/13, so if we can figure out what apps have been updated since then that might help us get to the bottom of the issue.
Hi all -
I'm on AT&T, 100% stock, non-rooted, etc. I upgraded to JB last night via Kies without issue.
However, ever since the upgrade, my phone won't go more than 5 minutes without freezing and then crashing.
It's a very odd behavior... the screen will still animate. So, if I'm playing a game with a timer, the timer will still count down. But all touch input (including menu/home/back) does nothing. Home/back don't illuminate or do anything, but they do provide haptic feedback. Power button does turn the screen on/off.
Eventually after a few minutes, the lock screen comes up with the "tip" even though I've clicked to never show it again. However, it barely registers a swipe to unlock when it freezes again. At that point, it will usually self-reboot.
I've tried to enable some of the developer options to see if maybe there was a rogue program that was incompatible with JB, and maybe causing the issue, but I couldn't see any correlations.
I really want to avoid doing a factory reset if at all possible, as I have a game that I worked really hard on to beat a few levels, and I'd hate to lose my progress.
Anyone have any ideas on what I can try?
I should note that uninstalling programs is iffy... sometimes it works, other times it just uninstalls indefinitely.
Thanks!
Castaway78 said:
Hi all -
I'm on AT&T, 100% stock, non-rooted, etc. I upgraded to JB last night via Kies without issue.
However, ever since the upgrade, my phone won't go more than 5 minutes without freezing and then crashing.
It's a very odd behavior... the screen will still animate. So, if I'm playing a game with a timer, the timer will still count down. But all touch input (including menu/home/back) does nothing. Home/back don't illuminate or do anything, but they do provide haptic feedback. Power button does turn the screen on/off.
Eventually after a few minutes, the lock screen comes up with the "tip" even though I've clicked to never show it again. However, it barely registers a swipe to unlock when it freezes again. At that point, it will usually self-reboot.
I've tried to enable some of the developer options to see if maybe there was a rogue program that was incompatible with JB, and maybe causing the issue, but I couldn't see any correlations.
I really want to avoid doing a factory reset if at all possible, as I have a game that I worked really hard on to beat a few levels, and I'd hate to lose my progress.
Anyone have any ideas on what I can try?
I should note that uninstalling programs is iffy... sometimes it works, other times it just uninstalls indefinitely.
Thanks!
Click to expand...
Click to collapse
This sounds somewhat familiar to my experiences with JB. I rooted right away with the stock JB and had freezing / crash issues. So I then went pure stock and had issues (un-rooted). I then tried a custom TW-based ROM called BlackJelly and had issues. Now I am on CM10.1 which is AOSP JB4.2.1 based and things are even worse.
There seems to be no JB ROM that is stable for my phone. Getting very tired of this.
See my thread for details:
http://forum.xda-developers.com/showthread.php?t=2044769
- Ed
Strangely enough, my issue ended up going away. I think it was a rogue program that needed it's dalvik cache rebuilt. Once uninstalled, the phone worked great. Not sure what app it was.
Stock/no root Tmo Note 3, with latest nk3 firmware update (ota) , WiFi won't turn on. In notification panel you tap WiFi button and it hangs partially green but not fully bright green, doesn't connect. In settings slide button is grayish but no connection, won't slide to off just sits there not connecting. A restart will put switch back to off, mobile network works fine just can't get WiFi to start.
Sometimes it works after phone sits for a while. Basic apps installed no facebook app or weird games.
This condition started recently out of nowhere, no problems after ota back in November, phone has same case since new back in Oct/2013 , phone has not been dropped or dunked in toilet.
No flashing or root attempts, download mode and stock recovery can be accessed. Not looking to flash custom ROM, rooting is a possible option if needed to solve issue.
Pp.
same here bro
PanchoPlanet said:
Stock/no root Tmo Note 3, with latest nk3 firmware update (ota) , WiFi won't turn on. In notification panel you tap WiFi button and it hangs partially green but not fully bright green, doesn't connect. In settings slide button is grayish but no connection, won't slide to off just sits there not connecting. A restart will put switch back to off, mobile network works fine just can't get WiFi to start.
Sometimes it works after phone sits for a while. Basic apps installed no facebook app or weird games.
This condition started recently out of nowhere, no problems after ota back in November, phone has same case since new back in Oct/2013 , phone has not been dropped or dunked in toilet.
No flashing or root attempts, download mode and stock recovery can be accessed. Not looking to flash custom ROM, rooting is a possible option if needed to solve issue.
Pp.
Click to expand...
Click to collapse
hey bro i have exactly the same problem , but my case is slightly different i am having this problem since i have rooted my phone now i just cant find any way to solve it , i just think its a hardware problem. if u come to find any solution plz dont forget to post it here. i am waiting for ur reply.
Will do that, been looking around but nothing yet, have read a bunch of stuff in Google, similar but not the same issue.
I'm suspecting the modem but have not attempted to flash or look for modem file yet.
Not sure if I'm going to find it here anyway, this Note 3 thread is the lamest thread here, I see a lot of questions asked here that go unanswered, I have asked questions in the past that got no response, and simply ones too.
I also follow the T-Mobile S4 thread and there you get a ton of activity but here, it's like pulling teeth.
Anyway I will post back for your sake if I figure out something.
Pp.
Tried reseting modem with this http://forum.xda-developers.com/showthread.php?p=52735067
but still acting up now and then .
But toggling "airplane mode" on/off un-greys wifi button and it works smoothly.
Pp.
So, the device has always been stock, never been rooted or anything, never had any custom firmware on it? I am understanding this correctly? And that being the case, this means the device has also never had the data partition scrubbed?
Honestly, I would strongly recommend wiping the device and installing the NK3 firmware via odin. I'm not sure you are going to find a solution.
One thing you can do first, is root the device, and download the app "LogcatX".. open the app, run a logcat, then hit that wifi toggle. Save the logcat and post it here.
I highly doubt this is fixable without a re-install of the OS, however.
Good luck
I had considered root just for debloating purposes and re-flashin the firmware but with an update around the corner I can toggle airplane mode for a bit longer.
I like stock touchwiz and also need reliability from the phone so won't be considering a custom rom.
Pp.
Use Tweaked ROM. It's more reliable than stock.
Kind of funny, you mention you need reliability and because of that you won't root and install custom firmware. Yet, your device is bone stock and your WiFi is broken. Lol.
Think about it.
Wifi is just an extra, I rely more on my unlimited data plan and living in the metropolitan area LTE is always strong and plentiful. Wifi comes in handy when downloading huge files, pdf's and some large images (work related )
and using download boost. Wifi calling is handy also to have but haven't really needed it.
So it's nice to have working. But not the end of the world.
Pp.