Related
I have a KFHD 7" (2012 model), it's rooted, the latest TWRP is installed and I'm currently running Kinology. From time to time it seems to be unnecessarily freezing and overheating (this used to happen for a long time now, but it doesn't seem to affect its performance from what I've seen) and I'm thinking of trying something new since it's already acting up.
I am currently using the latest Kinology, after I updated it to the latest version the freezing seemed to reduce visibly, but I still want to change the ROM. I was between PAC-MAN (http://forum.pac-rom.com/Thread-4-4-PAC-man-For-the-Kindle-Fire-HD-7) and CM11 (http://forum.xda-developers.com/showthread.php?t=2543455).
I was going to go for PAC-MAN but I'm having some issues figuring out which the latest stable version is, since they say they have updated to 4.4 but in their downloads I can't find it in the folders with the stables. I've asked many times in their site and their thread about KFHD here in xda but I haven't received an answer yet. I could just go for CM but I have some questions about it...
So what I need the rom I'll choose to do is:
run the kindle reading app normally (I don't care about the carusel, I just want normal access to my mobi files
run games ok
not freeze for no reason (I mean, the main purpose of flashing something new is to make my tablet run faster not slower)
have the facebook messenger work properly (since I installed kinology, unless I have "chat heads" manually opened and left to run, I get no notifications about new messages)
have the wifi and bluetooth working
So I need people who have CM or PAC-MAN to tell me if either of these roms has these features. Oh, also, I've seen there's some feature they call "OTA". What is that? I think when I rooted my kindle I had to make sure to disable those so that it wouldn't get randomly updated and undo my root? If someone could explain that to me I'd be grateful!
Oh and one more thing. With custom roms such as those two, are amazon's apps installed and running in the background for no reason just like they do if you have the stock rom, or are they disabled/uninstalled...?
With custom roms there is no such thing as Amazon apps. I suggest CM because of its reputation and support. But PAC is not bad.
OTA is Over the Air upate. If you receive an OTA in a custom rom,there is no reason for you to lose root.
SafinWasi said:
With custom roms there is no such thing as Amazon apps. I suggest CM because of its reputation and support. But PAC is not bad.
OTA is Over the Air upate. If you receive an OTA in a custom rom,there is no reason for you to lose root.
Click to expand...
Click to collapse
Ok, so if I want some of Amazon's apps all I have to do is download them from the appstore, right? (So relieved, I only ever used the reading app). So if it PAC has OTA, even if I install an older version (like 3.2 that I've found with certainty), it can install the latest on its own without me messing any more with the 2nd bootloader? I was hoping to try PAC before CM and to use CM only if PAC presents more issues than I can handle...
YuriPan said:
Ok, so if I want some of Amazon's apps all I have to do is download them from the appstore, right? (So relieved, I only ever used the reading app). So if it PAC has OTA, even if I install an older version (like 3.2 that I've found with certainty), it can install the latest on its own without me messing any more with the 2nd bootloader? I was hoping to try PAC before CM and to use CM only if PAC presents more issues than I can handle...
Click to expand...
Click to collapse
I seriously recommend CM. Even if you get any issues,the CM team will fix it MUCH faster than PAC. As for the Amazon Apps,I don't think all of them will be on the Play Store. But the Kindle reading app will.(I used it before)
SafinWasi said:
I seriously recommend CM. Even if you get any issues,the CM team will fix it MUCH faster than PAC. As for the Amazon Apps,I don't think all of them will be on the Play Store. But the Kindle reading app will.(I used it before)
Click to expand...
Click to collapse
Hmmm, then I might try CM11 today. It's true that in PAC they probably don't update too often, they don't even seem to check if people make questions or have issues too often. I've asked about which version to download a bunch of times in many different threads that they've made, and it's been 3 weeks and I'm still waiting for an answer.
One last thing. Do most games run alright in CM or are there compatibly issues? Oh, and something more. Does the playstore see the device as a kindle or as something else?
YuriPan said:
Hmmm, then I might try CM11 today. It's true that in PAC they probably don't update too often, they don't even seem to check if people make questions or have issues too often. I've asked about which version to download a bunch of times in many different threads that they've made, and it's been 3 weeks and I'm still waiting for an answer.
One last thing. Do most games run alright in CM or are there compatibly issues? Oh, and something more. Does the playstore see the device as a kindle or as something else?
Click to expand...
Click to collapse
Yep. I enjoyed Riptide GP 2. And I don't know about the latest nightly,but Hashcode's last unofficial build had the build prop set to recognise the device as an Amazon Kindle Fire HD.
Thank you so much for asking all my annoying questions! I sat down last night and flashed CM, set up everything and so far it's running smoothly. I tried some of the games I used to play and they seem to be running alright as well. I'm having some issues with the kindle reading app though, I downloaded it and logged in but it says it can't sync now and to try again later. I will try again later and see if it gets fixed...
Short and sweet... I love and recomend CyanogenMod.I use it on my kindlefire 1, 2 and 3 and I hope to
have it on this 2nd gen HD I'm working on now. With CM the possibilities are endless and anyone can easily customize
the kindle into a lean mean tablet with ease.... Thank You CM Team!
I took the plunge last night after having many issues with my Kindle Fire HD 7 that had been rooted and had both Amazon OS and Android. It started acting crazy after the last OTA that I thought I had shut off. Anyway, I re-rooted it, installed twrp 2.7.0.0, and then flashed it with cm-11-20140414-UNOFFICIAL-tate. Everything went smoothly and seems to work great. It also seems much faster now. Once I got all my account stuff setup, I did an update that it showed as being a stable version. I am now running cm-11-20140609-SNAPSHOT-M7. All my kindle books load up and I can read them on the device or cloud and was also able to find almost all of the games that I had before on my Kindle. It just seems so much nicer and faster now!
greg2074 said:
I took the plunge last night after having many issues with my Kindle Fire HD 7 that had been rooted and had both Amazon OS and Android. It started acting crazy after the last OTA that I thought I had shut off. Anyway, I re-rooted it, installed twrp 2.7.0.0, and then flashed it with cm-11-20140414-UNOFFICIAL-tate. Everything went smoothly and seems to work great. It also seems much faster now. Once I got all my account stuff setup, I did an update that it showed as being a stable version. I am now running cm-11-20140609-SNAPSHOT-M7. All my kindle books load up and I can read them on the device or cloud and was also able to find almost all of the games that I had before on my Kindle. It just seems so much nicer and faster now!
Click to expand...
Click to collapse
I decided to try out CM as well. Installed the latest stable version and it is indeed running much faster! I've never seen the keyboard not lag and the websites taking so little to load, so I'm satisfied so far. The Kindle app doesn't seem to be working for me though... I logged in my amazon account normally and every time I try to download books I don't even see a list, it says it failed to synch. I'll probably go over to the CM thread and as them about it...
Sent from my Amazon Kindle Fire HD
I was able to download my books and sync initially, then when I went back I too was having sync issues. I downloaded Aptoide and it wanted to update some of my apps and the Kindle reader was one of them. After the update, it seems to be syncing and working.
greg2074 said:
I was able to download my books and sync initially, then when I went back I too was having sync issues. I downloaded Aptoide and it wanted to update some of my apps and the Kindle reader was one of them. After the update, it seems to be syncing and working.
Click to expand...
Click to collapse
So, wait Aptoide is an alternative app store, right? You're saying that if I update the kindle reader from there it might work properly right?
YuriPan said:
Thank you so much for asking all my annoying questions! I sat down last night and flashed CM, set up everything and so far it's running smoothly. I tried some of the games I used to play and they seem to be running alright as well. I'm having some issues with the kindle reading app though, I downloaded it and logged in but it says it can't sync now and to try again later. I will try again later and see if it gets fixed...
Click to expand...
Click to collapse
Hi! Make sure you have the latest cm11 update settings-about tablet-cyangenmod updates
if you do and it still doesn't work please contact me and ill be will to provide further asistance1
I have the latest stable update according to my tablet, I checked. I seem to have issues with the Kindle reading app (it either doesn't sync or if I try an older version it crashes as soon as it is launched of after logging in), and it seems like Google services keep crashing randomly (I think this is the 4th or 5th day I'm running Cm but it wasn't doing so for at least the first two days). It also doesn't auto rotate although I have screen rotation unlocked, it rotates only after putting the Kindle in sleep mode and unlocking it again. I dunno if all those are related or not, if you could help me I'd really be thankful. =)
Sent from my Amazon Kindle Fire HD
YuriPan said:
I have the latest stable update according to my tablet, I checked. I seem to have issues with the Kindle reading app (it either doesn't sync or if I try an older version it crashes as soon as it is launched of after logging in), and it seems like Google services keep crashing randomly (I think this is the 4th or 5th day I'm running Cm but it wasn't doing so for at least the first two days). It also doesn't auto rotate although I have screen rotation unlocked, it rotates only after putting the Kindle in sleep mode and unlocking it again. I dunno if all those are related or not, if you could help me I'd really be thankful. =)
Sent from my Amazon Kindle Fire HD
Click to expand...
Click to collapse
Wait. Is it the M7 Snapshot?
SafinWasi said:
Wait. Is it the M7 Snapshot?
Click to expand...
Click to collapse
What do you mean the M7 Snapshot? Is this related to the version I'm running? I'm sorry to say so but I need you to be a bit more analytic cause I'm pretty new to custom roms...
YuriPan said:
What do you mean the M7 Snapshot? Is this related to the version I'm running? I'm sorry to say so but I need you to be a bit more analytic cause I'm pretty new to custom roms...
Click to expand...
Click to collapse
M7 is a monthly update considered more stable than nighty. I think one of the monthly snapshots had some issues. That may be what he's refering too. I am using the nightly from 7-2 (think) and it's running great for the things I use it for.
If you want to see the Tate nightie with changelog and pick a download go here http://www.cmxlog.com/11/tate/
Go here if you want to pick a monthly or nightly to download http://download.cyanogenmod.org/?device=tate
The Las three numbers are the month followed by the date.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
YuriPan said:
What do you mean the M7 Snapshot? Is this related to the version I'm running? I'm sorry to say so but I need you to be a bit more analytic cause I'm pretty new to custom roms...
Click to expand...
Click to collapse
Just tell me the CyanogenMod version you're running now.
SafinWasi said:
Just tell me the CyanogenMod version you're running now.
Click to expand...
Click to collapse
11-20131126-UNOFFICIAL-tate
YuriPan said:
11-20131126-UNOFFICIAL-tate
Click to expand...
Click to collapse
Umm... You're running an unofficial version. Download an official nightly or snapshot from the CyanogenMod website.
Sent from my device running CyanogenMod 11
Today I installed a new Sync update in my 2011 Lincoln MKS, and when I tried to pair my Nexus 6 (running the AICP ROM), the phone (or was it the car?) asked (for the first time) if I wanted the car to read my messages. I replied Yes, and it caused the phone's Bluetooth share service to force close. I had to clean flash the ROM and gapps, delete the device from the car, and re-pair the phone and the car but tell it No do not read messages. Don't know why I got the FC or why I couldn't undo the damage. Don't know what Ford/Lincoln did to Sync, but beware.
@almahix,
My stock, rooted N6 (5.1) pairs without problems with my 2015 MKC. And yes, it reads SMS messages.
Don't know if the problem is your ROM or the Sync update.
cam30era said:
@almahix,
My stock, rooted N6 (5.1) pairs without problems with my 2015 MKC. And yes, it reads SMS messages.
Don't know if the problem is your ROM or the Sync update.
Click to expand...
Click to collapse
Interesting. I'll have to try it with stock.
Yeah let me know, now that I know there is an update I'd like to install it but want to make sure it works, if it ain't broke don't fix it.
ChristianJay said:
Yeah let me know, now that I know there is an update I'd like to install it but want to make sure it works, if it ain't broke don't fix it.
Click to expand...
Click to collapse
After extensive testing today, the problem was traced back to CM 12.1 and ROMs derived thereof. AOSP based ROMs and stock do not exhibit this anamoly. Sorry for the premature alarm.
almahix said:
After extensive testing today, the problem was traced back to CM 12.1 and ROMs derived thereof. AOSP based ROMs and stock do not exhibit this anamoly. Sorry for the premature alarm.
Click to expand...
Click to collapse
Not premature, and no reason to apologize. People need to know.
I went for it and no problems, I'm running stock though. Great much needed update.
Unbelievable.
almahix said:
Today I installed a new Sync update in my 2011 Lincoln MKS, and when I tried to pair my Nexus 6 (running the AICP ROM), the phone (or was it the car?) asked (for the first time) if I wanted the car to read my messages. I replied Yes, and it caused the phone's Bluetooth share service to force close. I had to clean flash the ROM and gapps, delete the device from the car, and re-pair the phone and the car but tell it No do not read messages. Don't know why I got the FC or why I couldn't undo the damage. Don't know what Ford/Lincoln did to Sync, but beware.
Click to expand...
Click to collapse
Man, no update for years and now this. Has of last week I tore out the sync system in my car because it was giving me problems with lollipop and text messages. I was not sure that Ford would ever update the system, it hadn't since 2012. I really thought they left us in the cold. Damn, wish they would communicate with their customers a little more and keep timely updates. Now I'm pissed but thanks for the heads up.
I only stumbled upon it by visiting the Lincoln owner's website. I had no problems with SYNC on any of my phones or Android versions with the original 2010 SYNC or the update, except the CM 12.1 issue I found.
Sent from my Nexus 6 running AICP 9.0
Not the same for me.
almahix said:
I only stumbled upon it by visiting the Lincoln owner's website. I had no problems with SYNC on any of my phones or Android versions with the original 2010 SYNC or the update, except the CM 12.1 issue I found.
Sent from my Nexus 6 running AICP 9.0
Click to expand...
Click to collapse
My only problem was with the sms text reader and responder program I was using. When I was streaming Pandora and a SMS would come in, the program would ask me if I wanted it read, when I responded yes, it would read the Sms. But after that when it would give up the feed back to whatever streaming service I was using I'l always get the error,
"Bluetooth sharing as stopped working. Have to reboot to have the phone function with my ole sync system.
For some reason, I cannot select ok and continue on my pioneer 4100 after I connect to USB. I'm using cm12 with note 4.
Are you running CM12.1 (5.1), i had to downgrade to CM12 (5.0.2).
diagdave said:
Are you running CM12.1 (5.1), i had to downgrade to CM12 (5.0.2).
Click to expand...
Click to collapse
Yes, so downgrading fix the problem.
Thanks 4 the response.
killa2009 said:
Yes, so downgrading fix the problem.
Thanks 4 the response.
Click to expand...
Click to collapse
Yep, the layout was screwed on 5.1. if you force your dpi on your phone to 120 it works - of course your phone then is almost useless. so downgrade was only option.
So when do think there will be a fix? Can I force phone dpi to 120 then change it back normal after I select the box?
I have the save problem but it is intermittent. On 5.02. Thanks for the info. I thought my micro bypass was bad.
For 12.1 you should be able to go back to a nightly around the 22nd and it'll work.
22nd's nightly on one plus still works but anything after I have the display issue.
Andy
akp982 said:
For 12.1 you should be able to go back to a nightly around the 22nd and it'll work.
22nd's nightly on one plus still works but anything after I have the display issue.
Andy
Click to expand...
Click to collapse
Same issue as discussed here I assume? Has to do with the roms built in DPI changing functionality (I THINK)...
s2kpdx said:
Same issue as discussed here I assume? Has to do with the roms built in DPI changing functionality (I THINK)...
Click to expand...
Click to collapse
Since I could not get the CM from before 5/22 from CM I went on a hunt today to find a rom that would work with my 4100nex, I found that Euphoria from 6/02 based on 5.1.1 works for me. I tried several other builds from different devs, I really wanted to be able to find a 5.1.x that worked and it appears I have. I was not able to get past the Don't Show me this again scrunched up screen / DPI issue. I still have a phone book issue that I had on CM 12, for some reason it will not show names in my call log, but at least I got back into Android Auto. Hope this helps someone.
The latest CM12.1 nightlies have been working great for me with Auto. All of the nightlies that I tested in the first three weeks of May did not work, but the end of May nightlies have worked great so far.
bmxchampga said:
The latest CM12.1 nightlies have been working great for me with Auto. All of the nightlies that I tested in the first three weeks of May did not work, but the end of May nightlies have worked great so far.
Click to expand...
Click to collapse
The end of May and early June nightlies were fine, but then it got broke again sometime after that. It's been a crazy roller-coaster ride trying to figure out which build of which ROM has the features that you want and actually works with Android Auto.
WisdomWolf said:
The end of May and early June nightlies were fine, but then it got broke again sometime after that. It's been a crazy roller-coaster ride trying to figure out which build of which ROM has the features that you want and actually works with Android Auto.
Click to expand...
Click to collapse
Yeah, I just updated to the latest nightly and it broke Auto for me again.
how is everyone finding old version of CM 12.1 nightly that they can revert to? I have Oneplus One and i'm trying to revert to 05/31/15 nightly in which others have said works with Android Auto. I'm getting a Hyundai Sonata and want to be able to use Android Auto with it! (excited)
arabcamel said:
how is everyone finding old version of CM 12.1 nightly that they can revert to? I have Oneplus One and i'm trying to revert to 05/31/15 nightly in which others have said works with Android Auto. I'm getting a Hyundai Sonata and want to be able to use Android Auto with it! (excited)
Click to expand...
Click to collapse
Some phones have a better selection of older releases than others: http://download.cyanogenmod.org/
Sometimes other releases are downloadable from elsewhere.
Sometimes people keep copies under /sdcard/cmupdater.
This was fixed again on 01/07/2015 - http://review.cyanogenmod.org/#/c/102100/
http://www.cmxlog.com/12.1/bacon/ is rather useful for keeping track.
Updated mine yesterday and Android auto is back normal
Awesome, I'll have to flash and try myself. Do you think this would also apply to other custom ROMs that are based off of the newest CM?
Sent from my A0001 using XDA Free mobile app
akp982 said:
This was fixed again on 01/07/2015 - http://review.cyanogenmod.org/#/c/102100/
Click to expand...
Click to collapse
Some insight posted there:
density: do not apply to virtual displays Check the incoming configuration density to ensure that it is the same as the device's default density before forcing preferred values. Only apply display metrics if the display is not a presentation.
Click to expand...
Click to collapse
I was able to work around this problem on my Xperia Z2 tablet w/ CM12.1 by lowering ro.sf.lcd.density in /system/build.prop from default 240 to 180.
But this is just a workaround for the REAL problem shown in the comment. It had the side effect of making icons on homescreen smaller.
The REAL problem is that Android Auto uses a virtual display/Presentation to make up the AA display. Some ROMs were applying physical screen DPI of the phone to the virtual display, instead of the AA specified parameters that should come from the headunit. For Pioneer HUs (or at least 4100NEX) the parameters are 800x480 with a reported DPI of 160.
akp982 said:
This was fixed again on 01/07/2015 - http://review.cyanogenmod.org/#/c/102100/
http://www.cmxlog.com/12.1/bacon/ is rather useful for keeping track.
Updated mine yesterday and Android auto is back normal
Click to expand...
Click to collapse
Flashed July 4th build of BlissPop and it works great now with Android Auto. I had to turn off ADB in the developer settings.
Clean install or dirty...ota
Hey guys, I had posted a while back saying that for some reason, after flashing the new build of Marshmallow to my Nexus 6, the load times for web pages and just about everything else seems to be a bit slower than usual. I had said at the end of the post that it was fixed, but now the problem is arising again. Is anyone noticing long load times with all apps that use internet? Web pages load slower, the Facebook app takes much longer to load pictures and posts, Skype took longer to login and show everyone's profile pics etc. Never had this problem before on lollipop!
EDIT: Also, when I switch between my 2.4Ghz and 5Ghz WiFi bands, it shows a push notification that says that this WiFi signal has no internet access, and then it connects just fine after a few more seconds. This is odd. Maybe just a buggy first run of Marshmallow?
Sent from my Nexus 6
H4X0R46 said:
Hey guys, I had posted a while back saying that for some reason, after flashing the new build of Marshmallow to my Nexus 6, the load times for web pages and just about everything else seems to be a bit slower than usual. I had said at the end of the post that it was fixed, but now the problem is arising again. Is anyone noticing long load times with all apps that use internet? Web pages load slower, the Facebook app takes much longer to load pictures and posts, Skype took longer to login and show everyone's profile pics etc. Never had this problem before on lollipop!
EDIT: Also, when I switch between my 2.4Ghz and 5Ghz WiFi bands, it shows a push notification that says that this WiFi signal has no internet access, and then it connects just fine after a few more seconds. This is odd. Maybe just a buggy first run of Marshmallow?
Sent from my Nexus 6
Click to expand...
Click to collapse
maybe an issue with your wifi? how is it when you use mobile data?
simms22 said:
maybe an issue with your wifi? how is it when you use mobile data?
Click to expand...
Click to collapse
It's not loading really at all, but that's also due to my LTE coverage being awful in my area, that's always been bad haha so no change there. My other devices in the house are working just fine on my network, the Nexus 6 however seems to load slower, and it's only now that I'm on Android 6.0! Is it working fine for you?
EDIT: Just an update here, hours later, it may be my internet connection, possibly. But I'm not 100% sure on that either. If nobody else is having this issue, it may just be. Like I said though, it seems to be working fine with my other devices!
EDIT 2: http://imgur.com/gallery/TGiCU55 This is a speed test I did on my phone, I have 30Mbps internet and that shows!
I'm having same issue. Dirty flash. Kinda wondering if a clean factory reset is in order.
no issues here....came from a clean flash, which is standard protocol.
M seems fast so far, but I did change my animations Scale from 1.00 to .50! The only website to load very slow is XDA... go figure!
edif30 said:
I'm having same issue. Dirty flash. Kinda wondering if a clean factory reset is in order.
Click to expand...
Click to collapse
It's weird no? Mine was a clean flash! Formated userdata and cleared cache! Still have this issue.
Sent from my Nexus 6
H4X0R46 said:
It's weird no? Mine was a clean flash! Formated userdata and cleared cache! Still have this issue.
Sent from my Nexus 6
Click to expand...
Click to collapse
Yup. I did same. I might try the lollipop radio. Idk...
XDA is always sloooooow, even on a fast PC.
I've seen several other people mention slow net speeds on M as well but I've not noticed it yet. The WiFi code of M caused issues awhile back on some previous builds of HellsCore kernel too. I dont know the specifics of it though.
LGtMgG2t said:
XDA is always sloooooow, even on a fast PC.
I've seen several other people mention slow net speeds on M as well but I've not noticed it yet. The WiFi code of M caused issues awhile back on some previous builds of HellsCore kernel too. I dont know the specifics of it though.
Click to expand...
Click to collapse
So there was a definite change in the radio for this build then. More than a subtle change. I wonder if it's just not perfect, I realize having a Nexus means getting the first run of all Android software, but I wonder if this is a bug in the build, or a radio that could use some work. But it does sometimes take longer to load things! I'm on very fast WiFi too!
Sent from my Nexus 6
I honestly don't know and would like to hear more specifics. I can tell you I've seen comments on this board the last couple fo days talking about massive WiFi battery drain as well.
I only know HellsCore adopted the newer M code for WiFi in his kernel and people were affected. He then had to create two builds of the kernel. One with newer WiFi code that didn't cause any issues for people and another build with the older WiFi code from L. Have you checked his G+ site?
LGtMgG2t said:
I honestly don't know and would like to hear more specifics. I can tell you I've seen comments on this board the last couple fo days talking about massive WiFi battery drain as well.
I only know HellsCore adopted the newer M code for WiFi in his kernel and people were affected. He then had to create two builds of the kernel. One with newer WiFi code that didn't cause any issues for people and another build with the older WiFi code from L. Have you checked his G+ site?
Click to expand...
Click to collapse
No I haven't! I'll check that out! So that leads me to believe that it was a change in the new radio! He had to change it to code used in L radio so that may be it! Thanks for the info! I'll look into that some more!
Is it possible to flash the lollipop radio to test? I'd think you could. But I'm not 100%.
edif30 said:
Is it possible to flash the lollipop radio to test? I'd think you could. But I'm not 100%.
Click to expand...
Click to collapse
Yes, radio is independent of rom...
galaxys said:
Yes, radio is independent of rom...
Click to expand...
Click to collapse
So you're saying if I flash the radio file from a 5.1.1 stock image, marshmallow will boot and work correctly? I might try that!
Sent from my Nexus 6
Hey guys! An update here, I just read through another post that was about this same issue, and someone in there said that downloading DNset from the play store fixes this issue! It changes your WiFi settings from ipv4/ipv6 to just ipv4. I did it and it's working so far, but I'm going to give it some more testing and see if it fixed! Try it out
Sent from my Nexus 6
H4X0R46 said:
Hey guys! An update here, I just read through another post that was about this same issue, and someone in there said that downloading DNset from the play store fixes this issue! It changes your WiFi settings from ipv4/ipv6 to just ipv4. I did it and it's working so far, but I'm going to give it some more testing and see if it fixed! Try it out
Sent from my Nexus 6
Click to expand...
Click to collapse
Were you able to solve your slow page load issue?
I having same issue coming out of the box with a new N6P.
On TMO & Wifi - my old OPO had no issues.
But seems at least on LTE about town, my pages for social media & browsers are sloooooow.
perveeus said:
Were you able to solve your slow page load issue?
I having same issue coming out of the box with a new N6P.
On TMO & Wifi - my old OPO had no issues.
But seems at least on LTE about town, my pages for social media & browsers are sloooooow.
Click to expand...
Click to collapse
Hey dude, well honestly it didn't seem to fix it. Placebo effect lol What I think it comes down to is just Marshmallow being rough around the edges at this point because I have stock rooted Marshmallow 6.0 on my Nexus 6 and have cyanogenmod 12.1 installed as a secondary ROM, When booted into cyanogenmod, pages load much faster and it's more responsive as far as I can tell! So, it must be a bug with Marshmallow! Keep in mind cyanogenmod 12.1 uses Android 5.1.1 as a base!
Hi guys,
For those that have Bluetooth in your cars and use apps like SoundCloud, Pandora, etc., have you had issues with track information being displayed correctly?
Ever since I upgraded my Nexus 6 to nougat, the track information seems to be routed differently by the phones Bluetooth to my car's aftermarket Bluetooth receiver. Same has happened with my wife's Nexus 6 after she upgraded last week.
Both phones were working fine when on marshmallow using the same apps...Nothing else different other than upgrading to Nougat.
The only app that shows the metadata correctly on the main screen is the Play Music app. For all other 3rd part apps, I have to select "Channel List" and then I can see the track name. That was not the case with Marshmallow. All apps showed the metadata at the main screen where now it just displays some random numbers.
I know it's not the 3rd party music apps because they all display the metadata correctly when I have my work iPhone connected to my car.
Had the same problem on stock as well as Pure and Nitrogen. It's so frustrating because I don't have the slightest of clue on how I can go about figuring out what, if anything, has changed with the Bluetooth profile.
Any help or feedback would be greatly appreciated!
aerohp said:
Hi guys,
For those that have Bluetooth in your cars and use apps like SoundCloud, Pandora, etc., have you had issues with track information being displayed correctly?
Ever since I upgraded my Nexus 6 to nougat, the track information seems to be routed differently by the phones Bluetooth to my car's aftermarket Bluetooth receiver. Same has happened with my wife's Nexus 6 after she upgraded last week.
Both phones were working fine when on marshmallow using the same apps...Nothing else different other than upgrading to Nougat.
The only app that shows the metadata correctly on the main screen is the Play Music app. For all other 3rd part apps, I have to select "Channel List" and then I can see the track name. That was not the case with Marshmallow. All apps showed the metadata at the main screen where now it just displays some random numbers.
I know it's not the 3rd party music apps because they all display the metadata correctly when I have my work iPhone connected to my car.
Had the same problem on stock as well as Pure and Nitrogen. It's so frustrating because I don't have the slightest of clue on how I can go about figuring out what, if anything, has changed with the Bluetooth profile.
Any help or feedback would be greatly appreciated!
Click to expand...
Click to collapse
Ok first you need to understand a few things.
1. Just because it works on an Iphone doesnt mean anything when talking about android apps. They are completely different OSs as well as completely different apps. Built completely separately with different SDK
2. Just because it worked on the last update doesnt mean it will work on this.
As google play music works, that says they changed something in the 7.x update that broke the other apps. They will need to be updated to work with the change in the code.
zelendel said:
Ok first you need to understand a few things.
1. Just because it works on an Iphone doesnt mean anything when talking about android apps. They are completely different OSs as well as completely different apps. Built completely separately with different SDK
2. Just because it worked on the last update doesnt mean it will work on this.
As google play music works, that says they changed something in the 7.x update that broke the other apps. They will need to be updated to work with the change in the code.
Click to expand...
Click to collapse
Appreciate the feedback, thanks!
Yup... Definitely understand that iOS and Android are 2 complete different bases...I tested with the iPhone to make sure that the aftermarket Bluetooth receiver in the car was not the problem.
I do believe it's something that Google has changed and I'm starting to realize that the only option I may have is to wait and see.
One point I want to add is that the Nougat update did not break anything when it comes to connecting to my wife's Acura with built in Bluetooth. The track info continues to work fine..
I was hoping someone with more in depth knowledge of the Android systems maybe be able to chime in on what could have changed...I know the 3rd party apps i use have gone through multiple updates since Nougat came out so if they were gonna update something due to compatibility with Nougat, it would've happened already.
aerohp said:
Hi guys,
For those that have Bluetooth in your cars and use apps like SoundCloud, Pandora, etc., have you had issues with track information being displayed correctly?
Ever since I upgraded my Nexus 6 to nougat, the track information seems to be routed differently by the phones Bluetooth to my car's aftermarket Bluetooth receiver. Same has happened with my wife's Nexus 6 after she upgraded last week.
Both phones were working fine when on marshmallow using the same apps...Nothing else different other than upgrading to Nougat.
The only app that shows the metadata correctly on the main screen is the Play Music app. For all other 3rd part apps, I have to select "Channel List" and then I can see the track name. That was not the case with Marshmallow. All apps showed the metadata at the main screen where now it just displays some random numbers.
I know it's not the 3rd party music apps because they all display the metadata correctly when I have my work iPhone connected to my car.
Had the same problem on stock as well as Pure and Nitrogen. It's so frustrating because I don't have the slightest of clue on how I can go about figuring out what, if anything, has changed with the Bluetooth profile.
Any help or feedback would be greatly appreciated!
Click to expand...
Click to collapse
Exactly same issue here in my '15 Civic Si with Shamu, Victara, and Titan, Bluetooth metadata breaks after the first pairing/connection. Once Bluetooth is interrupted, either by shutting off car or disconnecting Bluetooth, metadata never displays again until I either clean flash ROM anew or delete the bluedroid folder contents and do the whole unpair and re-pair both audio device. Quite a pain of a workaround, and it doesn't stick either, breaks as soon as Bluetooth is interrupted again.
Since you're on Shamu, I can recommend Cyanide ROM and SIX ROM, also Pure Nexus (not sure why yours didn't work with it), I've tested a few updates of each of the three ROMs, and Bluetooth metadata worked fine. Nitrogen never worked for me either. AICP, CM, LOS, Resurrection Remix, Dirty Unicorns, Emotion OS, all break on this feature for now. Not sure how Google's own OS is running in this department, but I've seen quite a number of complaints on this issue with the 5x, 6p, both pixels, but not so much with Shamu. I've not ran Google's nougat since developer preview 5 of 7.0, and back then it was working, can definitely confirm. I just hopped on the custom ROM train ever since DU released their flavor of Nougat, and just can't or want to go back to stock vendor OS. But do try out Cyanide and SIX ROMs, they both worked flawlessly on this device. Both are packed with extra goodies too. If battery is more important, go with SIX ROM, it's by far the most fine tuned nougat ROM I've tested. You won't find it on XDA, look for it on G+ under "Frankie T (R3DS)" community. It's posted with all the direct links for proper installation. Cyanide is another amazing ROM, also another fine tuned ROM, comes with built in black theme, and good battery life (if you set the governor to interactiveX), but really smooth experience overall. SIX, by the way, uses Pure Nexus as a base platform, so just a heads up there. Personally I've used the last two pure Nexus ROM updates and had zero issues with song data displaying via Bluetooth. Make sure you clean flash the ROM, wipe dalvik cache, cache, date, and system. Leave the internal storage unchecked. If the issue persists, then backup your internal storage files/folders to an external drive/device and format the whole internal storage of your Shamu, then throw everything back on and try clean flashing, pure Nexus should work thereafter. I've even restored it as a nandroid backup a few times and had no issues. SIX ROM is pretty much a refined Pure Nexus with extra features. Give these a shot, well worth it. Let me know how it goes for you.
Syndrome666 said:
Exactly same issue here in my '15 Civic Si with Shamu, Victara, and Titan, Bluetooth metadata breaks after the first pairing/connection. Once Bluetooth is interrupted, either by shutting off car or disconnecting Bluetooth, metadata never displays again until I either clean flash ROM anew or delete the bluedroid folder contents and do the whole unpair and re-pair both audio device. Quite a pain of a workaround, and it doesn't stick either, breaks as soon as Bluetooth is interrupted again.
Since you're on Shamu, I can recommend Cyanide ROM and SIX ROM, also Pure Nexus (not sure why yours didn't work with it), I've tested a few updates of each of the three ROMs, and Bluetooth metadata worked fine. Nitrogen never worked for me either. AICP, CM, LOS, Resurrection Remix, Dirty Unicorns, Emotion OS, all break on this feature for now. Not sure how Google's own OS is running in this department, but I've seen quite a number of complaints on this issue with the 5x, 6p, both pixels, but not so much with Shamu. I've not ran Google's nougat since developer preview 5 of 7.0, and back then it was working, can definitely confirm. I just hopped on the custom ROM train ever since DU released their flavor of Nougat, and just can't or want to go back to stock vendor OS. But do try out Cyanide and SIX ROMs, they both worked flawlessly on this device. Both are packed with extra goodies too. If battery is more important, go with SIX ROM, it's by far the most fine tuned nougat ROM I've tested. You won't find it on XDA, look for it on G+ under "Frankie T (R3DS)" community. It's posted with all the direct links for proper installation. Cyanide is another amazing ROM, also another fine tuned ROM, comes with built in black theme, and good battery life (if you set the governor to interactiveX), but really smooth experience overall. SIX, by the way, uses Pure Nexus as a base platform, so just a heads up there. Personally I've used the last two pure Nexus ROM updates and had zero issues with song data displaying via Bluetooth. Make sure you clean flash the ROM, wipe dalvik cache, cache, date, and system. Leave the internal storage unchecked. If the issue persists, then backup your internal storage files/folders to an external drive/device and format the whole internal storage of your Shamu, then throw everything back on and try clean flashing, pure Nexus should work thereafter. I've even restored it as a nandroid backup a few times and had no issues. SIX ROM is pretty much a refined Pure Nexus with extra features. Give these a shot, well worth it. Let me know how it goes for you.
Click to expand...
Click to collapse
Wow! Thank you for the detailed feedback! Does your Si have factory nav?
Anyway, I can't tell you how many things I've tried to get this thing figured out...I also have active communication with the manufacturer of the Bluetooth unit to see if we can troubleshoot the issue..So far nothing.
This is the first time I'm hearing of SIX ROM so I'm gonna do some reading and then flash it later on in the week. I'll reply back with updates.
Thanks again!
aerohp said:
Wow! Thank you for the detailed feedback! Does your Si have factory nav?
Anyway, I can't tell you how many things I've tried to get this thing figured out...I also have active communication with the manufacturer of the Bluetooth unit to see if we can troubleshoot the issue..So far nothing.
This is the first time I'm hearing of SIX ROM so I'm gonna do some reading and then flash it later on in the week. I'll reply back with updates.
Thanks again!
Click to expand...
Click to collapse
Happy to help. No my Si doesn't have the navigation option, I just use my Shamu for that. I've finally got the attention of AICP moderator and developer at AICP G+ community, so it's looking like the Bluetooth metadata issue is a CM/LOS issue so far, they're going to look into it. I captured a logcat and pictures which are posted there under bugs+logcat. It's under AICP G+ community if you want to look at it, posted under my main Google account as Andrey K, you can check it out here: https://plus.google.com/112643646080294190790/posts/4FRbAonGT55.
As for you never hearing about SIX ROM, that's because the dev doesn't participate on XDA forums. It's a really stable nougat ROM all around, and now supports phh's root, which if paired with Magisk app, allows to hide root access from apps like Android pay and Pokemon go.
The most a manufacturer would offer is to replace the device, possibly for a fee, that won't solve your problem. Most nougat ROMs are currently experiencing this bug. Cyanide, SIX, and Pure Nexus do not have this problem, at least not on Shamu.
anyone ever come across a fix for this?
nerdyone255 said:
anyone ever come across a fix for this?
Click to expand...
Click to collapse
Nah, still struggling with it...I keep hoping that a new Android update will fix it but so far no luck. It used to work fine for me in Lollipop but nothing since I've upgraded to Nougat. I'm on Nexus 6. Wife has a pixel XL and had the same issue when she was on Nougat so it's not the phone. She did get the Oreo update this week so I'll try again to see if it works. If not, then this must be a compatibility issue that the adapter manufacturer may need to look at...
The annoying thing is that the metadata transfer is fine when using my work iPhone. But I hate the iPhone/Apple so I only touch that thing when I absolutely have to (work calls, work emails, etc)
Any solutions so far?
My S2 worked perfect with the Civic (only it did not import the whole phonebook). With S8 I have the whole phonebook but no metadata on tracks (still plays and controls work)
---------- Post added at 01:31 AM ---------- Previous post was at 01:31 AM ----------
Any solutions so far?
My S2 worked perfect with the Civic (only it did not import the whole phonebook). With S8 I have the whole phonebook but no metadata on tracks (still plays and controls work)