Related
Can someone please help me with this. I really want to update to Jellybean but I have the most annoying bluetooth issue on every ROM I have tried.
I have tried all JB ROMs and standard Kernel and the Sultan Kernel. I have asked in a couple of the ROM threads but got no reply.
The issue is when I connect to my car it takes 5 seconds for the sound to transfer from the phone internal speaker to the bluetooth in my car.
Use my phone for work and can't wait 5 seconds in the car when I receive a call before I can hear the other end of the conversation.
It worked perfectly on my old ICS ROM.
Anyone encounter this or know how to fix it?
Thanks a million for help!
turn your phone s-off if u ain't.
:-??
------------------------------------------------
PRESS THE PRETTY "THANKS" BUTTON IF I HELPED
Sent from a shaked up HTC Sensation XE using xda premium
lassykk said:
Can someone please help me with this. I really want to update to Jellybean but I have the most annoying bluetooth issue on every ROM I have tried.
I have tried all JB ROMs and standard Kernel and the Sultan Kernel. I have asked in a couple of the ROM threads but got no reply.
The issue is when I connect to my car it takes 5 seconds for the sound to transfer from the phone internal speaker to the bluetooth in my car.
Use my phone for work and can't wait 5 seconds in the car when I receive a call before I can hear the other end of the conversation.
It worked perfectly on my old ICS ROM.
Anyone encounter this or know how to fix it?
Thanks a million for help!
Click to expand...
Click to collapse
It could be a device incompatibility with the blue tooth receiver.
There are a few devices that just don't work right with the JB roms even though bluetooth does work. For instance on both Bruce's ROM and the offical CM10 rom, I don't have this problem. So it CAN work. But like I said there ar enumerous people who have had issues that turned out to be some kind of issue with the device not communicating well with JB.
It could still be an issue with your phone though. Do you have any apps that might interfere with bluetooh like an automatic volume up app when blueooth connects or something like that? If so, delete all that stuff. See if the results improve.
Do you have another bluetooth device you can test it with? At lest we could narrow down if it's a reciver issue or a ROM issue.
Also try doing a fresh install after a full wipe. Then just boot it up and try it. Don't install anything else. Just see if you have the problem on a completely clean install. If you don't, you might have an app interference issue.
Skipjacks said:
It could be a device incompatibility with the blue tooth receiver.
There are a few devices that just don't work right with the JB roms even though bluetooth does work. For instance on both Bruce's ROM and the offical CM10 rom, I don't have this problem. So it CAN work. But like I said there ar enumerous people who have had issues that turned out to be some kind of issue with the device not communicating well with JB.
It could still be an issue with your phone though. Do you have any apps that might interfere with bluetooh like an automatic volume up app when blueooth connects or something like that? If so, delete all that stuff. See if the results improve.
Do you have another bluetooth device you can test it with? At lest we could narrow down if it's a reciver issue or a ROM issue.
Also try doing a fresh install after a full wipe. Then just boot it up and try it. Don't install anything else. Just see if you have the problem on a completely clean install. If you don't, you might have an app interference issue.
Click to expand...
Click to collapse
Hi thanks for replying.
I will try Bruce's ROM but the official CM10 ROM didn't work for me.
I don't have any apps that could be interfering as all I have done whilst testing this problem is do a full wipe, install the JB ROM and go and check the bluetooth.
I will check tonight if the issue exists on another bluetooth device and report back any problems.
Cheers
AW: [Q] Bluetooth Issue - All Jellybean ROMs - All Kernels
Delete please
I have a Sony bluetooth head unit in my car which supports handfree and audio streaming profiles. I can play my music through the head unit just fine via bluetooth. I can also make and receive calls without problem when I am listening to the radio (ie when I am not listening to my own music). However, when I am playing my own tunes and I either make or receive a call, the head unit indicates I am on a call, it mutes the music but I just get silence through the speakers.
I used to have a Galaxy S Advance and it all worked just fine without too much configuration on the phone or head unit; basically just pair them up, make sure the right boxes are ticked in the bluetooth options and thats it.
Any idea what the problem could be? I've tried an upgrade to 4.2.2 but it didn't help...
Hi,
I have a similar problem. I can pair my s2 plus with cm11 from this thread to my car kit (Parrot MKi 9200). Playing music via phone on the car speakers works fine but when I place a call the receiving phone just gets loud static (and my voice very very silent).
I wanted to ask the developer of the cm11 I am using if he sees a way to exchange the bluetooth module (or what androis equivalent is) to the one of e.g. Android 4.1.2 because I know that one works perfectly. I am posting here because I havent reached 10 posts yet.
Of course I am open to other workarounds and ideas.
Thanks,
Kiesel
Bluetooth
Same issue here,
everything (music etc.) is okay, but the phone connection.
I'm connecting to my Ford Sync.
I can connect, but then the quality of the voice is very very bad, I can hardly understand anything...
I thing there's a configuration file in the etc/ folder, maybe that need some upgrade?!?
Hope someone can help, because I really like to keep CM11 on my phone...
Dan
This is a known problem wich has been asked 100 times before
Sent from my GT-I9105P using xda app-developers app
safariking said:
This is a known problem wich has been asked 100 times before
Sent from my GT-I9105P using xda app-developers app
Click to expand...
Click to collapse
How is this message supposed to be of any help? Of course we know that. We have seen a lot of threads. I have read the whole bug report including all the comments on googlegroups, I have browsed dozens of websites and googled my ass of. What I didnt find was an explanation (at this point I dont expect to find a fast solution anymore). After reading the googlegroups bug call I thought it was a problem with the bluetooth stack that apparently is being redeveloped by google. But here cooldevelopment said it isnt a google problem.
I fully understand that it must be annoying for you to see this question a million times but please understand, that it is also annoying (and unsatisfactory) to not know whats going on.
DeKiesel said:
How is this message supposed to be of any help? Of course we know that. We have seen a lot of threads. I have read the whole bug report including all the comments on googlegroups, I have browsed dozens of websites and googled my ass of. What I didnt find was an explanation (at this point I dont expect to find a fast solution anymore). After reading the googlegroups bug call I thought it was a problem with the bluetooth stack that apparently is being redeveloped by google. But here cooldevelopment said it isnt a google problem.
I fully understand that it must be annoying for you to see this question a million times but please understand, that it is also annoying (and unsatisfactory) to not know whats going on.
Click to expand...
Click to collapse
I know what you mean but i think the best method now is to wait until cooldev find a solution to this
As this is a bluetooth problem topic, i just want to ask one question. Can't use the CM 11 and ROM's based on it, because the sound problems with connection in my car. So back to stock ROM. I flashed the cooldev's kernel to get a better battery life, but after flashing, bluetooth makes the same problem as CM. Do you guys have the same issue?
kidmanis said:
As this is a bluetooth problem topic, i just want to ask one question. Can't use the CM 11 and ROM's based on it, because the sound problems with connection in my car. So back to stock ROM. I flashed the cooldev's kernel to get a better battery life, but after flashing, bluetooth makes the same problem as CM. Do you guys have the same issue?
Click to expand...
Click to collapse
Hmm, interesting. I will try this out as well. Might probably be a week though, I am leaving for holidays tonight and cant risk making my phone unusable. Maybe somebody else is willing to give it a try?
kidmanis said:
As this is a bluetooth problem topic, i just want to ask one question. Can't use the CM 11 and ROM's based on it, because the sound problems with connection in my car. So back to stock ROM. I flashed the cooldev's kernel to get a better battery life, but after flashing, bluetooth makes the same problem as CM. Do you guys have the same issue?
Click to expand...
Click to collapse
Thanks now i know where to search the problem.
Hi,
here is a logcat of a bluetooth connection during a call on stock rom/stock kernel.
What I did:
-start logcat
-start bluetooth
-chose a contact
-call contact-
-talk for a minute
-hang up
-stop logcat
I then wanted to flash the mosh kernel and do the same again but the last time I checked there wasnt this huge plethora of different kernels to choose from. Very impressive work!
Could you tell me which one you would like me to flash and I would then redo everything?
Hi,
I tried installing mosh kernel 1.8 and 1.85 (for stock, init.d enabled) on sazy rom but it didnt boot. It stayed at the very first screen you get when you turn the phone on. I then installed your cm11 build8, connected via bluetooth to my car and had someone call me.
Attached is the logcat.
Do I need the samsung stock rom for mosh kernel? I thought sazy rom was a stock rom?
Hi everyone,
this is my problem. I use almost always a very good quality headphones set (but without mic): obviously if I need to answer/make a call I have to talk into the phone's mic. Well, very often I'm not able to send my speech...I'm receiving very well, but the listener on the other side is not able to hear me, or at least he listen a very-very-very low sound. I did myself a test, calling me from an other mobile phone, and obviously I tried more than one headset.
I wrote "very often": actually, at the beginning after a reboot, this is not happening. It starts happening after a while, usually one hour after reboot: if you have a call, you are able to talk for 5 maybe 10 seconds, then there is the issue.
I thought it was a ROM bug (I was using Viper 3.1.4), then I tried Viper 5, then Elegancia, then Revelation...same problem... so I think it could be a kernel related bug ( @SebastianFM Kernel). Actually, no AOSP ROM has the same issue (Albinoman, Sultan, bilal, etc.).
Please, someone with these ROM can check if it is true?
Sorry for bumping it up. Anyone has experienced same issue? @SebastianFM, could it be ROM related issue, or I must search in a different place? Take in account that it happens only in ROM powered with your kernel...
pdbc said:
Hi everyone,
this is my problem. I use almost always a very good quality headphones set (but without mic): obviously if I need to answer/make a call I have to talk into the phone's mic. Well, very often I'm not able to send my speech...I'm receiving very well, but the listener on the other side is not able to hear me, or at least he listen a very-very-very low sound. I did myself a test, calling me from an other mobile phone, and obviously I tried more than one headset.
I wrote "very often": actually, at the beginning after a reboot, this is not happening. It starts happening after a while, usually one hour after reboot: if you have a call, you are able to talk for 5 maybe 10 seconds, then there is the issue.
I thought it was a ROM bug (I was using Viper 3.1.4), then I tried Viper 5, then Elegancia, then Revelation...same problem... so I think it could be a kernel related bug ( @SebastianFM Kernel). Actually, no AOSP ROM has the same issue (Albinoman, Sultan, bilal, etc.).
Please, someone with these ROM can check if it is true?
Click to expand...
Click to collapse
I've been experiencing a very frustrating issues where the mic is not working during phone call. I can hear the the other person but they cannot hear me, and if they can it's very very low, so low that they can't make out what I'm saying.
However, the microphone does work again if I go to speaker-phone mode. So i know the Mic itself is working (sound recorder works also).
I think somehow the phone thinks a headset is plugged in and disable the mic unless I'm on speaker-phone mode.
I don't think it is a ROM issues as I have tried a large number of different ROMS, including flashing stock OPO image. None worked.
If anyone know a solution to this issue please help me out. It's very frustrating that I can't make phone calls and have to turn on speaker-phone or use a headset.
Try a different Kernel, had the problem with my 3 different Headsets, i tryed the same ROM with some different Kernels and with the AK Kernel everything worked fine...not with the Furnace! Also try to flash UKM over a Custom Kernel. Check out the AK Kernel there you can find everything you need. If you have done everything right as in the "manual" open up Synapse...there is a point called "Sound", there you can find the point "Microphone", volume it up and try again. if its still not working make a full wipe that your device loses all data and reinstall the original CyanogenMod 11s with this tool here or any tool you want!
http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418
If its still not working delete again everything with the tool, install the CM11s with this tool again, install the CWM Recovery, flash the crDroid Rom (best ROM and everything works for me!), flash GAPPS, flash AK Kernel and last flash UKM!
This is my current setup and everything is working
ROM: http://forum.xda-developers.com/oneplus-one/development/rom-crdroid-v1-t2827599
Kernel: http://forum.xda-developers.com/oneplus-one/orig-development/kernel-ak-t2832168
Recovery: http://forum.xda-developers.com/showthread.php?t=2780894
UKM: http://forum.xda-developers.com/attachment.php?attachmentid=2913442&d=1409088319
Let me know if it worked
EasyGoingXD said:
Try a different Kernel, had the problem with my 3 different Headsets, i tryed the same ROM with some different Kernels and with the AK Kernel everything worked fine...not with the Furnace! Also try to flash UKM over a Custom Kernel. Check out the AK Kernel there you can find everything you need. If you have done everything right as in the "manual" open up Synapse...there is a point called "Sound", there you can find the point "Microphone", volume it up and try again. if its still not working make a full wipe that your device loses all data and reinstall the original CyanogenMod 11s with this tool here or any tool you want!
http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418
If its still not working delete again everything with the tool, install the CM11s with this tool again, install the CWM Recovery, flash the crDroid Rom (best ROM and everything works for me!), flash GAPPS, flash AK Kernel and last flash UKM!
This is my current setup and everything is working
ROM: http://forum.xda-developers.com/oneplus-one/development/rom-crdroid-v1-t2827599
Kernel: http://forum.xda-developers.com/oneplus-one/orig-development/kernel-ak-t2832168
Recovery: http://forum.xda-developers.com/showthread.php?t=2780894
UKM: http://forum.xda-developers.com/attachment.php?attachmentid=2913442&d=1409088319
Let me know if it worked
Click to expand...
Click to collapse
No luck here. : /
I've tried everything from flashing different ROMs to flashing different kernel. I even went back to factory reset, lock/unlock bootloader to wipe device. None of that work. Very frustrating. I'm starting to think it's a hardware issues, since trying out that many ROMs didn't help at all.
Did you informed oneplus already?
EasyGoingXD said:
Did you informed oneplus already?
Click to expand...
Click to collapse
Yep, filed a support/warranty request. But god knows how long it'll take for them to get back to me. There's no phone number support or anything. : /
neyurt said:
I've been experiencing a very frustrating issues where the mic is not working during phone call. I can hear the the other person but they cannot hear me, and if they can it's very very low, so low that they can't make out what I'm saying.
However, the microphone does work again if I go to speaker-phone mode. So i know the Mic itself is working (sound recorder works also).
I think somehow the phone thinks a headset is plugged in and disable the mic unless I'm on speaker-phone mode.
I don't think it is a ROM issues as I have tried a large number of different ROMS, including flashing stock OPO image. None worked.
If anyone know a solution to this issue please help me out. It's very frustrating that I can't make phone calls and have to turn on speaker-phone or use a headset.
Click to expand...
Click to collapse
Hi,
unfortunately I have the same problem. I've tried to fix it even modifying the system/etc/mixer_paths.xml but nothing works (http://forum.xda-developers.com/one...icrophone-ok-google-low-t2805568/post53914918). I noticed when that changing the values of hph-mic and anc-mic to 0, then handsfree mode doesn't work neither. Therefore we have clues to think the main mic is which has the problem.
Curiosly, I do not have had this issue out of the box, I think it began after 30O update. However I've downgraded to 25R and the issue remains.
I hope you the best luck
Regards
neyurt said:
I've been experiencing a very frustrating issues where the mic is not working during phone call. I can hear the the other person but they cannot hear me, and if they can it's very very low, so low that they can't make out what I'm saying.
However, the microphone does work again if I go to speaker-phone mode. So i know the Mic itself is working (sound recorder works also).
I think somehow the phone thinks a headset is plugged in and disable the mic unless I'm on speaker-phone mode.
I don't think it is a ROM issues as I have tried a large number of different ROMS, including flashing stock OPO image. None worked.
If anyone know a solution to this issue please help me out. It's very frustrating that I can't make phone calls and have to turn on speaker-phone or use a headset.
Click to expand...
Click to collapse
Cynogen 11s team is working to add support for CTIA headphones soon. See my post in similar thread (http://forum.xda-developers.com/showpost.php?p=55186894&postcount=25)
OK figured it out I uninstalled the latest hangouts update and made and received several calls all seems to be ok now
Is there any update regarding this issue? I still have this mic problem during calls and no clue on how to fix it.
OPO microphone problem is a hardware problem
Same problem here.
One morning main microphone in my OPO died - no one can hear me during call.
Recording sound with main mic gives some barely audible sounds.
tried reboot/factory defaults /root with fixing mixer paths - to no avail
The only solution is to call with speakerphone or bluetooth headset or normal headset.
Looks like hardware problem. Sadly OPO support sucks.
Jojo_1 said:
Same problem here.
One morning main microphone in my OPO died - no one can hear me during call.
Recording sound with main mic gives some barely audible sounds.
tried reboot/factory defaults /root with fixing mixer paths - to no avail
The only solution is to call with speakerphone or bluetooth headset or normal headset.
Looks like hardware problem. Sadly OPO support sucks.
Click to expand...
Click to collapse
I have a similar problem. Did you find a fix? I did everything. Restarted, ROM changed and everything!
As I wrote - no fix - IMHO it is a hardware fault. Still waiting for response from OPO support in hope for receiving RMA.
I am also thinking to return the phone because of this issue.
Just adding that I also have this problem - phone was working fine until yesterday.
Now mic is extremely quiet in call, unless I switch to speakerphone then it works fine (Video recording sound is fine also, but Google speech to text etc is not working)
I installed Swiftkey last night but I think its unrelated
Has anyone found any solutions for this problem yet?
Yes, I sold the phone!
:laugh:
L1ndon said:
Has anyone found any solutions for this problem yet?
Click to expand...
Click to collapse
I´ve opened a ticket. I advice to do the same.
- They will send you a link, with the ZIP-file in this link you have to reflash the rom. But probably it won´t work.
- Then tell them that it doesn´t work (of course only if it doesn´t work).
- Apply a RMA request
- Send them your ONE
- Receive an new one.
I´m waiting for the TNT courier, at the moment.
same problem here. No response from support. now recently even the emails to [email protected] are bouncing back with error, cannot deliver your email to the address.
So.. I'm having the same problem now..
I can't even submit a RMA, as I bought the phone from a person without the invite - so I have the receipt and everything, but when trying to submit the RMA, I have to select the order - Which I have none of, isn't that just wonderfull?
Did any of you find a solution?
I've had Samsung GS3 and GS4 with almost the same issues now and it is killing me, my will to keep living with these problems are close to none...
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?