I cannot be the only one with this problem, please help me out so i can enjoy my nexus one fully. I just got this about two weeks ago.
The problem is my nexus keeps rebooting randomly, and it does not matter which rom is installed.
My phone is rooted with 2.1-update1 firmware, baseband is 32.26.00.24u_4.04.00.03_2 (ORIGINAL RADIO THAT CAME WITH THE PHONE), build number is passion-user 2.1-update1 ERE27 24178 release-keys. Plus i always have about 180mb ram free and 90mb of internal space free. Also i am using APPS2SD with a class 6 card.
I have noticed it happening when using a specific app for a while, example using navigation, or playing a game, or listening music. Example where it does not do it is if i am checking my text messages or email, because that is something i check quickly then get out of the app.
Also i am not sure if i should start a new thread but it does apply here, if i use the car dock my phone will reboot within less than 2 minutes of using an app compared to if i use the phone by itself it will be about 5 minutes.
Here is what i have tried so far, I installed the three common roms for the nexus, enom-cyanogen-modaco (always doing a wipe before trying new one). I replaced the battery. I reformated multiple times the sdcard using RA_amons tool.
Now when i got my phone it already had the latest radio, so i left that alone. Is this why i get random reboots? should i flash cyanogen radio?
The phone does not reboot by itself on stand by mode, only when using apps.
PLEASE HELP SO I CAN ENJOY MY NEW PHONE, THANK YOU.
ifactory said:
Also i am using APPS2SD with a class 6 card.
Click to expand...
Click to collapse
Try turning APPS2SD off.
Good idea, i did not think about that. But also in all the threads on xda, i have not found anybody mentioning getting reboots because of apps2sd. The reason i say this is because i really need to have this on, i ran out of space when i first got my phone and started installing apps.
A bad SD card might cause that, regardless of whether the Apps2SD partition or the vfat partition is affected. Might be more problematic with the Apps2SD partition, though. Try another SD card.
it happens to me using slacker on any rom... so i moved slacker to the internal memory.
remember apps2sd isn't technically stable. while it works for most apps, there are some apps that just aren't compatible.
robert-qfh said:
A bad SD card might cause that, regardless of whether the Apps2SD partition or the vfat partition is affected. Might be more problematic with the Apps2SD partition, though. Try another SD card.
Click to expand...
Click to collapse
I just re-installed modaco rom, on a new 4 gig sd-card, and same problems
antoniouslj said:
it happens to me using slacker on any rom... so i moved slacker to the internal memory.
remember apps2sd isn't technically stable. while it works for most apps, there are some apps that just aren't compatible.
Click to expand...
Click to collapse
I am a big user of slacker radio, and is one of my software i notice making my phone reboot.
How do you move just a single app back to the internal memory even though you have apps2sd?
Just to try to narrow this issue more, i have notice something odd.
when i turn on my gps and use google maps or copilot, then try to multitask and use any app that plays sounds or music it will make my phone reboot.
Also i have noticed with the car dock (without having gps turned on, if i try playing music using any app it reboots the phone. I have seen other people mentioning this, can someone confirm using the 3.5mm headphone jack while the phone is in the car dock will reboot the phone.
So, I figured with Android getting ported quite nicely and is fairly well along, we should start working on getting it flashed directly to NAND. Eliminate Windows Mobile all together. So here are my notes. All this stuff combined in some order and sense will make it able to flash NAND with Android. But for some reason I just can't piece it all together and make the puzzle fit. I am posting this in hopes that someone with enough skill can take the information and build what is needed.
Working Tinboot - This is what the core of NAND android flashing is.
NBH for installation (Examples) - Needed to install android. Flash nbh, install android, reboot
To test all of this we need the RESUMEADDR of the HD2. Then we can pass RESUMEINTOBOOT to haret. Then we can check if there is enough low-level hardware support to even boot Android yet. This can be gotten by using haretconsole. But I have yet been able to get the RESUMEADDR because of issues with my computer.
Thanks goes to dzo for pointing me in the right direction for all of this.
They still need WinMo to boot to initialize some of the hardware... that's why most winmo phones that have android ports can't flash to nand yet... and the couple that do have flashable roms took a long time to develop.
What's the big deal about flashing it to nand anyways? Do you really want to take away your phones ability to run 2 os's to make it just another android phone that doesn't run it as well as a native android phone? Flashing to nand doesn't improve performance much, if any. Some people think that haret emulates android and thatg winmo is still running in the background, but that's not true. HaRET shuts down the windows kernel and starts the linux kernel. The only speed increase that you would see is the difference in data transfer speed from the nand or memory cards to ram, which would probably only be noticeable during certain tasks, but probably even then wouldn't make much of a difference.
I would prefer to have a dual-booting powerphone than to make it just another android phone that doesn't run as well as native android phones. If I wanted just android on my phone, I'd get an android phone.
i agree but...
zarathustrax said:
They still need WinMo to boot to initialize some of the hardware... that's why most winmo phones that have android ports can't flash to nand yet... and the couple that do have flashable roms took a long time to develop.
What's the big deal about flashing it to nand anyways? Do you really want to take away your phones ability to run 2 os's to make it just another android phone that doesn't run it as well as a native android phone? Flashing to nand doesn't improve performance much, if any. Some people think that haret emulates android and thatg winmo is still running in the background, but that's not true. HaRET shuts down the windows kernel and starts the linux kernel. The only speed increase that you would see is the difference in data transfer speed from the nand or memory cards to ram, which would probably only be noticeable during certain tasks, but probably even then wouldn't make much of a difference.
I would prefer to have a dual-booting powerphone than to make it just another android phone that doesn't run as well as native android phones. If I wanted just android on my phone, I'd get an android phone.
Click to expand...
Click to collapse
i agree with you, but this guy is asking for help do do a certain task.
I second you on your idea but there are people that would prefer to have a win mo. phone running android even if it runs slower or worst because some people just dont like wm. software.
By the way i cant help you jmztaylor because i just dont know...
zarathustrax said:
They still need WinMo to boot to initialize some of the hardware... that's why most winmo phones that have android ports can't flash to nand yet... and the couple that do have flashable roms took a long time to develop.
What's the big deal about flashing it to nand anyways? Do you really want to take away your phones ability to run 2 os's to make it just another android phone that doesn't run it as well as a native android phone? Flashing to nand doesn't improve performance much, if any. Some people think that haret emulates android and thatg winmo is still running in the background, but that's not true. HaRET shuts down the windows kernel and starts the linux kernel. The only speed increase that you would see is the difference in data transfer speed from the nand or memory cards to ram, which would probably only be noticeable during certain tasks, but probably even then wouldn't make much of a difference.
I would prefer to have a dual-booting powerphone than to make it just another android phone that doesn't run as well as native android phones. If I wanted just android on my phone, I'd get an android phone.
Click to expand...
Click to collapse
well running android from sd card creates higher battery consumption. Am I right? this is a good argument.
jojo_angelov said:
well running android from sd card creates higher battery consumption. Am I right? this is a good argument.
Click to expand...
Click to collapse
Yeah, that is true. Reading about the nand ports for other winmo devices show that battery is improved, but it still isn't no where near as good as winmo is with batteries. Power management is one of the issues that almost all android ports have.
At this point, i don't believe nand flashing is possible for the hd2... like i said, they need winmo to initialize many things. Also, once it is possible to flash nand, it probably won't have as much working hardware as the haret version until they get drivers that initialize all that hardware. If you look at some of the other nand flashable ports on other phones, things like wifi, bluetooth, camera, gps, etc don't work while they work when you use the haret bootable version. We're still a long way away from booting from nand... at least a version functional enough to want to get rid of winmo.
I'm really curious as to what peoples reason is to want a nand flashable version so bad.... I've heard people say that winmo is still running in the background with haret, but thats just not true. You generally have a much more functional android when run of storage card than the nand flashable ports are. There may be a small increase in battery life and small increase in speed when flashed to nand, but you will lose a lot of functions until they find ways to initialize the hardware without winmo. And from what i've seen with the hd2 ports so far, I don't think we will have any issues with speed like they did with other devices, so I don't see nand being needed to increase speed.
cmon people, lets support the motion.. remember we are dealing with one of the best htc-winmo devices here, the one of a kind htc-hd2..
for me the point is not "what is the need of doing this", the point is "it can be done "
maybe one shouldnt rush to start flashing android on hd2, thats why alpha and beta versions are made, where one understands the risks but does it anyways for the fun experience.. n remember this is just the beginning of android on hd2, i think there is room for a whole lot of improvement
zarathustrax said:
Yeah, that is true. Reading about the nand ports for other winmo devices show that battery is improved, but it still isn't no where near as good as winmo is with batteries. Power management is one of the issues that almost all android ports have.
At this point, i don't believe nand flashing is possible for the hd2... like i said, they need winmo to initialize many things. Also, once it is possible to flash nand, it probably won't have as much working hardware as the haret version until they get drivers that initialize all that hardware. If you look at some of the other nand flashable ports on other phones, things like wifi, bluetooth, camera, gps, etc don't work while they work when you use the haret bootable version. We're still a long way away from booting from nand... at least a version functional enough to want to get rid of winmo.
I'm really curious as to what peoples reason is to want a nand flashable version so bad.... I've heard people say that winmo is still running in the background with haret, but thats just not true. You generally have a much more functional android when run of storage card than the nand flashable ports are. There may be a small increase in battery life and small increase in speed when flashed to nand, but you will lose a lot of functions until they find ways to initialize the hardware without winmo. And from what i've seen with the hd2 ports so far, I don't think we will have any issues with speed like they did with other devices, so I don't see nand being needed to increase speed.
Click to expand...
Click to collapse
why dont we just have it running from internal memory without flashing? it would solve the speed and battery problems and we would still get to keep winmo . or is there a reason this cannot happen?
Well, knowing that android builds (system and user data) take about 530MB, it would be a tad hard to stuff in the HD2's 512MB, of which about 300 are used by Winmo...
Maybe on the 1GB TMOUS though....
kilrah said:
Well, knowing that android builds (system and user data) take about 530MB, it would be a tad hard to stuff in the HD2's 512MB, of which about 300 are used by Winmo...
Maybe on the 1GB TMOUS though....
Click to expand...
Click to collapse
but most of us have the 512 mb version
i would be interested in getting android stored on the device memory (Not a ROM flash). NRGZ28 released a winmo version that is very small (50 or 60MB) leaving me with 800Mb+ of internal storage. what must be changed to get HaRET to look in internal storage for the files and store information there?
This should be a very good discussion..btw ive been running off of sd card for a while now and battery consumption isn't that bad at all
As far as I see it, a major problem is for any non TMOUS HD2 owners an SD card will always be mandatory. Even if you are able to fit the whole system into the half sized NAND, there wouldn't be much room left for anything else.
And even on the TMOUS, it would be good to put Android and the Apps on internal memory, and have everything else on the storage card, like pics and such.
Main reasons I see for doing this, is once it's working a version that doesn't need to use WinMo can boot faster, and might be able to solve some issues eventually, like not needing a specific file in WinMo or specific ROM just to get calls working correctly.
As well, It gets annoying when even with bootloader it takes longer to boot back up, and I still sometimes get a voicemail or text message while HaRET is loading, and I have to reset, boot windows mobile, remove CLRCAD, reboot, and check the voicemail and texts. If I don't clear it in WinMo, sometimes I get a voicemail message notification every time I boot android even if I don't have any voicemail.
cavemaneca said:
as far as i see it, a major problem is for any non tmous hd2 owners an sd card will always be mandatory. Even if you are able to fit the whole system into the half sized nand, there wouldn't be much room left for anything else.
And even on the tmous, it would be good to put android and the apps on internal memory, and have everything else on the storage card, like pics and such.
Main reasons i see for doing this, is once it's working a version that doesn't need to use winmo can boot faster, and might be able to solve some issues eventually, like not needing a specific file in winmo or specific rom just to get calls working correctly.
As well, it gets annoying when even with bootloader it takes longer to boot back up, and i still sometimes get a voicemail or text message while haret is loading, and i have to reset, boot windows mobile, remove clrcad, reboot, and check the voicemail and texts. If i don't clear it in winmo, sometimes i get a voicemail message notification every time i boot android even if i don't have any voicemail.
Click to expand...
Click to collapse
agreed..then maybe after studying the 1gig version they can find a solution for the 512 version
Battery life isnt great on current builds but it is usable. Much of the issue is due to it being an a sd card. Once they put it on nand, battery life will be even better. As good as winmo? You never know until you try.
I dont get why people are all too ready to rain on someones parade. I say, if there is a possibility of making android boot on this thing, why not try it? WinMo is dying, some of want to jump ship and take our hd2s with us.
It seems that getting nand to run is a priority to devs. Check out the first 7/23 post at http://robsbay.co.uk/
These guys have been making a port much faster than others have anticipated. According to doom-sayers, we shouldnt have been at this point for another few months at least. Im willing to bet this thing will be booting on its own and running efficiently well before the doom-sayers would have expected us to even have this thing running on a sd card.
zarathustrax said:
What's the big deal about flashing it to nand anyways?
Click to expand...
Click to collapse
- Reliability
- Speed
- Battery life.
- Access to memory card as a removable device while Android booted.
Even a class 10 card can't compare to the speed of the internal nand.
Pagnell said:
- Reliability
- Speed
- Battery life.
- Access to memory card as a removable device while Android booted.
Even a class 10 card can't compare to the speed of the internal nand.
Click to expand...
Click to collapse
I completely agree. As others have noted, the main issue is initializing hardware. As an interim step to 100% Android, why not build an extremely slim WinMo with Android cooked into the NAND ROM.
I'm using desire v5 with latest Cotulla zImage it's pretty fast even off of a class 2 microSD. I really think my HD2 would be just as fast as my wife's EVO if the same thing were on the NAND.
nand boot tmous
any tmous user actually copy all of the files over to their phone's memory and try and boot haret? Or would this be detrimental to the life your WM phone?
I am a T-Mobile HD2 user and I think flashing from NAND would have many benefits. Lets do it up.
I am a T-Mobile HD2 use and this is great because we can boot both winmo and android from the nand, which is insane. All the non US users want to shut this down, because they are left out.
Leader2light said:
I am a T-Mobile HD2 use and this is great because we can boot both winmo and android from the nand, which is insane. All the non US users want to shut this down, because they are left out.
Click to expand...
Click to collapse
so have you booted it from the nand with your hd2?
I've been having quite a big problem recently. Something has been sucking internal memory like crazy. I've flashed several ROMs and still have the same problem of the low memory alert.
I flashed another ROM today and had 144MB of internal memory at noon. Now, without downloading any apps or doing anything major, I now have 133MBs for internal storage. I've currently been using a2sd because iGo is a total space hog and its better than the native gps app imho (doesnt seem to lose GPS signal every few minutes)
The other issue I'm having is the GPS. Its pretty much crucial to me right now because I've been going from Thousand Oaks to LA and everywhere in between and have only found two ROMs that I dont have GPS problems with. Those: EE4.0 and Aloysius
However, both of those have been giving me the low memory warning constantly and I cannot recover space no matter what I delete. I tried deleting iGo (a huge app) and it only accounted for a few MB (the full app is over 20)
I'm quite confused and have never had this problem before.
I've searched the web and it seems theres no solution available at the moment and Froyo takes care of it.
tokyoglow said:
I've been having quite a big problem recently. Something has been sucking internal memory like crazy. I've flashed several ROMs and still have the same problem of the low memory alert.
I flashed another ROM today and had 144MB of internal memory at noon. Now, without downloading any apps or doing anything major, I now have 133MBs for internal storage. I've currently been using a2sd because iGo is a total space hog and its better than the native gps app imho (doesnt seem to lose GPS signal every few minutes)
The other issue I'm having is the GPS. Its pretty much crucial to me right now because I've been going from Thousand Oaks to LA and everywhere in between and have only found two ROMs that I dont have GPS problems with. Those: EE4.0 and Aloysius
However, both of those have been giving me the low memory warning constantly and I cannot recover space no matter what I delete. I tried deleting iGo (a huge app) and it only accounted for a few MB (the full app is over 20)
I'm quite confused and have never had this problem before.
I've searched the web and it seems theres no solution available at the moment and Froyo takes care of it.
Click to expand...
Click to collapse
Well, about the internal memory storage, it could be your cache. Try downloading an app called CacheMate; I'm not sure about the free version, but the paid version has a 'Power Clear' option that clears ALL the cache on your phone. It usually clears about 8-14MB of cache everyday.
Also, 11MB really isn't really a big deal at all, as it will function just as well with 133MB as it will with 144MB.
Well, I got my HD2 to run Android okay, I guess. It does run better then the Vibrant. . .
But, my battery life sucks and I have no file transfer while running Android due the damn OS being on the SD card.
The WMO has all kinds off little glitches. . . . The battery life is half decent. But, there are no apps and it feels like Windows.
Anyone out there with a HD2 running at 100%? And if there is, it is hard to believe.
Uh...yeah? Mine runs pretty damn great with a custom WinMo ROM applied(Energy)...haven't soft reset in weeks. And there are applications for Windows...you just have to think outside the market
Well, the Wmo runs way smoother over time. . .
I am also running a Energy ROM. . . It's still has some glitchiness to it though.
samson_420 said:
Well, I got my HD2 to run Android okay, I guess. It does run better then the Vibrant. . .
But, my battery life sucks and I have no file transfer while running Android due the damn OS being on the SD card.
The WMO has all kinds off little glitches. . . . The battery life is half decent. But, there are no apps and it feels like Windows.
Anyone out there with a HD2 running at 100%? And if there is, it is hard to believe.
Click to expand...
Click to collapse
Mine runs awesome on the stock 3.14 ROM. It also runs awesome with a stripped 3.14 ROM and the Bluetopia 1.0.4 Android Build. I am getting about 12 hours of heavy use and more than a day if I turn off my data when I'm not using it. These phones are what you make them. You just have to try a lot of things out.
Out of the box with the stock rom they weren't awesome. Touch response was great, but it froze a lot. Then they updated the rom and it had ****ty touch response but didn't freeze. So people cooked ROMs with 2.10 touch drivers. Then they came out with 3.14 and everything worked.
On top of this, there are a ton of stable Winmo cooked ROMS to choose from.
And as of recent, there are flawless Android builds out there that run perfect with 3.14 stock ROM and lot of cooked ROM's as well. I prefer a stripped down 3.14 ROM for Android only use.
If Tmobile ever comes out with an Android native phone that is as nice as my HD2, I'll pick it up. Mostly because I know that WinMO 6.5 is dying and because the Android market is WAY bigger with better programs and utilities. I would end up keeping my HD2 and running WinMO only on it. I would also continue to play with it. I love to get my nerd on and the HD2 is the perfect phone for tinkering. But, I don't know when that will be. Not losing my screen size or the build quality/hardware awesomeness and I haven't seen anything comparable yet.
I don't mind rebooting into Windows to transfer to my SD card, but I'm also fine with shutting it down and pulling the card out and using an adapter. I guess it would be easier if you could just do it through Android but this isn't an Android native phone and it seems acceptable to me.
In the beginning my leo was a worthless pos, somehow over time it has begun to operate much smoother. A few downloads from this and a few other sites have straightened out some flaws
Be careful posting "issues" with your leo, you'll find that some loose cannon members on forums become extremely unstable and will begin kung fu flaming you until you never want to see another smartphone ever again.
then tear into your mom.
kick your dog/cat
etc.
Lol. . . . Flaming I can take. . .
Well, a few ROM's later I seem to have my HD2 running even better.
The file transfer is weak but like stated above, it is what it is.
A stripped down ROM really seems to best way to go for running Android.
I was also having major battery issues and today I finally found out why. I was using HandCent SMS. What it did was, it would wake up the phone and stay stuck at a 60 mA draw.
Removed the app and installed GO SMS, which has less then 1/3rd of the features of HandCent, but it does not hang up my phone.
So, it is getting better with time.
As far as hardware the HD2 is only second to the HD7(which just looks amazing).
But, the software is what makes the HD7 a 4.3" display having paperweight.
What are you guys talking about ? You can transfer files while booted in Android even if it is in the SD card.. Pull out your SD card while Android is on and it will still work.. I can transfer files fine.. Just change the mode from charge to disk mode..
MarlinFF said:
What are you guys talking about ? You can transfer files while booted in Android even if it is in the SD card.. Pull out your SD card while Android is on and it will still work.. I can transfer files fine.. Just change the mode from charge to disk mode..
Click to expand...
Click to collapse
I feel like a dumb ass. I didn't even notice the disk drive option. Thanks.
Is it safe to do since everything is installed on the card to copy to it while the OS is running? I assumed it didn't work and would not be a good idea. I didn't try to transfer anything, but it does work. I guess since the OS is actually running off the internal memory after you run Haret that it's cool. I just never really thought that much about it.
crisisinthecity said:
I feel like a dumb ass. I didn't even notice the disk drive option. Thanks.
Is it safe to do since everything is installed on the card to copy to it while the OS is running? I assumed it didn't work and would not be a good idea. I didn't try to transfer anything, but it does work. I guess since the OS is actually running off the internal memory after you run Haret that it's cool. I just never really thought that much about it.
Click to expand...
Click to collapse
My HD2 runs great. I use Core Cell Evo v4.1 on the WinMo side and use Darkstone Froyo Sense v3.2 on the Android side...works great for me.
I transfer files quite a lot and no problems.
If you eject your sd card it will continue to work but, when you install sd card again most things won't work and, then will lock up (I tried that and I have to pull battery, then reboot).
I did notice if you leave it hooked to your PC (disk drive) and don't use the default ringtones, they will default to them in Disk Drive mode.
My HD2 runs so well using BlueTopia that it has replaced my G2 as my primary.device I carry two phones, 1 for work and 1 for personal use.
-------------------------------------
Sent via the XDA Tapatalk App
Greetings all
I have a HD2 running Android. The ROM is DL DesireZ v2 internal. software number 1.72.466.4
I am at an understanding there is a new version out but the flash I have atm is 100% working besides one thing....the phone memory.
When I first flashed it I had loads of phone memory, I think it was like what, 150mb?
But I downloaded lots of apps, even used the Apps2Sd app to save space on the phone memory.
So after a while, I ran out of phone memory, how? I have no idea.
I have deleted all the apps I had and I still have <10mb space on my phone memory and I can not find ANYTHING on the phone memory taking up this space.
Anyone else have this issue?
My gf is going nuts at me over this, she said she may as well have the Win 6.5 back on it, since she had no apps anyways
Cheers,
Gib
yea i have the same problem..
all my apps are installed on my sd card or my ext3 partition.
still i have very little phone memory available.
somehow it looks like the phone is saving the app on the phone but then moving it to the sd card without removing it on the phone memory and causing data loss?
also when updating an app i just lose a lot of internal memory..
how is it possible that there are a lot of people with this problem (i searched the forums) and nobody know an answer to this?