Hi,
I didn't found any solution or working ROM/Kernel/Radio so maybe someone will point me to any direction except going back to 4.3
Like many users I have problems while listening music by my bluetooth headset. I have random disconnections while listening to audiobooks and calls. While listening to music it's usually random I can listen for 20-30 minutes nothing happens and sometimes it will disconnect after 5 and only reboot will fix the issue. Second problem is disconnect while calling. I have disconnections and reconnection's every 5 to 30 seconds. It's also random. Sometimes it works - usually it doesn't.
I'm using right now AOKP ROM but according to @aalvico post that problem exists also on Slim/PA/Purity and not on Omni and XeonHD.
Changing radio didn't solve issue. I tried AOKP/Franco/Hells Kernel. Same issue.
I started to experience this issue on KVT49L build.
So final question is - do any one knows 4.4/4.4.2 ROM that doesn't have this issue (meaning someone fixed it)?
I didn't had stock 4.4.2 yet, any one knows is the issue present there also?
This issue is so annoying that I would even go to stock to get rid of it.
Well, I'm using the nexus 5 port (KOT49H) with matrix 13.5 kernel and v4a and I never experienced problems like that, neither did I on previous builds.
Sent from my Nexus 4 using xda app-developers app
Oxious119 said:
Well, I'm using the nexus 5 port (KOT49H) with matrix 13.5 kernel and v4a and I never experienced problems like that, neither did I on previous builds.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thanks for reply. Could you give me more details what Rom you are using? I changed from AOKP 4.3 directly to 4.4.2 so I missed a lot nightly builds to catch this issue earlier. I don't really expect much of the rom except battery, I used AOKP ROM since second day I had my N4 so I don't really know how other roms/stock rom perform or what features I have in AOKP that I would not have in other (I needed ROM with quick pin unlock feature because of Exchange policy - now Xposed framework/mod did the job).
This issue is so annoying that I even considered selling N4 and buying something else.Then I thought first I need to try change the rom.
I have been terribly quiet for over 3 years and right now I can't even write in developer topics :/
Yes i had this some kind of similar bluetooth issue not with audio(actually didnt tried) but with bluetooth transfer from my pc to n4. the file got transfered successfully but my n4 hanged and restarted. Im using Purity rom with hellscore b45 stable kernel. This happened only once now the problem is solved on its own.
Related
A new problem has started for me and and a Google search has shown some other people have also mentioned in but no solutions have come up.
Since iv started using any Android 2. 3. 7 roms around 1once a day to once a couple of days answering a call causes phone app to freeze and the phone speaker makes a constant buzz sound that eventually stops. After the phone signal and 3g returns all is well but trying to make a call result in a full phone freeze wich needs a battery pull. Best thing I do now after this crash is reboot normally.
Also good thing is the call is not answered as far as the carrier is concerned so I can still follow up on the call with voicemail.
I'm considering I have to go back to an older nexushd2 Rom or some sense Rom wich usually has Android 2. 3. 5
Anyone know a way to fix it? Maybe flash an Android 2. 3. 6 apk or a modded libaudio ?
I had that happening to my old phone.... freezing, buzzing, battery pull.
It started happening after I overclocked the phone to 1.5ghz . And then just kept happening even when i stopped overclocking. The phone would be hot on the bottom. And sometimes wouldnt boot till it cooled off. All i can say is hopefully you have insurance bc if its anything like with mine it'll be happening more and more often with time. After 3 months of it, it was happening a couple times a day , till i got a replacement.
Visentinel said:
A new problem has started for me and and a Google search has shown some other people have also mentioned in but no solutions have come up.
Since iv started using any Android 2. 3. 7 roms around 1once a day to once a couple of days answering a call causes phone app to freeze and the phone speaker makes a constant buzz sound that eventually stops. After the phone signal and 3g returns all is well but trying to make a call result in a full phone freeze wich needs a battery pull. Best thing I do now after this crash is reboot normally.
Also good thing is the call is not answered as far as the carrier is concerned so I can still follow up on the call with voicemail.
I'm considering I have to go back to an older nexushd2 Rom or some sense Rom wich usually has Android 2. 3. 5
Anyone know a way to fix it? Maybe flash an Android 2. 3. 6 apk or a modded libaudio ?
Click to expand...
Click to collapse
This is related to the No Sound bug alright. What other apps do you have - SIP/ Viber/ any other VoIP? And do you use BT? There were a few post in the No Sound thread and Tytung's kernel thread few days back about what libaudio.so works fine for what kind of a usage.
Android 2.3.7 is just a coincidence, me thinks
ph03n!x said:
This is related to the No Sound bug alright. What other apps do you have - SIP/ Viber/ any other VoIP? And do you use BT? There were a few post in the No Sound thread and Tytung's kernel thread few days back about what libaudio.so works fine for what kind of a usage.
Android 2.3.7 is just a coincidence, me thinks
Click to expand...
Click to collapse
None of the above and I don't use Bluetooth.
Guess it ain't a coincidence. I wouldn't of posted if I thought it was part of the no sound bug.
Sent from my Nexus One using Tapatalk
I had a similar issue some time ago: for me the problem was the cpu/governor settings and i fix it with an appropriate SetCPU profile. Using another rom though.
Try to set an "in call" profile as the phone won'to go under 400 Mhz (roughly) and see if it happen again.
mi too
i using miu rom, HD2 NDT GINGER and recovery 3.0.2.4 with this i don have this problem. with any sense rom I have that problem
Sorry my bad english
Hi,
I noticed 2 issues in 4.2.2 :
With paranoid android 3.0 I can pair and connect my BT headphones but sounds become crazy after 20sec every time
-> apparently it's a known issue with ROM messing with 4.2.1 and 4.2.2
I tried also Xylon 2.1 with clean install from xylon 18 and now impossible to even turn the BT on.
Every time I try the button flicker and goes back to off
->Anyone have seen this?
Sent from my Nexus 7 using XDA Premium HD app
https://www.dropbox.com/s/g86bq2qj4vdagx9/4-2-2BluetooohFix.zip
Try that bud
Thx mate but same issue.
I also tried the new PA3.1 for tilapia and same problem.. Impossible to activate BT...
Sent from my Nexus 7 using XDA Premium HD app
Having the Same issues with My BT as well with my JVC in my car.. I have to reboot the nexus then its fine... but the bluetooth will turn off on its own.
I did notice that there is no BT issue when Wifi is off..
Same for me. N7 can't find and can't be found with my other device (One X). It's been asked in the original PA thread at least twice but no reply. I'll try ask again as this is my 10th post and I can finally post in developer section yay! :victory:
I´ve installed todays nightly I can´t enable my bluetooth too.
Hi everyone!
I'm getting an extrange touchscreen behavior in my Nexus 4, eventually a part of the screen stop registering touches, but from one time to another it becomes active again, or, when I lock and unlock, it starts working perfectly. I'm rooted on android 4.2.2 fresh and new install. But in a full charge cicle, that ocurred maybe 5 times whith 4,3 hrs of screen. Can't reproduce that behavior, it occurs randomly (I think). Sorry for my english, I'm from Argentina.
Thanks for your help.
My advice to you would be to try a different kernel and maybe even a different ROM.
The Franco.Kernel has a couple of entries that claim better handling with the touchscreen.
overhauling said:
My advice to you would be to try a different kernel and maybe even a different ROM.
The Franco.Kernel has a couple of entries that claim better handling with the touchscreen.
Click to expand...
Click to collapse
Hi, I'd tried sotck kernel, Harsh and now on Faux kernel whithout any difference. I'll give franco kernel a try, and commet later. I'm thinking on a hardware problem, but how could it be possible if it's not all the time?
I just try franko kernel With no luck same extrange touch screen behaviour.
anyone who could helpme?
Anyone who could help me with any idea?
If changing the kernel and ROM didn't help the issue, the problem is most likely hardware. You can try a few other kernels or ROMs, but you will most likely need an RMA
In, thanks. The problem is that I'm from argentina and can't even contact Google for nexus 4. I have one person in the us but he needs the address to take the nexus and I can't give it. The RMA is just by Mail? Anyone knows?
Thanks!
Now, I'm using it with android 4.2, and its working fine. Immediately when the firmware was installed it doesn't work but now I'm using it for about half hour without any problem? Could it be any disabled built in disabled app? Or any other issue related to android 4.2.2?
Sent from my Nexus 4 using xda app-developers app
Update: not working fine. Just intermittent. Anyone who deal With RMA can tell me is there's a place where I can send the phone in, cause in muy country there's no Google support.
new update: After about 1 and 1/2 week turned off, I strated up to re-flash stock rom 4.2.2 (I was on stock but to be safe decide to re-flash again) and lock bootloader, and now it's working and not making any kind of error, how could it be possible? I'm expecting the error, to tell to my reseller, and it's not happenning. But, is there any way to know if it will happen again? if Google recieve a supposed non-defective device, will they return it?
Final update: My reseller sent back to US, and they told me Google will replace my defective Nexus 4 with a new one. Hope get it back soon, and never have to view any problem on my nexus 4. Thanks for the answers and help.
Conclusion (at least for me): If you have problems with touch-screen (not the sensitivity) and no custom kernel/rom solve it, that's a hardware problem.
Please close thread.
Hi everyone,
I bought my nexus 4 about a year ago, and very recently I decided to give Cyanogenmod a try. I must say this was the first custom ROM I flashed on my device, and I'm quite fond of it. I also flashed a modified version of the latest franco.kernel for CM (http://forum.xda-developers.com/showpost.php?p=53707610&postcount=459)
The thing is that I noticed that my phone doesn't vibrate when it's supposed to. In fact, it doesn't vibrate at all; no matter what I try, it just doesn't. For the record, it had been working flawlessly until a few days ago.
So far I've tried:
- Disabling/Enabling vibration in keyboard, notifications and calls
- Rebooting my device several times
- Updating to 20140723 nightly (I was previously on M8)
- Disabling quiet hours
I've been doing some reading, and some old threads advise to perform a factory reset, but it's kind of a hassle for me to re-sync all the photos and stuff. So, is there anything I should try before I do a factory reset? Should I try and flash a different kernel/go back to stock kernel?
Thanks
It's most likely a hardware issue. I'd backup the phone and then flash the factory image. If it still doesn't vibrate it's a hardware issue. It doesn't cost much to replace the vibrator. Do it yourself or find a local cell repair shop.
Sent from my Nexus 5 using XDA Free mobile app
I would rather change the kernel first and see if there is any issues.
I flashed the latest CM nightly, which also changes the kernel to CM stock. This time you can hear the little buzz when you turn on the phone, but that's pretty much all the vibration I get. Phone calls and haptic feedback still don't work. At least, I know it's not a hardware issue.
ant_cc said:
I flashed the latest CM nightly, which also changes the kernel to CM stock. This time you can hear the little buzz when you turn on the phone, but that's pretty much all the vibration I get. Phone calls and haptic feedback still don't work. At least, I know it's not a hardware issue.
Click to expand...
Click to collapse
I still think it's hardware. Roms can change the force it vibrates at. But if it's still low the vibrator is bad.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I still think it's hardware. Roms can change the force it vibrates at. But if it's still low the vibrator is bad.
Click to expand...
Click to collapse
Maybe I wasn't very clear; the vibration force is OK, but the thing it that it only vibrates on startup, it doesn't buzz in incoming calls or any of that. So that's why I think the vibrator isn't broken
Hi, Okay so I am having a problem with the Nexus 4 microphone. It's not working for the following;
Calls
Voice Search
Video capture
Pretty much everything a mic is used for really...
The problem started persisting I believe back in 4.3 or possibly just after the 4.4 update, not entirely clear.
I have found a rather irritating fix for the problem, it's a silly fix but it's a fix nonetheless....as strange as it is if I plug in the usb data cable the mic works. Strange yes? If I plug in the usb cable and then unplug it the mic works for a little bit and then goes dead again. Even stranger yes?
Since the problem has occurred I have I have been running customs ROMS and Kernels, predominantly for the 4.4.4 update and nothing really less. The problem is still persistent, hasn't gotten worse in anyway...just persistent. Keep in mind I hadn't put anything custom on my phone until after the problem occurred.
So obviously this states that I have done factory resets, formats, flashes etc...
Currently running the latest Dirty Unicorn ROM with the PAGAAPS.
I have read a lot on the google product forums and some other threads around the place with others having practically the same issues. There is a lot of varying conclusions between it being a hardware or software issue with no real resolution though. Some have dissembled their phone and changed the mic and what ever other hardware they found necessary to change or try and fix....to also find that it hasn't fixed their problem.
Here is a link to one thread with everyone having the same issue, everything on there I have tried apart from doing open surgery on my phone.
Nexus 4 microphone not working Google product forum
So if this is a software issue for some phones, the problem could be solved in the upcoming update to Lollipop 5.0 which could be potentially awesome for me.
....if no resolutions happens from that, well then I'm stuck with what is causing the issue.
In conclusion notes; and in case the 5.0 update doesn't fix the issue, and in knowing that my small fix can be resolved with the data cable plugged in. Is there another fix I could try, with an app, rooted app, or with an Xposed module that anyone knows of that I could at least try? Any help in this direction would be much appreciated.
Best Regards,
Loopy
Loopy Frog said:
Hi, Okay so I am having a problem with the Nexus 4 microphone. It's not working for the following;
Calls
Voice Search
Video capture
Pretty much everything a mic is used for really...
The problem started persisting I believe back in 4.3 or possibly just after the 4.4 update, not entirely clear.
I have found a rather irritating fix for the problem, it's a silly fix but it's a fix nonetheless....as strange as it is if I plug in the usb data cable the mic works. Strange yes? If I plug in the usb cable and then unplug it the mic works for a little bit and then goes dead again. Even stranger yes?
Since the problem has occurred I have I have been running customs ROMS and Kernels, predominantly for the 4.4.4 update and nothing really less. The problem is still persistent, hasn't gotten worse in anyway...just persistent. Keep in mind I hadn't put anything custom on my phone until after the problem occurred.
So obviously this states that I have done factory resets, formats, flashes etc...
Currently running the latest Dirty Unicorn ROM with the PAGAAPS.
I have read a lot on the google product forums and some other threads around the place with others having practically the same issues. There is a lot of varying conclusions between it being a hardware or software issue with no real resolution though. Some have dissembled their phone and changed the mic and what ever other hardware they found necessary to change or try and fix....to also find that it hasn't fixed their problem.
Here is a link to one thread with everyone having the same issue, everything on there I have tried apart from doing open surgery on my phone.
Nexus 4 microphone not working Google product forum
So if this is a software issue for some phones, the problem could be solved in the upcoming update to Lollipop 5.0 which could be potentially awesome for me.
....if no resolutions happens from that, well then I'm stuck with what is causing the issue.
In conclusion notes; and in case the 5.0 update doesn't fix the issue, and in knowing that my small fix can be resolved with the data cable plugged in. Is there another fix I could try, with an app, rooted app, or with an Xposed module that anyone knows of that I could at least try? Any help in this direction would be much appreciated.
Best Regards,
Loopy
Click to expand...
Click to collapse
My N4 had a broken mic out of the box brand new lol. It was the latest batch, made in October 2013
I fixed it by getting a new mic because i diagnosed it wasn't a software issue
I ended up flashing "LRX08 B15.5S" from [L][5.0] Android L-pv N4 [B15.1 updated 10-27-2014] and I also put the "91u-a9: AOSP/L" Kernel from [KERNEL] [4.4.4/CM/(L)] [Bleeding Edge] Unleashed Kernel Series [91u-a9] [10/28/2014] Thinking there might be a chance it would fix my problem bringing it to 5.0 instead of 4.4.4.
I thought it worked all day yesterday without the data cable needing to be plugged in, I ran tests all day and it worked fine. Today is a different story though. I guess the data cable creates some form of initial connection the phone needs for my mic to work, and leaving it long enough it looses that connectivity. I'm not sure.
I don't have any intentions sending the phone in to get fixed, or repaired, as I'll be upgrading my nexus soon enough. I guess at this stage my fix is too cut the very end off of an old cable and have it in my pocket for incoming and outgoing calls. Anyone else have another solution?
Best Regards.
Loopy
Flash stock firmware... Don't flash custom firmwares without running a thorough check
Sent from my Nexus 4 using XDA Free mobile app
arkangel72 said:
Flash stock firmware... Don't flash custom firmwares without running a thorough check
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
I believe that's what I did in the very very beginning of the problem, however on the possibly note that I didn't I'll do that just before Nov 3rd, if the official L is update is available then. Thanks ark
Yup...
Sent from my Nexus 4 using XDA Free mobile app
arkangel72 said:
Flash stock firmware... Don't flash custom firmwares without running a thorough check
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
flashed stock. Problem still persists.