Two bugs with CM11 on KF8.9 - 8.9" Kindle Fire HD Q&A, Help & Troubleshooting

I installed Hashcode's CM11 build (up to 3/25) for the KF8.9 (jem) and have run into two bugs that look pretty bad to me. I would have posted over in Hashcode's dev thread, but the forum won't let me because I don't yet have 10 posts
1. If you go to encrypt your device, it shows the Android-as-a-lock logo but no progress bar, and never actually does anything. So encrypting doesn't actually work.
I was able to work around this by installing Hashcode's latest CM10.2 build, encrypting using that build (that worked), and then installing CM11. Unlocking and decryption works fine, it's just that the encryption doesn't.
2. The first OpenGL app works fine. After either exiting or returning to the home screen, every subsequent OpenGL app crashes on initialization. That means I have to reboot to run another OpenGL app, which is pretty painful.
Haven't yet tried Hashcode's CM10.2 build to see if this works there.
In general, Hashcode's CM11 build is great and everyone here owes him great thanks for his work. I just hope that there's a way to get these two bugs fixed as development goes on. Thanks!

Related

[Q] Running gedeROM 1.55 looking to change ROM's

As the title says, I am running gedeROM 1.55 for the past year, since I experimented with a couple ROM's and settled on this one. For the most part its been a decent daily driver but have found it a little 'sluggish' lately and it annoys me. The lack of deep sleep keeps me always scrambling to keep it charged and ready to go so I don't find it dead when I want to use it.
Of course in the process I am using an older version of FFF and TWRP, so I know an update of them would be necessary.
A couple questions, looking for opinions:
1. Is it possible to just use KFU and update FFF and TWRP without disturbing everything else? I'd like to get them up to date.
2. After reading for 2 hours or more I am unclear on the limitations of 10.1 JB and wonder if I should be changing to JB at all?
3. Are the 10.1 ROM's a better option than I am running for speed and reliability? If so, any shining star amongst them?
I know asking for opinions will bore most people to death reading this, but I need some guidance from those that have been active and keeping up with ROM dev on this unit while I left mine alone and got behind.
Thanks in advance.
This might help you:
1. Look on the first post of this thread. Theres a flashable zip for FFF1.4 (Just flash in TWRP)
2. Here is Ichigo's flashable zip for TWRP 2.5.0 (Just flash in TWRP) https://www.dropbox.com/s/b4idirzkmgvnm07/TWRP-Blaze-2.5.0.0.zip
Those will not disturb anything else.
And try This ROM first and see if you like 4.2.2. This is the OFFICIAL cyanogenmod 10.1. To me its by far the best in terms of stability and speed. Make sure you wipe everything BUT /sdcard in TWRP before you flash!
Moving to a recent JB ROM will be a good move compared to gede because not only will you have better battery life but you'll have almost another year of improvements made to the Kindle since then.
Thanks for the info.... I'm gonna give this a shot I think. Not much to lose, nothing mission-critical on my tablet anyway
I'll post back once it's done!
Thanks again.
Bozz5384
It seems to have gone well, thanks for all the info. Updated FFF, TWRP, and now on CM 10.1 ... I did the 5/20 nightly, wasn't sure which one to do -- seems pretty bug free at this point.

[Q] CWRM / TWRP Charging?

Hello,
I've read through the Everything thread on Development, as well as searched using the xda search and google site search, but come up with nothing.
The Everything thread mentions that the current version of CWRM won't charge when the phone is off or in recovery, but I can't find anything about which version is the 'latest' (6.0.1.2, 5.0.2.7), nor if this also affects the TWRP recoveries (2.6.3, 2.4.1)? For that matter, I can't find anything that even mentions the charging problems at all aside from the Everything thread!
If there is a charging problem with all of the third party ROMs, is there a method to go back to the stock recovery after flashing in a ROM and backing up /efs/? I'm basically shooting for a fully functional phone and I don't plan on changing ROMs all over the place, just root and ICS.
Help?
Thanks!
TooG435 said:
Hello,
I've read through the Everything thread on Development, as well as searched using the xda search and google site search, but come up with nothing.
The Everything thread mentions that the current version of CWRM won't charge when the phone is off or in recovery, but I can't find anything about which version is the 'latest' (6.0.1.2, 5.0.2.7), nor if this also affects the TWRP recoveries (2.6.3, 2.4.1)? For that matter, I can't find anything that even mentions the charging problems at all aside from the Everything thread!
If there is a charging problem with all of the third party ROMs, is there a method to go back to the stock recovery after flashing in a ROM and backing up /efs/? I'm basically shooting for a fully functional phone and I don't plan on changing ROMs all over the place, just root and ICS.
Help?
Thanks!
Click to expand...
Click to collapse
I think something like 6.0.4 the latest CWMR. ( you can build with http://builder.clockworkmod.com/ , Existing Device option doesnt work)
It charges in latest TWRP, you can see "+" char when on charge next to the battery level.
Stock uses recovery for official upgrade, and factory reset. We have only offline charge issue, but recovery has no effect on it. Offline charger works with a limitation. I wouldnt bother you with the explanation, since you said you would like to use stock ICS.
You can backup efs in rooted rom without recovery. You can always flash recovery with odin phone in download mode.
Thanks.
I guess I had assumed the comment was referring to the builds in the Development forum, not the overall CWMR project! Is there a currently recommended recovery, or is it a toss up to personal preference? I'm not so much tied to ICS as tied to a completely working ROM - especially as I see all the bluetooth and skype issues with the JB ROMs, which (as far as I can tell) are still unresolved / unknown?
TooG435 said:
Thanks.
I guess I had assumed the comment was referring to the builds in the Development forum, not the overall CWMR project! Is there a currently recommended recovery, or is it a toss up to personal preference? I'm not so much tied to ICS as tied to a completely working ROM - especially as I see all the bluetooth and skype issues with the JB ROMs, which (as far as I can tell) are still unresolved / unknown?
Click to expand...
Click to collapse
I make TWRP for i927, we dont have other up to date, but you can build yourself.
Dont you have issue with stock ICS? I made up to date issue list in me CM 10.2, you could decide it suit for you or not, you may know stock limitation already.
I hope voip issue would be resolved soon.
bubor said:
I make TWRP for i927, we dont have other up to date, but you can build yourself.
Dont you have issue with stock ICS? I made up to date issue list in me CM 10.2, you could decide it suit for you or not, you may know stock limitation already.
I hope voip issue would be resolved soon.
Click to expand...
Click to collapse
My only real requirement in a phone is that it be reliable - I don't want to have to pop out batteries or have no audio on calls if I get stranded in the middle of nowhere. At this point, my phone is still in the mail - got a used one from a friend, but it hasn't arrived, so I haven't had much ability to experiment yet.
My Android experience is exclusively with a Transformer TF101, which had 4.0.4 ICS stock and is currently running Katkiss JB 4.2.2_226 (Katkiss 4.3 isn't stable enough for me yet, was getting daily crashes last time I tried). All of the phone components are new to me - and the Glide seems to have a more fragmented recovery scene than the TF101, which is pretty much TWRP or nothin'
Thanks again for your help!

[Q] CWM crashes when trying to format /data

Hi,
this is my first post and I'm very sorry if it's a repeat, but I've searched all over and cannot seem to find anyone with my issue (which I find very hard to believe).
I'm trying to install a custom recovery (which I've done successfully before) using Odin. trying to use Philz Touch, cause it looks awesome, but now, I'm just trying to get anything to work.
The issue is I CANNOT format my /data partition. every time I try, it crashes. I have NO idea why. it can format anything else, I can mount/unmount /data, I just can't format it. cwm freezes and quickly crashes.
The particularly annoying thing is that this happened the last time I installed CWM too, but updating to the most recent version solved that. This time, I'm trying for the most recent version right away and nothing's happening. ALSO, today, I installed PhilzTouch and it WORKED!! so I installed my custom rom (Carbon) and went to reboot. This got stuck at the boot screen, and never loaded, so I booted back into recovery and whadayaknow, I can no longer format /data.......... I have no idea what is going on. I've followed all the instructions to the letter.
I'm on d2spr (sprint galaxy s3), trying to install cwm 6.0.4.5 (or philz 6.15.4) so that I can install CarbonROM v1.8 (which I also cannot get to work. I've happily been on SlimBEAN and then SlimKat for a while and wanted to try Carbon for the extra features).
Any help would be GREATLY appreciated. (also, I can't restore a backup because that includes writing to /data, which I can't do. I can get halfway through the backup so that I end up with a clean slimKat (which I don't really want, cause I have a lot of data), but that's it. CWM reboots the second it tries to write /data.
EDIT: This issue happens when I try to flash CarbonRom, but goes away if I flash something like CM or SlimBean. Once one of those roms is installed AND BOOTED, I can touch /data again, but once I try to get CarbonRom running, I can't. So it seems it's an issue with CarbonROM specifically. Any advice?
Update: It's only Carbon Rom
Hey, so apparently, I can flash literally every other ROM I've tried (cyanogen, slimbean, slimkat, beanstalk) and they all work fine, but when I flash Carbon (the release version, v1.8), I get to the "Samsung Galaxy S3" screen with the "C" logo and it hangs indefinitely. When I give up and pull the battery, the /data partition is untouchable like before, but that now seems like a symptom, not the problem, because it only happens with Carbon and it's fixed by flashing another rom and letting it boot. And yes, I've given it quite a long time to boot, but it never even gets to a legitimate boot screen (with some sort of moving animation). It just freezes and and never unfreezes.
Anyone, any help would be really appreciated. It's VERY frustrating....
pianoman1645 said:
Hey, so apparently, I can flash literally every other ROM I've tried (cyanogen, slimbean, slimkat, beanstalk) and they all work fine, but when I flash Carbon (the release version, v1.8), I get to the "Samsung Galaxy S3" screen with the "C" logo and it hangs indefinitely. When I give up and pull the battery, the /data partition is untouchable like before, but that now seems like a symptom, not the problem, because it only happens with Carbon and it's fixed by flashing another rom and letting it boot. And yes, I've given it quite a long time to boot, but it never even gets to a legitimate boot screen (with some sort of moving animation). It just freezes and and never unfreezes.
Anyone, any help would be really appreciated. It's VERY frustrating....
Click to expand...
Click to collapse
Just FYI, that version of Carbon is really old, you will probably want something more current like their KitKat builds or at least the 4.3.1 builds from November. Sounds like you are probably flashing 4.4 GApps, which would be a mismatch for the version of the ROM you are flashing, which is why things are hanging for you. Also, if you are using Philz Touch (highly recommended!), then the only wipe you need is "Clean to Install New ROM" and nothing more.
Mr. Struck said:
Just FYI, that version of Carbon is really old, you will probably want something more current like their KitKat builds or at least the 4.3.1 builds from November. Sounds like you are probably flashing 4.4 GApps, which would be a mismatch for the version of the ROM you are flashing, which is why things are hanging for you. Also, if you are using Philz Touch (highly recommended!), then the only wipe you need is "Clean to Install New ROM" and nothing more.
Click to expand...
Click to collapse
Thanks for the reply!
Actually, I want flashing any gapps at all specifically so that it didn't conflict. Should have mentioned that.
Also, I was under the impression that 1.8 was a 4,3 build, but if that's not true, I'd certainly want a later build. However, I'm looking for a stable room with lots of features, so I was only looking at release builds.... And 1.8 is the only release build for d2spr. Any suggestions on which later build is the most complete/stable?
And yes, I'm using philz touch. Latest version.
pianoman1645 said:
Thanks for the reply!
Actually, I want flashing any gapps at all specifically so that it didn't conflict. Should have mentioned that.
Also, I was under the impression that 1.8 was a 4,3 build, but if that's not true, I'd certainly want a later build. However, I'm looking for a stable room with lots of features, so I was only looking at release builds.... And 1.8 is the only release build for d2spr. Any suggestions on which later build is the most complete/stable?
And yes, I'm using philz touch. Latest version.
Click to expand...
Click to collapse
So Carbon never released a stable version of 4.3, just nightlies. It is hard to tell from how they restructured their downloads page, however, it is one of those things you would only know from following their progress since last fall. As far as stable, that is almost subjective, a lot of the newest nightlies are really good. I would recommend one of the Snapshots from CM11 or any Carbon nightly from 2/18 or earlier (2/4 was really nice) if you want something that should work well. As always, YMMV.

[Q&A] [ROM][UNOFFICIAL] CyanogenMod 11 Nightlies / Releases [M11]

Q&A for [ROM][UNOFFICIAL] CyanogenMod 11 Nightlies / Releases [M11]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
my desire hd cant boot when i swich to ART mode
Mustaavalkosta said:
General:
These are UNOFFICIAL CM11.0 Kitkat Nightlies / Releases brought to you by AceEnablementProject and TeamCodefire as a continuum to CM10 and 10.1 nightlies. Builds are generated automatically each night. Process starts around 00:30 PDT. If it fails, then there will be no build until the reason for failure is taken care of which can take time. Latest 12 nightlies will be kept on the server. If you want a longer history of them, you are free to archive them yourself.
Thanks and credits:
Andromadus
CodeAuroraForum
CyanogenMod
BananaGranola
Epic Beard Men
eXistZ
Flemmard
Flinny
goo.im
Juansheng
paulb_nl
randomblame
synergye
TeamCodefire (for build server and hosting, priceless)
All the rest that have helped to construct these builds and develop software for ace directly or indirectly in the past.
Githubs:
CyanogenMod
AceEnablementProject
Changelogs:
CM Gerrit
CM Google+
Github (see above)
Installation instructions:
Download Nightlies / Releases [BasketBuild mirror]
Download gapps from here. Pico/Nano/Micro recommended, Mini/Full/Stock doesn't fit in our system partition after the ROM has been installed.
Put the files on SD card.
Reboot to recovery.
Do factory reset (ie. format /data, /cache, /sd-ext and /sdcard/.android_secure)
Flash cm-11-YYYYMMDD-UNOFFICIAL-ace.zip
Flash gapps zip
Remember to reflash boot.img via fastboot if you are HTCDev unlocked.
Reboot and enjoy.
Update instructions:
Download Nightlies / Releases [BasketBuild mirror]
Put the file on SD card.
Reboot to recovery.
Flash cm-11-YYYYMMDD-UNOFFICIAL-ace.zip
Remember to reflash boot.img via fastboot if you are HTCDev unlocked.
No need to flash gapps as CM backuptool script should take care of them. (Results may vary depending on which gapps package you are using.)
Reboot and enjoy.
InspireMod
http://downloads.codefi.re/mustaavalkosta/inspiremod
Kernel
Source: github
Compiler: stock AOSP gcc-4.7
Branch: cm-11.0
Kernel Version: 3.0.101
defconfig: spade_defconfig
Contact:
My Google+
My twitter
#codefireX @ freenode
Donations:
For hosting: codefi.re (use the donation button at the bottom of the page)
I don't really need your money right now but if you insist on donating to me I suggest you donate that money to EFF instead here: https://supporters.eff.org/donate
Q&A:
Q: I tried to flash the ROM and got this:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/..path od ROM.zip
(Status 7)
Installation aborted.
A: Update your recovery to one that is compatible with new recovery functions. See the list below.
4EXT Recovery Touch v1.0.0.6 RC 3 or newer
CWM 6.0.4.8 Advanced Edition / PhilZ Touch 6.29.8 or newer
TWRP 2.7.1.0 ACE or newer
Q: I've used HTC Dev unlock and flashed the rom but it won't boot. What should I do?
A: You need to extract boot.img from the zip and flash it via fastboot. If you don't have fastboot executable anymore from flashing recovery, install Android SDK platform tools (Linux users should find it from distro's package management) and then reboot to bootloader, open command prompt and navigate to the location you extracted your boot.img and type:
Code:
fastboot flash boot boot.img
You need to repeat this everytime you flash new version of this rom to ensure everything will work fluently as long as you have just basic HTC Dev unlock.
Q: Where are my developer and performance options?
A: http://goo.gl/jpS8r
Q: Feature X doesn't work, let's make 1000 posts about it to annoy everyone.
A: Please, dont. Use search and then use search again and only then report your problem with necessary logs. [Logcat guide, thanks to MusikMonk for the link]
Q: I hate you for not fixing this issue X!!!
A: I love you too.
Q: How I can build CM11.0 myself?
A: Setup a basic Android build environment.
Code:
mkdir cm11
cd cm11/
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
mkdir -p .repo/local_manifests
wget https://github.com/AceEnablementProject/android/raw/cm-11.0/local_manifest.xml -O .repo/local_manifests/cm_ace.xml
repo sync
cd vendor/cm/
./get-prebuilts
cd ../../
. build/envsetup.sh
lunch cm_ace-userdebug
mka bacon
Once the build finishes you'll find your goods from out/target/product/ace/ directory.
Q: Something about something something something.
A: Ask the guy/gal next to you.
XDA:DevDB Information
[UNOFFICIAL] CyanogenMod 11 Nightlies / Releases [M11], ROM for the HTC Desire HD
Contributors
Mustaavalkosta, paulb_nl
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: M11
Beta Release Date: 2014-10-08
Created 2014-04-11
Last Updated 2014-10-09
Click to expand...
Click to collapse
some saids it`s because the partition of cache is too small
CM11 latest release freezes after first reboot
GD to all. I am trying to install CM11 latest release, first time starts ok, but after reboot it doesn't start, freezes with black screen before bootanimation. Tried to flash boot.img via ADB & also tried to install CM 10.1 SR3, nothing helped, same situation. Waiting for your replies. Thx in advance.
Hey!
Would it be possible to you to add gpu overclock to that kernel?
Thx
Question about bugfixes
Hi,
at the moment i have M10 installed but i want to ask if there is a fix in M11 included which fixes sudden restarts.
My DHD restarts over night or when i want to something (it doesnt depends on what i am doing).
And another Problem sometimes the screen wont turn on when pressing the power button only the menu keys lighten up.
And i think it is more like off topic but how i can unlock the phone that i do not need to flash boot.img it is at the moment only HTC-Unlocked.
And very much thanks for this ROM it is great!
Thanks in advance for your answers
ag1707
Cannot dirty flash Nightlies
Hi
Since sometime around M11 release, I can not dirty flash nightlies on nightlies. The phone stuck at booting with the message "Android is upgrading / Finishing boot".
I'm using TWRP 2.7.1.0 for recovery.
1. Install Rom
2. Wipe Cache/Dalvik (I've tried without wipe too)
3. Reboot System
Am I missing something here?
I'm using non-English locale. Could it be the reason?
Best Regards,
Solved
Nanashi_anon said:
Hi
Since sometime around M11 release, I can not dirty flash nightlies on nightlies. The phone stuck at booting with the message "Android is upgrading / Finishing boot".
I'm using TWRP 2.7.1.0 for recovery.
1. Install Rom
2. Wipe Cache/Dalvik (I've tried without wipe too)
3. Reboot System
Am I missing something here?
I'm using non-English locale. Could it be the reason?
Best Regards,
Click to expand...
Click to collapse
Just figured it out that PA_GAPPS requires flash every update for recent ROMs.
Hi and thx for your rom!
I flashed the cm-11-20141008-UNOFFICIAL-M11-ace from releases, using twrp 2.7.1.0 for the recovery on a HTC Desire HD.
I am experiencing some lag when opening the screen or starting apps / widgets. It can take be almost instant up to 3-5 sec for the app to launch and be accessible (camera, gallery, weather, settings, mail anything really).
Also once in a while parts of the text in the screen get deformed (example here), any action by me (moving my finger around) or by the OS (some notification) fixes it.
As far as I can tell I followed your instructions properly. Is there anything I could try?
XZelin said:
some saids it`s because the partition of cache is too small
Click to expand...
Click to collapse
Possibly. There are some posts about this from paulb_nl on the main thread but I didn't find them right now. They are there though.
sky141 said:
GD to all. I am trying to install CM11 latest release, first time starts ok, but after reboot it doesn't start, freezes with black screen before bootanimation. Tried to flash boot.img via ADB & also tried to install CM 10.1 SR3, nothing helped, same situation. Waiting for your replies. Thx in advance.
Click to expand...
Click to collapse
Are you using the latest recoveries mentioned in the first post's Q&A section in the development thread? If your issue is what I think it is, full wipe with the previously mentioned recoveries should fix it.
_Bon_Bon said:
Hey!
Would it be possible to you to add gpu overclock to that kernel?
Thx
Click to expand...
Click to collapse
Is there working GPU OC for ace? I thought it was hardware locked thus can't be overclocked via software.
ag1707 said:
Hi,
at the moment i have M10 installed but i want to ask if there is a fix in M11 included which fixes sudden restarts.
My DHD restarts over night or when i want to something (it doesnt depends on what i am doing).
And another Problem sometimes the screen wont turn on when pressing the power button only the menu keys lighten up.
Click to expand...
Click to collapse
I haven't heard any complaints about frequent reboots. I know that there are those but it's been said to happen like once a week or so. M11 may change something if your issues come from corrupted devlog partition but if it's something else, then M11 won't do anything for your reboot issue.
Nihim said:
Hi and thx for your rom!
I flashed the cm-11-20141008-UNOFFICIAL-M11-ace from releases, using twrp 2.7.1.0 for the recovery on a HTC Desire HD.
I am experiencing some lag when opening the screen or starting apps / widgets. It can take be almost instant up to 3-5 sec for the app to launch and be accessible (camera, gallery, weather, settings, mail anything really).
Also once in a while parts of the text in the screen get deformed (example here), any action by me (moving my finger around) or by the OS (some notification) fixes it.
As far as I can tell I followed your instructions properly. Is there anything I could try?
Click to expand...
Click to collapse
It's a bit slow but I suppose that's understandable considering we are talking about 4 year old device. People have reported it gets slower the more apps you install. I'm not sure why.
I'm seeing that kind corruption on the screen graphics for the first time. Any chance of figuring out how to reproduce it and write step-by-step what to do so I could maybe replicate the issue on my end?
Mustaavalkosta said:
It's a bit slow but I suppose that's understandable considering we are talking about 4 year old device. People have reported it gets slower the more apps you install. I'm not sure why.
I'm seeing that kind corruption on the screen graphics for the first time. Any chance of figuring out how to reproduce it and write step-by-step what to do so I could maybe replicate the issue on my end?
Click to expand...
Click to collapse
Yea that is very much true, this might sound bad but would is there some other version you would recommend (even if it's a previous android release) which would be snappier? (your ROM so far is absolutely fine outside of that lag which as you stated is probably because DHDs hardware can't handle it).
As for that graphics glitch can't think of something, any apps were installed from play store (not restored by titanium for example) it happens on different ones but a lot more often on k-9 email client (from which the screenshot is).
If there is something that you would like me to try, feel free to tell me, though any action on the screen restores it to its normal way.
Nihim said:
Yea that is very much true, this might sound bad but would is there some other version you would recommend (even if it's a previous android release) which would be snappier? (your ROM so far is absolutely fine outside of that lag which as you stated is probably because DHDs hardware can't handle it).
As for that graphics glitch can't think of something, any apps were installed from play store (not restored by titanium for example) it happens on different ones but a lot more often on k-9 email client (from which the screenshot is).
If there is something that you would like me to try, feel free to tell me, though any action on the screen restores it to its normal way.
Click to expand...
Click to collapse
I don't mind people looking for better solution for their needs. You may want to try my CM10.1 builds which were noticeably faster if I recall correctly. I haven't been using other ROMs that much during the time I've kept my own stuff going here so I can't really recommend anything else. A fellow user may be a bit less biased to recommend other options.
I'll see if I can catch that graphical glitch with K-9 myself. Thanks for reporting it!
Mustaavalkosta said:
I'm seeing that kind corruption on the screen graphics for the first time. Any chance of figuring out how to reproduce it and write step-by-step what to do so I could maybe replicate the issue on my end?
Click to expand...
Click to collapse
I get that black boxes glitch with the standard Email app all the time. They usually go away in less than a second. I also checked for those when I was testing the 4.4 adreno drivers and it was still not fixed.
paulb_nl said:
I get that black boxes glitch with the standard Email app all the time. They usually go away in less than a second. I also checked for those when I was testing the 4.4 adreno drivers and it was still not fixed.
Click to expand...
Click to collapse
Oh ok. If it has been mentioned in the development thread, I've just probably forgotten about it.
Mustaavalkosta said:
I don't mind people looking for better solution for their needs. You may want to try my CM10.1 builds which were noticeably faster if I recall correctly.
Click to expand...
Click to collapse
Thanks! What would be the proper way to backup the whole "phone" so I can switch back and forth between roms? Atm I 'm only backing up apps & data with titanium.
Nihim said:
Thanks! What would be the proper way to backup the whole "phone" so I can switch back and forth between roms? Atm I 'm only backing up apps & data with titanium.
Click to expand...
Click to collapse
Doing a backup in recovery should be sufficient to backup everything except sdcard.
Mustaavalkosta said:
Are you using the latest recoveries mentioned in the first post's Q&A section in the development thread? If your issue is what I think it is, full wipe with the previously mentioned recoveries should fix it.
Click to expand...
Click to collapse
Thx 4 yours above. I'm using latest 4ext recovery touch + full wipe, of course. Will try to do something with partition.
Update from M11 to Nightly
It is possible to flash the newest nightly over the M11 release?
Or I need a full wipe.
Christian1987 said:
It is possible to flash the newest nightly over the M11 release?
Or I need a full wipe.
Click to expand...
Click to collapse
Well, generally it's recommended to wipe if you switch from one to another but it may work in this case without wiping. Make a nandroid backup and try it.
My battery dies really fast. Do you guys have a recommendation in terms of which battery to get? Link it here. Thanks.
prufessor_oak said:
My battery dies really fast. Do you guys have a recommendation in terms of which battery to get? Link it here. Thanks.
Click to expand...
Click to collapse
You can get original Desire HD battery on ebay cheaply, no point looking at other batteries which cost almost the same. Just look for one in your region.
Install Wakelock Detector from the Play store and find out what is causing your battery drain. Depending on phone use it should be able to last all day, 2 days if just left on standby all the time. Screen on all the time will be around 3-4 hours.

[Q&A] [ROM][L900] Cyanogenmod 12.0 [12/14/14]

Q&A for [ROM][L900] Cyanogenmod 12.0 [12/14/14]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][L900] Cyanogenmod 12.0 [12/14/14]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
keyboard ?
works Good to what i see but there's no keyboard . Any fix for that ?
Working great no issues with phone, gps or camera. Great job and I look forward to the updates. Seems great so far.
Thanks
I just installed the new build I am only wondering how do I turn off my mobile data. This ROM is amazing and everything works except for data turning off and front camera
Battery Life
When i flashed this rom onto my device, i noticed a significant drop in battery life. Has anyone else noticed this and is there a fix for this?
thnx
Thank you sooooooooooo much man ,,, its sooooooo cooool ROM
working Perfectly on my sprint Note 2 SPH-L900
camera works fine ,,, everything is cool ,,, downloading now gapps
So I'm relatively new to the forums, I mostly just read, learn and try to stay out of way. Just flashed latest nightly last night. So far very smooth and stable. I did some poking a prodding this morning to answer some questions I had coming from CM11 which I was also new to.
Nice to see Sprint carrier billing back in this version. I know I saw it posted that NFC was not working but everything but Tap & Pay seems to work fine for me. Beam and Tags all function okay.
On top of Netflix not working yet, Play Movies 3.6.16 FCs on launch and after reverting to 3.4.23 it waits until you press play to FC.
I did have the keyboard issue that has been mentioned but was prepared with SwiftKey apk on my sdcard just in case. After finishing setup ALL keyboards seem to function just fine.
BT and GPS both working great.
All in all very usable and I'm going to give it a go as a daily for as long as possible though I may have to revert back to CM11 just for the Netflix/Play Movies since we only stream in my household. We'll see.
Not sure if this thread was the best place to share (I can't seem to comment on the main thread) but if there's a more appropriate place to provide feedback that someone wants to point me at, happy to do it.
Nice work everyone who's contributing. Thanks for your efforts keeping my Note 2 relevant.?
GPS
How did you get the GPS working? I tried flashing the GPS fix linked in the thread and a clean install with the latest nightly. I drive around and never obtain a GPS lock.
k3v0 said:
How did you get the GPS working? I tried flashing the GPS fix linked in the thread and a clean install with the latest nightly. I drive around and never obtain a GPS lock.
Click to expand...
Click to collapse
I followed the sequence in this comment on the main thread and it just worked.
http://forum.xda-developers.com/showthread.php?p=58403610
Credit: @kylemccracken
"Edit: Make sure all important data and backups are stored to your external SD card before formatting. I used Philz 6.48.4 and CWM 6.0.5.0 when following this procedure.
[IMPORTANT]
After wiping clean to install a new rom, factory resetting, and wiping cache and dalvik cache, in philz recovery, go to your storage and mounts settings and format every option you can EXCEPT sdcard1. Reboot your recovery then proceed with the steps below.
Make sure you have your ROM, Gapps, SuperSU, and GPS fix zips on your external sdcard1. Flash in the order below.
1. Flash your ROM zip.
2. Perform a factory reset then wipe both cache options. This step is very important when facing problems after flashing.
3. Flash your Gapps zip. Wipe both cache.
4. Flash your SuperSU zip. Wipe both cache.
5. Flash GPSfix zip. Wipe both cache.
6. Reboot.
This process will give you the cleanest possible install with the highest chance of success. When I start having problems with flashing, I format everything (except sdcard1) then follow those steps. It's the same procedure I took when flashing the CM12 nightly and all is running well."
So I've been following the change log for this Rom, and I can't understand much.
I'm still on the 1/5/15 non nightly version and it's pretty much functional as a daily driver. What I'm wondering is are there any major differences for the newer nightlies?
Perhaps in addition to being a Q&A on these nightlies, everyone can post which version they're on, how it is (what's broken/what's been fixed), and what's new if anything.....
Newb question: This is the first time I've started on a ROM at such an early stage of its development. Typically how fast does CM development progress once a new version is started? Idle curiosity mostly.
The Commish said:
Newb question: This is the first time I've started on a ROM at such an early stage of its development. Typically how fast does CM development progress once a new version is started? Idle curiosity mostly.
Click to expand...
Click to collapse
That would be nightly.
Sent from my SM-N910P using XDA Free mobile app
t4d73 said:
That would be nightly.
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
Haha, thanks. ? I understand the nightly releases. What I meant was I guess is how long after a new version is started does it normally take to get to the first milestone or even snapshot release for instance? Like I said, I'm just curious about the process.
The Commish said:
Haha, thanks. ? I understand the nightly releases. What I meant was I guess is how long after a new version is started does it normally take to get to the first milestone or even snapshot release for instance? Like I said, I'm just curious about the process.
Click to expand...
Click to collapse
Lol. Yeah I wouldn't get your hopes up too high for that. It might happen but I guess we'll see. I don't think any device has gotten a milestone just yet anyway.
Sent from my SM-N910P using XDA Free mobile app
Keeps restarting on cm12 boot screen
Hey guys,
I have a situation I've never come across and wanted to see if someone might be able to point me in the right direction. I have two Samsung Note 2(l900) and running on cm12 as of this morning. I installed the new nightly on both devices the same exact way by opening clockwork recovery and installing zip. One device was successful and is working just fine, the other seemed to flash fine until it had finished loading the apps and going into boot. The device would restart on the note 2 logo screen and then proceed to the cm12 boot screen and then restart after a few seconds. I went back into recovery which took longer than usual, and proceeded to clear partition, wipe dalvik cache, and install older nightlies. I had the same result no matter what nightly I went with.
I decided to set the device back to stock rom and root again. I it worked just fine, so I went through the process about 4 times installing different nightlies but had the same restarting results. It was then I noticed that getting in clockwork recovery manually lagged about 30 seconds. I took the advice of someone on the Google plus forum and switched the recovery from clockwork to twrp. Tried again with the same restarting results and with the manual recovery lagging about 30 seconds to get into.
It seems to work just fine if I flash to stock touchwiz but recovery seems to have issues.
Anyone getting Netflix or Play Movies to work yet on the latest versions? It's the only thing that made me have to revert back to CM11. I tried looking over the change log but honestly I don't know what half that stuff means.?
The Commish said:
I followed the sequence in this comment on the main thread and it just worked.
http://forum.xda-developers.com/showthread.php?p=58403610
Credit: @kylemccracken
"Edit: Make sure all important data and backups are stored to your external SD card before formatting. I used Philz 6.48.4 and CWM 6.0.5.0 when following this procedure.
[IMPORTANT]
After wiping clean to install a new rom, factory resetting, and wiping cache and dalvik cache, in philz recovery, go to your storage and mounts settings and format every option you can EXCEPT sdcard1. Reboot your recovery then proceed with the steps below.
Make sure you have your ROM, Gapps, SuperSU, and GPS fix zips on your external sdcard1. Flash in the order below.
1. Flash your ROM zip.
2. Perform a factory reset then wipe both cache options. This step is very important when facing problems after flashing.
3. Flash your Gapps zip. Wipe both cache.
4. Flash your SuperSU zip. Wipe both cache.
5. Flash GPSfix zip. Wipe both cache.
6. Reboot.
This process will give you the cleanest possible install with the highest chance of success. When I start having problems with flashing, I format everything (except sdcard1) then follow those steps. It's the same procedure I took when flashing the CM12 nightly and all is running well."
Click to expand...
Click to collapse
I've tried several methods and combinations of wiping at every possible opportunity before pressing reboot and i'm still having
issue. All the the apps are listed in the app drawer displaying the file name instead of the app name. Also all of the apps display the same icon (default android) and the not installed toast appears when attempting to launch any of them. Is anyone else having this issue
attempted flashing
cm-12-20150203-NIGHTLY-l900.zip with md5: ba795d6a4261654648b0eb5cec019021 downloaded from http://download.cyanogenmod.org/?device=l900&type=stable
cm-10.1.3-l900.zip with md5: ba795d6a4261654648b0eb5cec019021 downloaded from http://wiki.cyanogenmod.org/w/Gapps
has anyone had success with either of these
currently running Android 5.0 Lollipop ROM for Galaxy Note 2! [CM12] downloaded from http://galaxynote2root.com
attempted with both gapps-lp-20141109-signed.zip and LollipopMicroGapps-121914-HighOnAndroid.zip both downloaded from http://galaxynote2root.com
I would prefer to use the aforementioned build because the build I'm running is not compatible with the nightlies
thanks for any responses in advanced.
KAZETARO said:
I've tried several methods and combinations of wiping at every possible opportunity before pressing reboot and i'm still having
issue. All the the apps are listed in the app drawer displaying the file name instead of the app name. Also all of the apps display the same icon (default android) and the not installed toast appears when attempting to launch any of them. Is anyone else having this issue
attempted flashing
cm-12-20150203-NIGHTLY-l900.zip with md5: ba795d6a4261654648b0eb5cec019021 downloaded from http://download.cyanogenmod.org/?device=l900&type=stable
cm-10.1.3-l900.zip with md5: ba795d6a4261654648b0eb5cec019021 downloaded from http://wiki.cyanogenmod.org/w/Gapps
has anyone had success with either of these
currently running Android 5.0 Lollipop ROM for Galaxy Note 2! [CM12] downloaded from http://galaxynote2root.com
attempted with both gapps-lp-20141109-signed.zip and LollipopMicroGapps-121914-HighOnAndroid.zip both downloaded from http://galaxynote2root.com
I would prefer to use the aforementioned build because the build I'm running is not compatible with the nightlies
thanks for any responses in advanced.
Click to expand...
Click to collapse
Sorry, I'm probably not the most knowledgeable. If it wasn't for these forums I wouldn't know how to do any of it. I haven't had any issues flashing, but I followed the steps I quoted from the get go and do that every time. Currently I'm back on the last KitKat nightly because Netflix/Play Movies is still not working on CM12. Have you tried any of the CM11 builds? Im currently using:
http://download.cyanogenmod.org/get/jenkins/98444/cm-11-20150118-NIGHTLY-l900.zip
and I use the 20140606 GApps package found here:
http://wiki.cyanogenmod.org/w/Google_Apps#Downloads
The Commish said:
Anyone getting Netflix or Play Movies to work yet on the latest versions? It's the only thing that made me have to revert back to CM11. I tried looking over the change log but honestly I don't know what half that stuff means.?
Click to expand...
Click to collapse
Odd that Netflix and Play Movies don't work. Plex, Amazon Instant Video, MX Movie Player, and Chromecast all work.
Sent from my SPH-L900 using Tapatalk
Deleted

Categories

Resources