Related
Hi all,
I have a fairly frequent issue with my Glide Captivate. Unfortunately too frequently, when I turn it on, the network is disabled (O with slash through it), most widgets say "Loading Widget..." the slide down status menu shows nothing (well except the Wifi / BT / GPS toggles.) and "USB Connected" if it is. Nothing else. The phone gets incredibly hot, and near as I can tell sucks the battery. The screen often won't unlock - it will just light up the 4 soft buttons on the bottom (menu, home, etc). When I CAN get on it, I get frequent "Sorry! Process system is not respoding"
Attempting to go through System / Manage Applications - usually about a minute in the screen will blank for a minute then go back to the lock screen.
Any suggestions?
Thanks.
Try re flashing the rom, if you're using one. If you're not using a rom, and it's not rooted, try restoring it?
Sent from my SAMSUNG-SGH-I927R using xda premium
doode2011 said:
Try re flashing the rom, if you're using one. If you're not using a rom, and it's not rooted, try restoring it?
Sent from my SAMSUNG-SGH-I927R using xda premium
Click to expand...
Click to collapse
Stock rom, it is rooted. Unfortunately, restoring it is the fix - like every week
Could be a hardware issue if you have a warrenty i would complain and try and get a new one which means you need to flash a non rooted stock rom i dont know if you can do this ive never had to remove root
sent from my captivate glide
jayjayjoker2 said:
Could be a hardware issue if you have a warrenty i would complain and try and get a new one which means you need to flash a non rooted stock rom i dont know if you can do this ive never had to remove root
sent from my captivate glide
Click to expand...
Click to collapse
I was going to say this next. But didn't the cwm thread find a way to go back to stock? Check put that thread
Sent from my SAMSUNG-SGH-I927R using xda premium
All u have to do it download the firmware from samsungs site and flash it and it will be like out of the box no root or anything
Sent from my SAMSUNG-SGH-I927 using XDA
Hey i had the same issue for months with my glide. I bought it outright from rogers and was just running it stock. Drove me nuts exchanged the phone 3 times. Finally narrowed it down to the media scanner/sd card issue. The scanner would run a few times and then reboot the phone. I tried booting it without the sd card in and booted up fine. Tried a dew diff sd cards and seem to have found one that works, but it would happen once every few weeks for me. Ive looked it up on the forums its that common problem with samsung phones. Pain in the butt. Cant remember if you said you were rooted id recommend trying that im too chicken myself. Happens on my sgs2 also.
Sent from my GT-I9100M using xda premium
I have also this issue once in a while, its very annoying, I think that if we could have a AOSP rom that would fix it since samsung polluted their rom so much. Maybe if we get lucky, with the ICS/JB update that issue will be gone. I have also another issue, the phone randomly turns "off" and becomes really hot, it depends on how long it takes for me to realize, but most of the time, it has drained my battery to near death. I don't think those are hardware related issues, but more on the software side since its not AOSP.
Does the temperature rise when it's charging? Because that happens to my phone too. If you have the voltage control, try lowering the max cpu use to lower the temperature a little bit.
Sent from my SAMSUNG-SGH-I927R using xda premium
I update to v20c a couple of times, the first time I use machzelet unbrick method using v20c kdz, I had a couple of random reboots and the rom was not rooted, after that I flashed brianlili's rotted v20c images, but I still have the random reboots (but I install a lot of software), I do a factory reset and I don't install any software at all and I will test the stability. Any ideas about the random reboots: could it be setcpu, titanium BK, nobloat or lucky patcher?, any ideas?
Thanks.
fguzmant said:
I update to v20c a couple of times, the first time I use machzelet unbrick method using v20c kdz, I had a couple of random reboots and the rom was not rooted, after that I flashed brianlili's rotted v20c images, but I still have the random reboots (but I install a lot of software), I do a factory reset and I don't install any software at all and I will test the stability. Any ideas about the random reboots: could it be setcpu, titanium BK, nobloat or lucky patcher?, any ideas?
Thanks.
Click to expand...
Click to collapse
All I know is I did the official AT&T ICS Install and it is stable as hell, I haven't had a random reboot or dreaded HoNo/CM boot loop at all.
The only thing I miss is the fact that this is not rootable at this time. If and when this does I will root and stick with stock rom and kernel as this has been the stablest my phone has ever been!
- Kaos
I upgraded mine from stock unrooted gb using the lg update tool. I've had one crash/reboot since yesterday when playing a video from gallery using the stock video player. I don't have any of these apps installed. If I keep on having constant random reboots I'll probably try a factory reset and see if it fixes it.
Never saw reboots on 20c, 10f or other unofficial roms.
I strongly recommend doing a factory reset for everyone who upgraded to V10c, even if you don't notice any problems (yet). It's already fixed issues for many people.
My guess is it will fix the reboots.
20c is really unstable for me; even after factory resets. As much as I like UI, I can't be bothered to deal with it and it's terrible battery life.
Sent from my LG-P930 using xda app-developers app
No more reboots
After the factory reset that I've done yesterday, I had no reboots today, also I recommend reading this google support post:
http://code.google.com/p/android/issues/detail?id=28819
The first application, that I suspect as responsible for the reboots its app manager.
Other possible cause could be battery managers aka juice defender or easy battery saver.
The post mention about kernel panic error, and that it’s caused by excessive memory use of an application, I notice that facebook app use aproximate 100mb of memory, so I uninstall it and use the web site (with dolphin).
Other thing that I’ve done was disable almost all lg applications using the stock app manager.
I will install some other applications and let you know about the stability on weekend.
Bad news, Reboots reapear.
So it seems official, ICS for LG Nitro it's not stable:
http://support.lgforum.com/lg/topics/problems_with_ics
Ya know, I haven't had any issues at all with the ICS update.
mattman86 said:
Ya know, I haven't had any issues at all with the ICS update.
Click to expand...
Click to collapse
I completely agree, ICS update is running VERY stable with great options to disable a bunch of bloatware. Great options until we get a easy root method
I have the worst problem with GPS locating me with ICS. It takes at least 5-10 minutes for me to connect in google navigation. Only problem I've had with stock ICS though.
Sent from my LG-P930 using xda app-developers app
pbutler1224 said:
I have the worst problem with GPS locating me with ICS. It takes at least 5-10 minutes for me to connect in google navigation. Only problem I've had with stock ICS though.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I have the same problem. I cannot get GPS lock on V20C
Terrrible batttttery life
Battery life has been terrible since the update, no gps, no wireless, screen dimed to low, and tweaks here and there to save battery and it my phone doesnt hold more than 7 hours of battery life on idle..
pbutler1224 said:
I have the worst problem with GPS locating me with ICS. It takes at least 5-10 minutes for me to connect in google navigation. Only problem I've had with stock ICS though.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
gps locked on quickly and easily for me, within 20 seconds. And that was indoors !
fguzmant said:
So it seems official, ICS for LG Nitro it's not stable:
http://support.lgforum.com/lg/topics/problems_with_ics
Click to expand...
Click to collapse
How does this make it official?
Sent from my LG-P930 using xda app-developers app
zapper_master said:
gps locked on quickly and easily for me, within 20 seconds. And that was indoors !
Click to expand...
Click to collapse
I don't have this problem too. I was able to get a GPS lock in google maps in ~20 seconds, and that too inside the house.
mattman86 said:
Ya know, I haven't had any issues at all with the ICS update.
Click to expand...
Click to collapse
Yep, I heard that, so, why meeeee?
Sorry about that, I was trying to figure out, and I have some clues, I did not use the original microSD, I have a 32 GB sandisk, but gingerbread work just fine with that memory, could it be?
dnorthington said:
How does this make it official?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
Because the problem is acknowledged in that official LG Forum.
esqwav said:
I don't have this problem too. I was able to get a GPS lock in google maps in ~20 seconds, and that too inside the house.
Click to expand...
Click to collapse
Google Maps does not have the GPS lock problem. It's the navigation app that has problems getting GPS lock. It'll be stuck on the screen that says "Searching for GPS"
996gt2 said:
Google Maps does not have the GPS lock problem. It's the navigation app that has problems getting GPS lock. It'll be stuck on the screen that ways "Searching for GPS"
Click to expand...
Click to collapse
I use to have this problem in GB, I read in a post that it's related with the servers used in the file /system/etc/gps.conf. You can use an app called FasterFix (require root) to solve this problem.
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...
I had this problem before a few weeks ago, but a full boot.img stock reversion fixed things and I unrooted (then re-rooted) and installed the PACman ROM with the AK Kernel. Everything was fine until a few weeks later it started to lag really bad again. I'm talking the screen would hang for 5-10 seconds or just freeze completely. Earlier today I had to pull my battery about 3 times because of the freezes. I tried to install a new kernel a week ago, but that made it worse.
Why does it keep doing thing. I love the custom ROMs and the kernel tweaks, but I won't be able to use them if I go to stock...
Same thing here on complete stock 4.2.2
Been doing factory reset once a month since I got the phone in September.
Sent from my Galaxy Nexus using xda app-developers app
brad416 said:
Same thing here on complete stock 4.2.2
Been doing factory reset once a month since I got the phone in September.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
What are we doing wrong? :crying:
Had d same prob
Just use lagfix(fstrim) from google play
Sent from my Galaxy Nexus using xda premium
seriousia said:
Had d same prob
Just use lagfix(fstrim) from google play
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
sounds too good to be true tbh.
gonna try
RedDeadDorito said:
What are we doing wrong? :crying:
Click to expand...
Click to collapse
Not giving any information other than your own "diagnosis" for one.
063_XOBX said:
Not giving any information other than your own "diagnosis" for one.
Click to expand...
Click to collapse
i didn't give a diagnosis. I gave symptoms.
RedDeadDorito said:
i didn't give a diagnosis. I gave symptoms.
Click to expand...
Click to collapse
You interpreted the symptoms yourself rather than just report the issue and what software combination is resulting in the issue. Its lagging but why is it lagging? "Lag" isn't a symptom its a result of something else going on deeper down.
063_XOBX said:
You interpreted the symptoms yourself rather than just report the issue and what software combination is resulting in the issue. Its lagging but why is it lagging? "Lag" isn't a symptom its a result of something else going on deeper down.
Click to expand...
Click to collapse
I'm sorry, man. I didn't realize I had to report the issues exactly as I know them. I totally wouldn't resolve the problem myself if I knew what it was.
I guess you missed the part where I asked what software combination might be causing it.
Diagnosing problems you don't understand is exactly the kind of thing that makes it impossible to help someone. The phone may be right in front of you and you may know what you did but so far all you've done is tell us that:
1. Your phone lags
2. You tried a different kernel
3. You've pulled the battery
Not much to work with is it?
What CPU settings are you using?
What superuser apps?
Etc.
How much free space is on your phone? How about ram usage?
063_XOBX said:
I guess you missed the part where I asked what software combination is causing it.
Click to expand...
Click to collapse
I don't know. Turning the phone on takes about 3 seconds, same with turning it off. After unlocking, it hangs for about 4 seconds. Opening Chrome takes 5-10 seconds. Pressing the home button while on any app takes 5 seconds before it gives a response.
Don't say those are regular waiting times either, before I had these problems, things would appear at the touch of a button.
I also forgot to mention that a fresh ROM install doesn't help.
bodh said:
How much free space is on your phone? How about ram usage?
Click to expand...
Click to collapse
1.1GB
550-600mb+ being used at any given time.
RedDeadDorito said:
I don't know. Turning the phone on takes about 3 seconds, same with turning it off. After unlocking, it hangs for about 4 seconds. Opening Chrome takes 5-10 seconds. Pressing the home button while on any app takes 5 seconds before it gives a response.
Don't say those are regular waiting times either, before I had these problems, things would appear at the touch of a button.
I also forgot to mention that a fresh ROM install doesn't help.
Click to expand...
Click to collapse
"Fresh ROM install" as in you're just wiping cache and data then reinstalling?
Move on to the next step which is flashing a factory image.
063_XOBX said:
I guess you missed the part where I asked what software combination might be causing it.
Diagnosing problems you don't understand is exactly the kind of thing that makes it impossible to help someone. The phone may be right in front of you and you may know what you did but so far all you've done is tell us that:
1. Your phone lags
2. You tried a different kernel
3. You've pulled the battery
Not much to work with is it?
What CPU settings are you using?
What superuser apps?
Etc.
Click to expand...
Click to collapse
.180ghz min
1.4ghz max
interactivex
headphone boost 1
everything else is unchanged.
using SuperSU.
063_XOBX said:
"Fresh ROM install" as in you're just wiping cache and data then reinstalling?
Move on to the next step which is flashing a factory image.
Click to expand...
Click to collapse
factory reset
formatting system
then wiping cache
then installing
I think that space is an issue. I've read that once you get below 3 or 4 gigs free, the lag begins. Supposedly, on any disk, you should keep about 20% free, which for a 16gb gnex is 3.2gig.
Edit: isn't 180ghz min pretty low? I've seen 384 as a min suggested if lagging is an issue. And i think you mean mhz.
bodh said:
I think that space is an issue. I've read that once you get below 3 or 4 gigs free, the lag begins. Supposedly, on any disk, you should keep about 20% free, which for a 16gb gnex is 3.2gig.
Edit: isn't 180ghz min pretty low? I've seen 384 as a min suggested if lagging is an issue. And i think you mean mhz.
Click to expand...
Click to collapse
really? but I like my music :crying:
This is why they shouldn't have gotten rid of SD cards...
I'll see if clearing out my HDD space does anything. I've had it that full for quite some time though...
I'll see if putting 384 as min fizes it.
Your device also might not be able to handle 1.4 GHz oc. While its originally a 1.5ghz processor mild imperfections in the manufacturing process result in it being sold as a (guaranteed safe at) 1.2ghz processor.
What that means is that not every phone will handle the same speeds, voltages etc. You should try running at stock speeds for testing purposes.
I have this same issue, I've tried a number of different ROMs and kernals. They all start out great, then after about a month my phone starts to get random lag, then as time goes on it gets worse and worse until I bite the bullet and start over again
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