Would like to tell you my story
this morning JB was release and i updated my tablet with the new update. I was hoping for a nexus 7 like experience only to find out how jerky and stuttery JB is running in my TF700. After a factory reset nothing same story. To end the story quickly, i brick my tablet with TWRP and JB.
Replace my unit (bestbuy)which was a C08 for a C07 (the only one left). It came with .22 after booting my tablet it did a upgrade to .30 and then it did an upgrade to JB. i did a factory reset afterward. Boy is this thing fast, just as fast has my nexus 7 (no joke). Why my old TF700 was stuttery and jerky all over this one is lag free EVERYWHERE. I have own several Android device which i have updrade from ICS to JB and i now how butter smooth feels. GS3, Galaxy nexus, TF300.
Don't know what to say guy but my guess willl be downgrade to .30 do a factory reset, upgrade to JB and do another factory reset. I almost gave up on the TF700 and the tablet i owned this morning. Now i'm in love again and truly a believer in this tablet.
Most likely removal of apps that were hogging resources was the fix. Factory reset removes these
cmdrdredd said:
Most likely removal of apps that were hogging resources was the fix. Factory reset removes these
Click to expand...
Click to collapse
Factory reset was done on both devices
eduardmc said:
Factory reset was done on both devices
Click to expand...
Click to collapse
You said you only reset after the update on your first one so you wrote the JB firmware right over the top. With the new one you started clean.
It's somewhat similar to doing a full wipe vs dirty flash with custom roms. Flashing over the top can sometimes be a little bit more problematic.
cmdrdredd said:
You said you only reset after the update on your first one so you wrote the JB firmware right over the top. With the new one you started clean.
It's somewhat similar to doing a full wipe vs dirty flash with custom roms. Flashing over the top can sometimes be a little bit more problematic.
Click to expand...
Click to collapse
"I was hoping for a nexus 7 like experience only to find out how jerky and stuttery JB is running in my TF700. After a factory reset nothing same story."
That still tells me "I wrote new firmware over old firmware without wiping data first".
I'm not saying it's what caused the noticeable performance improvement, but I know with many things from BIOS updates (reset CMOS before flash) to custom roms (wipe caches and data reset), everyone advises to do it before and after. *shrug*
Related
Hello everyone
This might sound like a silly question. I upgraded my phone with the latest gingerbread OS. This OS is extremely buggy and other than the browser improvement I have only faced problems with it. My phone has to be reset everyday otherwise calling becomes extremely laggy. Battery life has taken a hit surprisingly (In froyo it was so amazing for me). Tethering error is there..
I am planning to do a factory reset. Just wanted to know whether my gingerbread update will be reset back to Eclar (2.1) after the factory reset? I am ok with my apps and contacts getting deleted since I have them backed up.
Thanks
Sid
Go right ahead
No, if you installed the official GB update, it will reset to that. I did, and I'm *delighted* I did! I updated to Froyo without a factory reset, and the phone gradually accumulated cruft to the point of becoming really annoying. When I updated to GB, my Cappy became basically unusable: very slow, with constant FCs. After doing a factory reset, it's amazing---just like having a brand new phone (which is the whole point of a factory reset!)
Well...it appears that you have not chosen a good GB ROM. Go for Serenity or Illuminance ( Both KK4 builds and trouble free) . These kk4 builds are very stable and should serve the purpose. However, if you wish to go back to the stock Froyo ROM, download the ODIN One-Click package of UCKF1.
"THANKS' .. if I helped you
Youre just deleting data not firmware... you should be ok
I'm running stock jb and sadly its very laggy and many taps will result in many second of waiting. Even Google search takes ages to start.
Are the cyanogen Roms better? Is there already a working cm10 rom available?
Shahpur.Azizpour said:
I'm running stock jb and sadly its very laggy and many taps will result in many second of waiting. Even Google search takes ages to start.
Are the cyanogen Roms better? Is there already a working cm10 rom available?
Click to expand...
Click to collapse
I would give Jellybro a try. Seems to be fairly popular ROM based on CM10
http://forum.xda-developers.com/showthread.php?t=1791751
Make sure you make a nandroid backup and know how to flash beforehand.
i agree! jellybro is the sastest jb rom here !
I'm using paranoidandroid 1.9.5 its very smooth and fast but WiFi tethering is not working
Sent from my Nexus S using Tapatalk 2
Since you need to wipe the phone either way, have you tried a factory reset yet? It's worth a shot. You never said whether or not you did. But if you're looking for more features all baked in, go with a custom ROM
I think CM9 is still faster overall although it isn't buttery smooth like JB or CM10.
chronophase1 said:
Since you need to wipe the phone either way, have you tried a factory reset yet? It's worth a shot. You never said whether or not you did. But if you're looking for more features all baked in, go with a custom ROM
Click to expand...
Click to collapse
My boot loader is already unlocked so I shouldn't have to wipe for root, right? I'm just not sure if CM10 is worth it. Don't know if nexus s is capable of keeping it fast with Android 4.x...
You should try the jellybro rom because its super fast.
Sent from my Nexus S using xda premium
Try doing a full wipe/system reset. My Nexus S OTA to JB a few weeks ago. Even at stock, it was fast. No lag.
If you are experiencing lags, it is likely your phone's filled with resource contending stuff.
BTW, I've seen flashed in CMREX Beta9 JB. Boot up is insanely fast. Everything works.
Also you can try the V6 Supercharger mod. It helped my other phone - Gingerbread equipped XT615 Motoluxe speed up quite nicely.
Shahpur.Azizpour said:
My boot loader is already unlocked so I shouldn't have to wipe for root, right? I'm just not sure if CM10 is worth it. Don't know if nexus s is capable of keeping it fast with Android 4.x...
Click to expand...
Click to collapse
Mine runs very well on JB. You're already rooted and whatnot, all you need to do is backup via recovery. Properly wipe the phone and flash. There's a few 4.1 ROMs out there. Give them a shot and see what you like. The phone is still pretty quick despite its age. Like I said. The phone may just need to be cleaned up. I've never had mine lag, personally.
Should I wipe SD partition too? It takes ages to backup the SD partition to a PC first...doesn't seem to support USB 2.0...
I would try a factory reset first to see what happens...
Shahpur.Azizpour said:
Should I wipe SD partition too? It takes ages to backup the SD partition to a PC first...doesn't seem to support USB 2.0...
I would try a factory reset first to see what happens...
Click to expand...
Click to collapse
From my understanding just do a factory reset/wipe, wipe the dalvik cache and then flash your ROM.
Shahpur.Azizpour said:
I'm running stock jb and sadly its very laggy and many taps will result in many second of waiting. Even Google search takes ages to start.
Are the cyanogen Roms better? Is there already a working cm10 rom available?
Click to expand...
Click to collapse
First try change kernel..
Nocerino's Rulez with RAScarlo's ROM features TriNitY
I've had the same issue and came here to see if others shared. JB was initially pretty solid (I initially did a full wipe), but now it lags real bad. Google Now is the worst offender. It takes at least 5 seconds to appear, and then a good chunk of time to allow me to input text. It's too much.
I'm going to keep looking for another ROM, but honestly, I was counting on the fact that stock would be the most reliable. I've also had trouble using my radio to make calls / use data. I'm disappointed as I figured these problems were previously mostly due to custom ROMs. All I want is a stable, simple ROM that functions consistently.
Google Now was fast for me initially but it's super slow now but I doubt this is a ROM issue.
Everything else is fast and smooth.
Sent from my Nexus S using xda premium
I think its time to upgrade...just waiting for a nexus without pentile screen.
Do a full wipe, clear cache
This is the best time to check as many roms as possible. no need to worry about losing anything as you should of backed it all up by now. So clean slate and try some different Roms. To say stock is laggy does sound strange. So back up everything, even whats on your SD.
Clean start.
Best backup program to save apps and data - Titanium backup
Best app for everything else (app manager, processes etc..) - Romtoolbox.
Now go have fun!
try Xenonhd v6.0 and Air kernel JB weekly.
My phone is better than new with this combo. I am not going to try anything else until these give me a serious issue (I dont think they will)
Looking to gift my 7+ to my sister by doing a factory reset to return to unrooted stock. Flashed the European ICS a while back from HC via Mobile ODIN, Been reading about the Superbrick Bug on some Samsung devices has me a tad leery.
Probably know the answer but thought I'd ask regardless. Any instances of problems with reset given the above 7+ profile? Now that US ICS is out would quite probably update to US ICS afterwards.
Suggestions? Thoughts? Idle ramblings?
thanks
skeeterpro said:
Looking to gift my 7+ to my sister by doing a factory reset to return to unrooted stock. Flashed the European ICS a while back from HC via Mobile ODIN, Been reading about the Superbrick Bug on some Samsung devices has me a tad leery.
Probably know the answer but thought I'd ask regardless. Any instances of problems with reset given the above 7+ profile? Now that US ICS is out would quite probably update to US ICS afterwards.
Suggestions? Thoughts? Idle ramblings?
thanks
Click to expand...
Click to collapse
As of right now be sure that you all are extemely cautious when trying to flash any type of ICS package (be it firmware, a ROM, or any type of system running it). Our tablet may have an issue with ICS as many other galaxy devices have. A bug currently exists that corrupts the mounting of the data partition on the device which *MAY* lead to a permanent hard bricking of your device.
This is currently a very RARE issue, however, those who are not well educated in Android development and that do not know how to 100% reset their tablet should refrain from flashing any type of ICS ROM or ODIN package.
If you have already flashed an ICS ODIN package or are running CM9 safely and have been for a good amount of time.
For those of you who insist on upgrading to ICS, backup your entire ROM and make sure that you have the stock HC ODIN package. Although it probably won't help having them if you are hard bricked.
My personal experience is positive, from honeycomb , i am past to CM9 , then with ODIN to flashing ICS , I do not have locked the device , there were problems with bootloop ,but solved by using a wipe data , factory reset from the recovery..
skeeterpro said:
Looking to gift my 7+ to my sister by doing a factory reset to return to unrooted stock. Flashed the European ICS a while back from HC via Mobile ODIN, Been reading about the Superbrick Bug on some Samsung devices has me a tad leery.
Probably know the answer but thought I'd ask regardless. Any instances of problems with reset given the above 7+ profile? Now that US ICS is out would quite probably update to US ICS afterwards.
Suggestions? Thoughts? Idle ramblings?
thanks
Click to expand...
Click to collapse
If you need to reset it, DO NOT FACTORY RESET FROM ICS RECOVERY. Flash back to hc with Odin, then do a factory reset there, or install cwm recovery and reset it from there (probably the route I would take, as it is far easier)
Sent from my myTouch 4g via Tapatalk
as per what i did, i have done factory reset from within the settings menu, which rebooted my device to stock recovery.
the initial reset was fine, but when i flashed the new asian ICS firmware, i did a reset from the stock recovery itself, which have bricked my tab.
so, be careful with factory reset, as it also uses the default recovery (correct me if i understand it wrong).
So I did a factory reset on my friend's note 10.1 and was surprised that it stayed at android 4.1.2
Her note was lagging a bit and I thought that the cause was when I updated the tablet to 4.1.2 as soon as it was opened so we did a factory reset.
No lag anymore now but I was hoping to have it back in the very very beginning and have her use it as it is then update it after a few weeks.
Has anyone else tried this?
The new rom is now the only rom on the note 10.1... If you install a custom rom and do a factory reset it will still have the custom rom on it. To hold over 1Gb of rom in memory in case you want to go back is a waste of memory...
Factory reset cleans data only and all stuff you put dont do any downgrade on software.
Sent from my SGH-M919 using xda premium
Ah i see. It would be a waste of space to keep the old version so it was completely deleted when I upgraded her tablet. Makes sense now. I'll look at factory reset differently now.
Hello, am I the only one experiencing bugs that I didn't have before since upgrading to 4.4.3?
To be specific: I never had the mm-camera-daemeon bug before updating, now I see it in the battery statistics! I thought 4.4.3 was supposed to fix this, not introduce it for people who previously didn't have it.
Also, this might just be me, but the speaker and headphone volume seem quieter than before, which again, I thought this bug was supposed to be fixed.
I installed the factory image from google with fastboot, but didn't wipe the data.
Any thoughts?
the camera deamon itself is not a bug, itll show up if you use the camera. what was a bug is that it continued to drain battery after the camera was used.
simms22 said:
the camera deamon itself is not a bug, itll show up if you use the camera. what was a bug is that it continued to drain battery after the camera was used.
Click to expand...
Click to collapse
But this is showing up after rebooting, and I haven't used the camera for a few days. I also don't have any apps like skype that may be accesing it. Maybe I'm just being paranoid though.
I always recommend wiping when updating Android versions. The Same principles as custom ROMs actually apply to stock too. Of you have bugs, rule out your data and legacy settings first by wiping data
Sent from my Nexus 5 using Tapatalk
rootSU said:
I always recommend wiping when updating Android versions. The Same principles as custom ROMs actually apply to stock too. Of you have bugs, rule out your data and legacy settings first by wiping data
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah, I know it's a good idea, but I'm always hesitant to do so since my internet speed is around .25 mbps. Redownloading apps takes a looong time. I suppose there's always backup solutions though.
iJimaniac said:
Yeah, I know it's a good idea, but I'm always hesitant to do so since my internet speed is around .25 mbps. Redownloading apps takes a looong time. I suppose there's always backup solutions though.
Click to expand...
Click to collapse
Yeah you can use helium.
Sent from my Nexus 5 using Tapatalk
No issues here
iJimaniac said:
Hello, am I the only one experiencing bugs that I didn't have before since upgrading to 4.4.3?
To be specific: I never had the mm-camera-daemeon bug before updating, now I see it in the battery statistics! I thought 4.4.3 was supposed to fix this, not introduce it for people who previously didn't have it.
Also, this might just be me, but the speaker and headphone volume seem quieter than before, which again, I thought this bug was supposed to be fixed.
I installed the factory image from google with fastboot, but didn't wipe the data.
Any thoughts?
Click to expand...
Click to collapse
I have no issues, but I waited for the OTA and sideloaded it because I didn't want to wipe my data.
Dirty flashing is almost always a bad idea, if you have problems your just going to have to reset your device.
Yet everyone insists on doing it because they can't wait a day for the OTA to drop
Happens every time there's a new Google version put out, tons of people with issues because they dirty flashed the factory image.
Lesson
Wait for the OTA to sideload or install the factory image and let it reset your device as it's designed to do.
movielover76 said:
I have no issues, but I waited for the OTA and sideloaded it because I didn't want to wipe my data.
Dirty flashing is almost always a bad idea, if you have problems your just going to have to reset your device.
Yet everyone insists on doing it because they can't wait a day for the OTA to drop
Happens every time there's a new Google version put out, tons of people with issues because they dirty flashed the factory image.
Lesson
Wait for the OTA to sideload or install the factory image and let it reset your device as it's designed to do.
Click to expand...
Click to collapse
Actually, I flashed it because I had modified the /system partition and my limited understanding of how Nexus devices update told me the ota wouldn't work with a modified system. Is this correct, or does the modified system only keep your device from receiving the ota, not sideloading it? This is the first device I've had that actually receives official updates, so I'm new to this.
Modified system
iJimaniac said:
Actually, I flashed it because I had modified the /system partition and my limited understanding of how Nexus devices update told me the ota wouldn't work with a modified system. Is this correct, or does the modified system only keep your device from receiving the ota, not sideloading it? This is the first device I've had that actually receives official updates, so I'm new to this.
Click to expand...
Click to collapse
If your not stock your right, the OTA will likely fail. You can get away with being rooted, you'll just lose root.
Unfortunately everyone wants to get away without clearing and reseting their device and it leads to problems when people dirty flash the factory image.
If your not stock and want the latest update, your best bet is to bite the bullet and install the full factory image the way it was intended.
Clearing the device at the same time with the factory image, or installing one of the pre-rooted roms that comes out shortly after the new version drops. (Again clearing user data)
It's part of the price that comes with tinkering with your device.
movielover76 said:
If your not stock your right, the OTA will likely fail.
Unfortunately everyone wants to get away without clearing and reseting their device and it leads to problems when people dirty flash the factory image.
If your not stock and want the latest update, your best bet is to bite the bullet and install the full factory image the way it was intended.
Clearing the device at the same time with the factory image, or installing one of the pre-rooted roms that comes out shortly after the new version drops. (Again clearing user data)
Click to expand...
Click to collapse
Alright, good deal! Now I know for next time, thanks