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

FINAL ADB SOLUTION: For those who couldn't get ADB with Recovery

1. Install HTC Sync 2.0.25 onto your PC (it came with your phone) (maybe the custom driver works but I haven't tried it yet)
2. Power off your device
3. Remove the battery
4. Plug in your USB cable
5. Insert your SDcard (any kind, it doesn't matter the type, i have 6 different cards and class associations in my possesion and have rooted all of my co-workers DI's today using all 6 cards for proof of concept, 9 phone total [Everyone wanted Wireless Tether)
6. Insert your battery
7. Hold Vol. Down button + Power button
8. Start and loop (you can start this before now if you wish, just has to be before entering recovery)
9. After the phone scans the sdcard choose "Recovery" and press the Power button.
*10. SOLUTION: As soon as the white screen appears just casually (don't be a speed demon) click IN & OUT your sdcard and continue to do so (keep clicking it) when the black screen with triangle appears. You will be listening for the last windows chime that identifies the USB has registered. But, you want to stop with your last sdcard click IN just before the last windows chime is sounded through your PC speakers. You might need to do this a couple times just to get familiar with the timing of the windows sounds on your computer system. Those phones that don't have to do this and was rooted first have a much earlier timing of when the Exploit is active.
11. Now go get Rooted using the steps on the first page of this post.

dymanese said:
1. Install HTC Sync 2.0.25 onto your PC (it came with your phone) (maybe the custom driver works but I haven't tried it yet)
2. Power off your device
3. Remove the battery
4. Plug in your USB cable
5. Insert your SDcard (any kind, it doesn't matter the type, i have 6 different cards and class associations in my possesion and have rooted all of my co-workers DI's today using all 6 cards for proof of concept, 9 phone total [Everyone wanted Wireless Tether)
6. Insert your battery
7. Hold Vol. Down button + Power button
8. After the phone boots up and scans the sdcard choose "Recovery" and press the Power button.
*9. SOLUTION: As soon as the white screen appears just casually (don't be a speed demon) click IN & OUT your sdcard and continue to do so (keep clicking it) when the black screen with triangle appears. You will be listening for the last windows chime that identifies the USB has registered. But, you want to stop with your last sdcard click IN just before the last windows chime is sounded through your PC speakers. You might need to do this a couple times just to get familiar with the timing of the windows sounds on your computer system. Those phones that don't have to do this and was rooted first have a much earlier timing of when the Exploit is active.
10. Now go get Rooted using the steps on the first page of this post.
Click to expand...
Click to collapse
is this while running loop.bat? it didn't say

vzw said:
is this while running loop.bat? it didn't say
Click to expand...
Click to collapse
yes run the loop.
I tried this for about an hour with no result btw.

Worked for me

Seriously , this is the EXACT same steps that has been posted numerous times before. When you speak of a Solution as something Final it SHOULD NOT involve trial and error steps that require timing or just *luck*.
What a waste of a post and thanks for im sure getting peoples hopes up.

Seriously , this is the EXACT same steps that has been posted numerous times before. When you speak of a Solution as something Final it should involve trial and error steps that require timing or just *luck*.
What a waste of a post and thanks for im sure getting peoples hopes up.
Click to expand...
Click to collapse
Yes you run the loop but not necessary to run in a loop. Yes it is about timing and similar posts have been made but I think I've written it with more detail.
These precise steps worked with the exact timing on 8 DIFFERENT phones yesterday. If its not working for you then perhaps you don't know how to follow directions well.
-------------------------------------
Sent via the XDA Tapatalk App

Ouch.... Burned by last post
dymanese said:
Yes you run the loop but not necessary to run in a loop. Yes it is about timing and similar posts have been made but I think I've written it with more detail.
These precise steps worked with the exact timing on 8 DIFFERENT phones yesterday. If its not working for you then perhaps you don't know how to follow directions well.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
You know, just because it worked for you doesn't mean it will for others....
I CAN follow directions well, and I can't get it reproduced. (though it may be because I'm already rooted?)

Just keep clicking that card in your own intervals after the white screen and you will get it. With my own proof I can contest that there is a BIG misconception that this is only achieved during the White screen. NOT TRUE!!!
Those steps are what I experimented with trying to root my own DI and it worked. I was not convinced I'd get it to work on other phones since It's been days and countless hours trying to get mine to connect to ADB in Recovery. So, one of my co-workers let me try it on his phone with his different card type, and one co-worker after the other, success! The root I did on MY phone was with an sdcard I bought that came with some of the phones (SanDisk 2gb). I didn't get a free card from VZW. I had FASTER success with this card of all 6 cards I've rooted with. It took longer with the other cards, class 4 PNY, and off-brand class 6 cards. With the 2gb SandDisk class 2 it works on the first try for every phone I've tried.
Did you have HTC Sync installed as your active driver, I really can't say if the customer driver works as I haven't tried it myself? My laptop is the latest Sony VAIO F-series with Core i7 with Windows Ultimate x64. In Device Manager, while in HBOOT my phone only showed up as Android 1.0 and as HTC Bootloader.

dreamersipaq said:
You know, just because it worked for you doesn't mean it will for others....
I CAN follow directions well, and I can't get it reproduced. (though it may be because I'm already rooted?)
Click to expand...
Click to collapse
No, and if you want to be in tune with the FINAL SOLUTION, your chakras must be aligned with Lady DI and her mysterious ways. I recommend balancing her on your head while you sleep for a fortnight, and then comes the sacrificial goat!
Seriously OP, I followed the last CARD CLICK prophet's advice and now my card mushes into lock--the DI just ain't built for the kind of abuse frenzied insert/ejection creates. I respect that you're good at what you do, but as others have found, teaching timing with http very difficult, at best.

I installed root by using an old laptop with XP... I had one point installed the HTC drivers. In this case, I had unistalled the HTC drivers and the HTC sync driver. Now I only used the SDK usb.inf drivers with the modified line for HTC incredible.

rynosaur said:
No, and if you want to be in tune with the FINAL SOLUTION, your chakras must be aligned with Lady DI and her mysterious ways. I recommend balancing her on your head while you sleep for a fortnight, and then comes the sacrificial goat!
Seriously OP, I followed the last CARD CLICK prophet's advice and now my card mushes into lock--the DI just ain't built for the kind of abuse frenzied insert/ejection creates. I respect that you're good at what you do, but as others have found, teaching timing with http very difficult, at best.
Click to expand...
Click to collapse
Oh CHAKRAS! Formula 51 reference FTW!!!! B.E.S.T. M.O.V.I.E E.V.A.R.R.R.R.!.!.!.!

dreamersipaq said:
Oh CHAKRAS! Formula 51 reference FTW!!!! B.E.S.T. M.O.V.I.E E.V.A.R.R.R.R.!.!.!.!
Click to expand...
Click to collapse
Believe it or not, I haven't seen it yet--just added it to my Netflix queue tho.
OP, can you get us a dmesg of you hitting the timing with your method? I want to see how it reacts to mounting/checking the sdcard devices more than once in recovery boot. I think good dmesg logs would help us all figure out what's going on here . . . .

From what I've seen
rynosaur said:
Believe it or not, I haven't seen it yet--just added it to my Netflix queue tho.
OP, can you get us a dmesg of you hitting the timing with your method? I want to see how it reacts to mounting/checking the sdcard devices more than once in recovery boot. I think good dmesg logs would help us all figure out what's going on here . . . .
Click to expand...
Click to collapse
It depends on how quick you insert/remove. It takes anywhere form a 1/2 second to 1 second between the initial "Slot changed from 0 -> 1" to where the card is actually mounted. If you click too fast, you never that that "mount" so you'll never get root, since it seems like the "mount" is actually causing the error we need. If you slow down your insert/remove to a slower pace, you'll get numerous mounts of the sd card. This might increase your chances of getting root because you're mounting multple times, but it makes the mounts more random then precise timing, and unfortunately, to get our error that we need, the read needs to happen at a percise time. You've seen the dmesg that was posted by 'mite.

THANK YOU OP! Worked for me :-D
My other 2 incredibles had worked consistently, but this one took your process to get.

dreamersipaq said:
You've seen the dmesg that was posted by 'mite.
Click to expand...
Click to collapse
Yeah, and I'm still wondering why he was so 'elliptical' about explaining what was going on there. I still can't figure out if it's the mount process or the mounted card that triggers the adbd event, or if a delayed sdcard process simply pushes adbd start into the recovery window, when commands such as 'adb shell' can be received by daemon for a split/few seconds. Would be nice to hear his explanation of what system events are occurring outside of what is logged in dmesg. The OP says mount event can complete in recovery/black screen, you say sdcard mount must complete before black screen, that's a big diff.
I wonder if it's possible to create a host-side script that reads dmesg, watches for card mount and triggers 'adb shell' at a much faster rate than a simple win shell 'loop'. That would be killer, and would eliminate all need for card insertion timing, IMO.

rynosaur said:
Yeah, and I'm still wondering why he was so 'elliptical' about explaining what was going on there. I still can't figure out if it's the mount process or the mounted card that triggers the adbd event, or if a delayed sdcard process simply pushes adbd start into the recovery window, when commands such as 'adb shell' can be received by daemon for a split/few seconds. Would be nice to hear his explanation of what system events are occurring outside of what is logged in dmesg. The OP says mount event can complete in recovery/black screen, you say sdcard mount must complete before black screen, that's a big diff.
I wonder if it's possible to create a host-side script that reads dmesg, watches for card mount and triggers 'adb shell' at a much faster rate than a simple win shell 'loop'. That would be killer, and would eliminate all need for card insertion timing, IMO.
Click to expand...
Click to collapse
I don't think so. Don't have the devices in front of me right now, but I believe that the phone is disconnected from the PC (that first do - do) before our window of opportunity, which means the pc is not communicating with the phone at all. So if (big if) I am correct, nothing local to the PC can be done to initiate anything AT THE TIME that we need it to.

dreamersipaq said:
I don't think so. Don't have the devices in front of me right now, but I believe that the phone is disconnected from the PC (that first do - do) before our window of opportunity, which means the pc is not communicating with the phone at all. So if (big if) I am correct, nothing local to the PC can be done to initiate anything AT THE TIME that we need it to.
Click to expand...
Click to collapse
Dat's kinda what I thought

I'll try to get you guys a dmesg as soon as possible. I'm at work right now and I'm responsible for alot of servers at a law firm in DC. (never get any free time it seems) I'm been trying to check in with you guys as often as I can. It's brutal today because we have Maintenance tonight throughout the morning.

This is what I found by myself to work for me after trying for 3 days originally.

Say what you will about the OP, but the timing is key and his post did help me out. I've tried tons of cards, every method out there and had no luck, until now. So for what's it's worth, this post was much appreciated.

Need help with Incubus26Jc's Super FroYo 2.2, install issues

Hey everyone, I'm trying to upgrade from Myn's Warm Eclair [BETA 1] (I know, I know, lol I should check here more often...) to Incubus26Jc's Super FroYo 2.2 [Deodexed] [RLS10] [7/8/10] (the download link that says "DOWNLOAD RLS10" in large orange font underneath the "What Doesn't Work" secton on his 1st post.
I'm doing what I usually do to install android, which is:
download the .nbh (which is voguimg-240x320-froyo-08-07-10.nbh)
rename it to RUU_signed.nbh
place it in the ROMUpdateUtility
add the ANDBOOT folder to the root of my SD card
placing the androidinstall.tar file inside
holding the power and camera buttons to boot into the RGB 'usb' screen
then running the ROMUpdateUtility to install it and boot up the linux
in linux I hold down the center button to get the the install menu
then install both system and data to the NAND (since I don't have partitions on my 8 gig SD
Here's the problem that I'm running into, once it formats and goes to install it says allot of random stuff then goes through about 15 lines of code saying "no such file or directory exists"
I was wondering if I'm doing something wrong or using the wrong files together.
Any help would be greatly appreciated!

this happens to me all the time. the question you need to ask is "is the device getting to the desktop?" and "is the operating system fully loading to a usable state?"
in my experience answering either of these questions 'yes' puts you in a good position. there have been reports of boot sequence taking up to 20 mins. personally, i can make it to desktop in about 10 mins every time.
hope it helps.

sometimes you just need to format the sd card to fat32 again then try reinstalling after putting the files back on the card of course. if the sdcard is formatted wrong then it wont be able to read the directory and will give you that error

Darkstarrdp said:
Here's the problem that I'm running into, once it formats and goes to install it says allot of random stuff then goes through about 15 lines of code saying "no such file or directory exists"
I was wondering if I'm doing something wrong or using the wrong files together.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
It's not a problem - this is the permission setting - ignore the messages
Just let it get back to the install screen, and then hit Quit or soft-reset device.
Then wait about 10-15 minutes for first boot and go through startup setup
Reboots are quicker, maybe anywhere from 2-4 minutes.
I overclocked my vogue to 496mhz with no issues & I guess some people hit 510mhz safely.

Just to add, Ive been running at 520 for a month now without noticing any major adverse effects...Sorry to chime in

I second wisconsinated's note -- I had this problem last night. I reformatted the card as FAT32 and things went as expected after. Not sure why they tanked in the first place, but I suppose that's not important, right?

ill third that. a reformat of my microsd did the trick.

i think it says on most of the eclair builds that you should just run the installer then let it sit for a good 10 15 minutes and you should be good to go.

ericbond said:
i think it says on most of the eclair builds that you should just run the installer then let it sit for a good 10 15 minutes and you should be good to go.
Click to expand...
Click to collapse
oddly enough, with an experimental operating system, one needs to exercise extreme patience at times.
glad its all in order for you now

Thanks guys, I got it to finally install after the third try, I guess it was just having hiccups trying to install. Everything's good now.... OS installation side at least.
Now I have a different problem... my touch sensitivity is kinda out of whack.
it's like touch screen is dead half the time, on my stock sprint ROM it will work perfectly, but, on the newer builds of android (2.1's) the touch screen won't react most of the time. Like, I'll have to hit the screen over and over a few time's before it'll finally pick it up. I've used the calibration tool to get it all lined up, but when I go to test the calibration I notice that it will only recognize my touch between the .50's and .60's range, it's like it's locked into that area and won't pick up anything else. I also drew a circle around my screen about 10 times once I got it to recognize my pressure and out of the 10 circles 4 or 5 drew a line directly to the bottom right corner of the screen then it would bounce back to where I was actually pressing. It makes it really hard to get anything done on a touch phone if the screen doesn't want to pick up lol.
Like I say, when I move back to my original sprint rom everything is fine and dandy using WinMo 6.1 but who wants to use 6.1 now adays
So, is there any way to fix my touch sensitivity? or is my screen just crapping out on me?

Digitizer going bad
Ok, I've been looking around on the forums, it seems my digitizer is going bad, this is my second vogue (the first one's power button broke). I've only had this vogue for about 8 months so far and I really don't want to pay another $100 dollars to get Asuiron to send me another replacement. So I was wondering if there is any way to salvage my phone, maybe a screen pressure threshold setting within android to help the sensitivity issue?
Is there any way to fix this? Any help would be greatly appreciated! =)

Darkstarrdp said:
Ok, I've been looking around on the forums, it seems my digitizer is going bad, this is my second vogue (the first one's power button broke). I've only had this vogue for about 8 months so far and I really don't want to pay another $100 dollars to get Asuiron to send me another replacement. So I was wondering if there is any way to salvage my phone, maybe a screen pressure threshold setting within android to help the sensitivity issue?
Is there any way to fix this? Any help would be greatly appreciated! =)
Click to expand...
Click to collapse
I am not sure this can help, are you familiar with terminal?
open terminal or adb and type
Code:
cat /sys/module/tsc2003/parameters/sensitivity
to see current setting, it usually is 8192
write it down and change the param to lower value like 3072
Code:
echo "3072" > /sys/module/tsc2003/parameters/sensitivity
check the result
Code:
cat /sys/module/tsc2003/parameters/sensitivity
it should now display 3072
HTH

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.