Related
I'm not sure if this has happened to anyone else..
However, this seems to be an ongoing issue with me and Android.
I've had the X10a and Nexus One .. both after only rooting it and using a different rom. While making phone calls and charging.. my phone would reboot..
Or playing a game on the phone.. it would reboot. I basically couldn't do anything without the phone rebooting. Which was sad.
Now with the Galaxy S2X.. This very same issue just happened to me moments ago.
Should I have never rooted it or changed the rom in the first place?
It was running very well before I decided to do so.. even while charging and talking on the phone.
Its funny because it just happened while charging.... I'm not even on the phone myself.
Does anyone seem to have any problem with this when using custom ROMs?
Because if this is true.. then I guess I'll flash the stock kernel and stuff back on the phone just to HOPE it doesn't occur then. :/
I've only experienced this after trying different roms and kernels. I flashed the stock kernel and the deodex rooted stock rom back at the same time and have had no such things happen again.
Imo, stock always runs better than any other rom. I always get better battery too.
My sensation was/is the same way, reboots, dropped signals and all until I put it back to stock rooted. Now it's fine.
——————————
Deebo took your bike too?
Yes I have had it more often on this phone though but it has been fixed by wiping the proper things first then flashing. If not then you might need to redownload the file.
If that doesnt work then you need to make sure that the kernel you are using is compatible with the rom
Also make sure that you are using the proper cpu software for the kernel.. Setcpu seems to work good for most but on Juggernauts new kernel they highly recommend Fauxclock .
I've run roms and kernels since we got root. Never had a random reboot or any other problem for that matter.
Sent from my SGH-T989 using Tapatalk
no6969el said:
Yes I have had it more often on this phone though but it has been fixed by wiping the proper things first then flashing. If not then you might need to redownload the file.
If that doesnt work then you need to make sure that the kernel you are using is compatible with the rom
Also make sure that you are using the proper cpu software for the kernel.. Setcpu seems to work good for most but on Juggernauts new kernel they highly recommend Fauxclock .
Click to expand...
Click to collapse
The only thing I'm worried about is if I continue to wipe and reinstall these customs ROM's that this issue could worsen, but you said that Fauxclock was highly recommended for Jug's Rom? I should try that out myself.
I've always done exactly what was written on the Instructions themselves.
But as for now. . I did a full wipe.. including my SD and the USB data and did a practice call for roughly an hour with me playing games and surfing. So far, there has been any problems. I hope this is perm!
I'd hate to waste another $500 phone D:
As far as the problem kernel with rom etc..
I am running Jug's rom straight. No different kernel's nothing.
I just had it happen to me last night. First time on this phone it has happened. It its stock, rooted. Happened while I was paying music in the car. My other phones with custom roms used to do it all the time.
I wonder if this has happened to anyone without ANY mods on their phone? =X
Fix Permissions
What exactly does that do?
jangst123 said:
Fix Permissions
Click to expand...
Click to collapse
Sent from my SGH-T989 using XDA App
none, with Juggernaut, they did an excellent job
yes, with stock ROM
Sighx said:
I'm not sure if this has happened to anyone else..
However, this seems to be an ongoing issue with me and Android.
I've had the X10a and Nexus One .. both after only rooting it and using a different rom. While making phone calls and charging.. my phone would reboot..
Or playing a game on the phone.. it would reboot. I basically couldn't do anything without the phone rebooting. Which was sad.
Now with the Galaxy S2X.. This very same issue just happened to me moments ago.
Should I have never rooted it or changed the rom in the first place?
It was running very well before I decided to do so.. even while charging and talking on the phone.
Its funny because it just happened while charging.... I'm not even on the phone myself.
Does anyone seem to have any problem with this when using custom ROMs?
Because if this is true.. then I guess I'll flash the stock kernel and stuff back on the phone just to HOPE it doesn't occur then. :/
Click to expand...
Click to collapse
Are you overclocking?
I am running jugs rom. Before I cleaned everything I did move a lot of apps to SD. Maybe that cause it but as for now I have no.problem. definitely report in the future should there be anymore.
AllGamer said:
none, with Juggernaut, they did an excellent job
yes, with stock ROM
Click to expand...
Click to collapse
Sent from my SGH-T989 using XDA App
Reviving old thread... I have a completely stock S2X running 4.0.3 and it randomly reboots or shuts itself off.
I'm trying to figure out if it's a wayward app or a hardware problem. Thinking of rooting and removing the bloatware.
I also saw that it could be a faulty power button, but it also happens by itself, sitting on a desk.
jabela said:
Reviving old thread... I have a completely stock S2X running 4.0.3 and it randomly reboots or shuts itself off.
I'm trying to figure out if it's a wayward app or a hardware problem. Thinking of rooting and removing the bloatware.
I also saw that it could be a faulty power button, but it also happens by itself, sitting on a desk.
Click to expand...
Click to collapse
Root try new rom and kernel see if that fixes it.
Did anyone find any solution? everything in this thread failed for me ..
Have you tried updating to jellybean? Mu phone used to randomly reboot on 4.0.4 probably once a day, and hasn't done it since I did. I am on stock rom.
Sent from my SGH-T989D using Tapatalk 4 Beta
Hello people!
I am a new member with XDA Developers
Anyways, I would like to ask if any of you face this problem where at any random time the phone would start vibrating continously until you shut down the phone and is there a fix for this?
l_daruwala said:
Hello people!
I am a new member with XDA Developers
Anyways, I would like to ask if any of you face this problem where at any random time the phone would start vibrating continously until you shut down the phone and is there a fix for this?
Click to expand...
Click to collapse
Hello and welcome the the XDA Forum!
I've found at time that the app "Whatsapp" when I get a message, My phone will constantly vibrate until the screen goes off for 5-10 seconds then it's fine until I turn the screen / unlock the phone, I think it's a common problem as I remember someone else had this issue.
Jamie
jamidodger1 said:
Hello and welcome the the XDA Forum!
I've found at time that the app "Whatsapp" when I get a message, My phone will constantly vibrate until the screen goes off for 5-10 seconds then it's fine until I turn the screen / unlock the phone, I think it's a common problem as I remember someone else had this issue.
Jamie
Click to expand...
Click to collapse
Yes i also found that too, but sometimes I encounter the problem with SMS too. Never encountered this problem with my previous phones, the GALAXY Ace (GT-S5830) and the GALAXY 3 (GT-I5801)
l_daruwala said:
Yes i also found that too, but sometimes I encounter the problem with SMS too. Never encountered this problem with my previous phones, the GALAXY Ace (GT-S5830) and the GALAXY 3 (GT-I5801)
Click to expand...
Click to collapse
It hasn't done it for SMS for me but yeah it never did it on my previous phone either ZTE Blade
When my profile switch app change profile and take phone to silent mode sometimes makes my W too...
The only solution reboot...
Looks like this affects all GALAXY W's
l_daruwala said:
Looks like this affects all GALAXY W's
Click to expand...
Click to collapse
Yes, and it happens always the best time... meetings, driving...etc.
never happen to me
but if it happened, I'll flash a new fresh ROM and see if it solves the problem
Happens to mine, seems like it was only when Whatsapp and something else had a notification at the same time.
soulbkd said:
never happen to me
but if it happened, I'll flash a new fresh ROM and see if it solves the problem
Click to expand...
Click to collapse
I had many ROMs like: Stock, Kezra, F.A.W Special. I get vibration in each case.
mayerkemp said:
I had many ROMs like: Stock, Kezra, F.A.W Special. I get vibration in each case.
Click to expand...
Click to collapse
that's weird, mine never experience it
I have tried stock, Bagux's, Blacknote, Kezra, and deodexed rom.
maybe something to do with HW version?
mine is rev 0.6 (via *#2222#)
soulbkd said:
that's weird, mine never experience it
I have tried stock, Bagux's, Blacknote, Kezra, and deodexed rom.
maybe something to do with HW version?
mine is rev 0.6 (via *#2222#)
Click to expand...
Click to collapse
Unfortunately mine too. No more idea.
Damn, mine is also REV 0.6 as well.
Still same problem
Mine also rev 0.6
Tried Rebel Rom, Bagux, Bionic Cow 2 v 7, stock DXLM3, stock XXLM8 , all still has the same random vibration.
And the vibration won't stop until you reboot.
Probably hardware related?
This happens to me since the first day I got this phone...
Honestly, it's annoying me !
Cause the only way to Stop it, is a reboot..
Sometimes it starts to vibrate in school, and as Im using a TPU SoftCase it's even more uncomfortable...
I thaught I was the only one, but seems like it affects all Wonders..
No matter which Rom I use, everytime the same Problem
A random time.
mayerkemp said:
I had many ROMs like: Stock, Kezra, F.A.W Special. I get vibration in each case.
Click to expand...
Click to collapse
same problem
Every now and then my phone is getting stuck in landscape. I first thought is was the ROM I was using. Then today I unrooted and put back to stock and it happened again. If I reboot it fixes it. Is this just a JB bug?
Sounds more like something wrong with your device.
It started after 4.1
Doesn't mean it's not a problem with your device. A search turns up no complaints about anything like this and I've never had it before.
my wifes NS4G also has the issue after jellybean.
venom_762 said:
my wifes NS4G also has the issue after jellybean.
Click to expand...
Click to collapse
Don't have it on my NS either. Also on JB.
That's happened to me a few times, using the unified remote app. But going to the home screen fixed it for me, don't know if its the same issue as you're having.
Sent from my Galaxy Nexus using xda premium
It just doesn't seem hardware to me.
venom_762 said:
Every now and then my phone is getting stuck in landscape. I first thought is was the ROM I was using. Then today I unrooted and put back to stock and it happened again. If I reboot it fixes it. Is this just a JB bug?
Click to expand...
Click to collapse
I have noticed the same thing on mine... and it started happening after the 4.2.2 update. It doesn't happen often though and only reboot fixes it. It has to be software related...I don't know what causes it though...
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
wbexpress said:
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
Click to expand...
Click to collapse
it turns on with pac 20.0 not sure if it stays on though. I'm on the latest twrp. full wiped, adsk and nos script. give that a try?
wbexpress said:
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
Click to expand...
Click to collapse
I works on the 2/26/13 Nightly of CM10.1. You wanna try and clean flash it? If it doesn't work then it's just a problem with your phone hardware instead of the software. Might be a buddy bluetooth adapter or such.
zxstyle07 said:
it turns on with pac 20.0 not sure if it stays on though. I'm on the latest twrp. full wiped, adsk and nos script. give that a try?
Click to expand...
Click to collapse
Fingers crossed, so far so good. I reinstalled Rootbox which is awesome. I changed from CWM back to TWRP and also installed Cerux 1.42 which in the thread made mention of the bluetooth issue being fixed, and being kernel, not ROM related. I am using crossbreeder which makes things crazy fast. I saw the "nos script" in some thread but couldn't find it with a Google search. Do you have a link for it and what exactly does it do?
Edit: Crap. it went away. Oh well, back to 4.1. Hellybean it is. I just don't get it. BT works fine on any 4.1 or ICS ROM. Only thing with 4.1 is music skips in my music player but I can live with that, I can't live with no BT. Thanks for your help. Maybe when source drops it will be all good.
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
joeyrey said:
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Yup, this helped for my JB-MR build 4!
no more having to reboot to enable bluetooth
wbexpress said:
Fingers crossed, so far so good. I reinstalled Rootbox which is awesome. I changed from CWM back to TWRP and also installed Cerux 1.42 which in the thread made mention of the bluetooth issue being fixed, and being kernel, not ROM related. I am using crossbreeder which makes things crazy fast. I saw the "nos script" in some thread but couldn't find it with a Google search. Do you have a link for it and what exactly does it do?
Edit: Crap. it went away. Oh well, back to 4.1. Hellybean it is. I just don't get it. BT works fine on any 4.1 or ICS ROM. Only thing with 4.1 is music skips in my music player but I can live with that, I can't live with no BT. Thanks for your help. Maybe when source drops it will be all good.
Click to expand...
Click to collapse
http:// http://forum.xda-developers.com/showthread.php?t=2158329
joeyrey said:
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Well, what seems to happen is it is fine for 15-30 minutes after I've freshly installed the ROM, then it just turns off. When I then try to turn it back on it hangs at "turning on" and then goes back to off. At that point when I click "turn on", it doesn't even move. I'm a gonna try the fix, nothing to lose at this point...
Nuts. It fast moves to on and immediately goes back to off. White flag, thanks to all.
Apply the fix and delete all you devices then try turning it on and off with nothing on it...if it works then add devices one by one...if you have devices married to it the patch might not work also I think my computer dongle was the culprit
Sent from my SAMSUNG-SGH-T989 using xda premium
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
djtheraven said:
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Yeah, how about that. I can't see that it's hardware-related, it's perfect on 4.1.
wbexpress said:
Yeah, how about that. I can't see that it's hardware-related, it's perfect on 4.1.
Click to expand...
Click to collapse
Your exactly right...
Sent from my SAMSUNG-SGH-T989 using xda premium
djtheraven said:
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
If you ever figure it out, please put something here. I keep looking every so often, I have to believe enough folks are having the issue that eventually someone is gonna fix it. Thanks...
wbexpress said:
If you ever figure it out, please put something here. I keep looking every so often, I have to believe enough folks are having the issue that eventually someone is gonna fix it. Thanks...
Click to expand...
Click to collapse
I'm posting to a couple of devs hope they can get it...the problem was people were commenting that it worked when they had no Bluetooth device hooked up...if you uninstall all devices then bt will toggle on and off...so they thought it was working when it wasn't...
Sent from my SAMSUNG-SGH-T989 using xda premium
bluetooth issues
djtheraven said:
I'm posting to a couple of devs hope they can get it...the problem was people were commenting that it worked when they had no Bluetooth device hooked up...if you uninstall all devices then bt will toggle on and off...so they thought it was working when it wasn't...
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Has anyone had any luck with this? I've tried various combinations of different 4.2.2 roms and kernels and have the same issues described in this thread with all of them.
Not a perfect answer...
RandyToe said:
Has anyone had any luck with this? I've tried various combinations of different 4.2.2 roms and kernels and have the same issues described in this thread with all of them.
Click to expand...
Click to collapse
I found one thing that at least gets it working again without rebooting is to activate airplane mode. Its faster than rebooting. Wish I had a better answer...
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