I know the first one is probably nitpicky. I did just finally get CM6 to the point where it's buttery smooth, faster than EVERYTHING else out there, and works 99% how I want it to. A few things that bother me yet, and I'm hoping someone can help me out. I have read through all (yes, all 700 odd pages) of the CM6 thread here, as well as checked over the cm wiki, the cm snap thread, and even delved into the source for one thing (battery related, different thread). What's left is low hanging fruit that hopefully is just something that's common knowledge that I missed.
Running CM6 final, with GAPPS from 8/17, snap 8.2-850 on a nova 002
Jittery fade on screen off:
This was always described as a "smooth fade" when the screen turned off by my friends. It's much smoother on theirs, but when I turn my screen off, it's like it's only hitting 3 brightness levels before it goes off, and it takes FOREVER to finish the process (1+ seconds) after I've hit the power button. I have disabled setcpu profiles in an attempt to fix, as I've got a screen off profile. No dice.
Settings->Sound crashes every time:
Pretty much just as described. I simply can't enter this part of the settings application. That means no ringtone changes, I've got to use a different app for volume adjustment, etc. etc. Basically, it's a pain. Attached is a logcat excerpt from when I ran logcat via ADB while trying to diagnose myself.
The first question to ask is..Does it do that without the snap kernel?
im running snap kernal and have neither of those issues.
Yes, this happens using snap or stock cm6 kernel. I did want to post that i was using snap to give a clear picture of my current phone conditions though.
- From my EVO
Related
I'm hoping you Android experts can help me. I need LogCat interpretation. Since updating to 2.2 (not rooted), I've seen my phone go to a white HTC screen followed by a re-start of the home screen. It ends up being on the home screen page I was at, not the "center" one.
This has been happening several times a day, usually when unlocking the phone or exiting from an app. It seems like it's related to receiving some sort of alert while locked or using an app.
I have a LogCat excerpt which I snagged while taking some screen shots with ddms. I was snapping screens from Dolphin. After I was done, I used Dolphin's menu Exit button to stop Dolphin. I got the white HTC screen then the home screen restart. I've attached the relevant LogCat data. Can someone look at this and tell what happened and why the home screen restarted? I am looking for real concrete info. There is a ton of Old Wives' Tales going around about this and I'm not interested that sort of nonsense
PS: I tried to post some context in the form of CODE blocks from LogCat but I got refused because this forum prohibits me from posting "outside links". There is no hyperlinking info in the LogCat info, but...
I am also getting the same issues. Using virtuous 2.5 and BFS#1. If this doesn't get better, I am just going to try a different flash and see how it goes.
Sigh... I was hoping one of the Android jocks here would be able to tell from that LogCat. I see this mentioned in other threads on other forums. But all I have found amounts to old wives' tales.
Sorry I don't know how read those but if your not rooted I don't think it matters anyway because you cannot access those files. I would root the phone Unrevoked forever with s-off and then download rom manager if you have never flashed roms and stuff. from rom manager install your custom recovery and do a nandroid backup. So from this point basically you can do anything short of changing the radio without worries. because if you mess it up just boot into recovery and restore from the nandroid backup. you will be no worse off than you are now. you can download stock 2.2 or even try virtuous 2.6. its awesome and super stable. in fact it runs better than stock did. Anyway good luck all the info you need is on the forum. if you have a question i will try to help but im not a computer programmer but i have been playing with android for about a year.
Jonathan --
I finally went back and looked at this thread. I did root the phone with the Reflash from the #unrevokedtest IRC channel. In fact it went so smoothly, I "gave back" by spending several hours a night for 5 nights helping and encouraging others on IRC. Then I wrote up an article based on the things people had trouble with (see http://bit.ly/aBez98). One of the unrEVOked guys picked it up, made some suggestions, I edited it, and now it's linked in the /topic of the channel. Your suggestion pushed me over the edge.
I am using Auto Memory Manager, which allows you to tune the way the OS prunes tasks. With it set to "Mild" my Sense restarts are a thing of the past.
I'm pretty sure that somehow the HTC Sense "app" is actually getting pruned by the OS, causing it to need to start from scratch when exiting from whatever task needed that extra bit or memory to run. It's not a bug, it's a feature!!!!
Thanks..I'm gonna try this.
I don't like spending hours tweaking task killers and the like.. but if I'm ever showing my phone to someone, I don't want the phone to appear buggy.
On the same token, I'd like to know when this feature is updated to prevent the symptom.. so I can dump the memory manager.
I tested the solution of using Auto Memory Manager configured to Mild for a couple weeks... I don't feel there was any improvement. Anyone else?
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.
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?
Kernel - http://forum.xda-developers.com/showthread.php?t=1414876
ROM - http://rootzwiki.com/topic/11472-rom-android-revolution-hd
Loaded them up perfectly clean, just like the directions explained, no problems during installation.
Now - this was my fault, I should have tested by restarting the phone with both loaded prior to installing an app, but I just had to get the EX Go Launcher :-( Well, after installing that is when I first attempted the shutdown since loading the kernel. That's when it just sat at "shutting down" and never shutdown. left it for 5 minutes, nadda. It will turn the radio off, and you can see any activity in the background, but it will sit there at that shutting down screen pretty much indefinitely, until you pull the battery. You can still hit and hold the power button, which gives you another shut down prompt that overlaps the first one. You hit the shut down, just does the same thing and sits there.
So just a report for you folks. I would be reporting this on the kernels respective thread, but I don't have enough posts and it directed me to post here, but that kernal and rom seemed like the perfect duo. I didn't have patience to reload the rom and kernel since then, so I can't confirm if it works with the go launcher. Or maybe it was just a fluke and it will work with another reload. I'll continue to keep this thread updated, I'll be doing it again within the next couple weeks.
UPDATE: Not sure why I didn't try this before, guess it sounded to simple to make sense, but I just uninstalled the Go Launcher from the OS and all is top notch. Phone shuts down without an issue. So it's so the combination of the two, or one of the two thereof the not cooperating with go launcher.
Otherwise, loving the combo. So far better battery life and smoother operations. Still trying to figure out how to adjust the CPU performance, or set it to auto throttle. But, all with time.
EDIT: Mods please feel free to throw [REVIEW] in my thread title, missed that part