I bought a gnex 2 days ago and have some weird issue. Occassionally, when unlocking the phone, the phone stops responding for 30-45 seconds, reboots itself and is sending me a bugreport. The report can be found in the link below. Also, there is a screenshot saved every time thta happens, however the screenshot is only the lock screen.
After the reboot the phone becomes a bit slow when switching between applications, after I manually reboot once more it works flawlessly again.
The android version is the stock 4.1.1 JellyBean. The phone is rooted.
Note: I had the same issue with my Nexus S before, but I thought its because its a lot slower.
Bug report link:
https://docs.google.com/open?id=0B_FOxKiTQcvbZEdGMDUwUEJtRWM
Sent from my Galaxy Nexus using Tapatalk 2
Palaryel said:
I bought a gnex 2 days ago and have some weird issue. Occassionally, when unlocking the phone, the phone stops responding for 30-45 seconds, reboots itself and is sending me a bugreport. The report can be found in the link below. Also, there is a screenshot saved every time thta happens, however the screenshot is only the lock screen.
After the reboot the phone becomes a bit slow when switching between applications, after I manually reboot once more it works flawlessly again.
The android version is the stock 4.1.1 JellyBean. The phone is rooted.
Note: I had the same issue with my Nexus S before, but I thought its because its a lot slower.
Bug report link:
https://docs.google.com/open?id=0B_FOxKiTQcvbZEdGMDUwUEJtRWM
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Have you done a factory reset?
I would say one of your apps is causing this.
That is my idea aswell (since I imported my apps via Ti backup from my nexus s - only the user apps, without data), the issue is that I really dont have the time to test 1by1and actully all I apps that I have installed are apps I use aswell, so I figured someone here might figure out what exactly causes this from the crash log i supplied.
Sent from my Galaxy Nexus using Tapatalk 2
well, i'm not sure but:
i see a bunch of errors after
Code:
------ ducati trace1 (/d/remoteproc/omap-rproc.1/trace1: 2012-09-28 00:30:19) ------
searched a bit around, found this: http://omappedia.org/wiki/Category:RPMsg
Maybe you could try flashing ICS? binaries are probably different, and although I'm not sure it would solve anything, but it's worth a try.
edit: does your device get hot rapidly?
bk201doesntexist said:
well, i'm not sure but:
i see a bunch of errors after
Code:
------ ducati trace1 (/d/remoteproc/omap-rproc.1/trace1: 2012-09-28 00:30:19) ------
searched a bit around, found this: http://omappedia.org/wiki/Category:RPMsg
Maybe you could try flashing ICS? binaries are probably different, and although I'm not sure it would solve anything, but it's worth a try.
edit: does your device get hot rapidly?
Click to expand...
Click to collapse
Usually between 30-36°C (i saw 36 only once so far)so I guess it doesnt get hot.
Sent from my Galaxy Nexus using Tapatalk 2
Palaryel said:
Usually between 30-36°C (i saw 36 only once so far)so I guess it doesnt get hot.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
okay. try flashing ICS, see where that leads you.
follow this guide if you need instructions.
Also try factory reset with no apps import from TI and see how you do for a few hours.
Sent from my Galaxy Nexus using xda app-developers app
Update: another weird thing (it might br the cause of the problem), if i happen to press all 3 hard keys (vol up + down+power) while the phone is turned on i get the same thing as described above.
Could anyone try to reproduce this?
Sent from my Galaxy Nexus using Tapatalk 2
Found the cause of the problem: its the su binary from Superuser 3.2 RC.
The solution is to swap to either SuperSU or Superuser 3.1.3.
The problem does occur oy when all 3 hard keys are pressed, however it will not crash if a other binary is present (instead of the 3.2 one) in case of the other versions the bug still occjrs (bugreport appears) and the su log shows a lot of su rewuests by "shell", anyway no syst reset or slow response happens.
Sent from my Galaxy Nexus using Tapatalk 2
Palaryel said:
Found the cause of the problem: its the su binary from Superuser 3.2 RC.
The solution is to swap to either SuperSU or Superuser 3.1.3.
The problem does occur oy when all 3 hard keys are pressed, however it will not crash if a other binary is present (instead of the 3.2 one) in case of the other versions the bug still occjrs (bugreport appears) and the su log shows a lot of su rewuests by "shell", anyway no syst reset or slow response happens.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
great, you solved it. thanks for sharing. thumbs up for this thread. could you please edit the title to include tag "[SOLVED]"?
sent from my i9250
Related
i have this phone for a week and the lock screen disappeared after the first day .... i thought its a issue so i replaced it with a new one ... and it also had the same problem ..... and now it is getting restarted ... it has happened to me twice in 2 days .... does anyone know how to fix the lock screen that disappeared ??????????
sanil1986 said:
i have this phone for a week and the lock screen disappeared after the first day .... i thought its a issue so i replaced it with a new one ... and it also had the same problem ..... and now it is getting restarted ... it has happened to me twice in 2 days .... does anyone know how to fix the lock screen that disappeared ??????????
Click to expand...
Click to collapse
Yea the same thing happened go mine. I no longer have
a lock screen. I've tried everything too. I rooted tried custom ROM tried flashing back to stock nothing works.
Sent from my SGH-T989 using Tapatalk
sanil1986 said:
i have this phone for a week and the lock screen disappeared after the first day .... i thought its a issue so i replaced it with a new one ... and it also had the same problem ..... and now it is getting restarted ... it has happened to me twice in 2 days .... does anyone know how to fix the lock screen that disappeared ??????????
Click to expand...
Click to collapse
Also every time I restart my Bluetooth is turned on and the screen timeout is set to 10 mins. I'll post a video later
Sent from my SGH-T989 using Tapatalk
The lock screen disappearing and the power menu going away is a bug that can randomly happen apparently. You probably trigged this bug by going into the lcdtest menu (typing *#0#* or whatever it is). The only way to fix this is a master reset. Just avoid using the lcdtest menu and it shouldn't happen again.
Sent from my SGH-T989 using xda premium
alright will try to do a master reset again and not do the lcd test this time .....
matthenry87 said:
The lock screen disappearing and the power menu going away is a bug that can randomly happen apparently. You probably trigged this bug by going into the lcdtest menu (typing *#0#* or whatever it is). The only way to fix this is a master reset. Just avoid using the lcdtest menu and it shouldn't happen again.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Tried a master reset on the phone and no luck at all still have the same problem. Also thr initial welcome screen never showed either.
Sent from my SGH-T989 using Tapatalk
same here .... no luck at all .... i dun know if this bug will be fixed or not ....
Is anyone else having this issue?
Sent from my SGH-T989 using Tapatalk
i came to know that a lot of people are having this issue .... even if the lock screen is not fixed atleast samsung shouil fix the restarting issue ... its just growing more and more .... i had two restarts yesterday .....
I havent had any random restarts. Im thinking about going to get an exchange
Sent from my SGH-T989 using Tapatalk
this is my second galaxy ... the earlier one also had the same problem with heating too ... atleast this one does not heat up always
it's all in the software
keep an eye on what you are installing, and how the apps behave in the phone
some apps stay in the background if you don't exit them properly
the screen lock bug is a known issue that gets triggered after you run some test
to get it back just restore everything back to default using factory wipe
did the factory reset .... and didnt do any test .... yet the second day the lock screen disappeared and the third day the restarting happened and still it continues
AllGamer said:
it's all in the software
keep an eye on what you are installing, and how the apps behave in the phone
some apps stay in the background if you don't exit them properly
the screen lock bug is a known issue that gets triggered after you run some test
to get it back just restore everything back to default using factory wipe
Click to expand...
Click to collapse
yea I'm sure its just a software issue hopefully its fixed soon.
but I've tried everything. like the person above from me said, it happened on the second day.
I've tried factory resetting the phone and even flashing a stock rom and no go. its gone.
im not having the restart issue though
hope everything will be fixed in ice cream sandwich .... the lock screen in that is a facial recognition ... so hope it will be a huge improvement ... cant wait for that .... just read somewhere that samsung might get ice cream sandwich to s2 users as early as December
Will samsung be releasing a patch before ICS to address the pattern draw lockscreen issue? This is the only problem preventing me from leaving the sensation and jumping onboard the SGS2. I carry a lot of sensitive material, so that would be a huge security breach.
Ive only had this issue when the phone boots on. There are unlock icons but i see my homescreen and the phone is locked. Rooted to jugs 2.6 and still the same thing.
Sent from my SGH-T989 using xda premium
This was a big deal with the Samsung Behold 2. I am surprised samsung repeated this software defect with such a high end phone. I wonder if there will be a patch for this before the ICS update. IMO this is worse than the vertical lines!
Problem Solved
i actually figured out a way to restore my lock screen back.
Note: This involves messing with the efs folder. So do this at you own risk
also, your phone must be rooted in order to do this.
Tools Needed:
1. Hex Editor
2. Root Explorer
Steps to restore:'
1. Using root explorer locate the /efs/imei/ folder. In that folder there should be a file called keystr. In my case the file was missing which is why the lock screen was missing and was causing my problems.
2. using root explorer create a new file called keystr
3. also in root explorer open the file keystr in text editor and type ON
4. now go into hex editor and locate the /efs/imei/keystr file.
5. using hex editor the first two values in green should be 4f and 4e. all others should be 00.
6. make sure you save the file.
7. reboot.
Sorry to bring up and old thread but I just wanted to have it here incase anyone has the same problem in the future. I had the same problem as well after running LCD Test. To fix it I followed the solution on this thread
http://forum.xda-developers.com/showthread.php?t=1401723&highlight=lock
It fixed my problem without a factory reset!
Recently I bought myself a Galaxy Nexus after owning a Nexus S for 1,5 year.
I never had issues with the Nexus S (even with JB), however this seems a different story on the GNX.
My issues:
- Youtube doesn't play videos and crashes
- Gallery crashes when looking at videos. I get a black screen when playing a video but it doesn't start to play, when I press back the system doesn't react, pressing home returns me to the home screen.
- Face unlock doesn't start it's process and I'm redirected to enter my PIN
Any ideas? I noticed the factory JB 4.1.1 image is released, maybe I should place a clean image on my GNX?
Thanks for all comments!
Are you currently on a stock or custom ROM?
I have this problem here many and many times too with a stock rom.. Yesterday I reinstalled the factory ROM 4.1.1 but the problem persists, I think it's a bug in this version because in 4.0.4 doesn't have this problems..
I don't have this problem and I very much doubt many do. I suspect you may have a hardware problem. Probably faulty memory.
Sent from my Nexus 7 using XDA Premium HD app
Dr.Paul said:
I don't have this problem and I very much doubt many do. I suspect you may have a hardware problem. Probably faulty memory.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I don't think is a problem of faulty memory, it is difficult to reproduce this bug, you must open a video in the gallery or on youtube, watch the video and pause, after a few minutes reopen a video and do that sometimes and you have the problem ..
I've never had anything like this happen on jb.. .
I don't have this problem - did you try deleting the Youtube app and reinstalling it?
It might be worth trying to do a total hardware reset if you have a couple hours.
superdx said:
I don't have this problem - did you try deleting the Youtube app and reinstalling it?
It might be worth trying to do a total hardware reset if you have a couple hours.
Click to expand...
Click to collapse
I've done it already, I've deleted the cache's app and the problem continues, it does not happen right the first time, occurs after about 10 times you watch a video and then watch again ..
It's a new phone. It came with ICS 4.0.1 which went to the OTA upgrade path: 4.0.2, 4.0.4 and then 4.1.1. So completely stock.
I also notice that the camera app doesn't come up (the same problem which does occur when unlocking with face unlock).
Pictures from the gallery show up without problems.
What are the best steps to have a complete hardware reset? Flashing the stock JB 4.1.1 factory image via fastboot?
If it's hardware defect, is there a offline diagnostic tool I can run on my GNX?
I appreciate all replies!
For me the only way to solve that is using the 4.0.4 stock ROM
RicardoSul said:
For me the only way to solve that is using the 4.0.4 stock ROM
Click to expand...
Click to collapse
I dont have problems on my nexys with 4.1.1
knudsen81 said:
I dont have problems on my nexys with 4.1.1
Click to expand...
Click to collapse
Today I returned my Galaxy Nexus to the shop. I will get a new one as soon they're back on stock.
I returned to my Nexus S which has JB, unfortunately it seems JB is still not as stable as ICS. Had some Google Talk crashes today.
Never had a crash on my Nexus S on ICS.
Edit: Nevermind I didn't read your last post completely.
Glad to see you're getting a new one
I'm also waiting for a replacement for mines (kept crashing randomly). It will arrive on thursday.
xanadu.dm said:
Today I returned my Galaxy Nexus to the shop. I will get a new one as soon they're back on stock.
I returned to my Nexus S which has JB, unfortunately it seems JB is still not as stable as ICS. Had some Google Talk crashes today.
Never had a crash on my Nexus S on ICS.
Click to expand...
Click to collapse
I think I figured out how to solve these bugs, here they stopped to occur after disabling facial recognition, use another way to unlock your phone and make sure that they stopped
Sent from my Galaxy Nexus using xda app-developers app
Probably the people who reported not having the bug doesn't use face recognition, I think this is the reason for very few people reporting this bug.
Sent from my Galaxy Nexus using xda app-developers app
I've never had these issues and I used face recognition since the first day I got the phone.
Meanwhile I got a brand new Galaxy Nexus, however after one week of use the same problems returned!
I wonder if an app or something else is causing these problems.
I have not had these issues, you probably have a faulty phone.
It can't be that I have two times a faulty phone? First one was delivered with the Google ROM, the second one with the Samsung ROM which I changed immediately to the official yakyu ROM.
xanadu.dm said:
It can't be that I have two times a faulty phone? First one was delivered with the Google ROM, the second one with the Samsung ROM which I changed immediately to the official yakyu ROM.
Click to expand...
Click to collapse
Turn off face recognition and test again..
Sent from my Galaxy Nexus using xda app-developers app
Im new in this nexus section...i'm asking why my galaxy nexus sometimes reboots? It has the latest 4.2.2 android version stock...it isnt the update, i think, because also before this happen...and when it reboots there's like a opened locket under the google logo....who can help.me? I tried also the nexus toolkit...but when i try to do something with fastboot the program says WAITING DEVICE forever...
Guys, please help!! Its really urgent!
Hi,
I think there are two reasons for random reboots:
1- overheating
2-lack of ram (many running proceses, so ram gets full, so it reboots.
Press the thanks button if I helped
blakstar said:
Hi,
I think there are two reasons for random reboots:
1- overheating
2-lack of ram (many running proceses, so ram gets full, so it reboots.
Press the thanks button if I helped
Click to expand...
Click to collapse
No, even when the battery isnt hot it reboots!!
and it is without any apps installed, only stock apps!! I did also a factory reset from settings..but nothing happened...
Searching on net, i read that the opened locket is the bootloader....is that causing random reboots? If yes, how to relock with toolkit? Beacause it says me WAITING DEVICE
isko95 said:
No, even when the battery isnt hot it reboots!!
and it is without any apps installed, only stock apps!! I did also a factory reset from settings..but nothing happened...
Searching on net, i read that the opened locket is the bootloader....is that causing random reboots? If yes, how to relock with toolkit? Beacause it says me WAITING DEVICE
Click to expand...
Click to collapse
No, unlocking the bootloader shouldn't do this. I have an unlocked bootloader, and I have this phone(xperia arc) for 5 months and I only had one random reboot and it was definitely because of lack of ram
blakstar said:
No, unlocking the bootloader shouldn't do this. I have an unlocked bootloader, and I have this phone(xperia arc) for 5 months and I only had one random reboot and it was definitely because of lack of ram
Click to expand...
Click to collapse
Yes but im talking about NEXUS and maybe its different!!
I used to have that happen all the time. I used to think that the phone sucked but my husband never had that happen with his. I compared the apps and wiped my phone, only installed what he had on there. It still happened. I was really beginning to get mad but I wiped it again. I Installed things one by one only allowing myself to install a new app only after it had gone a week with no nonsense. Yes, this was a painful process but I found the cause of my random reboots. I use Handcent. That alone isn't the cause. When I would get new sounds for my GN, I would have the option of making them a ringtone or a Handcent notification among other things. If I made Handcent notifications, that seemed to cause the problem. If I move a sound into the notifications folder and assign it to contacts in Handcent, everything has been fine.
I don't know if this helps your problem but some settings could affect unexpected things. Good luck!
Sent from my Xoom using xda premium
3devious said:
I used to have that happen all the time. I used to think that the phone sucked but my husband never had that happen with his. I compared the apps and wiped my phone, only installed what he had on there. It still happened. I was really beginning to get mad but I wiped it again. I Installed things one by one only allowing myself to install a new app only after it had gone a week with no nonsense. Yes, this was a painful process but I found the cause of my random reboots. I use Handcent. That alone isn't the cause. When I would get new sounds for my GN, I would have the option of making them a ringtone or a Handcent notification among other things. If I made Handcent notifications, that seemed to cause the problem. If I move a sound into the notifications folder and assign it to contacts in Handcent, everything has been fine.
I don't know if this helps your problem but some settings could affect unexpected things. Good luck!
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
I did factory reset twice from device's settings, but nothing.
no one who can help? wow!!
I had random reboots on my Verizon GN running the OTA 4.1.1. I got so fed up with it that I went back to 4.0.4. I have had no problems or reboots since doing this.
Are you running Chrome or the stock browser? I've always had the random restarts on my N10, but only started seeing them on my GN after I started using Chrome around the time 4.2.2 came out.
gforce1963 said:
I had random reboots on my Verizon GN running the OTA 4.1.1. I got so fed up with it that I went back to 4.0.4. I have had no problems or reboots since doing this.
Click to expand...
Click to collapse
Reaally? How did you get back to 4.0 ics?
OP, read the return to stickied thread on general forum by efrant, if your problems still happen after restoring back to stock through fastboot, then you may have faulty hw.
Sent from my Nexus
bk201doesntexist said:
OP, read the return to stickied thread on general forum by efrant, if your problems still happen after restoring back to stock through fastboot, then you may have faulty hw.
Sent from my Nexus
Click to expand...
Click to collapse
why when i try to do something with nexus toolkit it says waiting for device?
Heeeeeeeeelp heeeeeeeeeeelp!
why no one can help in here?!?!?!
Do dmesg or logcat, maybe we can help resolving your problem or you can ask your phone service.
Sent from my MT27i using my finger
ahlulnugraha said:
Do dmesg or logcat, maybe we can help resolving your problem or you can ask your phone service.
Sent from my MT27i using my finger
Click to expand...
Click to collapse
How to make logcat??
Really a few people answers!
Bk201 handled it as always. Follow his suggestion. If that can't help you it must be PEBKAC.
Hi,
History:
I have a problem with my Nexus. It randomly reboots. Nothing seems to help.
It started after a few months after I was rooted on CyanogenMod 10.0. In 3 days, it quickly escalated to a reboot every 10 minutes on average.
A factory reset (without user apps installed on it) on CynogenMod reduced the frequency (every hour?), but didn't eliminate it.
Unrooting to stock Jellybean 4.1.2 seemed fine only in the first week. The problem came back afterwards, and updating to JB 4.2.1 didn't help.
Now, 2 months on stock ROM, I get even more random times. Sometimes it is 2 times a day, sometimes once a week.
Just before it:
I get a metallic screeching noise for 1-2 seconds, and immediately following that, device turns off with a "pang". Although these days I HAVE had situations that the sound came for up to 3 seconds (and the screen freezes), but the phone worked normally afterwards.
What happens:
It randomly reboots. The rebooting is at irregular intervals, whatever i was doing on it (even when not using it).
What happens after:
It takes much, much longer to startup again. It can get stuck at the "Google" logo screen for up to 5min. It doesn't take this long to reboot if I shut it down myself.
Any ideas? What causes this? Is it software or hardware?
Can I even send it for warranty if I cannot reproduce the problem?
I don't want to send it to warranty if I don't have to. I don't want to loose my phone for I don't know how long.
Hi, what's your eMMC version? Maybe buggy memory, try looking at other threads.
Отправлено с моего Galaxy Nexus через Tapatalk
Have you tried different batteries?
GeeNex | Carbon nightlies | Rubiks
I'm new to this eMMC thing, but according to an app my eMMC Type is V3U00M. To check whether it is buggy or not it needs root, which I don't currently have. If it IS buggy, I don't have a choice but to bring it for warranty right?
No, I have not tried to changed batteries. I don't have other batteries. But can the problem really lie with the battery? Btw, my phone is less than 8 months old.
Djalaal said:
I'm new to this eMMC thing, but according to an app my eMMC Type is V3U00M. To check whether it is buggy or not it needs root, which I don't currently have. If it IS buggy, I don't have a choice but to bring it for warranty right?
No, I have not tried to changed batteries. I don't have other batteries. But can the problem really lie with the battery? Btw, my phone is less than 8 months old.
Click to expand...
Click to collapse
Well, try waranty, that chip is buggy. Mine too )) but I just live with it using lagfix app and discard mount options, but things requires root. Good luck.
krugdenis said:
Well, try waranty, that chip is buggy. Mine too )) but I just live with it using lagfix app and discard mount options, but things requires root. Good luck.
Click to expand...
Click to collapse
Well, I am planning to root again. I want to switch back to CyanogenMod 10.1. Lagfix app isn't needed if you can use -discard mount option right? How to use either, if let's say I'm on CyanogenMod. This is also the first time I hear of lagfix and discard mount... :/
Btw, the app i used to check my eMMC Type said that my chip is ok. No brickbug. Are you sure it's buggy?
http://code.google.com/p/android/issues/detail?id=39154
Отправлено с моего Galaxy Nexus через Tapatalk
I might be wrong here, but from what I've read at the link and other xda posts (http://forum.xda-developers.com/showthread.php?t=2029246), the V3U00M chip is not buggy (in the sense that it's stable for rooting and using the -discard command), but it does give slowdowns. I do have horrible slowdowns, so thanks for that solution I didn't know existed. However, this doesn't solve my random reboot problem at all...
No one else got any solid way to find out the source of the problem?
BUMP
Djalaal said:
Hi,
History:
I have a problem with my Nexus. It randomly reboots. Nothing seems to help.
It started after a few months after I was rooted on CyanogenMod 10.0. In 3 days, it quickly escalated to a reboot every 10 minutes on average.
A factory reset (without user apps installed on it) on CynogenMod reduced the frequency (every hour?), but didn't eliminate it.
Unrooting to stock Jellybean 4.1.2 seemed fine only in the first week. The problem came back afterwards, and updating to JB 4.2.1 didn't help.
Now, 2 months on stock ROM, I get even more random times. Sometimes it is 2 times a day, sometimes once a week.
Just before it:
I get a metallic screeching noise for 1-2 seconds, and immediately following that, device turns off with a "pang". Although these days I HAVE had situations that the sound came for up to 3 seconds (and the screen freezes), but the phone worked normally afterwards.
What happens:
It randomly reboots. The rebooting is at irregular intervals, whatever i was doing on it (even when not using it).
What happens after:
It takes much, much longer to startup again. It can get stuck at the "Google" logo screen for up to 5min. It doesn't take this long to reboot if I shut it down myself.
Any ideas? What causes this? Is it software or hardware?
Can I even send it for warranty if I cannot reproduce the problem?
I don't want to send it to warranty if I don't have to. I don't want to loose my phone for I don't know how long.
Click to expand...
Click to collapse
Same as you man...
I'm seriously considering throwing my phone to the garbage. I don't like iPhones, but google is really pushing me into it with this crappy piece of phone. Is so frustrating to have these rebooting issues, I've tried everything, from wipe to factory reset, back to stock, flash custom ROMS and KERNELS, turning location access off, uninstalling all apps/widgets that might interfere, and every single "solution" it's out there, and STILL I'M HAVING THESE DAMN REBOOTS!
Now it's even worse, I can't even transfer files to my phone anymore because, guess what... IT REBOOTS! everytime I transfer ANY KIND of file.
The only thing that seems to work for a while is reformatting and start from scratch. I've done that like 3 times already. But still after a few weeks the issue reapears... i'm really mad about this, and no one seems to care. Not Google and not even Samsung.
The only interesting thing that i found around the internet is this guy's findings
plus.google.com/113601948978986762347/posts/2ALASEC1dG2
I read the log on my phone and matches to his... but now the thing is, what do i do with this information? I'm not a programmer o something like that.
Any ideas?
I think your board is faulty. Even so, have you tried disabling SR and raising voltages across the board? Trimming eMMC? Omapflash?
a manta wrote this.
Hey! Thanks for the reply but I'm just a regular user with just a little bit of computer knowledge... so the things you mentioned are basically Chinese to me
Sent from my Galaxy Nexus using xda app-developers app
elcampeondelrodeo said:
Hey! Thanks for the reply but I'm just a regular user with just a little bit of computer knowledge... so the things you mentioned are basically Chinese to me
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
He is saying that you have root you need to install trickster mod from the play store. Open the app and go to specific. Then disable the smart reflex toggles and click the oké button in the upper right corner see if that works. If it doesnt re enable smart reflex and go tot MPU voltages. Next to the words MPU voltages there is a blue plus/minus button. Click that and click the plus one time. Accept it and push again the oke button. The other two things I dont exactly know..
Sent from my Galaxy Nexus using XDA Premium HD app
Honestly, if you are getting reboots on a clean stock (including stock kernel) , it's probably a hardware issue.
Sent from my Galaxy Nexus using Tapatalk 2
Thanks for the reply guys!
mrgnex said:
He is saying that you have root you need to install trickster mod from the play store. Open the app and go to specific. Then disable the smart reflex toggles and click the oké button in the upper right corner see if that works. If it doesnt re enable smart reflex and go tot MPU voltages. Next to the words MPU voltages there is a blue plus/minus button. Click that and click the plus one time. Accept it and push again the oke button. The other two things I dont exactly know..
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
I tried both things you mentioned with no luck
I'm still searching around for those other things beekay201 mentioned earlier. I found that Omap Flash is a tool for flash roms in binary mode, so that way you can unbrick some phones. Still trying to find out how that can be useful for my case (forum.xda-developers.com/showthread.php?t=1242330)
bpyazel said:
Honestly, if you are getting reboots on a clean stock (including stock kernel) , it's probably a hardware issue.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
The thing is that after a clean stock install everything works fine for a week or two, that means no random reboots, and i can transfer any kind of file of any size with no problem. Then for some estrange reason (even with no crazy apps installed) starts with a random reboot, after that first reboot i know is time and that i wont be able to transfer files anymore, because it WILL reboot while i'm transfering files. Other thing i have noticed is that around where the camera lens is, get really hot. So I think that the reason it reboots is kernel panic caused by overheating, or the other thing is that my sdcard have some issues when writing files.
Right now i'm using CyanogenMod 10.0.0-maguro with jelly bean 4.1.2 and franco.kernel 3.0.51-nightly-512GPU and i have already tried going back to stock.
how can a I check if my hardware is fine? Is there any app out there?
Thanks!
elcampeondelrodeo said:
Thanks for the reply guys!
I tried both things you mentioned with no luck
I'm still searching around for those other things beekay201 mentioned earlier. I found that Omap Flash is a tool for flash roms in binary mode, so that way you can unbrick some phones. Still trying to find out how that can be useful for my case (forum.xda-developers.com/showthread.php?t=1242330)
The thing is that after a clean stock install everything works fine for a week or two, that means no random reboots, and i can transfer any kind of file of any size with no problem. Then for some estrange reason (even with no crazy apps installed) starts with a random reboot, after that first reboot i know is time and that i wont be able to transfer files anymore, because it WILL reboot while i'm transfering files. Other thing i have noticed is that around where the camera lens is, get really hot. So I think that the reason it reboots is kernel panic caused by overheating, or the other thing is that my sdcard have some issues when writing files.
Right now i'm using CyanogenMod 10.0.0-maguro with jelly bean 4.1.2 and franco.kernel 3.0.51-nightly-512GPU and i have already tried going back to stock.
how can a I check if my hardware is fine? Is there any app out there?
Thanks!
Click to expand...
Click to collapse
512GPU? You mean your GPU is overclocked? Maybe try to set your GPU to stock. And if it gets really hot and you have random reboots you can try to over volt with trickster mod.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
512GPU? You mean your GPU is overclocked? Maybe try to set your GPU to stock. And if it gets really hot and you have random reboots you can try to over volt with trickster mod.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
No, I don't think my GPU is overclocked, that's the full name of the kernel, you say that the kernel automatically puts my GPU to 512?. Anyways i just installed that kernel two days ago just because i thought it might make the reboots go away. I'm having rebooting problems since february (just after upgrading to 4.2.1), so i don't think that the GPU is causing the reboots.
elcampeondelrodeo said:
No, I don't think my GPU is overclocked, that's the full name of the kernel, you say that the kernel automatically puts my GPU to 512?. Anyways i just installed that kernel two days ago just because i thought it might make the reboots go away. I'm having rebooting problems since february (just after upgrading to 4.2.1), so i don't think that the GPU is causing the reboots.
Click to expand...
Click to collapse
Well if it keeps rebooting you can try to over volt. Maybe that helps.
Sent from my Galaxy Nexus using XDA Premium HD app
OK I'll try that! Thanks for your help man!
Sent from my Galaxy Nexus using xda app-developers app
PLEASE DON'T TRY THIS FIX! If you are experiencing any touch screen irregularities, then it IS HARDWARE related. Use the warranty of the phone and either request a new device, or get a different device. Ignore the remainder of this post and the thread.
Sorry if this is very long and boring, but saying it all now saves everyone from saying it later
There is a massive problem that the Z1 suffers from, an erratic touch screen.
Some people have the problem, whilst others don't. I am one of the unlucky owners of a Z1 which has this problem :crying:
People report that the screen registers an input, then shortly losses the input and then regains it, making web browsing difficult as anything you scroll by could be clicked by accident.
I suffer from that and then some. If I use the phone for a prolonged period of time (usually 20 minutes), the screen will register my input at completely different places to where my finger actually is!
This makes normal use almost impossible since you have no control as to where it will register your input.
Oddly enough, locking the phone for a few seconds (just long enough so that the phone falls into deep sleep) then waking it again makes the problem disappear temporarily. It does start doing it again eventually. This happens regardless of phone temperature. This also proves that the issue isn't hardware related, as if it was then it should be doing this all the time, regardless of anything.
Trying to do a clean install fails to fix the issue (at least for me), and even the highly anticipated KitKat update failed to address the issue, despite them claiming that KitKat will fix it (it didn't work for me).
NOW comes the possible solution. Since I know that this could not be a hardware issue, there must be a way to fix it via the software.
I researched a lot and found something that could fix the issue.
I'm saying this now. I don't guarantee that this will fix the problem, but trying won't hurt anyone
I didn't do a nandroid backup (I'm on 4.4.2 = no system mount in recovery), but if you feel uncomfortable with this, then by all means make one
You will need the following:
Root
Terminal Emulator
Any file explorer with root access
External microSD Card
Any stock/stock based Sony ROM (try the fix on other custom ROMS if you want. No harm in trying, cough NANDROID IS YOUR FRIEND )
1: Open up the Terminal Emulator
2: Type in "su" with no inverted commas.
3: Type in the following command: touch /sdcard1/Calibration.ini
There must be a space between "touch" and "/".
If done right, you should get no response (no message at all, just back to "[email protected]:/ #"
4: Enter and after that, shutdown the phone. Whilst it is booting, do not touch the screen. You can safely touch the screen after it is done booting (when you can see the UI). You can also reboot it instead of shutting it down, but I found that a proper shutdown works better (your mileage may very).
5: Goto a file explorer and delete the "Calibration.ini" file. This will prevent the phone from calibrating the screen after every reboot (not needed since it has just been calibrated).
6: All done :highfive:
Now, test the phone properly and see if the problem is gone.
If you have the time and patience, I recommend setting the screen timeout to 30 minutes and using the phone without letting the screen turn off. If it doesn't do anything strange in that time, then you can safely assume that the problem is gone for good :highfive:
Ever since I did this, the problem has ceased to be. It has gone and met its maker
Hopefully you will have the same results
Even if it didn't work, there was no harm in trying
Good luck! :good:
Note: For the app that does the same thing as this method, see post #2
Please link sources where you found all this info? I found threads about three years old using this method on G-Tablet and stuff from back in the day but wonder if it's still actually working.
There's also an APP that calibrates the screen without reboot with reference to above manual fix:
http://forum.xda-developers.com/showthread.php?t=934500
Beware, no idea what it does. If it works or if it ****s your phone up:
View attachment TouchRecalibrate.apk
Daelyn said:
Please link sources where you found all this info? I found threads about three years old using this method on G-Tablet and stuff from back in the day but wonder if it's still actually working.
There's also an APP that calibrates the screen without reboot with reference to above manual fix:
http://forum.xda-developers.com/showthread.php?t=934500
Beware, no idea what it does. If it works or if it ****s your phone up:
View attachment 2645905
Click to expand...
Click to collapse
Those which you posted are not exactly the ones I discovered.
That would be this thread:
http://forum.xda-developers.com/showthread.php?t=1960416
I knew about that app also, but I don't want to risk using it. I think that the manual method is better since it can work on any phone (or at least I think every phone)
That app may only be developed for a specific device and using it on other devices sounds like trouble to me.
Either way, the manual method worked for me. I severely doubted it would work but it did. I tested the phone for at least 1 hour straight without letting the display turn off. Game after game I ran, battery drained by at least 18% and there was not a sign that the screen was going to bugger out again
I even set the screen timeout to 30 minutes just to make sure it won't sleep.
Still no sign of the problem, 5 hours later
I haven't rebooted it yet. I don't know if it will come back once a reboot has happened...
Seems to be working
I did your method and also changed the touch filter level from 2 to 5 as mentioned in another thread. I havent had the issue since, not sure if it was your method or his or a combination of the 2, but really glad its gone. Thanks a million.
Daelyn said:
Please link sources where you found all this info? I found threads about three years old using this method on G-Tablet and stuff from back in the day but wonder if it's still actually working.
There's also an APP that calibrates the screen without reboot with reference to above manual fix:
http://forum.xda-developers.com/showthread.php?t=934500
Beware, no idea what it does. If it works or if it ****s your phone up:
View attachment 2645905
Click to expand...
Click to collapse
I tried the apk...for me it works fine for now... Will have to wait and see if it continues
Sent from my C6903 using XDA Premium 4 mobile app
Tried the method using terminal emulator and it seems the method has fix the problem,,
But i need to test again further..
Thankyou
Gesendet von meinem C6903 mit Tapatalk
I'm trying it with cm... I'll report in some days. But thank you allready
Tried the method. Touch sensor on the edge of the screen still seems quite buggy from time to time. Everything else seems to show some improvement. Will try a bit longer and report back.
Sent from my C6902 using xda premium
I'm tyring this fix on my Z1 flashed RomAur 6.1, and working fine.
Touch response is very sharp and fix touch problem.
Many Thanks!
Is that normal?:what::what:
Inviato dal mio C6903 utilizzando Tapatalk
[Fenix] said:
Is that normal?:what::what:
Inviato dal mio C6903 utilizzando Tapatalk
Click to expand...
Click to collapse
Space is missing after "touch"...
touch /sdcard1/calibration.ini
You forgot the space
Sent from my C6902 using xda premium
The app seems to invoke online calibration. Works fine here and I feel improvement. Of course it could be placebo.
I will try to disassemble the app when I got the time. I want to know what it does and how it does it.
Sent from my C6903 using Tapatalk
Please Delete, already answered.
Please Delete, already answered.
[Fenix] said:
Is that normal?:what::what:
Inviato dal mio C6903 utilizzando Tapatalk
Click to expand...
Click to collapse
you could also try the APK in the other post... i tried that and it worked for me
The app has definitely worked for me. I would mostly notice the bug when scrolling in the Falcon Twitter app - tweets would open accidentally all the time, it hasn't happened once since using the app.
R: Potential Xperia Z1 touch screen fix (please test)
Josh.L.Wang said:
touch /sdcard1/calibration.ini
You forgot the space
Sent from my C6902 using xda premium
Click to expand...
Click to collapse
RyokoN said:
Space is missing after "touch"...
Click to expand...
Click to collapse
lol maybe i'm blind
Thanks for the help it works
I'm very glad to see that people are having positive results with the terminal method and even the application that was linked earlier
Doubted that the application world work
I have to add this though. After testing a bit more, the problem hasn't come back. However, I did discover that wiping cache and delvik will make the problem come back again with a vengeance. So, I did the fix again and what do you know? Problem is gone again
One last thing. Every time the phone boots up with the Calibration.ini file, you might get different results with regards to calibration. I recommend that once you are contempt with the outcome of the calibration, DELETE THE FILE ASAP!
Also, shutdown the phone instead of rebooting it
Have fun
D395267 said:
I'm very glad to see that people are having positive results with the terminal method and even the application that was linked earlier
Doubted that the application world work
I have to add this though. After testing a bit more, the problem hasn't come back. However, I did discover that wiping cache and delvik will make the problem come back again with a vengeance. So, I did the fix again and what do you know? Problem is gone again
One last thing. Every time the phone boots up with the Calibration.ini file, you might get different results with regards to calibration. I recommend that once you are contempt with the outcome of the calibration, DELETE THE FILE ASAP!
Also, shutdown the phone instead of rebooting it
Have fun
Click to expand...
Click to collapse
I have not had any problems since using the app.. I have rebooted quite a few times and all is still good...
So nice to actually being able to use swipe keyboard without problems
We owe ye
Sent from my C6903 using XDA Premium 4 mobile app
New poll is up!
I bid you all good day