Hy.
I used the 4.2.1 with franco kernel and today i get this problem when i wan't to calling anyone. If i call, the screen going to black, and i just can't aborting the call. Only i can do, is remove the battery. So i pull back the 4.1.2 with stock kernel, but the problem is still alive.
Anybody know about this something ? It's a really frustrating problem.
SamS1989 said:
Hy.
I used the 4.2.1 with franco kernel and today i get this problem when i wan't to calling anyone. If i call, the screen going to black, and i just can't aborting the call. Only i can do, is remove the battery. So i pull back the 4.1.2 with stock kernel, but the problem is still alive.
Anybody know about this something ? It's a really frustrating problem.
Click to expand...
Click to collapse
A similar thing happened with me long time ago when I installed a nightly CyanogenMod on my S2 but it disappeared immediately after changing the ROM. It seems 4.2.1 and franco kernel were working fine with you at first but only today you got this problem, right?
I would make a nandroid backup, wipe all (system, factory reset, cache, and dalvik) then install the ROM again or better try another ROM to at least know if it is the hardware (proximity sensor?) or the software causing this problem. The nandroid backup will help you restore everything in case you get into any further trouble
Good Luck
Related
Hey all, I have only been flashing custom ROMs onto my G2 for about a month now, so this might be a dumb oversight. Ever since RC4, I have had an issue where every single time I reboot or power off the phone and power it back on, I get the HTC screen for a few seconds and then the CyanogenMod 7 splash screen with the arrow going round and round. And that's it. Even overnight. Now the ROM runs BEAUTIFULLY all the time. No GPS, Google Sych, or Battery Life Issues. Love it, so any help that would allow me to stick with this ROM would be great.
I am running CM 7.0.0
.26 Radio
the base CM7 kernel (2.6.32.28)
Overclocked to 1017Mhz
What should I do to get this issue to stop?
SpeedBlue47 said:
Hey all, I have only been flashing custom ROMs onto my G2 for about a month now, so this might be a dumb oversight. Ever since RC4, I have had an issue where every single time I reboot or power off the phone and power it back on, I get the HTC screen for a few seconds and then the CyanogenMod 7 splash screen with the arrow going round and round. And that's it. Even overnight. Now the ROM runs BEAUTIFULLY all the time. No GPS, Google Sych, or Battery Life Issues. Love it, so any help that would allow me to stick with this ROM would be great.
I am running CM 7.0.0
.26 Radio
the base CM7 kernel (2.6.32.28)
Overclocked to 1017Mhz
What should I do to get this issue to stop?
Click to expand...
Click to collapse
Have you tried a full wipe and then reflash? What rom did you come from? A few details about those things might make it easier for people to help u
dont send me pm's crying about how i hurt your feelings in a thread
I came from the stock post-ota ROM. I did a full wipe when I installed RC4, but I haven't since, just wipe data then re-flash. Should I wipe everything - data, cache, dalvik, etc and then re-flash? Of course Nandroid before...
just cache and dalvik was enough... no data wipe needed (at least.. I haven't needed that before)
But I still need to re-flash the ROM after I clear cache and Dalvik though, right?
Well, apparently, that worked out. Everything is humming along just fine. Thanks a lot for the help everyone.
Hi guys,
Anyone know what could be the reason? Phone just restarts when Im about to receive phone call.
Tried wiping data, cache, and then restoring nandroid but the same.
I don't know the solution but you can try a full wipe
Backup the sdcard also and format that too in recovery !
And in the aroma choose stock kernel, maybe this helps
Aosp lockscreen was the issue.
Thanks
Solved
Cool ! Not a biggie in the end
vioer x rebbot
stifler05 said:
Aosp lockscreen was the issue.
Thanks
Solved
Click to expand...
Click to collapse
Hi i have the same problem, when someone tries to call me it reboots, i would just know them to be calling me thru SMS that tey will be saying why im not picking up when the things is my phone is rebooting each time someone calls me..
tried going to stock kernel from narcotics and all. if its the locks screen is the issue i do hope to fix mine too..
Thanks!
Calls worked until I installed cm10.1 nightly. Now I can't be heard unless i turn on speaker phone. Sound is still crap but at least I can make a call.
I have tried a few nightly's and now I'm on the people's rom 3.14. (Loving tpr by the way). I doubt it is a hardware issue based on other reports and the fact it was fine until the custom roms.
I still use my phone as a phone from time to time and need it to work or I have to go back to stock.
Thanks
Could have been a bad flash / download
Did you check the md5sum?
leftcranium said:
Calls worked until I installed cm10.1 nightly. Now I can't be heard unless i turn on speaker phone. Sound is still crap but at least I can make a call.
I have tried a few nightly's and now I'm on the people's rom 3.14. (Loving tpr by the way). I doubt it is a hardware issue based on other reports and the fact it was fine until the custom roms.
I still use my phone as a phone from time to time and need it to work or I have to go back to stock.
Thanks
Click to expand...
Click to collapse
Let me make sure I'm understanding you correctly:
Your mic was working fine until you flashed the CM10.1 nightly. Afterwards, the other person could only hear you when you were on speakerphone.
You switched to TPR 3.14. This switch did not fix the mic problem.
You're thinking that switching back to stock (presumably unrooted) will fix this issue.
Please correct me if any of the above is incorrect.
If he issue isn't hardware-related, I'd bet it has to do with the kernel. Let me ask you the following:
Which CM10.1 nightly did you install? Did you see any other issues in the CM10.1 thread which might indicate problems with the nightly you flashed?
What kernel did you use while on CM10.1? I know that the newer kernels (3.4.y verses the old 3.0.y) have had issues and are just recently getting stable.
As CNexus asked,did you check the md5sum for the TPR Rom you flashed?
When you flashed TPR, did you do a full system wipe, or only a Factory Reset (data) wipe? I believe since you were coming from a 4.2.2 Rom (CM 10.1) to a 4.1.2 Rom (TPR), you should do a full system wipe. Some remnants of the CM10.1 kernel/system files could still be there, messing up the mic.
I would think re-flashing TPR (after checking the md5sum) with a full system wipe would fix your issue, but answering these questions would help us diagnose the problem better.
topherk said:
Let me make sure I'm understanding you correctly:
Your mic was working fine until you flashed the CM10.1 nightly. Afterwards, the other person could only hear you when you were on speakerphone.
You switched to TPR 3.14. This switch did not fix the mic problem.
You're thinking that switching back to stock (presumably unrooted) will fix this issue.
Please correct me if any of the above is incorrect.
If he issue isn't hardware-related, I'd bet it has to do with the kernel. Let me ask you the following:
Which CM10.1 nightly did you install? Did you see any other issues in the CM10.1 thread which might indicate problems with the nightly you flashed?
What kernel did you use while on CM10.1? I know that the newer kernels (3.4.y verses the old 3.0.y) have had issues and are just recently getting stable.
As CNexus asked,did you check the md5sum for the TPR Rom you flashed?
When you flashed TPR, did you do a full system wipe, or only a Factory Reset (data) wipe? I believe since you were coming from a 4.2.2 Rom (CM 10.1) to a 4.1.2 Rom (TPR), you should do a full system wipe. Some remnants of the CM10.1 kernel/system files could still be there, messing up the mic.
I would think re-flashing TPR (after checking the md5sum) with a full system wipe would fix your issue, but answering these questions would help us diagnose the problem better.
Click to expand...
Click to collapse
I think you have the symptoms correct.
I did a data wipe but not a factory reset before each rom install.
I started with this rom
cm-10.1-20130303-NIGHTLY-d2spr.zip
I tried 3/13, 3/24 and 3/27 before trying TPR3.14.
leftcranium said:
I think you have the symptoms correct.
I did a data wipe but not a factory reset before each rom install.
I started with this rom
cm-10.1-20130303-NIGHTLY-d2spr.zip
I tried 3/13, 3/24 and 3/27 before trying TPR3.14.
Click to expand...
Click to collapse
Yeah, a full system wipe might be the ticket. Let us know if that works.
I'm Back Baby
I tried a system wipe and a rooted stock rom. This didn't work. I then tried the LJ7_Stock_with_count_reset16 rom and my sound was ok. I cleaned out the mic hole with a pin and bam sound was like normal. I'm now back on TPRGS3.14 and everything is good. I think I had 2 issues but possibly only 1. messed up mic from multiple flashes and crap in the mic hole. I guess checking for a physical problem even as small as a mic debris is an easy first step.
thanks for the suggestions
Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?
JonnyZaggi said:
Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?
Click to expand...
Click to collapse
Since yesterday I am facing the same problems you are describing. At first I thought it was a bad flash or something like that. Clean installed various 4.3 costum roms and it's always the same.
Right now I will look deeper into it since the phone is unusable in that condition.
If I find a solution I will comment.
Best regards
Edit: Okay, works again flawlessly. I simply flashed an nightly from carbon-rom and the lags were gone. Hope it helps. What exactly caused the lag I don't know. For now I am staying on 4.2.2 Carbon as it is my favourite rom anyway and I will wait till there are stable 4.3 from carbon.
Are you sure it's the phone and not an app?
chrisinsocalif said:
Are you sure it's the phone and not an app?
Click to expand...
Click to collapse
Not pretty sure, but it still occured after countless factory resets, wipe cache, wipe dalvic cache and wipe system via TWRP.
Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4
chrisinsocalif said:
Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yes I did. I only flashed for example newest PA and their PA Gapps.
So far I resolved it by "downgrading" to a 4.2.2 nightly from carbon. The lags are completly gone. I will stay and wait till carbon has stable 4.3.
why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct
Zepius said:
why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct
Click to expand...
Click to collapse
Already did that.
I am having the same/similar problems with my GNex too. Specifically bullets [1-3] from the original post. I am running unmodified yakjuux and have tried with just my google account with no other apps and the same problem exists.
Mine makes a noticeable "click" sound with a vibration followed by a reboot.
It usually happens during calls and after it boots the phone call log shows no record of the incoming/outgoing call that just happened. Its like a blue screen of death for android!
I have sent the phone back to Samsung's warranty service 4 separate times and each time they reported no trouble found in the completion report. They just factory reset or put an older version of jelly bean back on the phone and send it back to me with some notes of PRL updates and other nonsense to make it seem like they did something to fix it.
Does anyone have any suggestions (logs, adb, etc) how I can help prove to Samsung/service absolute that the phone is a lemon (other than trying to video tape the phone hoping it reboots - because that is the last resort)?
I already escalated to executive customer service and they refused an exchange because the completion reports show no trouble found :crying:
Thx!
well... I also have this problem.
First happened when I flash Cm10.2 nightly (don't remember which one).
Then I flash PA, or whatever... Looks like the random reboot relating to notifications? It's usually happened when whatsapp notification coming in, but not always.
But a few weeks ago I flashed stock ROM rooted (via TWRP, not fastboot).
The problems solved. No random reboots anymore. Then today I tried latest CM10.2, and it happened again... Wonder why... Looks like it's a very rare problems.
Interesting to see someone having the same problem...
Now I want to flash stock ROM via fastboot to check if it'll fix.
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?
lonestrider said:
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?
Click to expand...
Click to collapse
I believe CM offers an upgrade option somewhere in the system settings. Unless you want to wipe your phone and flash directly to 10.2 in which case I do not think you need to flash stock 4.3 first. Maybe just do a reset within 10.1 before you flash CM10.2 via whatever recovery (clockwork etc) you are using but even that may be unnecessary.
My 1 year warranty expires this month so if I can't manage to get something out of Samsung I am going to play around with flashing stock 4.3 as you suggested. I have tried converting yakjuux to yakju in the past but still saw the problem then which made me revert back to yakjuux so I could send the phone back for service).
I have been looking for a solution to this problem for weeks and have found nothing that will fix it.
I am currently on CM11-M3, and have had the problem since 10.2. No matter what ringtone I select it will not play during an incoming call.
I have been testing with wheresmycellphone.com. Ehen a call comes in the phone will vibrate once and very rarely the ringtone will play for a fraction of a second, but most of the time there is no sound. I have noticed that the mute icon (speaker with a line through it) flashes in the notification area briefly the second the phone starts ringing.
Does it be behave the same way on other custom and stock ROMs?
Are you clean flashing?
audit13 said:
Does it be behave the same way on other custom and stock ROMs?
Are you clean flashing?
Click to expand...
Click to collapse
I dirty flashed 10.2 from 10.1, I did a clean install when I switched to CM11, every flash since has been with a cache/dalvik wipe. I have not yet tried a rom beyond CM.
You should try another ROM, even if it is based on CM11 to see what happens.
audit13 said:
You should try another ROM, even if it is based on CM11 to see what happens.
Click to expand...
Click to collapse
I will when I get a moment. I need to be accessible for work right now so I can't risk any excessive off time just yet.
zero|fade said:
I will when I get a moment. I need to be accessible for work right now so I can't risk any excessive off time just yet.
Click to expand...
Click to collapse
Well, I finally got off my ass to try fixing this again. I was going to try installing SlimKat, and as prep I wiped cache, dalvik and then factory reset. I rebooted to try receiving a call before I started work on flashing the rom and the phone now rings fine. I have no idea what changed, I had tried a factory reset on M2 and it didn't fix the issue. This is the first factory reset I applied to M3 though.