I have rooted my device around 2 weeks ago and everything has been fine until 2 days ago. The E-reader basically just froze and wasn't responding to anything. I attached the usb cable from my computer and that seemed to help boot up the device. On start up it literally had 0% charge. The device would still work and when fully charged I could take out the cable and use it as normal. However, the device simply refuses to shut down and generally it is much more unstable. Initially, it did say the googleframework app crashed or something like that, so I decided to uninstall that and the android market in the hopes of resolving this issue for good.

Unfortunately, the same issue has occurred today. It froze, i used the cable to help boot it up and there is 0% charge. I think it is important to know that ever since the initial crash, there has been an orange light that flashes on and off (near the power button).

What does this mean? And should I recover my device? (I am a little unsure about recovering as I haven't done much reading on it, so what exactly does that do? Or is there another solution?).

Some more details: I have installed 2 games from the market, I used a mod version of the homescreen (the one that changes recently added to recently read), I also installed an alternative homescreen (This one: http://blog.the-ebook-reader.com/201...reader-prs-t1/) But the weird thing is that the reader was working perfectly for around 2 weeks, so I really cannot pinpoint the cause.

I have rooted my device around 2 weeks ago and everything has been fine until 2 days ago. The E-reader basically just froze and wasn't responding to anything. I attached the usb cable from my computer and that seemed to help boot up the device. On start up it literally had 0% charge. The device would still work and when fully charged I could take out the cable and use it as normal. However, the device simply refuses to shut down and generally it is much more unstable. Initially, it did say the googleframework app crashed or something like that, so I decided to uninstall that and the android market in the hopes of resolving this issue for good.

Unfortunately, the same issue has occurred today. It froze, i used the cable to help boot it up and there is 0% charge. I think it is important to know that ever since the initial crash, there has been an orange light that flashes on and off (near the power button).

What does this mean? And should I recover my device? (I am a little unsure about recovering as I haven't done much reading on it, so what exactly does that do? Or is there another solution?).
Some more details: I have installed 2 games from the market, I used a mod version of the homescreen (the one that changes recently added to recently read), I also installed an alternative homescreen (This one: http://blog.the-ebook-reader.com/201...reader-prs-t1/) But the weird thing is that the reader was working perfectly for around 2 weeks, so I really cannot pinpoint the cause.
If more detail is needed please ask.hanks.

Sounds like the perfect "sling it back at the retailer you bougfht it from for a replacement, nothing else acceptable - unless you've bricked it so bad by now your warranty's done for .........

The device is rooted and has new software installed, so I don't buy this 'device is a lemon and should be returned' advice. I don't think the OP does either. In terms of advice, I would say look for processes that take power (simple to say). It could be something using the WiFi, or the sound (can plug in the headphones to check), or the CPU. I don't know a lot about rooting the T1, but if you used adb in the process, then you should be able to connect to the device using 'adb shell', and do some snooping from the command-line on the T1. Use 'ps -a -x -l' to see what processes exist, and if any are currently running. Look at how much time each has spent executing to see if any one of them is hogging hours of CPU time. I've also read reports here in the past where crud on the screen causes the IR touch interface to waste time reacting to and ignoring the events. The 'dmesg' command shows you the system logs, and can often be useful for finding out low-level problems.

The device is rooted and has new software installed, so I don't buy this 'device is a lemon and should be returned' advice. I don't think the OP does either. In terms of advice, I would say look for processes that take power (simple to say). It could be something using the WiFi, or the sound (can plug in the headphones to check), or the CPU. I don't know a lot about rooting the T1, but if you used adb in the process, then you should be able to connect to the device using 'adb shell', and do some snooping from the command-line on the T1. Use 'ps -a -x -l' to see what processes exist, and if any are currently running. Look at how much time each has spent executing to see if any one of them is hogging hours of CPU time. I've also read reports here in the past where crud on the screen causes the IR touch interface to waste time reacting to and ignoring the events. The 'dmesg' command shows you the system logs, and can often be useful for finding out low-level problems.

Thanks for your help. I had already unrooted the device so I won't be able to use the system logs. But since it is unrooted there shouldn't be any apps 'running in the background' so to speak.

Unfortunately the problem still persists.

The only thing I haven't tried yet is a factory reset, which I'm hoping will do the trick.