Related
Hi, I recently changed to insertcoin for a week or so and I started getting the issues with unlocking, apps not responding to touch and such. So I got annoyed and I decided to compile myself a Rom, and since then I never got a touch screen issue again. It's been 2 weeks. So is the touchscreen issue a hardware problem or a software problem? And have any of you experience this before ?
Sent from my own custom Rom for sensation. 200mb free :3
illuminarias said:
Hi, I recently changed to insertcoin for a week or so and I started getting the issues with unlocking, apps not responding to touch and such. So I got annoyed and I decided to compile myself a Rom, and since then I never got a touch screen issue again. It's been 2 weeks. So is the touchscreen issue a hardware problem or a software problem? And have any of you experience this before ?
Sent from my own custom Rom for sensation. 200mb free :3
Click to expand...
Click to collapse
It seems to be software related because I had the problem with my stock rom, after installing TouchScreen Booster from the market, it fix it.
http://www.xda-developers.com/android/galaxy-nexus-gets-ics-4-0-4-update/
We'll most likely get it once the sources are updated to 4.0.4. It looks like a lot of things have changed in this build too. Maybe performance will increase on our phones?
Source has been pushed.
Sent from my Amazon Kindle Fire using Tapatalk 2 Beta-4
dw9906 said:
Source has been pushed.
Sent from my Amazon Kindle Fire using Tapatalk 2 Beta-4
Click to expand...
Click to collapse
ok guys its here Whitehawkx AOKP 29 is android 4.0.4 maybe its just me but it seems a lot smoother
I just like the fact that multitouch was updated in it for the keyboard issues I was having... Typing drunk on CM9 was messing with everything I needed lol.
Anyone know when the OTA will be out
Been trying different ROMs but then my phone started random rebooting even when I put it back to completely stock and re-locked it. So, I sent it in for replacement. Now my replacement phone at the top of the screen used to say "T-mobile" but now just reads "LG" on the glass. I guess the later phones were no longer branded T-mobile.
One thing I noticed though is when I put in a ROM that worked flawlessly on my old phone it would cause the replacement to have random reboots, force close, and just plain lock up where I would be required to remove/replace the battery to get it to work again. Any ideas or suggestions??? I have only been able to run the stock GB rom successfully.
Any ideas on what the phones issue may be?? Or maybe when the OTA for a stock ICS will be available?
Thanks,
NotinStock
notinstock said:
Been trying different ROMs but then my phone started random rebooting even when I put it back to completely stock and re-locked it. So, I sent it in for replacement. Now my replacement phone at the top of the screen used to say "T-mobile" but now just reads "LG" on the glass. I guess the later phones were no longer branded T-mobile.
One thing I noticed though is when I put in a ROM that worked flawlessly on my old phone it would cause the replacement to have random reboots, force close, and just plain lock up where I would be required to remove/replace the battery to get it to work again. Any ideas or suggestions??? I have only been able to run the stock GB rom successfully.
Any ideas on what the phones issue may be?? Or maybe when the OTA for a stock ICS will be available?
Thanks,
NotinStock
Click to expand...
Click to collapse
1. why are you posting in this thread?
2. some roms/kernels are undervolted, if your phone cant handle it youll get random reboots.
3. nobody knows when ICS will get here, NOBODY. if anyone says they know when it will get here, they are lying. there are no exceptions, EVER!
Loving all the improvements that come with this update. I just installed AOKP build 31 and have had zero issues thus far. Just one thing missing...can't hangout in G+ and we know whose fault that is. Nvidia
Hi guys
So I bought tablet here in the UK about a month ago and apart from being sluggish on ICS (seems, everyone knows that problem) everything was fine. The JB OTA FW has rolled out and I upgraded and shortly after that TF300 started to play around by randomly rebooting itself every so often. Recently It got so bad that it happens all the time I mean in less than every 5 minutes.
I am gonna take it back to the shop but I am curious if any of you had this problem and if You know what's causing it...Ohh.. forgot to mention that obviously I did the Factory Reset and it didn't help...
I have to admit that after my faulty device and so many people had on this forum I will never ever unlock it after i get it back fixed/replaced...It's just not reliable enough to trust Asus on that especially if it cost so much money to fix it after ...
i ve got mine for over a month now. First ICS and JB later, I honestly can remember it ever rebooting
Adriael said:
I have to admit that after my faulty device and so many people had on this forum I will never ever unlock it after i get it back fixed/replaced...
Click to expand...
Click to collapse
When I read your issue, the first thing I thought was how glad I am that I'm unlocked and running stable builds rather than the stock ASUS stuff.
If the issue is hardware related, ASUS should cover it under warranty regardless of locked or unlocked. Unlocking it didn't cause the hardware to fail. If it's a ROM issue, you can easily re-flash or try another. It's a win-win.
Regardless, good luck with your tablet.
Adriael said:
Hi guys
So I bought tablet here in the UK about a month ago and apart from being sluggish on ICS (seems, everyone knows that problem) everything was fine. The JB OTA FW has rolled out and I upgraded and shortly after that TF300 started to play around by randomly rebooting itself every so often. Recently It got so bad that it happens all the time I mean in less than every 5 minutes.
I am gonna take it back to the shop but I am curious if any of you had this problem and if You know what's causing it...Ohh.. forgot to mention that obviously I did the Factory Reset and it didn't help...
I have to admit that after my faulty device and so many people had on this forum I will never ever unlock it after i get it back fixed/replaced...It's just not reliable enough to trust Asus on that especially if it cost so much money to fix it after ...
Click to expand...
Click to collapse
After doing factory reset did you try your pad without restoring any apps? It could be that an app you had was causing the reboot, it seems strange that it didn't do that on ICS and it does on JB.
Yes i did..but then again it was working fine on ICS so can't be a single app besides it usually reboots when the screen goes off...I started to think that it may have something to do with the bootloader since one it didn't even boot but stopped on asus screen giving me some message about bootloader error etc.(can't exactly remember what it said)..one way or another it is strange that only some ppl get this random reboots and for other jb is working fine so I'm gonna get it replaced or money back and maybe but tf700 ..i was gonna unlock it and flash custom rom but if problem still occurs then I'm completely screwed on money...
Sent from my Galaxy Nexus using xda app-developers app
So after the JB update I too had the random reboots while in the dock and charging I did all the usual, and cold reboots etc etc, but after reading in Atrix about there issues with ICS custom roms where it was noted that reboots stopped if you removed you external memory (or any memory cards come to that)
So I tried it, and now it doesnt do random reboots.....not sure if this will help anyone but might just make one irritation go away
deech said:
So after the JB update I too had the random reboots while in the dock and charging I did all the usual, and cold reboots etc etc, but after reading in Atrix about there issues with ICS custom roms where it was noted that reboots stopped if you removed you external memory (or any memory cards come to that)
So I tried it, and now it doesnt do random reboots.....not sure if this will help anyone but might just make one irritation go away
Click to expand...
Click to collapse
Can you give more informations, please.
What's model ?
If it's a TG, the better solution for you, it's to contact ASUS for an exchange.
You're not alone => Census TF300TG / TL 3G failed
it's the TF300t just normal bog standard machine, not rootd or unlocked, happened after the JB update, reported it in the JB issues thread, but wrote this after testing it after reading about the Atrix's similar issues after a custom ICS....
Since removing the sd cards from both dock and pad not had any more random re-boots, will try to see if it's one or other of the slots causing it.
deech said:
it's the TF300t just normal bog standard machine, not rootd or unlocked, happened after the JB update, reported it in the JB issues thread, but wrote this after testing it after reading about the Atrix's similar issues after a custom ICS....
Since removing the sd cards from both dock and pad not had any more random re-boots, will try to see if it's one or other of the slots causing it.
Click to expand...
Click to collapse
I'll have to test this out since I have 2 MicroSD cards inserted into my TF300T right now with the newest JB release. It appears that my tablet is having the same issues as I've seen with custom ROMs on phones with too much running the background. I wish I had root, since I could trim what apps are running but that'll have to wait for later.
deech said:
it's the TF300t just normal bog standard machine, not rootd or unlocked, happened after the JB update, reported it in the JB issues thread, but wrote this after testing it after reading about the Atrix's similar issues after a custom ICS....
Since removing the sd cards from both dock and pad not had any more random re-boots, will try to see if it's one or other of the slots causing it.
Click to expand...
Click to collapse
CrimsonKnight13 said:
I'll have to test this out since I have 2 MicroSD cards inserted into my TF300T right now with the newest JB release. It appears that my tablet is having the same issues as I've seen with custom ROMs on phones with too much running the background. I wish I had root, since I could trim what apps are running but that'll have to wait for later.
Click to expand...
Click to collapse
The best you can do it's to installed the new kernel that you will find in my index (click in my sig )
Apparently it could solve the problem with these random reboots
philos64 said:
The best you can do it's to installed the new kernel that you will find in my index (click in my sig )
Apparently it could solve the problem with these random reboots
Click to expand...
Click to collapse
Thanks. I'll verify that I have the same kernel version as v10.4.2.17, which I updated to recently. I've read that a lot of people have issues with the power button, but since I don't, I believe that it is something within JB. The odd part is that I've seen this exact same issue in Android since 2.2. Maybe its my power user ways...
This drove me crazy on my TF101... so I gave up and got the TF300T. After the first day it started random rebooting.... I was PISSED!!! :crying: After searching for and answer I came across a thread on another forum that suggested a fix was to install an app called "WakeLock" and set it to "Partial" .... 2 months later not one single reboot since I installed it. :good:
Market Link
https://play.google.com/store/apps/...t#?t=W251bGwsMSwxLDEsImV1LnRoZWRhcmtlbi53bCJd
Riptide9 said:
This drove me crazy on my TF101... so I gave up and got the TF300T. After the first day it started random rebooting.... I was PISSED!!! :crying: After searching for and answer I came across a thread on another forum that suggested a fix was to install an app called "WakeLock" and set it to "Partial" .... 2 months later not one single reboot since I installed it. :good:
Market Link
https://play.google.com/store/apps/...t#?t=W251bGwsMSwxLDEsImV1LnRoZWRhcmtlbi53bCJd
Click to expand...
Click to collapse
Thanks! I'll test it out thoroughly & see how it goes.
CrimsonKnight13 said:
Thanks! I'll test it out thoroughly & see how it goes.
Click to expand...
Click to collapse
I installed the program last evening ,got a reboot 5 hours later.
Running overclocked at 1600Mhz .(governor "interactive")
ejssje said:
I installed the program last evening ,got a reboot 5 hours later.
Running overclocked at 1600Mhz .(governor "interactive")
Click to expand...
Click to collapse
OCing can make a reboot happen due to overheating. Have you tried just doing stock speed?
I had reboots all the time when the dock was connected. I updated to the latest firmware two days ago and have not rebooted since. I also installed WakeLock set on partial and it seems to help.
Hey so after a few days of the new update running OK I started having random reboots! I noticed on a few other sites people complaining about the same issue of reboots multiple times of the day! Just wanted to let everyone know a possible solution to the issue! I have went through multiple FDR's and did come to the conclusion that the random reboots for my phone were associated with a new update to the chrome browser and were easily fixed by uninstalling new update and telling it not to automatically update so hope this helps anyone who may be having the same issues!!!
Well so much for that after trying everything its back to rebooting again? I love my phone but seriously considering putting it against a wall!!!
xgshortbus25 said:
Hey so after a few days of the new update running OK I started having random reboots! I noticed on a few other sites people complaining about the same issue of reboots multiple times of the day! Just wanted to let everyone know a possible solution to the issue! I have went through multiple FDR's and did come to the conclusion that the random reboots for my phone were associated with a new update to the chrome browser and were easily fixed by uninstalling new update and telling it not to automatically update so hope this helps anyone who may be having the same issues!!!
Well so much for that after trying everything its back to rebooting again? I love my phone but seriously considering putting it against a wall!!!
Click to expand...
Click to collapse
Never had that issue with the new update. Try doing a factory reset or try the new fast boot files to start fresh. Not sure why chrome would be an issue.try the chrome beta version but I suspect chrome had nothing to do with the reboot just a bad initial update.
Sent from my DROID RAZR HD using Tapatalk 2
Fixed!! I hope!!!
Finally broke down done a fast boot to the new files all is working seems OK anyway know in a day or 2!!!
xgshortbus25 said:
Finally broke down done a fast boot to the new files all is working seems OK anyway know in a day or 2!!!
Click to expand...
Click to collapse
My Wife's phone is doing the Random Reboot thing since the 4.1.2 update as well. I did a Factory Reset on it and it still does the same thing.
I suspect an application is doing it? Because I put the phone in Safe Mode and it never rebooted while in Safe Mode.
But I have No Idea of how to tell which app is doing it, other than to uninstall a random app after every reboot to find out which one it is.
But I would like to try this fast boot option? I know how to get the phone into fastboot, but which files are you redoing? What exactly are your doing ?
Have the same problem. I have done:
SBF 4.1.2
FDR
WIPE
Even tried running a parallel rom with safestrap (bakatang)
The chrome thing did not work
Keeps freezing. Seems the problem is way worse when having the phone play some music.
I am just about unlocking the thing and SBFing back to 4.1.1 but not really interested into unlocking the bootloader. That would be the last choice for me.
If someone knows of some way to fix this, please help, this used to be a great phone...
No problem here with the sfr rom... used for over 1 month now and no problem and my system is always fast...
Sent from my XT925 using xda premium
I've been running some tests for about a week now since I got my RAZR and the results are interesting... I've had lockups and reboots multiple times a day, most often while doing something involving sound i.e. listening to music or playing a game or video. I've tried stock and custom 4.1.2 ROMs and custom 4.2.2 ROMs and it persists so I'm inclined to say its either bad audio software or faulty audio chips. This is everything I've done:
1. turning off sounds (keeping phone on vibrate/silent) pretty much eliminates the random lockups/reboots I got from receiving multiple texts or calls at once. I noticed if I bombarded the phone and made it ring a lot it gave the same results as listening to music but if its just a text or email or call here and there during regular use it the phone works fine.
2. Listening to music, either streamed or local from phone/SD storage and through headphones or speaker, would cause skips and audio cutting out. After a few minutes of this the phone will lock up completely and reboot itself. Strangely enough it happened only rarely or not at all while streaming music via bluetooth to a stereo.
3. I don't think its anything kernel related or if it is its not causing visible errors or wake locks. My battery seems to be just fine through all this.
4. I have tried multiple music/video players, put my SD card with music in another phone and the music plays fine, stock ROMs with nothing disabled/removed still has the issue, custom ROMs debloated and modified also have the issue. I think I've just about covered every base I can as an end user to track down what's causing it but I'm open to suggestions.
I have a replacement scheduled so I will see if that fixes it, I have seen this problem reported quite a few times all over the interwebz but there are also a lot of people not having the issue either so idk. If there are any Devs or anyone skilled in android-fu that can read logcats I will be more than willing to get those for you. Sorry for the essay everyone lol
tl;dr Like others I have freezes and reboots from what seems to me to be an audio software/hardware problem, either built in or from the 4.1.2 update
Sent from my DROID RAZR HD using Tapatalk 2
I am almost sure is kernel related bc I did not have problems in the 4.1.1 sw.
If someone that has an unlocked bootloader could install 4.1.1 from an sbf and tell if the problems are gone, would be great!
here is the sbfs: http://sbf.droid-developers.org/vanquish/list.php
here is the bl unlocker: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
u have to be rooted here: http://www.droidrzr.com/index.php/topic/15208-root-motochopper-yet-another-android-root-exploit-412/?pid=244281#entry244281
I am not doing that bc I do not use custom roms so dont want to unlock BL. If someone has, this could help much. It is different from using safestrap, because safestrap uses the same kernel, from what I read.
barbaroja said:
I am almost sure is kernel related bc I did not have problems in the 4.1.1 sw.
If someone that has an unlocked bootloader could install 4.1.1 from an sbf and tell if the problems are gone, would be great!
here is the sbfs: http://sbf.droid-developers.org/vanquish/list.php
here is the bl unlocker: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
u have to be rooted here: http://www.droidrzr.com/index.php/t...roid-root-exploit-412/?pid=244281#entry244281
I am not doing that bc I do not use custom roms so dont want to unlock BL. If someone has, this could help much. It is different from using safestrap, because safestrap uses the same kernel, from what I read.
Click to expand...
Click to collapse
I have seen reports that the problem persists even on 4.1.1 but I am unlocked and rooted on stock 4.1.2 so if I get time I can give it a try
Sent from my DROID RAZR HD using Tapatalk 2
anoninja118 said:
I have seen reports that the problem persists even on 4.1.1 but I am unlocked and rooted on stock 4.1.2 so if I get time I can give it a try
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
When I was at 4.1.1 phone was near perfect.
If you are unlocked, please do check. I am debating whether to unlock or not just bc of this. Today it has resetted at least a good 20 times or so.
Thanks for helping!!! Waiting for your results!!!!
barbaroja said:
When I was at 4.1.1 phone was near perfect.
If you are unlocked, please do check. I am debating whether to unlock or not just bc of this. Today it has resetted at least a good 20 times or so.
Thanks for helping!!! Waiting for your results!!!!
Click to expand...
Click to collapse
one solution that has worked for me is silencing the phone or putting it on vibrate and I haven't had a freeze or reboot in almost 2 days... the problem seems to me to be related to audio/sound and not listening to music or watching videos along with silencing ringtones has put a stop to it which kind of confirms my suspicions... I will try and flash back when I can but it'll need a day or 2 of field testing to confirm if its a solution
Sent from my DROID RAZR HD using Tapatalk 2
I can confirm that audio stuff just does worse to the phone. However, I have not had your luck when silencing. Keeps rebooting no matter what. Please let us know when you do.
barbaroja said:
I can confirm that audio stuff just does worse to the phone. However, I have not had your luck when silencing. Keeps rebooting no matter what. Please let us know when you do.
Click to expand...
Click to collapse
looks like a negative on the SBF, tried to restore 4.1.1 and it failed halfway through the flash, now won't turn on... working on reviving it... I really need to replace this thing as its been nothing but a PITA since I got it
old school post from my Thunderbolt via Tapatalk
wow that sucks. I recall reading somewhere that you could actually downgrade your software version if you have an unlocked bootloader.what is the error you are getting? Tried using RAZR utility 1.1? Won't it turn on at all? Maybe a discharged battery? Hope we can solve it
barbaroja said:
wow that sucks. I recall reading somewhere that you could actually downgrade your software version if you have an unlocked bootloader.what is the error you are getting? Tried using RAZR utility 1.1? Won't it turn on at all? Maybe a discharged battery? Hope we can solve it
Click to expand...
Click to collapse
got it revived with Mattlgroff's new 1.2 utility, was able to force it to fastboot mode... the problem seemed to be some kind of partition error, I tried redownloading the sbf files thinking it was a bad file and got the same error so idk what it is since I'm on stock unrooted 4.1.2. My bootloader is already irreversibly unlocked so that won't be a problem lol but I am a n00b to RSD Lite and Moto devices so I'll tinker with it more when I get some free time
edit: I did have a Maxx HD way back at launch for a month or so running stock 4.1.1 and it ran perfectly, so my idea is its kernel/codec/software related. Hopefully a custom ROM (or hell even stock) with Hashcodes Qcom kernel will fix the issue we're having
Sent from my DROID RAZR HD using Tapatalk 2
I talked with vzw service, the assistant said that 2% of the phones were having this issue, wich for this kind of technology is a pretty big number of phones. Suuggested to send it to Motorola but since its rooted its almost sure not to be replaced by them. What is strange is that not everyone is having this issue. I would be almost sure Motorola is going to release a fix for this, but would not count days. Getting kind of frustrated with this phone I used to like so much. Thinking of going the htc route bc this is getting unbearable.
Any news in this? Anyone tried a new ROM that could solve this? Or even a fix?
... or just everyone had another phone lying aroud...
barbaroja said:
Any news in this? Anyone tried a new ROM that could solve this? Or even a fix?
... or just everyone had another phone lying aroud...
Click to expand...
Click to collapse
My wife & I both have this phone and still are constantly being rebooted. This is even after the software update. I have been wiped, factory reset, and everything possible, but I've not called for a replacement yet. Normally I havea worse luck with those.
Wife used to love this phone, now she hates it and hates we changed from AT&T to Verizon since we have no backup Verizon phones. At least we could take the sim out and go to the iPhone that's floating around the house when the phone went to pot before. Makes me really hate suggesting that we go back to Moto phones since that's all that I've used on Verizon.
Wonder if big red will get the new HTC One....
Tried flashing the MR-4 sbf, but did not solve the issue.
Sent from my GT-I9100 using Tapatalk 2
barbaroja said:
Tried flashing the MR-4 sbf, but did not solve the issue.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
If an sbf didn't solve it then it's a hardware problem.you guys are definitely in the minority with this reboot issue.go get a warranty replacement.this phone and moto in general are solid phones.
sent from my xt926 RAZR maxx hd