Related
Hello all,
My asus TF300 is crashing all the time. I was on JB 4.2.1 with the original rom. Everything was fine all the time until he crashes, even when he is plugged in the power plug. The problem is that when he crashes he won't get on directly. After a few minites he starts again. Sometime crashes directly again after he is booting. after 30min he will start again and works perfect.
I was tinking to root him and putting a other kernel on it and rom. Still does the crashing part.
Does someone have a solution for this? In standby he does not have the problem.
Code:
Model: ASUS Tranformer Pad TF300T
Android version: 4.2.1
GPS Version: 7.9.11
WIFI Version: 7.1.1.50
Bluetooth version: 11.38
touchscreen version: ELAN-3011-4822
Camera version: TF300T-000128
Kernel Version: [email protected]#13
Build nummer: TF300 CROMi-Xenogenisis 5.4 - 10.6.1.27.5 WW DEODEX
PAD EC-version: PAD-EC20T-0216
Thanks for your answer.
Just tested a battery calibration tool downloaded from google play store. Must charge the battery at 100% and then run the tool. After I downloaded a tool (battery dis-charger.) After 3-5min my tablet falls out. Hope this info helps. Hope anyone has a solution, it was a refurbished tablet and had only 6 months warranty. This happens at 9 months.
snakeboots said:
I was tinking to root him and putting a other kernel on it and rom. Still does the crashing part.
Click to expand...
Click to collapse
You don't need to root before flashing another rom. The "root" bit will be part of the rom you will flash.
Still have the problem. Anyone have a solution that I can try?
Just tested the KatKiss Lolipop rom, still have the same crash problem, i think it's called "Sleep of dead" but can't find a solution for it. Now with the new rom sometime it takes longer to crash and then there are times that it's after a couple of seconds. Anyone have any idea's?
Just downloaded again the firmware from the ASUS website. And installed the blob file with fastboot. Seems do to fine now.
snakeboots said:
Still have the problem. Anyone have a solution that I can try?
Click to expand...
Click to collapse
Sleep of Death (SODs) usually occur because of a misbehaving app. Run a logcat before the SOD occurs and you might be able to figure out which app is messing with the sleep.
Hello everybody,
I have the same problem with my TF300T too.
It make a little electric sound when it crash, but I have the feeling it's not a sleep of death.
It now with katkiss room, it very fast but it crash
If somebody has a solution ?
Thanks a lot
It make a little electric sound when it crash, but I have the feeling it's not a sleep of death.
Click to expand...
Click to collapse
That's exactly what it does, after installing the original rom it works good for the first time. But after that I had again the same problem. It's going faster and faster. Really annoying. Hope someone has a solution for this problem, because it's a good tab but with this problem I can put it in the garbage.
Still having the same problem.
- Formatted all with fastbood and installed the official WW rom, but no success.
- downgraded the bootloader to 4.1 without success.
- Updated the bootloader again and installed Omnirom 5.1 but still no success.
Does anyone have an other idea what I can do?
For the moment when he cut's the power I can't get it on and must wait a long time. Sometimes the low battery logo comes on but what is strange is when I plug in the power charger and charges it for 5 min I can boot it. When I go to TWRP I see 90% also when I boot in android I see +/-90% so really don't know what this means. Does anyone have an Idea how I can bring again life to my asus tab tf300t? (the power cut's also in TWRP or at boot. It depends, when he cut's the power and I restart the tab it seems to cut faster and faster until I charge it a little.
Info about tab: I'ts a refurbished tab bought with 6 months warranty, the problem started at month 6 - 7., so no warranty.
Hello, does anyone have a solution that I can try for my wonderfull TF300T crashing problem?
Thanks
I updated my Nexus 5 today, using the official firmware + fastboot to flash all but the user parition.
Everythink worked fine, applications get updated, phone is booting and running.
But the device is getting hot, even 15 minutes after flashing. Anyone else monitored this behavior ?
Warlord711 said:
I updated my Nexus 5 today, using the official firmware + fastboot to flash all but the user parition.
Everythink worked fine, applications get updated, phone is booting and running.
But the device is getting hot, even 15 minutes after flashing. Anyone else monitored this behavior ?
Click to expand...
Click to collapse
Do you run Greenify? The stable version was causing that on mine. It doesn't work with Lollipop. There's a beta version that seems to work fine.
After a clean shutdown and restart, the warming has gone.
I guess something hung there in background and caused CPU load.
Hi everyone.
I recently replaced my shatter LCD and was subsequently trapped in a bootloop. I began to wonder if the LCD I ordered was defective, so I removed the new screen and attached the old one. The device booted up fine (as fine as a devastated LCD screen would permit anyway). I detached the broken screen and reattached the new one and the device seems to be working fine.
I am now worried that shutting down the device will cause it to enter a boot loop again. Would reflashing the stock rom solve this issue? Has Motorola installed a failsafe that would prevent devices from booting up if there is a replacement screen attached to the logic board??
I am having the same issue, did you find a solution?
mike29892 said:
I am having the same issue, did you find a solution?
Click to expand...
Click to collapse
Unfortunately, no. After replacing the screen I've opted to keep the device on. Have you turned your phone off after getting it to work with the new screen?
ElonNoir said:
Unfortunately, no. After replacing the screen I've opted to keep the device on. Have you turned your phone off after getting it to work with the new screen?
Click to expand...
Click to collapse
I restored the phone to 5.1 and it booted up fine. Unfortunately my new screen seems defect, it has phantom touches and is not accurate. Perhaps with 6.0 a screen hardware test was added on bootup and both of our devices are failing it?
mike29892 said:
I restored the phone to 5.1 and it booted up fine. Unfortunately my new screen seems defect, it has phantom touches and is not accurate. Perhaps with 6.0 a screen hardware test was added on bootup and both of our devices are failing it?
Click to expand...
Click to collapse
Were the phantom touches present before restoring to 5.1? I'm running Marshmallow right now and I don't have a phantom touch issue. I've thought about reflashing stock rom and updating back to 6.0 but if a hardware test was indeed added, perhaps Flashing CM will allow the phone to operate free of bugs. Maybe that's just wishful thinking.
ElonNoir said:
Were the phantom touches present before restoring to 5.1? I'm running Marshmallow right now and I don't have a phantom touch issue. I've thought about reflashing stock rom and updating back to 6.0 but if a hardware test was indeed added, perhaps Flashing CM will allow the phone to operate free of bugs. Maybe that's just wishful thinking.
Click to expand...
Click to collapse
I couldn't even get the device to boot before restoring to 5.1. I was on 6.0 broke my screen and then replaced the screen. After turning the phone back on it entered a boot loop. I restored to 5.1 and it was able to boot, but the touch screen was all wonky, and getting phantom touches. I tried to flash 6.0 again and it just put me in the boot loop again.
Same issue here on XT1540. Ordered from the most popular seller on Ebay. I'm wondering running CM might fix it.
Update - unlocked bootloader and flashed CM12 - no issues any more with new LCD. Maybe some sort of hardware check with the stock ROM? Tested the digitizer with the "pointer location" dev tool and it was accurate.
Update 2 - can't seem to boot into TWRP with the new screen and CM12 flashed. Rom boots with no issues and runs with no issues though. Old broken screen boots TWRP no problem. Not sure why this is. Can boot cyanogen recovery but that doesn't seem to flash correctly.
fresh cut vegetables said:
Same issue here on XT1540. Ordered from the most popular seller on Ebay. I'm wondering running CM might fix it.
Update - unlocked bootloader and flashed CM12 - no issues any more with new LCD. Maybe some sort of hardware check with the stock ROM? Tested the digitizer with the "pointer location" dev tool and it was accurate.
Update 2 - can't seem to boot into TWRP with the new screen and CM12 flashed. Rom boots with no issues and runs with no issues though. Old broken screen boots TWRP no problem. Not sure why this is. Can boot cyanogen recovery but that doesn't seem to flash correctly.
Click to expand...
Click to collapse
Sorry for the delayed response. How did you manage to flash a ROM if the device goes into bootloop when turned off or rebooted? This is what is keeping me from doing it flashing CM. I fear the device will reboot during the flashing process and it will be borked and stuck in a bootloop.
ElonNoir said:
Sorry for the delayed response. How did you manage to flash a ROM if the device goes into bootloop when turned off or rebooted? This is what is keeping me from doing it flashing CM. I fear the device will reboot during the flashing process and it will be borked and stuck in a bootloop.
Click to expand...
Click to collapse
It won't reboot until the OS starts loading, as long as you can access TWRP you should be safe to flash a custom ROM... it seems to be a known issue that a non-Moto replacement screen will bootloop the OS with Marshmallow but not Lollipop, unknown if CM13 and ROMs based it (which is all custom MM ROMs) will bootloop or not.
Best solution is replace it with an OEM Moto screen, it won't bootloop, only 3rd party ones do.
I am on Oxygen OS 9.5.8.GM21AA. Recently I met the random restart problem. And it become more and more frequent. I have Magisk and EdXposed installed, but I have not update or install new modules recently.
The problem most time happened when I swipe from bottom screen to switch apps. And the whole phone become black. And several seconds later. It will automatically restart. The phone is showing "The phone is restarting" message.
I was tried to disable EdXposed modules one by one, but still not found any incompatible.
einverne said:
I am on Oxygen OS 9.5.8.GM21AA. Recently I met the random restart problem. And it become more and more frequent. I have Magisk and EdXposed installed, but I have not update or install new modules recently.
The problem most time happened when I swipe from bottom screen to switch apps. And the whole phone become black. And several seconds later. It will automatically restart. The phone is showing "The phone is restarting" message.
I was tried to disable EdXposed modules one by one, but still not found any incompatible.
Click to expand...
Click to collapse
Are you using a custom kernel? Updating to 9.5.9 might also help.
harpin14789 said:
Are you using a custom kernel? Updating to 9.5.9 might also help.
Click to expand...
Click to collapse
I am using ElementalX kernel. And i just update this kernel to 1.11, let's me check any problem than.
einverne said:
I am using ElementalX kernel. And i just update this kernel to 1.11, let's me check any problem than.
Click to expand...
Click to collapse
I also have the same issue as you.
This issue is a kernel related issue, oneplus is aware and will push an update in the near future.
As far I know, Fraken kernel is the only that seems to have fixed this issue, so I suggest you flash that, atleast till, OP pushes an update to fix this issue. I have tried all the kernel 7pro and have the issue with every single one. But hvae not the issue in over a week with fraken.
Good Luck!:good:
had this device all of a week (barely), seemed to work great out of the box, have left it stock intentionally.
take the April security update, reboot.
Have completely lost pinch zoom / multitouch and it seems as though the screen's settings, software or combination are completely misaligned / out of whack regarding touch input.
It's the kind of behavior you get when you have a droplet on your screen and the phone screen is getting erratic input... like it's compromised or fragmented somehow.... I've increased sensitivity which made the phone more usable, but I can barely use the bottom row of my home screeen. If I switch to left hand and try my L thumb, it better detects the input (if I aim WAY LOW). Almost like the calibration for the screen touch has been completely FUBAR.
Hoping custom software and lack of OTA updates fixes this? Has this community seen this issue and are custom ROMs a way out of the mess, or is this a hardware issue that absolutely requires the device to be returned and replaced? Seems odd the change happened with no physical change to the phone.
Same issue here when updating. Complete factory reset fixed mine
@beflythis hey did you figure the fix out? I have a similar issue. Factory reset didn't help me
Got a screen replacement from B2X and updated it to Android 13 subsequently. Since the update or repair, multi-touch has been ruined, cannot pinch-to-zoom, and the keyboard is very buggy since screen responsiveness seems to have been compromised. I flashed android 12 on it again using flash.android but the issue still persisted. I am unable to figure out a solution. Is it a hardware or software issue? Once in a while after a restart the pinch-to-zoom will work and keyboard will work fine before it gets ruined again. Please tell me what to do
Update: Downgrading the phone to Android 10 fixes everything. I. DONT. KNOW. HOW. THO
@anshuuu03 so after downgrading the phone to Android 10, can you update it to Android 12 back? Or should you always use Android 10 now to have sensors working correctly?
anshuuu03 said:
Update: Downgrading the phone to Android 10 fixes everything. I. DONT. KNOW. HOW. THO
Click to expand...
Click to collapse
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
This is definetly an issue with what seems to be the software, not sure exactly what is wrong though (I dont know too much about kernel driver code),
anshuuu03 said:
Got a screen replacement from B2X and updated it to Android 13 subsequently. Since the update or repair, multi-touch has been ruined, cannot pinch-to-zoom, and the keyboard is very buggy since screen responsiveness seems to have been compromised. I flashed android 12 on it again using flash.android but the issue still persisted. I am unable to figure out a solution. Is it a hardware or software issue? Once in a while after a restart the pinch-to-zoom will work and keyboard will work fine before it gets ruined again. Please tell me what to do
Click to expand...
Click to collapse
Exacty same issue, got a screen replacement from UbreakiFix, wonder if it might be a batch of screens that are bad on specific kernel drivers? I honestly dont know.
fbievan said:
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
Click to expand...
Click to collapse
Do let me know if it works. It would be a life saver
fbievan said:
Exacty same issue, got a screen replacement from UbreakiFix, wonder if it might be a batch of screens that are bad on specific kernel drivers? I honestly dont know.
Click to expand...
Click to collapse
I think downgrading to Android 10 has worked for almost everyone facing this problem
vovapolischuk said:
@anshuuu03 so after downgrading the phone to Android 10, can you update it to Android 12 back? Or should you always use Android 10 now to have sensors working correctly?
Click to expand...
Click to collapse
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
fbievan said:
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
Click to expand...
Click to collapse
Now that i know that im now going crazy, and atleast one other person has very very similar story to mine, there needs to be a proper fix. I do know that android 10 and android 11 do have different touchscreen drivers. Downgrading then upgrading back wont work, atleast to my knowledge. I've done plenty of looking, and just don't know whats wrong. If any kernel devs that know their way around touchscreen drivers, and pixel 4as. Would be a life saver. But I have little idea of whats actaully going wrong.
anshuuu03 said:
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
Click to expand...
Click to collapse
Yep, downgrading again to Android 10 alllows multittouch to work
anshuuu03 said:
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
Click to expand...
Click to collapse
Update: I actually got it working on Android 12L. So, I downgraded to Android 10, from googles flash tool. Then upgraded one by one. And for some reason that seemingly worked. Can u confirm?
fbievan said:
Update: I actually got it working on Android 12L. So, I downgraded to Android 10, from googles flash tool. Then upgraded one by one. And for some reason that seemingly worked. Can u confirm?
Click to expand...
Click to collapse
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
anshuuu03 said:
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
Click to expand...
Click to collapse
I flashed from android 10 to 11 t0 12 to 12L. Didnt try 13 because i use lineageOS. Also another note is that i did flash a build of the holy dragon kernel on Android 10. But that should influence it.
fbievan said:
I flashed from android 10 to 11 t0 12 to 12L. Didnt try 13 because i use lineageOS. Also another note is that i did flash a build of the holy dragon kernel on Android 10. But that should influence it.
Click to expand...
Click to collapse
Make sure to test, test, and test
anshuuu03 said:
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
Click to expand...
Click to collapse
Can I ask: has that worked for you?
fbievan said:
Can I ask: has that worked for you?
Click to expand...
Click to collapse
I think I will try and do the 10 > 11 > 12 > 13 in a few days. I am stuck with some work and cannot afford to keep resetting my phone atm. But I will update here whatever is the update on that