phone.apk issues - Sprint Samsung Galaxy Note II

I have been having this issue only with aosp based ROMS, where i will dial a number or answer a phone call and once i put the phone to my ear the screen shuts off like it is supposed to. It has a lot of trouble turning the screen back on once i take my face away from the phone. Its kind of an issue because then to get back to using my phone i have to take the battery out, and if someone doesnt answer they get a voicemail of me struggling. Its happened on sbrissen's cm10 and cm10.1 roms as well as slick_ricks aosp based roms. Just to clarify this is not a complaint, just wondering if anyone else has experienced this issue and if it can be fixed somehow or if its not a device specific issue. Thanks in advance for anyones help, its greatly appreciated. Thank you as well to sbrissen and slick_rick for the great roms, i still use them daily even with this issue.

Related

[Q] Vibrate/Haptic Feedback Randomly Stops Working (Evo 4G)

I am having a problem where all vibration/haptic feedback will just randomly stop working completely. Then a few hours (and sometimes days) later it will randomly start working again. It will keep working again for a few hours or maybe days, and then randomly stop again. There seems to be no pattern to it.
I have no idea what is causing this. Has anyone else experienced this, or does anyone have any idea how to fix it?
This is extremely frustrating as I am someone who never uses the ringer; I just always have my phone on vibrate.
I'm running the latest stable release of CM 7.1 for the Evo 4G, but I had this happen before on stock Sense as well.
mredmond2012 said:
I am having a problem where all vibration/haptic feedback will just randomly stop working completely. Then a few hours (and sometimes days) later it will randomly start working again. It will keep working again for a few hours or maybe days, and then randomly stop again. There seems to be no pattern to it.
I have no idea what is causing this. Has anyone else experienced this, or does anyone have any idea how to fix it?
This is extremely frustrating as I am someone who never uses the ringer; I just always have my phone on vibrate.
I'm running the latest stable release of CM 7.1 for the Evo 4G, but I had this happen before on stock Sense as well.
Click to expand...
Click to collapse
I am having this same issue as well. It must be software related because the vibrate function works just fine when the phone rings. I am running CM 7.1 stable on an Evo 4G. I noticed the issue as well on CM 7.0.3.1 or whatever the latest stable build was on CM.
Does the phone ever always (or never) vibrate under a certain circumstance? i.e. incoming text, email, incoming/outgoing call, typing, etc.? Also, do you have any toggle widgets that could affect vibrate/ringer status?
I ask this because, and this may sound silly, it may be that you are modifying settings unknowingly. I've had that happen where I have my hands in my pockets and next thing I know I've accidentally got my Facebook up and running and typed half a book in the status field.
Again, I know that sounds silly but I ask because it's happened to me before.
Concordium said:
Does the phone ever always (or never) vibrate under a certain circumstance? i.e. incoming text, email, incoming/outgoing call, typing, etc.? Also, do you have any toggle widgets that could affect vibrate/ringer status?
I ask this because, and this may sound silly, it may be that you are modifying settings unknowingly.
Click to expand...
Click to collapse
That's fine, its an important clarification to make. But no, I am absolutely sure I have not changed any of the options unknowingly. As I said in the OP, ALL vibration/haptic feedback will cease to function entirely. I've often had it happen that in the middle of typing something, the haptic feedback for the keyboard will just go away. Immediately after this if I check the soft key buttons or test the vibration for notifications, none of these will produce any sort of vibration response either. Then randomly a few minutes, hours, or days later, all haptic feedback will just return. Its been an extremely strange and frustrating issue.
4nth0ny said:
It must be software related because the vibrate function works just fine when the phone rings. I am running CM 7.1 stable on an Evo 4G. I noticed the issue as well on CM 7.0.3.1 or whatever the latest stable build was on CM.
Click to expand...
Click to collapse
For me, when the vibration stops working, it stops working for everything, even when the phone rings. But that's what I can't figure out: if it is a software or hardware related issue. I was having this problem on stock Sense, and I figured if it was software related, perhaps flashing a new ROM (in my case, CM7), would fix it. However it hasn't, so I'm beginning to think if it is indeed a software issue, it must be a bug somewhere very deep within the code, otherwise it has to be a hardware issue. But if its a hardware issue, I can't figure out why it would randomly stop/start working like it does, and the thing is, most (75%) of the time, it is working. Its just the other 25% that annoys the hell out of me. That's why I thought I'd ask and see if anyone else had experienced it or found any solutions.
Its a CM7 thing I've noticed it on Xplod, Decks, and CM7 I don't really mind it cuz my ringers are loud as hell but yeah its pretty weird :shrugs:
Usually AOSP ROMs for some reason have that problem cuz on sense ROMs it never happens
infamousteeboy said:
Its a CM7 thing...Usually AOSP ROMs for some reason have that problem cuz on sense ROMs it never happens
Click to expand...
Click to collapse
Well like I said before, I was having this problem on my stock Sense ROM.....
infamousteeboy said:
Its a CM7 thing I've noticed it on Xplod, Decks, and CM7 I don't really mind it cuz my ringers are loud as hell but yeah its pretty weird :shrugs:
Usually AOSP ROMs for some reason have that problem cuz on sense ROMs it never happens
Click to expand...
Click to collapse
I've never had that problem on CM and I've been using many different versions of it for a long time. I don't know if I am lucky or what but people complain about a lot of issues that are claimed to be CM issues....yet I've never had a single one of them.
Concordium said:
I've never had that problem on CM and I've been using many different versions of it for a long time. I don't know if I am lucky or what but people complain about a lot of issues that are claimed to be CM issues....yet I've never had a single one of them.
Click to expand...
Click to collapse
Well I kinda had the same problem that he's run into on CM but I figured it out but I figured since he's had the problem on a sense ROM also then maybe its not the ROM but I jus went into everything that had the option to vibrate and turned them all on cuz I've flashed a couple ROMs and the vibration would be off I try not complain about anything about any ROM its a person hard work they've done for free I try to figure things out on my own as much as possible before I create a thread not bad talkin the OP but jus sayin you know?
I don't think that it's rom related. I've been having issues with my haptic feedback since I got the phone, even before rooting it. I think it's just a crappy vibrator. (If there's a better name than "vibrator", please someone tell me.)
I had vibration problems on my first Evo as well, it was never rooted. My second Evo was a HW004 and the haptic feedback was perfect - it was softer instead of the shock-like haptic feedback I've experienced with my 003s. My current and third Evo is also a 003, so I assumed it had something to do with the motor used in 003s.
I've just turned haptic feedback off. I thought I'd miss it, but I've gotten used to it. I still use have my phone set to vibrate for notifications and calls and I've seen fewer issues.
If you think you can go without, I'd suggest turning haptic feedback off. Otherwise, unroot and take it into Sprint. You may have more luck calling, because if you can't replicate the issue in front of them then they can't do much.
Sent from my Evo + MIUI using Tapatalk!
plainjane said:
I don't think that it's rom related. I've been having issues with my haptic feedback since I got the phone, even before rooting it...
...Otherwise, unroot and take it into Sprint. You may have more luck calling, because if you can't replicate the issue in front of them then they can't do much.
Click to expand...
Click to collapse
Yeah, its definitely not ROM related...I don't know if people aren't reading the posts, but I've said several times that this occasionally happened on stock Sense, both before and after rooting.
Dang. I didn't want to have to bring it in to get it fixed, but I guess that's what I'm gonna have to do if its a hardware problem...I was really hoping it was software related or if someone would know of a way to fix it so that I could avoid dealing with warranty services...I got suckered into the Best Buy warranty, and it turns out that even though they either give you a new or refurbished model, they make you turn yours in and wait 5-7 days for the replacement to come in instead of ordering the replacement and then doing a trade with you when it comes in. I already experienced it once before when my USB port broke... :/
Not being able to replicate the issue is my main concern since sometimes it works and sometimes it doesn't. Trying to get it to stop working at a time when I can actually run out to the store is gonna be a pain...And I really don't want to waste a trip to the Best Buy store only to have it start working again with me trying to tell the GeekSquad Agent, "I promise, I promise! It was broken just 5 minutes ago!!" I can't imagine how many of those they have to deal with....

[Q] S3 Speakerphone Echo Bug

Greetings,
First post here, I hope this is the appropriate section for it. I have google'd and forum searched extensively and have yet to find a thread dedicated soley to this issue. Many people have reported it within various ROM threads only to have the next poster state he doesn't have the issue and the problem get buried in a 500 page thread.
Having gotten my feet wet with the stock ICS ROM that came with my Galaxy S3, I was happy to enter the world of custom ROM's and flashed CM 10 M2 as my first custom ROM. I was very much enjoying CM 10 when I received my first phone call after switching. Being an exclusive speakerphone user, I answered the call and enabled the speakerphone as usual. The caller stated they couldn't understand me as there was an echo on the line. I turned speakerphone off and they stated the problem was fixed. After finishing the call, I called my cell phone from my landline and enabled the speakerphone on my S3, then walked to the other side of the house to minimize any close vicinity interference. When I spoke into my landline I could hear myself echo making a conversation almost impossible. I disabled the speakerphone on my S3 and the problem went away.
I restored my stock ICS ROM and was unable to duplicate the problem. I assumed the bug was specific to CM 10 and tried AOKP JB milestone 1 and had the same issue. Today I tried Task and Ktoonsez's latest AOKP JB 4.12 ROM and The Collective's AOCP ROM with the same results. All the problem ROM's were JB builds so perhaps it's a JB related issue. I will be trying a touchwiz based JB ROM next to see if I still have the issue.
I think alot of people assume when they read this bug report they blow it off as they can't actually hear the echo unless the person on the other line reports it. Maybe alot of people don't use speakerphone? I don't think it's a universal problem or more people would be reporting this but it's not intermittent either. I can reproduce it 100 percent of the time and it goes away when I recover to stock. I also removed my case when testing this and it had no effect. If there is a workaround or fix for this I would be very thankful to learn of it as I very much enjoyed the custom ROM's but I just can't give up speakerphone. Thanks in advance! :fingers-crossed:
I'm having the same issue...
+1
Follow up
kenrothman said:
I'm having the same issue...
+1
Click to expand...
Click to collapse
So today I tried newest builds of Parandoid Android, and Liquid Smooth with the same result. Pretty much all the popular ROM's in the "AT&T Galaxy S III Original Android Development" contain this bug, I'm assuming because they share alot of code. Seems like they base alot of work off of Cyanogen Mod so perhaps that's where it lies, I don't know.
What I do know is I installed DrewGaren's Jellybean 747 Milestone 7 ROM which is Touchwiz based and the speakerphone echo went away. So my stock ICS ROM and this one do not contain the issue but every other JB based ROM I have tried does. I don't have the knowledge to troubleshoot this issue I just wanted to share what I've found and hopefully someone with the knowledge can help track it down.
I do prefer the CM 10 style ROM's over the stock experience but I can't live without speakerphone so hopefully this issue gets resolved, thanks for listening!
I have the problem too. I bought my S3 3 weeks ago and within a few days rooted it and installed the latest CM10 nightly. The first time I used the speakerphone I became aware of the echo problem with the it. So I switched back to the stock rom and the problem was gone, so I knew it wasn't a hardware problem with my phone. I've tried every nightly CM10 rom including the recently released stable build. I also tried the latest official AOKP as well as Task and Koonsez's latest build and they all produce the echo.
My buddy suggested I try the black jelly rom, and that's the only one I've been able to use that doesn't have any echo, but it's a touchwiz/Samsung based build. It's not bad, but it doesn't support wifi tethering and it's not as smooth as CM or AOKP. I really want to run CM but can't live without speakerphone.
On a side note, I rooted and rom'd my wife's and friends S3 the exact same way as mine and neither of theirs have the speakerphone echo problem. I suspect there are some hardware differences with Samsung phones. Maybe different parts suppliers that aren't playing properly with the drivers in the CM10 build.
From my tests this bug sounds like the mic is turned up max when speakerphone is on so it's super sensitive. Also, the volume level doesn't have any effect on the speakerphone volume whether you raise or lower it.
Really hope the dev's can fix this so I can run CM or AOKP once and for all.
On a final note, my phone is blue, while both my wife's and my buddy's are white. I don't want to conclude that the white phones don't have the speakerphone echo problem with CM roms. Hope it's just a coincidence.
for cm10 there is an official bug ticket for it here : https://code.google.com/p/cyanogenm...on Model Network Owner Summary Stars Priority
Randomacts said:
for cm10 there is an official bug ticket for it here : https://code.google.com/p/cyanogenm...on Model Network Owner Summary Stars Priority
Click to expand...
Click to collapse
thanks for pointing that out. looks like it's not really a popular issue, or popular enough to get them focussed on fixing it
anyone have any thoughts as to why identical phones don't behave the same, ie some S3's have the echo and some don't? I have 3 days left (30 day purchase return policy) to exchange my phone, and am contemplating getting it swapped to see if I get lucky with another unit which won't have an echo problem running CM10 or AOKP.
gots54 said:
thanks for pointing that out. looks like it's not really a popular issue, or popular enough to get them focussed on fixing it
anyone have any thoughts as to why identical phones don't behave the same, ie some S3's have the echo and some don't? I have 3 days left (30 day purchase return policy) to exchange my phone, and am contemplating getting it swapped to see if I get lucky with another unit which won't have an echo problem running CM10 or AOKP.
Click to expand...
Click to collapse
Hi, just wondering if anyone has found a fix for this or any other AOSP JB Roms that has the speakerphone echo fixed?
ladd76 said:
Greetings,
First post here, I hope this is the appropriate section for it. I have google'd and forum searched extensively and have yet to find a thread dedicated soley to this issue. Many people have reported it within various ROM threads only to have the next poster state he doesn't have the issue and the problem get buried in a 500 page thread.
Having gotten my feet wet with the stock ICS ROM that came with my Galaxy S3, I was happy to enter the world of custom ROM's and flashed CM 10 M2 as my first custom ROM. I was very much enjoying CM 10 when I received my first phone call after switching. Being an exclusive speakerphone user, I answered the call and enabled the speakerphone as usual. The caller stated they couldn't understand me as there was an echo on the line. I turned speakerphone off and they stated the problem was fixed. After finishing the call, I called my cell phone from my landline and enabled the speakerphone on my S3, then walked to the other side of the house to minimize any close vicinity interference. When I spoke into my landline I could hear myself echo making a conversation almost impossible. I disabled the speakerphone on my S3 and the problem went away.
I restored my stock ICS ROM and was unable to duplicate the problem. I assumed the bug was specific to CM 10 and tried AOKP JB milestone 1 and had the same issue. Today I tried Task and Ktoonsez's latest AOKP JB 4.12 ROM and The Collective's AOCP ROM with the same results. All the problem ROM's were JB builds so perhaps it's a JB related issue. I will be trying a touchwiz based JB ROM next to see if I still have the issue.
I think alot of people assume when they read this bug report they blow it off as they can't actually hear the echo unless the person on the other line reports it. Maybe alot of people don't use speakerphone? I don't think it's a universal problem or more people would be reporting this but it's not intermittent either. I can reproduce it 100 percent of the time and it goes away when I recover to stock. I also removed my case when testing this and it had no effect. If there is a workaround or fix for this I would be very thankful to learn of it as I very much enjoyed the custom ROM's but I just can't give up speakerphone. Thanks in advance! :fingers-crossed:
Click to expand...
Click to collapse
+1
speakerphone echo
I also have this problem. using baked 8. with kt747 and its awesome!! They seem to be aware and working on it. tried a different kernel but no dice. Ive been in every setting cant seem to get rid of it. my phone is white so its not that. hope someone can figure this out soon. tw roms dont have this problem and I like the aosp feel.It would be nice to know if anyone even an idea of the cause, maybe the users could check files and find something.
I confirm that I LOVE these ROMs, but absolutely need a working speakerphone too.
Some other thread said something about changing the radio to ULVA3 or something like that... not sure if anyone had any luck with that.
Anyways, thought I'd break my lurked tendencies and post for my 1st time here.
Love my GS3!
So I've been very happily using the Samsung-based ROM called Devils Reject since Dec 2012, and have been on V7 since it came out a few months ago and have been really happy with it. It's pretty smooth and stable, has great battery life, has tethering, custom toggles, various battery icons, AOKP lockscreen, power button menus, plus a bunch of other stuff I can't remember, and of course, there are no speakerphone problems.
But I've always been curious about giving CM another chance with CM10.1 and especially with the latest RC2 out.
Does anyone know if the speakerphone bug still exists with it?
speakerphone echo bug in CM10.1 RC2 for quincyatt
gots54 said:
So I've been very happily using the Samsung-based ROM called Devils Reject since Dec 2012, and have been on V7 since it came out a few months ago and have been really happy with it. It's pretty smooth and stable, has great battery life, has tethering, custom toggles, various battery icons, AOKP lockscreen, power button menus, plus a bunch of other stuff I can't remember, and of course, there are no speakerphone problems.
But I've always been curious about giving CM another chance with CM10.1 and especially with the latest RC2 out.
Does anyone know if the speakerphone bug still exists with it?
Click to expand...
Click to collapse
I have the speakerphone echo bug on my Samsung Galaxy Note with CM10.1 RC2. This has happening on earlier versions as well, but I thought a reset/wipe fresh install would fix it. Would like to stay on CM10.1 but I really depend on my speakerphone.

[Q] Dial up tone sound when making calls

I have been flashing ROMs for years and can almost always resolve issues on my own but I am stumped and can't find answers. I have been getting random aol type dial up sound when I make some calls. Even once I hang up the call the sound continues until i turn off my phone and turn it back on. Of course this seems to happen at the worst time so it is rather annoying. I first noticed it on RC8 then RC9 I have tried several other roms and even flashed root66 to try and resolve this. I have also flashed kootz kernel, lean kernel and the kernel that comes with some CM based roms and nothing has worked so far. I am looking for help if anyone has ideas I would greatly appreciate it. Thanks in advance

[Q] Random reboots and lock ups (memory leak?)

Hey all,
I've had this issue with everything but the stock rom. After a certain amount of time the phone either locks up to where I have to pop the battery, or will graphic glitch on the screen for a second and then auto reboot. Happens maybe 2-4 times a day depending on the day.
I've done a full wipe and full factory reset. I've been modding phones for ages and this is the first time I've encountered this issue. Everything else seems to run completely fine.
I'm running resurrection rom, but it's done this on several other roms I've tried. However all roms are AOKP/AOSP based if that's relevant.
If there is anymore information I can offer please don't hesitate to ask. I searched the forums and couldn't seem to find anyone else really talking about this. It can be a giant headache so hopefully I can get it sorted.
heartspains88 said:
Hey all,
I've had this issue with everything but the stock rom. After a certain amount of time the phone either locks up to where I have to pop the battery, or will graphic glitch on the screen for a second and then auto reboot. Happens maybe 2-4 times a day depending on the day.
I've done a full wipe and full factory reset. I've been modding phones for ages and this is the first time I've encountered this issue. Everything else seems to run completely fine.
I'm running resurrection rom, but it's done this on several other roms I've tried. However all roms are AOKP/AOSP based if that's relevant.
If there is anymore information I can offer please don't hesitate to ask. I searched the forums and couldn't seem to find anyone else really talking about this. It can be a giant headache so hopefully I can get it sorted.
Click to expand...
Click to collapse
If this has just started recently in would say it is indeed apart of the cm base, and related to kernel issue. Since the kernel devs are using cm and their kernel base most ROMs kernels have the same base, which means in a round about way they may react the same way on your device. To me, you said graphic glitch, then reboot. I would bump up your voltage little by little and see if it stops, I also would change govs in the kernel.. I'm assuming it happens on any cm kernels you've tried? Yank555 has an awesome cm kernel I would highly recommend, or even imoseyon always has a solid stable cm kernel as well.
How are you transferring the firmware? The heavy cable with the heavy plug? If so, it might have damaged your device's USB port and is causing intermittent disconnections which are corrupting the data as it is transferred. Try a lightweight cable and make sure it is firmly seated, then don't let it move during the transfer.
If this solves it then maybe look into replacement due to faulty design.
Frank
It is happening on all roms, however the only custom roms I've tried are CM based. I'll take a look at these other kernels and see if that resolves. Thanks for the help and idea's so far guys.
I've been having the same issues. Hellish reboots though. 10+ a day... Keep me posted. Thanks
Sent from my SM-N900T using XDA Premium 4 mobile app

AOSP on D851 Question

I have tried numerous times to go from 30e stock to Cyanogenmod to no avail. Everything installs properly and seems to be working perfectly until I make calls. People start to complain that the call quality is horrible and I end up flashing back to stock and the call quality goes back to normal. Anyone else have this issue? Any suggestions on how to fix this?
I really want to run LineageOS but without good call quality I am reluctant to switch to any other rom.
Thanks for any help or input you can provide.
jrosetto said:
I have tried numerous times to go from 30e stock to Cyanogenmod to no avail. Everything installs properly and seems to be working perfectly until I make calls. People start to complain that the call quality is horrible and I end up flashing back to stock and the call quality goes back to normal. Anyone else have this issue? Any suggestions on how to fix this?
I really want to run LineageOS but without good call quality I am reluctant to switch to any other rom.
Thanks for any help or input you can provide.
Click to expand...
Click to collapse
Since the lack of responses I decided to make the plunge to LineageOS 14.1. I think I figured out that in APN settings if I set it to IPv6 only the issue is resolved. Time will tell.

Categories

Resources