Related
Can someone please help me..
I installed Cyanogen 3.4 when it got released a few days ago and it was running smoothly.. I think he is a genious. Just today my phone shut off on its own and I had to take the battery out and put it back in to get it to come back on. I don't know if it is Cyanogen or some sort of app, as I download apps quiet frequently. I am going to go through my apps now and also reinstall Cyanogen 3.4 tonight and leave my phone on all night. I guess I will have to see in the morning..
Anyways, can someone help
I ve fot sometimes the same issue with dudes cupcake which use th cygnonen kernel...
I ll be glad to have a fix
Are you overclocking the processor? That might contribute to it shutting down.
I do overclock but why do i have to 'battery pull' to make it reboot?
Yes, same issue here.
Uhh, again...
Powered up, set to standby, waited 1 min, shut down.
EDIT: I'm on Rogers Cyanigenized.
Same issue here. Complete lockup with screen off, have to pull battery to boot again. Seems to happen every 6-12 hours for me.
My Phone:
Cyanogen 3.4
radio 2.22.19.26I
Haykuro's SPL
Kernel 2.6.27.24-cm by [email protected] )
NOT overclocked, and no clocking tools even installed. Persists after several clean wipe and reflash also.
This thread's timing is great... I was just about to reset back to rc29 and build back up. Thought I was going to have to replace my phone
Rastasia said:
I do overclock but why do i have to 'battery pull' to make it reboot?
Click to expand...
Click to collapse
This question should probably be in the Dream section and will probably get locked/moved but Pulling the battery reset the "overclock" until it boots back up. This would be why pulling the battery helps.
hey you don't havbe to pull battery just push end call start call and menu all at once it will reboot you phone
Ok, thanks to Jakob, we know, that android freezes, is doesn't shut down.
I now tested with and without overclock, it made no matter to me not to overclock, there's no difference.
But I experienced it didn't happen when it's connected to a charger..
mysterious..
This keeps hapening to me, first it was happening in Cyanogized Rogers rom, then in The Dudes 1.3 b 12, I'm flashing JAC1.62 right now, this never happened to me before I got my class 6 16gb and started using apps2sd
Just curious, does this happen to anyone without a2sd
i'm having the same problem
seems to happen in the builds using the Cyanogen kernel. I'm sure this issue will iron itself out in future releases so just sit tight.
I too am having the problem on the Cyanogen 3.4 build. Its definately a change in 3.4 as I didn't have this problem in any of the 3.3 betas. I'm doing Apps2SD as well.
One thing I have noticed as well is that networking has been acting flakier than normal.
I had this issue on the pre-cupcake radio but not as frequent, so maybe it's just an amplified version of the same problem? There was a thread about it before but I'm too lazy to search for it.
The hangs was the only reason I moved to virtududes rogers rom v3
I'm going to try and get this sorted out tomorrow. For some reason the OOM killer kicks in sometimes and kills a critical process like zygote.
atleast you don't have this problem!
I've reflashed,wiped,formatted and apps2sd2 or sdpsplit, so many times already... trying different ways for each. But same thing always happens... my memory card gets damaged then wiped all by itself.
Uninstall toggle Setting and use Reparing Ext partition with Cyonagen recovery seems to fix this issue
So happy I found this thread! I'm using Google Ion and having this issue since yesterday. So annoying. Anyone got a fix?
I`m having the same problem, the phone freeze, looks like is a hardware problem, i`m on CRC1
I have started to have this issue as well. I am currently running Cyan4.1.999. It happened yesterday while on a call, after a call, and also while the phone was on charge.
Solutions?
Hello there,
I really am stumped, and would really like some help! I've searched the forums, can't really find what I'm after, so apologies if this as already been asked/answered.
Basically, my G1 hangs a lot when it goes to sleep. I'm running Cyanogen 4.0.4 with an 8Gb Class 6 card - everything was fine when I was using the stock 2Gb card that came with the phone, but after having loads of trouble trying to transfer my apps, I decided to just wipe and start again. The card is Ext2 parted with a 293Mb size partition. I did have it as Ext3, but thought this might be the problem (since I didn't have any problems with Ext2 on my old card), and wiped and repartitioned as Ext2 but that wasn't the case and problems persisted. Occasionally the phone will hang when it is on, but mostly the hanging happens when I leave it alone for a while; the screen stays dark and nothing happens, and I have to take the battery out and restart the whole phone.
One thing to note is that when I did reinstall everything, MybackupPro often didn't like the card, and gave me 'I/O problems with card' or 'Cannot install app' mesaages until I rebooted and started again each time the messages came up. I had to reinstall my apps in 10 - 20 app chunks in the end, rebooting when errors came up, but eventually I got everything reinstalled.
I'm running Swapper (I know Cyanogen does something similar natively, but wasn't sure how it worked...someone please correct me if I shouldn't be using it), and Overclock Widget. Like I said. I never had a single problem before with my old card and these apps, so this all leads me to think it may be the card, but any advice would be much appreciated!
markdjj said:
Hello there,
everything was fine when I was using the stock 2Gb card that came with the phone
MybackupPro often didn't like the card, and gave me 'I/O problems with card' or 'Cannot install app' mesaages until I rebooted and started again each time the messages came up.
I never had a single problem before with my old card and these apps, so this all leads me to think it may be the card, but any advice would be much appreciated!
Click to expand...
Click to collapse
Hmm... sounds like the card to me. And the fact that you are using swapper on a possible defective card may very well be causing your system to hang. The system is relying on the sdcard as part of it's memory. So if the cards fails at any point, so will your phone. It'll be like pulling the RAM module out of your computer while your using it. Include a logcat of the phone crashing if you can and post it. Also reformat and check the partition for errors.
Thanks for your advice, I thought it may be the card too. Partitions seems fine...I used Partition Manager and it didn't throw up any problems.
As for Logcat, I did try and do that, but got a bit stuck trying to fiddle with my computer, and I don't think it's going to happen. I'm a bit of a newbie I'm afraid.
I don't mind getting a new card, but the only thing I'm concerned about is moving my apps...on this post here http://forum.xda-developers.com/showthread.php?t=553469 it looked pretty easy, but could you tell me if these commands are to be executed in the terminal on the handset? Does it copy the apps, because I imagined that if you fiddled with stuff that's in use (like moving an app from the Ext2) would cause a lot of FCs and possibly even hangs.
odd hang
I myself am getting a bit of a hang when waking the phone up, i have to hit the menu button several times, kinda reminds me of the coma issue that we had back on the old kernal. i didn't have a problem till i clean out my phone by wiping and reformating my card, it is not that big off a deal but it is just strange. oh and to the op, you do not need to run openclocker since cyanogen's rom has cpu scaling that does it already and if you have your partions in order as fat,ext,swap than it will auto use compchace
gridlock32404 said:
I myself am getting a bit of a hang when waking the phone up, i have to hit the menu button several times, kinda reminds me of the coma issue that we had back on the old kernal. i didn't have a problem till i clean out my phone by wiping and reformating my card, it is not that big off a deal but it is just strange. oh and to the op, you do not need to run openclocker since cyanogen's rom has cpu scaling that does it already and if you have your partions in order as fat,ext,swap than it will auto use compchace
Click to expand...
Click to collapse
My phone did the exact same thing when I was using either Jac's Hero 1.3 or cyanogenmod 4.0.1. I tried everything and it wouldn't go away so I ended up switching to xrom.
Since cyan has been doing a lot of kernal tweaks lately do you think that it is possible that the coma issue has gotten reintroduce though, I mean both mine and the op is doing it, his is worse but if you remember that is what was happening to a lot before, mine never got to the point of pulling the battery but to the point of annoyance just like it used to
How is the xrom <that's jac's non hero build, right?> is it comparable to cyanogen's, I love cyan's performance but if this persits, I might find something else for awhile
I love it honestly. He just updated it to 1.4r3 and its is sweet, it has a custom theme and it looks really good. The performance is great and I don't even use a swap with it. I tried cyan again when 4.0.3 came out and only used it for 2 days before switching back to xrom. Personally I liked the icons and lockscreen of xrom 1.3r3 better then 1.4r3 but that is just my opinion, If you want to try 1.3r3 I can send it to you since it's not up anymore. Try 1.4r3 first though and see what you think because IMO it is the best rom out. Hero is nice but no matter what you get some lag and after a week or to it gets slower so I don't use it yet, I try the new builds but never stick with them.
Yeah I feel the same way but the hero builds too, nice to play with but nowhere near usable for me, I might just have to check out the xrom but I don't wanna give up loccy's browser, it is just friggin sweet and it works good for me because of the option of viewing just destop versions of sites since I get the men's health daily newsletter and whenever I would click on a link it would give me the moble version and not the article I would like to read, if loccy's brower works on the xrom, we might just have a winner
I haven't tried it yet so I'm not sure. Is it just a simple .apk to install or do I need to push it?
I just read the thread on the browser and it says it should work on xrom. It says to push it but I have just installed it like a normal apk before
Yea I am downloading it right now so I will let you know how it goes. Just so you know the browser on xrom doesn't have those zoom in/out buttons that pop up when you touch it, also it has multi touch just no double tap to zoom. I don't see any settings for turning off mobile pages though.
Well I am downloading the xrom right now so I will be flashing within the next half an hour or so, let me now if the browser works for you, by the way is compchache or swap automatic on it like cyan's or do I need to set it up myself, I perfer swapper, it just seems to work better for me
I think swapper is automatic but to be honest I never have used it for xrom because it is fast enough without it. The better browser works I just installed it normally, no pushing and I am using it right now with no problems, you have a pm.
If you like the notification bar icons in the first picture on the xrom thread they are from 1.3r3 because they changed in 1.4r3. If you want the older ones I can give you that rom amd it runs just as fast, only has a few differences from the newer one.
This xrom is nice, I am happy with the newest, oh and when I installed swapper and went in it was already set at 96mb and swappiness of 80 and I am on a fresh install and reformat so it must be automaticly set to then, explain why it is so smooth. Definitely comparable performance wise to cyanogen so I might have to stick with this for a while
I dont even have a linux-swap partition on my sd and I haven't had any problems with speed or lag.
Mine is silky smooth, better than I have had on any roms even the stock one
I was wondering if I was missing a post. I still get random Cyanogen Shut downs. I am using 4.2.13 after a wipe and still experience random shutdowns.
The phone just goes dark and I have to power it up again.
I have read some people attribute it to locked home screen and some people while using locale.
It is quite frustrating and I was wanting to know... if there isn't a fix, what Rom should I port back to. I need to clear this up because it gets aggravating missing calls.
Give superD 1.2 a try or even dwangs ROM they both are very speedy and well stable
Try re-flashing the rom, or you can try another rom as you said...i recommend Super D or WG Build....i myself use WG Build
You might be running out of system space.
Go to console:
$ su
# df
Check the Available next to /system. 28mb should be normal, but you could always apply the 10mb ramhack. Go with CFS for stability.
Can you recreate the scenario by which the phone will reboot on it's own and get a logcat?
No I cannot recreate it, it is very random. Afterwards I cannot logcat. I have tried wipe and reinstall of alot of his roms, all of them do the same thing.
I was hoping there was a fix because it is his rom I prefer.
I guess I will try another rom and maybe the problem will resolve itself.
Brutal-Force said:
No I cannot recreate it, it is very random. Afterwards I cannot logcat. I have tried wipe and reinstall of alot of his roms, all of them do the same thing.
I was hoping there was a fix because it is his rom I prefer.
I guess I will try another rom and maybe the problem will resolve itself.
Click to expand...
Click to collapse
Try Enoms rom if you tried Super D and WG-Build Y-2.6 with no success.
The problem you have is definitely weird.
I also suggest updating your Radio, Spl and RA Dream to the latest versions.
If possible try another microSD card preferably Class 6 to see if that fixes your problem.
I've been experiencing this same thing with random shut downs. I am running 4.2.13 also.
I have tried a wipe and re-install but the problem still exists.
There doesn't seem to be any rhyme or reason to it. The only thing I can say is that it always happens after the phone has been idle and when I go to pick it up it's powered down and I then need to power it back up.
It is very frustrating becuase you're never fully aware that the phone is off until you go to use it. I don't know if it's the ROM or some program that I've installed. I've been uninstalling all recent programs but so far the problem still exists. Perhaps I'll try one of the other recommended roms.
I have tried the stock rom and Dwangs rom, so I doubt its the ROM. Also I installed minimal applications and it still happens.
Its a toss-up between battery and phone. Although my battery is an extended battery, it can happen even when the battery is at 80%+ charge.
I called T-mo and they are going to swap out my phone. When I get it I will run the stock rom for a couple days with my Extended Battery. If it continues, I will put the stock battery back in it. Then I will go back and root it. If the problem comes back, then it has to be the rom.
Brutal-Force,
I'll eagerly wait your results. Unfortunately I purchased my G1 off of ebay a year ago so if it is the phone I'm out of luck.
Out of curiosity do you use Nitrodesk Touch down for Exchange? I've had some reboots right in the middle of synchronizing my email with this program.
Thanks
No I do not. As a matter of fact, I had uninstalled almost everything in an attempt to track down the culprit.
I really do think its gonna end up being the battery. Since the phone is not an option for you, I would recommend trying out a cheap 10 dollar battery off the internet. While I can't imagine why a charged battery would do this, I have noticed by looking at a friends G1 that the phone interprets batteries in different ways. In his phone his battery never showed below 90% even though after 10 hours it would run out of battery. As soon as he put in on the charger it showed 90%.
I to had purchased one of the extended batteries shortly after purchasing the phone. It has worked fine for just about a year but perhaps it is beginning to have problems. I'll dig out the original stock battery later today and try that for a day or so and see what happens.
Thanks
I have the same problem. My phone randomly restarts. It's more of an annoyance rather than a big problem, especially since it's almost always a restart and not a shutdown. If you guys do indeed find out it's the battery do post your findings here!
Thanks
I have exactly the same symptoms. Though before I saw this post I was attributing it to the fact that I have recently dropped my phone.
I also have a spare battery (I'm using Andida instead of original now), so I'll test to see if that happens with the original too.
Hmmm..
OK so i take out my extended battery and put in the original battery and plug it in to charge since it's on the low side. The phone immediately reboots and continues to do so indefinitely.
As soon as the home screen comes up it reboots.
So I put my extended battery back in and same thing. Now I'm not sure what to think so I've backed up my SD card and performed a complete wipe and am installing a completely different ROM.
I'm hoping it was the ROM or some program and not the phone.
I'll get back later.
rckeystone said:
Hmmm..
OK so i take out my extended battery and put in the original battery and plug it in to charge since it's on the low side. The phone immediately reboots and continues to do so indefinitely.
As soon as the home screen comes up it reboots.
So I put my extended battery back in and same thing. Now I'm not sure what to think so I've backed up my SD card and performed a complete wipe and am installing a completely different ROM.
I'm hoping it was the ROM or some program and not the phone.
I'll get back later.
Click to expand...
Click to collapse
Its good that you guys are investigating the cause of this issue. I too admitingly started using CM when I first rooted my phone. I too had issues and FCs so changing the Rom was the first thing that came to my mind.
You never know maybe its the battery (see the 1700 battery thread on the many problems Andidas has had with their G1 extended batteries)
In the end I am hopeful that you find a solution and have found out sometimes its as easy as changing Roms to fix many complaints/issues you might have.
This is what I've experienced so far.
I did a full wipe of my phone yesterday and installed the AOSP ROM (went away from cyanogen) and I have installed most of my programs. So far all is great. I've had no reboots or any other issues. Since yesterday I have been using my extended battery so I know the battery is OK.
I can't say for sure what was causing my issue. I had been using cyanogen's ROM for quite some time so I don't have a reason to think it was the ROM unless it was one of the current updates.
Perhaps I just had a collection of issues that came to a head and it was time to clean the phone and start over.
Same Problem
Hi, First post here. Great site by the way.
I am having the same problem as you are. Cyanogen, manup's 2.1 (1.5) and the "official tmobile 1.6" rom would frequently reboot or shut off on me. I tried three different sd cards and completely wiped my phone everytime i went between these roms. After much frustration I unrooted my phone last week and went to stock 1.6. It was working perfectly fine but the terrible battery life convinced me to try rooting my g1 again. After going through all the steps the same symptoms came back. So in order to be able to use my phone I went back to the stock unrooted rom. I also would like to mention that before these symptoms came up I had my phone rooted since may 2009. I also tried various SPL's and recoverys while trying to resolve my problem. Thanks
Random reboots are the reason why I don't run CM roms for any length of time anymore. I do load them from time to time to check it out and what not, but more often than not, I always find myself back on a Dwang rom.
My new G1 should be arriving tomorrow, but it has been 2-3 days now with the original battery. No shut downs. While it will be nice to have a new phone (although my phone is unblemished) it will suck to have to re-root it. I am pretty certain its the battery.
I will recheck when I get my new phone set up, I will put the extended battery back in it. I am still pretty certain it is the battery though.
Wouldn't open up a thread for this question but any custom ROM (RECENT EDITIONS) I've tried (NRGZ's, Sergio's, Ark's, Athine's and some others) for several days now have the "dead aka black" screen issue. Tried to find an answer in the original ROM-threads but haven't got any substancial responses. It seems like only few people have these issues. This would make me think the problem is my hardware (German Generic TP2) but the older ROMs of same chefs then run normal and without the dead screen issues.
Please any ideas, solution suggestions or experience share?
Thanks! Ibster
Edit: confirmed solution method described in post# 10 http://forum.xda-developers.com/showpost.php?p=5934002&postcount=10 . Thank you agent 47 big time for the tool you provided!
Ibster said:
Wouldn't open up a thread for this question but any custom ROM (RECENT EDITIONS) I've tried (NRGZ's, Sergio's, Ark's, Athine's and some others) for several days now have the "dead aka black" screen issue. Tried to find an answer in the original ROM-threads but haven't got any substancial responses. It seems like only few people have these issues. This would make me think the problem is my hardware (German Generic TP2) but the older ROMs of same chefs then run normal and without the dead screen issues.
Please any ideas, solution suggestions or experience share?
Thanks! Ibster
Click to expand...
Click to collapse
Is this the same as the "Sleep of Death" (SOD)? In which the phone won't wake from sleep/suspend state and has to be soft-reset?
If not, what's the symptom exactly?
MCbrian said:
Is this the same as the "Sleep of Death" (SOD)? In which the phone won't wake from sleep/suspend state and has to be soft-reset?
If not, what's the symptom exactly?
Click to expand...
Click to collapse
that's exactly what I'm talking about. I didn't know it was called the "sleep of death". I jusst have to softreset the phone all the time. The phone becomes just unuseable.
Ibster said:
that's exactly what I'm talking about. I didn't know it was called the "sleep of death". I jusst have to softreset the phone all the time. The phone becomes just unuseable.
Click to expand...
Click to collapse
i also experience it on my Tilt 2 AT&T unlocked, so i reverted back to Sense 2.1 Euro 1.86.401.0. any solution there, i bought mine from Negrielectronics USA.
Ibster said:
that's exactly what I'm talking about. I didn't know it was called the "sleep of death". I jusst have to softreset the phone all the time. The phone becomes just unuseable.
Click to expand...
Click to collapse
i also exprence it on my Tilt 2. is there any help out there
It's because chiefs have updated their XIP. Ask them to cook a rom for you with the old XIP from stock HTC WM6.5 Sense 2.1 rom.
Ach, that's just my theory based on my experience. I might be wrong, so keep that in mind.
I have a similar issue, but not exactly the sleep of death
A lot of times when I unlock the phone, Sense would not show up, only the taskbar and occasionally the bottom bar
Everything is responsive, the taskbar notification works, hardware buttons works, but not the sense part in the middle
This usually happens when I'm having an SMS conversation
I run this setup most of the time:
WM 6.5.x
Sense 2.5
HD mini lockscreen with Smartlock 2.0F or Lockdevice 1.6
Same here on the SMS black screen
ctbear said:
I have a similar issue, but not exactly the sleep of death
A lot of times when I unlock the phone, Sense would not show up, only the taskbar and occasionally the bottom bar
Everything is responsive, the taskbar notification works, hardware buttons works, but not the sense part in the middle
This usually happens when I'm having an SMS conversation
I run this setup most of the time:
WM 6.5.x
Sense 2.5
HD mini lockscreen with Smartlock 2.0F or Lockdevice 1.6
Click to expand...
Click to collapse
I just started having this problem with the newest Leo Cell Pro, I have not had it with any NRG or Deep Shinig ROMS though but I do like The cell pro details and the others are not without there faults. I like your screenshots and I can hardly wait for that new white theme to come out. I think it will make my phone so much better outdoors and enhance the Windroid look I am workin on.
Apical said:
I just started having this problem with the newest Leo Cell Pro, I have not had it with any NRG or Deep Shinig ROMS though but I do like The cell pro details and the others are not without there faults. I like your screenshots and I can hardly wait for that new white theme to come out. I think it will make my phone so much better outdoors and enhance the Windroid look I am workin on.
Click to expand...
Click to collapse
Yes....interesting that I've never had this issue on Energy's...my guess is he doesn't cook in the latest HTC SMS client which can be unstable at times
Are you talking about Elcondor's GTX theme? Yes that is a very awesome theme
I couldn't wait until 201x version comes out so I made my own Not as good as GTX but I'm half satisfied now
Apical said:
I just started having this problem with the newest Leo Cell Pro, I have not had it with any NRG or Deep Shinig ROMS though but I do like The cell pro details and the others are not without there faults. I like your screenshots and I can hardly wait for that new white theme to come out. I think it will make my phone so much better outdoors and enhance the Windroid look I am workin on.
Click to expand...
Click to collapse
like i mentioned in the the post#1 I had these problems with almost all recent (last two weeks) custom ROM releases, ROMs of different chefs. Because others or the majority of people don't have any problems with that I thought the reason must be hardware issues. yesterday I saw this thread http://forum.xda-developers.com/showthread.php?t=649191 opened by agent_47 where he provides a modified tool:
agent_47 said:
when u flash a rom, you are copying files onto the internal memory (like duh!) but if u repeatadly flash different roms, sometimes files from older version stays behind as when u flash a rom, you just copy and sometimes overwrite files without deleting the older ones. hence at times these older files may create bugs\instability. hardrest donot always fix it.so we use MTTY
Click to expand...
Click to collapse
Well I used it and have flashed to Sergio's Leo Cell Evo 6 and I can confirm that I haven't had any "sleep of death" issues, well still haven't and hope I won't have this "SOD" issue anymore. And when I tried this same ROM before I wasn't even able to make a proper configuration and set up the phone because the phone always froze or as soon the screen went off I wasn't able to activate it back without soft reset.
So maybe this is a solution and could help others who also are having this issue of "sleep of death".
Please if you try the tool from the mentioned agent_47's thread, let know us here because it will be very useful for the rest of the users to finally figure out "the dark side" of their phone and fix it.
Cheers, Ibster
Solution
I had this just recently. Funny side was that I installed an official new ROM from HTC which I just updated. Somehow the phone just didn't want to turn on and show the screen. So just like you guys said, hard-reset did the thing but just when the screen went off, same thing happened.
So what I did was wipe/clean or any other name. Practically did the installation of the rom again. Now, the device works normally and without any problems.
Maybe this happens because some old files of older ROMS sayed on the device itself and started making problems. Anyways, check this thread too, maybe it will explain something more: http://forum.xda-developers.com/showthread.php?t=649191
Or, final explanation. Our Rhodiums have soul inside their little chips and they just simply fu.k with us They tell us they're too tired of so many ROM changes.
I have also had this problem with my two latest official swedish roms (manilla 2.1 and 2.5) cant remember if I had it when I used 6.1. Now I use a cooked rom and still have the issue several times a week. The only thing I had done with my Rhodium before using cooked Rom was flashing hard spl for future use. If its not an inbuilt hardware/software problem from the beginning the only thing I can point at in my case is hard spl?
Originally Posted by agent_47
when u flash a rom, you are copying files onto the internal memory (like duh!) but if u repeatadly flash different roms, sometimes files from older version stays behind as when u flash a rom, you just copy and sometimes overwrite files without deleting the older ones. hence at times these older files may create bugs\instability. hardrest donot always fix it.so we use MTTY
Click to expand...
Click to collapse
back with my kaiser you always had to flash back to stock before going to a new ROM no matter what, for just this very reason...
could flashing back to stock be a 'best practice' that we as users should start doing to help with this issue?
I - have had some xperience with the issue in a few ROMS. Im a loyal flasher of Agent 47s masterpieces. And a month or so ago he had like 2 or 3 builds that had this issue. From what I remember he said that he thought it had to do with some sys evrybody was using to cook roms. and after her came out with this diagnosis and "fixed"(i dont know the technical part of what was fixed) this problem it has never happened since. But a good thing I would say to try is in Agents thread about 4 or so pages from the last page(maybe more or less) but close to the last page he posted a .zip file for this mitty fix. and you essentially flash this zip just like a rom then reflash which ever rom you had or a new one and ta da. Ive also heard of people reflashing a stock rom with results from doing so but from what Agent said is flashing a stock rom then back technicaly "shouldnt" do anything and to definately use mitty. But one of the other frequent valkyrie users that I chat with all the time Mcbrian who posted here on the first page has used the stock rom and did have whatever issue he had cured dont remember what that was tho.
UPDATE- Oh I guess that Agent has a thread for Tool29 so you dont have to search through his thread to find it.
I can confirm agent 47 method is working for me. I no longer have the sleep of death. But its only been half a day. I will report back in a few days.
aichemist said:
I can confirm agent 47 method is working for me. I no longer have the sleep of death. But its only been half a day. I will report back in a few days.
Click to expand...
Click to collapse
Great! I'm glad to hear your confirmation. I now on my side haven't had a sleep of death for three days on the ROM (Cell Leo V6) that previously, before I used the agent_47's tool, couldn't even start normally at all or had extremely many "sleeps of death". But I also noticed overall improvements even though the speed slows down but there are barely any freezes and stability is much better.
Cheers, Ibster
aichemist said:
I can confirm agent 47 method is working for me. I no longer have the sleep of death. But its only been half a day. I will report back in a few days.
Click to expand...
Click to collapse
I did tried agent 47 method at least three times this weekend. I did exactly what agent 47 instructed, flash Energy ROM 23547 with MaxManila = failed to initiated. Flash Tool29 again, reflash Energy ROM 23545 from MicroSD = Failed. Flash Athine OS XTreme = Worked, install MaxManila 3.0 on top of Athine OS Xtreme = Corrupted the manila display. Reflash stock ROM. Flash Deep Shining X.23544 = Worked. Flash Deep Shining X.23547 = Failed.
Look like I can get my phone to work but can't move on from now on! Any suggestion is greatly appreciated!
Thanks
kienkham said:
I did tried agent 47 method at least three times this weekend. I did exactly what agent 47 instructed, flash Energy ROM 23547 with MaxManila = failed to initiated. Flash Tool29 again, reflash Energy ROM 23545 from MicroSD = Failed. Flash Athine OS XTreme = Worked, install MaxManila 3.0 on top of Athine OS Xtreme = Corrupted the manila display. Reflash stock ROM. Flash Deep Shining X.23544 = Worked. Flash Deep Shining X.23547 = Failed.
Look like I can get my phone to work but can't move on from now on! Any suggestion is greatly appreciated!
Thanks
Click to expand...
Click to collapse
I'm not very clear about what you mean by failed. Do you mean you can't flash some of the ROMs or you get screens of death with them?
What I did was this: I took out the SD card. Ran the tool29 modified by agent_47 (see post 10 of this thread). After the tool finished cleaning all internal memory the phone went back on but got stuck in loading. I took the battery out of phone for few seconds and then put it back in. Then I connected the USB cable to the phone and started it in the bootloader mode by quickly pressing and releasing the switch button and then hitting the volume down. On the tricolor screen then it shows USB. Then I just flashed my ROM of choice normally with USB without need to flash from SD. I've done this several time with several ROMs without problems.
Ibster said:
I'm not very clear about what you mean by failed. Do you mean you can't flash some of the ROMs or you get screens of death with them?
What I did was this: I took out the SD card. Ran the tool29 modified by agent_47 (see post 10 of this thread). After the tool finished cleaning all internal memory the phone went back on but got stuck in loading. I took the battery out of phone for few seconds and then put it back in. Then I connected the USB cable to the phone and started it in the bootloader mode by quickly pressing and releasing the switch button and then hitting the volume down. On the tricolor screen then it shows USB. Then I just flashed my ROM of choice normally with USB without need to flash from SD. I've done this several time with several ROMs without problems.
Click to expand...
Click to collapse
Thanks for quick response. Yes. I did exactly what you spelled out in the message. i.e: Remove the memory card, Run Tool29, remove the battery, got into the bootloader mode, then flashed with USB connection. The phone went to the initial setup, I clicked the T-Mobile connection ....etc... then it restart - then stopped at "Launching HTC Sense...." This is = failed for me. i.e: Failed to clean the internal memory!
By the way, if the internal memory is cleaned, shouldn't the Start->Setting->Device Information->Software Information: Incoming Call & Outgoing Call reset to 0?
Thanks
kienkham said:
Thanks for quick response. Yes. I did exactly what you spelled out in the message. i.e: Remove the memory card, Run Tool29, remove the battery, got into the bootloader mode, then flashed with USB connection. The phone went to the initial setup, I clicked the T-Mobile connection ....etc... then it restart - then stopped at "Launching HTC Sense...." This is = failed for me. i.e: Failed to clean the internal memory!
By the way, if the internal memory is cleaned, shouldn't the Start->Setting->Device Information->Software Information: Incoming Call & Outgoing Call reset to 0?
Thanks
Click to expand...
Click to collapse
Your steps should be
1. Shutdown tp2..
2. Remove memory card( I also removed sim card).
3. Turn on tp2, connect through the computer through active sync.
4. Run task 29. Let it load flash, whatever it is doing until it actually reboots.
5. At this point, everything should be cleaned, you don't have a rom or radio anymore, so its blank, so you "pull battery out."
6. Put memory card/sim card back in. Flash radio through boot whatever menu. Soft reset it yourself. Pull battery out again.
7. Flash rom this time, and soft reset it again. Now rom should start setting up.
This shouldn't be rocket science.
ok first off i love the fresh roms so im not bashing.
does anyone else have an issue that seams to be directly related to flashing the new fresh 2.1.1 rom.
when im in a call and end it with the power button it restarts the phone.
is this because of what i think it is or something else.
i wiped everything when i flashed so i dont know what else it could be, in the mean time i guess i have to go back to fresh 1.1 sense i cant find a fresh 2.0d download link anymore and i deleted my nandroid and the 2.0d rom off my computer like an idiot. uneless someone could point me to a 2.0d link
shawnwojcik said:
ok first off i love the fresh roms so im not bashing.
does anyone else have an issue that seams to be directly related to flashing the new fresh 2.1.1 rom.
when im in a call and end it with the power button it restarts the phone.
is this because of what i think it is or something else.
i wiped everything when i flashed so i dont know what else it could be, in the mean time i guess i have to go back to fresh 1.1 sense i cant find a fresh 2.0d download link anymore and i deleted my nandroid and the 2.0d rom off my computer like an idiot. uneless someone could point me to a 2.0d link
Click to expand...
Click to collapse
probably should be in q&a or fresh's thread but here is a link all fresh's downloads are on geekfor.me should be at the bottom
http://geekfor.me/category/android21/page/2/
I found that the restarting issue on my end was linked to the battery stats and roation stats. After i wiped those, for some reason, i stopped restarting.
sdotcarlisle said:
probably should be in q&a or fresh's thread but here is a link all fresh's downloads are on geekfor.me should be at the bottom
http://geekfor.me/category/android21/page/2/
Click to expand...
Click to collapse
sorry i wasnt sure where to put it. sould i start a new thread in there or can a mod move this one?
Powers16 said:
I found that the restarting issue on my end was linked to the battery stats and roation stats. After i wiped those, for some reason, i stopped restarting.
Click to expand...
Click to collapse
Can you elaborate on this? How do you wipe these stats?
i had the same problem but it was on fresh and damage control, i figured out it was the app i was using to call people with...called quick connect...
it didn't happen if i dailed with the stock dialer or through people...
jasonevil said:
i had the same problem but it was on fresh and damage control, i figured out it was the app i was using to call people with...called quick connect...
it didn't happen if i dialed with the stock dialer or through people...
Click to expand...
Click to collapse
Alright I did everything mentioned, above. i wiped the battery and rotation stats in ra recovery i even re partitioned my sd card and did a wipe data/factory reset plus the ext and dalvik-cache. then re flashed fresh 2.1.1.
also i am not using any other dialer that i know of. just the one that comes backed in the rom.
so why am i still resetting randomly!!! it even did it when i was doing nothing at all not just in a call like before.
this is on two seperate sprint htc heros that this is happening to.
anyone please help!
shawnwojcik said:
Alright I did everything mentioned, above. i wiped the battery and rotation stats in ra recovery i even re partitioned my sd card and did a wipe data/factory reset plus the ext and dalvik-cache. then re flashed fresh 2.1.1.
also i am not using any other dialer that i know of. just the one that comes backed in the rom.
so why am i still resetting randomly!!! it even did it when i was doing nothing at all not just in a call like before.
this is on two seperate sprint htc heros that this is happening to.
anyone please help!
Click to expand...
Click to collapse
couple questions.
1. are you using any aggressive process killers, like the one found in spare parts?
2. what, exactly, do you mean by resetting? do you mean a quick 10 second restart of rosie, or a full on 1.5 minute reboot?
Nextelian said:
couple questions.
1. are you using any aggressive process killers, like the one found in spare parts?
2. what, exactly, do you mean by resetting? do you mean a quick 10 second restart of rosie, or a full on 1.5 minute reboot?
Click to expand...
Click to collapse
sorry i took so long to reply.
no process killers.
Im now able to replicate it restarting (not randomly) if i let the phone go to sleep by its self and sit for a minute when i hit the end button to wake it up nothing lights up like it should instead it does a full on 1.5 minute reboot every time.
on a separate thread someone suggested i try a different battery because whenever they put a different battery in it stopped resetting. (I was not able to try this yet because i don't have any spare batteries laying around)
I just find this hard to believe only a few people are having these problems and why no one seems to have a definitive answer.
This is kind of one of those bugs where I have to say it's something going on with your phone. Fresh Rom 2.1.1 has been downloaded over 4000 times. I restart mine constantly while testing things which means I am constantly duplicating your situation of restarting the phone, letting it sleep, and then turning it on via the power button, and I have never had this happen.
Please post a debug log of it happening and we'll see if we can figure out why your phone is doing it.
My sister had this issue even on stock 1.5. Rooted, added recovery still had it. Flashed 2.0d, still had it, went to recovery and wiped battery stats.
Haven't had it happen since. Now on 2.1.1 and all is well...go figure.
flipzmode said:
This is kind of one of those bugs where I have to say it's something going on with your phone. Fresh Rom 2.1.1 has been downloaded over 4000 times. I restart mine constantly while testing things which means I am constantly duplicating your situation of restarting the phone, letting it sleep, and then turning it on via the power button, and I have never had this happen.
Please post a debug log of it happening and we'll see if we can figure out why your phone is doing it.
Click to expand...
Click to collapse
thank you for helping flipz, sorry for thinking it was something to do with your rom (foot in mouth). I now believe it a hardware issue related to any 2.1 fw.
This has happened to me on 2 different phones. Mine and my friends. Mine restarted "randomly" once i wiped the battery and rotation stats and it fixed mine. My friends on the other hand i could not get to stop restarting for the life of me. So i was forced to switch back to a 1.5 fw rom.
Point being it will take me a few days to get back over there and put a 2.1 fw back on it and get a debug log off of it. for now i can try using his battery in my phone and see if i have any issues. im crossing my fingers in hope i will so we can buy a new battery and see if it goes away for him.
in the mean time i can post a debug log for my phone but it probably wont do any good
i will try to post the results of the battery swap later today.
again thanx flipz i am confident with your help we can resolve this.
ok i thought i attached a error log but i guess its too big, so ill try zipping it and attaching it.
hero
I noticed reinserting the root file helped me also make sure your not using otwidhet or super pc unless u have a rom for it i use fresh toast 2.1 no problems quickquickquick
REDSCARFACE said:
I noticed reinserting the root file helped me also make sure your not using otwidhet or super pc unless u have a rom for it i use fresh toast 2.1 no problems quickquickquick
Click to expand...
Click to collapse
I kind of a noob, what do you mean reinserting the root file? i thought the root was the main directory not a file.
Also i dont know what "otwidhet" or "super pc" are, im assuming im not using them if they didnt come with the rom. right?
whoops, i forgot to post the results of swapping my battery with my fiends to see if i could single out a bad bad battery.
i didnt have any luck making my phone reset itself with his battery. One of these days im going to buy a couple new batteries put on in my friends hero and flash fresh 2.1.2 on it. Im also going to try using different radios on a hunch from a different thread i read.
i dont mean to waste anyones time im just busy and messing with phone is something i cant devote alot of time to especially sense i put a 1.5 fw rom on my friends phone and he no longer has any issues.
thanks for the patients in helping me guys.
ok im at a loss. i really need your guys help.
I put a 2.1fw on my buddies phone. put my battery in his phone let it go to sleep by itself and hit the end button to wake it up and it still does a reset. now i guess im not sure if it s a full on reset but it takes about a minute to reset.
so i put his battery in my phone and let it go to sleep and het the end button to wake it up and it also reset, now i did not clear the battery stats either and now after one time i can not get my phone with his battery to self reset for the life of me...???
no matter what bettery i try his phone will not stop resetting.
im posting an error log from his phone i got off adb using
adb bugreport > errorlog.txt
is that what im suppose to do? please help i would have been just fine with the 1.5fw on his phone but there was an audio issue that on some calls the person on the other end could not hear him.
does anyone know if the flipz audio fix will work for that or is that not a good ides?
Here is his error log, i hope this is what im suppose to post.
if anyone has any ideas about the audio fix for the 1.5fw that would be awesome cause now i gotta go back to that becasue i cant leave his phone with porblems.
Could it be that it is just Sense restarting and not the whole phone. Try using Fresh 2.1.2 with LauncherPro and see if you still have the problems. Make sure that you are not using the vanilla launcher in 2.1.1 as I had several instances where it caused instability.
lineman78 said:
Could it be that it is just Sense restarting and not the whole phone. Try using Fresh 2.1.2 with LauncherPro and see if you still have the problems. Make sure that you are not using the vanilla launcher in 2.1.1 as I had several instances where it caused instability.
Click to expand...
Click to collapse
I dont think thats the issue, my phone now restarts itself abuot once a day and i am using launcher pro. i also have my friends battey in my phone. so i guess is could still be the battery.
Im still confused on what i have to do to get some help from the devs. i posted a error log like asked if i was suppse tp post something else could someone please tell me? this is getting extremely frustrating. am i the only one here???
please someone help.