Related
I'm running Fresh 2.1.2 and I've been having a ton of issues with lag that I never had on Fresh 2.0d. Are people having lag issues on the official 2.1 release too? I've tried to check and see what's running when the lag is happening, and it seems consistent with an app updating itself. I'll go to the list and see that mail has 5% or twitter (not peep) is updating and at 10% or something, but nothing is ever over that and it's always just one or two apps like that and the phone is unusable until they are done.
Now I'm noticing that if my phone is just sitting on the desk and someone calls, it takes a good 5 seconds for the phone to display the screen that tells me who it is. It vibrates, waits a couple seconds, then the default ring tone starts to play, then a couple seconds later the display comes up that says who is calling.
It generally is running like ass. It did not do this before on Fresh 2.0d. I was running apps2sd on that as well as on here. It seems that the only difference between fresh 2.0d and 2.1.2 is the fact that it's now the official released rom. Are people with the official rom having the same issues??? If they are, I'm going back to 2.0d. It ran completely fine. This is starting to get on my nerves and is not the experience I want....
CodeMonk said:
I'm running Fresh 2.1.2 and I've been having a ton of issues with lag that I never had on Fresh 2.0d. Are people having lag issues on the official 2.1 release too? I've tried to check and see what's running when the lag is happening, and it seems consistent with an app updating itself. I'll go to the list and see that mail has 5% or twitter (not peep) is updating and at 10% or something, but nothing is ever over that and it's always just one or two apps like that and the phone is unusable until they are done.
Now I'm noticing that if my phone is just sitting on the desk and someone calls, it takes a good 5 seconds for the phone to display the screen that tells me who it is. It vibrates, waits a couple seconds, then the default ring tone starts to play, then a couple seconds later the display comes up that says who is calling.
It generally is running like ass. It did not do this before on Fresh 2.0d. I was running apps2sd on that as well as on here. It seems that the only difference between fresh 2.0d and 2.1.2 is the fact that it's now the official released rom. Are people with the official rom having the same issues??? If they are, I'm going back to 2.0d. It ran completely fine. This is starting to get on my nerves and is not the experience I want....
Click to expand...
Click to collapse
Just go back to 2.0d. I ran 2.1.2 for a very short time and I couldn't take it anymore plus you know that the sprint 2.1 has confirmed issues one of which is the sdcard
Where can I get the original 2.0d now? Can someone post a download link to it please? I'm also experiencing a lot of lag these days as well..
Here's a quote from Fresh Toast v2.1:
A note on slowness: It is coming to our attention that there are several bugs in the latest Sprint 2.27.651.5 RUU which is the official Sprint release. It doesn't surprise me that there are bugs considering our original 1.5 had plenty. The main one that we have come across is a service called com.htc.bg that sucks up your processor. This causes that phone to become extremely laggy and overall run like crap. Go read my new FAQ: Why is my Android phone running so slow? to see what you can do about it, and to report the issue. Keep in mind that this would be a Sprint bug and not Fresh Rom / Fresh Toast.
Click to expand...
Click to collapse
I think this is why we're experiencing lag, hopefully someone can find a fix for it..
EDIT: Nvm, found the link, here it is:
http://geekfor.me/new-release/fresh-20d
I think you guys are right. I've been toying with the idea of using Fresh Toast to get overclocking, but 2.0d just worked for me and I had no real issues other than keyboard lag.
Are you guys running w/ Auto Killer (or alternative TK) or no? I've been running FT w/ AutoKiller set to Extreme, with max time between boots having been about 48 hours, and haven't seen any significant slowdown the longer the phone's been on..
My phone will randomly shut down and will not power back on unless I pull the battery, I have 2 batteries and it happens with either one. It does not shut down while on charger/dock. I have wiped the phone multiple times with odin, I've used several different roms/kernals,same results every time. Just curious if anyone else has been experiencing this issue.
I've been experiencing this after I went to eb13 with the custom kernels that are out. But my.phone will either lockup and I have yo pull the battery or it will reboot itself. Never had what happens to u yet.
Sent From My Evo Killer!
This has been happening multiple times a day to me. Completely at random. its beginning to become unbearable. My phone will lock up like this about 8-20 times in a day. Someone save meee! hahaha
nalewis89 said:
This has been happening multiple times a day to me. Completely at random. its beginning to become unbearable. My phone will lock up like this about 8-20 times in a day. Someone save meee! hahaha
Click to expand...
Click to collapse
I'm averaging 10 times a day myself
Permanent sleep
I may have experienced a similar problem, running a DK28 based kernel with both Quantum 2.5 & 2.7 ROM's.
When the phone sleeps and you're not able to wake it, do the 4 buttons at the bottom of the screen still light up? If they do then I have had the same issue. I could only narrow it down to restoring apps+data or putting the phone in sleep while an app is running. Once it was the result of putting the phone in sleep after a FC.
I can only posit that it MAY be an ext4-only ROM related issue, considering I did not have the above situation occur with rfs ROM's or rfs/ext4 dual ROM's. In addition this was only limited to DK28 for me. I was off DI18 <16hrs after I bought the phone. The DK28 gps issue was a non-factor as well, occurred whether gps worked or not.
before updating to 2.2 - I did the DK28 and now the EB13 one - with 2.1 I would have my phone randomly reboot - I would be sitting there and here the music it makes when it starts up but I never turned it off?
other times it would just be turned off, but when I turn it back on the abttery is not low enough to cause it to turn off
all this went away with DK28 2.2 and hasnet happened since I installed EB13 2.2
This happeed to me the other morning. I wasn't able to boot until I reflashed the kernel. Twilight frozen btw.
Sent from my SPH-D700 using XDA Premium App
My first epic would randomly hard power off, even running stock ROMs. If you are running a stock ROM and seeing a hard power off at random, I suggest you go swap the phone. It's just broken.
Ive never had this problem and im on my first and only epic and ive had it since it came out,
Ive been very careful with my epic as it has been great to me, it hates me probaly tho for feeding it stuff while experimenting things that make it spit up FCS,
But my phone has been always working perfect, all the way back to d118.
CLazman said:
I may have experienced a similar problem, running a DK28 based kernel with both Quantum 2.5 & 2.7 ROM's.
When the phone sleeps and you're not able to wake it, do the 4 buttons at the bottom of the screen still light up? If they do then I have had the same issue. I could only narrow it down to restoring apps+data or putting the phone in sleep while an app is running. Once it was the result of putting the phone in sleep after a FC.
I can only posit that it MAY be an ext4-only ROM related issue, considering I did not have the above situation occur with rfs ROM's or rfs/ext4 dual ROM's. In addition this was only limited to DK28 for me. I was off DI18 <16hrs after I bought the phone. The DK28 gps issue was a non-factor as well, occurred whether gps worked or not.
Click to expand...
Click to collapse
the buttons don't stay lit, i'm using twilight kernal right now but was happening with genocide kernal too, going back to eclair just to eliminate 2.2, ext4, etc.. to see if it's a hardware issue
First try
dk18 update.zip flash
Restored apps and data with my backup pro root
Random reboots, FC
Second try
Odin to dk18
Wipe x3
Restored apps and data with mybackup pro root
FC, music player force closing (doubletwist, stock and musicmod, poweramp worked though?), fc when trying to change ringtone or notification.
Started reading about others with the same issues and thought data backups were a reoccuring theme. Did a third try tonight and so far so good. Music players working, no force closings, keyboards working correctly, gps lock indoors. Its still early, problems might still popup, thought id share...
Latest froyotempt
Fresh backup with mybackup pro root
Wipe x3
odin eb13 prerooted (ctsy xda forum) same file from attempt 2. Did this x3 as well, read it in a thread somewhere...
backup apps only with mybackup pro root
All attempts were with genocide kernal.
So far so good, none of the previous bugs are apparent, so far... Those of you that are on the fence regarding doing the same, so far its worth the time.
Sent from my SPH-D700 using XDA App
I was thinking back-ups were part of the problem also, so I used odin and started all over from dl18 without restoring any data, same problem still occured
Still messing with my phone, everything that was broken seems to be fixed. Hopefully it stays this way...
Sent from my SPH-D700 using XDA App
That used to happened to me on eclair when I set my setcpu profiles too low when screen off. You wouldn't happen to be using setcpu would you?
actually I am, I have my minimum down to 200 MHz, going to raise it and see if that helps
@400 MHz did it again, trying 800
I'll add to this thread. I seem to be having the same problem and I believe it started when I installed quantum rom... but I'm not sure. The symptoms i had were random reboots, where the screen would shut off and the 4 lights would stay on. Then I would have the sound of lost signal as if my phone rebooted and was starting over. Also, the most recent problem I get is my phone completely shuts off and I need to battery pull to get it to start up, and it loops on the splash screen of my rom. I have tried doing a complete odin wipe and not restoring anything and I believe it is still happening...
joedig52 said:
actually I am, I have my minimum down to 200 MHz, going to raise it and see if that helps
@400 MHz did it again, trying 800
Click to expand...
Click to collapse
Any update?
Also, make sure the governor isn't "powersave". If you have 100-400MHz powersave governor, it still ONLY runs at the lowest speed (100MHz), even if it's 100-400MHz.
Still happening, not on powersave, doesn't matter what settings I have in set cpu. Did a hard reset back to 2.1 and it still happens, bringing it in for repair.
Hey,
I was hoping to find someone who had similar problems to mine but have had no luck, so I decided to break down and just make a thread.
My Evo (003) has been giving me really scary problems ever since I tried installing CM7 rc3. To preface, I have been installing the nightlies since 15 and could be considered a flashaholic. I run amonra 2.3 and have all of the latest radios and such. To avoid a long paragraph, I'll post them as bullet points. I've tried other ROMs and plenty of kernels and I get similar errors in every attempt. I'm currently running CM7 final and the latest savaged kernel
- Whenever I reboot the phone, it bootloops once, then boots fine
- When I take the phone off the charger in the morning, the phone runs badly and the charging light stays on until I reboot
- I get a lot of "phantom" keypresses every now and then that render my phone useless until it stops in roughly a minute
- The screen off animation no longer works in CM7
- The phone randomly reboots every other day or so
- General slowness
I can't help but be scared that I will restart the phone at one point and it won't boot up, like some other people are experiencing. Can I be saved?
Thanks for any help!
I have had mine for about 9 days now, and it has dose the sleep of death thing twice already... i am running Prime 1.5 it seems that peoples screens dont work after some sleeps of death... just wondering on it.
Optimus-Prime said:
I have had mine for about 9 days now, and it has dose the sleep of death thing twice already... i am running Prime 1.5 it seems that peoples screens dont work after some sleeps of death... just wondering on it.
Click to expand...
Click to collapse
I know that when I installed Prime 1.5, I get "Sleep of Death" every hour... I went back to stock and "Sleep of Death" went away... I'm not sure if this issue was fixed yet. I was told last week that it might be kernel related issue. But in the meantime, you can also try a different kernel and see if that fixes the problem... If not, try a different rom or even use Prime 1.4. Worst case is to go back to stock 3.1.
I'm still using stock rom right now and plan on using it for a while...
ill have to give stock a test drive. i did see that when i changed roms i did get sleep of death.
we can just flash a CWM stock rom right?
I had this problem for the first time today. I'm on Prime 1.5.
I also had no sound when I got it back on. Had to reboot to get the sound back.
Any similar sound/sleep of death issues?
Any new information on a permanent fix for this?
Thanks.
ASUS is working on a fix for this. It has something to do with 'power management.'
Just wait patiently while they release a OTA to fix this and then devs will also incorporate this fix within the ROM.
I had it nearly every time I left the tablet on for more than an hour without touching it. Upgraded to stock 3.1 and it hasn't happened since... (I manually flashed it; didn't wait for the OTA if that matters..)
My first TF suffered a SOD but I think it was a screen of death not sleep of death. I could never get it back so I replaced it at TigerDirect. My current solution? I pushed the TF off to the side of my desk and bought a Xoom...
zephiK said:
ASUS is working on a fix for this. It has something to do with 'power management.'
Just wait patiently while they release a OTA to fix this and then devs will also incorporate this fix within the ROM.
Click to expand...
Click to collapse
I read Asus saying they were fixing hte dock draining issue, nothing about the sleep of death. I have never had this happen, though I'm on stock, and form the looks of it the peeps that are on custom roms have this issue so doubt they'd fix a non-stock problem.
zephiK said:
ASUS is working on a fix for this. It has something to do with 'power management.'
Just wait patiently while they release a OTA to fix this and then devs will also incorporate this fix within the ROM.
Click to expand...
Click to collapse
I also only saw reference to the dock issue being fixed in an OTA. If you have a link to any information about the fix they are working on, it would be most appreciated.
Thanks.
So i replaced everything with stock, and no sleep of death yet to happen. but i have been using it alot lately so ill let it chill for about the next 2 hours and see what happens.
Optimus-Prime said:
So i replaced everything with stock, and no sleep of death yet to happen. but i have been using it alot lately so ill let it chill for about the next 2 hours and see what happens.
Click to expand...
Click to collapse
Thanks... let me know if it works for you.
Bought my TF a week ago, with 3.01, NEVER has seen SOD; today -finally- OTA upgrade to 3.1 in the Netherlands; since upgrade SOD every time TF goes in sleep mode..
Great upgrade, thanks ASUS! Any solution (except downgrading) around, plz?
Last nights OTA update fixed my deep sleep problems. This update apparently included a power management fix.
I've had my transformer for 2 months now. I had it stock, always updated OTA, until the NVflash/APX mode rooting method appeared and then I flashed PRIME! v1.4 and never had any SOD until recently when I upgraded to PRIME! v1.5. However, I did two other things around the time of the v1.5 upgrade that could equally have started the problem, namely; I started using a 16GB SDHC card in the keyboard dock and I also connected HDMI to my TV for the first time using a C-to-A adapter (this also does not work properly - uinstable image - intermittent digital interference flickers along the bottom of the screen).
I have since re-flashed PRIME! v1.5 using the APX/NVflash method and have stopped using the 16GB SDHC card in the dock and now the SOD has stopped happening..... HDMI is still an issue but that could be the cable and/or adapter.
Deep sleep , could it be tegra 2 issue?
the Folio 100, the toshiba thrive and Asus TF has this problem. all of them have Tegra 2. if i set the folio 100 to 30 minutes before sleep i can use it as long as i don't let it go over 30 min before i wake up the screen. if i close the screen (via the button) i don't get deep sleep problem before 30 min has gone. so there is some problem related to the CPU and memory going to deep sleep and can not get interupts from the button anymore
My SOD seems to only happen when it's attached to the keyboard dock. If I leave it undocked, it never get's the SOD. I'm on a replacement dock, and the original dock I had never gave me the SOD either.
I have the latest firmware installed and that didn't make a difference.
No dock. But had my first SOD with Prime 1.6 + Netformer and IO fix OC'd to 1.5
My first post so I'm locked out of development forum with the relevant thread
http://forum.xda-developers.com/showthread.php?t=1070343&highlight=waking+sleepsleep+of+death
Anyway, had my TF for only a couple of days, goes to SOD two-three times a day already. I didn't play around with 3.0 much before doing OTA to 3.1 but 3.1 and now 3.2 still put it to this unnatural sleep.
Actually, it didn't wake up after updating to 3.2 itself.
From reading that thread the best probable cause appears to be the voltage issue when CPU clock speed changes - when waking form sleep clock speed goes up but voltage doesn't or something like that, and if some processes are left running, like logging to a file, the system never really goes to sleep so no problem with waking but a problem with catching the culprit.
Someone also said that in 3.2, by design, there should be even more sudden clock speed increases so SOD problem might become even more frequent.
One more possible argument for the voltage theory - SOD doesn't happen when TF is charging, meaning that CPU management is not that strict. Someone reported that Juice Defender, the app to minimize power consumption/CPU load, actually caused SOD on his TF.
The actual cause of SOD is a failure to get the correct value for blacklight on waking so looking at the display closely with a flashlight one still can see it running, allegedly, and can even unlock it. If that happens and the system is otherwise responsive maybe there's a way to force the backlight on, maybe some widget that toggles autobrightness on something. I'm waiting for my next SOD to test this theory, sometimes the screen doesn't look black, simply not light enough.
Maybe all I've said is nonsense but I'm an unrooted noob, I'm allowed.
Hey guys,
I have rooted my device over two months ago. The first ROM I had flashed was running nice and smooth except for a few issues like the camera issue.
After a week or so, I've changed the ROM and since then, I've always had problems. The ROM runs nice and smooth at the beginning and later (between ten minutes and three hours) the problems start again.
It never got bricked but it always kept shutting down, freezing (short), lagging, overheating, not reacting untill pulling out the battery or all apps and services crashing and so on.
I then managed it to get working better than ever before running a custom ROM (don't remember which one).
But that didn't last long. After a day or so the phone started lagging again. I've booted into TWRP and wiped cache and dalvik. The next boot ended in a "encryption unsucesfull" and I had to reflash the ROM.
What I've noticed today was that it helped to wait abit before turning the phone on again after pulling the battery out.
Since then I'm trying to figure out how to fix that.
I'm waiting for the Oneplus 4/5 anyway, and I'm not sure anymore if I should root that thing too since I risk to go through the same (or worse) struggle all over again.
If you need any further information to help me, feel free to ask for it.
With my Note 4, I have waited till the warranty time was over.
Thanks in advance
PS: Heat seems to be a huge problem. I don't mean overheating, I mean usual working temperatures. That would explain problems like the massive drop in performance as soon as I got in to my car which was standing in the sun.
PS2: Kind of solved. Downloading the wakelock app and setting it on "partial_wake_lock" helped.