Originally Posted by MontAlbert

do you have a nandroid backup you can revert to , which is before this charging bug came in?

Yes, after taking an unusually long time to restore (and, for what it's worth, a whole lot of dots more on the status 'bar' while doing so), no charging, no animation, battery level stuck at 13%.

Originally Posted by MontAlbert

do you have a nandroid backup you can revert to , which is before this charging bug came in?

yeah i do but its still was fked. i've done everything i could think of besides changing kernels backwards and forwards really. nandroid backup, wipe multiple times, charge with usb, AC you name it. Just wait for cyanogens verdict and see if it works for others. only then if my battery hasn't arrived we can arrange a meet up.

Thanks really though. Dont really meet nice and willing strangers to help you fix your device
i just hope you aint out there to get my phone XD

Originally Posted by thenoo

Yes, after taking an unusually long time to restore (and, for what it's worth, a whole lot of dots more on the status 'bar' while doing so), no charging, no animation, battery level stuck at 13%.

try not to let your battery die. You'll need to be able to flash it once a fix is out. Dont let it die and be in my situation.

Originally Posted by babijoee

try not to let your battery die. You'll need to be able to flash it once a fix is out. Dont let it die and be in my situation.

Thanks, man, I know, and I'm very aware of the impending danger whenever I try flashing something on it (like Modaco's ROM, which didn't solve it either, but we know that much ) or a backup/restore cycle. My Nexus One's either on AC/USB power or shut off, right now.

cool. i just hope theres a fix soon
though we may need some of the people who can still operate give some info and logs to cyanogen. It should help speed things up.

Originally Posted by maddie

my nexus one gets random reboots after flashing the memory hack .29 kernel and with JIT disabled.

i'm getting confused.. don't get any error outputs in logcat

Me too. After a few minutes testing (only in boot, not flashed), the phone rebooted itself. Wireless didn't turn on either, but it maybe because the kernel was not flashed. Is there a way to see what happened just before the reboot?

Been using the new rom and .32 kernel/Wififix plus the memoryfix.

Works nicely when running without the jit and on fast.

Downsides;
Batterytime.
Can´t connect to my WIN 7 PC anymore - won´t see my N1 - yeah but only as a massstorage? Have had it all working fine with the USB drivers - but BAM after the .32 kernel update it aint working nomore...

Originally Posted by flak0

I tried top and could not reproduce; however if u have advanced task manager under services it shows Bluetooth service could this b the same thing

I have same error, with ethomer 1,4 and stock rom. It seem the memory fix have some issues to fix

Do you have a battery widget running? Try uninstalling that, reboot and see if that helps.

Originally Posted by babijoee

cool. i just hope theres a fix soon
though we may need some of the people who can still operate give some info and logs to cyanogen. It should help speed things up.

Originally Posted by InFlicT666

and me.

Phone not seen by PC (Win7 x64) before kernel update adb was working fine.

Same issue