Database Info

How to.know if i recieved a bad TF300T

Hi, for some reason my Tf300 is behaving weird.
It becomes sluggish, crashes, doesn't respond to my touch.
Is there any diagnostics I can run?
It's weird, my galaxy note is a lot faster than this tablet, even with "only " a dual core.
Is this normal?
It happens more inside Dolphin Browser and when there is an update from the store happening, it freezes for seconds. Again, this is my fourth android device and none have had this issue... Even my kindle fire with cm7 was faster.
Should I restore to factory settings?

Install the latest Stock ROM and then factory reset and see if the problem is still there. Don't root or install custom recovery until you know its not a faulty unit.

How do I do that? Do I just check for updates? Any links?

http://support.asus.com/download.as...nsformer+Pad+TF300T&hashedid=8BmzkQ4yoz5WzBrW
If you are planning to ROOT your device you will need to wait for the OTA updates. See the Dev Forum for Rooting on .17 firmware.
If you are planning to unlock the bootloader you can apply the manual updates
http://support.asus.com/download.as...nsformer+Pad+TF300T&hashedid=8BmzkQ4yoz5WzBrW

Is it bad to cold boot frequently?
Sent from my ASUS Transformer Pad TF300T using XDA

Northern-Loop said:
Install the latest Stock ROM and then factory reset and see if the problem is still there. Don't root or install custom recovery until you know its not a faulty unit.
Click to expand...
Click to collapse
How can I keep my app data/ files if I factory reset? Could I copy it all to an SD card?
Sent from my ASUS Transformer Pad TF300T using XDA

No, I just want stock Asus. I like to keep the original os as long as possible and then root and change roms.
Anyway how do I install it? I just checked and it seems I have the latest version already installed

KindaUndisputed said:
How can I keep my app data/ files if I factory reset? Could I copy it all to an SD card?
Sent from my ASUS Transformer Pad TF300T using XDA
Click to expand...
Click to collapse
You could use the ASUS Backup program but to keep a copy.
But I wouldnt restore anything because it could be an application causing the slow downs.
Have you click on the performance mode in the bottom right of the screen?

Neuralgia said:
No, I just want stock Asus. I like to keep the original os as long as possible and then root and change roms.
Anyway how do I install it? I just checked and it seems I have the latest version already installed
Click to expand...
Click to collapse
So should I just restore it or download the file? If I download how do I install it?

Neuralgia said:
So should I just restore it or download the file? If I download how do I install it?
Click to expand...
Click to collapse
If you go to Settings, About and see the build version of .29 you are on the latest.
So you don't need to update.
PDF explaining the updates http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF201/e7203_TF201_Update_SOP.pdf

Just kind of general fyi - the Intl one x apparently has scaling issues, it uses the same processor as us. If your rooted, try set CPU or something of the like, and bump up the minimum clock rate. Might eat battery, but its worth a try
Sent from my SGH-T989 using XDA

This thread has me worried now...
I exchanged my 16G TF300 for a 32G the other day and noticed some apps were crashing that weren't before. Everything should be clean -- just installed apps from the market and setup email.
I'm a bit confused by the concept in general. Is it common that devices will ship with bad hardware that causes intermittent issues?
EDIT: I also updated the firmware to the latest, but that was also the case with my previous 16G so I'm not expecting that to be related.

CHeck out the app system tuner. You can monitor the effects of different processes, apps, etc, and find out what is causing these problems and whether theyre related to your build,prop , cpu, or if they sold you a lemon

If your apps are acting up wipe or cold boot the *****
Sent from my VS910 4G using xda premium

Stop Jellybean Update

Honest ive been searching for an hour, how do i stop the update from happening. Not permanently, hopefully like blocking the update app with Titanium like i did on my Galaxy S3. Also, the location of the already downloaded file so i can delete it. Thanks

Honestly!!?? Is this really that dumb of a question? I honestly still cant find how to block the JB update. Please anybody?

I would love to know that too. I really don't want to hit the update by mistake...

Honestly, just make sure you honestly don't click the update button. Honestly that's all there honestly is to it...honest!:laugh:

Honestly

The update file (dlpkgfile) is in the/cache/ folder.
And I don't know if this will stop the OTA or if this will completely F up your device but the Dmclient (or is it cmclient) system app can probably be disabled. It handles the OTA's

After some research I found that renaming otacerts.zip (in /system/etc/security/) with a .bak at the end could prevent the update to start but the notification is still here.
I tried to stop the Firmware Update Utility in app manager, even by renaming it with a .bak in /system/app/ . The notification is still here, but it seems that the popping window is not showing. Time will tell.
I saw somewhere that renaming the fingerprint line in build.prop woud work, luring the update into thinking the firmware is already up to date, but since I never touched this file (android newbie here!) I will wait for someone more experienced in modifying that kind of things...

If you are rooted, edit your build.prop (back up your original) and then tell the tablet to update. The update will fail (red triangle) and will reboot into ICS. The notification should go away and you will have to update manually.

Ok but what to edit in build.prop?

Gamlus said:
Ok but what to edit in build.prop?
Click to expand...
Click to collapse
Check this thread in the development section. There is a tweaked build.prop that I used before my upgrade. That is what caused my OTA update to fail. BE sure to use the correct file and back up your current build.prop.
http://forum.xda-developers.com/showthread.php?t=1641219

Yes !
I didn't actually changed the whole build.prop, but I downloaded the stock JB build.prop to take the fingerprint line.
So, after a backup of my build.prop, I changed this line :
ro.build.fingerprint=asus/WW_epad/EeePad:4.0.3/IML74K/WW_epad-9.4.3.30-20120604:user/release-keys
With this one :
ro.build.fingerprint=asus/WW_epad/EeePad:4.1.1/JRO03C/WW_epad-10.4.2.9-20120809:user/release-keys
And now, no more notification, after a reboot and a failed install of JB.
Thank you !

turdbogls said:
The update file (dlpkgfile) is in the/cache/ folder.
And I don't know if this will stop the OTA or if this will completely F up your device but the Dmclient (or is it cmclient) system app can probably be disabled. It handles the OTA's
Click to expand...
Click to collapse
ok guys this does work, first remove the update file, then use a root system app freezer and freeze dmclient, reboot, if this does not work, unfreeze dmclient, then change your build.prop to show the blueprint of your asus tf300t or tf300tg tablet on jelly bean, reboot, then freeze dmclient, reboot, and that will remove any chances of getting an OTA or accidentally messing up the device, after this change your build.prop back to original state, reboot, and everything will be gone.
note i have tested the second method, and its working perfectly, no glitches, no FC's
Sent from my ASUS Transformer Pad TF300T using xda app-developers

with my previous returned tf300: after i turned it on the first time it downloaded the ICS .30 firmware and asked me to update, i installed it. then i was curious why it did not download the JB update, so i went to check update manually, it started downloading the jb update and i had to update to jb. after a few days because of hardware problem i returned it.
my new tf300 came yesterday, and the same thing above happened, i updated to ICS .30, now i try to remind myself to not accidentally manually check for update, sounds weird, right? i see cmclient and dmclient always running but it never knows that there's a update lol. and i usually don't go to about tablet so i guess i won't do manual update accidentally.

bige914 said:
ok guys this does work, first remove the update file, then use a root system app freezer and freeze dmclient, reboot, if this does not work, unfreeze dmclient, then change your build.prop to show the blueprint of your asus tf300t or tf300tg tablet on jelly bean, reboot, then freeze dmclient, reboot, and that will remove any chances of getting an OTA or accidentally messing up the device, after this change your build.prop back to original state, reboot, and everything will be gone.
note i have tested the second method, and its working perfectly, no glitches, no FC's
Sent from my ASUS Transformer Pad TF300T using xda app-developers
Click to expand...
Click to collapse
Just wanna say thanks for this. Deleting the update and freezing the dm client with titanium seems to be working. And hasnt caused any other issues as of yet. I think its stupid that we dont have an opt out option if we like the way our tablets are now. We should not be forced to change our tablets that we paid for and OWN!

Gam3r 4 Life said:
Just wanna say thanks for this. Deleting the update and freezing the dm client with titanium seems to be working. And hasnt caused any other issues as of yet. I think its stupid that we dont have an opt out option if we like the way our tablets are now. We should not be forced to change our tablets that we paid for and OWN!
Click to expand...
Click to collapse
Thanks +1
Worked for me too...

neur28 said:
Thanks +1
Worked for me too...
Click to expand...
Click to collapse
Does your stock email app work now? After freezing the DM client the stock email app gets stuck at waiting for sync.
Nevermind. I defrosted the dmclient and email still didnt work. So I rebooted. Saw the update again. So I refroze dmclient, then restored my email app and data in titanium and that fixed it.

I'm glad I helped all of you and enjoy your tablets as I am :3 screw Asus JB update we D block that yo
Sent from my HTC Ruby using xda app-developers app

Random freeze and reboots

So recently after updating to 4.1, I have been experiencing random freezes then reboots. I factory reset my tab 3 times and none seem to have fixed it. Also it appears it only happens in performance mode. Has anyone else experienced this? If so, have you found a fix?
Thanks
Sent from my MB860 using xda app-developers app

pfoxdizzle said:
So recently after updating to 4.1, I have been experiencing random freezes then reboots. I factory reset my tab 3 times and none seem to have fixed it. Also it appears it only happens in performance mode. Has anyone else experienced this? If so, have you found a fix?
Thanks
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Did you make any tweaks on the system before your update? I.e. rooted or custom rom system with changing build.prop, MinFree, or anything that basically you can only do after rooting?

No changes. Completely fresh and.un modified tablet
Sent from my MB860 using xda app-developers app

Honestly, I have gotten some and I'm fresh totally stock just got mine. However, I stopped connecting it to dock and uninstalled songza and MX player. Its a shot in the dark but lets see if any reboots, otherwise back to amazon.

pfoxdizzle said:
So recently after updating to 4.1, I have been experiencing random freezes then reboots. I factory reset my tab 3 times and none seem to have fixed it. Also it appears it only happens in performance mode. Has anyone else experienced this? If so, have you found a fix?
Thanks
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
I'm curious as to how much RAM your tablet is using after a cold boot in balanced or perf mode.
Mine stays between 579 and 654mb no matter what.
Haven't had a crash or a freeze since the first 3 days of ownership.
Well that's a lie...I had a lot of freezes and crashing with sygic and earlier editions of some browsers.

pfoxdizzle said:
So recently after updating to 4.1, I have been experiencing random freezes then reboots. I factory reset my tab 3 times and none seem to have fixed it. Also it appears it only happens in performance mode. Has anyone else experienced this? If so, have you found a fix?
Thanks
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
I thought it was just me. I've been playing The Bard's Tale on it and got the update the same night. I, too, have noticed random reboots where the game will freeze, and then 5 seconds later the tablet is rebooting. I honestly thought it was the game, but since you're saying it happens to you on Performance mode only, and that is exactly where I am as when I am playing the game, maybe it is performance mode and not hte game causing mine as well.
if that is the case, chalk me up for these random reboots as well.
pfoxdizzle said:
No changes. Completely fresh and.un modified tablet
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Mine was far from fresh, but only rooted, no other mods made.
pceasar said:
Honestly, I have gotten some and I'm fresh totally stock just got mine. However, I stopped connecting it to dock and uninstalled songza and MX player. Its a shot in the dark but lets see if any reboots, otherwise back to amazon.
Click to expand...
Click to collapse
I don't think that will help as 1) I have neither of those two apps, and 2) mine happened when I was not connected to a dock at all.

My tablet after JB update, has been getting freezes. Screen is black but lit and I have to reboot :\

Aria807 said:
My tablet after JB update, has been getting freezes. Screen is black but lit and I have to reboot :\
Click to expand...
Click to collapse
To fix this reboot and screen blank out, you guys need to reflash the full version of JB.

buhohitr said:
To fix this reboot and screen blank out, you guys need to reflash the full version of JB.
Click to expand...
Click to collapse
Might not be a bad idea. But a full install won't allow us to use root keeper methods, so we'd then have to wait for a new root method, right?
I'll deal with the idiosyncrasies until i can root JB and then "blob" my pad (I've been dying to say that, can't you tell?).
Sent from my rooted BIONIC running ICS 6.7.247 (!) via Tapatalk 2

johnlgalt said:
Might not be a bad idea. But a full install won't allow us to use root keeper methods, so we'd then have to wait for a new root method, right?
I'll deal with the idiosyncrasies until i can root JB and then "blob" my pad (I've been dying to say that, can't you tell?).
Sent from my rooted BIONIC running ICS 6.7.247 (!) via Tapatalk 2
Click to expand...
Click to collapse
To root a JB locked bootloader=NO, but for unlocked bootloader=YES. Another way to solve the reboot/screen issue and keep root is to downgrade to .30 (full version), root, then OTA root keeper to save root then let the JB OTA upgrade back to JB, then restore root.

buhohitr said:
To root a JB locked bootloader=NO, but for unlocked bootloader=YES. Another way to solve the reboot/screen issue and keep root is to downgrade to .30 (full version), root, then OTA root keeper to save root then let the JB OTA upgrade back to JB, then restore root.
Click to expand...
Click to collapse
That is exactly what I did. I'll test later this evening, but so far it has been a lot snappier *and* no random reboots.
But, I've also not run performance mode either.
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk

johnlgalt said:
That is exactly what I did. I'll test later this evening, but so far it has been a lot snappier *and* no random reboots.
But, I've also not run performance mode either.
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk
Click to expand...
Click to collapse
Also highly recommend to install browse2ram, make all your browsers(stock included), kick ass!!!

buhohitr said:
To root a JB locked bootloader=NO, but for unlocked bootloader=YES. Another way to solve the reboot/screen issue and keep root is to downgrade to .30 (full version), root, then OTA root keeper to save root then let the JB OTA upgrade back to JB, then restore root.
Click to expand...
Click to collapse
What's the point of doing this? I was already on .30 to begin with, ran Debugfs rooted .30 and OTA rootkeeper backed up, and I got the OTA update from JB a week later, which had the SOD issue. Why downgrade and upgrade?

Aria807 said:
What's the point of doing this? I was already on .30 to begin with, ran Debugfs rooted .30 and OTA rootkeeper backed up, and I got the OTA update from JB a week later, which had the SOD issue. Why downgrade and upgrade?
Click to expand...
Click to collapse
The point is it's going to solve your random reboot/blank screen issue. Most of people did exactly what you did included myself, but once you are on JB and experiencing reboot and blank screen, you need to reflash because the install did not done correctly some how. If you reflash a full version of JB, it will fixed the issue but then you don't have root, this is not a problem if you're unlocked. So if you still have locked bootloader, you need to downgrade with full version of .30 then re root. when you install a full version it automatically wipe for you so you don't need to wipe before downgrade. Once you have a fresh install of .30, now you can use OTA to upgrade to JB and keeping root.

Ah gotcha. Well in this case, I might as well just unlock my bootloader and flash [ROM][10/3][JB4.1.1] - Stock Root Odex / De-Odex - 10.4.4.16 Base since it's stock based minus bloatware?

Aria807 said:
Ah gotcha. Well in this case, I might as well just unlock my bootloader and flash [ROM][10/3][JB4.1.1] - Stock Root Odex / De-Odex - 10.4.4.16 Base since it's stock based minus bloatware?
Click to expand...
Click to collapse
Sure you could do that, but I'm waiting for Zeus Rom. This rom is amazing with I/O.

Actually, could the problem be the idle clock speed? I don't recall the TF700 having a 51mhz speed. I thought lowest multiplier was 102mhz. Perhaps that's why it is freezing/sod
I'm gonna raise my min clock speed at 102mhz and see if it freezes any more
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app

buhohitr said:
To fix this reboot and screen blank out, you guys need to reflash the full version of JB.
Click to expand...
Click to collapse
Well, I had the same issue on ICS stock and custom rom and JB so I don't think this is anything to do with reflashing, but our old friend IO.
Like people have mentioned before ,change the number of background processes to 4.

[Q] About this newly introduced wifi problem

Hello guys,
my brand new nexus 5 just came back from replacement and worked flawlessly for a week or two,
The thing it that after the update, i had this strange "Stuck at turning wifi on bug".
I tried everything i saw on all the forums i managed to find and google usually tell users to replace their devices.
The thing is i just flashed the radio-hammerhead-M8974A-1.0.25.0.17 Radio, and at reboot i was able to turn wifi on.
The main problem now is, that the device freeze 15 second after succefully showing me nearby wifi networks, and then proceed to reboot.
I think many users are in the same situation, has someone managed, somehow, to patch the error ? I can't even tell if this is a software or hardware related glitch, but more and more users are experiencing troubles and i think google should talk more about it.

The majority of users don't have this problem. I don't. What else have you done to the device? What have you flashed?
Sent from my Nexus 5 using XDA Free mobile app

no such issues here.

I've seen this issue on various phones and it's always been either:
1) Dodgy /data (user data, apps etc)
2) Hardware problem.
I have not had this issue on the N5

jd1639 said:
The majority of users don't have this problem. I don't. What else have you done to the device? What have you flashed?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Of course i did not mean that all users where on the same case,
what i said, is that i already found many thread of people experiencing the same "undefined behaviour", which mean this is not a random bug, and that it can definitly happen to anybody's device.
My phone was using the last stock rom, the bootloader was locked and it never was altered in any ways when the problem started to appear.
Then, i did a hardreset, i unlocked the bootloader, i flashed custom roms (PA, MIUI, CYANNOGEN), then i flashed an older rom's radio image and the wifi started to activate again, but to reboot 15 sec after.
then i went back to a PA rom, and exactly the same bug occur.

weacd said:
Of course i did not mean that all users where on the same case,
what i said, is that i already found many thread of people experiencing the same "undefined behaviour", which mean this is not a random bug, and that it can definitly happen to anybody's device.
My phone was using the last stock rom, the bootloader was locked and it never was altered in any ways when the problem started to appear.
Then, i did a hardreset, i unlocked the bootloader, i flashed custom roms (PA, MIUI, CYANNOGEN), then i flashed an older rom's radio image and the wifi started to activate again, but to reboot 15 sec after.
then i went back to a PA rom, and exactly the same bug occur.
Click to expand...
Click to collapse
Flash a full factory image back to latest stock. If it still happens, send it for repair

rootSU said:
Flash a full factory image back to latest stock. If it still happens, send it for repair
Click to expand...
Click to collapse
Already done, guess i have no choice.
Then i would like to tell all the peoples who are experiencing the same experience to replace their phone using google's warranty service.
Some peoples managed to fix the bug for a time with a lucky trick, but it always end to come back.

weacd said:
Already done, guess i have no choice.
Then i would like to tell all the peoples who are experiencing the same experience to replace their phone using google's warranty service.
Some peoples managed to fix the bug for a time with a lucky trick, but it always end to come back.
Click to expand...
Click to collapse
If it comes back while on stock rom then it's a problem with the device and you should rma it. That's what warranty is for
Sent from my Nexus 5 using XDA Free mobile app

Question Help ! No wifi and bluetooth scanning

Hi friends,
Since yesterday, my wifi and bluetooth don't work anymore. When enabling them, it scans nothing . I've made a factory reser without any psuccess !
Never seen an issue like this on any phone...
Thanks for your help guys

Have you tried restarting the phone? I had 1 time yesteday too, suddenly, the phone was idle, and when I checked Wifi found nothing. Restarted and then it works again. Not sure if related to March update or some other stuffs

creezalird said:
Have you tried restarting the phone? I had 1 time yesteday too, suddenly, the phone was idle, and when I checked Wifi found nothing. Restarted and then it works again. Not sure if related to March update or some other stuffs
Click to expand...
Click to collapse
Restarted and also factory reseted

YassGo said:
Restarted and also factory reseted
Click to expand...
Click to collapse
Wow...after a factory reset, that's pretty much it!
You can try doing the reset network settings button (you can search it in the search bar in Settings or find it in the Internet setting on top right button [wrench and reset circle]), but I can't imagine it doing better than a factory reset.
The best/last thing that can be suggested, since it states you are rooted in your sig, is to flash the latest Full Factory image (March) and/or with the "-w" intact (since you stated that you did a factory reset so I imagine your phone is wiped anyways) and see if that doesn't fix the issue. The best 3 methods to achieve this is using the online Android Flash Tool, the tool PixelFlasher that can be found here on XDA, or manually using platform-tools (you must've used one of these in the past to be rooted, so I assume you're familiar).
Hopefully you get it figured out. Worst case, the phone is still under manufacturer's warranty and you should be able to get it replaced with a refurbished if it truly isn't resolved...

simplepinoi177 said:
Wow...after a factory reset, that's pretty much it!
You can try doing the reset network settings button (you can search it in the search bar in Settings or find it in the Internet setting on top right button [wrench and reset circle]), but I can't imagine it doing better than a factory reset.
The best/last thing that can be suggested, since it states you are rooted in your sig, is to flash the latest Full Factory image (March) and/or with the "-w" intact (since you stated that you did a factory reset so I imagine your phone is wiped anyways) and see if that doesn't fix the issue. The best 3 methods to achieve this is using the online Android Flash Tool, the tool PixelFlasher that can be found here on XDA, or manually using platform-tools (you must've used one of these in the past to be rooted, so I assume you're familiar).
Hopefully you get it figured out. Worst case, the phone is still under manufacturer's warranty and you should be able to get it replaced with a refurbished if it truly isn't resolved...
Click to expand...
Click to collapse
Yesterday I dirty flashed March update bmand disabled verity stuff. It forced me to format data. Is it enough or is there a better clean flash way ?
Btw I tried the reset network thing without success

YassGo said:
Hi friends,
Since yesterday, my wifi and bluetooth don't work anymore. When enabling them, it scans nothing . I've made a factory reser without any psuccess !
Never seen an issue like this on any phone...
Thanks for your help guys
Click to expand...
Click to collapse
YassGo said:
Yesterday I dirty flashed March update bmand disabled verity stuff. It forced me to format data. Is it enough or is there a better clean flash way ?
Btw I tried the reset network thing without success
Click to expand...
Click to collapse
Mmmm...when you stated you "factory reset", it wasn't clear whether it was from the OS system setting or when flashing...
I don't think there is a "better clean" way to flash and/or reset the phone. If you're not flashing/sideloading OTA (which you aren't)...
It (reset network) was a very long shot, but worth exploring just in case it hadn't been tried yet...
I mean, I guess you can try Android Flash Tool and even go as far as to flash to both slots and relock bootloader to get a pure, stock status and see if the problem truly sticks that way. You've already wiped the phone, so I doubt this could hurt or you lose anything important at this point. But I can't imagine dirty flashing the latest March update (or even including disabling the verity stuff) wouldnt've addressed or reset things to set the issue straight...
If it's still there after relocking the bootloader and flashing to both slots, then it's warranty exchange time (if you ever want to resolve the issue)...
*most likely the flashing somehow wrecked the system board radio enough...
If/When this works, you'll need go through the trouble of unlocking the bootloader, and reflashing the Full Factory image with disabling the verity & validation stuff, before rooting again.

Ok I think it's a hardware problem. When I shake my phone, I hear something moving.
I dropped it from my bed saturday night. The wifi module must be disconnected.
Let's send it to Google....

YassGo said:
Ok I think it's a hardware problem. When I shake my phone, I hear something moving.
I dropped it from my bed saturday night. The wifi module must be disconnected.
Let's send it to Google....
Click to expand...
Click to collapse
Are you sure that what you are hearing move when you shake the phone is just the OIS for the camera? All phones with OIS will make some noise when you shake them.

jaseman said:
Are you sure that what you are hearing move when you shake the phone is just the OIS for the camera? All phones with OIS will make some noise when you shake them.
Click to expand...
Click to collapse
I don't know my friend. Google will send me the return process tomorrow. They told me 7 to 10 days for repairing. Why did I sell my old oneplus ?

YassGo said:
I don't know my friend. Google will send me the return process tomorrow. They told me 7 to 10 days for repairing. Why did I sell my old oneplus ?
Click to expand...
Click to collapse
I have had several OnePlus phones and they have all been great for me! However, I am having no problems with my 7 Pro either so....YMMV