Related
Hi,
I just got my Galaxy Nexus (European ver., 4.1.1) few days ago and it randomly crashes all the time, especially when using apps with calling function (eg. dialer, viber, walkie talkie app...etc). It works fine sometimes and it crash and reboot automatically sometimes....
I have tried to flash it to CM10 and CM9, but the problem is still there.
Does any body know what's the problem?
I have two nexus (one for my family), and they both have the same problem.....
sorry for n00bness, but how to do reset to factory settings with customs rom? i tried settings>> backup and restore>> factory restore, but it didn't work.
Thank you
secretiff said:
Hi,
I just got my Galaxy Nexus (European ver., 4.1.1) few days ago and it randomly crashes all the time, especially when using apps with calling function (eg. dialer, viber, walkie talkie app...etc). It works fine sometimes and it crash and reboot automatically sometimes....
I have tried to flash it to CM10 and CM9, but the problem is still there.
Does any body know what's the problem?
I have two nexus (one for my family), and they both have the same problem.....
sorry for n00bness, but how to do reset to factory settings with customs rom? i tried settings>> backup and restore>> factory restore, but it didn't work.
Thank you
Click to expand...
Click to collapse
Well, if you have a custom rom, you probably have a custom recovery such as TWRP or CWM (ClockWorkMod Recovery), reboot to recovery, and select wipe data/factory reset, yes, and you are done.
If you are having problems rebooting to recovery, just power off the phone, hold volume up + volume down + press power, press volume down until you see the word "Recovery" and then hit power.
Wiping from a custom recovery (ClockWorkMod or TWRP) will not wipe your internal SD (pictures,music) but it will wipe your apps/settings. Wiping from a stock recovery will wipe your pictures/music/everything in addition to your apps/settings.
EDIT: What I find funny is that your phone reboots and both of them. Flash stock google factory image and see if it reboots. If it does, probably its a faulty phone. It would be a great idea to lock the bootloader with stock rom and return the device.
akash3656 said:
Well, if you have a custom rom, you probably have a custom recovery such as TWRP or CWM (ClockWorkMod Recovery), reboot to recovery, and select wipe data/factory reset, yes, and you are done.
If you are having problems rebooting to recovery, just power off the phone, hold volume up + volume down + press power, press volume down until you see the word "Recovery" and then hit power.
Wiping from a custom recovery (ClockWorkMod or TWRP) will not wipe your internal SD (pictures,music) but it will wipe your apps/settings. Wiping from a stock recovery will wipe your pictures/music/everything in addition to your apps/settings.
EDIT: What I find funny is that your phone reboots and both of them. Flash stock google factory image and see if it reboots. If it does, probably its a faulty phone. It would be a great idea to lock the bootloader with stock rom and return the device.
Click to expand...
Click to collapse
yes, they both rebooted with google stock rom when i got them! so i thought maybe it was something do with comparability or bugs from the stock rom...so i flash them with CM10, not working. then i thought...maybe it's the jelly bean? so i flash CM9....and it still happens...
Thanks for your suggestion, reli appreciate that
secretiff said:
yes, they both rebooted with google stock rom when i got them! so i thought maybe it was something do with comparability or bugs from the stock rom...so i flash them with CM10, not working. then i thought...maybe it's the jelly bean? so i flash CM9....and it still happens...
Thanks for your suggestion, reli appreciate that
Click to expand...
Click to collapse
I've also heard, some phones don't like Jelly Bean. But you have issues with CM9 too, so its really weird. Only solution for them was to return the device. There are reports of people having difficulties with any Jelly Bean based ROM (even stock)
akash3656 said:
I've also heard, some phones don't like Jelly Bean. But you have issues with CM9 too, so its really weird. Only solution for them was to return the device. There are reports of people having difficulties with any Jelly Bean based ROM (even stock)
Click to expand...
Click to collapse
oh...really??? guess we are just the unlucky minors...everybody is so happy with their nexus
it really irritates me cause i like my nexus, but it just have its spontaneous psycho flicks
after rebooting, it doesn't work right away...if i use those calling apps right after it finishes reboot, it will reboot again :crying:
I have to wait for some moments for it to work.......
sure im gonna return it, and buy another one from other stores... *sighs*
secretiff said:
oh...really??? guess we are just the unlucky minors...everybody is so happy with their nexus
it really irritates me cause i like my nexus, but it just have its spontaneous psycho flicks
after rebooting, it doesn't work right away...if i use those calling apps right after it finishes reboot, it will reboot again :crying:
I have to wait for some moments for it to work.......
sure im gonna return it, and buy another one from other stores... *sighs*
Click to expand...
Click to collapse
Sorry to hear man. Looks like it is a faulty one. However, Viber if you don't know, doesn't work on Jelly Bean. If you don't mind waiting, maybe you should use a spare phone in the mean time and wait for the next Nexus. :good:
akash3656 said:
Sorry to hear man. Looks like it is a faulty one. However, Viber if you don't know, doesn't work on Jelly Bean. If you don't mind waiting, maybe you should use a spare phone in the mean time and wait for the next Nexus. :good:
Click to expand...
Click to collapse
I tried to go to my cwm recovery and chose wipe data/factory reset but it's still CM9...
I would like to flash back to the stock rom, unlockbootload and unroot it so i can return. is there any way to do that? there isn't many tutorials online....
(Im using mac.)
Thank You
secretiff said:
I tried to go to my cwm recovery and chose wipe data/factory reset but it's still CM9...
I would like to flash back to the stock rom, unlockbootload and unroot it so i can return. is there any way to do that? there isn't many tutorials online....
(Im using mac.)
Thank You
Click to expand...
Click to collapse
nvm, i have already done it with my frds pc!
Hi, there are thousands of people with the same problem, its not the rom(JB)... but the proximity sensor that crashes the kernel, during calls, make the phone freeze/reboot.Search in google groups issue 37485, there are no solution, google and samsumg, dont say a word...It happens in nexus s too.
I have the same problem
firestruck said:
Hi, there are thousands of people with the same problem, its not the rom(JB)... but the proximity sensor that crashes the kernel, during calls, make the phone freeze/reboot.Search in google groups issue 37485, there are no solution, google and samsumg, dont say a word...It happens in nexus s too.
Click to expand...
Click to collapse
What shall one do then? I have such behaviour as well i think where phone has difficulties to come back from deep sleep.
I had this problem too
Random crashes which got worse, my phone would crash every 15 minutes.
I took the battery out and put it back and it didn't want to boot anymore.
Had to send it back to Samsung -> broken motherboard which got replaced
firestruck said:
Hi, there are thousands of people with the same problem, its not the rom(JB)... but the proximity sensor that crashes the kernel, during calls, make the phone freeze/reboot.Search in google groups issue 37485, there are no solution, google and samsumg, dont say a word...It happens in nexus s too.
Click to expand...
Click to collapse
OMG what the hell????? how come i never heard it before???
can't believe this is happening...how can they put the phone on the market without thoroughly testing it???
frandel said:
I had this problem too
Random crashes which got worse, my phone would crash every 15 minutes.
I took the battery out and put it back and it didn't want to boot anymore.
Had to send it back to Samsung -> broken motherboard which got replaced
Click to expand...
Click to collapse
is your phone new? or have been used for awhile??
firestruck said:
Hi, there are thousands of people with the same problem, its not the rom(JB)... but the proximity sensor that crashes the kernel, during calls, make the phone freeze/reboot.Search in google groups issue 37485, there are no solution, google and samsumg, dont say a word...It happens in nexus s too.
Click to expand...
Click to collapse
found a post discussing this issue on other forum:
http://code.google.com/p/android/issues/detail?id=38595
he temporarily solved the problem with using headphone when calling.
cuz the sensor is disabled when headset is plugged in
here are five conditions that proximity sensor disable during a phone call.
These conditions is default settings of Phone application in android.
You can find the source code in PhoneApp.java,
boolean screenOnImmediately = (isHeadsetPlugged()
|| PhoneUtils.isSpeakerOn(this)
|| ((mBtHandsfree != null) && mBtHandsfree.isAudioOn())
|| mIsHardKeyboardOpen
|| mOrientation == AccelerometerListener.ORIENTATION_HORIZONTAL);
(1) isHeadsetPlugged(): When user headset is plugged, proximity sensor will be disable
(2) isSpeakerOn: When user turn on the speaker, proximity sensor will be disable
(3) BT device is connected and audio path is On
(4) Hardware Keyboard is opened.
(5) DUT is at Horizional state.
Click to expand...
Click to collapse
Please read forum rules before posting
Questions go in Q&A
Thread moved
Friendly Neighborhood Moderator
Google, has just moderated me, for complain about have a useless Phone, see?? They dont have a solution, and they dont want to pay for people who spent 400$, in a useless phone...So they shut up us...Really sad became google policy...
---------- Post added at 02:22 PM ---------- Previous post was at 02:17 PM ----------
Yep, with phones it works, but its a pain in the ass have all the time the headphones conected, even in your pocket...
secretiff said:
is your phone new? or have been used for awhile??
Click to expand...
Click to collapse
I have it since it came out in December last year
frandel said:
I had this problem too
Random crashes which got worse, my phone would crash every 15 minutes.
I took the battery out and put it back and it didn't want to boot anymore.
Had to send it back to Samsung -> broken motherboard which got replaced
Click to expand...
Click to collapse
I have such problem with my Nexus S, I heard it was something wrong with bootloader for JB that Google released, which have caused countless Nexus S to be bricked.
I have tried everything even some hardware level modification provided by XDA member to save it but with no success so only solution is motherboard replacement...
Hope same thing won't happen to Galaxy Nexus... because if it does, I will try to buy 4th generations of Nexus series and I will be killed by someone because it would be very expensive and I just brought GNex 2 months ago...
Sent from my Galaxy Nexus using xda premium
frandel said:
I have it since it came out in December last year
Click to expand...
Click to collapse
so...it crashes randomly while it was new :cyclops: ?
Hey guys so i know there are plenty of threads going over this issue and even a official t mobile page explaining how to fix the issue but I'm all out of options. So i was running the stock rooted rom and saw a beats installer app in the market and decided to check it out. I proceeded with the process but when i got to the end and the app said the phone will now reboot the phone froze. I waited but after awhile decided to reboot the phone. I rebooted and the phone stayed stuck on the Samsung screen. I then proceeded to flash the stock rom i found online ( i think it was adroid police ) and rebooted. I noticed the phone didnt wipe though. I didnt have to log into google or anything. When i got back home, everything and its mom started to fail. Pop up screens so bad that i had to pull the battery and went back into odin and decided to oding the stock rooted rom. Got back to the home screen ( my phone didnt wipe after odin either ) and everything was failing still. I decided i better factory reset. That helped alot. After all day of getting my phone back together and loosing game data, i went to play virtual city and that wouldnt load. I gave up and uninstalled. I then went to join my contacts and after deleting contacts my phone pops the same error. What now? Hoping someone knows something i dont. Thanks guys.
If anyone cares, I did another factory reset but from the settings menu instead of recovery and the phone seems to be running great so far. Keeping my fingers crossed
Sent from my SGH-T999 using Tapatalk 2
knarfies said:
If anyone cares, I did another factory reset but from the settings menu instead of recovery and the phone seems to be running great so far. Keeping my fingers crossed
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Ran into that problem recently. Fixed by clearing data on contact and contact storage in app manager.
Happens sometimes when ever a new ROM is flashed.
I'm also getting the same error. I started getting it after trying to root with the odin procedure with no flash counter increase. when i flash the stock image back it works normally, but i want root!
dellenrules said:
Ran into that problem recently. Fixed by clearing data on contact and contact storage in app manager.
Happens sometimes when ever a new ROM is flashed.
Click to expand...
Click to collapse
Googled your post, worked for me on the Tab 10.1 after flashing a CM10 update without clearing user data. Thanks!
dellenrules said:
Ran into that problem recently. Fixed by clearing data on contact and contact storage in app manager.
Happens sometimes when ever a new ROM is flashed.
Click to expand...
Click to collapse
This also worked for me! just curious how did you know to clear contact and contact storage ?
Thanks again now to import my contacts back...
dellenrules said:
Ran into that problem recently. Fixed by clearing data on contact and contact storage in app manager.
Happens sometimes when ever a new ROM is flashed.
Click to expand...
Click to collapse
Thanks, you saved my bacon! I thought I would have to delete all my user data, but I did this after a flash and it worked perfectly. Appreciate your post!
dellenrules said:
Ran into that problem recently. Fixed by clearing data on contact and contact storage in app manager.
Happens sometimes when ever a new ROM is flashed.
Click to expand...
Click to collapse
Had the same problem, and your advice worked like a charm.
Thanks a lot.
No problem. Glad it helped.
[/COLOR]
knarfies said:
If anyone cares, I did another factory reset but from the settings menu instead of recovery and the phone seems to be running great so far. Keeping my fingers crossed
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Love you <3
Just wanted to say thanks for the post. Helped me as well when I flashed the new AOKP rom on my VZ Galaxy Nexus. :good:
Android bug
The problem occurs due to a bug in android , when you have saved a contact's birthday as 29 Feb, which occurs only in leap years. temporary solution is to change the birth date to any other date until google releases a fix .
I get the error with google failing more than I'd like to count...
knarfies said:
If anyone cares, I did another factory reset but from the settings menu instead of recovery and the phone seems to be running great so far. Keeping my fingers crossed
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for this! Solved the error message on my S2
dellenrules said:
Ran into that problem recently. Fixed by clearing data on contact and contact storage in app manager.
Happens sometimes when ever a new ROM is flashed.
Click to expand...
Click to collapse
Dear sir, you just made my day! i was so freaked out
THANK YOU!
Hi
I have this problem "unfortunately the process android.process.acore has stopped".When ever I 'Power ON or Restart' my SKyrocket(I727)..This issue started after flashing the new JB ROM--][UCLL3] SUPERLITE SAMSUNG JB 4.1.2 > (http://forum.xda-developers.com/showthread.php?t=2066468)
I have already tried with "clearing data on contact and contact storage in app manager"..Any other tips?
BR
My device was earlier running on SUPERLITE CM10 JB4.1.2 RoM | V8.0 (http://forum.xda-developers.com/showthread.php?t=1862244)
Same Issue
knarfies said:
If anyone cares, I did another factory reset but from the settings menu instead of recovery and the phone seems to be running great so far. Keeping my fingers crossed
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I had that issue. Took me a while to figure out that I had forgotten to clear all my caches when I flashed the new 4.2.1 AOKP ROM. Cleared the caches and the problem was resolved.
-ss
dellenrules said:
Ran into that problem recently. Fixed by clearing data on contact and contact storage in app manager.
Happens sometimes when ever a new ROM is flashed.
Click to expand...
Click to collapse
I also did this stuff..but,this 'data' on 'contact/contact storage' never gets cleaned...as soon as clearing,I go back and check again,it contains the 'data' agin..What do i 'miss'?
dellenrules said:
Ran into that problem recently. Fixed by clearing data on contact and contact storage in app manager.
Happens sometimes when ever a new ROM is flashed.
Click to expand...
Click to collapse
Worked for me too! thanks!
Last month, my gnex suddenly rebooted itself when texting, then it just stuck in bootloop forever.
I got it work again only after several times of factory reset and even pushing factory image.
I was using xenon + franco at that time.
However, 3 days ago it rebooted itself again when playing a music app, then the bootloop problem happened again. Somehow it could boot, but within a minute, it reboots and bootloops again.
i was using xylon + ak kernel this time.
I started to think if this is due to hardware problem.. and i took it to store yesterday after pushing the factory image to it. they said this is due to some incompatibility of some apps... (i dun understand why factory image could have this issue...) and did a recovery for me. My phone is reset back to 4.0.4 and it seemed working fine..
Then i pushed back the 4.2.1 factory image to it and still nothing happened. i started flashing back xylon and ak kernel to see if it works. It did run perfect for the whole night until this morning. When i was installing some ordinary apps, eg. air, skout, it rebooted itself again...
Flashing factory image of 4.2.1, 4.1.2, and even 4.0.4 all do not work.
it got past the google screen, and then to the bootanimation for a few seconds and it freezes and color seems weird, and then reboot again.
i have tried flashing through the toolkit and also through fastboot command..
does anyone know what is the problem causing this...
thanks in advance.
Anyone help please..
thyau said:
Anyone help please..
Click to expand...
Click to collapse
ok lets see if my craziness can help lol
ok this will seem crazy but it is a last resort which i did the other day .
if you have nothing to lose do this its a 50-50 shot
but first
what recovery and what toolkit do you have before i tell you this
I'm using cwm touch 6.0.2.3 and gnex toolkit v10
What's the method I'm driven crazy by this phone.. So this may be useful for me... :angel:
thyau said:
I'm using cwm touch 6.0.2.3 and gnex toolkit v10
What's the method I'm driven crazy by this phone.. So this may be useful for me... :angel:
Click to expand...
Click to collapse
ok i have twrp and this tool kit
http://www.wugfresh.com/nrt/
but idk if the v10 is the same way
but i wiped the system and took the whole os off the phone than restored the factory image
idk if that option is in your recovery tho
or download the toolkit i linked go to fastboot flash the stock image in that toolkit root it (it will install the recovery i use also)
and restore you apps if it happens again wipe the system and do as i said.
i highly trust the toolkit i use it saved my ass alot. i couldnt get the v10 toolkit to work for me at all
Alpha_wolf said:
ok i have twrp and this tool kit
http://www.wugfresh.com/nrt/
but idk if the v10 is the same way
but i wiped the system and took the whole os off the phone than restored the factory image
idk if that option is in your recovery tho
or download the toolkit i linked go to fastboot flash the stock image in that toolkit root it (it will install the recovery i use also)
and restore you apps if it happens again wipe the system and do as i said.
i highly trust the toolkit i use it saved my ass alot. i couldnt get the v10 toolkit to work for me at all
Click to expand...
Click to collapse
If this is the case... I have been crazy already.. lol as I've tried wiping all the things including the system partition..
But I haven't tried using your combination, so Ill give it a try :good:
Thanks bro
thyau said:
If this is the case... I have been crazy already.. lol as I've tried wiping all the things including the system partition..
But I haven't tried using your combination, so Ill give it a try :good:
Thanks bro
Click to expand...
Click to collapse
nothing to lose right? might as well try anything lol
sounds like your device might have a problem with its internal storage
Alpha_wolf said:
nothing to lose right? might as well try anything lol
Click to expand...
Click to collapse
All user data has been lost due to the crash already, really nth to lose.. lol
simms22 said:
sounds like your device might have a problem with its internal storage
Click to expand...
Click to collapse
You mean physically right??
thyau said:
All user data has been lost due to the crash already, really nth to lose.. lol
You mean physically right??
Click to expand...
Click to collapse
yea, physically. when/if it finally goes, you wont be able to recover from the bootloop.
simms22 said:
yea, physically. when it finally goes, you wont be able to recover from the bootloop.
Click to expand...
Click to collapse
I think I'm going to store tmr again..
But how to stress that this may be due to hardware problem? Since if I just describe the issue, I'm afraid they may think that this is software incompatibility again..
thyau said:
I think I'm going to store tmr again..
But how to stress that this may be due to hardware problem? Since if I just describe the issue, I'm afraid they may think that this is software incompatibility again..
Click to expand...
Click to collapse
well, it is a common issue with the nexus devices without a sd slot(nexus s and the galaxy nexus).
after a clean flash of Maguro Overdrive milestone 1, the phone is running again...
restored some of the apps.
let's see how long can the phone stand before another round of bootloop...
thyau said:
after a clean flash of Maguro Overdrive milestone 1, the phone is running again...
restored some of the apps.
let's see how long can the phone stand before another round of bootloop...
Click to expand...
Click to collapse
Op the same thing is happening to me, i also was on xylon and it was running fine and it just started bootlooping. i tried everything toolkit, flashing factory image lie you did and nothing, the only one that works now is ics stock 4.0.4 .if i try any other rom stock or custom the bootloops starts again and it wont boot, it only boots on 4.0.4 .so pretty much the same thing happened to me .
I actually this time have no idea what happened to this phone, but after reinstalling the OS the phone's camera began to work... Up until a day later it stopped working again. So i moved on from CM10.1 to Blackout ICS, which went well I suppose, up until two days later it died again, it just goes to a black screen when launching the camera app, if i have music playing that will stop, and the phone will be unable to play music for a minute or so, im touching on reformatting the SD Card, but before i do that i want to know if theres any ways to get the camera going again, and if theres any hardware faults (which is unlikely because when it works it works perfectly)
humzaahmed155 said:
I actually this time have no idea what happened to this phone, but after reinstalling the OS the phone's camera began to work... Up until a day later it stopped working again. So i moved on from CM10.1 to Blackout ICS, which went well I suppose, up until two days later it died again, it just goes to a black screen when launching the camera app, if i have music playing that will stop, and the phone will be unable to play music for a minute or so, im touching on reformatting the SD Card, but before i do that i want to know if theres any ways to get the camera going again, and if theres any hardware faults (which is unlikely because when it works it works perfectly)
Click to expand...
Click to collapse
Have you tried wiping the cache and dalvic in recovery?
tonylee000 said:
Have you tried wiping the cache and dalvic in recovery?
Click to expand...
Click to collapse
Yes, it still freezes at a black screen, because of the mods applied to my Rom, reinstalling the os is a bit of pain because I have to apply them again
Sent from my Desire HD using Tapatalk 2
humzaahmed155 said:
Yes, it still freezes at a black screen, because of the mods applied to my Rom, reinstalling the os is a bit of pain because I have to apply them again
Sent from my Desire HD using Tapatalk 2
Click to expand...
Click to collapse
Well it seems then that one of your mods is to blame.
have you attempted to install your Rom without your mods?
OMGMatrix said:
Well it seems then that one of your mods is to blame.
have you attempted to install your Rom without your mods?
Click to expand...
Click to collapse
Yup, after the.camera stopped.working again I decided to install.them again, it made no difference to be honest
Sent from my Desire HD using Tapatalk 2
humzaahmed155 said:
Yup, after the.camera stopped.working again I decided to install.them again, it made no difference to be honest
Sent from my Desire HD using Tapatalk 2
Click to expand...
Click to collapse
I think you misunderatood the question, if one of your mods are causing the problems, do you know which one? If yes then why do you install it? If no then reinstall the rom with no mods at allfor a few days then add one of the mods and wait a few more days to see if everythings ok and keep doing that until you can identify which mod is causing the problem. Id do a nandroid before installing each mod. Once identified the mod thats the issue, restore the bavkup from just before it was installed and dont reapply the mod, either do without it or look for an alternative
tonylee000 said:
I think you misunderatood the question, if one of your mods are causing the problems, do you know which one? If yes then why do you install it? If no then reinstall the rom with no mods at allfor a few days then add one of the mods and wait a few more days to see if everythings ok and keep doing that until you can identify which mod is causing the problem. Id do a nandroid before installing each mod. Once identified the mod thats the issue, restore the bavkup from just before it was installed and dont reapply the mod, either do without it or look for an alternative
Click to expand...
Click to collapse
Yup, going.to try it now, I can uninstall all mods from the same AROMA Installer I got them from, I can wait for the new update which has similar mods included
Sent from my Desire HD using Tapatalk 2
Hello together,
I got a strange problem with my new HTC M9.
Everything was fine for the first 2 weeks, but then it startet to lag extremly.
There are mini freezes every few seconds. Sometimes i have to wait 2 seconds for the system to continue... It appears after a fresh restart and with all apps close.
I wanna ask here, before doing a reset and loosing all my settings.
Btw it is a stock unrooted phone (1.32.161.15).
I could not find a topic for this. Noone else experience lags like this?
Thank you!
Regards
Sebastian
yes it will remove everything on the internal storage but im not sure about the sd card. just do a back up while its still working.
I have the exact same problem !! have you found a solution to this or resetting the device is my only way out?
If u have resetted, has this occurred again?
Sent from my HTC One M9 using XDA Free mobile app
at004 said:
I have the exact same problem !! have you found a solution to this or resetting the device is my only way out?
If u have resetted, has this occurred again?
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
If you are rooted with TWRP try wiping cache and dalvik cache through advance wipe if it doesnt work flash a new rom