Had to get rid of EXT4 ..
Seems like battery life has gone down the tubes.. doesn't matter which ROM i'm using. I can't seem to stay away from an outlet.
I've odin'd back to Di18 and started from scratch and still .. no luck. It's fast as hell, but I need my battery life back.
(I've been through all the settings, no widgets, no weather updating every 10 min. or nothing like that)..
But after using odin to flash from Di18 > DK28 numerous times this week.. I checked for bad blocks on my NAND and I still only have the same 3 that I've had since we determined that we could check for bad blocks.
(just wanted to share)
So i went back to a pre-EXT4 ROM w/ RFS for now.. hopefully this will alleviate some bluetooth maladies and help improve my battery life some until samsbung or sprint gets moving.
/useless_post LOL
If flashing back to an RFS rom didn't fix it, dont you think that it wasn't EXT4 that was causing the problem? Also, how does a file system format cause increased battery drain?
Could have saved you a bunch of work if you would have asked beforehand.
im having much better battery life on etx4 running the bonsai rom. much better than any rom i had on my evo.
True (muyoso) from what I've seen so far, since our devs don't have the kernel source, i really haven't experienced any major changes to battery life, from rom to rom (dk28).
Maybe take a look at the apps you've been running? Or widgets that update, like clocks/weather/news. I usually keep an eye on running services (menu, settings, applications, running..)
I'm always for doing a titanium backup, wiping data, and restoring the stuff I need manually thru it (titanium). It's painless if you categorize your necessary apps in there. Fwiw
muyoso said:
If flashing back to an RFS rom didn't fix it, dont you think that it wasn't EXT4 that was causing the problem? Also, how does a file system format cause increased battery drain?
Could have saved you a bunch of work if you would have asked beforehand.
Click to expand...
Click to collapse
I just finished the flash back to RFS to try for a day or two (mostly for troubleshooting)..
each time i switched ROMs (to determine if it was a ROM issue or not) i started over w/ Di18 and continued all the way to EXT4/ROM.. so it wasn't a chance of bad ROM flash...
I can't say for sure if it was or wan't EXT4 causing the dilemma... the only thing I know for sure is that i set my phone up the same way every time, manually, no titanium backup, no advance data restore, etc.. it's a ***** but it's the only way i can compare apples to apples.
Gonna try RFS w/ the last bonsai ROM that I used before original EXT4 conversion and see how it goes.
Related
hi im new to the forum and have a quick question. i just flashed viperrom 5.0 yesterday and everything worked great and really like the rom. only problem is when i shut down the phone and restart it i loose all apps including the market. ive tried reflashing it again and its doing the same thing. this is the only issue im experiencing so far. thanks!
Are you pulling the battery to shut the phone down? i think Journaling is turned off which can cause data loss.
no just turned it off no battery pull. i also noticed that when i restarted the phone usb debugging came back on. is this normal? how would i solve the journaling issue? i just flashed back to eb13 for now and its working alright. sorry im fairly new to flashing roms so bare with me
mk4cam said:
no just turned it off no battery pull. i also noticed that when i restarted the phone usb debugging came back on. is this normal? how would i solve the journaling issue? i just flashed back to eb13 for now and its working alright. sorry im fairly new to flashing roms so bare with me
Click to expand...
Click to collapse
Not not normal. I would re download all files and flash again, with starting with Fresh EC05 with ODIN.
i cant use odin cause im on linux so i have to flash through cwm everytime. but i did switch to ec05 today. i did notice that when i flashed viperrom one last time i restarted the phone before sync'ing with gmail and it kept the market upon restart. but when i synced gmail and restart i lost the apps including the market again. thats when i got real confused so i went to ec05.
in case it's caused by journaling being turned off, here's what I would suggest:
1) get the ROM installed (like you did previously)
2) get your apps downloaded and installed (as you did previously)
3) DON'T restart the phone yet....
4) after getting all your settings/apps setup
5) boot into clockwork mod and do a complete backup.
6) after making a backup, boot the phone. .if it's missing stuff.. don't worry..
7) boot back into clockwork mod and do a restore. Restore system/data, etc..
by doing a nandroid restore (step 7) you will enable journaling.. now when your phone boots back up, you'll have all your settings in place.. and you shouldn't lose them after a re-start (check it and see)
Hope this helps (if it does, hit thanks )
Journaling is on in the viper rom, but making a backup in cwm after you get it set up is a good idea. Also using an app backup, such as titanium, will let you restore your apps while on if you notice them missing.
Sent from my SPH-D700 using XDA Premium App
mikey80021 said:
Journaling is on in the viper rom, but making a backup in cwm after you get it set up is a good idea.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
i wasn't sure about Viper.. I use ACS and journaling is off by default but I like the piece of mind from journaling so I got all set up, did a backup, then restore LOL..
tomato tomatoe
Step 7 above is not a good way to turn on journaling. I've seen instances where some partitions have it and some don't. Best just to get a rom that has journaling on in the first place. Please also keep in mind that with journaling on it really slows down your system. You might not notice it now, but if you have been used to running ext4 for a while it will seem like molasses some how got in your phone.
Sent from Bonsai 7.0.3
Top Nurse said:
Step 7 above is not a good way to turn on journaling. I've seen instances where some partitions have it and some don't. Best just to get a rom that has journaling on in the first place. Please also keep in mind that with journaling on it really slows down your system. You might not notice it now, but if you have been used to running ext4 for a while it will seem like molasses some how got in your phone.
Sent from Bonsai 7.0.3
Click to expand...
Click to collapse
not to start a debate, but all the posts/advice that I've seen in the fora here have suggested that doing a restore will enable journaling..
I am currently running a nandroid restore and have been running the same for the last 2 weeks and I have no molasses Although, running ACS, maybe my phone is too "frozen" for the molasses to run out hahaha
YMMV..
Okay, I'm here everyday reading this stuff, Id first like to say you guys rock. Everyone here, and the makers of these awesome mods, you have made my phone and my life quit amazing, and less boring like stock!
It seems something is wrong
I sort of switch back and forth between cm and savage zen when each have an update. I love savage zen because of the higher resolution, makes my evo screen crystal clear, while cm is much more stable, and has not only the meat, but the potatoes and gravy, while savage only has the meat
But anyway, no matter what I do, gmail crashes, and media crashes, market doesn't work etc. The google apps in rom manager have worked before, when I was using 2.3.4 I was able to find that google app package somewhere online.
The google apps in rom manager that im thinking of says its compatible with 2.3.3, and well I used it for a few weeks perfectly. Silly me though I'm never satisfied...
I'm running 7.0.3.1, but it seems the google apps that comes with that package has never worked, you know when you check the box for google apps.
So instead I would do it manually, and again I mean it worked fine.
I decided to go back to savage zen, loved it (everytime deleting delvik cache and full wipe)
I think I am missing something...
The order I would do things is, wipe dalvik cache/data, install mod/google apps. I mean that has always worked before just fine. I tried a before and after also, booted it before restoring my data, nothing crashed, it all went smoothly.
In recovery, I go to restore, advanced restore, then restore data. My 2 latest backups both fail. Am I not restoring correctly, oh im sure this is all my fault.
Sorry im sure this has been answered many times over...I found a few threads but they wernt quite what I was looking for because the person I was reading about both times was using cm6, and I think I did the steps correctly..but thats what I'm here for, Please help me fix my bad *** phone.
Quick Update
Okay, so yeah I do still have more to learn. I was thinking well maybe if I just wipe the cache partition....(havnt done that before..just did full wipes)
Is this all my fault? Maybe all this going back and forth is just not good? lol
I figured this out by myself. I went into titanium backup, and wiped the cache of every program that was giving me the error. Done and done. I guess clockwork mod doesn't get rid of all cache?
Well..thanks anyway...I didn't find the fix on google, or anywhere for that matter..It just came to me..
I remember reading comments about how clockwork dosent nandroid wimax keys and does not fully wipe like it should, you should try switching to amon's RA recovery.
I switched to Amon Ra a few months ago. I agree it's way better and it's nice to be able to whipe dalvik cache without waiting a few minutes for it to even get to the right screen, but I have still had a few problems even after dalvik/cache wipe. Titanium backup is a nice way of cleaning things up also, media storage!
That's something I figured out, it was media that kept crashing and it's happened again, but I do flash like a junkie! Always making sure to wipe dalvik/cache and making a nandroid backup before flashing.
Going into settings, applications, media storage then clear data. Works like a charm.
Also once I had 2 ringtones playing when my phone rang...couldn't figure it out and did EVERYTHING. Clearing media storage saved the day.
I think I'm done flashing..may of found my perfect combo
Synergy rls1 + godmode with aggressive freedom kernal.
mmmmm delicious! RLS1 made the phone actually seem to be overclocked before overclocking it (If that makes sense LOL), it ran just as smooth as it did running cyanogen overclocked to 1190. Of course I overclocked it anyway
I'm stuck at the boot-screen of Deck's 1.2 rom, however, I can still access HBOOT and Clockwork Mod Recovery.
I don't see an explicit option, but is there a way I could access Apps or other data to save as a back-up?
I foolishly deleted my rom back-up, and last time I used Titanium Backup was a few weeks ago, so it's not a good option. Thanks!
Android 17 said:
I'm stuck at the boot-screen of Deck's 1.2 rom, however, I can still access HBOOT and Clockwork Mod Recovery.
I don't see an explicit option, but is there a way I could access Apps or other data to save as a back-up?
I foolishly deleted my rom back-up, and last time I used Titanium Backup was a few weeks ago, so it's not a good option. Thanks!
Click to expand...
Click to collapse
As long as the .zip for the ROM doesn't wipe /data, you could reflash "Deck's 1.2 ROM hopefully fixing your issue and not losing your apps.
mattykinsx said:
As long as the .zip for the ROM doesn't wipe /data, you could reflash "Deck's 1.2 ROM hopefully fixing your issue and not losing your apps.
Click to expand...
Click to collapse
I already tried wiping cache and dalvik, reflashing the rom, and I still get stuck in a boot-loop =/
Thanks for the suggestion though.
Android 17 said:
I already tried wiping cache and dalvik, reflashing the rom, and I still get stuck in a boot-loop =/
Thanks for the suggestion though.
Click to expand...
Click to collapse
You could wipe /boot and /system as well and reflash and see if that fixes it.
mattykinsx said:
You could wipe /boot and /system as well and reflash and see if that fixes it.
Click to expand...
Click to collapse
I just tried that and it didn't work either. This is maddening.
The last thing I remember doing was tinkering with the lockscreen settings in the advanced settings. I set up a rotary revamped lockscreen with Dolphin Browser HD as my custom application. I have Dolphin saved to SD too, but I don't see why such a small thing would cause constant bootloops.
It ran fine before 1.2 stable and messing with the lockscreen.
Android 17 said:
I just tried that and it didn't work either. This is maddening.
The last thing I remember doing was tinkering with the lockscreen settings in the advanced settings. I set up a rotary revamped lockscreen with Dolphin Browser HD as my custom application. I have Dolphin saved to SD too, but I don't see why such a small thing would cause constant bootloops.
It ran fine before 1.2 stable and messing with the lockscreen.
Click to expand...
Click to collapse
I have titanium backup run every night along with my call log back up app and go sms to back up texts.
Prevents this kind of thing.
Nothing you've said you have done explains a boot loop.
mattykinsx said:
I have titanium backup run every night along with my call log back up app and go sms to back up texts.
Prevents this kind of thing.
Nothing you've said you have done explains a boot loop.
Click to expand...
Click to collapse
That's a good idea. I usually just use Titanium backup when I'm doing a full wipe or flashing a ROM with significant updates, but since I'd been using Deck's for a while and having no issues whatsoever really and just updating incrementally, I didn't think to backup in a while.
I had actually backed-up the ROM prior to flashing 1.2 stable, but I needed to delete it to make room to back up the newer version, and I didn't think it'd be a big deal since it was stable for a few boots. I guess I got too comfortable.
This is ridiculous, I didn't make any changes to the ROM or flash any new radios or anything of the sort that should cause a bootloop.
I do also use the Theme Manager MattedBlues theme but I've been using that for over a week or so with no issues, so I doubt that's the cause.
Oh well, thanks for the ideas though.
Android 17 said:
That's a good idea. I usually just use Titanium backup when I'm doing a full wipe or flashing a ROM with significant updates, but since I'd been using Deck's for a while and having no issues whatsoever really and just updating incrementally, I didn't think to backup in a while.
I had actually backed-up the ROM prior to flashing 1.2 stable, but I needed to delete it to make room to back up the newer version, and I didn't think it'd be a big deal since it was stable for a few boots. I guess I got too comfortable.
This is ridiculous, I didn't make any changes to the ROM or flash any new radios or anything of the sort that should cause a bootloop.
I do also use the Theme Manager MattedBlues theme but I've been using that for over a week or so with no issues, so I doubt that's the cause.
Oh well, thanks for the ideas though.
Click to expand...
Click to collapse
Sorry I took my Xanax to sleep or else I'd likely be able to think of some kind of solution.
Hopefully someone else can help you out.
I think in CWM if you mount System&Data /apps you could utilize adb pull..... Also did you set up any custom partitions, a2sd, data2ext, ect... ?
Sent from my HERO200 using XDA App
Actually thanks for the suggestions guys, I managed to dig up an older version of the rom saved on my downloads folder and flashed it and booted.
For some odd reason, an older release labeled as experimental works better than the 1.2 stable...
It's strange too because I looked around Deck's thread and no one else reported any problems similar to what I was having at all.
For all intents and purposes it appears to be very stable and functional for everyone BUT me
Thanks for the suggestions though. I guess I'll hold off on flashing any roms for a while or wait for a newer version and try flashing with a full wipe.
Cool glad you got her going.
Kaaameeehameeehaaaaaa!
i started noticing that after i flashed a new rom, alot of my settings are set to the way i had them before. and some apps are already installed that would otherwise need a marketplace install..
keep in mind, i always do a wipe of cache/dalvik/sdcard
i think it started happening after i partitioned the sd card for those old sense roms that needed extra space.. cant remember..
but it seems like theres a portion of rom that isnt being wiped and all my settings are being carried over to the next rom flash..
how can i fully wipe my phone or get it back to normal?
this is weird, and i want it to stop. any ideas?
i just flashed back to amonra
TorxT3D said:
i started noticing that after i flashed a new rom, alot of my settings are set to the way i had them before. and some apps are already installed that would otherwise need a marketplace install..
keep in mind, i always do a wipe of cache/dalvik/sdcard
i think it started happening after i partitioned the sd card for those old sense roms that needed extra space.. cant remember..
but it seems like theres a portion of rom that isnt being wiped and all my settings are being carried over to the next rom flash..
how can i fully wipe my phone or get it back to normal?
this is weird, and i want it to stop. any ideas?
i just flashed back to amonra
Click to expand...
Click to collapse
Are you using ROMs that have Google back up enabled?
Also, if the zip isn't set to wipe /data and you're not wiping it then you'll still have all of your data.
That has happened to me too. Are you wiping sdext and android.secure in recovery. I always wipe those and haven't had that happen since I started doing that.
We're comin from a pure power source.
naw i turn off all that google backup stuff.
thats the thing, when i try to wipe sdext it gives me an error (from the last i remember doing it)
Hmmm. Latest version of amon ra?
We're comin from a pure power source.
keep in mind, i always do a wipe of cache/dalvik/sdcard
Click to expand...
Click to collapse
You should be wiping data as well when flashing new roms.
I flash vrsuperwipe everytime I flash, but I use Google backup, so when I flash a new sense ROM it saves a lot of my settings, and my SD-ext apps automatically appear. Good feature imo.
Sent from my PC36100 using Tapatalk
bump for any other answers or advice
thanks guise.
still wondering about other options before testing some new roms
same thing happened to me so I tried repairing sdext and then re-partitioned my card and left it ext2 instead of ext3,wipe data/cache/dalvik cache/system flash superwipe, then flashed rom. don't know which one worked but it stopped. Also I noticed it mainly happens when I flash 3.0 roms but it has happened on CM7 to
TorxT3D said:
i started noticing that after i flashed a new rom, alot of my settings are set to the way i had them before. and some apps are already installed that would otherwise need a marketplace install..
keep in mind, i always do a wipe of cache/dalvik/sdcard
Click to expand...
Click to collapse
You did not wipe data. If you do this you will preserve all of you apps (if they were not on card), data and system settings. This may work for you if the new ROM that you are moving to is similar enough. It can cause big problems if the structure of the ROMs is too different. You can end up with a phone that lags and has wakelocks (at best) or is not functional at all due force closes all over the place.
You should really wipe data as well before flashing a ROM and then do a selective restore of data on the new ROM.
Ok, so here's the back story as best as I can manage. I recently (like Monday) flashed a new version of Civato's Flexstriker to my A500. The flash went fine and my tab was working great. Last night out of the blue, the internet browser started acting up, locking up, and even rebooting the tablet. I have it overclocked to 1680 using smartassv2 governor. Anyway, I first thought it was because maybe it was getting too hot, so I underclocked it to something like 600MHz to let it cool, but no luck. So then I thought maybe it was because something was wrong with the ROM. I decided to nandroid backup, and re-install the ROM. This is where the fun starts. After attempting a complete wipe, I re-flashed and got stuck in a boot loop. Re-wiped, installed a completely different ROM, boot loop. So I started digging into the wipe and noticed that I was getting a formatting /data error and that the entire /data/app folder is read only.
SO now I'm thinking maybe there is a conflict between my ROMs and the /data/app folder that won't let it boot. I tried mounting the /data/app in adb and it won't let me remove anything because it says it's read only.
How do I clean this thing off completely and start over? I'm stuck with a tablet that doesn't work and that is not acceptable. (PS- I know it's all probably my fault, so I don't need a lecture. I am a complete newb on android/linux.)
Did you Wipe Data (Wipe Menu) or Format Data (Mounts Menu) in CWM?
bthefirst said:
Did you Wipe Data (Wipe Menu) or Format Data (Mounts Menu) in CWM?
Click to expand...
Click to collapse
yes. When I do the wipe data I get a format error. "Error removing...." so I checked the status of the /data/app folder and it's all read only. I tried deleting the files in adb using the rm -r command, but I still get the read only file system.
How do I change the file system to read/write?
This is also new, When I do :su in adb, I get a segmentation fault. what's going on?
Try to do format Data from Mount Menu. That Segmentation Fault I've received when the device was not correctly rooted. Maybe try flashing another kernel.
bthefirst said:
Try to do format Data from Mount Menu. That Segmentation Fault I've received when the device was not correctly rooted. Maybe try flashing another kernel.
Click to expand...
Click to collapse
Still get the error formatting data from that menu.
I've flashed an older ROM, and still get the same thing.
I'll try locating a kernel to flash. So far, I'm stuck with a dead tablet. Anyone got any ideas?
i had a similar prob earlyer this week. not the same but close read this
http://forum.xda-developers.com/showthread.php?t=1496884
the first bit wont help but read on you prob have currupt data that cant be wiped and there is a way around it.
Moscow really helped me out!!!
give it a look any way
I know this may be a little late to ask, but do you have a nandroid you can do to go back? Even when i've had filesystem issues (on my Epic) i've been able to get back by doing a nandroid. If all else fails, you can go back to stock...
kazea182 said:
I know this may be a little late to ask, but do you have a nandroid you can do to go back? Even when i've had filesystem issues (on my Epic) i've been able to get back by doing a nandroid. If all else fails, you can go back to stock...
Click to expand...
Click to collapse
if it is a similar prob to mine the currupt data is in your back up too
kazea182 said:
I know this may be a little late to ask, but do you have a nandroid you can do to go back? Even when i've had filesystem issues (on my Epic) i've been able to get back by doing a nandroid. If all else fails, you can go back to stock...
Click to expand...
Click to collapse
I have several nandroids. the big problem is that I can't wipe the data directory because it's telling me it's a read only file system. And I can't change the file system because I'm not sure how to, and the SU comes back with a segmentation fault.
are you using cwm? if so what version?
---------- Post added at 01:46 PM ---------- Previous post was at 01:38 PM ----------
If you are using Thor's CWM. And his recovery only;
Here are the steps to completely wipe all internal data. And give it a clean internal system (according to Thor)
Note: Optional Formatting.
If you really want to remove EVERYTHING in Internal Memory, at this point, go to Backup and Restore. Select "Toggle backup and restore of internal storage (/data/media). Enable this setting by selecting it. By default, it is disabled. Then proceed to the formatting steps. This will format the Entire Internal Memory when you proceed.
Note, this will format EVERYTHING in internal memory (not ext sd card)
Select Go Back, Goto Mounts and Storage
1. Format System
2. Format Cache
3. Format Dalvik
4. Format Flexrom
just let it format, and hopefully it will take care of the corrupted data
Then just install the fresh rom.
After you reboot, I believe it resets back to the defaults.
it will wipe your backups tho but that dosent matter if they arent working
im not an expert just passing along info that was given to me
dr mcknight said:
i had a similar prob earlyer this week. not the same but close read this
http://forum.xda-developers.com/showthread.php?t=1496884
the first bit wont help but read on you prob have currupt data that cant be wiped and there is a way around it.
Moscow really helped me out!!!
give it a look any way
Click to expand...
Click to collapse
Ok, I downloaded the latest recovery, did the steps to fully delete the data and it didn't error this time. Wiped like 3 time on everything. re-installed my rom and I'm now re-booting.... fingers crossed..
Update: Booted!!!!! Finally!!!!
Thank you, Thank you!!!!!
Just by chance, I went on this thread.
Really, I am glad you got it running, and glad me and Dr Mcknight pitched in to help. He'll be an OC monster before too long
For all you users wanting to overclock. Never run at the max OC speeds. Usually they are unstable.
Yeah, i run at 1600, and I'm stable, but I am just lucky. But I don;t run it all the time. Typically, 1504 is fine.
Anything above 1600, is purely for benchmarks. And if you use it normally, at that speed, you may have reboots, freezes, corrupt data.
I'm lucky as I only had 1 reboot at 1686. Or was it 1748???? I forget.
So people, keep it at a normal level.
Moscow Desire said:
Just by chance, I went on this thread.
Really, I am glad you got it running, and glad me and Dr Mcknight pitched in to help. He'll be an OC monster before too long
For all you users wanting to overclock. Never run at the max OC speeds. Usually they are unstable.
Yeah, i run at 1600, and I'm stable, but I am just lucky. But I don;t run it all the time. Typically, 1504 is fine.
Anything above 1600, is purely for benchmarks. And if you use it normally, at that speed, you may have reboots, freezes, corrupt data.
I'm lucky as I only had 1 reboot at 1686. Or was it 1748???? I forget.
So people, keep it at a normal level.
Click to expand...
Click to collapse
just trying to show a lil love back to the community
Moscow Desire said:
Just by chance, I went on this thread.
Really, I am glad you got it running, and glad me and Dr Mcknight pitched in to help. He'll be an OC monster before too long
For all you users wanting to overclock. Never run at the max OC speeds. Usually they are unstable.
Yeah, i run at 1600, and I'm stable, but I am just lucky. But I don;t run it all the time. Typically, 1504 is fine.
Anything above 1600, is purely for benchmarks. And if you use it normally, at that speed, you may have reboots, freezes, corrupt data.
I'm lucky as I only had 1 reboot at 1686. Or was it 1748???? I forget.
So people, keep it at a normal level.
Click to expand...
Click to collapse
Normally I run it at 1400 or 1200. I set it to 1680 and forgot it was there. So yeah, my own dumb fault. Live and learn.
Thanks again for that thread. You really saved me.
CPU'S and overclocking
Computer processors due to the way they are assembled. all have dead transistors.. Some call them simi conductors.. . With this being said .. not all of them can run at the same clock speeds.. In the far past when cpu's were made. they would test them to see the max perfectly stable speed to run at.. stamp them and sell at that level.. Power users and main boards started hitting the market allow you to change voltage and clock speeds . This caused a onslot of people over clocking.. That is what lead to LOCKED MULTIPLIERS ON Boxed cpu's.
Anyway what this all means is ONE Device spun on the same die . might run much faster then the one next to it . OP It does sound like you have taken life of your device . I DO Hope you did not cause to much heat on the embedded ram and rom chips. if so you will always have a unstable to end of life device
Tis the reason to never BUY A USED Gaming computer.. YOU KNOW it was clocked far to high way to many times..
glad you have it fixed and was nothing but corrupt data..
erica_renee said:
Computer processors due to the way they are assembled. all have dead transistors.. Some call them simi conductors.. . With this being said .. not all of them can run at the same clock speeds.. In the far past when cpu's were made. they would test them to see the max perfectly stable speed to run at.. stamp them and sell at that level.. Power users and main boards started hitting the market allow you to change voltage and clock speeds . This caused a onslot of people over clocking.. That is what lead to LOCKED MULTIPLIERS ON Boxed cpu's.
Anyway what this all means is ONE Device spun on the same die . might run much faster then the one next to it . OP It does sound like you have taken life of your device . I DO Hope you did not cause to much heat on the embedded ram and rom chips. if so you will always have a unstable to end of life device
Tis the reason to never BUY A USED Gaming computer.. YOU KNOW it was clocked far to high way to many times..
glad you have it fixed and was nothing but corrupt data..
Click to expand...
Click to collapse
I'm an at home overclocker. So I guess I'm aware of the risks involved. And like I said, I normally don't OC this tablet for any kind of time. I just managed to forget about it this time. It didn't ever get hot to the touch, not even really warm, and I know the aluminum case is a link in the cooling chain on this device. So I'm pretty confident it wasn't baked too bad. BUT, you're right it still has the risk there. Hey if it becomes too unstable, I'll pass it down to the kids and get a new one.....