Hello,
I got an problem on like 4 of the 5 kaisers here.
The problem is that sometimes the kaisers goes into an sleep where it doenst come out without reset.
You will get an black screen and the light of your keyboard is on and doesnt turn off. When this happens the battery goes from 100% to 0% in like 40 mins. without the problem i can use the phone for 2 days.
My question is how to solve this? I tried the following things.
- Radio 1.65, 1.70. 1.71
- 2 different hspl
- old and new kernel.
- and loads of different roms. from gingerbread to eclair.
Any solution or fix for this? because i can't use it for daily base now since when i dont notice the battery is empty of that bug.
Best Regards,
Veldmuus
That's the black screen of death. I never get that, but it's one of three problems that I have heard of. I think it might be related to going to sleep. I use the latest kernel, from git, which is pretty much identical to scooter1556's kernel with separate cache. What kernel are you using?
The second problem is the white screen of death, which I get a lot when I leave the phone on the charger. The screen is white bright, the kernel is not crashed. Sometimes Fn-Right-soft-key twice will cure this, but usually not. Some have guessed that this has something to do with the phone going to sleep not quite properly while charging. There is an option to not go to sleep while connected to a charger, and I haven't tried that option for a long time.
The third problem is a kernel crash (screen freezes, keyboard doesn't turn on LED, etc) caused by compcache (zram). Can be avoided by not using compcache.
The most annoying issue I have is that I've never figured out how to tweak the build so that apps can be installed to SD. I've been trying to change initrd so that, when installed completely on NAND, the sdcard is completely managed by vold. So far no success, and I've pretty much moved on to my newer phone (Rhodium, aka AT&T Tilt2).
I have spent the last week or so "tweaking" my build.prop file, adding lines for disabling sleep mode, 3G speed tweaks (doesn't do much yet) and fixing small compatibility issues such as AGPS/GPS not working. So far so good, no more sleep of death/black screen/white screen.
If successful, I would ask that the modified build.prop file be added to the Froyo builds on SourceForge, intergrated directly as to eliminate "end user interaction", meaning you won't have to touch it.
I am also looking into some sysinit.rc mods as well, but I haven't had much time lately.
Veldmuus, do you have a way to edit your own build.prop file such as Root Explorer, or would you have to push it to the phone via ADB?
Does anyone else have issues with the WiFi connection while the screen is turned off? I noticed that not a single one of my music streaming / radio apps work when the screen isn't on. It works for maybe a minute before all sound just stops. Starts just fine again once I power up the screen.
Has there been any changes done to the handling of these matters in ICS perhaps?
Pretty annoying not being able to stream music over WiFi as I think I'll hit my 5GB limit on data pretty fast if I can't use the WiFi at work for this.
So has anyone else noticed these issues?
SBS_ said:
Does anyone else have issues with the WiFi connection while the screen is turned off? I noticed that not a single one of my music streaming / radio apps work when the screen isn't on. It works for maybe a minute before all sound just stops. Starts just fine again once I power up the screen.
Has there been any changes done to the handling of these matters in ICS perhaps?
Pretty annoying not being able to stream music over WiFi as I think I'll hit my 5GB limit on data pretty fast if I can't use the WiFi at work for this.
So has anyone else noticed these issues?
Click to expand...
Click to collapse
Yeah same here. I remember this being an issue with Android 2.1 for my Desire but was fixed in custom roms. Might be the same situation here again.
I remember this being an issue with my Nexus One, don't remember if it was fixed in 2.2 or 2.3. I remember testing file transfer using SwiFTP, with the bug the file transfer would go down to double digits (kB/sec), with the bug fix it would be a few hundred kB/sec, with the screen on it would hit mB/sec or so (in any Android version).
I believe this is the official issue:
http://code.google.com/p/android/issues/detail?id=9781
With my Nexus S I'm not experiencing this bug. Sscreen on still gives me a major wifi speed boost, but screen off I get a few hundred kB/sec, which should be more than enough for any streaming app. KiloBYTES btw, not bits. I'm surprised ICS and/or Galaxy Nexus brought this problem back. Or it could be something else entirely.
Are you connected via 2.4GHz or 5GHz wifi? I would think the new 5GHz radio in the GN probably has more aggressive power saving features. Try switching to 802.11b/g (instead of 802.11n, in any frequency), see if it helps.
Have you changed your WIFI sleep policy?
On my Froyo phone, if you hit menu while in the WIFI settings (I know there is no menu in ICS) you get an option to go into advanced settings where you have the option to choose your WiFi sleep policy (When screen turns off, never when plugged in, never).
There should be a way to access that advanced settings area somewhere.. My phone is a couple hundred miles away right now and I won't see it for another week so I can't be of much further help right now. However, there "was" a setting in previous versions.
best info at the time last year was here for the N1
http://www.google.com/support/forum/p/android/thread?tid=01a47ff5b0a92d52&hl=en
7xx replies there to read, but really good info. somewhere in there, maybe around#600 the info gets good, can't remember. But shortly around this time the problem was gone/fixed.
there was a guy with an app i think it was wifi fixer, i could be wrong. that worked sometimes, but battery drain was bad. Whatever google, or CM did fixed the low power save mode issue. I'm thinking it was something at the kernel level?
edit, on second thought, there's no good reason to read all that. You won't get a fix out of it anyway. It was updated away in the end, something related to MAC addresses and build numbers and frf50 or some such.
BUT this seems like the same kind of thing going on in the power save mode.
Have you checked your advanced settings?
Wi-Fi>>(settings [bottom right])>>Advanced>>Keep Wi-Fi on during sleep...
Mine was set to always by default, so I suspect that the issue lies else where...
Neville.Holland said:
Have you checked your advanced settings?
Wi-Fi>>(settings [bottom right])>>Advanced>>Keep Wi-Fi on during sleep...
Mine was set to always by default, so I suspect that the issue lies else where...
Click to expand...
Click to collapse
Same here. Mine was set to always by default but still getting this issue.
Sent from my Galaxy Nexus using XDA App
I would suggest that this issue is related to the individual applications you are using, rather than anything to do with Android.
I am able to stream music from Google Music via WiFi just fine when the screen is off, and I am also able to talk to someone on Skype via WiFi just fine when the screen is off.
oscillik said:
I would suggest that this issue is related to the individual applications you are using, rather than anything to do with Android.
I am able to stream music from Google Music via WiFi just fine when the screen is off, and I am also able to talk to someone on Skype via WiFi just fine when the screen is off.
Click to expand...
Click to collapse
Thanks for posting that; I was getting pretty worried and disappointed after reading this thread. I had to deal with this when I first got my Nexus One, until Google released the 2.2.1 update with a new Broadcom driver which finally fixed the issue. No streaming, no pushes, just nothing at all from wifi when the phone went to sleep. All traffic to/from the phone would just stop. It was maddening.
The Galaxy Nexus comes to Canada a week from today, and this would've been a show-stopper for me. At least it's working for you, so my day isn't ruined quite yet
Has this issue ever been nailed down? I've seen considerable discussion on it going back years. I've seen considerable speculation regarding WIFI mode and Governor. I've seem many of the bug reports marked closed.
Yet I have a GN on v4.0.4 and the moment the screen goes off - either because you turn it off or it just times out - the WIFI goes to h*ll. I've run ping and network trace from both sides and there is no doubt the WIFI stays connected, however latency goes way up and packets are lost... and with TCP connections it gets congested with retransmits. I've run with the governor set to "Performance" and there is no difference.
So, is there any consensus on what is causing this problem with current stock hardware/software?
I read that it's something that's been coded in for a while. Try using this:
https://play.google.com/store/apps/details?id=com.ratcash.wifiperf
-Sent via XDA Premium-
Ok, to answer my own question, this is still related to the PSP issue from years ago:
code.google.com/p/android/issues/detail?id=9781
code.google.com/p/android/issues/detail?id=15549
Bottom line is that some hardware - like GN - has an additional level of PSP on WIFI. The issue was resolved by inclusion of an additional lock mode - WIFI_MODE_FULL_HIGH_PERF - some time ago. However, its up to an application to request the new lock state if it thinks it needs it. Many don't.
So, its probably not a bad idea to contact developers of the various applications and recommend they look into the new lock level in the later APIs.
Also, the "WIFI High Performance Widget" can be used to manually hold a WIFI_MODE_FULL_HIGH_PERF lock on the WIFI if you're dealing with an application that isn't doing it its self. Beware of the other "WIFI fixes" out there, none of the ones I tested were acquiring the correct lock.
Also, from an adb shell you can use "dumpsys wifi" to see who is holding what lock, for example:
Code:
Locks acquired: 5 full, 5 full high perf, 5 scan
Locks released: 4 full, 4 full high perf, 5 scan
Locks held:
WifiLock{PANDORA type=1 [email protected]}
WifiLock{HighPerformance type=3 [email protected]}
Here you can see Pandora is only holding type=1 (WIFI_MODE_FULL) and HighPerformance is holding type=3 (WIFI_MODE_FULL_HIGH_PERF). Dumping the WIFI state takes the guess work out of it.
Tried that widget, having absolutely no luck with 'in tune' and 'winamp' for radio with the galaxy nexus verizon...
as soon as the device sleeps, wifi goes to hell and buffer drops in and out every 2 seconds. Completely unusable, any recent fixes? this is totally making me think I just bought a $400 brick since this feature was very important for me.
What may be confusing about that widget is that it is a "widget". You have to locate it under "widgets" and then put it on the surface and then click it to enable it... it should be blue when on, and black when its not.
tlum said:
What may be confusing about that widget is that it is a "widget". You have to locate it under "widgets" and then put it on the surface and then click it to enable it... it should be blue when on, and black when its not.
Click to expand...
Click to collapse
I have been trying to put the 'widget' itself (2x2 square) on the home screen but even if i hold and drag it to where I want it, it never actually appears on the screen. And of course i'm still getting crazy ping times...Does anyone else have this working on a GN (verizon - not that it should make a difference)?
I have found a few workarounds to this issue, none are great and frustrate me greatly.
1. Root and use the franco kernel. Seems people with that have no issues - since you can set? the wifi to full performance.
2. Use this wifi performance widget
3. Use an app that has properly set its own wifi settings. - Going through all the radio apps on the google market, i am finding only one app that seems to be doing this right: DI Radio - some kind of dance/techno/etc - confirmed it with ping times, they remain low on sleep.
Not one other radio app seems to have set 'proper' settings - which shows that something needs to be addressed in the os...I was having good luck with the yahoo music app, but depended on the stream (maybe some buffer more :dunno - the ping results are garbage.
EDIT: I tried installing high performance wifi again, and finally got the widget to one of the homescreens! Let me break it down for anyone else who comes across this. After install, the small 1x1 blue app box is put on your desktop and the black screen comes up with the wireless networks and a checkbox. I then went to apps->widgets and tried putting the 2x2 widget on the home screen again, and like always it clicks on like its there (and when you click home and its never there). However, this time I hit BACK instead of home after dropping the widget and it took me back to the black screen with the checkbox, then i hit home and voila its sitting there. You can click on it like you mentioned! Confirmed with ping for tune in...pings remain low.
If this continues to work, it may be a godsend. It is annoying having to have this, but far far better than not.
I had that problem also especially when i tried to download big files when the screen turn off the download speed became extremely slow, this widget solve this, i think to that moment its the easiest solution tap it when you need it tap it again when you done.
By the way i had this problems with franko kernel also and again to my opinion it is the good solution for now, until the apps developers update their apps.
Sent from my Galaxy Nexus using XDA
If you download the SDK - you only need Android SDK Platform-tools - to a PC and use the adb shell it is easy to dump the WiFi lock state with dumpsys wifi and see exactly which app(s) are holding what locks. Completely takes all of the guessing out of who is doing what when. Judging the behavior can be subjective because there are other reasons that the WiFi can break up which can be very frustrating.
developer.android.com/guide/developing/tools/adb.html
Erlang2012 said:
I had that problem also especially when i tried to download big files when the screen turn off the download speed became extremely slow, this widget solve this, i think to that moment its the easiest solution tap it when you need it tap it again when you done.
By the way i had this problems with franko kernel also and again to my opinion it is the good solution for now, until the apps developers update their apps.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
The app does work well, however I have been running into some issues as I continue to use it. It randomly decides to turn off the forced max wifi (even though its still blue and looks like its operating) or perhaps the phone is forcing the wifi issue again. It seems to happen when you are downloading, playing with some other apps? You only notice it when you sleep it and the streaming radio immediately starts having issues.
Solution is to flip back to the widget turn it off and turn it on again. It works, but is another annoyance.
I haven't yet ascertained exactly what causes it to switch off yet.
tlum said:
If you download the SDK - you only need Android SDK Platform-tools - to a PC and use the adb shell it is easy to dump the WiFi lock state with dumpsys wifi and see exactly which app(s) are holding what locks. Completely takes all of the guessing out of who is doing what when. Judging the behavior can be subjective because there are other reasons that the WiFi can break up which can be very frustrating.
developer.android.com/guide/developing/tools/adb.html
Click to expand...
Click to collapse
I will look into this, thank you.
---------- Post added at 06:16 PM ---------- Previous post was at 05:28 PM ----------
I used the adb shell (learned how to install all these dev tools and how to use it first ) and here is some updated info:
Tunein = type=1
Pandora = type=1
Audioaddict service (Digitally imported app I posted above previously) = type=3
google music = type=3
High performance app = type=3 (havent figured out why this likes to stop randomly)
I will update with more app info, hopefully others can also email the developers and see that it gets fixed, so we no longer have to use damn workarounds...
jeep364 said:
... It randomly decides to turn off the forced max wifi (even though its still blue and looks like its operating)...
Click to expand...
Click to collapse
Yes, it definitely has an issue holding its lock, and it definitely seems related to another application taking over and also when it switches to cell and back, I can confirm that. It may be related to the OS since the widget thinks it still on when clearly the lock as been released, so it may be that the OS released the lock and the widget has no idea. I haven't taken the time to look into the details yet, and this is something we should make the developer aware of.
tlum said:
Yes, it definitely has an issue holding its lock, and it definitely seems related to another application taking over and also when it switches to cell and back, I can confirm that. It may be related to the OS since the widget thinks it still on when clearly the lock as been released, so it may be that the OS released the lock and the widget has no idea. I haven't taken the time to look into the details yet, and this is something we should make the developer aware of.
Click to expand...
Click to collapse
Yup, from what I can see it loses lock:
1. when cell switching
2. manually killing/starting wifi
3. when ANY application is downloaded/removed (ie. changes in permissions)
4. when playing with dolphin, other apps for more than a few minutes, it will kill it even though the blue stays lit. I think its as you mentioned, during general use of the phone, at some point some permissions are changed and hifi performance is tossed off its lock.
If you only are streaming music and re enter the phone to check a gmail alert or two...it seems to be fine. otherwise you need to hit the lock widget one more time before sending it to sleep with pandora/tune in playing.
Logcat #1 - http://pastebin.com/QwiBtnWg
Logcat #2 - http://pastebin.com/GnZe6S4s
Hiya,
DHD, running Cyanogenmod (running the 16th November 2011 nightly), with LordMod 8.5 CFS kernel. The nightly seems to me to be better than the stable release; the battery drain has been fixed and there don't seem to be any noticable bugs, so I don't think this is a CM7 nightly issue.
----
I recently downloaded "Traffic Panic Attack 3d" from the android market - and it's a great game There's over a million downloads so should all be good. However when you cause a large crash sometimes a car explodes, but this explosion seems to crash my phone - about 2/3 of the time a car explodes, the game freezes and eventually the phone completely locks up and dies.
The first time it happened I assume my phone had had a mishap or something and ignored it, but then I realised it was the same game causing at at this certain point. I attached it to ADB and tried to logcat it, but it seems to stop logcatting after a while so the second logcat is started after I lost responsiveness of the phone.
The screen freezes and the soft touch buttons still respond, but then they stop working and it completely freezes. If you quickly do "adb reboot" it'll reboot the phone but another time I just left the phone to see if it could recover itself, and then not even adb reboot would work, it just went to a new line, as if it were trying to connect, but didn't ever get through. I pulled the battery (it then said no status, so was clearly trying to reboot the phone) and turned it on, and all is fine again.
Any idea if this is an issue with the app, my phone or what? I can only assume the explosions are particularly GPU/CPU heavy and it causes my phone to fall over.
First logcat (http://pastebin.com/QwiBtnWg) stops after the first crash (phone rebooted itself so logcat stopped) the second (http://pastebin.com/GnZe6S4s) is started during a lockup I think, and I had to pull the battery to get it do anything.
Are you using ADW launcher by any chance?
Yes, I am - the free version that comes with CM7
Why?
No such game on Market :-?
https://market.android.com/details?id=com.neonplay.trafficpanic2
And just seen the reviews (I saw different ones on my phone that talk about any problems) - it seems I'm not alone with this issue, and it's not just the DHD either
Sorry for the delay in replying.
I asked about ADW Launcher because I was reading this as that was describing similar symptoms & error messages. This was caused by an OpenGL issue & ADW Launcher, as far as I could tell.
Have you downloaded Chainfire3D from the market & installed the OpenGL driver. If you have, try uninstalling the driver & try again. And if you haven't install the driver & try again.
Thanks for the info.
I installed the driver, but no luck. But then again I think it must be the app rather than anything else as so many others are also having problems.
Hi all,
I am struggling with an issue that pretty much makes the Kindle Fire useless for my usage.
Basically the KF will be carried around by users - who will be alerted by a sound from the Kindle Fire when it received a message over WiFi.
Problem is, I cannot get the WiFi to stay reliably connected when the screen turns off.
I have tried WiFi Keep Awake - with limited success. It helps some of the time, but is unreliable.
To test this, I am simply pinging the KF from a PC - and in many instances it refuses to respond. Using WiFi Keep Alive I have even found it not rejoin the WiFi reliably once the screen is turned on.
This is essential for what I need - and I find it bizaare as well if you wanted to use for email etc that it seems to drop off.
So - firstly, has anyone solved this without installing a custom ROM?
Secondly, can it be solved with a custom ROM (maybe stock Android)?
Any help appreciated!
Thanks
I would definitely try a custom ROM. Most of the ROMs here are rock solid. Also I would try this app. It's free so you can sideload it if you don't have the Play Store.
The ROMs I've used that have the most stability are Gederom v1.7, CM9 SGT7 based ROM by twa_priv, and CM10 SGT7 based ROM by twa_priv.
Thanks - will give that app a try.
I want to avoid a custom ROM if I can........
Since I upgraded my KF to JB ROM, I saw that I have problems with the Pulse app.
If I read more than 25-35min the newsfeeds, the device becomes unresponsive, and all I can do is a hard reset to make it back to life.
What is strange is that I have radio playing in the bg, just for test, and it keeps singing, while in freeze state, though with short interruptions.
I suppose it is the RAM overloading problem, but anyway this is annoying.
So, is there any way to solve this so that I can keep reading the Pulse? Maybe there is someone that could give an advice about how to overcome this obstacle?
(I use to have 2 pages with 150+ news titles on every one of it)
[SOLVED]--------------------------------------------------------------------------
Well, after all the views of this thread, and no answer, this is the idea I came up with:
- installed RAM manager Pro
- in settings, chose "Balance" mode
- in settings, chose "VM Heap size" to "64m"
Now it still makes some sluggishness, but it is rare, short and at never froze my KF since.
Thanks!