Hello! I have several issues with my Note 2 N7105 version:
- on original ROM the camera, dialer, speaker, microphone, network not working, also the device is random restarting. Also the touchscreen have huge delays in operating.
- on CM11 ROM the camera, dialer and network is working, but the speaker and microphone doesn't, and the restarts come only when the phone is entering in standby/sleep mode. Never restarts when is conected to PC or charger.
I tried serveral original ROM's installed with Odin, but it seems that only CM11 it's bring my phone to life even that the speaker or microphone doesn't work. Also the network works on CM11, I can send and receive messages.
Can be these issues related to a hardware problem or I didn't find yet the correct version of ROM for this device? Many thanks in advance!
Related
Hello there !
I have a Galaxy Nexus (GSM) running CM10 Nightly.
My problem is (almost) everytime i call/get a call my phone is crashing, then rebooting, also happens with skype, the strange part, it's not happening everytime, sometime i can get calls without any trouble at all.
Another strange thing, my phone is not crashing if a call/skype with any ear/headphones connected. (Samsung with mic or any other)
This was already happening with stock JB rom so it's not CM related.
Any way to fix this ?
Thanks !
Somebody HELP!!!!!!!!
I'm running Resurrection Remix LP v5.5.8 on my T-Mobile Galaxy S4 (SGH-M919). I love this ROM, but I'm having a persistent problem with Bluetooth crashing, within minutes of starting up. This a consistent problem, not even remotely intermittent - happens every single time I try to turn on Bluetooth - it shuts itself off, refuses to turn back on again, and on occasion, gives me the error message "Unfortunately Bluetooth share has stopped."
I have tried clearing the Bluetooth share app cache and data to restart - it will then turn back on, but soon turns back off.
The problem was bad enough that I took RR off my phone and tried some other ROMs, including basic CM12.1. I came back to RR because the other ROMs had more critical issues, but they did help me eliminate causes of my problem, in that I didn't have Bluetooth issues with them like I do with RR, and I was still running all the same apps, same devices I was trying to attach, etc.
I've also played with several of the settings in the Kernel Aduitor, including completely shutting off the task killer. No difference - problem persists.
I also tried some of the apps on Google Play that say they're supposed to cure problems like this. Fixed nothing.
Please help. Is there an alternative something that I can flash - Bluetooth driver, different kernel, something, that can fix this issue once and for all?
Got the same problem. Android V6 RR Remix. Any suggestions?
Seems to be a consistent MM ROM issue, currently. Some seem to work better than others on some phones.
Keeping bluetooth working on the S4 seems to be "dark arts". Cyanogenmod has historically had much problems with this too. Some nightlies are okay, then others cause BT to crash. Some don't work at all.
Anyone have any resolution to this issue? I'm having the exact same symptom, but I'm on a different phone.
Note II / T-889, Conch Republic. Might've been from a radio update I did a while back, trying different ones now.
denverjoe72 said:
Keeping bluetooth working on the S4 seems to be "dark arts". Cyanogenmod has historically had much problems with this too. Some nightlies are okay, then others cause BT to crash. Some don't work at all.
Click to expand...
Click to collapse
You might give this AOKP 6 MM ROM a try:
http://forum.xda-developers.com/showthread.php?t=3391994
Users are reporting that after a week of testing the Bluetooth seems to be working rather well.
Sent from my SGH-M919 using XDA-Developers mobile app
I have the D851 LG G3 phone that crashes on every media app that uses sound and it does this on every ROM I tried. This originally happened while running Lollipop. The phone automatically restarted while I was browsing the internet one day (I think) and when it turned back on, it no longer produced any sound through the speaker or the headphone output (no music, no alarms, no ringtones, etc). I later realized that the phone dialer would crash every time I'd try to dial a number. The phone would make a call but you could not hear or be heard on the other end, then the dialar would crash. Video players, music players, YouTube and similar apps would either not produce media or would crash all together. But the phone worked flawlessly in every other aspect. After trying many things, I did a factory reset thinking that it would definitely fix the issue but I was wrong. The phone kept doing the same thing. At that point I thought that the issue might be with a kernel or the radio or something outside the operating system so I rooted the phone and began trying different ROMs. At first I reverted back to Kit-Kat then I tried Cloudy then a few de-bloated custom Lollipops and I even tried flashing CM13 Marshmallow but non these got my phone working. I now essentially have a phone that can't call but can message, take pictures and run non-media apps and I'm desperate to fix it but I have no clue of what to do next. Does this sound familiar to anyone and what can I try next? Could this be a hardware issue?(although a hardware issue I think would seem to yield more severe glitches) Any help is very appreciated. Thanks!
I also have the same problem. Did you find any solutions?
Update to MM then flash exceed kernel 4v via TWRP...apparently there is random restart issue on stock d851 if ur not using tmobile sim...also try replacing battery
jinderation said:
Update to MM then flash exceed kernel 4v via TWRP...apparently there is random restart issue on stock d851 if ur not using tmobile sim...also try replacing battery
Click to expand...
Click to collapse
Thanks for your answer, I have updated to MM but I dont think that I can flash that kernel, my version of the LG G3 is the G3 beat D722p, I am currently uzing CM13, I also tried the Xosp, in both cases the problem doesn't disappear.
Im sorry but there hasnt been any development for ur model ur best bet is to try flashing firmware stock or custom otherthan that i really dont know
Hi, I have nexus 2013 with Android 6.0.1, since this update and issue came all along and I don't know why!
My WiFi, is intermittent, it disconnects and reconnects all the time
All my other sensors are not working anymore, like auto rotation and gyro
screen sometimes is not being responsive, unless I turn it off couple of times
is it a software issue or my unit is dud? it used to work perfectly for couple of years though.
Yup same here!
Ditto on the rotation working intermittently. Works for a minute after restarting then stops working until I reboot. My wifi is solid though.
I am having the exact same issues as OP, doesn't matter which rom/stock.
Ahmed Sarhan said:
Hi, I have nexus 2013 with Android 6.0.1, since this update and issue came all along and I don't know why!
My WiFi, is intermittent, it disconnects and reconnects all the time
All my other sensors are not working anymore, like auto rotation and gyro
screen sometimes is not being responsive, unless I turn it off couple of times
is it a software issue or my unit is dud? it used to work perfectly for couple of years though.
Click to expand...
Click to collapse
I'm in the same situation but I'm not using stock rom. I'm using a custom RR Nougat Rom for almost 2 years, everything was working nice until this happened. WIFI either stops entirely stops working or works intermittently, and auto rotate doesn't work. I downloaded a sensors app from play store to see if they were actually working or not, to my surprise it says no sensors detected. I panicked and did a hard reset, and then it stucks at bootloop (can't get past the four dots, may be the ROM can't find sensors). Flashed countless custom ROMS, stock rom (6.1, 5.0), but still no dice. But then when I was about to give up, I thought I would give the stock rom 4.3 a final try and magically, my nexus successfully boots up with all the sensors working perfectly. Then I re flashed the custom rom back to my device in which all the sensors are working fine (ORIENTATION, GYRO...).
So may be go back to STOCK ROM 4.3 and then see if the problem persists. I see a lot of 6.0 people are facing these issues.
Good luck!
I have been using Cypher OS with elemental x kernel, in my OnePlus 3.
Recently tried the AKT for battery life. Zhana Profile. And battery life was amazing.
But before few days (idk if this is related to the tweaks), my phone started hanging and reboots whenever I call someone. Then I noticed that the phone hangs and reboots whenever any app tries to use the mic (for example, Google Assistant, WhatsApp voice message, any other app)
I tried changing the ROM, to Paranoid Android. First few minutes, phone works fine along with the mic. And then, the problem starts again.
I tried flashing stock ROM with stock recovery. Again, for the first few minutes, everything goes fine and the problem starts again.
I searched on this, and guess no one has been facing this issue. Any help would be appreciated. Thanks in advance!
stazot said:
I have been using Cypher OS with elemental x kernel, in my OnePlus 3.
Recently tried the AKT for battery life. Zhana Profile. And battery life was amazing.
But before few days (idk if this is related to the tweaks), my phone started hanging and reboots whenever I call someone. Then I noticed that the phone hangs and reboots whenever any app tries to use the mic (for example, Google Assistant, WhatsApp voice message, any other app)
I tried changing the ROM, to Paranoid Android. First few minutes, phone works fine along with the mic. And then, the problem starts again.
I tried flashing stock ROM with stock recovery. Again, for the first few minutes, everything goes fine and the problem starts again.
I searched on this, and guess no one has been facing this issue. Any help would be appreciated. Thanks in advance!
Click to expand...
Click to collapse
Did you do a full clean install while switching roms en such. And perhaps proper firmware? These issues are not caused by AKT. Have you tried the unbrick tool? If that doesn't help then this really sounds like a hardware problem.