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: ?
Related
Having upgraded to 4.2.x now for about a month I have nothing but fustrations about the upgrade. I've had probably 5-6 random reboots where as on 4.1.x I had none. The phone has had problems connecting to data where the only remedy was to reboot. I've also had problems connecting with GPS AND bluetooth where only a reboot would fix things. The OS studders much more than before and (it could be my imagination) it seems some apps run slower than before. With that said if I have to reboot one more time this week I will be downgrading.
BTW I'm stock with bootloader unlocked on yakju.
Like everyone else you should try a fresh install of the factory image wiping everything without restoring any data. It shouldn't matter if you are going to downgrade anyway.
We are many who have had no issues at all, so give it a shot.
Lots of threads already on these issues.
Just downgrade now and save us having to listen to more whining...
If you updated from 4.1 to 4.2 without a full wipe there's potential for a lot to go wrong. There could be some app running as a service that isn't fully compatible with 4.2 causing your issues.
With that being said, I would try fully resetting the device, no need to re-flash the stock image because it's already in place on the device anyway.
Install apps that are known to work on 4.2 ONLY. Then, you can begin testing to see if it becomes stable. After that, do what you want.
mortenmhp said:
Like everyone else you should try a fresh install of the factory image wiping everything without restoring any data. It shouldn't matter if you are going to downgrade anyway.
We are many who have had no issues at all, so give it a shot.
Click to expand...
Click to collapse
Thanks, I'll give a try!
cymru said:
Lots of threads already on these issues.
Just downgrade now and save us having to listen to more whining...
Click to expand...
Click to collapse
Not all of us have the time to look through all the threads to make sure threads aren't duplicate buddy.
g8who said:
Not all of us have the time to look through all the threads to make sure threads aren't duplicate buddy.
Click to expand...
Click to collapse
Yeah, it's as if someone should add a search button to the forum :silly:
cymru said:
Yeah, it's as if someone should add a search button to the forum :silly:
Click to expand...
Click to collapse
But searching takes time...
And it's not like you can make it through a page in either General or Q&A without tripping over a 4.2 whine thread.
g8who said:
Having upgraded to 4.2.x now for about a month I have nothing but fustrations about the upgrade. I've had probably 5-6 random reboots where as on 4.1.x I had none. The phone has had problems connecting to data where the only remedy was to reboot. I've also had problems connecting with GPS AND bluetooth where only a reboot would fix things. The OS studders much more than before and (it could be my imagination) it seems some apps run slower than before. With that said if I have to reboot one more time this week I will be downgrading.
BTW I'm stock with bootloader unlocked on yakju.
Click to expand...
Click to collapse
if you're on the VZW Galaxy Nexus, then i strongly recommend getting the mmuzzy rom. i think it's made specifically for that carrier/model only. it's been great for me so far. so smooth, no issues thus far!
i don't know how much experience you have with swapping roms, but you should use the Super Wipe utility that mmuzzy recommends.
jpildave said:
if you're on the VZW Galaxy Nexus, then i strongly recommend getting the mmuzzy rom. i think it's made specifically for that carrier/model only. it's been great for me so far. so smooth, no issues thus far!
i don't know how much experience you have with swapping roms, but you should use the Super Wipe utility that mmuzzy recommends.
Click to expand...
Click to collapse
This guy is correct MMuzzy has been the most stable for Vzn Gnex. I only have a qualm with the GPS, but that's every phone
Sent from my Galaxy Nexus using xda premium
Most of people that have problemas... solve with a clean install... i dont know why dont try before back to 4.1
Only bluetooth problem
LeBaldi said:
Most of people that have problemas... solve with a clean install... i dont know why dont try before back to 4.1
Click to expand...
Click to collapse
Hi.
I only have problems in bluetooth in 4.2.1... Sometimes I turned it off and I cannot turn it on again Also... sometimes when the phone goes into sleep mode it disconnect the connection with handset... It never happen in 4.1.
I downloaded the factory image of 4.2.1 from Google and flash it... still the same. I saw people saying a clean install... Should I do another kind of install other than I did?
Can someone please tell me if got this kind of bluetooth problem and have solved it? How?
Thanks
abcorp said:
Hi.
I only have problems in bluetooth in 4.2.1... Sometimes I turned it off and I cannot turn it on again
Click to expand...
Click to collapse
i have also encountered that behaviour, gets greyed out while "Turning off".
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 .
So I was working on putting on a new ROM and when I went to install the PA G Apps zip it said in my recovery that I didn't have enough space in the system storage. Which was a little confusing since I had just wiped it like usual through the recovery before I do a ROM. However I was navigating the recovery since it had been a while and just check out some of the things I didn't notice that changed. Went to the Mounts and Storage area, then I guess I touched "Format /system" and when I realized that it moved to asking me if I wanted to format /system I tried to push NO but apparently I have fat fingers and still pushed yes...So now after having rebooted the phone it is stuck at the screen "Google *small unlocked Lock at the bottom*". And now I'm not sure what to do.
Any advice?
Well this is nothing serious. Just reflash your ROM or flash the new one you werd gonna flash..
P.s. formatting system is a good idea anyway before flashing a new ROM..
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Well this is nothing serious. Just reflash your ROM or flash the new one you werd gonna flash..
P.s. formatting system is a good idea anyway before flashing a new ROM..
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Well the issue is it is stuck...I let it sit for at least 5min or so and it just sat there at that same spot. Is that because I need to reflash it? I have the Galaxy Nexus Toolkit, but I haven't used it as of late since I haven't needed it. If you don't mind going into detail I would appreciate it .
Should also mention if I go into the bootloader, it hangs at "Downloading..." so effectively I can't do anything to reflash my ROM or anything. And I probably should be clear that this all happened AFTER I flashed the new ROM and then remembered I needed the PA G Apps. Should have refreshed my memory with doing this sort of thing since I'm not as experienced as I use to be long ways back.
Ysosrslawl said:
Should also mention if I go into the bootloader, it hangs at "Downloading..."
Click to expand...
Click to collapse
Did you actually use the right combination to go to bootloader? Because from what I understand, you simply wiped your /system clean, which is a simple matter to fix - just flash any ROM or restore any valid backup to make it work again.
Sent from Google Nexus 4 @ CM11
AndyYan said:
Did you actually use the right combination to go to bootloader? Because from what I understand, you simply wiped your /system clean, which is a simple matter to fix - just flash any ROM or restore any valid backup to make it work again.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
Volume button then Power button until it vibrates then keep holding down the volume button? Only way I know how to do it, seeing as I've never heard of another way to do it.
Ysosrslawl said:
Volume button then Power button until it vibrates then keep holding down the volume button? Only way I know how to do it, seeing as I've never heard of another way to do it.
Click to expand...
Click to collapse
Yeah, make sure you hold BOTH volume keys for bootloader. Hold only VOLUME- for Download mode as you've seen before. If you indeed held both keys but still got to Download mode, chances are you have a broken volume key.
Sent from Google Nexus 4 @ CM11
Yep I'm dumb apparently and misjudged how the buttons were being pressed down...now on to step 2! Hmmm....
Seems like the zip for the ROM isnt in the storage anymore. How do I copy it back on from just being in fastboot mode or recovery? I'm not familiar with ADB at all. I may have figured out the problem so hold on...I think I derped and forgot that I removed the device drivers off my desktop because I wanted to fresh install them way back.
Edit2: Doing this the hard way.
OK SO I feel like a total noob, which I really am. I've never used ADB, never tried pushing files, or anything of the sort. I tried for a very long time to get the Galaxy Nexus toolkit to help me out but it REALLY didn't do ANYTHING for me. None of the options worked like I had hoped, the ONLY thing it did for me was to install the missing drivers I needed. Other than that it was utterly useless. You guys may find this funny, but I really had no idea on how to fix this even in the slightest. Even with the responses put here by some of the community.
However, with a little searching I was able to find the answers to my questions, not found here on XDA unfortunately. What I ended up doing was updating my SDK tools and learning how to open up ADB (had no idea why the adb.exe wasn't just opening for me like I assumed it would). From there I used the sideload option in my recovery to help me get my ROM flashed back on my phone. So now all is well and I can go back to being a noob who just likes to find good looking ROMS and play with them every couple months.
Thanks, my issue is now resolved.
Yesterday I answered a phone call while playing the Family Guy Game (The Quest For Stuff) and using my 3G. As usual, the game had stopped when the phone call rang but the music from the game kept playing in the backgound while I was talking with the other person. The phone was very slow during this whole process (starting a little bit before the first phone call).
After hanging up the phone, I tried many times to call the other person to no avail. Tried to call other people and even emergency numbers. VoIP still works, headphones/speakers also works and the other person can listen to me when I call. Seems to me to be a software problem rather than hardware.
Here is what I have tried so far:
- Rollback to previous CM version;
- Wipe data/Clear Cache/Reinstall phone dialer;
- Uninstall the game+data, uninstall the dialer and reinstall it;
- Boot phone into safe mode.
I am using 11-20140607-NIGHTLY-n7100 on Samsung Galaxy Note II N7100.
I am running out of options here and I would really appreciate some help.
Togatheone said:
Yesterday I answered a phone call while playing the Family Guy Game (The Quest For Stuff) and using my 3G. As usual, the game had stopped when the phone call rang but the music from the game kept playing in the backgound while I was talking with the other person. The phone was very slow during this whole process (starting a little bit before the first phone call).
After hanging up the phone, I tried many times to call the other person to no avail. Tried to call other people and even emergency numbers. VoIP still works, headphones/speakers also works and the other person can listen to me when I call. Seems to me to be a software problem rather than hardware.
Here is what I have tried so far:
- Rollback to previous CM version;
- Wipe data/Clear Cache/Reinstall phone dialer;
- Uninstall the game+data, uninstall the dialer and reinstall it;
- Boot phone into safe mode.
I am using 11-20140607-NIGHTLY-n7100 on Samsung Galaxy Note II N7100.
I am running out of options here and I would really appreciate some help.
Click to expand...
Click to collapse
Might be missing drivers.
There's an app on Play Sore', named 'Volume Booster+', give a try with that.
m.b.jikre said:
Might be missing drivers.
There's an app on Play Sore', named 'Volume Booster+', give a try with that.
Click to expand...
Click to collapse
I'll give it a try then. But how could a driver be missing in my case?
Togatheone said:
I'll give it a try then. But how could a driver be missing in my case?
Click to expand...
Click to collapse
I said 'Might be!'.
Because I had also got this problem.
have you muted all sounds? unmute your phone and up the volume and then reboot your phone.
m.b.jikre said:
I said 'Might be!'.
Because I had also got this problem.
Click to expand...
Click to collapse
I see. Even installing the app it didn't work. I had to resort for a factory reset + complete wipe of the phone =/ But thanks for the help!
weebeast said:
have you muted all sounds? unmute your phone and up the volume and then reboot your phone.
Click to expand...
Click to collapse
Tried that to. No luck though.
Togatheone said:
I see. Even installing the app it didn't work. I had to resort for a factory reset + complete wipe of the phone =/ But thanks for the help!
Click to expand...
Click to collapse
With this one https://play.google.com/store/apps/details?id=wait.what.volumebooster ,or anything else?
If yes then its your hardware problem.
Are you saying a factory reset didn't work, nor a clean install of cm?
If so, return to a stock rom (match your bootloader to decide which stock rom - at least 4.1.2 and no higher if you aren't knoxed yet). Twice on two phones I've have issues with cm where a stock rom flash and then return to cm was the only solution I could find.
EmptyArea said:
Are you saying a factory reset didn't work, nor a clean install of cm?
If so, return to a stock rom (match your bootloader to decide which stock rom - at least 4.1.2 and no higher if you aren't knoxed yet). Twice on two phones I've have issues with cm where a stock rom flash and then return to cm was the only solution I could find.
Click to expand...
Click to collapse
I did the factory reset and it worked. And today (again) the same bug happened right after launching the Family Guy game. I am trying other solutions before doing a factory reset again.
m.b.jikre said:
With this one https://play.google.com/store/apps/details?id=wait.what.volumebooster ,or anything else?
If yes then its your hardware problem.
Click to expand...
Click to collapse
Tried the app and yet again, it didn't work. And it is not hardware, since the speaker still works.
Guys I don't know if there's something wrong with my phone or not. Whichever rom or kernel I try, there is an abnormal shut down of my device. Like I'm using it and I leave it for a few minutes or so and it shuts down. I'm not sure if it had something to do with deep sleep or anything, but I need help. Please guys anyone
on custom kernel, random reboots may happend when
1. trying disconnecting whatsapp call
2. trying disconnecting gsm call
can you plug in audio jack to earphone and notice the device? (a strange excersize but worth trying)
YasuHamed said:
on custom kernel, random reboots may happend when
1. trying disconnecting whatsapp call
2. trying disconnecting gsm call
can you plug in audio jack to earphone and notice the device? (a strange excersize but worth trying)
Click to expand...
Click to collapse
Yes, When audio jack is plugged in I did notice a reboot, however, noticed a reboot without it being plugged as well.
Nothing with calls.
I just let my phone sit for a while and it shuts down. I have to power it up again. When I'm using it continuously it doesn't do that. That is why I'm skeptical if it is related to deep sleep somehow.
promiscuss said:
Yes, When audio jack is plugged in I did notice a reboot, however, noticed a reboot without it being plugged as well.
Nothing with calls.
I just let my phone sit for a while and it shuts down. I have to power it up again. When I'm using it continuously it doesn't do that. That is why I'm skeptical if it is related to deep sleep somehow.
Click to expand...
Click to collapse
lets step back for a moment
if you are on MIUI10, or Miui 9.6.x
do you experience the same with your phone? if yes then you should take it up to the dealer and have it replaced. if such doesnt happen on MIUI then its some APP conflicting with your rom or kernel. try to list / think all such apps which may have given root access indefinately.
whatsapp on custom rom makes device act funny ( I experienced it many time) so does few repost apps (instagram)
YasuHamed said:
lets step back for a moment
if you are on MIUI10, or Miui 9.6.x
do you experience the same with your phone? if yes then you should take it up to the dealer and have it replaced. if such doesnt happen on MIUI then its some APP conflicting with your rom or kernel. try to list / think all such apps which may have given root access indefinately.
whatsapp on custom rom makes device act funny ( I experienced it many time) so does few repost apps (instagram)
Click to expand...
Click to collapse
Actually I'm not using miui since I unlocked my BL and it had been months since I've been using custom non miui roms. This just started recently. I get what you're hinting at, but I don't think there's something wrong w the hardware but I can't be too sure.
Anyway, yes about the apps, it did occur to me that this might be the case. So I simple wiped my device internal(don't use sd card) and wiped all system, data and everything to install a new custom rom. After setting it up, I left it for a few moments and it shut down again (had not yet installed any of my personal apps, just the regular gapps
promiscuss said:
Actually I'm not using miui since I unlocked my BL and it had been months since I've been using custom non miui roms. This just started recently. I get what you're hinting at, but I don't think there's something wrong w the hardware but I can't be too sure.
Anyway, yes about the apps, it did occur to me that this might be the case. So I simple wiped my device internal(don't use sd card) and wiped all system, data and everything to install a new custom rom. After setting it up, I left it for a few moments and it shut down again (had not yet installed any of my personal apps, just the regular gapps
Click to expand...
Click to collapse
Has been an entire day since it happened again, I've turned on 'Always on display' to just keep a lil activity on device so that it does not shut off, maybe that did it. I'll try one entire day without always on display
promiscuss said:
Has been an entire day since it happened again, I've turned on 'Always on display' to just keep a lil activity on device so that it does not shut off, maybe that did it. I'll try one entire day without always on display
Click to expand...
Click to collapse
sir, which custom ROM + kernel + anrdoid version are you on ?
YasuHamed said:
sir, which custom ROM + kernel + anrdoid version are you on ?
Click to expand...
Click to collapse
Previously I was on AEX pie with derp and now on Havoc 2.0 modded with derp as well.
promiscuss said:
Previously I was on AEX pie with derp and now on Havoc 2.0 modded with derp as well.
Click to expand...
Click to collapse
Could you try
https://forum.xda-developers.com/redmi-note-5-pro/development/rom-aosip-8-1-t3804473
on
https://forum.xda-developers.com/redmi-note-5-pro/development/insigniux-kernel-t3835939 (kernel)
?
YasuHamed said:
Could you try
https://forum.xda-developers.com/redmi-note-5-pro/development/rom-aosip-8-1-t3804473
on
https://forum.xda-developers.com/redmi-note-5-pro/development/insigniux-kernel-t3835939 (kernel)
?
Click to expand...
Click to collapse
Thanks for all your effort, the problem seems to have resolved on its own. I'm not sure what it was.
now it's happening to me but it's much more severe. First it started slowly now it's so frequent that the phone might shut down even on boot. This is really frustrating.
I had the same problem with my redmi note 7, flashed stock rom with MI flash tool, fixed everything for me