Related
I have to reboot my Tilt daily b/c it becomes uber slow. It takes FOREVER to respond to anything. Some things don't even respond. I have taken off everything that wasn't stock. Even reset the phone back to factory settings. I'm on WM6.1 the ONLY program I have running is Active Sync and I have to have that running for work.
I emailed HTC and they said to upgrade to 6.1 to which I told them I already was and they never responded. Is there an app to reboot my phone every day at a certain time? I'm about to throw this thing in the trash.
This is my 2nd one doing the exact same thing.
Oh wait... Can I volunteer my trash can?? I have never had that problem. But then I don't run stock ROMs.
So, if I upgrade my ROM it could potentially fix the isuue? Got a recommendation on a ROM to run? I'm not to up on that stuff.
First step: Flashing your First Rom (For Noobs) "read read & read again"
With regards to ROM choice it's a personal choice and you will find the ROM you like.
Take a read of the ROM threads.
stylez said:
First step: Flashing your First Rom (For Noobs) "read read & read again"
With regards to ROM choice it's a personal choice and you will find the ROM you like.
Take a read of the ROM threads.
Click to expand...
Click to collapse
Sweet, thanks!
I never had this issue, and i'm running the HTC stock ROM.
Well, I finally said screw it and decided to quit being a wuss and install a ROM. I wanted to try the HyperDragon IV, but the download link wouldn't work. So, I did this one http://sakajati.com/blogs/2008/11/hyperdragon-iii-raphael/
Been up and running for about an hour. Just getting my exchange email accounts finished and populating. So far so good. We'll see how long between reboots I can go.
Thanks for the suggestions guys.
you should reboot daily anyhow
I have had my TyTN II with stock rom for over a year now and I have never had to reboot without it being my fault, ie. installing something that doesn't agree with my device. Mine runs happily along all the time.
I have SK Tools installed and with it comes FreeupRam, which I run periodically to....well....free up ram...hehehehe.
Often some plugins do not agree with our devices, causing havoc, resets etc. This was my problem at one time. Now I am running Spb Mobile Shell and it is sweet, snappy and I have it customised just the way I like it. I found that phoneAlarm and HTC Home Customiser were the biggest culprits. Since I removed them and started using Spb Mobile Shell, I do not have those problems.
I also recommend that you purchase a programme called SafeMode. You set the time in seconds to boot into safe mode. It displays when the splash screen appears. This has saved me lots of frustration and unnecessary resets.
Here is the URL where you can buy it and it is well worth the US$12.95!!!
http://monocube.com/index.php?optio...atid=35:windows-mobile-professional&Itemid=56
Never
i never had this problem, i may restart my kaiser after 10 days or more, i am using Athenos WM6.1 ROM
Nope... My last flashing/hard reset was about 4 months ago, I have ~40 programs installed and don't usually reboot more than once every 1-2 weeks, unless it's because I've installed/uninstalled/changed something that requires me to.
Using original stock 6 ROM, no need to reboot. But i noticed that from time to time Kaiser just turns off, wtf?
Is that because of the ROM i'm using, anyone with similar experience?
phone goes off, no questions asked. I tried to shake sim card holder, suspecting it has something to do with it. Sometimes i have to remove battery for a while, then hold reset with stylus, then to turn it off. Can it be fixed maybe, or will flashing help?
Thanks
dakipro said:
Using original stock 6 ROM, no need to reboot. But i noticed that from time to time Kaiser just turns off, wtf?
Click to expand...
Click to collapse
Could your power button be sticky, or jammed?
Well, I didn't notice, it just sits on the desk, and goes off, then sometimes i just press power and it turns on, sometimes reset button needs to be pushed and/or battery removed, then just power button and it goes on again. I was suspecting most on sim holder, but testing it with fingers couldn't produce similar error. I'm really considering moving to athenes rom, but must figure out backup system in case i want to go back to stock with current settings and programs.
Hey all,
I posted a while ago about my phone having died and only having red flashing lights...I managed to solve that- thanks for you help, but now have a completely different problem.
Since then about a week has passed and approximately every 36 hours the phone seems to crash. When I take out the battery and turn it on again it invariably hangs at the Ericsson logo screen. When I then leave it off for a period of time (between 2 and 12 hours) I either find it starts to work again, or that I'll have the red flashing lights and have to leave it for longer.
When it does start working, it always seem to have been hard reset and I have to go through the set up again.
It's possible heating the battery speeds up how long it takes to start working again (although I've tried it with 2 batteries so I'm not sure why that would work) - and I'm not sure if that is actually the case yet or not anyway.
- It's very frustrating to lose all of my contacts daily, but I don't want to give up on £250 worth of kit... any ideas?
Thanks so much
welbis said:
Hey all,
I posted a while ago about my phone having died and only having red flashing lights...I managed to solve that- thanks for you help, but now have a completely different problem.
Since then about a week has passed and approximately every 36 hours the phone seems to crash. When I take out the battery and turn it on again it invariably hangs at the Ericsson logo screen. When I then leave it off for a period of time (between 2 and 12 hours) I either find it starts to work again, or that I'll have the red flashing lights and have to leave it for longer.
When it does start working, it always seem to have been hard reset and I have to go through the set up again.
It's possible heating the battery speeds up how long it takes to start working again (although I've tried it with 2 batteries so I'm not sure why that would work) - and I'm not sure if that is actually the case yet or not anyway.
- It's very frustrating to lose all of my contacts daily, but I don't want to give up on £250 worth of kit... any ideas?
Thanks so much
Click to expand...
Click to collapse
LOL,
no idea why.
Installed any tweaking software??
Sadly no - and I've tried it with 2 different roms too
welbis said:
Sadly no - and I've tried it with 2 different roms too
Click to expand...
Click to collapse
Heh, don't know.
Maybe some other rom's installation messed up something....
hmm... I faced the same problem...
So.. I did have to send it for repair :S ....
maybe i have the same problem... many roms tried, many soft and hard-reset, but the lifetime cycle of the phone before to re-flash the device is at maximum 1-2 days... now i'm trying the tips about quickgps (maybe could be correlated) on the thread in this forum... but the most probably truth i think that could be an internal memory rom damage... if anyone find a soluzion about this problem via software i'm here...
I seem to be having the same problem.
A week ago i tested the latest roms with winmo 6.5.1, after several roms i settled with a rom with build 23081, enabled htc sense, played around abit and went to bed and put the phone to charge. when i woke and touched the screen, the phone immediately froze.
After removing battery it froze again in SE boot screen and after second removal of battery the phone hard reseted it self.
The phone has been freezing and flashing itself ever sense, sometimes the uptime is minutes sometimes over day.
Currently the phone has survived 3 days without a spontaneous flash, the only difference is that i didn't bother to enable htc sense last time it flashed. So i enabled htc sense once again and will see if the phone survives a day.
ristiisa said:
A week ago i tested the latest roms with winmo 6.5.1, after several roms i settled with a rom with build 23081, enabled htc sense, played around abit and went to bed and put the phone to charge. when i woke and touched the screen, the phone immediately froze.
After removing battery it froze again in SE boot screen and after second removal of battery the phone hard reseted it self.
The phone has been freezing and flashing itself ever sense, sometimes the uptime is minutes sometimes over day.
Currently the phone has survived 3 days without a spontaneous flash, the only difference is that i didn't bother to enable htc sense last time it flashed. So i enabled htc sense once again and will see if the phone survives a day.
Click to expand...
Click to collapse
i had approximatively also the same problem... i'm trying to understand what is the reason of this instable situation... gps location? memory? graphic instance that use HTC sense? is heavy to understand... if anyone could also find the right solution...
was having the same problem tried the method in this thread http://forum.xda-developers.com/showthread.php?t=540290 and it is working on my X1 so far
lebkom said:
was having the same problem tried the method in this thread http://forum.xda-developers.com/showthread.php?t=540290 and it is working on my X1 so far
Click to expand...
Click to collapse
Did the "task 29" do anything?
I tried the method suggested but no change besides hard reset. And the X1 froze about 12h after that...
ristiisa said:
Did the "task 29" do anything?
I tried the method suggested but no change besides hard reset. And the X1 froze about 12h after that...
Click to expand...
Click to collapse
ye mine did it again aswell this morning
i just tried hard reseting then install a stock rom then hardreset again and install a custom rom, will let you know if it works
Do you guys often use Opera Mobile?
Ahah!
Very encouraging to see other people had the same difficulties... and I suppose that it's just a question of making sure a fresh ROM flash works properly.
Sadly mine has reached the stage where it's no longer working for 'a day' before crashing... it's just pretty much dead.
Now I can bring up the tricolour screen if I'm plugged in, the ROM then begins to flash off the memory card, but crashes half way through every time.
I have tried this with 2 batteries, one of which (which I have used once and was working fine but only lasted 2 days before breaking) now does nothing whatsoever. The other lets me get half way through the flash every time.
- I can't send it back on the warranty until I reflash it myself (and I don't have a receipt anyway) so I'm going to go find a high street mobile fixing place and see if they can help.
hardresetting then flashing a stock rom (R3A generic) then hardresetting again then installing custom rom and hardresetting, definately fixed my phone, has been working for more than 2 days now it usually stops in less than 1 day.
FYI - high street phone guys managed to reflash the device for £15....it lasted 4 days but has just died again.
Hi
I am new to Android world. So please handle with care
I used to use an iPhone. Recently (bout 3 weeks ago) I bought a galaxy note and am loving it.
I was going through a lot about Android system and found out 'rooting a phone'.
so I rooted the note and installed Rocket rom v22, GoLauncher Ex and few apps like Setcpu, Adfree, Bank, Xchange etc. I don't have games or many apps on my phone.
My phone turns itself off randomly every now and then. during phone conversation it rebooted itself once so far. and when my phone is stand-by, I found my phone is turned off.
I am not sure why it's happening. Is there any settings i shouldn't set?? or ???
Could anyone please tell me how to fix this issue?
If the phone is faulty, I need to make my phone as the same as when I first got which I am not sure how to :-( yet
The first thing to do is go completely stock. Flash the lastest stock rom and see if that fixes the problem.
When using ICS ROMs there's a known bug called Sleep of Death (SOD) that is similar to what you're experiencing. The phone simply won't turn on the screen and you have to press the power button for several seconds to turn it on again.
Almost all GNote users experience this issue so don't worry about it. Going back to stock will not solve the problem.
Hi
Thanks for the reply.
Before the rom v22, I had v19. my phone still did turn itself off several times. after flash the room v22, it didn't happen as many as v19 so I am not sure that the ICS causes the issue.
anyway, I will try the one you suggested and see how I go.
Thank you
kelvin fong said:
Almost all GNote users experience this issue so don't worry about it. Going back to stock will not solve the problem.
Click to expand...
Click to collapse
I am more worried about the alarm. if the phone turns itself off while i am in sleep, i won't be able to hear the alarm going off.
well if that happens again, i might have to get a alarm clock.
i was thinking of setcpu app might cause the issue... not sure though.
Thanks for your help
I experience the same issue when i was running stock. I've tried several stock versions but the problem still exists.
Sent from my GT-N7000 using XDA App
I have definitely never ever experience SOD when the phone is stock and lock.
The only time i did experience SOD is when i change to modded kernel.
I'm running stock with cf root and have never ever experienced this, so not all notes are affected. That would really suck!
Sent from my superior GT-N7000 using Tapatalk
Never had Sleep of Death on stock rom.
I am on stock ICS Rom n it has happenedwith me twice.
My GNote goes dead randomly and only starts up after pulling out battery.
Weird!
Install an ICS from Clean
Start from a Stock ICS rom using PC Odin, then follow my Post as follow :
http://forum.xda-developers.com/showpost.php?p=26772618&postcount=12
Try another rom other than that you had, or a higher versionof it.
The MIDTEAM v1.4.2 is Good and Stable.
Good Luck
I had this problem most of ICS ROMs on my Galaxy Note. SO I guess it's an ICS related bug and it is very uncomfortable to have to reset it to unlock it .
I too have tried several Stock ROMs but it still gets into the Sleep of Death at least once a day.
I guess that it should help to have a Kernel that changes the Deep Sleep settings...
Of my 2 GNotes, one of them had this problem. Happens when you put the note on the table with small drop or whatsoever.
The problem disappeared when inserted 3-fold 80g paper between battery and the edge of battery compartment. The battery tolerance is not so tight so when small drop (like putting on the windowsill) happens, the phone shut down.
The problem completely disappeared after inserting paper.
Of course, more professional would be go to Samsung repairs and show it and ask for replacement - either battery or phone internal casing. You can reproduce the problem by turning the screen on and dropping phone 10cm into hard surface.
But I did not bother.
I won't say that yours has exactly the same problem. But check the tolerances of battery 1st. Sometimes solutions are too obvious to see 'em.
I upgraded from stock to CM9 3 days ago and my Note has turned off several times a day since then. Never before upgrade, so I don't think it has to do with battery being loose in its compartment - not in my case.
I am loving ICS, but I will have to downgrade to gingerbread to get rid of this irritating bug.
this is happening to my galaxy nexus!!! yeah it turns off at random like sleep of death and small drops can trigger it. if i knew this could happen i would have never rooted
lol root itself has nothing to do with it.
if small drops cause it, and paper adding in compartment fixes it. its the gap between battery and whatever should fixate it.
if it occurs during deep sleep, dig into logs what you can find there. Also check roms/kernels feedback if others have it with that version. Many ways to illiminate possibilities.
I miss some good analyzes in this is issue from those experiencing stuff. Android I guess is not user friendly that way.
Sent from my GT-N7000 using Tapatalk 2
Galaxy Note Sleep of Death on 4.1.2 JB
I'm still trying to figure this out... I had hoped that with Samsung Stock upgrade to 4.1.2 it would be fixed but its not... anybody still experiencing this problem?
Things that I have tried
Move all apps from Internal SD Card (USB) and format
Factory Reset
Paper wedge between battery
Opened and re-connected all connectors to Motherboard
Install CPUSpy (deep sleep is OK)
I'm at wits end now, and this problem is very apparent. I havn't wanted to flash to a custom rom, because I've seen reported that it still happens with whatever ROM whether stock or custom
Any more ideas on how to make the Sleep of Death go away?
rasielbz said:
I'm still trying to figure this out... I had hoped that with Samsung Stock upgrade to 4.1.2 it would be fixed but its not... anybody still experiencing this problem?
Things that I have tried
Move all apps from Internal SD Card (USB) and format
Factory Reset
Paper wedge between battery
Opened and re-connected all connectors to Motherboard
Install CPUSpy (deep sleep is OK)
I'm at wits end now, and this problem is very apparent. I havn't wanted to flash to a custom rom, because I've seen reported that it still happens with whatever ROM whether stock or custom
Any more ideas on how to make the Sleep of Death go away?
Click to expand...
Click to collapse
What is the status of your phone now :
Working or not?
It works then it turns off by itself
Bootloop
Stuck on the white Samsung logo
Completely Off?
It does work but it turns itself of, the longest its gone without restarting is 44 hrs. I contacted Amazon where I bought and they are offering s full refund, so I , might send it back but I love it and had wanted tho keep it if the problem is fixed.
Sent from my GT-N7000 using xda app-developers app
Turning off problem too
I don't know if it is exactly the same problem, but my GNote keeps turning off every time, but not seem to be randomly. Looks like ti shut down every time a high performance is required. I tested several roms, ICS and JB, custom and stock, but the problem still goes on.
Please, any ideas?
So i've been experiencing this issue for months now. I've had the issue since i've gotten the phone but its the past few months that its really gotten bad. So before anyone jumps the gun, i've done quite a bit of research on this and cannot find anything worthwhile, more on that soon.
So as usual, i'll pickup my phone and press the power button or the home button to turn on the screen, but at completely random times the screen will not come on at all. Sometimes the capacitive buttons will light up (maybe 15-20% of the time), but not always.
In my searches I found the following solutions to this problem:
Get a new sim card
Dont use an SD card
Get a new battery
Check the leads on the battery and phone for cleanliness
Factory reset
Remove 1 app at a time and test until it stops happening
Dont freeze any apps
Restore stock firmware
Dont use SetCPU
Turn off animations
Get rid of the lock screen
Remove custom message from lock screen
Clear cache through Recovery
Dont restore data with Titanium Backup when restoring apps
Turn off WiFi and/or Bluetooth and/or GPS
Dont use GreenPower or Greenify
Avoid stock launcher
I have tried all of the above except for removing 1 app at a time (and those that dont apply). I'm deep into that one and only have a few apps left to try. This is something that happens at least once a day, but typically 3-5 times in a day. I used to think i could make it happen by pressing the power button to turn on the screen and immediately hit it again to turn it off. It would sometimes work but that doesnt trigger it anymore.
My phone used to be rooted, but being on AT&T there was no "normal" way to flash a good recovery like CWM or TWRP and install roms, you have to use some other thing which i dont use. So i've always had stock recovery, im fully updated to the newest stock rom that is out, update came OTA which was after i removed root and used odin to flash an older stock rom back. My wife's Note 3 also has the same issue and it has never been rooted, we have gone through all of the above and still it continues to happen.
Also on a side note, my phone was swapped out because of an issue it had 3 months after i purchased the phone. I was able to get a brand new one, not refurbished. The issue had occured once or twice before the swap and an incredibly frustrating amount of times since then.
Reading through most of the other threads, everyone seems to have to remove their battery and re-insert it to get back into their phone. The ones that dont have to do that have found that removing their SD Card, getting a new one, sending the phone in, or one of the other options have worked. However for me, nothing has worked.
Does anyone have any other ideas? Is this common on the Note 3 (I've had it since release)? 70% of the time i can hold the power button for a few seconds to try and bring up the power menu and it works, but not always.. I usually just have to wait up to a minute or two (never actually counted, i use my phone for that stuff...which.. isnt..working...)
I've had wake lock lag on a few android phones. Even iPhones.
I would highly recommend rooting it on att and flash a mod that reduces it on the note 3. I talked about it here.
http://forum.xda-developers.com/showthread.php?t=2628716
Rebooting the phone always helps.
wudien said:
I've had wake lock lag on a few android phones. Even iPhones.
I would highly recommend rooting it on att and flash a mod that reduces it on the note 3. I talked about it here.
http://forum.xda-developers.com/showthread.php?t=2628716
Rebooting the phone always helps.
Click to expand...
Click to collapse
Unfortunately I cannot root my phone. I have to have my company email on my phone, and for Android devices they use Air Watch. I tried for weeks to get it working while rooted, and even used Root Cloak or something like that (with Wanam Xposed) to hide root from specific apps. Air Watch was specifically tested to work with that app but it still for some reason didn't work (new version of Air Watch perhaps with no update to Root Cloak? Just my guess). I had to remove root, factory reset and re-flash stock from Odin (that was a dual purpose flash) to remove all traces of Root so I could use Air Watch for my company email/calendar/contacts/etc again, even after unrooting and using all the cleanup tools, triangle away, and everything, it still detected my phone as rooted...
However, I don't think that's really a viable solution to the problem, that's more of a band aid. Looking at that thread and looking around, it seems to work well but I still haven't found anyone with my same issue where they used it and it worked. I would like to narrow this down to what the issue is exactly, the root cause. I think its a problem with KitKat, or at least all of 4.4.x (not sure about 4.4.4 yet).
I may be the lucky one whose screen didn't start to peel off yet,but f*ck me this phone is starting to really piss me off.
Everything worked well after I have gone to SLiMM 1.4(way before) and as I was upgrading SLiMM versions it was slower and slower to the point where the phone is unusable!
So I thought,let's try to do a good old phone reset,reflash the ROM and go from the beginning.
I restored the apps,rebooted the phone and it was STILL painfully slow,so I resetted it again but this time restoring half the apps and half the Xposed modules I have used before.
It improved a tiny bit but nothing significant.
So I thought it is finally time to unlock the bootloader and see if there is any good AOSP ROMs,as the first one I tried was AOSP 7.1.1.
Fastest ROM I have used by far,the biggest problem,my device gets very hot from loading Messenger and jumping back to Snapchat and in AOSP 7.1.1 it would stop charging the phone because of the high temperature and this was quite a big issue.
So after using it for 2 weeks,I couldn't handle the charging thing anymore,so next best thing was Sony Concept ROM.
I install the ftf,goes well,install the recovery,install DRM fix,SuperSU and Xposed.
After rebooting I notice that Xposed didn't install properly so I jump back and flash it again,and the problem now was it would get like VERY VERY hot(you couldn't touch it) when it came to the "Android is starting" screen and of course the device started rebooting itself because it was way too hot.
So what I did was put the phone on a bag of f*cking ice to keep it cool,and it FINALLY passed that screen,only to find out a second later it returned to the bootanimation and gone into a bootloop.
Now I reflashed the ftf,but before even booting the ROM for the first time I flashed recovery,Xposed,SuperSU and the DRM fix.
It booted up fine,so I started to restore my apps and everything went well until I rebooted my device to find out it doesn't want to log in to Snapchat,the app I use very often.
So I flashed Magisk,systemless Xposed just that I can hide the root from it and disable Xposed just to log in to my account.
Even that didn't work so fine I'll try it next day.
So I decide to reboot the phone quickly and it has gone into the "Android is starting" screen and shut off in the half of the process. F*cking pissed.
I cool the phone down,boot it up,wait for it to finish and when it was close to finishing it has gone into a bootloop,and wiping cache doesn't solve it.
It is currently in a bootloop as we speak.
I really do like the phone but why is it behaving so badly? I do not know if someone had a similar experience as I did.
If anyone could give me a suggestion to make my phone stable and functional,please write a post since I need my phone to work.
Flash original android rom/kernel to the device to make device fully stock. Once it is back to stock, if problems still continue i recomend sell device and buy new one.. On my xperia, display stopped working out of blue, replaced it and my camera became blurry and vibration motor stopped working... Opened it again, fixed vibration motor, now it waits another opening to replace battery and camera lens... Disaster, but hey, device is great in hw department..
Strmy said:
Flash original android rom/kernel to the device to make device fully stock. Once it is back to stock, if problems still continue i recomend sell device and buy new one.. On my xperia, display stopped working out of blue, replaced it and my camera became blurry and vibration motor stopped working... Opened it again, fixed vibration motor, now it waits another opening to replace battery and camera lens... Disaster, but hey, device is great in hw department..
Click to expand...
Click to collapse
I forgot to mention,every time I said reset the phone I actually did flash the stock ftf and set it up all on my own,but whatever.
I guess it is just bad luck.
Dinkec27 said:
I forgot to mention,every time I said reset the phone I actually did flash the stock ftf and set it up all on my own,but whatever.
I guess it is just bad luck.
Click to expand...
Click to collapse
Jebiga mi Hrvati imamo lose srece sa mobitelima hahah
More luck next time
Dinkec27 said:
I forgot to mention,every time I said reset the phone I actually did flash the stock ftf and set it up all on my own,but whatever.
I guess it is just bad luck.
Click to expand...
Click to collapse
internal memory is failing.
bookworth said:
internal memory is failing.
Click to expand...
Click to collapse
Awesome
bookworth said:
internal memory is failing.
Click to expand...
Click to collapse
Dinkec27 said:
Awesome
Click to expand...
Click to collapse
Exactly, I suggest the same issue. I had exactly the same problem on my Xperia T, it became slower, slower, incredibly slow after three years so I couldn't even flash anything using flashtool - it was showing many errors. Even after factory resetting the phone, it was booting and setting up for like... two hours or more, becoming VERY hot but it finally booted, still was very slow.
Two solutions - warranty or selling it.
romcio47 said:
Exactly, I suggest the same issue. I had exactly the same problem on my Xperia T, it became slower, slower, incredibly slow after three years so I couldn't even flash anything using flashtool - it was showing many errors. Even after factory resetting the phone, it was booting and setting up for like... two hours or more, becoming VERY hot but it finally booted, still was very slow.
Two solutions - warranty or selling it.
Click to expand...
Click to collapse
It just doesn't make sense to me that the internal memory could be failing just under a year...
I cannot go for warranty since I voided it with unlocking the bootloader,and selling it is not an option because I am on a contract currently and I can only sell it once it expires and then get a new phone to renew my contract.
If it is internal memory,it is a second tine in a row,before I had the Galaxy S3 and it had the same symptoms,it looks like I'm prone to internal memory failures lol
Is there a way I can test the internal memory?