Related
I am having two problems
1st, when i am on the phone using speaker, sometimes people can no longer hear me (I can still hear them. It mostly happens when i open up different apps and also when i have a call waiting. This only hapens on speaker mode.
2nd probem is, I cannot send or recieve MultiMedia mesages. I can send/recieve reagular text just fine but no pic/video messages at all.
Info:
Tmobile Touch Pro 2
Energy Rom
Manil version 2.5.20121225.0CFC
Rom Version 16.May.2010 WWE
have you tried the may 22 NRG rom yet to see if that fixes your issues?
no i havent tried it yet. I was hoping it was just some kind of setting that i can change that will make it work.
dweezy108 said:
no i havent tried it yet. I was hoping it was just some kind of setting that i can change that will make it work.
Click to expand...
Click to collapse
Your best bet is to either ask in his rom thread or ask NRG over twitter.
Ive asked in his thread and ive got no response. Another person also stated how they are having the exact same problem. Maybe the answer will come soon enough.
You need to ask in the Energy thread though, even if you're not getting an answer there (which I understand must be frustrating). If everyone started a new thread when they didn't get an answer in the relevant thread, then ...
hey folks,
I have been following all the Milestone development threads since the very beginning, and have gone through each inkarnation of kabaldans incredible work since CM6. Recently, I updated to CM10 (first without, now with 2nd boot) and am absolutely amazed by how far our good old milestone has come. While playing around with it quite a bit, I have come across some problems (I would love to report them in the appropriate development thread, but the 10-post-count won't let me unfortunately.)
First, I really loved the keyboard multipress-system since I live in Germany and have to enter Umlauts very frequently (ä, ö, ü, etc.). The multipress-system sped that up greatly. Now, although the corresponding settings are there in the Milestone-specific part of the Settings-app, multipressing actually doesn't work for me in CM10. Is that problem specific to me, or is multipress not yet fully integrated in CM10?
The second thing I noticed (probably since 2nd boot, but I am not entirely sure) is, that in the Settings under About Phone > Status neither IME nor Serial number are displayed (instead, it says "unknown"). This also prevents me from launching Whats App - it quits saying "Your phone could not be identified ....".
Does anyone else experience those issues - and/or could perhaps somebody please post this into the CM10 development thread, so kabaldan notices?
thanks, mvol
mvol said:
hey folks,
I have been following all the Milestone development threads since the very beginning, and have gone through each inkarnation of kabaldans incredible work since CM6. Recently, I updated to CM10 (first without, now with 2nd boot) and am absolutely amazed by how far our good old milestone has come. While playing around with it quite a bit, I have come across some problems (I would love to report them in the appropriate development thread, but the 10-post-count won't let me unfortunately.)
First, I really loved the keyboard multipress-system since I live in Germany and have to enter Umlauts very frequently (ä, ö, ü, etc.). The multipress-system sped that up greatly. Now, although the corresponding settings are there in the Milestone-specific part of the Settings-app, multipressing actually doesn't work for me in CM10. Is that problem specific to me, or is multipress not yet fully integrated in CM10?
The second thing I noticed (probably since 2nd boot, but I am not entirely sure) is, that in the Settings under About Phone > Status neither IME nor Serial number are displayed (instead, it says "unknown"). This also prevents me from launching Whats App - it quits saying "Your phone could not be identified ....".
Does anyone else experience those issues - and/or could perhaps somebody please post this into the CM10 development thread, so kabaldan notices?
thanks, mvol
Click to expand...
Click to collapse
I have issue like this, and I can see IMEI and IMEI SV, but the Serial Number is "unknown".
after doing a full wipe, IMEI now shows up for me as well, but unknown serial and multipress problems remain.
mvol said:
hey folks,
(I would love to report them in the appropriate development thread, but the 10-post-count won't let me unfortunately.)
Click to expand...
Click to collapse
You are almost at the 10th post.
Maybe wiping everything is a solution for that?
mvol said:
hey folks,
I have been following all the Milestone development threads since the very beginning, and have gone through each inkarnation of kabaldans incredible work since CM6. Recently, I updated to CM10 (first without, now with 2nd boot) and am absolutely amazed by how far our good old milestone has come. While playing around with it quite a bit, I have come across some problems (I would love to report them in the appropriate development thread, but the 10-post-count won't let me unfortunately.)
First, I really loved the keyboard multipress-system since I live in Germany and have to enter Umlauts very frequently (ä, ö, ü, etc.). The multipress-system sped that up greatly. Now, although the corresponding settings are there in the Milestone-specific part of the Settings-app, multipressing actually doesn't work for me in CM10. Is that problem specific to me, or is multipress not yet fully integrated in CM10?
The second thing I noticed (probably since 2nd boot, but I am not entirely sure) is, that in the Settings under About Phone > Status neither IME nor Serial number are displayed (instead, it says "unknown"). This also prevents me from launching Whats App - it quits saying "Your phone could not be identified ....".
Does anyone else experience those issues - and/or could perhaps somebody please post this into the CM10 development thread, so kabaldan notices?
thanks, mvol
Click to expand...
Click to collapse
Hi mvol,
I am running the new CN10 10/24, the seril reports also Unkown but it doesnt stop me from running and using WhatsApp app.
regards
EP
WhatsApp now works - it looks like the full wipe which solved the unknown IMEI problem also fixed WhatsApp.
mvol said:
WhatsApp now works - it looks like the full wipe which solved the unknown IMEI problem also fixed WhatsApp.
Click to expand...
Click to collapse
Realy ? I will have a try !
I also went through this and really soh after giving a factory reset was decided that in fact
have you guys tried multipress using the hardware keyboard? Does it work for you?
mvol said:
have you guys tried multipress using the hardware keyboard? Does it work for you?
Click to expand...
Click to collapse
here using the shift and alt is working normally above 2 keys simultaneous ... not tested on that specifically, you will use more than 2 simultaneous keys?
with "multipress" I mean the feature invented by nadlabak/kabaldan that allows one to press the same key multiple times very quickly to enter special characters (like pressing "a" two times very fast producing "ä", for example.) It worked perfectly for me in CM7, but it doesn't anymore in CM10...
anyone, please?
It works fine for me. I use it frequently.
mvol: I still haven't found the time to implement the multipress feature completely in CM10. Only a few of the final bits is missing. Please be patient.
thanks for your answer - in that case, I'll wait patiently
Link not working for me
Hi All,
Im unable to access the latest builds for milestone CM10 by kabaldan. Please can anybody provide alternate link?
Thanks
Hello people!
I'm a long time CM ( 6 and 7 ) user on my Milestone.
After updating it to CM10 ( full wipe, ext3 partition formatted ), adb does not find my device anymore.
I have changed the USB settings and enabled the debugger in development, but nothing changes. Even after a restart.
Running on Ubuntu 12.10.
Any ideas?
Thanks!
The issue I have is quite annoying, if I can use such a word in a development stage . After each restart, the network is being forgotten, so I have to switch to the airplane mod off and on.
@pt0: This is a known issue, if I can say that. I experience this too, though not after every restart. I think it's a problem we can live with.
Hi there,
I believe I'm not the only one who tried to connect a bluetooth keyboard to the moto x. After a lot of research I found that it is just as easy as connecting a bluetooth device. The problem is that the Apple Keyboard doesn't work.
(since it is my first time, xda doesn't allow me to put images, so here are the links
imgur. com/v0Py8CR,5uCefZo
imgur. com/v0Py8CR,5uCefZo#1
Here you can see that the keyboard is seen by the phone, and I can pair it by typing the numbers on the keyboard. But after it is paired, and even though it is checked as input device I get no answer from the keyboard when I try to type.
I'd be really happy if anyone had a solution for this.
this is my first time posting here, so I hope that I am posting in the right section.
alexluz said:
after it is paired, and even though it is checked as input device I get no answer from the keyboard when I try to type.
Click to expand...
Click to collapse
Ooh it looks like you might have walked into a hornet's nest, a touchy issue that has been around a while and is yet to be resolved. See here: https://code.google.com/p/android/issues/detail?id=58202 and here: http://code.google.com/p/android/issues/detail?id=62740 and here: http://android.stackexchange.com/qu...ple-bluetooth-keyboard-paired-but-not-working
Be sure to search for a better solution, and I hope someone else can shed some light on the issue, but I see only these options currently:
1) wait for Android 5.0 Lollipop, it might fix the issue. Shouldn't be too long a wait either.
2) if you have root or you can root, you can try using this app, no idea if it does anything: https://play.google.com/store/apps/details?id=com.heightdev.ganhou&hl=en
3) the answer presented in the stackexchange link i mentioned above. unfortunately the solution there is getting a different version Apple keyboard hardware.
good luck.
dtg7 said:
Be sure to search for a better solution, and I hope someone else can shed some light on the issue, but I see only these options currently:
1) wait for Android 5.0 Lollipop, it might fix the issue. Shouldn't be too long a wait either.
2) if you have root or you can root, you can try using this app, no idea if it does anything:
3) the answer presented in the stackexchange link i mentioned above. unfortunately the solution there is getting a different version Apple keyboard hardware.
good luck.
Click to expand...
Click to collapse
Yes, I saw that and it made me really sad. I tried here already knowing about that with hope that someone had a solution.
But thank you anyway.
TLDR: only the 2011 Apple Wireless Keyboard has this problem, and without a solution (until now).
Hi all, I'm certain this info can be found in tons of places on this forum, but I'm brand-new (first post, woo!) and that amount of info here is a little overwhelming.
So, first thing's first: Pumpkin's forum is crap, the one moderator there either doesn't allow posts about android upgrades or flatly denies it isn't possible (I know they're lying).
I have a Pumpkin RQ0248, using an RK3188 cpu and still running Android 4.4.4. I've learned here that it's also known as "MTCB-KLD6-v2.85". It seems like my car radio CAN be upgraded to Android 5.1 (which is awesome), but I'd just like to check some facts with the experienced folks here:
- I download an "Update.img" file to a... microSD card? USB? (Does it even matter? Pumpkin's site says microSD in the maps slot).
- I run the System update button (or whatever it's called) and select the above image file. Let it do it's thing. It'll reboot, at which point I do a factory setting reset? I believe so.
- The file I've downloaded is "KLD_LP_rk3188_p_2016_05_11", I think it's the right one, but I want to be certain. Perhaps there's an even newer one?
- While poking around (and getting confused) I saw some people claim their radio app sometimes would stop working? Is that a regular thing? I know how to enter the "factory" settings (using PW 126) and saw that some people just had to change their radio chip version? Is that trial and error or is there a specific one I should use for mine?
Thanks for all the help in advance! And sorry for the newbie questions!
Anyone? Please lend a hand... I'm very nervous about flashing (and possibly bricking) my car radio...
cmetaphor said:
Anyone? Please lend a hand... I'm very nervous about flashing (and possibly bricking) my car radio...
Click to expand...
Click to collapse
You need to take pictures of the pages in factory settings for later use. e.g radio and other settings.
What you have given so far concerning MCU it should be possible to upgrade. Don't touch MCU, only
ROM needs to be upgraded.
Also be sure you can get in to recovery. Important is also the screen size 800 or 1024. You have to pick the right one. If you don't
know go to play store and install an app that tells your screen size. It doesn't matter in which SD-slot you're upgrading from.
Normally we use the GPS-slot (left one).
halloj said:
You need to take pictures of the pages in factory settings for later use. e.g radio and other settings.
What you have given so far concerning MCU it should be possible to upgrade. Don't touch MCU, only
ROM needs to be upgraded.
Also be sure you can get in to recovery. Important is also the screen size 800 or 1024. You have to pick the right one. If you don't
know go to play store and install an app that tells your screen size. It doesn't matter in which SD-slot you're upgrading from.
Normally we use the GPS-slot (left one).
Click to expand...
Click to collapse
ROM? I thought MCU was the important part that needed to be "flashed".
Can't post links to photos... not enough posts yet... Just tell me other info is required beyond what I posted originally?
I know my screen size is 480x800. Recovery mode, I don't know right now how to get enter it, but I know it exists (button combination held when booting).
Was the file I mentioned in my first post not the correct one to use?
The "official" response from the Pumpkin trash "tech" is that there is no real upgrade for my unit, but he provided a link for me to try it (aka removing any responsibility for bricking the radio). So full of crap, I've already seen RQ0248's being sold online with Android 5.1
If you haven't figured this out yet...here you go. I believe you and I have exactly the same unit. I actually read your thread with Jammy and his responses. HAHA. He isn't much help. I actually flashed what he provided to you and it booted, but the resolution was all off. I think that was for a 800X480 unit.
Pretty simple:
Download the latest V2.97 MCU image file for KLD6: http://forum.xda-developers.com/showthread.php?t=3246386
and download the latest Malaysk Rom: http://forum.xda-developers.com/showpost.php?p=69366390&postcount=860
I just put them both onto a USB flash drive, booted into recovery, and flashed them. After flashing I wiped data again and flashed them again, and wiped data one more time. First boot can take some time, but it's working flawlessly now.
dmband64 said:
If you haven't figured this out yet...here you go. I believe you and I have exactly the same unit. I actually read your thread with Jammy and his responses. HAHA. He isn't much help. I actually flashed what he provided to you and it booted, but the resolution was all off. I think that was for a 800X480 unit.
Pretty simple:
Download the latest V2.97 MCU image file for KLD6: http://forum.xda-developers.com/showthread.php?t=3246386
and download the latest Malaysk Rom: http://forum.xda-developers.com/showpost.php?p=69366390&postcount=860
I just put them both onto a USB flash drive, booted into recovery, and flashed them. After flashing I wiped data again and flashed them again, and wiped data one more time. First boot can take some time, but it's working flawlessly now.
Click to expand...
Click to collapse
Yeah, don't get me started with that forum over there... I shiver in disdain with my entire experience there.
TBH, Im like 99% certain my radio is 800x480 (we ARE talking about the RQ0248 right?). I'm still running the v2.91 MCU with the stock image "that person" gave me. And at very least, most of my issues with the radio have improved since doing so: My FM radio reception seems a little clearer, and the Bluetooth audio quality (streaming from spotify on my phone) is also quite a bit better.
That being said, everything about the 5.1.1 OS i'm running is HIDEOUS. The home screen and radio app particularly are just so ugly, aesthetically-speaking. I wasn't about to push my luck on the other forum though: it was hard enough to get an official response to fix my software bugs in the first place.
So, question time!
1) What does MCU v2.96 offer vs v2.91?
2) What does the Malaysk ROM offer vs the stock 5.1.1?
3) Does the Malaysk offer different skins? Customization?
4) Is there some way to improve the functionality of the built-in radio/music apps? (ex: no ID3 tags from MP3s... I'm pretty sure my MP3 player from 2002 has ID3 tags, this radio does not).
Thanks for answering! I had almost given up hope for this forum, it seems very popular in some areas, but this section seems to have much less in the way of activity.
Looking forward to hearing back!
cmetaphor said:
Yeah, don't get me started with that forum over there... I shiver in disdain with my entire experience there.
TBH, Im like 99% certain my radio is 800x480 (we ARE talking about the RQ0248 right?). I'm still running the v2.91 MCU with the stock image "that person" gave me. And at very least, most of my issues with the radio have improved since doing so: My FM radio reception seems a little clearer, and the Bluetooth audio quality (streaming from spotify on my phone) is also quite a bit better.
That being said, everything about the 5.1.1 OS i'm running is HIDEOUS. The home screen and radio app particularly are just so ugly, aesthetically-speaking. I wasn't about to push my luck on the other forum though: it was hard enough to get an official response to fix my software bugs in the first place.
So, question time!
1) What does MCU v2.96 offer vs v2.91?
2) What does the Malaysk ROM offer vs the stock 5.1.1?
3) Does the Malaysk offer different skins? Customization?
4) Is there some way to improve the functionality of the built-in radio/music apps? (ex: no ID3 tags from MP3s... I'm pretty sure my MP3 player from 2002 has ID3 tags, this radio does not).
Thanks for answering! I had almost given up hope for this forum, it seems very popular in some areas, but this section seems to have much less in the way of activity.
Looking forward to hearing back!
Click to expand...
Click to collapse
I'm not sure what the benefit is of the 2.96, but it's newer so it must be better! That was just the latest so that's what I used. THere are a ton of benefits so you should read the thread....but here are a few: Malaysk offers quite a few optimizations, built in root, customization including skinned apps and radios, and MOST importantly in my opinion is the FUSE support...which means the full 16gb of system space are available to use for apps. You won't run out of space again. Yes there are other music apps included in his ROM as well, but I haven't used them much so I can't really speak to their functionality...but I'm sure it's better than the stock app.
But, do the new music apps work with the steering wheel controls?
That pumpkin forum is ridiculous lol yes im after a factory looking stable rom with fuse the origional firmware that came with the 2.85 mcu worked flawlessly but it double booted so i tried custom firmware when he sent me the original firmware again, it wasnt the same it didnt even boot properly with 2.85 i had to update the mcu to 2.91 for the firware to even become useable
cmetaphor said:
But, do the new music apps work with the steering wheel controls?
Click to expand...
Click to collapse
Can I get an answer to this? The music app is terrible in terms of supporting things like ID3 tags and the like.
Don't even get me started on the 5.1.1 radio app, never seen something so hideous.
So I really want to know if there are alternative apps out there, or at very least better skins, for the garbage apps that Pumpkin dishes out.
Side Note: How good is the android auto integration in these head units? I've never tried it myself.... But Android auto is quite pretty to look at, and I really wouldn't mind tethering my phone via USB cable to my car radio if it meant a better overall experience. That being said though, things like the steering wheel control absolutely MUST function with android auto tether/mirror link/whatever it's called too.
Thanks in advance for anyone that replies! It's unfortunate that so few people do reply here, and this forum has been far more helpful than any other I've used so far.
cmetaphor said:
Can I get an answer to this? The music app is terrible in terms of supporting things like ID3 tags and the like.
Don't even get me started on the 5.1.1 radio app, never seen something so hideous.
So I really want to know if there are alternative apps out there, or at very least better skins, for the garbage apps that Pumpkin dishes out.
Side Note: How good is the android auto integration in these head units? I've never tried it myself.... But Android auto is quite pretty to look at, and I really wouldn't mind tethering my phone via USB cable to my car radio if it meant a better overall experience. That being said though, things like the steering wheel control absolutely MUST function with android auto tether/mirror link/whatever it's called too.
Thanks in advance for anyone that replies! It's unfortunate that so few people do reply here, and this forum has been far more helpful than any other I've used so far.
Click to expand...
Click to collapse
Pumpkin is a seller only, there is no such thing as a "Pumpkin RQ0248", its a Klyde unit. I m guessing you havent bothered to read the wiki, if you did youd find a load more info and realise that that your unit is the same as any other Klyde unit no matter what it looks like on the outside or who you buy it from (Eonon, Pumpkin, Erisin ) and that its also so similar to any other MTCB or MTCC head unit made by the 10 odd manufacturers who produce these units, that it can use the same software as all of them.
I m also guessing that you dont read or look in the main threads in the 4 MTCB/C forums either, cos youd know all about the custom ROMs and modified apps that are available.
I m guessing neither did the OP or he wouldnt have opened the thread in the first place, we cant have a thread open for every made up model number by every seller of all 10 manufacturers, there would be literally 1000s of thread all with the same content. All the info for this unit is the same for any other MTCB/C unit.
cmetaphor said:
But, do the new music apps work with the steering wheel controls?
Click to expand...
Click to collapse
typos1 said:
Pumpkin is a seller only, there is no such thing as a "Pumpkin RQ0248", its a Klyde unit. I m guessing you haven t bothered to read the wiki, if you did youd find a load more info and realise that that your unit is the same as any other Klyde unit no matter what it looks like on the outside or who you buy it from (Eonon, Pumpkin, Erisin ) and that its also so similar to any other MTCB or MTCC head unit made by the 10 odd manufacturers who produce these units, that it can use the same software as all of them.
I m also guessing that you dont read or look in the main threads in the 4 MTCB/C forums either, cos youd know all about the custom ROMs and modified apps that are available.
Edit: Yay! This forum had an ignore button! Just learned that today too.
I m guessing neither did the OP or he wouldnt have opened the thread in the first place, we cant have a thread open for every made up model number by every seller of all 10 manufacturers, there would be literally 1000s of thread all with the same content. All the info for this unit is the same for any other MTCB/C unit.
Click to expand...
Click to collapse
Oh look everyone! I've found the @#$%.
Kind replies are far more helpful than sarcastic, snide, rude and jerk replies. Instead of replying next time, I'd prefer you not reply at all.
There are actual helpful people here that could explain these to me nicely, and have been doing so thus far. These forums are MASSIVE - I don't have the time to read for hours and possibly put myself on the Wrong track if I happen to miss some important details. Also, unless I somehow was able to magically learn what a Klyde radio is on my own, I had never heard of that detail before. Maybe a nice person could've explained it to me.
But kind isn't you. So please go away and allow the nice people to speak.
cmetaphor said:
Oh look everyone! I've found the @#$%.
Kind replies are far more helpful than sarcastic, snide, rude and jerk replies. Instead of replying next time, I'd prefer you not reply at all.
There are actual helpful people here that could explain these to me nicely, and have been doing so thus far. These forums are MASSIVE - I don't have the time to read for hours and possibly put myself on the Wrong track if I happen to miss some important details. Also, unless I somehow was able to magically learn what a Klyde radio is on my own, I had never heard of that detail before. Maybe a nice person could've explained it to me.
But kind isn't you. So please go away and allow the nice people to speak.
Click to expand...
Click to collapse
I didnt write anything that was unkind, snide, sarcastic rude or jerk, I simply gave you some information about where to look to avail yourself of some basic info about your headunit, I didnt have to, I wasnt paid for it, yet I did, in my book, thats "kind". What you require, it seems is someone to spend their time re-typing out whats already been written in other threads into this thread, because you cant be bothered to either look for it/read it yourself (known on xda as "spoon feeding").
It seems that you also havent bothered to read the post I just made properly either, because if you had, you would have seen me refer to "the wiki" (also linked to in the sticky in the very first post of this forum AND in my signature !) and would realise that you dont need any "magic" to learn what a "Klyde" is, you just need to read something mentioned TWICE on the screen in front of you !
In your previous post you also complained that "so few people reply here", if you read what I wrote in my reply, you ll realise why that is - theyve all read the basic info and are replying in threads that apply to ALL MTCB/C headunits.
On xda youre supposed to read stuff and find out for yourself and if you cant find the info you need or dont understand something or need help with something then there are loads of people (including me - look at my thanks meter) who will happily help you. But its clear that you havent read a thing, nothing, not one bit, not the sticky in the general section, not the Q&A section's first thread, not the wiki, nothing, diddly squat. So to help you in the way you want, I would have to write whats already been written and I aint doin that - you read at least the basics of it and ask questions if you dont understand something or cant find it.
Curtusz said:
That pumpkin forum is ridiculous lol yes im after a factory looking stable rom with fuse the origional firmware that came with the 2.85 mcu worked flawlessly but it double booted so i tried custom firmware when he sent me the original firmware again, it wasnt the same it didnt even boot properly with 2.85 i had to update the mcu to 2.91 for the firware to even become useable
Click to expand...
Click to collapse
Sounds like the ROM you were given was more up to date ROM - new features often have to be enabled by updating the MCU too, as that controls a lot of functions. Its also because you now have an MTCC MCU - 2.85 is MTCB, 2.91 is MTCC and older ROMs dont work with older MTCB MCUs.
Yup it is now a mtcc unit ... im actually using kld9 2.98 i think, i found now my new rom is also double booting after an app install , so its certain apps that cause double booting. Just outa interest what rom are you using? (if you have a kylde unit)
Curtusz said:
Yup it is now a mtcc unit ... im actually using kld9 2.98 i think, i found now my new rom is also double booting after an app install , so its certain apps that cause double booting. Just outa interest what rom are you using? (if you have a kylde unit)
Click to expand...
Click to collapse
I m using booroondook's ROM. When you say double booting do you mean it boots, shuts down then reboots ?
Basically boots up as it should , then after about 5 seconds boot logo appears then boots again doesnt shut/power down , it started after i downloaded an app called virtual dyno mobile, i will try the rom your using
Curtusz said:
Basically boots up as it should , then after about 5 seconds boot logo appears then boots again doesnt shut/power down , it started after i downloaded an app called virtual dyno mobile, i will try the rom your using
Click to expand...
Click to collapse
Thought so, not heard of that before, strange.
Yeah its common across the pumpkin forum. I dont know where they are getting their roms from but they are terrible.
Curtusz said:
Yeah its common across the pumpkin forum. I dont know where they are getting their roms from but they are terrible.
Click to expand...
Click to collapse
They get their ROMs from Klyde, the manufacturers of the units !
Hello everyone,
I'm having major issues with my Nexus 6 over the past 3 weeks or so.
I've had this phone for almost 2 full years now and love it, however, over the past 3 weeks the bluetooth function keeps turning off when I reboot my phone every night.
It NEVER did this in the past 2 years. Only the last 3 weeks. It seems to be some sort of battery saving feature, I would presume.
What drives me nuts, is I always like to have my bluetooth on, since I get in my truck and it auto connects to my GMC IntelliLink (which is also a problem).
So does anyone know why, all of a sudden, after reboot, bluetooth defaults to off and I have to manually turn it on every time? My Nexus 6 has been flawless up until now.
I've looked everywhere for an "auto start" option for bluetooth, but cannot find one. I have ZERO idea how this happened all of a sudden. I've been running the same ROM since last February with no problems (ROM screenshot attached).
As for my bluetooth truck problem, that started today. All of a sudden "phone audio" will not let me select the box, only "Media Audio" and "Contact Sharing" boxes are selected. Thus my Pandora plays over bluetooth, but my phone calls will not.
Also my Bose Quiet Comfort headphones used to connect perfectly with my Nexus 6, now I'm at work and I notice if I turn the headphones off, then come back and turn on, it'll say "connected to Nexus 6", but the sound is playing through the phone instead of the headphones, even though the bluetooth connection has been established.
Again, this is only over the last few weeks.
Any help would be greatly appreciated.
I'm willing to update to a new ROM or do a wipe, I just tend to live by the motto "if it ain't broke, don't fix it"........ except now it is broke and I want to fix it.
Thank you-
Paste a logcat here. A dev could take a look and help you out.
or
Backup your stuff and do a clean install of a new pure nexus or whatever rom, if it's still present after that, maybe it's just your battery starts to dying after 2 years.
Edit: I'm using crdroid as daily driver and have no bt issues
So glad you posted this, I'm having the same issue! After either a restart or just a period of time my Bluetooth turns to disabled. It is especially frustrating as I have it connected to my watch, which allows me to unlock with smart unlock. When the Bluetooth is disabled, I have to punch my pin in.
I am on stock 7.1.1, February update. I am rooted and flashed the Echo Permissions Fix. I was going to flash stock again this morning, but decided to check here first for a solution. I am just happy to know that it's not just me.
That being said, like @MVLJR, I recently flashed PureNexus ROM and that for me is when this began. I flashed back to stock via flashall, but it has not stopped the problem. Could it be a PureNexus thing?
As we have PureNexus somewhat in common, I am doing some searching on that page. I had previously posted there about it, but I don't think I ever got a response. Someone mentions it on Page 3417, I'll keep reading to see if I find a solution.
My post, by the way, is on page 3420.
I had a problem like this on Pure Nexus and flashed back to stock (N6F26R) to see if the problem goes away...
Previously on stock (release before N6F26R) and never had an issue. I use Bluetooth with a watch, fitness band and sometimes my Wife's Ford...
Sent from my Nexus 6 using Tapatalk
@muiriddin, did the problem go away for you? Because I flashed back to stock and the problem persists.
@MVLJR, I suspect that the problem is Android Wear 2.0 on our phones. Do you have a smart watch?
Edit: On the PureNexus forum, people without Android Wear are also experiencing it. So back to the drawing board. I still do not think it is your ROM.
Reading this thread reminded me of something I dealt with a while back, I don't know if this will do it for all of you, but I figured I'd post this. I screenshotted a reddit thread that fixed the problem for me. I can't remember if what I experienced was the same as all of you, and I am not having the problem now. But I hope this helps. Please see the attached screenshot.
I don't have an android watch, but I do have a fitbit and don't have any problems with it.
A little update, I cleared my Bluetooth cache and changed the name of my device, which seems to have helped.
My Bose headphones now autoconnect like before.
However, my Bluetooth still shuts off after reboot. My GMC Intellilink still won't let me select "Phone Audio" either.
I think I'm going to flash a new ROM this week, which sucks because I've grown attached to the Pure Nexus ROM.
Can someone show me how to post a logcat?
Thanks
This (and similar) bluetooth issues have been reported on the nougat product pages. It's not unique to PureNexus or the Nexus 6.
Reports are that 7.1.2 (beta) fixes the issue on devices that have access to it. Hopefully a fix comes down the pipe for the Nexus 6 as well, as I have some of the same issues.
Similar posts can be found on the nexus6 and googlepixel subreddit pages.
My question is, what prompted this?
I've had the same ROM for a year, no OTA updates. Had to be an app update, correct?
No other way to explain how it worked for a year, now problems all over the place
You've been using the same ROM, but updating the version of the ROM, correct?
And the ROM updates are based on updates made to Android by Google.
So if a bug makes it into Nougat, it will (generally) make it into the modified ROM as well.
Incorrect, I've been on the same version of Pure Nexus since last February, screen shot in original post
I take it the fix I posted didn't help? I was really hopeful that it was the same issue and that would fix it up.
I haven't tried it yet, at work right now, I'll give it a shot later.
I'll update my findings.
Thanks
Will keep my fingers crossed. One thing to note, when doing that fix, it *will* wipe your bluetooth auto-pair devices. So don't fret if nothing automatically connects afterwards. You have to repair everything.
It is not a new problem, there are many threads in the Q&A forum if you search. Here is one:
https://forum.xda-developers.com/nexus-6/help/bluetooth-off-reason-pattern-t3435436
(there are more links and suggested workarounds in that thread from me)
That said, installing the AW 2.0 DP 4 totally solved my BT disconnects from my Huawei watch and LG stereo headset.
The changelog on the latest Huawei AW 1.5 mentions BT issues, but I have not tried it.
AW 2.0 official is supposed to start rolling out OTA tomorrow, so we shall see. (finners crossed tite )
I'm on Jan 21 PN 7.1.1, latest AW app. I have no suggestions of those having issues with no Android Wear, but there are threads here with suggested workarounds that solved this for many of us before, you might want to check them.
@Morpherios and @MVLJR
I don't know if it's of any note, but one of the actions I attempted in trying to fix mine was to reset all network settings via the "More" option in Wireless & Networks settings (I backed up wifi settings in advance). That's essentially a nuking of all network settings, including wifi, cell, and bluetooth. It did not resolve my issue.
@Pkt_Lnt seems to be indicating that with updated AW on his watch, the disconnects are not happening. How the software on the watch (as opposed to the AW app on the phone) would be causing bluetooth to crash, I'm not sure. But it's not outside the realm of possibility.
larrysteeze said:
@Pkt_Lnt seems to be indicating that with updated AW on his watch, the disconnects are not happening.
Click to expand...
Click to collapse
My words were / are different than that:
AW 2.0 DP 4 totally solved my BT disconnects
That means they do NOT happen any more, since Dec 11, 2016 when I installed AW OS 2.0 DP4 was released and I installed it on my watch. Not. One. Disconnect. None. Nada. Zero. Zip. Zilch. Nein.. :victory:
BT devices communicate both directions. The watch CAN control the phone, and was turning off BT. It was obvious when it happened, when my headphones prompt "Out of Range, trying to connect" (I came to hate hate that voice prompt )
I would immediately open the AW app on the phone at disconnect and was prompted to turn on BT because it was off.
@Pkt_Lnt I completely agree that it BT communication is two-way...I stated that it's not outside the realm of possibility because there are a number of factors that could do it, including the phone receiving a message it simply doesn't know what to do with and causing a fault. This could explain my bluetooth share crash messages that I received on occasion.
It's encouraging to know that it's fixed with AW 2.0 for you. I hope it carries through to me when I get the update. If the OTA doesn't drop tomorrow, I may have to flash the DP as well.