[Q] Anyone updated their KFHD (7") to M8? - 7" Kindle Fire HD Q&A, Help & Troubleshooting

!!Forgot to add it to the title, I'm talking about CM11 for KFHD7!!
Earlier this morning I found a thread saying M8 has been released for select devices. I went to CM's download page to check if it was out for KFHD 7 (tate) and found no M8, only the latest nightlies. I checked again a few times, hoping it might appear later today.
I still can't find it for tate, but when I went to Settings -> About Tablet -> CyanogenMod updates and had it check for updates, it found an update with this name: cm-11-20140708-SNAPSHOT-M8. I supposed this was it, so I downloaded it and flashed it to my kindle. Turns out I couldn't open my settings in any way, cause every time I tried to launch them they kept crashing.
I downgraded it again to M7 since I might need it tomorrow, but it's bugging me. This update can't be found in CM's download page (at least I don't see it anywhere), and if the settings aren't even opening, it's probably not too stable. I don't know much about nightlies and monthlies yet, but I thought monthlies were supposed to be more stable than nightlies... Does anybody know what's up with this update?

I've had no issues with m8 as of yet. Installed and working fine, already put my DPI back to 178 and enabled my dual panes and running fine.

YuriPan said:
!!Forgot to add it to the title, I'm talking about CM11 for KFHD7!!
Earlier this morning I found a thread saying M8 has been released for select devices. I went to CM's download page to check if it was out for KFHD 7 (tate) and found no M8, only the latest nightlies. I checked again a few times, hoping it might appear later today.
I still can't find it for tate, but when I went to Settings -> About Tablet -> CyanogenMod updates and had it check for updates, it found an update with this name: cm-11-20140708-SNAPSHOT-M8. I supposed this was it, so I downloaded it and flashed it to my kindle. Turns out I couldn't open my settings in any way, cause every time I tried to launch them they kept crashing.
I downgraded it again to M7 since I might need it tomorrow, but it's bugging me. This update can't be found in CM's download page (at least I don't see it anywhere), and if the settings aren't even opening, it's probably not too stable. I don't know much about nightlies and monthlies yet, but I thought monthlies were supposed to be more stable than nightlies... Does anybody know what's up with this update?
Click to expand...
Click to collapse
Yes i have, settings crashes every time you open, but can be fixed if you clear data. I also had few lag problems and minor glitches and that was it. Hascode didn't realize the m8 had come out for android so i think there may be a problem.

Bao289 said:
Yes i have, settings crashes every time you open, but can be fixed if you clear data. I also had few lag problems and minor glitches and that was it. Hascode didn't realize the m8 had come out for android so i think there may be a problem.
Click to expand...
Click to collapse
Οh, so there's a fix for that. Thanks. Although I think I'll stick to a nightly, it seems like too much trouble to go and fix that when the nightly after M8 hasn't caused any stability issues to me yet.

Related

[Q] kabaldans CM10 nightly - some issues

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.

GSM Signal on Custom ROMS // Sense Crashes

Hello all,
I live in Europe so after buying my HTC One, I proceeded to root it and SIM Unlock it (Successfully).
All was well and good, until a month or so later the phone begins to behave strangely.
When I hit Home there is a stutter and pause and the home panels appear as though the process had just been started (When it should be kept in the background). The App drawer would refuse to populate with apps and the phone would freeze and heat up (Extremely hot) at random times and for random lengths of time.
Having used Cyanogenmod on my Desire HD I decided to give it a go and bypass my problems altogether. It worked great! No more crashes or anything like that. Except I cannot pick up any GSM signal. Through messing with the mobile network settings I can get it to show "3" (my network) as the local network, but I cannot receive or send messages or calls.
After a lot of experimenting with tonnes of ROMs I have figured out that no custom ROM will give me a signal!
But every ROM that is based heavily on sense (Like Viper 1.1.0 for the HTC One) experiences the same crashes I had suffered with initially.
Does anybody have any ideas about this issue?
I use TWRP recovery and Factory Reset (via TWRP) before every flash.
Bump?
I am currently on stock and my phone continues to crash regularly for anything between 2-20 minutes. The issue has gotten a lot worse and my backup from months ago (just after SIM Unlock) does not help the issue. I don't know what the root cause is but it is something to do with Sense so I need to use another ROM. Does anybody have anything to add to the Signal/Reception issue I'm having with custom ROMs?
Okay one last bump.
Tried all the Sprint HTC One specified ROMs I could find, still no service.
Tried different radios, every network setting under phone info and mobile settings. Countless reboots.
APN settings never appear, rarely does the phone pick up my 3 Network but never has reception.
My recent desperate google searches are actually brining me back to this thread!
Stock sense is still spontaneously crashing when I restore to it, for when I need to use my phone again.
Hey, I know I'm talking to myself at this stage but to anyone who gets here in the meantime and has the crashing issue...
Installing something like Apex or Nova launcher instead of HTC Sense seems to solve it.
I guess blinkfeed had decided to become suicidal or something.
Anyway, the GSM issue is still there with other ROMs.
Sent from my HTCONE using xda app-developers app
Like i posted in your previous thread, did you try downgrading to a ROM having build 1.29?
Settings> About > Software Information > More > Build number
indy1811 said:
Like i posted in your previous thread, did you try downgrading to a ROM having build 1.29?
Settings> About > Software Information > More > Build number
Click to expand...
Click to collapse
Yes. I am currently running a stock that is Software Version 1.29.
I have tried a 1.31 version of stock too but the same issue exists across all the versions I could find, concerning the crashes. The only solution so far has been to change the Launcher.
Thanks, for checking out this thread too.
GMach234 said:
Yes. I am currently running a stock that is Software Version 1.29.
I have tried a 1.31 version of stock too but the same issue exists across all the versions I could find, concerning the crashes. The only solution so far has been to change the Launcher.
Thanks, for checking out this thread too.
Click to expand...
Click to collapse
One final thing i can think of...
Did you try editing your build.prop file?
I changed these settings:
gsm.sim.operator.alpha
Vodafone
gsm.operator.iso-country
in
ro.ril.hsupa.category
6
ro.ril.hsdpa category
10
gsm.sim.operator.iso-country
in
gsm.operator.numeric
40486
ro.telephony.default_network
3
gsm.sim.operator.numeric
40486
These are settings for my telephone operator in India. You might want to google for your settings...Have a look at the other settings as well.

[Q] Can't decide on a custom ROM!

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

Confused with Lollipop builds! Please help me select..

Hi. Currently I am on jcsullins CM11-20141002 Kitkat build. I plan on upgrading to Lollipop but I am confused between the 3 builds (invisiblek-cm12, flintman-evervolv and milaq-cm12).
I frequently use the browser, YouTube and Skype (audio only) on my TP, amongst other apps. Could someone please help me select the right build? TIA.
Bump..
abhi.eternal said:
Hi. Currently I am on jcsullins CM11-20141002 Kitkat build. I plan on upgrading to Lollipop but I am confused between the 3 builds (invisiblek-cm12, flintman-evervolv and milaq-cm12).
I frequently use the browser, YouTube and Skype (audio only) on my TP, amongst other apps. Could someone please help me select the right build? TIA.
Click to expand...
Click to collapse
I am using a recently installed Evervolv build in which everything I have tried on mine seems to be working. I have used the browser a bit. Skype runs but I haven't used it on the TP yet. On my machine it seems fine but slower that the early Jan build I put in before.
I did a friends machine with the default partitions, he did not have the OEM USB and use a thinner aftermarket he had. It installed but there were various problems.
- no camera detected
- Google play does not offer updates to the core apps (as it did on mine) as it should
- Gmail won't launch at all
I don't know if its a partition issue or corruption from the cable used. It was a complete reset and wipe of the system with WebOS gone. I didn't have time to do it all again and will look at it another time I ma down.
@Tripple-c Thanks. I think I'll go with invisiblek's CM12 build as by his post only the camera is broken. I can live with that for now. I need the mic to work which is still not 100% in Evervolv going by flintman's post.
Tripple-c said:
I am using a recently installed Evervolv build in which everything I have tried on mine seems to be working. I have used the browser a bit. Skype runs but I haven't used it on the TP yet. On my machine it seems fine but slower that the early Jan build I put in before.
I did a friends machine with the default partitions, he did not have the OEM USB and use a thinner aftermarket he had. It installed but there were various problems.
- no camera detected
- Google play does not offer updates to the core apps (as it did on mine) as it should
- Gmail won't launch at all
I don't know if its a partition issue or corruption from the cable used. It was a complete reset and wipe of the system with WebOS gone. I didn't have time to do it all again and will look at it another time I ma down.
Click to expand...
Click to collapse
That issue you discribed above would only happen if you did a dirty install and didn't install gapps. The newer version backs up gapps so you only have to install. I recommend a clean install(factory reset and format system) to get the camera to detect the only way and then reinstall with gapps use the newest nightly.
abhi.eternal said:
@Tripple-c Thanks. I think I'll go with invisiblek's CM12 build as by his post only the camera is broken. I can live with that for now. I need the mic to work which is still not 100% in Evervolv going by flintman's post.
Click to expand...
Click to collapse
Is there a reason to update to Lollipop besides wanting to test it out? I think Lollipop itself has a lot of issues lingering that Google still needs to fix.
pekcle said:
Is there a reason to update to Lollipop besides wanting to test it out? I think Lollipop itself has a lot of issues lingering that Google still needs to fix.
Click to expand...
Click to collapse
Well, if you look at it that way.. There was no reason for me to upgrade to KitKat! I think I just like my devices to be updated
abhi.eternal said:
Well, if you look at it that way.. There was no reason for me to upgrade to KitKat! I think I just like my devices to be updated
Click to expand...
Click to collapse
It's all cool. There's no harm in that. But Android 4.1 to 4.4 was fairly mild and incremental. Lollipop was a hefty change in concept and usage. I tried it on my N7 2013, and it was just harder to use. Buttons were smaller and closer together, more taps and swipes just to do something, etc. It feels like they compromised ease of use just to adhere to the material design. Seriously made me consider going to an Apple product. No joke!

CyanogenMod 12 fix for android auto?

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

Categories

Resources