Database Info

CM 4.2.11.1 Camera and Home Screen issues

Firstly I'd like to thank PSYCHO13OI on the #cyanogenmod IRC channel for spending quite a bit of his time helping me out. I thought I might just throw my problem out there.
I received my new HTC Magic a few days ago, but spent quite a few days prior researching different ROMs.
I've got a 32A that came from 3 Australia.
Firstly, a summary of what I originally did.
After receiving my phone and playing around with the original ROM;
1) I fastbooted into: recovery-RA-sapphire-v1.5.2H.img.
2) I wiped data, and wiped a non-existant ext partition.
3) I partitioned the SD card using 32MB swap-size and a 256MB ext partition. Further I used ext2 -> ext3.
4) Loaded and flashed the following in order:
- DRC83_base_defanged
- update-cm-4.2.11.1-signed
5) Rebooted.
After 30 minutes of the original boot splash screen, I took the battery out (I couldn't, and still can't, figure out how to hard power off) and re-fastbooted into the recovery image.
6) I reperformed steps 1-4, this time actually flashing the kernel port: bc-4.2.11.1-ebi1-signed. I also repartitioned the SD card using a swap size of 256MB and ext partition of 1024MB and went from ext2 -> ext3 -> ext4.
7) Rebooted again.
8) When I get to the "Touch the android to begin." screen, I got this error message:
Sorry!
The process com.android.
phone has stopped unexpectedly. Please try again.
My only option is to force close which still allows me to touch the android and proceed as normal. Otherwise, everything seemed fine and dandy.
A few days later I decided to try using the Camera and Camcorder apps. This caused a reboot. This did not happen on the original ROM.
After the reboot I noticed that the home screen hung after trying to swipe my home screen. This eventually lead to the error message (after 10 seconds or so):
Sorry!
Activity Home(in process
android.process.acore) is not
responding.
I was prompted with the option to either force close or wait. Choosing either will restore complete functionality in 20-30 seconds.
Now this happens after every reboot (and I'm uncertain whether or not it is related to the Camera issue).
Trying to fix both issues, I repeated the flashing process, this time wiping the dalvik-cache as well.
Still no go. I've made the logcats of the first boot after reflashing CM 4.2.11.1 as well as a reboot. I have also linked my last_kmsg after rebooting due to the Camera app crash.
1st Boot: http://pastebin.com/m356cf97e
Reboot: http://pastebin.com/m69a15127
last_kmsg: http://pastebin.com/m76c42ee6
This camera issue is touched on here: http://code.google.com/p/cyanogenmod/issues/detail?id=792
As for the Camera issue, similar to the OP in the above thread, I only have issues when on battery power. However, I do not have any issues in other apps that utilize the camera such as barcode readers.
Things I have not tried:
- Another CM version.
- Wiping battery information or anything else other than data/ext partition/dalvik-cache.
- Reflashing an original ROM (which I did not backup - my friend's Magic is coming in the next week or so, so I'll grab his image).
Hopefully I've documented everything important (and perhaps trivial). I'm open to any suggestions.
EDIT: Some things I forgot to mention.
- 8GB Class 4 SD card
- Added details to my original post about partition sizes/types.

It seems I was wrong about rebooting only in the default Camera and Camcorder apps as I just recently experienced a reboot on the Barcode Scanner app.

Perhaps try an older version of cm. I had more stability on some of the older releases

What would be one of the more stable versions?

i always find CM has better themes and mods "BUT" the rom is laggy. in fact, amon's rom is fast and clean but not much of any theming. wasted.

scyzerd said:
What would be one of the more stable versions?
Click to expand...
Click to collapse
i'm back to 4.2.9.1 atm because it's a little less buggy. something like that or 4.2.8.1 or 7.1 maybe? go for the .1 versions because they will contain bug fixes for any known issues in the first release at that number...

I have that problem too... but I don't get it as often now. maybe once in a blue moon.....
there is two things I notice that when the reboot happens in the camera mode.
1) there are too much tasks running (you can notice it because the phone runs a little laggy, or if you check Taskskiller and the memory running low)
2) the audible selection is turn on
so now I watch taskskiller before I used the camera and reboot deson't happen that often, specially with the audible selection turn off.
let me know if you guy discover some other fix....

I wonder why in the world did you make such a big swap partition, since you have a 32A model you don't need any swap to run the CM ROM. To be honest CM works flawlesly without the SWAP partition on my phone which is also 32A. I have no problems with the homescreen nor the camera. Please try to repartition the SD card so it doesn't use the SWAP partition, you can also ditch the ext partition as the 32A model has more than enough space for applications installation (about 295MB space). Wipe and reinstall from scratch. Enjoy a working CM 4.2.11.1 build, you can even try 4.2.12.2
EDIT: ehhh, and if you encounter an alarm clock bug where the screen doesn't turn on when the alarm goes off, replace the existing alarm application (AlarmClock.apk) with the one provided in release 4.2.9. You lose some functions in the alarm clock but it works

Same problem different ROM
I'm having the same problem on a Rogers Magic 32A using AmonRa's Donut ROM.
The phone reboots after the 1st or 2nd restart of the camera. Plugged in to a charger, I can restart the camera at least 10 times. This isn't surprising since I did a wipe and reinstall the ROM and the problem still occurred with no other apps installed. Very strange.

I have the same problem...No not so much after I start using an other cam app, however the phone still reboots itself.

Any new(er) touchpad drivers/sw?

I'm becoming increasingly disenchanted with this thing day by day. I love the dual core, 512MB ram, wifi n and especially the 1080p capability, but is it worth the trouble? I begin to wonder...
Anyway, this just started happening recently to a point where it's become increasingly frustrating. I'm not sure if the enhancement pack or something else is the cause - I don't think it's the hardware unless it's going bad with time (hopefully not the case!). I haven't pinpoint anything, all I can say is that the last thing I did install was the enh. pack and that otherwise it's just stock 3389 on there.
My screen is becoming less and less responsive. Parts of it, are now taking a few touches to activate. The reason I don't think it's the screen itself or hardware is that after a while it seems fine - but after a fresh startup it's hell to do anything on there and it's not because of starting processes etc. because if I turn the screen to portrait mode I can touch the places I need activated and they'll work.
A definite area of contention for me, for example is the battery and wifi indicator which are, on first/fresh boot impossible to activate now. It takes a good 5 minutes of touching the screen all over the place to get it to a point where I can actually bring up the bubble dialogs from those 2 icons OR if I turn it to portrait mode, it will work.
I don't remember the screen ever being like this from fresh stock (3389) or even stock + gapps so I'm wondering if there's something in the enh pack interfering with touch driver performance or if there are new touch drivers in there that aren't as good as the old ones. The enh pack def. makes the pad feel quicker and I like the new Gmarket in there so now I have to decide between a faster/quicker but somewhat unresponsive device or an average speed device which is more responsive off the bat. Then there's of course the other possibility which is that it's not the software at all, but that the hardware really is finicky...in which case nothing would really make it work as it should. Oy veh.

Neoprimal said:
I'm becoming increasingly disenchanted with this thing day by day. I love the dual core, 512MB ram, wifi n and especially the 1080p capability, but is it worth the trouble? I begin to wonder...
Anyway, this just started happening recently to a point where it's become increasingly frustrating. I'm not sure if the enhancement pack or something else is the cause - I don't think it's the hardware unless it's going bad with time (hopefully not the case!). I haven't pinpoint anything, all I can say is that the last thing I did install was the enh. pack and that otherwise it's just stock 3389 on there.
My screen is becoming less and less responsive. Parts of it, are now taking a few touches to activate. The reason I don't think it's the screen itself or hardware is that after a while it seems fine - but after a fresh startup it's hell to do anything on there and it's not because of starting processes etc. because if I turn the screen to portrait mode I can touch the places I need activated and they'll work.
A definite area of contention for me, for example is the battery and wifi indicator which are, on first/fresh boot impossible to activate now. It takes a good 5 minutes of touching the screen all over the place to get it to a point where I can actually bring up the bubble dialogs from those 2 icons OR if I turn it to portrait mode, it will work.
I don't remember the screen ever being like this from fresh stock (3389) or even stock + gapps so I'm wondering if there's something in the enh pack interfering with touch driver performance or if there are new touch drivers in there that aren't as good as the old ones. The enh pack def. makes the pad feel quicker and I like the new Gmarket in there so now I have to decide between a faster/quicker but somewhat unresponsive device or an average speed device which is more responsive off the bat. Then there's of course the other possibility which is that it's not the software at all, but that the hardware really is finicky...in which case nothing would really make it work as it should. Oy veh.
Click to expand...
Click to collapse
Yeah, lots of us have had touch screen sensitivity issues. Luckily we figured out how to fix them. It's very simple.
If you are running the latest TNT Lite or Vegan ROM beta 4, the fix is very simple - drop an empty text file called "calibration.ini" in your /sdcard directory (you can copy it over from your desktop via USB cable, or just use ES File Explorer or similar file manager with create capability to create the file) and reboot, and *DON'T* touch the screen while your G Tab is rebooting. Voila, re-calibrated touchscreen, very sensitive again. Once it's working well, just delete that calibration.ini file so it doesn't recalibrate on every boot.
On earlier versions of the ROMs or on the stock 3389 ROM, the calibration executable looked for calibration.ini in the /sdcard2 directory so you needed an external microSD card to calibrate your touchscreen.
There's a whole thread on this called "touch screen sensitivity" or something like that where we figured all this stuff out originally.

rcgabriel said:
Yeah, lots of us have had touch screen sensitivity issues. Luckily we figured out how to fix them. It's very simple.
If you are running the latest TNT Lite or Vegan ROM beta 4, the fix is very simple - drop an empty text file called "calibration.ini" in your /sdcard directory (you can copy it over from your desktop via USB cable, or just use ES File Explorer or similar file manager with create capability to create the file) and reboot, and *DON'T* touch the screen while your G Tab is rebooting. Voila, re-calibrated touchscreen, very sensitive again. Once it's working well, just delete that calibration.ini file so it doesn't recalibrate on every boot.
On earlier versions of the ROMs or on the stock 3389 ROM, the calibration executable looked for calibration.ini in the /sdcard2 directory so you needed an external microSD card to calibrate your touchscreen.
There's a whole thread on this called "touch screen sensitivity" or something like that where we figured all this stuff out originally.
Click to expand...
Click to collapse
I already tried that and it had 0 effect. First I tried it in the original root, then I tried it on my actual SD card root. No effect whatsoever as to the accuracy or sensitivity of the screen. That is why I bothered to make this post at all.
In fact, I think I even made a post in a thread mentioning calibration.ini a few days ago. It def. does not work for me.

Neoprimal said:
I already tried that and it had 0 effect. First I tried it in the original root, then I tried it on my actual SD card root. No effect whatsoever as to the accuracy or sensitivity of the screen. That is why I bothered to make this post at all.
In fact, I think I even made a post in a thread mentioning calibration.ini a few days ago. It def. does not work for me.
Click to expand...
Click to collapse
Hmmm, that's weird. Okay, let me step you through running a manual calibration:
1) Create calibration.ini in the /sdcard directory (as described above)
2) Install "Android Terminal Emulator" from Market if you haven't already (it's free)
3) Run Terminal Emulator. Press menu button then Toggle Soft Keyboard to get the keyboard up.
4) type "/system/bin/TSCalibration" into the terminal and press enter
Let us know what output you see (if it's looking in /sdcard2 for calibration.ini instead it will tell you, if there's an error it will tell you, etc.).

/sdcard2
I think the post said you tried /sdcard and that won't work. You need a microSD crd inserted as /sdcard2 to do the fix and it doesn't work on the /sdcard that comes with the device.

justauser said:
I think the post said you tried /sdcard and that won't work. You need a microSD crd inserted as /sdcard2 to do the fix and it doesn't work on the /sdcard that comes with the device.
Click to expand...
Click to collapse
The enhancement pack includes the TSCalibration that works off of /sdcard, not /sdcard2.

"First I tried it in the original root, then I tried it on my actual SD card root."
Original root = internal storage/sd card, SD card root = sd card root, lol...as in little chip you stick into the phone or sd card 2.
I mentioned I tried both. I will attempt what rcg recommends and let you know.
Update: I got terminal emulator by zta labs (the only one I see in the android market as somehow it broke itself) and all that app does is force close.
Update 2: I got frustrated and just wiped it all and went back to 3899. Fixed now. Thanks all for attempting to help. Think I'm going to suck it up and stick with stock until 2.3 or Honeycomb comes.

[Q] Multiple Issues with xt720

I am a new user of touchscreen and android phones, so I'm not sure if I'm just being picky with my issues, or if they can be fixed. But if anyone can help I'd really appreciate it.
1. My phone will randomly mute mid-conversation. I then have to re-enter my password and get back to the phone "app" to un-mute it.
2. When I'm using the camera, if I leave it long enough for the phone to go into sleep mode I can't get it to turn back on. The touch buttons are still highlighted at the bottom of the phone, but the screen is black. I can hear the phone beeping like it is turning back on, but get nothing on the display. I then have to take out the battery, wait for 30-60 sec and then put it back in. Sometimes I have to do this repeatedly before it will start working again.
3. When I try to update the OS in Settings I keep getting the message that the phone cannot connect to the server. However, I have not other problems connecting to any other sites.
4. I added the facebook app and want to remove it now. I have gone into settings > applications and "uninstalled" it. However, the icon is still on my homepage and I can't seem to remove it. When I hold my finger on it a trash bin shows up below. But this only moves it to my apps page.
5. The phone is freezes pretty often. At least a couple times a day.
Ok, this is it for now. If anyone can help I'd really appreciate.
Thanks

I going to guess your still on 2.1 when was 2.1 stock the was way too touchy. The light goes out and you can't get to turn on unless battery pull this a issue found on 2.1 their a 2.2 update coming in late July. Update this on all this option will not work xt720 it not ota compatible so your settings area will not work . Be patient wait for Cincinnati bell update and if your not with them I intend to leak it.
Sent from my XT720 using XDA Premium App

As much as I'm liking my return to 2.1, it does indeed freeze up often, as I recall it did when I first got the phone. (the whole screen goes black, lights on bottom turn on thing)
Facebook app is a stock app and can't be removed unless your rooted.
Never had the mute issue.
The cannot connect to server thing I have had. But it's irrelevant as there shouldn't be any updates to get anyways.

Is updating the OS the best way to improve the performace of my phone? or should I still do the overclocking. If you advise to do the overclocking, should I wait untill I update the OS, or do it now?

There is no update to the OS, except for one that just overclocks from 550 to 720mhz. Chances are you already have that though. I do think that overclocking is a good idea if you want to increase the speed of your phone obviously. 1Ghz is nice and stable.
EDIT: Or do you mean update as in install one of the 2.2 ROMs from here?

I think Queenmantis's problem are related to the original Home app. try some Launcher apps such as Launcher Pro.
for now, my favorite is GoLauncher EX, with the latest update last week, that app totally rock. you guys should try.
I really love Dexter's 2.2, but the short battery life keeps bugging me so I've already went back to 2.1 since last week. I've got no modification except Milestone Overclock + App2Card 2.8.2. Eclair is still so sweet.

Hi I have bluesteel I have modified it some and would put up against any of 2.2 or 2.1 my numbers. Startup 65 memory and regular memory is 70 to 88 program memory and don't freeze and no lag.
Sent from my XT720 using XDA Premium App

Wait for CBW's update if you don't want to root.. If you're open to the idea of rooting your phone, then go ahead and update to Dexter's 2.2, save yourself the headache, then flash one of Khalpowers' ROMs, that should fix you up real good, there's always the option of going back to stock of you don't like the results, or go back to the "official 2.2" from CBW once it's available. But that's just me..

Queenmantis said:
I am a new user of touchscreen and android phones, so I'm not sure if I'm just being picky with my issues, or if they can be fixed. But if anyone can help I'd really appreciate it.
1. My phone will randomly mute mid-conversation. I then have to re-enter my password and get back to the phone "app" to un-mute it.
2. When I'm using the camera, if I leave it long enough for the phone to go into sleep mode I can't get it to turn back on. The touch buttons are still highlighted at the bottom of the phone, but the screen is black. I can hear the phone beeping like it is turning back on, but get nothing on the display. I then have to take out the battery, wait for 30-60 sec and then put it back in. Sometimes I have to do this repeatedly before it will start working again.
3. When I try to update the OS in Settings I keep getting the message that the phone cannot connect to the server. However, I have not other problems connecting to any other sites.
4. I added the facebook app and want to remove it now. I have gone into settings > applications and "uninstalled" it. However, the icon is still on my homepage and I can't seem to remove it. When I hold my finger on it a trash bin shows up below. But this only moves it to my apps page.
5. The phone is freezes pretty often. At least a couple times a day.
Ok, this is it for now. If anyone can help I'd really appreciate.
Thanks
Click to expand...
Click to collapse
1. Maybe the Proximity sensor for auto turn-off has problems, when you are using the phone, the backlight turn-on and your face or your ear touch the surface and it mute.
2. Obviously this is a hardware problem, you should bring your phone to where you buy it to check.
3. I have the same problem, but I think this is not our phones' fault. Motorola seems not to support this phone anymore.
4. Facebook is considered to be a system app on this phone, you can not remove it. The app call facebook you installed on the phone, just the update of the original facebook app. Don't worry about that.
5. This maybe is relevant with the problem you have in the number 2 - a hardware problem.
-------------------------------------------------------------
Please forgive if there is something wrong above. I'm willing to listen and learn.
thank you

spiderx_mm said:
I think Queenmantis's problem are related to the original Home app. try some Launcher apps such as Launcher Pro.
for now, my favorite is GoLauncher EX, with the latest update last week, that app totally rock. you guys should try.
I really love Dexter's 2.2, but the short battery life keeps bugging me so I've already went back to 2.1 since last week. I've got no modification except Milestone Overclock + App2Card 2.8.2. Eclair is still so sweet.
Click to expand...
Click to collapse
May you show me how to install App2Card 2.8.2 on Eclair. I try but i failed. What should I know first to do this.

Any news on how you did..?
Sent from my XT720 using XDA App

CrystalShield said:
May you show me how to install App2Card 2.8.2 on Eclair. I try but i failed. What should I know first to do this.
Click to expand...
Click to collapse
I think most important part of App2Card is partitioning of SD card. I had tried the partitioning tool in App2Card but it never fail to fail . So I partitioned my card as below and I use "Parted" software inside Ubuntu. My SD card is Sandisk 8GB SDHC Class6 card.
1st Partition - FAT32 (7.2 GB)
2nd Partition - EXT3 (512 Mb)
3rd Partition - SWAP (256 Mb)
Create one partition at a time. Don't create everything in one batch.
Then, the card should be ready to use.
now come with the App2Card. Open the app, make sure u grant root access and all, make sure the app detect the card. then close it again. (that might be the trick). And open it again. Just do open and close till the "What's New" pop-up never show up. It might be two or three times. Then click "Install EXT/Transfer apps to EXT" button.
it will install, make the phone reboot and configure.
after the phone is rebooted, open the App2Card to make sure it show no error message. If there's any error message, just try to reboot the phone. It will surely work.

Display / menus freezing and / or disappearing, system apps force closing

I've been searching this form for an hour or two now and still haven't found my issue, so here goes.
Just got an HTC Inspire 4G off of ebay and it arrived today.
The seller had mentioned that the phone was freezing / rebooting, but I figured.. that's because he's not running cm7, right?
Charged and booted up the phone and it turns out that the problem was a little worse than I first expected. I only experienced occasional freezing, and it only rebooted once, but there is a worse problem.
The phone loaded up fine, looked good, but tapping around on the home screen I got messages alerting me that system apps (htc sense, launcher, and even com.android.phone) had stopped responding or had shut down.
I hit the menu and go to settings. I scroll down the list and the entire list goes black. I hit home and it goes to a home screen, but with no launcher or icons. Basically, every few taps, the interface goes out. If you are on a menu it blacks out, if you are at home or press home after the menu blacks out you will get anywhere from pieces of icons / widgets to just a blank desktop. The live wallpaper even keeps going, but all of the interactive stuff quits. The disappearing menus didn't usually give app closed messages, they just went black. The home screen only gave app closed messages sometimes.
I thought this was a software problem, so I managed to root the phone and flash cm7. Everything booted good, but it still had the same problem of weird disappearing menus and home interfaces. I went ahead and flashed gapps and got the little intro thing about setting up my Inspire 4g that starts when you first boot your phone. I clicked through that but when it gets to connect wifi, the phone entirely freezes and I have to pull the battery.
I flashed inspiremod and nothing changed, tho that's for something else, so I'm not sure that's entirely relevant, but I was trying everything I could think of.
I'm definitely no expert on hardware, but it almost sounds like a ram problem, like it doesn't have enough to keep all of the interface going all the time and shuts it down or shuts parts of it down to work.. but I don't want to believe that. I'm really hoping that it's a software problem.
I got the phone at a good price and it came with an otterbox, so I won't be too disappointed if I can't get it fully functional, but it would still be a bummer.
Any help / advice / suggestions appreciated. Thanks, guys!
EDIT: I cleared the cache / dalvik cache before flashing / reflashing cm7, which I did once or twice
EDIT 2: Now if I leave it on the intro screen where it freezes it reboots after a minute or so. Gonna try flashing a different mod.. see if that helps.

That was a long post. But it was good, you gave a lot of info.
The cm7 zip that you downloaded, check the md5 checksum, make sureit matches whatever is in the op (first page) or wherever the md5 is, maybe where you downloaded it from. If it doesn't, download again.
Then,
from recovery,
Wipe data/factory reset.
Wipe dalvik
Format all partitions(except sd card)
Flash zip/rom.
Check if it works. If not, try using it without the sd card. If not, come back and report.
Sent from a dream.

Thanks for the reply and suggestions.
I check the md5, and it's good. I just did a factory reset and wiped cache and dalvik.. I'm unsure what you mean by format all partitions except sd card. I don't think I know how to do this with clockworkmod.
Started up without sd card and it still has the same problem. Looks great until I touch the screen, then everything disappears except the wallpaper.

Reboot in recovery and do it from there. You'll find format all partitions at the bottom... well, maybe. Cwm has an option to reboot in recovery, and I think if you press and hold the power button, select reboot and it will also ask you if you wantto boot into recovery. Cant remember if cm7 has it, it should.
After you wiped those, flash the rom. Stay in recovery and search for fix.permissions. Reboot.
Sent from a dream.

Just did that and re-flashed cm7, but the phone was still having the same problems.
I then repeated the process with a MIUI ICS rom and it seemingly worked for a little bit. I got a "Maps has stopped working" message, but I was able to slide back and forth through the home screens, and the menu came up. After I tapped though the menu a bit it started being weird again, but with MIUI the weirdness is different. It looked like the screen was divided up into 20 something smaller screens tiled across the display with messed up looking bits of screen in them.. weird..

If you are wiping correctly then I am out of ideas. I would say try a GB rom, however that is a strange issue and just might be a hardware problem. Tough, Im not sure.
Sent from a dream.

I've tried cm7, which is 2.3, and I've tried a 4.0.4 MIUI build and one other sense rom that didn't work well at all.
I'm wiping and flashing the same as I did on my LG p509, which works beautifully with cm7.
If it is hardware, hopefully it's something simple like the battery, and not bad RAM or anything serious..
Maybe if I keep at it I'll get it.
Thanks for all the suggestions!

Np. Keep us updated.
Sent from a dream.

I ordered a new battery for it, and that fixed the random reboots, which had been occurring more frequently, but the other problems were still there.
I flashed and re flashed and formatted and reinstalled a bunch, but still no luck. I then decided that I might take it by the local cell phone repair shop and see if they could fix it.
In preparation, I used aahk to flash the stock ruu with everything how it was when I got it. After booting it up, it seemed to be working ok.
I still get the occasional menu glitch, but it's so infrequent it's not an issue.
The phone still freezes up quite a bit when I'm using it, but it's nearly a useable device now!

awkwardcheesecake said:
I ordered a new battery for it, and that fixed the random reboots, which had been occurring more frequently, but the other problems were still there.
I flashed and re flashed and formatted and reinstalled a bunch, but still no luck. I then decided that I might take it by the local cell phone repair shop and see if they could fix it.
In preparation, I used aahk to flash the stock ruu with everything how it was when I got it. After booting it up, it seemed to be working ok.
I still get the occasional menu glitch, but it's so infrequent it's not an issue.
The phone still freezes up quite a bit when I'm using it, but it's nearly a useable device now!
Click to expand...
Click to collapse
Have you tried changing out the sd card? Having a bad sd card can cause all inds of odd issues

I booted it without an sd card before and couldn't tell the difference, but it had a lot more issues than just freezing then.
I haven't tried it since those other issues have stopped. I'll try that when I get home from work.

[A700] crash instead of powering off when empty

Hi devvers,
The last update for the German version of the tablet is not working so well for me.
First things first: the tablet drains a lot of battery power! Have you noticed that too??
And second: when the tablet is almost empty like 7%, the tablet turns off instantly. I don't see the second warning screen because there's still over 4% left. It used to show me the second screen and then when it's really empty, Android powers off.
Turning the tablet back on isn't an option anymore. You have to plug the charger and then it'll boot again.
I'm using a stock rom and no root whatsoever.
Am I the only one out there? :/
Ps. Are there people having a notification showing that the sd card is inserted every hour or so?

Okay, this problem has occured multiple times and today nothing happend and everything went how it should. Awesome.

TomONeill said:
Okay, this problem has occured multiple times and today nothing happend and everything went how it should. Awesome.
Click to expand...
Click to collapse
Self-Healing
With battery drains though, it's better to check your Applications and see if you downloaded some apps that might be using too much battery. Go to Settings/Apps and select Apps running. This will show you what's running in memory.
MD

Thanks for your reply.
Yeah, it's self-healing xD
I did last week and I didn't notice any particular app eating too much RAM memory. I also checked the cached processes, but that wasn't a problem either. I did turn off some notifications from games I didn't play anyway, but that did not really help.
May I ask how much RAM you have left when having nothing running?
I have between 200-300 MB left, sometimes after a boot 300 to 400, but not really that often.
I'm running the stock ROM by the way.
Another thing: Do you have a SD card in your SD card slot? Cause every now and then since the JB update I get the notification "SD Card is inserted". Which I'm sliding away and it pops up back after having my tablet in stand-by modus for a few minutes (perhaps hours).
Edit:
I have to say that I have been installing a lot of apps, but that I deleted a lot of them 2 weeks back. Then I checked my sdcard data (internal data) for any traces of deleted apps, but I was quite surprised how little there was left of traces of deleted apps. Microsoft could learn from that (though it's not Microsoft who makes their uninstallers not fully deleting everything. But am going off topic now.). Could that may have effects on the RAM? I don't assume it will, but just FYI.