Database Develop

Phone hangs in sleep mode

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

Nook will turn on by it self after 5 minutes or so

First I thought that I'm crazy but now I can confirm that my NC will boot on it's own after about 5 minutes after power OFF. I have to shut down 2nd time and than it will stay OFF. Any idea what's wrong ?
Thanks
(Yes I did confirm after first shut down that it's actually OFF since no buttons will respond)

Any weather Apps running? Many of them have an option to wakeup in order to update. Check your mail, twitter and facebook apps. It has to be something you installed, I have run every update, tried all the froyo images and both Honeycomb releases and I have not seen that.

To expand on what gedster wrote, it seems kind of crazy and out there but what about any devices on your network that might send Wake on Lan requests? What if something on your network had located your NOOKcolor. I don't even know why a eReader Tablet would have a function for Wake on Lan but it's just another crazy avenue to jog down.

I do have weather app installed but I find it hard to believe that it can wake up OS that is not in standby but completely off. WIFI is also not enabled before shutdown.

Looks like the problem is there only if I used market, if market is not used it will shut down fine and it will not boot on its own.

lifeisfun said:
Looks like the problem is there only if I used market, if market is not used it will shut down fine and it will not boot on its own.
Click to expand...
Click to collapse
Seems that's unlikely if you're the only one having the issue, I'd keep digging if I were you.

Looks like you're right I can't replicate the problem every time
The timing when it will boot also varies 5, 15 and even 35 minutes.
Don't know what to do, it's hard to imagine how it can boot on it's own from
complete power off state

I can't believe I'm the only one with this problem

lifeisfun said:
I can't believe I'm the only one with this problem
Click to expand...
Click to collapse
I just posted a thread about this issue for me less than an hour ago! Funny, no one replied to mine: http://forum.xda-developers.com/showthread.php?t=940713. It was pretty long...guess I should've added a TL;DR.
It happens to me on any (or no) power source. Timing varies like yours as well. I'm going to pull my weather app based on the above recommendation, and I will try your Market theory out. Knowing someone else has this issue makes me hopeful that we can find something that we have in common as the culprit.
I did download the newest Honeycomb image yesterday and I'm going to put that SD card in and see if I can get it to turn itself back on on a Market-less, user App-less build. If successful I'll Titanium my 1.1 apps and remove everything non-system, then slowly add until I get this figured out. Keep me posted if you figure something out, I'll be sure to do the same!
In case it matters I bought mine about a week ago and the serial number starts with 20046.
EDIT: Testing with Honeycomb SD now so if that's the case here it should just stay off. I booted into Honeycomb at 9CST and turned it off at 9:01. I'll give it a couple of hours.

I used to have this same problem. I would randomly find my 1.0.1 auto-nootered 950mhz rom nook on, when I knew I had turned it off. interesting part is, this problem completely solved itself after I flashed my emmc with the custom nookie 5.9 img. so it must be an eclair issue and not a hardware issue

woot1524 said:
I used to have this same problem. I would randomly find my 1.0.1 auto-nootered 950mhz rom nook on, when I knew I had turned it off. interesting part is, this problem completely solved itself after I flashed my emmc with the custom nookie 5.9 img. so it must be an eclair issue and not a hardware issue
Click to expand...
Click to collapse
Really? I've been putting that off because I don't like the idea of not having Clockwork Recovery. I understand there are ways to do the same things using IOMonster's things but I'd really rather just have Clockwork Recovery working. Unless there's a way to get it going that I missed?

Yup, I've been having this issue as well. I really want to flash NF but I want hardware video acceleration.

oscillot said:
Really? I've been putting that off because I don't like the idea of not having Clockwork Recovery. I understand there are ways to do the same things using IOMonster's things but I'd really rather just have Clockwork Recovery working. Unless there's a way to get it going that I missed?
Click to expand...
Click to collapse
you are correct that clockwork does not work with froyo. however the bootable sd card that you would burn automatically starts up clockwork first. you can run a backup and restore, as far as i know, without having to reflash froyo. on a personal note, froyo still has some issues but overall I'm exteremly pleased so far. i really just wanted to get rid of all of the b&n stuff (mainly the status bar) along with any possible way of them pushing an update to break root. I would recommend it, but CM 7 with gingerbread will probably be out sooner rather than later.

woot1524 said:
you are correct that clockwork does not work with froyo. however the bootable sd card that you would burn automatically starts up clockwork first. you can run a backup and restore, as far as i know, without having to reflash froyo. on a personal note, froyo still has some issues but overall I'm exteremly pleased so far. i really just wanted to get rid of all of the b&n stuff (mainly the status bar) along with any possible way of them pushing an update to break root. I would recommend it, but CM 7 with gingerbread will probably be out sooner rather than later.
Click to expand...
Click to collapse
Which I guess brings us back to, why is Eclair doing this, and why does it seem to be limited to lifeisfun and myself?

I'm glad I'm no longer special
My serial # is 200503 .....
Removing all application that I have installed didn't help.
Only 100% way to shut down is to let it boot and immediately shut down.

unknown.soul said:
Yup, I've been having this issue as well. I really want to flash NF but I want hardware video acceleration.
Click to expand...
Click to collapse
Now that I understand the power of this things SD slot and that CWR can be run off of an SD, I can totally live with that. Hardware Video isn't a must for me yet, so I may take the plunge tonight after work...BTW, what are people's favorite video apps? I have been playing with VLC stream and convert, which works somewhat with my media server's samba shares. I have the share mounted to a directory on the sdcard since many apps look there exclusively.
More on topic, I couldn't get SD Honeycomb to start itself on its own. I tried booting then shutting down. 2 hrs of nothing 15mins light activity then shutting down. 2 more hours of nothing. About an hour of heavy use, seeing what could be installed, sideloading, testing, editing things like build.prop and rebooting often and trying to get swype working (don't think it's supposed to, but that's "heavy use" for me.) Powered down. Went to bed. Still not on this morning. This looks indeed to be an issue with the B&N stock Eclair.

Mine doesn't turn itself on with no interaction at all, but will turn on every time when you plug in the charger or cable hooked to USB port in computer.
I can turn it off once it is already plugged in and it will stay off, but remove and replug the charger and it is on again.
Strange.

Well, strange that only two or three of us noticed this strange problem.

Yeah, started for me after 1.1 update. Turned it off last night, tonight it was on with 40% battery! I think its 1.1 related, this didn't happen with 1.0.1 ...

I'm sure there's a condition that's causing or exasperating this issue, something common to us all. But at this point since I don't use the Nook as a video player (I actually bought it to read books, but I use Aldiko and the open epub format) I will likely flash Nookie to the eMMC and call it a day. Honestly can't wait to get a clean notification bar on this thing anyway.

[Q] Problems with Nookie Froyo and CM7

like namely, neither one will boot.
Grabed the Nookie Froyo boot image, wrote it onto a card (8Gig AData Class 6 card) with my linux box then watched as whole lot of nothing happened.
Saw a "Loading..." screen for a bit then "ANDROID.." and it stops there.
Somewhat similar problem with CM7. The installer version never could finish. Froze just past the mkfs the first time, second time got past the extract process, third time it said it made it and to restart. Never made it past that and actually booted.
Found a pre-done CM7 image, just sat at the logo screen for a long time before I shut it off. (like ~15 minutes)
The honeycomb preview image I found also didn't work...
I've tried both ones I have avaliable right now. (they're both identical from a different (failed) project involving a PSP and a Mem Stick Pro Duo adapter)
Technically I do have a 4Gig Class 4 in my MP3 player but i'd rather avoid using it. (it's near full right now and i'd have to copy everything off of it)
Right now i'm just wondering what's going on?

ok, just tried the Kingston 4gb class 4 card
Used the win32 disk imager program to write the nookie froyo image to the sd card.
Works fine, if a bit sluggish (class 4 card, ~15MB/sec read, ~5-6 writes, what do I expect here)
so i'll make an assumption that the Adata cards aren't suitable for use? Really sucks if this is true, was hoping to avoid spending any more money on this.
Now my only problem is that SoftKeys is misbehaving "Unable to execute as root"
Should I just tough it out on 2.1 until the "official" 2.2 or CM7 comes out? (heard something about how sleep is broken)
Sorta sucks a little as there's a 2.2 only app I rather wanted to run.

Fnord12 said:
ok, just tried the Kingston 4gb class 4 card
Used the win32 disk imager program to write the nookie froyo image to the sd card.
Works fine, if a bit sluggish (class 4 card, ~15MB/sec read, ~5-6 writes, what do I expect here)
so i'll make an assumption that the Adata cards aren't suitable for use? Really sucks if this is true, was hoping to avoid spending any more money on this.
Now my only problem is that SoftKeys is misbehaving "Unable to execute as root"
Should I just tough it out on 2.1 until the "official" 2.2 or CM7 comes out? (heard something about how sleep is broken)
Sorta sucks a little as there's a 2.2 only app I rather wanted to run.
Click to expand...
Click to collapse
Is softkeys the only app that cant get root privileges? I guess you could try to fix permisions in rom manager, it wont hurt anything

johnmagoo said:
Is softkeys the only app that cant get root privileges? I guess you could try to fix permisions in rom manager, it wont hurt anything
Click to expand...
Click to collapse
I didn't play around with it much given it's somewhat sluggishness. I did see the superuser prompt for softkeys but it apparently didn't work. Not sure what you mean by "rom manager" though?
Am getting ready to try out CM7 RC4 though. Wondering what that's like. Launcher Pro on 2.1 is nice-ish but it's clearly made for a phone given the wide spacing between buttons on the NC's screen.

Fnord12 said:
I didn't play around with it much given it's somewhat sluggishness. I did see the superuser prompt for softkeys but it apparently didn't work. Not sure what you mean by "rom manager" though?
Am getting ready to try out CM7 RC4 though. Wondering what that's like. Launcher Pro on 2.1 is nice-ish but it's clearly made for a phone given the wide spacing between buttons on the NC's screen.
Click to expand...
Click to collapse
Rom Manager is in settings, its part of CWM for flashing roms and stuff.
I am personally running Nookie Comb with no problems. For me it runs super smooth, wireless does not loop, and all my apps work just fine. I think I will probably switch to CM7 once the actual release is out, I am just having a really hard time switching to it now because Nookie Comb is working flawlessly for me.

johnmagoo said:
Rom Manager is in settings, its part of CWM for flashing roms and stuff.
I am personally running Nookie Comb with no problems. For me it runs super smooth, wireless does not loop, and all my apps work just fine. I think I will probably switch to CM7 once the actual release is out, I am just having a really hard time switching to it now because Nookie Comb is working flawlessly for me.
Click to expand...
Click to collapse
Well, so far CM7 is running better off the card than Nookie Froyo did.
app downloads are slow as hell though, no clue why.
once CM7 is out and if the odd wireless issue is solved then I may install it to the internal memory.

Time to fully boot off SD card with CM7

Hi there, I recently installed CM7 onto my SD card and was wondering if the time it takes to fully boot up is normal? My rough counting indicates that it takes approximately 20 seconds from when I press the power button to get to the CM7 splash screen, then another 30 seconds to get to my "desktop". I am using a Sanddisk 8gb class 4 card. The OS when running seems pretty quick and applications seem responsive. My Nook is a refurbished unit.
thx.

That's about right. It's not much different on eMMC.
Rodney

Sounds about the norm here too.

Sounds way fast to me actually. I'm pretty certain that mine takes quite a bit more time than that to boot, the CM7 splash screen is up forever.

i just switched from emmc to flash card and its about the same for both...whats funny is my wireless runs better off the flash card...

sure would love to know what benefits folks still see worth the hassle of booting from SD.
Not being an ass....i just really dont understand it.

TainT said:
sure would love to know what benefits folks still see worth the hassle of booting from SD.
Not being an ass....i just really dont understand it.
Click to expand...
Click to collapse
Since performance is almost the same, if you need warranty work you can just pop the card out and send it in to B&N, but if your device no longer boots or has some other major problem and you send it in and they see a custom ROM on it, they will not give you warranty coverage.
At least that's ONE reason...

TainT said:
sure would love to know what benefits folks still see worth the hassle of booting from SD.
Not being an ass....i just really dont understand it.
Click to expand...
Click to collapse
Personally I liked the way the stock B&N software worked for reading books better than the Nook app. So I can see wanting the flexibility of being able to use the stock Nook when I was reading a book, then being able to pop in an SD card and use it like a tablet when I wanted to do other things.
Seems like kind of a pain though.

darien87 said:
Personally I liked the way the stock B&N software worked for reading books better than the Nook app. So I can see wanting the flexibility of being able to use the stock Nook when I was reading a book, then being able to pop in an SD card and use it like a tablet when I wanted to do other things.
Seems like kind of a pain though.
Click to expand...
Click to collapse
Agreed I actually wanted to use some of the BN features, books reading is better and reading of magazines in color rocks. It functions very as it was originally intended to be a "reader". But I like to be able to use it as a tablet when I want.

I have only run from SD card but I played with my son's that is flashed to eMMC and build for build, I can't tell any difference so I just stick with SD card.

Timed mine...
hokudog said:
Hi there, I recently installed CM7 onto my SD card and was wondering if the time it takes to fully boot up is normal? My rough counting indicates that it takes approximately 20 seconds from when I press the power button to get to the CM7 splash screen, then another 30 seconds to get to my "desktop". I am using a Sanddisk 8gb class 4 card. The OS when running seems pretty quick and applications seem responsive. My Nook is a refurbished unit.
thx.
Click to expand...
Click to collapse
From power button push to when the CM7 rotating circle is centered on screen was 39 seconds. Desktop appeared at 1:03. A few more seconds for everything to 'settle' (fancy widget gets its skin, superuser ok's nook tweaks, etc).
On a new Sandisk 16gb class 4.

So far I think CM7 on SD would be my choice for running Android. Reviews are positive about it, applicable solution for noob like me.

I've a chance to run both CM7 off uSD and eMMC.
Here's my take:
+ Boot off uSD
1. simpler procedure (good)
2. avoid "void warranty" (good)
3. want the original NOOKcolor = remove the uSD, want fancy CM7 = insert uSD, want fancy Honeycomb = insert uSD, want fancy bla bla bla = insert usD
4. seems slower than the eMMC version
5. if having Kingston or Transcend (even with class 6), there are too many FC's errors
+ Root and run from eMMC
1. have to do more procedure (such format /data / system /cache)
2. B&N doesn't like it if rooted. There are ways to restore stock ROM those, again, more steps
3. Want original NC? do a restore procedure. Want to try Honeycomb? repeat installing procedure, ....
4. Seems faster
5. Virtually eliminate all FC's errors unless it's a real software bug.
6. Still some issues, at least in my case such Gallery doesn't work if no external uSD (FAT32) plugged in. Why? Why requires an external card? Turn ON USB storage has to go through more steps, my case, I have to unmount the eMMC's /media storage first then plug the usb cable in, then mount the /media for it to work connecting PC.

Best of both worlds
Very much a noob here. I bought my nook as an early retirement present. I originally had a Velocity Cruz but wanted to do more with it than it was capable of. Started reading threads on this site and BN site and after a week or two decided to make a dual bootable sd card running CM7. Everything went smooth but instead of the 15 min to create this card like I read on posts here it took me 4 to 5 hrs. Ok so I had a few issues!!!!! Loved it for the next couple of weeks; then while checking things out one night after I officially retired I was in Rom manager. Big MISTAKE! Saw there was an update to the CM7 I was using. Thought ok I'll update and low and behold I ended up updating internally not to the SD card. It was really nice rooted internally but after a week I decided to put stock operating system back on. Created that bootable card and went back to stock. Bought a 16 gb card made a new dual boot card with the same OS that I had inadvertantly rooted internally too. For all of you techies out there it was a lot quicker this time. I'm one happy camper now. I have Aldiko reader on the card and Calibre on my computer with plugins for taking drm off my books so husband and I can both read them. If I can do all this anyone can. I feel I have the best of both worlds now.

votinh said:
+ Boot off uSD
3. want the original NOOKcolor = remove the uSD, want fancy CM7 = insert uSD,
Click to expand...
Click to collapse
Depending on the ROM, you shouldn't need to remove the uSD to load to stock. For example, with CM7, you should be able to just hold N while it's booting and it will go to a boot menu, from which you can choose stock/recovery/sd/etc. Or, if that doesn't work, you can usually use a different uboot file.

Creating the SD card to run CM7 was very easy with all the how-to's up here and around the net. The performance is close to the same as internal memory. The best part is I have my whole OS in a tiny little SD card, which I can remove for security reasons or a lost or damaged Nook. Just pop it into any Nook and away you go.

TainT said:
sure would love to know what benefits folks still see worth the hassle of booting from SD.
Not being an ass....i just really dont understand it.
Click to expand...
Click to collapse
Warranty issues for one - but mostly there's no speed difference between SD and EMMC. It's actually *less* hassle - because you can fark around with an SD card all you want and *never* risk bricking your NC. The SD card sits in there and is no different in speed or boot up process - it just boots and runs.

I'm running racks' dual boot phiremod/hc and boot for phiremod seems slightly faster than hc. Maybe a few seconds faster than the 50 seconds it takes you, but seems like you're in the ball park.

[Q] Upgrade Nexus One to the Prime or just keep it?

I bought the N1 on the day it came out and it's still going fine. Well I must provide soem caveats here so say it's not the original unit. I have gone through 2 RMA's with HTC and 2 paid for repairs for the power button. The last time the power button failed, the repair only lasted abouit 6 weeks and when I complained they sent me a refurb rather than fix it.
For me the only issues for the N1 are
- flaky touch sometimes (go to suspend and back usually fixes it)
- constantly running out of system memory and all apps I can move are moved to the SD card.
So it's either get a new phone or root the N1. Given that the phone works for what I want rooting and a new firmware might be the answer.
So given that I have never rooted a phone or installed new firmware, can people suggest the most appropriate firmware I should be looking at and the easiest way to get there. The phone is currently on 2.3.6 (OTA).
There is so much conflicting information out there it's hard to know what the best route is.
Thanks

lchiu7 said:
I bought the N1 on the day it came out and it's still going fine. Well I must provide soem caveats here so say it's not the original unit. I have gone through 2 RMA's with HTC and 2 paid for repairs for the power button. The last time the power button failed, the repair only lasted abouit 6 weeks and when I complained they sent me a refurb rather than fix it.
For me the only issues for the N1 are
- flaky touch sometimes (go to suspend and back usually fixes it)
- constantly running out of system memory and all apps I can move are moved to the SD card.
So it's either get a new phone or root the N1. Given that the phone works for what I want rooting and a new firmware might be the answer.
So given that I have never rooted a phone or installed new firmware, can people suggest the most appropriate firmware I should be looking at and the easiest way to get there. The phone is currently on 2.3.6 (OTA).
There is so much conflicting information out there it's hard to know what the best route is.
Thanks
Click to expand...
Click to collapse
I have a rooted N1 that I bought in February of 2010, a month after they became available. It was rooted when I bought it on eBay and running one of the CM ROMs. I don't know how to root a phone, sorry.
I DO know how to load ROMs and have variously updated and modded the phone myself. I have been fortunate in that my power button has never failed, but while I was running a series of OTA ROMs (ROMs based on the pure Android released from Google) I noticed that the latest ones disabled the trackball wake feature, meaning that the power button was the only way to wake the phone. I had gotten used to trackball wake with the first CyanogenMod ROM, and so once I learned that the power button was a weak spot, I decided that a CM ROM or a modded AOSP ROM was the only option.
As there were some issues with CM ROMs that took months to work out (see WONK), I went with an AOSP ROM that I found here http://forum.xda-developers.com/showthread.php?t=1121595 . It's now a dead thread, but the links to the 3.1 version of the ROM is still there. I use the apps2SD version of the 3.1 ROM.
There are several more ROMs that are more recent, but this one is the best one I have ever found. You will need to root your phone and install a custom recovery (like AmonRA or ClockworkMod) to use it, but I have found that everything works well and it is extremely stable. I have over 70 apps on my phone with over 80MB of internal memory still available.
The only problem I have ever had is an intermittent battery drain, which I was able to fix by wiping the cache files (Dalvik and regular caches). The custom recoveries have the ability to do this. Apparently any corruption of the cache files causes excessive battery drain, but wiping them (which causes the phone to rebuild them on the next boot - a 4 minute process!) gives you fresh cache files and fixes the problem.
If you are willing to learn how to root your phone and install a custom recovery, I can recommend that ROM. Once the first part is done, loading a custom ROM is as easy as putting the zipped ROM file on your SD card, getting to the bootloader and telling it to install the zip.

Well just so you know, rooting or installing any ROM will never stop the touch input problems. Its my main dislike about the N1. Apps2SD would solve your storage issues though and all the extra little perks of rooting just sweeten the deal.
Replacing a phone is expensive and just not necessary for the N1 yet. May as well root in my opinion. CM7.1 is now perfectly stable, include trackball wake, can support A2SD as far as I know and has some nice extras too.
As well as that it shouldn't be TOO much longer until we get a decent ICS ROM.
Hope that helps you.

addam360 said:
Well just so you know, rooting or installing any ROM will never stop the touch input problems. Its my main dislike about the N1. Apps2SD would solve your storage issues though and all the extra little perks of rooting just sweeten the deal.
Replacing a phone is expensive and just not necessary for the N1 yet. May as well root in my opinion. CM7.1 is now perfectly stable, include trackball wake, can support A2SD as far as I know and has some nice extras too.
As well as that it shouldn't be TOO much longer until we get a decent ICS ROM.
Hope that helps you.
Click to expand...
Click to collapse
Thanks. I never expected the new ROM to fix the touch input problems. That is a fundamental hardware issue.
I was thinking along the same lines regarding ICS. It's gone AOS now and I now see somebody has built a port for the N1 already. So if I wait a bit if I choose to install some custom firmware, if the reports suggest ICS runs fine on the N1 (to confirm that Google didn't release it because there was a performance issue with the N1 and ICS) then that's the route I will take. In for a penny, in for a pound I guess!

lchiu7 said:
(to confirm that Google didn't release it because there was a performance issue with the N1 and ICS)
Click to expand...
Click to collapse
The issue is not because of performance, its the system partition size is not enough... Gosh! Did u know Galaxy Nexus's system dump is 600MB+