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?
Related
I just updated to DK28 using the update.zip over stock software (no root) and on top of various new features and new bugs, I've noticed a strange new behavior.
At least several times per hour, my phone will give a quick vibration pulse, then maybe a second or two later will give two (or sometimes three) real quick pulses. I have no idea why it's doing this and whether it means something or not. Anyone know?
I can't seem to correlate the behavior to anything in particular the phone is doing at the time. It happens with the phone sleeping, and it does it while I'm using it. It happens when I'm on the home screen, when I'm reading web articles, when I'm playing with other apps, when it's on the charger, when it's off...
pilby said:
I just updated to DK28 using the update.zip over stock software (no root) and on top of various new features and new bugs, I've noticed a strange new behavior.
At least several times per hour, my phone will give a quick vibration pulse, then maybe a second or two later will give two (or sometimes three) real quick pulses. I have no idea why it's doing this and whether it means something or not. Anyone know?
I can't seem to correlate the behavior to anything in particular the phone is doing at the time. It happens with the phone sleeping, and it does it while I'm using it. It happens when I'm on the home screen, when I'm reading web articles, when I'm playing with other apps, when it's on the charger, when it's off...
Click to expand...
Click to collapse
I got that too, plus lag and other bugs when first went to 2.2 (rooted 2.1 and used update.zip). Did you wipe when you updated? I didn't so it was acting weird... Plus the GPS didn't work so I did the Odin thing and now it works fantastic.
Did you wipe when you updated?
Click to expand...
Click to collapse
No. I probably should.
I just wondered whether these little vibration pulses were meant to indicate something, or whether they're just a bug.
happens when an app crashes
My vibration was related to turning on the WIFI became very unstable. The DK28 I had came with clockwork mod so I did a recovery to Epic Experence 2.0.7 chosing the recover form a specific zip file I had copied to my SDcard. Fixed the vibration problem and my USB connection then agin worked on my Windows 7 laptop
I reinstalled my android build over and over and tried various builds (not so super and incubus super froyo) both have the same effect, if i have the phone inside my jeans, it sometimes wont awake the screen and it just stays off,....
sometimes i can still controll the touchscreen and unlock and putt phone off.
but else i am doomed to push the reset button..
does anyone have the same sleep crash error, or am i the only one tytnII and android user and is it just a phoneissue?
i hope some1 could help me since it aint stable enough to use as a mobile phone (if the phone really crashes and i cant control phone inside "sleep" or screen off crash, i am not available for calls or smses..)
logcat logfile is here:
http://jhonnie.nl/screenoff.txt
i'm afraid it sometimes really crashes, since i am not available for phonecalls of sms messages.
maybe it has to do something with button pushes since i dont have much problems when the phone is left to my desk.
get radio version 1.65.x or higher. Get a kernel with different panel settings
radio rom is 1.71.09.01.. and just tried panel 2, panel 1 has "loose pixels" and always had paneltype auto....
any other options?
jhonniedj said:
radio rom is 1.71.09.01.. and just tried panel 2, panel 1 has "loose pixels" and always had paneltype auto....
any other options?
Click to expand...
Click to collapse
Try downgrading your radio to a 1.65.xx.xx brand. I'm running 1.65.21.18, and have had very minor (about 1% of the time) crashes while phone sleeps.
Tried all 3 panels now, without succes, all 4 failed (1,2,3,auto) and still left me with a black screen of death, trying new radio now...
i'll let you guys know,..
using the incubus rs16 super froyo,.. hope this doesnt have any effect the bsod error
jhonniedj said:
Tried all 3 panels now, without succes, all 4 failed (1,2,3,auto) and still left me with a black screen of death, trying new radio now...
i'll let you guys know,..
using the incubus rs16 super froyo,.. hope this doesnt have any effect the bsod error
Click to expand...
Click to collapse
Tried multiple radios, now notsosuper rs18 wont work with radio :|
and tried incubus, wich had data, but was not stable enough to keep the phone from crashing....
trying old myn warm donut, and hoping that will work...
Tried various things, but doenst look like the change of panel helped, and also tries 3-4 versions of radio rom, and tried full install to windows mobile to "clean" anything left.
and when i install clean of Not-So-Super-Froyo, it had the most stability, modpack with essential kernel files, wern't needed and, leaving them untouched had more stabiliy then modded androidinstall.tar file..
Has anyone has more updates or can help me with this, because phone crashes, reboots and is stuck sometimes with screen left off... i don't think i am mobile enough to keep my phone to android, and i'm considering going back to windows mobile..
-Looks like it could have something to do with touching buttons since when i leave it in my jeans, it crashes much more when i leave it on my desk (where it doenst crash mutch or doenst crash at all)
is there anyone that has the same problems or is there some1 who doenst have any problems crashing? (since i would like to have the same configuration)
jhonniedj said:
Tried various things, but doenst look like the change of panel helped, and also tries 3-4 versions of radio rom, and tried full install to windows mobile to "clean" anything left.
and when i install clean of Not-So-Super-Froyo, it had the most stability, modpack with essential kernel files, wern't needed and, leaving them untouched had more stabiliy then modded androidinstall.tar file..
Has anyone has more updates or can help me with this, because phone crashes, reboots and is stuck sometimes with screen left off... i don't think i am mobile enough to keep my phone to android, and i'm considering going back to windows mobile..
-Looks like it could have something to do with touching buttons since when i leave it in my jeans, it crashes much more when i leave it on my desk (where it doenst crash mutch or doenst crash at all)
is there anyone that has the same problems or is there some1 who doenst have any problems crashing? (since i would like to have the same configuration)
Click to expand...
Click to collapse
I assume you are on .32 kernel? All of .32 kernels gave me different troubles. Now .25 branch even though it is quite old is very stable for me and it can run for weeks without any issues.
-Arturo- said:
I assume you are on .32 kernel? All of .32 kernels gave me different troubles. Now .25 branch even though it is quite old is very stable for me and it can run for weeks without any issues.
Click to expand...
Click to collapse
hmmz, that looks like wise advice, thx!
anyone tried the "2011-01-24-gingerbread" yet?
Hello all, First, I searched the forums for my answer with no such luck, that being said if Im repeating a question thats been asked I apologize. I have a problem with keeping android stable. I have flashed with different versions of windows several times all with success. I do however, prefer the android system, I find that it runs much better, faster and has better perks. Everytime I flash following the original how to, I run in to a couple similar problems.
The first is when I hit the power (not hold the power) the back light cuts off and the keyguard enables, the screen goes dark all as it should. Depending on the time ( the longer it is the worse it is) when I hit the power key to revive my phone, I often get a white screen, then it waits , then it goes dim, Sometimes If I hit the power button several times it eventually comes back to the key guard option, but others I have to remove the battery and reboot. This is the major problem, as I cant use my phone when I need it. This problem seems to get worse the farther it gets away from the flash date, e.g..,, after a brand new flash it works pretty good and then it goes downhill from there.
Second, it seems to lock up when I let it charge overnight, not always (but most of the time) I get up, click the power button to revive the phone and I have a white screen before me that is frozen solid. This like the previous problem seems to be linked to the distance from the last flash.
I hope that its something Im doing wrong, as Im currently using wmobile 6.5 and since Ive had a taste of the droid os, my wm phone is just disappointing. And as I was unsuccessful in finding a post that adequately describes my problem ,Im hoping that there is a way around this .
I have tried, Incubus Superfroyo, Wrym warm donut, and Cyanogens build. Im sure Ive tried others, they just escape me, I was re-flashing daily until I went back to windows. I truly hope someone out there has encountered what I have and has a solution. thank you all for what you do, these forums have been extremely valuable and helpful.
Sounds like you have the wrong panel type selected. Is it set to auto? if it is, try setting it to 2 instead. That cleared up the problem for me.
Tried all panels all have the same problem.
Well thanks for all the many replies. I give Ive tried everything on this site and m android is still really glitchy. Guess it will be windows until I get perhaps a phone capable of running android smoothly.
What kind of phone do you have?
Sent from my HTC Vision using XDA App
do you have an SD card you can try to boot from and share your settings?
What we need to know is which kernel you're using, or an image of the kernel you currently have. Also, we need to know which radio version you're using, as this can have detremental effects on stability as well.
Personally, I have been using radio version 1.70.19.09, which seems to be the most stable with kernel .25 IMHO.
I have also "personalized" ThoughtlessKyle's "Fat-Free Froyo", adding/removing apps that I need or don't use respectively (navigation, QQPlayer, Pandora, etc.).
Currently, I think I might be one of the only people not experiencing any issues with this phone running Android 2.2.1. I do get the occasional "hang" (I wait for it to finish what it's doing instead of force close), but that usually has something to do with network coverage or an app requesting something from an unopened port.
Old phone, new OS and runs smooth as could be expected.
Next for me will be the HTC HD2 (if I get one at the right price, the tilt was free)...
I know, I know that MANY PEOPLE THINK OF THE WAKE UP WHITE JIBBERISH SCREEN as NEVER WORKING.
PoXFreak said:
What we need to know is which kernel you're using, or an image of the kernel you currently have. Also, we need to know which radio version you're using, as this can have detremental effects on stability as well.
Personally, I have been using radio version 1.70.19.09, which seems to be the most stable with kernel .25 IMHO.
I have also "personalized" ThoughtlessKyle's "Fat-Free Froyo", adding/removing apps that I need or don't use respectively (navigation, QQPlayer, Pandora, etc.).
Currently, I think I might be one of the only people not experiencing any issues with this phone running Android 2.2.1. I do get the occasional "hang" (I wait for it to finish what it's doing instead of force close), but that usually has something to do with network coverage or an app requesting something from an unopened port.
Old phone, new OS and runs smooth as could be expected.
Next for me will be the HTC HD2 (if I get one at the right price, the tilt was free)...
Click to expand...
Click to collapse
Ill try that combination and post my results. The latest I tried was
Scoot CyanogenMod 6.1.2 RLS6 with 2.6.32 still no joy, white screen crashes and hang ups. and it seems progressively worse the longer the rom is on the phone. To whomever asked what phone I have, its the at&t tilt II
srlebonv said:
Ill try that combination and post my results. The latest I tried was
Scoot CyanogenMod 6.1.2 RLS6 with 2.6.32 still no joy, white screen crashes and hang ups. and it seems progressively worse the longer the rom is on the phone. To whomever asked what phone I have, its the at&t tilt II
Click to expand...
Click to collapse
I can't help you regarding panel selection but, please have Radio ROM version 1.65 or higher. And do give my fresh foryo a go with 2.6.25 kernel (everything is there in the thread on how to use it with 2.6.25 kernel).
the WHITE GLITCHY SCREEN IS THE PROBLEM WITH ANDROID DRIVERS. Install with Data on SD Card often causes lockups / force closes.
I am using panel type 1 and white glitchy screen stays for like half of a second and next moment I get a nice clean keylock screen. I don't know but its like 20th time I am explaining the problem related to LCD
Change Panel Type, Get a compatible Radio version (1.65.x or HIGHER)
You say that often install with data on the sd card causes lock ups and freezes. Can you explain further what you mean ?
dark_prince said:
I can't help you regarding panel selection but, please have Radio ROM version 1.65 or higher. And do give my fresh foryo a go with 2.6.25 kernel (everything is there in the thread on how to use it with 2.6.25 kernel).
the WHITE GLITCHY SCREEN IS THE PROBLEM WITH ANDROID DRIVERS. Install with Data on SD Card often causes lockups / force closes.
I am using panel type 1 and white glitchy screen stays for like half of a second and next moment I get a nice clean keylock screen. I don't know but its like 20th time I am explaining the problem related to LCD
Change Panel Type, Get a compatible Radio version (1.65.x or HIGHER)
Click to expand...
Click to collapse
Ok, so I installed your version of froyo, the accompanying 2.6.25, the radio that you use. For the most part the hanging up is fixed. Now the second problem is still in place. Sometimes when Its been in hibernation(or whatever you would call when you hit the power button once ) when I attempt to refresh my phone (hitting the power button once) nothing happens, the green light is still blinking at the top but the screen stays blank, normally have to remove the battery and restart to get back to using the phone. Is this a sleep setting? or is this something Ive done wrong during the installation.
This problem only really happens after my phone has been on for days at a time. I have had this problem on the latest stable and latest nightly for CM7 (each one cleanly installed after a total wipe).
What happens is that most screens are replaced with entirely black ones. The most consistent example of this is the settings screen. The first Settings screen (which shows Display, Sound, etc) loads correctly. If I click on any of those, I just get a black screen. This will happen in other applications too, like Baconreader or Browser. Also, another connected issue is that the lockscreen won't animate once this problem starts. I can drag it down to unlock, but the rotary wheel won't move at all. If I drag to the right to load my custom app, the lockscreen won't go away and it will force my to pull the battery.
Has anyone else run into this problem? I'd just like to know I'm not alone. I'm not really expecting a bugfix, especially when I'm not even posting a Logcat.
Did you fix permissions?
midget tossing is habit...2010 midwest regional champion... hw 001
Saturn2K said:
This problem only really happens after my phone has been on for days at a time. I have had this problem on the latest stable and latest nightly for CM7 (each one cleanly installed after a total wipe).
What happens is that most screens are replaced with entirely black ones. The most consistent example of this is the settings screen. The first Settings screen (which shows Display, Sound, etc) loads correctly. If I click on any of those, I just get a black screen. This will happen in other applications too, like Baconreader or Browser. Also, another connected issue is that the lockscreen won't animate once this problem starts. I can drag it down to unlock, but the rotary wheel won't move at all. If I drag to the right to load my custom app, the lockscreen won't go away and it will force my to pull the battery.
Has anyone else run into this problem? I'd just like to know I'm not alone. I'm not really expecting a bugfix, especially when I'm not even posting a Logcat.
Click to expand...
Click to collapse
I suffered this same thing today. Thankfully a full restart fixed out, but I would love to learn a real solution.
bootny said:
Did you fix permissions?
midget tossing is habit...2010 midwest regional champion... hw 001
Click to expand...
Click to collapse
Next time it happens I will, I'm just afraid it will break Facebook/SMS integration like I've had happen before.
It's just so weird since it breaks everything. The lockscreen, the options, Pandora's station list, the browser, and it goes on and on. It's like there's some sort of display mode that gets screwed up.
dom085 said:
I suffered this same thing today. Thankfully a full restart fixed out, but I would love to learn a real solution.
Click to expand...
Click to collapse
What version are you using. I'm going to try to install nightly 77 today after a fresh wipe.
I was seeing the same thing. Now I'm trying to figure out why my data speeds are so painfully slow on CM7 so I can't offer a fix. Flashing back to Warm to troubleshoot 3G.
I get these issues all the time no matter what kernel or nightly I'm running. It has forced me back to sense roms lol
Same problem here. I updated stable mod from stable mod. Reinstalled. Going on 4 days, no issues so far.
Sent from my PC36100 using XDA App
I have the same exact issue. This never happens on a sense rom. I did some tweaks to my system over the past week and I haven't had to reboot since this past Saturday or Sunday. I thought I had fixed it!
Then...
My phone started doing it this morning after I turned on 4G at work, literally as I was writing this post it started doing it. I then turned off 4G.. and it instantly went away. Turning back on 4G and it isnt doing it right now. Now my phone is doing something weird with go sms pro... when I get a text and I respond via the pop up message.. once my text moves to a second line I dont see what I am typing anymore... and now it has progressed to where the pop up box isnt refreshing after I send a message (this is all happening while I am typing this post). Now the phone has become laggy and somewhat unstable... rebooted! All is well. So I went roughly 4-5 days without a reboot... where as before I had to reboot at least once a day.
Thats about the best I can get with these settings:
CM7 7.0.3.1
Savaged Zen 2.6.38.5 CFS > Using SavagedZen Governor, min 384 max 998
Displaying some animations (read somewhere that is a "fix".. or helping extend the time it takes for the Black screen of death to appear).
This is after several full wipes, several when I was running Amon RA recovery 1.8 then updated to the latest and did it two more times. After upgrading Amon and wiping I did not use any backups and started completely from scratch.
So I am not sure what else to do. Some people are getting this, some are not.
Hi everyone!
So far for the past 2 years I have been running various builds of Android on various Kaisers (yes, I have 4 of them now).
For the past 6 months or so I have stuck with the 2.2.2 build from SourceForge (system_froyo_us_odex) and never had any issues... until now.
All of a sudden, for the past 2 weeks I have been getting that dreadful "sleep of death" problem, sometimes upwards of ten times a day!
Current installation is as follows:
Scoot cache kernel, 15mb cache, 500mhz, ext4, 1500mah battery.
Froyo 2.2.2 US Odexed from SF with all the stock apps, extras listed below
ADW EX Launcher ver. 1.2.2
Beautiful Widgets ver 3.3.4 with the animation package (Super clock 4x2)
Rogue tools
Root explorer
Scanner radio (barely use due to constant data usage)
Pandora (again, data usage can be high so barely used)
Facebook ver 1.8.2 or current build
Foursquare ver 2012.02.27
I have looked at dmesg on the SD and compared to one from a backup SD but cannot find anything extraordinary, nor is there anything wierd in /system/sysinit.rc. Performed a complete wipe and reinstall from stock with all the same apk's and even changed to the brand new (turned on once) Kaiser after unlock/SPL install.
If anyone sees anything out of line (except the BW 3.3.4, I like my flip clock), please do let me know. If there is any files you may need from either the phone or SD card I can paste them accordingly.
Okay, made some line entries in build.prop via root explorer's text editor and added the line "ro.ril.disable.power.collapse" with the argument set to 1, which should have turned off any sleep mode, and also added the line "pm.sleep_mode" with the argument set to 1. This after doing a search on google for build.prop tweaks (there's a bunch).
Battery life has suffered a little but it seems to have helped somewhat. It will still hard lock in sleep mode and be unresponsive until a stylus reset or battery pull.
I got an equal issue after inserting pm.sleep_mode= in my startup.txt for haret. Sometimes the 'sleep of death' and sometimes never ending boot circles. The only argument working is the default value '1'
What I ended up doing was to go back to scratch. This happened on 2 separate phones by the way so the spare was the guinea pig.
I started with the kernel first, rebuilt it and reinstalled it, then installed a clean froyo build, which would still hard-lock.
I went back even further and reflashed the SPL, then rebuilt the kernel as before and another new froyo install, which seemed to work. I then copied what I did on the spare and refreshed the newer phone and synced my accounts to it, then reinstalled all of the apps, one at a time, to make sure there wasn't one causing this.
So far so good, no SOD or hard locks.
Went in and re-edited the build.prop to add some performance mods (dalvik.vm.startheapsize=4m, dalvik.vm.heapsize=32m, etc)... seems to be better, smoother and doesn't FC apps as much.
We shall see what happens...
Well, since you can't find this post on the front page, I'll have to put up a new post about my build.prop changes that really help with speeds and FCs'.
Look for it on the front page...