Related
Hi folks
I have a Nexus S (i9020a). It has stock 4.1.2 Jelly bean from Google (downloaded the stock image and flashed it). It worked fine for over a month.
Suddenly few days back this device got a problem. When I dial any number I can't hear any dialing sounds and even after the call has connected I can't hear the opposite person and the opposite person also can't hear me (The phone still shows as 'Dialing' though it's already connected). The same is true when I answer any call. Both parties can't hear anything.
This is solved by rebooting the phone for the first phone call only. After I reboot, the 1st phone call works fine, then this problem persists for any calls I make/receive until I reboot the phone again.
I tried flashing a different radio but this problem is still there. I tried my sim card on a different phone and it works fine, so the problem is not that too. My 3G data works just fine.
I need this phone for the next few days/weeks (hopefully not months) before my Nexus 4 gets delivered :laugh:
Thanks..
Edit: Modified the title; Probably gave the wrong meaning that the problem is solved.
<bump> Modified the title. Earlier title gave an impression that the problem is solved whereas I still have a problem.
Have you installed any apps which could somehow affect the dialler?
Unless someone else can give you a different advice, I can't think of any other option than do a full wipe and reflash.
I haven't installed any such apps.
Also, I already did a full wipe and flashed the stock image again. The problem is still there.
Don't know what else you could try, sorry mate - hope someone else can help you sort it out!
Thanks for trying. I think I will go to some hardware shop and see if they can figure out..
Try using a headset for making phone calls so that we can identify if it's really the hardware's problem.
ej8989 said:
Try using a headset for making phone calls so that we can identify if it's really the hardware's problem.
Click to expand...
Click to collapse
That's the first thing that I tried... doesnt work.
mailrachit said:
That's the first thing that I tried... doesnt work.
Click to expand...
Click to collapse
I had similar problem when RAM running out. Usually a reboot fix the problem for a bit.
What I did:
1. With Titanium Backup Pro, froze unused RAM hogging system apps, like Google+, Google play magazine,etc
2. Froze or uninstall Facebook, Word with Friends, etc which are resident and hog RAMs .
3. Install marmite kernel, free up more usable RAMs.
Hope it helps you too.
_android_ said:
I had similar problem when RAM running out. Usually a reboot fix the problem for a bit.
What I did:
1. With Titanium Backup Pro, froze unused RAM hogging system apps, like Google+, Google play magazine,etc
2. Froze or uninstall Facebook, Word with Friends, etc which are resident and hog RAMs .
3. Install marmite kernel, free up more usable RAMs.
Hope it helps you too.
Click to expand...
Click to collapse
Thanks for the suggestion!
I tried this too but doesn't work...
Try any custom ROM instead of stock ROM and a different kernel too. There could be chances that you've flashed the wrong ROM / radio too.
Sent from my Nexus S
Problem solved.
I went to a hardware store today. The guy said that it's a problem with the 3G service of my carrier (Vodafone India). The moment I enabled the '2G only' option in the Mobile networks settings area, this problem was gone. The technician said that this issue is affecting some people randomly. He said that since 3G service was launched just last year, the networks are not yet capable of handling all kinds of devices (he claims that the bug is so erratic that another Nexus S i9020a may work just fine with the very same bootloader/radio/rom which doesn't make any sense). When I said that 3G service was working fine before, he said that most probably my carrier changed some settings on their side which is causing this issue for me.
I have tried this for 6-8 hours now, making a lot of phone calls and it seems that the issue is gone. It saddens me that I am off 3G for now but at least my phone calls and basic EDGE internet works fine. I will have to work with Vodafone to solve this or simply wait for my new phone (Nexus 4) and hope it won't have the same problem..
Q&A for Lollipop 5.0 runs on our msm8960s on kkbl
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Lollipop 5.0 runs on our msm8960s on kkbl. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Battery Life
derpyherp said:
I think its odd how there is no deep sleep state i put a screen shot of the cpu times at each cpu speed... Its odd but somehow battery life is amazing
Click to expand...
Click to collapse
I switch back to cm11 because i have 6%/hr of battery drain, (7hr/41min Screen on time, 65% left), that is for me horrible battery life.
I did not look the cpu states, but, if there is no deep sleep, it sould explain mi experience about battery.
I have the same mensage when I was in f2fs. I have to go back to ext4 to work.
Does anyone know if the AOSP Camera will be made available? I don't like the Google one since it doesn't allow me to choose the external SD card as a storage option.
The system itself boots, and runs quite smoothly from what I've tried so far. Very exciting!
But I've found that Lastpass crashes immediately when I try to launch it. I did a clean install with CM12 11/17. Has anyone else seen this behaviour with this app? I'm assuming for the moment it just hasn't yet caught up to Android 5, and I'll have to sit patiently on 4.4 until then.
Cubkyle said:
The system itself boots, and runs quite smoothly from what I've tried so far. Very exciting!
But I've found that Lastpass crashes immediately when I try to launch it. I did a clean install with CM12 11/17. Has anyone else seen this behaviour with this app? I'm assuming for the moment it just hasn't yet caught up to Android 5, and I'll have to sit patiently on 4.4 until then.
Click to expand...
Click to collapse
I don't use that app, but it's probably either one of two things (or both):
This ROM was just release back on 11/14, so it's fairly new (the 11/14 was the first release), so there could be some issues that are causing the app to fail.
The app needs to be updated to run correctly under LP. There were some major changes to the API for LP that could cause other apps to fail that are now using these deprecated API calls. The developer needs to take there app and compile it under the latest LP compiler and libs to see if it compiles.
So, you'll probably have to wait and see. So far, I've been lucky. The apps that I need to work (CoPilot USA, etc) all work. Just waiting for dhacker to figure out the correct set of libs for DRM so that Google Play Movies and Netflix start working again. They work fine under my Nexus 7 running LP, but that was an official release by Google.
iBolski said:
I don't use that app, but it's probably either one of two things (or both):
This ROM was just release back on 11/14, so it's fairly new (the 11/14 was the first release), so there could be some issues that are causing the app to fail.
The app needs to be updated to run correctly under LP. There were some major changes to the API for LP that could cause other apps to fail that are now using these deprecated API calls. The developer needs to take there app and compile it under the latest LP compiler and libs to see if it compiles.
So, you'll probably have to wait and see. So far, I've been lucky. The apps that I need to work (CoPilot USA, etc) all work. Just waiting for dhacker to figure out the correct set of libs for DRM so that Google Play Movies and Netflix start working again. They work fine under my Nexus 7 running LP, but that was an official release by Google.
Click to expand...
Click to collapse
It turns out it was simply a matter of PEBCAK. I uninstalled Android System Webview, because it has the same icon as the stock Browser, while I was removing unwanted processes.
The first time , I flashed 11/15 version, everything seems to work fine ,then I flashed gapps, then I got no signal anymore,but everything else seems to work, so I did a factory reset, the gsm signal came back again, today when I trying to flash 11/18 version, the signal gone again, this time I don't want loose my data , what should I do to get a gsm signal? *#*#4636#*#* seems not working on 11/18, sorry for my poor english
Cubkyle said:
It turns out it was simply a matter of PEBCAK. I uninstalled Android System Webview, because it has the same icon as the stock Browser, while I was removing unwanted processes.
Click to expand...
Click to collapse
Ah, I'm familiar with those errors as well as the ID10T error as well.
Works just fine, very smooth. Had no troubles with the signal at all.
However, I can't receive a call, the dialer just stops. It is possible though to make a call. Anyone had this problem?
yes had that error many times "dialer has stopped", this is work in progress man. I hope that dhacker checks this and the other thread and try to remedy some of the prob.
For that dialer has stopped error, a reboot can cure it. But again i cant rely on a phone that is going to quit when you need to make or receive a call.
So the fix for no service is still reboot and hope?
I'm on Verizon CDMA, XT926, 11/23 build, 11/22 gapps, SuperSU 2.27
Thanks.
Doug B.
I had an odd issue on 11/22 build:
When I connect my car via bluetooth, when a call comes in, pressing the answer button does nothing and the call keeps ringing forever.
Also,
Is Anyone having issues with restoring on TWRP 2.8.1.0? I tried restoring a backup I made and my phone won't boot. It just gets stuck at the cyanogen mod screen.
Edit: I restored a previous backup, installed TWRP 2.8.2.0 and then restored the backup I was trying to. It worked.
dvgb173 said:
So the fix for no service is still reboot and hope?
I'm on Verizon CDMA, XT926, 11/23 build, 11/22 gapps, SuperSU 2.27
Thanks.
Doug B.
Click to expand...
Click to collapse
On my 11/25 build data wasn't working at first, I just turned it on and off from settings and it started working.
11/25 build is working for me as far as being able to receive phone calls. I was previously getting FCs on it when an incoming call was coming, but I was also running f2fs. I've gone back to ext4 and things seem to have stabilized at this point.
This build is the dhacker? I found nothing in his link. Many changes over the previous build?
When open 3g ,call comein can not.
How to fix it?
Thank.
soowijux said:
When open 3g ,call comein can not.
How to fix it?
Thank.
Click to expand...
Click to collapse
Now, I install 30/11 it OK.
Thanks.
SMS issue
Is the sms issue (can't receive sms, although the phone I'm sending from receives the delivery report) still present in this new build (12-02)? I've tried the 11-25 build and BlissPop and none of them allowed me to receive sms... It's the one real issue that's keeping me from jumping into Lollipop
Razr HD (XT925, KK bootloader)
My device does not come out of the boot with this version.
Q&A for [ROM] Un-Adulterated CM12 5.0.2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] Un-Adulterated CM12 5.0.2. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
I noticed one small problem, I was unable to send a text message. I could read them but.unable to send with the built messaging app. I did not have a lot of time to spend on this rom yet. Look forward to it though. Thanks
eevanskiteboards said:
I noticed one small problem, I was unable to send a text message. I could read them but.unable to send with the built messaging app. I did not have a lot of time to spend on this rom yet. Look forward to it though. Thanks
Click to expand...
Click to collapse
Hrm, were you using hangouts? I use hangouts for SMS and have had no probs yet, haven't really tested MMS yet though.
Sent from my SM-G900P using XDA Free mobile app
I really want to try this ROM on my phone but I only have one device and its my daily device. I read in the other thread that there was an issue with answering incoming calls. Is there a fix for that?
Prince_Basil said:
I really want to try this ROM on my phone but I only have one device and its my daily device. I read in the other thread that there was an issue with answering incoming calls. Is there a fix for that?
Click to expand...
Click to collapse
The incoming calls is fixed, I am using it on my only device and its pretty solid so far.
Sent from my SM-G900P using XDA Free mobile app
Has anyone tested the IR Blaster on this build yet? I'm interested in trying this ROM but from what I understand and from my previous CM12 experience, I haven't seen the IR Blaster working on any AOSP ROM.
Anyone have advice on getting the messaging app to work? I'm using a third party app but the regular messaging app is constantly force closing. Would it be safe to just disable it or would that stop texts all together?
rwenterprises said:
Has anyone tested the IR Blaster on this build yet? I'm interested in trying this ROM but from what I understand and from my previous CM12 experience, I haven't seen the IR Blaster working on any AOSP ROM.
Click to expand...
Click to collapse
Just briefly tested, volume and channels work on my lg TV using IR 2.0 Universal Remote.
Prince_Basil said:
Anyone have advice on getting the messaging app to work? I'm using a third party app but the regular messaging app is constantly force closing. Would it be safe to just disable it or would that stop texts all together?
Click to expand...
Click to collapse
I use hangouts for SMS and no issues.
Sent from my SM-G900P using XDA Free mobile app
Thanks, I'll try that App out. I've been using Smart Remote with TW based ROM's w/great success, thought I'd give IR a try again on AOSP ROM's since it appeared to be working per list of working items. Thanks again for the reply.
call bug in CM12
Whenever my phone received a call it would forward them straight to voicemail and would have this ringing sound that would come from the handset earpiece of the phone and it would only stop after I restart the phone. What should I do?
P.s. I have the SM-G900p (sprint variant) of the Samsung galaxy
Thanks for the awesome ROM!
I did also notice some bugginess with BT, Pandora when connected to my Mazda 3.
Funny behavior is that it works fine when disconnected but soon as I connect to the car Pandora does not play...so I'm not sure If its an issue with Pandora itself or something else..
Thanks! Great work!
---------- Post added at 04:35 PM ---------- Previous post was at 03:59 PM ----------
Dre8597 said:
Whenever my phone received a call it would forward them straight to voicemail and would have this ringing sound that would come from the handset earpiece of the phone and it would only stop after I restart the phone. What should I do?
P.s. I have the SM-G900p (sprint variant) of the Samsung galaxy
Click to expand...
Click to collapse
I experienced this as well when using the CM from the official site. Mike's ROM Fixed this..
Another Issue I've found, not sure if its just google or CM12 base, but if you open up the dial pad while in the call i.e to push keys for menus or something, the ear piece stops outputing sound, have to enable speaker phone in order to hear when key pad is open.
Bluetooth issue, bluetooth share crashes after a few songs played back on Pandora..
Anyone else experiencing MISC battery drain? 40% of my battery drain is related to that. I've read its caused by WIFI being on (makes sense as I"m almost always connected to WiFi (home or work) ... going to test to see if keeping wifi off at work tomrrow helps out more.
I'm using the 1/13 nightly build (flashed 1/11 beforehand) - this looks and works great. Two bugs in facing: I cannot receive phone calls (just a weird ring that only goes away with a reboot) and MMS won't work. Planning on doing tonight's build.
@ Izzy.. ineteresting, I was seeing that with Official Nightly's, but not Miked's compile.. wonder what he's doing differently
Also, with the latest nightly for 1/12 that Mike put out looks like bluetooth is stable.... atleast made it through my entire morning commute to work (about 30 mins) without any issues. Lets see what happens on the way home.
Regarding calls
In regards to calls in the most recent posts on page 9, I am also having issues. I have tried calling to and from my office so I can control both ends and I'm unable to hear either end. The calls connect but there is no noise from either speaker. Just chiming in on the issue. Thanks for an otherwise solid build!
Remesar said:
Anyone else experiencing MISC battery drain? 40% of my battery drain is related to that. I've read its caused by WIFI being on (makes sense as I"m almost always connected to WiFi (home or work) ... going to test to see if keeping wifi off at work tomrrow helps out more.
Click to expand...
Click to collapse
I think I may have found a fix for the battery drain, try out my latest build and let me know.
As for the call problems people are having, I really don't know I have not had any issues since the first build I did. After the first one I used a different device tree and haven't had any problems. Just to try to correlate the issue, could anybody having calling problems please report what baseband they are using? I am on NKD, and like I said no probs. The first build I made had the same problem as the official nightlies where it had a weird ring but couldn't pick up. In fact the only build I had the problem on was actually removed from the links so anybody experiencing it is likely running into something new.
miked63017 said:
I think I may have found a fix for the battery drain, try out my latest build and let me know.
As for the call problems people are having, I really don't know I have not had any issues since the first build I did. After the first one I used a different device tree and haven't had any problems. Just to try to correlate the issue, could anybody having calling problems please report what baseband they are using? I am on NKD, and like I said no probs. The first build I made had the same problem as the official nightlies where it had a weird ring but couldn't pick up. In fact the only build I had the problem on was actually removed from the links so anybody experiencing it is likely running into something new.
Click to expand...
Click to collapse
I've installed your latest build, testing it now, well will charge fully to 100% and then see if misc battery drain appears.
I'm on NK4 baseband. Experiencing a few issues...
- Laggy dialer
- When using keypad in the dialer sometimes earpiece cuts out and have to put into speaker phone and then back (i.e when using automated menus during calls)
I am able to make and receive calls as far as I can tell... Should I have flashed the stock lolipop rom first I wonder...
Remesar said:
I've installed your latest build, testing it now, well will charge fully to 100% and then see if misc battery drain appears.
I'm on NK4 baseband. Experiencing a few issues...
- Laggy dialer
- When using keypad in the dialer sometimes earpiece cuts out and have to put into speaker phone and then back (i.e when using automated menus during calls)
I am able to make and receive calls as far as I can tell... Should I have flashed the stock lolipop rom first I wonder...
Click to expand...
Click to collapse
That's the same thing I am wondering, not sure if the people who are experiencing call issues are related to their baseband. I did briefly test on some earlier basebands and didn't notice any probs, but the testing was far from extensive. Its just a thought but could be related.
I haven't noticed the earpiece problem, but I always use speakerphone for menus and such. The dialer lag I have noticed, it just hasn't seemed worse to me than on any other ROM including stock ones. Hopefully these are things that will be washed out with future updates. I plan to continue builds indefinitely, and fix what I can, but these seem like they would be hard to track down at this point.
2-02 Updated Rom
Did you forget to change the data in the OP?
Hi there, I bought an S Relay when it was first released here in the US. I just have a tiny issue with it that still hasn't been resolved in however many times I've updated the damn thing.
I currently have a cyanogenmod based rom on the phone, but this happens with almost any cyanogenmod rom. (Including the official ones) The screen, even though I unlock the phone, will sometimes decide to stay dark or give me this weird broken-crt pattern with bits of what I'm supposed to be looking at jumbled in. Does anybody else have this issue? Or am I just crazy?
In this respect, the offical samsung rom works great with the phone. I would use it if it didn't suck so bad, which is why I want to figure this out. The specific rom is FatToad[Android 5.0.2] by TeamApexQ, but this has happened ever since they started development on the cyanogenmod rom way back when.
Are you using bluetooth when this happens? As of FatToad 5.0.2, currently the only verified reason for this to happen is memory exhaustion (and resultant spike in CPU as it attempts to swap and fails) The only thing I've seen to cause this and not fall prey to Android's low memory killer is the bluetooth stack which seems a bit buggy. If you are not using bluetooth, please send me a logcat of the issue. Also, when this happens, can you still get to adb?
Magamo said:
Are you using bluetooth when this happens? As of FatToad 5.0.2, currently the only verified reason for this to happen is memory exhaustion (and resultant spike in CPU as it attempts to swap and fails) The only thing I've seen to cause this and not fall prey to Android's low memory killer is the bluetooth stack which seems a bit buggy. If you are not using bluetooth, please send me a logcat of the issue. Also, when this happens, can you still get to adb?
Click to expand...
Click to collapse
I'm going to install android studio now and see if I can get the log info. But no, without bluetooth enabled, this still happens.
I just dumped the log from my phone around when this happens. It took a few tries to get it to happen, but it eventually did. I stopped logcat right after I got the screen to wake and unlock successfully. I'll attach it here.
Also, adb does work even when the screen doesn't wake up.
(I had to zip it since the size nazis caught me 36 kb over the 512 kb limit.)
jjsullivan5196 said:
I currently have a cyanogenmod based rom on the phone, but this happens with almost any cyanogenmod rom. (Including the official ones) The screen, even though I unlock the phone, will sometimes decide to stay dark or give me this weird broken-crt pattern with bits of what I'm supposed to be looking at jumbled in. Does anybody else have this
Click to expand...
Click to collapse
Same problem here, and I have yet to find a solution (CM11)
I tried to change the governor, and it seemed to work, but then I*updated to Valdius 5.0.2, and no wakelocks.
After last update ( Build cm-13.0-20160110-UNOFFICIAL-skyrocket ) i can't make calls
the device reboots when i do this and this problem was in ( Build cm-13.0-20151219-UNOFFICIAL-skyrocket )
so what i can do ??!
M7mD.Sa3eD said:
After last update ( Build cm-13.0-20160110-UNOFFICIAL-skyrocket ) i can't make calls
the device reboots when i do this and this problem was in ( Build cm-13.0-20151219-UNOFFICIAL-skyrocket )
so what i can do ??!
Click to expand...
Click to collapse
Flash something else more stable that better suits your needs for now. This rom is still a work in progress. There will be a few hiccups from time to time. Wait for the next update
Sent from my SAMSUNG-SM-G890A
M7mD.Sa3eD said:
After last update ( Build cm-13.0-20160110-UNOFFICIAL-skyrocket ) i can't make calls
the device reboots when i do this and this problem was in ( Build cm-13.0-20151219-UNOFFICIAL-skyrocket )
so what i can do ??!
Click to expand...
Click to collapse
Yeah me too, I'm in the process of sending logs to developer. So I went back to 20151222 until problem analysed/resolved.
spacebar208 said:
Yeah me too, I'm in the process of sending logs to developer. So I went back to 20151222 until problem analysed/resolved.
Click to expand...
Click to collapse
I'm on 20151222 right now until the problem be solve
Sent from my SGH-I727 using Tapatalk
Bumping the **** outta this. Same issue on a build one year later (Cm13 Oct 01/2016 Celox). Contacts and phone stopped working. So I replaced them with Google's AOSP variants from the play store. At that point, the phone reboots when I try to call. The 3g works wtf...
Edit:
Yes, this was sent from my SGH-I727R by I'd rather be making calls with this. Also, incoming calls work. Just outgoing is the issue. Can't be my radio, right? Cm11 or 10 whatever it was worked flawlessly on the same one.
Edit2:
Ok, so after jerking around the apps, disabling/re-enabling the system dialer, etc., I received a call from my friend. At the point, all four soft keys stopped working while the calling issue completely fixed itself. After a reboot, the soft keys and the calling work flawlessly 0.0
Typical Android issues...
Although my friend is complaining about some beeping noise coming from my end during a call. Will look into it.
So current fix (for now): disable/re-enable the inbuilt contacts and dialer apps, reboot, enable them, clear their data, cache, whatever it takes, etc. Keep doing so until it magically fixes itself. Maybe try getting a buddy to call you and pick up. That is all I can think of in order to reproduce such weirdness :/
Cyanogen Mod is dead
dimapoter said:
Bumping the **** outta this. Same issue on a build one year later (Cm13 Oct 01/2016 Celox). Contacts and phone stopped working. So I replaced them with Google's AOSP variants from the play store. At that point, the phone reboots when I try to call. The 3g works wtf...
Edit:
Yes, this was sent from my SGH-I727R by I'd rather be making calls with this. Also, incoming calls work. Just outgoing is the issue. Can't be my radio, right? Cm11 or 10 whatever it was worked flawlessly on the same one.
Edit2:
Ok, so after jerking around the apps, disabling/re-enabling the system dialer, etc., I received a call from my friend. At the point, all four soft keys stopped working while the calling issue completely fixed itself. After a reboot, the soft keys and the calling work flawlessly 0.0
Typical Android issues...
Although my friend is complaining about some beeping noise coming from my end during a call. Will look into it.
So current fix (for now): disable/re-enable the inbuilt contacts and dialer apps, reboot, enable them, clear their data, cache, whatever it takes, etc. Keep doing so until it magically fixes itself. Maybe try getting a buddy to call you and pick up. That is all I can think of in order to reproduce such weirdness :/
Click to expand...
Click to collapse
I don't think anything will really work in cm now because it's now discontinued and function will not work Cyanogen Account, etc. I also think it's modems stopped working... see here:Click Here