Sorry I have to post here, I am a long time viewer but first time Poster
Okay I am having a very weird thing happen… upgraded from SC 2.6 to SC 2.9 (did all the steps Wiped cash, Wiped Dalvak, etc.) phone works fine but periodically (maybe 30 minutes maybe 2 hrs) l I get a black screen and nothing can wake it until I do a hard reset.
This only happens when not connected to power.
I have reinstalled via CWM (Red) and Odin, I have replaced the Modem.bin and applied 2.9.1
My feeling is this may be related to a application as my last ODIN install worked for over 12 hours until I updated applications, but the applications I am running are not that big of a deal
Dolphin HD, Facebook, Youmail, Alarm Clock Plus, SMS Backup+, Titanium Backup, Rom Manager, YouTube, Flash 10.1, Google Voice, Google Maps, Barcode Scanner, Poynt & Widgetoid 2.x
I ran the same Apps on SC 2.6, Balckhole 4 and JT's Vanilla Froyo without issue, I have tried the Voodoo and Non Voodoo installs to no avail, anyone seen anything similar or even better have a fix?
Sounds like the sleep of death issue to me. So far there isn't a fix for it.
Deff the sleep of death. . And the really bad part is.. You can't get calls in that state, and of you receive a text in that state it will go to the twilight zone never to be seen again.
Sent from my Rocking dj05, themed superdark w/o swype mod, voodoo 5, with custom boot and shutdown.. With premium xda app.
My problem is getting rid of it... I have now flashed 3 different versions of of SC on it SC 2.9, 2.8 and 2.3 and it still exists ..
I may try putting a whole new ROM see if that has any effect!
****
Ok now I know the problem there is a good thread here, thanks for the guidance http://forum.xda-developers.com/showthread.php?t=960080&highlight=sleep+death
I found that my sleep of death only happens when I use the clock app thing. The app semi sleeps the phone then when I touch the screen it doesn't come out of it properly so the next time I turn it off it won't wake. Now I just don't use that stock alarm click thing.
Sent from my SCH-I500 using XDA App
Phasze said:
I found that my sleep of death only happens when I use the clock app thing. The app semi sleeps the phone then when I touch the screen it doesn't come out of it properly so the next time I turn it off it won't wake. Now I just don't use that stock alarm click thing.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Had a feeling it revolved around clocks.. .. people know beautiful widgets cause sleep of death.. And people report that their clicks lag in froyo.. Froyo has some serious issues.
Sent from my Rocking dj05, themed superdark w/o swype mod, voodoo 5, with custom boot and shutdown.. With premium xda app.
Related
Had anyone had any problems playing pandora or slacker radio with the new nero 5?
they both worked fine for me with bionix fusion but now just cut out all the time.
I was thinking maybe it has something to do with the modem.
let me know if you've had the same problem and gotten it fixed.
Thanks.
Sent from Samsung Vibrant rooted with Nero V5
Pandora works fine for me with Nero 5
Works great for me as well. I use it in car in landscape mode. I had to install adfree because pandora ads are in the weirdest place in landscape. I also think it sounds a tad better in nero5
Are you overclocked? I once had that problem with a ROM. Had something to do with minimum CPU processor speed. I had set it too low on SetCPu and had to bump it to 400 or something like that....
No, I'm not overclocked.
Could I have messed up something when I odined back to stock?
Or maybe it's my 3g, I'm not sure. But it does suck.
Should I do the 1.4 overclock kernel?
Thanks for helping.
Sent from Samsung Vibrant rooted with Nero V5
Have you tried to reboot? The other day I did have a problem connecting for some reason. It would just show the splash screen. After I rebooted it worked, not sure what happened as I could still do calls and texts.
I had the same problem w nero4 but I flashed 5 before I was able to figure out the problem. So far no problems with 5
Sent from my SGH-T959 using XDA App
I've tried rebooting and it works again for a little while but then it cuts out again.
It's weird it cuts out and then some times it just starts back up when ever it wants. And it seems like it just sucks up all my ram.
Sent from Samsung Vibrant rooted with Nero V5
Might want to try fixing permissions and see what happens. Do you have SetCpu installed? If so, what settings are your CPU speeds set at?
I don't have setcpu right now, I'm not over clocked right now. As for the permissions how would I fix thoses?
Sent from Samsung Vibrant rooted with Nero V5
You can fix the permissions using rom manager. Just open rom manager and in the utilities sections it says fix permissions, choose that and then reboot when it is finished. I have not had any problems with pandora. Haven't used slacker though.
Sent from my SGH-T959 using XDA App
It could be the outageously low-memory kernel that's used at the moment by Nero, Axura and others.
There's only 304 MB of RAM available for the user, compared to the usual 320 MB from the JI6 kernel or even 340 MB from the custom JI6 with Voodoo kernels.
In Nero v5 I used Autokiller Memory Manager to change the system's auto process killing parameters, and I saw that by default it's set to kill Provider processes (like Pandora's background playback) until 90 MB of RAM is available. And since it's so easy to reach less than 70 MB free with this bloated Samsung bull **** (even though the bloatware has been mostly removed), your Pandora is ended by the system in order to keep enough memory available.
Another reason to get CyanogenMod working on the Vibrant: I tried CyanogenMod 6.1, an absolutely pure Android build... 100% AOSP, 0% Sam**** (except for kernel), and I have much more memory available. Try it out.
Sent from my SGH-T959 using XDA App
I'll try the auto memory killer. I tried fixing the permissions with no luck and I installed and reinstalled pandora with no luck.
Sent from Samsung Vibrant rooted with Nero V5
So far so good, using auto memory killer.
Sent from Samsung Vibrant rooted with Nero V5
Played pandora for 4 hours straight with no problems, thanks alot for the help guys.
Sent from Samsung Vibrant rooted with Nero V5
Why is it that I always have to reset "never kill app" in auto memory kill for pandora? Even if I don't reboot my phone it changes on its own.
Sent from Samsung Vibrant rooted with Nero V5
Hey Guys,
Having an issue that I just can't seem to figure out. First, my phone specs:
Running EB01 Modem & JT's EB01 Voodoo Kernel w/SuperClean 2.2 Voodoo, ASOP Lock, Power & Battery Mod (via Domush walkthrough).
Now the problem: my phone just shuts off completely when it feels like it and the only way to get it back on is to do a battery pull. Searched the forums and throught it might be the proximity sensor, but flashed it back to stock and it was fine. It seems to happen randomly. It's not the battery because each time i turn it back on it have plenty of battery life. I've tried freezing all my apps and it still does it as well.
Is there someting i'm missing? Anyone else have an idea?
Thank you in advance
My first suggestion is backup your apps and do a wipe wipe wipe. See if that corrects problem.
Let us know
sent from my vanilla voodoo fascinate
I had that happen a couple times as well with SC 2.1. I only ran it for a couple days before SC 2.2 came out. After flashing 2.2 over 2.1, and wiping the cache a couple times, I haven't had it happen again. Then again I only upgraded yesterday, so it may yet happen again. Time will tell.
Posted from my EB01 SuperClean Fascinate with Voodoo
So far so good....I wiped x3 everything (cache, davik, everything) and it seems to have worked. Thank guys. I'll let you know if it acts up again.
Come to find out it was a rom prob, fixed in the forums, called the sleep of death.
Sent from my SCH-I500 using XDA App
FWIW, I did not have the problem with 2.2, and now have upgraded to SC 2.4, and the issue still has not returned. It does seem like I have to hit the power button twice to wake it up once in a while, but it never fails to wake up.
Posted from my EB01 SuperClean Fascinate with Voodoo
It seems to have only happen when you do the steps in a certain order. It's all fixed with the patch.
Actually, it's NOT been fixed with the patch. If you read the thread, the people that thought it worked had it come back after a few hours of use. The only way I've been able to "fix" it thus far is to go back to the stock ebo1 rom. FWIW, the problem for me seems to resurface after I access any media. The first time was after I listened to music through Poweramp and the latest was after watching a video in media hub.
JJRocker said:
Actually, it's NOT been fixed with the patch. If you read the thread, the people that thought it worked had it come back after a few hours of use. The only way I've been able to "fix" it thus far is to go back to the stock ebo1 rom. FWIW, the problem for me seems to resurface after I access any media. The first time was after I listened to music through Poweramp and the latest was after watching a video in media hub.
Click to expand...
Click to collapse
Hmm, I'll have to check it out....I went through my photos and it worked fine after that. I use Audiogalaxy so I don't have music on my phone. I'll go run a video and see if that triggers it. Good looking out JJRocker
This so far has been an issue that's really hard to find info for and it's driving me nuts...lol. So yeah, even though I'm far from being an expert, I'm trying my best to figure out what's causing it so that I can work around it or better yet, help the devs out since they are the real experts here. Adrynalyne put a test patch up and asked people to report on it, so it would probably help a lot if everyone having the problem would post their results in this thread. He's the guy that's probably most likely to figure this out. Also, that link has the patch if you want to give it a shot.
One thing I should probably mention is that at least in my case, once the SOD surfaces, it happens about every 4th to 5th wakeup until I reflash the rom or go to another one. So if you've experienced it already, there's a good chance you won't be able to cure it without a reflash.
Ive noticed there is a certain population of folks who have it, and a larger population of those who do not.
I've been researching for hours on end, with no clear common resolution.
For some, not using Titanium to restore apps fixes it.
For some, my test patch works.
For some, a double reboot fixes it.
I had it happen once, ever, and it was on stock eb01. It never happened again. I myself have noticed increased instability on eb01 using maps and gps, however. A couple days ago, launching maps, and turning on the gps afterwards hard locked my device.
@adrynalyne
Exactly.
It seems that mine is fixed with the patch in both of your SuperClean 2.3 & 2.4, I've tried different media and it seems fixed. Only time will tell tho.
And thank you for all that you do with this phone. It had such great potenital and with you and folks like jt, it's making this phone amazing!
It's strange....I had it happen once this morning and now I can't replicate it. I have used Titanium to restore apps but I only restore one app, AndroidPit App Center. I need it to download ADW EX and Beautiful Widgets since they take PayPal and my debit card doesn't do foreign currency.
Anyway, someone at Android Central suggested avoiding ADW because people were reporting issues with the SOD and that launcher. So, I'm gonna run LP+ for a while and see how that works out.
I have been using ADW EX and no real problems...
...but I didn't think about it, I did clear out me Titanium Backup and just reDownloaded stuff this time. Maybe the backups are the culprit?
Well, right now I'm starting over on SC 2.4 and trying all the remedies I've seen posted thus far. I wiped data and cache, flashing SC 2.4. I'm going to skip the backup assistant since it might try to restore apps that were restored by Titanium. I'll run LP+ and flash a theme (VA green is my current fave...love the BA). Gonna restore my apps manually from the market and I'll even double reboot when I'm all done...lol. Anyway, wish me luck...the real test will be tomorrow at work. I use HandBase to keep track of things so I put my phone in and out of sleep a lot during the day.
And also, many thanks to Adrynalyne and all the other great devs here. The work put into this stuff is much appreciated. I wouldn't put this much effort into getting this working if SC wasn't such an amazing ROM.
JJRocker said:
Well, right now I'm starting over on SC 2.4 and trying all the remedies I've seen posted thus far. I wiped data and cache, flashing SC 2.4. I'm going to skip the backup assistant since it might try to restore apps that were restored by Titanium. I'll run LP+ and flash a theme (VA green is my current fave...love the BA). Gonna restore my apps manually from the market and I'll even double reboot when I'm all done...lol. Anyway, wish me luck...the real test will be tomorrow at work. I use HandBase to keep track of things so I put my phone in and out of sleep a lot during the day.
Click to expand...
Click to collapse
When I redid it again my aps were automatically restoring themselves. So to save you some sanity, make sure you go into privacy and turn off "Backup my settings" and "Restore my settings" as well. It may be dimmed out, but it will sutomatically restore them as well. It's doesn't really do much from what I can tell (I still have to manually add passwords to wifis, which it says it backs up)
Ya know, maybe that's the cuplrit of this whole shabang
Ok, so I had the SOD on LP+ too. Out of curiosity, is anyone with this problem using Switchpro widget or another power control widget that changes brightness? The one thing that seems to always precede the SOD for me has been installing and putting this widget on my desktop. Also, one time I did have it before I installed the widget and checked my screen timeout settings...there was nothing checked which is the same as having the screen never turn off. Apparently, backup assistant restored the setting automatically from a previous flash. Also, I think Super Clean has a power control widget on one of the homescreens by default if I remember correctly. Everything was running great, couldn't get it to SOD, so I started installing some of my apps and put the switchpro widget on my main homescreen, and got SOD on the very next wakeup.
I believe I may have found my culprit!! But before I say, let me recap:
I backed up using TiB. Flashed everything back to DI01 and got the OTA update. Restarted, then flashed to DL09. Reboot, Flashed to Deoxed EB01. I also kept the origional kernel, didn't meess with it because I believed that it was the cuplrit, I am assuming I'm wrong. Everything was good. Slowly started adding programs back seeing which one will kill my phone. I finally found it......it was YouMail.
If you are using this product, you can have it on to your system and it will work. But as soon as it receives its notification of a New Voice Mail notification from their servers. It locks up. Hopfully uninstallation and a reboot will take it away, but only time will tell. I'll report back in.
I had been on Bionix for quite a while when this first happened.
I, was playing a youtube video it said "video playback failed. Touch to retry." It never worked so I restarted the phone, and then it finally worked..... for a while.
I started noticing that when this happened (inevitably after a certain amount of uptime) my videos stores locally would stop playing as well, and so would my mp3's. A reboot would always fix it, but it certainly is annoying).
Fast forward to today, I'm running Trigger, and I'm still getting the same problem. I did fix permissions, I wiped the youtube cache, I wiped the dalvik cache, I did factory reset, but I cannot get media to work consistently.
Does anyone have an idea on how to fix this?
I should probably disclose that I use titanium backup to restore missing apps with data only, but never any system apps.
Any help would be greatly appreciated, as this issue has me stumped!
(ps.: playback of videos directly within youtube.com also does not work either, and not because of the (this video is not available on mobile error either, but due to this all encompassing issue, I think).
Sent from my SGH-T959 using XDA Premium App
This happens to me the other day and all I did was a reboot and it started working again.
Sent from my SGH-T959 using Tapatalk
I know what you're saying, it does indeed work after a reboot, but after a certain amount of time, it stops working again, and once again it needs to reboot.
It is kind of annoying, and I wish I could figure it out once and for all.
Hopeless bump.
Can anyone shed some light on this issue? Playback keeps getting broken.
I have this issues aswell. Is there for fix for Bionix V 1.3.1 or any TW roms. My youtube app is broken and its driving me crazy!
if you have the official twitter client installed, then get rid of it. I had the same problem, and read another post about this. The problem never happened again for me after I uninstalled the twitter client.
kcshmo said:
if you have the official twitter client installed, then get rid of it. I had the same problem, and read another post about this. The problem never happened again for me after I uninstalled the twitter client.
Click to expand...
Click to collapse
How do you know for sure that this is the issue. I will try it anyways since nothing else seems to fix this annoying issue.
So far this is working. Been 3 hours without videos on youtube not playing. Usually I have to reboot the phone every 30mins for youtube to work again. Will test this theory....
Why would twitter not fix this flaw in the apps programming?
Sent from my SGH-T959 using XDA App
How can I be sure? I don't. Like I said in the earlier post, I am just relaying the info from another post I read. It also fixed it for me. I don't need rebooting my phone anymore because media doesn't play.
That's why I just stopped flashing up to bionix 1.3. Tried 1.3.1 with some flaws noticed. Went back to 1.3 for 2 months already no hiccups or whatsoever. Running on kb5modem, overstock 2.4.1 kernel, splash of colors 4.1. Some minor system apps were pushed. Modded boot animations and shutdown too. Quads at 1900, 2003 at highest. Gps at 5secs lock with 8meters accuracy. Snappy fast blazing bionix.
Sent from my SGH-T959 using XDA Premium App
Yesterday I was driving to work. My Fascinate was working flawlessly since I got it the day it came out. I have leaked DL30, Midnight v1.0 theme and DJ05 kernel which I have been using with no changes for about 2 months.
While I was driving, my phone reset, the default desktop screen for the theme came up. A few of my desktop widgets are gone.
Also I have these strange things:
1. My settings button on the app drawer does not open the phone settings. I highlights blue but does not open.
2. When I try to create a shortcut on my desktop it force closes my launcher (ADW, TW and LP).
3. My blue tooth headset is no longer paired (and I can not pair it since I can not get into settings).
Now I have no way to access my phone settings. I did not think that they phone would do the Froyo update since i was rooted with the leaked version already on it, but I can not check to see what is installed since I can't get into the settings.
I have tried many battery pulls and I installed AVG antivirus and that didn't find anything.
Like I said, this is kind of weird since everything was running fine as is for the last 2 months.
Any ideas or suggestions before I do a full Odin wipe and re-install?
Thanks
Why not just back up apps with TB and install ED01 or EB01 (which ever your choice).
Kaze105 said:
Why not just back up apps with TB and install ED01 or EB01 (which ever your choice).
Click to expand...
Click to collapse
That is most likely what I am going to do.
PLEASE NOTE: This patch addresses application force closes on newer google maps applications (5.5-5.7) running on gingerbread-based ROMs for the ERIS. This does not address reboots/restarts (see http://forum.xda-developers.com/showthread.php?t=1157099 for progress on this other problem)
After extensive testing on CondemnedCM7 V15, I believe that the Navigation force closes many of us experience on the newest maps version is fixable (at least on Condemned's ROM; GSB users report that problems still remain) by rolling back google maps framework files to a version used for Android 2.2 ROMS. I have been testing since last week and have not had a single navigation force close. My longest test was 1 hour 10 mins with multiple reroutes and no force close. One known issue, Map application (not navigation) will unexpectedly close (that is, will not offer a force close but will shut down) randomly while using the search box. I have not been able to consistently reproduce this
I am attaching two zip files flashable from AmonRa Recovery if you would like to try the fix. The first replaces the current maps framework with the froyo framework. The second rolls back the change to the latest gingerbread framework.
If you are using maps 5.2 which CS included in the system apps for v15 and are happy with the result, then you do not need to flash this file. If you would like to use the newest maps app (5.7), you may wish to try this.
In theory, this fix would work on an AOSP or Cyanogen gingerbread ROM, so if folks on other devices are having similar problems, they may want to try.
Good luck everyone!
NOTE: this is repeated from CondemnedSoul's CM7 thread. The attachments can be found there: http://forum.xda-developers.com/showpost.php?p=15978440&postcount=535
Thanks for everything your doing on this issue.
I upgraded to 5.7 and flashed the patch. Ran Nav for 30 minutes and all was fine. Not sure when I can test longer but if I do I'll let you know the results.
Only got to run Nav for another 30 minutes today but she worked flawlessly again.
Glad its working for someone other than me!
Sent from my ERIS using XDA App
I can't believe no one else is trying it and letting you know their results.
I guess were the only ones who care, our at least, the only ones who get lost
Sent from my ERIS using XDA App
klobkelosh said:
I guess were the only ones who care, our at least, the only ones who get lost
Sent from my ERIS using XDA App
Click to expand...
Click to collapse
Or the only ones that use that ROM lol
Lol!
Sent from my ERIS using XDA App
Maps 5.8 is out. I'll be testing to see if 1) the navigation patch is still needed, and 2) if it still works. Stay tuned...
Sent from my ERIS using XDA App
klobkelosh said:
Maps 5.8 is out. I'll be testing to see if 1) the navigation patch is still needed, and 2) if it still works. Stay tuned...
Sent from my ERIS using XDA App
Click to expand...
Click to collapse
Have to go get it myself.
klob, will upgrading to 5.8 overwrite the fix files, or should I have run the unfix before upgrading?
Either way all I did was upgrade and so far Nav has been running for 40 minutes. Not driving anywhere, just have Nav running while I'm in the house.
Upgrading maps app will not affect the fix, so if you want to find out if it works with stock gapps, you'll need to flash the unfix. Also, bftb0 on the gsb thread has demonstrated that desktop navigation is not a good test for force closes. I'd get it on the road to be sure.
My commute starts in about 15 minutes. I'll report back soon...
Sent from my ERIS using XDA App
Update: it seems google had fixed whatever was misbehaving in maps 5.7. No force closes on my commute.
Sent from my ERIS using XDA App
I got to use Google Nav today and it wasn't the best. After 5 minutes it went shut off, just shut off and phone went to sleep. Opened Nav back up and after 14 minutes the map locked, never updated/moved, tough screen commands still came up along with menu but nothing worked. Rebooted and applied the fix that klobkelosh posted earlier and it didn't change anything, screen keeps freezing. This is all after full wipe and flashing latest CS v16 vanilla with 5.8 Maps.
Sir_Eagle said:
I got to use Google Nav today and it wasn't the best. After 5 minutes it went shut off, just shut off and phone went to sleep. Opened Nav back up and after 14 minutes the map locked, never updated/moved, tough screen commands still came up along with menu but nothing worked. Rebooted and applied the fix that klobkelosh posted earlier and it didn't change anything, screen keeps freezing. This is all after full wipe and flashing latest CS v16 vanilla with 5.8 Maps.
Click to expand...
Click to collapse
Odd. I just full wipe installed ccm16sth with 5.8 maps and navigation worked fine. One thing I did was disable text to speech, maybe that's the culprit? You can disable by renaming system/lib/libtts.so.
Sent from my ERIS using XDA App
klobkelosh said:
You can disable by renaming system/lib/libtts.so.
Click to expand...
Click to collapse
I don't have that file, got libttspico.so and libttssynthproxy.so.
Sorry, its the libttspico.so file
Sent from my ERIS using XDA App
GPS files the culprit?
Not sure if this will help but today running GSB 3.8 ODEX with Maps 5.8 (no framework mods.) my phone completely restarted in the middle of a walk. The thing is that I was not using Maps nor Nav. I WAS using TrackerBooster, an app that uses GPS to measure my walking distances. So maybe this is more related to GPS files than it is to Maps or Nav. As you can tell I am not a developer, so this may be all one and the same. Just thought posting it might lend a clue. Thanks for all you guys are doing to figure this out!
aceof89 said:
Not sure if this will help but today running GSB 3.8 ODEX with Maps 5.8 (no framework mods.) my phone completely restarted in the middle of a walk. The thing is that I was not using Maps nor Nav. I WAS using TrackerBooster, an app that uses GPS to measure my walking distances. So maybe this is more related to GPS files than it is to Maps or Nav. As you can tell I am not a developer, so this may be all one and the same. Just thought posting it might lend a clue. Thanks for all you guys are doing to figure this out!
Click to expand...
Click to collapse
I tried Telenav with the same force close issue too
Sir_Eagle said:
Only got to run Nav for another 30 minutes today but she worked flawlessly again.
Click to expand...
Click to collapse
Something I noticed... making me wonder if it's memory allocation issue... after a reboot, going right into Nav, it still force closes but not until 30+ minutes,
If I haven't rebooted in a while and have been running other apps like, gmail, exchange, facebook, and the going driving with NAV the reboot happens right away