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.
Related
Please discuss all CM11 related items here until we get official nighties / another thread from shellnut. Here I will link what we have so far.
******Backup EFS partitions using recovery/freegee!******
---------------
You need the latest clockworkmod recovery. Use Flashify from the Play store to flash. Be sure to READ the installation instructions.
---------------
Download Area. Do NOT forget to read installation instructions:
Clockworkmod Recovery Image (Go to page 4): Clockworkmod Latest Recovery! Click Me!
Flashify: Flashify Play Store Link. Click me!
Downloads (Unofficial from Shellnutt2): Shellnutt2 Unofficial CM11. Click me!
New Official updates; download.cyanogenmod.org
choose LS970
Gapps (Choose CM11): CM 11 Gapps. Click Me!
-----------------------------------------
Working:
Phone Calls
SMS/MMS
Camera (Autofocus Too!) (Camera is only 8 Megapixels though.)
UI
Pretty much everything
Bugs known so far: WiFi is hit or miss. Some people has it working, some do not.
Extra info:
To install, Do the normal.
1. Place Rom/Right Gapps on internal storage
2. Download recovery from link.
3. Use Flashify to flash the new recovery
4. Be sure to backup everything important to you.
5. Did you backup? Good.
6. Backup EFS partitions using recovery/freegee!
7. Wipe normal as you would. Be sure to not wipe internal storage. Wiping system may or may not help.
8. Install rom/gapps
9. Profit. Have fun!
MikeEx Posted:
Shellnut2 has said that we are slated to go for nighties when they officially start.
If your WiFi is giving you "Association rejected" please hop on IRC and get some logcats to Shellnut2
Server: irc.freenode.net
Channel: #lg-optimus-g
Click to expand...
Click to collapse
Also, how to use ART
MikeEx Posted (Couldn't quote or it wouldn't show red on XDA app):
Remove your phone from any case and place in front of a fan where the top front and back receive air flow.
The phone will get extremely hot (80*C+) if left uncooled while ART compiles everything. This could be a total brick hazard.
Having around 200 apps could take well over 10 minutes.
ART will recompile every time you flash a new nightly.
-----------------------
Disclaimer!
No on here takes responsibilty for anything YOU do to YOUR phone. You can not blame us for anything that happens.
---------------------------
All credit here go to its respective Builders/Complilers/Owners. I am merely providing links until official support is given.
Do I have to use CWM to flash this? Has anybody used flashify on our phone? How's Wi-Fi? I'm full of Qs but I'm dying to run a 4.4 that isn't from mako sources.
HdMsTrTeCh said:
Do I have to use CWM to flash this? Has anybody used flashify on our phone? How's Wi-Fi? I'm full of Qs but I'm dying to run a 4.4 that isn't from mako sources.
Click to expand...
Click to collapse
Use CWM, I believe there's an updated version that someone built (it's in the cwm recovery thread towards the last couple pages). Flashify works on LGOG as that's what I used to flash the cwm touch img file. Wifi works on my end. I flashed the 11/30 build and then dirty flashed 12/03 build.
I realize this is probably buggy but is it worth the switch from 10.2 to use as a dd? What if I want to go back? All my backups are TWRP
Use online nandroid backup to make a CWM backup without CWM
Here: https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup
Sent from my Bangin' LS970 on who knows what ROM
HdMsTrTeCh said:
Do I have to use CWM to flash this? Has anybody used flashify on our phone? How's Wi-Fi? I'm full of Qs but I'm dying to run a 4.4 that isn't from mako sources.
Click to expand...
Click to collapse
WiFi is hit or miss for certain people. You must use clockworkmod recovery. I will add links to op here in a min. I use flashify and it worked just fine.
-Whiplashh
"I think a ducks opinion of me is heavily influenced by whether I have bread or not."
Shellnut2 has said that we are slated to go for nighties when they officially start.
If your WiFi is giving you "Association rejected" please hop on IRC and get some logcats to Shellnut2
Server: irc.freenode.net
Channel: #lg-optimus-g
Links up. Thread cleaned up. Have fun.
jblazea50 said:
Use CWM, I believe there's an updated version that someone built (it's in the cwm recovery thread towards the last couple pages). Flashify works on LGOG as that's what I used to flash the cwm touch img file. Wifi works on my end. I flashed the 11/30 build and then dirty flashed 12/03 build.
Click to expand...
Click to collapse
Linked recovery in OP
-Whiplashh
"I think a ducks opinion of me is heavily influenced by whether I have bread or not."
Whiplashh said:
.
Click to expand...
Click to collapse
Hey add a warning to OP for using ART. Red bold letters. something like:
Remove your phone from any case and place in front of a fan where the top front and back receive air flow.
The phone will get extremely hot (80*C+) if left uncooled while ART compiles everything. This could be a total brick hazard.
Having around 200 apps could take well over 10 minutes.
ART will recompile every time you flash a new nightly.
Wifi works fine for me at home but at work it will not connect.
Sent from my LG-LS970 using Tapatalk
Basically everything worked for me except video recording and playback. Try recording a video in snapchat and see what happens.
That said, the camera works better than on the other 4.4 ROMs. No autofocus issues and no weird coloration issues, no capture rate issues either.
MikeEx said:
Hey add a warning to OP for using ART. Red bold letters. something like:
Remove your phone from any case and place in front of a fan where the top front and back receive air flow.
The phone will get extremely hot (80*C+) if left uncooled while ART compiles everything. This could be a total brick hazard.
Having around 200 apps could take well over 10 minutes.
ART will recompile every time you flash a new nightly.
Click to expand...
Click to collapse
Added it. Will add red letters tomorrow.
-Whiplashh
"I think a ducks opinion of me is heavily influenced by whether I have bread or not."
Fresh bacon up!
Sent from my LG-LS970 using Tapatalk
---------- Post added at 10:29 AM ---------- Previous post was at 09:34 AM ----------
Still can't connect to my work wifi after a dirty flash. Going to try clean here in a minute. Strange though how I can connect to some routers but not others.... They are both WPA security
Sent from my LG-LS970 using Tapatalk
Ran the 12/3 build all night last night - dirty flashed up from the latest 10.2 build just for kicks.
Initial boot the OS was just crawling (likely dirty flash issue) - 2nd boot brought everything back to life and been fine since.
Not running ART just yet - need to verify and trim down my 200 app list lol (plus I don't want to lose Xposed just yet)
3G/4G both work great
Wifi worked fine at 3 different locations
GPS worked great
Auto Focus of course works fine
USB Tether works (woot!) and no long kills my phones USB connection when un-tethering (double woot!)
BT worked fine
NFC Works
Audio book played without any audio distortions/glitches (issue in another KK rom)
Google Nav/Maps is still using the wrong voice - an issue I had in the 10.2 build which may have carried over due to dirty flashing. The other KK rom I use uses the correct voice.
Using the PA Gapps Mini-Mod package
Had to reset my battery meter setting since the 10.2 option doesn't exist (yet) in 11 - had me confused for a bit since I had >no< battery meter lol
Aside from having to use CWM, this is pretty dang slick so far.
has the updater been implemented? The one really cool thing I liked about CM
What is ART? Is it optional?
Here's the CWM -6.0.4.5.zip file for the LS970, Uploaded by shellnut
http://www.4shared.com/zip/jULzGS4j/cwm-6045-ls970.html
Here's the stock LG Optimus G camera zip (For AOSP/CM)
http://www.4shared.com/zip/6UeG0pi_/CamCM1018030.html
MMS zip
http://www.4shared.com/zip/ZMj_Eds5/Mms.html
Everything works great, even auto focus.
Today is my birthday, and I flashed my 12/5 birthday build, I couldn't be happier
MikeEx said:
Hey add a warning to OP for using ART. Red bold letters. something like:
Remove your phone from any case and place in front of a fan where the top front and back receive air flow.
The phone will get extremely hot (80*C+) if left uncooled while ART compiles everything. This could be a total brick hazard.
Having around 200 apps could take well over 10 minutes.
ART will recompile every time you flash a new nightly.
Click to expand...
Click to collapse
i've never had these issues myself, but i can see why they would arise. i think a warning or piece of advice should be mentioned stating that if someone plans on using ART, they should enable it immediately upon rom installation, before other apps are installed. that way, optimization isn't as tedious of a process
Derp
Shiny ROM: Android 4.4.4, KTU84P for VZW Galaxy Nexus (Toro)
Skip right to the downloads (if you dare )
Hello there XDA GNex community! I'll admit this is a pretty spontaneous post; I've been building ROMs from the Android Open Source (Project) for awhile now, but I've never "published" any of them. I myself own a Verizon Galaxy Nexus, so I've always built from AOSP to make sure I'm as up to date as possible. Well, that's a little background so let's get going with the overview of the ROM itself:
Overview
This ROM is Android KitKat 4.4.4, build KTU84P. The ROM is built directly from source, that is, the Android source code published by Google available for download to all of us developers. The reason I say the ROM is "OTA-like" is because I make VERY few modifications to it, aside from the things that it takes to get the ROM working. I'll go into detail about those things below, but basically I just want the ROM to make your phone feel stable and shiny and new as if it has just received a new OTA update. That being said, it's clear that the landscape of Nexus devices is changing as new ones are released. Therefore, the other primary goal of this ROM is to keep our Galaxy Nexus as close to the modern Nexus design as possible. This means that I will also add in features that will still be stock, but will also make our phones as close to a current Nexus as possible.
As for how I handle the forum side of things, I'm always open to comments, questions, suggestions, requests, etc. I know that most of those things will often be in the form of criticism, but it's okay, I think I can handle it That being said, I do also have a life and am a college student, so I may not get to come on here ALL the time. I will check back as frequently as possible, and I'm hoping that you guys will help each other out as much as possible! Keep it friendly! So now for the details...
Features
Stock Android 4.4.4, build KTU84P
Source (AOSP) built kernel (boot.img)
Easily rootable (see information below)
G-Apps (GMail, Play Store, etc.) included in build along with Nexus apps
Stock browser replaced with Google Chrome
Shiny restart options - access them by holding down the power button and then long pressing on "Power Off"
All the crazy Google proprietary app stuff has been taken care off
Updated frequently
Everything works!
So what do I mean when I say "Everything works!"?
I'm sure by now you all know that when someone says that, it usually ends up not being true. This ROM is not an exception to that rule, but I can say that I've tested most of the things that would be expected to work in stock Android, such as...
WiFi Tethering (no subscription check)
Bluetooth streaming
Google account sign-in and auto-restore of apps and settings
Google Wallet
Location Services (pretty fast GPS lock in my area also)
Photosphere
Android beam
Photo editing with the new filters
Email
Exchange support
Like I said, the normal stuff (data, voice, hardware acceleration, etc.)
More things that aren't important enough to mention here - check out the changelog for a more comprehensive list
Possible Bugs
It's impossible for me to test for and notice EVERY single possible bug in the operating system, so as of right now I can't say that there are any, although I'm sure you will find some. If you do, report them here!
Other IMPORTANT Information
Root
But wait, nothing in this post said anything about root!!!11!!1!1!!! That's right, my ROM does NOT have root built in! (I don't use any root apps, and it's important to the whole "OTA-like" theme). That being said, the ROM is easily rootable; I made sure of this because I know that many, many of you will use root for many useful purposes. If you want to root the ROM, it's as easy as installing Chainfire's new superuser control app/su with this ZIP file. More detailed information can be found in the "Installation Instructions" section. **NOTE** If you are rooted and upgrading to a new build, you should not have to reflash the rooting flashable ZIP because the ROM will keep root for you.
Updates
Now that the ROM has gotten to this stage, the update policy needs a bit of editing Based on the stats I have access to from the website host and data that I collect myself, it seems like Shiny ROM is currently (as of May 27, 2014) stable for at least 80% of the users who have downloaded it. Based on this, and because the ROM is stock, Nexus-like, it doesn't really make sense to update the ROM as frequently as before. The ROM will still be updated as soon as possible after new versions of Android are released. In between Android versions, I will work on making things 100% stable, although that goal isn't always attainable with older devices and aging hardware support. If we decide to explore other paths for the ROM, you will see many more updates If/when the time comes for me to stop updating Shiny ROM, I will let everyone know in a clear way.
Radios
This ROM will (most likely) work with any toro radios; however, I of course recommend using the most recent, Verizon-approved radios which are the FK01 and FK02 radios. My ZIP installation package for these radios can be downloaded here.
Bootloader
Once again, I'm assuming that this ROM will work with all tuna/toro bootloaders; BUT for optimal experience and performance, use the newest Google-approved bootloader, PRIMEMD04. My ZIP installation package for that bootloader can be downloaded here.
ClockworkMod Recovery
I personally recommend using ClockworkMod Recovery as it has always worked well for me with no quirks. Android 4.2 messed up a few aspects of recoveries because of its multi-user system. ClockworkMod Recovery has been updated to correct some of these issues, and I recommend updating to the most recent version, 6.0.4.3. You can flash either the touch recovery or non-touch recovery image through fastboot OR you can download my flashable recovery update ZIP (touch/non-touch) and flash it in recovery. Check out the installation instructions for more details on this.
Some Other Not-so-important Information
Naming Conventions
All of my ROM ZIP files are automatically generated by my build computer. The file name for all builds up to and including the 11/10/13 build always begins with baldwinguy77_toro_aosp so you know that it's my build for toro. All builds after 11/10/13 begin with the prefix ShinyROM_toro_aosp. That prefix is always followed by the date in mmddyy format (e.g. 112212), a hyphen ("-"), and the time in 24-hour, hhmmss format (e.g. 153945). Finally, all builds end with the "signed" suffix - it just helps me know which packages have finished building and which have not. Hopefully this helps everyone to know which update is newest; I stay away from version numbers because I let Google do all of the version control.
Source
In keeping with the spirit of open-source, all relevant Shiny ROM code can be viewed on Github. I'm not extremely experienced with Github, so bear with me as I learn! Thank you!
File Hosting
I've switched over from using Dev-host to a privately hosted site, graciously and generously given to me by user Goofball. Dev-host is still an amazing service, but it's much more convenient for me to use a privately hosted site, plus I get my own suburl and FTP access! HUGE thanks to Goofball! The private hosting will definitely help me deliver a better experience to you guys as far as downloading goes. You can view all of my uploaded, public files here: http://shinyrom.goofball.org/
Also, if anyone ever wants to mirror for me, please feel free so long as you keep the file name and the file itself intact. As for everyone who downloads from a posted mirror: BE CAREFUL! Always use a virus scanner and be careful with what you are putting on your device!
Installation Instructions (VERY IMPORTANT - Note: You can flash all of these ZIPs in CWM or TWRP*)
*Android 4.4 KitKat builds must be installed using the latest version of your preferred recovery!
ROM
1. Download the latest version of the ROM from the download post. (Also download any other files you will need to install, such as Chainfire's SuperSU Root ZIP, the radios installation ZIP, the bootloader installation ZIP, etc.)
2. Put the file(s) you downloaded in step 1 on your phone's internal storage (sdcard).
3. Turn off your phone.
4. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
5. Use the volume keys to change the arrow until it says "Recovery," then press the power button to boot into recovery.
6. Because of differences in recovery types, I will make the following steps rather generic.
7. Wipe cache.
8. Wipe dalvik cache.
9. If you want to be 100% sure there are no problems, wipe data. If you are coming from another ROM or Android version, wipe data. If you do not wipe data and something goes wrong, repeat this process but wipe data - this step is not necessary if you are simply upgrading.
10. If you are updating your radios, flash FK01_FK02_Radios-signed.zip
11. If you are updating your bootloader, flash PRIMEMD04-signed.zip
12. Flash the ROM (ShinyROM_toro_aosp...signed.zip)
13. If you are rooting, flash Chainfire's SuperSU ZIP file - this step is not necessary if you were rooted on the previous build and are simply upgrading.
14. Reboot your phone, and enjoy!
**Note: If you are simply upgrading to a new version of the ROM and want to keep root, follow the exact instructions above, and do not format /system. It really is not necessary to format /system at any time (unless specifically noted), as the ROM installer has this function built in.
Mods
1. Download the latest version of the mod(s) you wish to install from the download post.
2. Put the file(s) you downloaded in step 1 on your phone's internal storage (sdcard).
3. Turn off your phone.
4. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
5. Use the volume keys to change the arrow until it says "Recovery," then press the power button to boot into recovery.
6. Because of differences in recovery types, I will make the following steps rather generic.
7. Wipe cache.
8. Wipe dalvik cache.
9. Install the mod(s) you downloaded in step 1.
10. Fix permissions (not really necessary)
11. Reboot and enjoy!
**Note: You can remove all mods you've installed by dirty flashing the latest version of the ROM.
ClockworkMod Recovery (Fastboot method - must have an unlocked bootloader and fastboot in your path)
1. Download either the CWM touch recovery image or non-touch recovery image to your computer and rename it to "recovery.img".
2. Power off your phone.
3. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
4. Plug your phone into your computer using the standard USB cable.
5. Open the command prompt/terminal and navigate to the folder where your "recovery.img" is saved.
6. Type "fastboot devices" to make sure your phone is recognized; a serial number should show up on the screen.
7. Type "fastboot flash recovery recovery.img" and wait for the process to complete (should be quick).
8. You're done! Use the volume keys to select "Recovery" and boot into your new recovery!
ClockworkMod Recovery (Flashable ZIP method - easier)
If you are updating your recovery before flashing a ROM, these steps should ALL be completed PRIOR to flashing the ROM.
1. Download either the touch recovery flashable ZIP or the non-touch recovery flashable ZIP.
2. Place the ZIP file downloaded in step 1 on your internal storage/sdcard.
3. Turn off your phone.
4. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
5. Use the volume keys to change the arrow until it says "Recovery," then press the power button to boot into recovery.
6. Choose "Install update from sdcard"
7. Select "Choose file from sdcard"
8. Find the flashable recovery ZIP file you downloaded and install it
9. Back up to the root menu of recovery
10. Select "advanced"
11. Select "reboot recovery"
12. The phone should boot up into your new recovery!
Credits
As with most ROMs, I only did a small part to get everything together. Also, a note that should be made here is that when I am using someone else's file, I ALWAYS host files on the Shiny ROM server to ensure that I don't put any unnecessary stress on their servers. Any file, however, still belongs to and is accredited to its original creator as listed below:
Willyjay - For providing us with lots of amazing and innovative mods for the ROM!
Inmanster - Another great modder who we are fortunate to have here in the thread. He works in collaboration with Willyjay and his mods for many things, but also does some of his own unique mods!
Chainfire - For their SuperSU app and su binary, as well as the convenient ZIP update package, which was previously used and recommended. Check out their website, http://www.chainfire.eu/
Groupers - My new buddy who helped me out with a GPS issue that popped up in 4.2.
Google - Without their amazing staff and willingness to share the source code of their operating system, I wouldn't have been able to build this ROM! Of course, all of the Google apps are theirs, along with the Play Store and system apps. They really are the true owners of all of this.
Samsung - We all may have some mixed feelings about them, but in the end they gave us the amazing, hackable phone that is the Galaxy Nexus.
XDA - By providing such a great Android community, ROMs like this one are able to easily connect with users and get their work out there
Dev-Host - The file-sharing service with virtually no limits on sharing - kudos to them and their hard work. d-h.st
Koush and the ClockworkMod/ROM Manager Team - They make the best recovery that's been around for longest, and their constant updates allow us to keep making ROMs! Also, Koush's recently released open source Superuser control app is the best available and the one linked to in the thread. Thanks Koush! clockworkmod.com
Kevdliu - Huge thanks to this dev and their amazing quick settings mod!
The CyanogenMod Team - For a working implementation of DSPManager on Android which can be ported to any AOSP-based ROM! Without them and Bigwavedave25, the DSP manager mod would not be available! Be sure to thank them and to check out the CyanogenMod website! Also, for their feature-filled version of the stock Messaging app which is available as a mod for my ROM!
bouchigo - a user who has helped to make the CM10 Messaging app available as a mod for my ROM in conjunction with Willyjay for bringing it to my attention.
Schoat333 - A user who helped out Willyjay with the bubble styled MMS mods. The credit for the screenshots to go along with the mods goes to him!
Yarly - The most experienced admin I've ever had the pleasure of talking with, who taught me some new debugging tricks and answered some of my questions.
Razorloves - Another admin who helped me out with a few problems and answered a lot of my questions!
Tiny4579 - A kernel dev who also took the time to talk with me and answer a few of my questions.
Thanks to everyone for their hard work and sharing that work with others!
DISCLAIMER
Come on guys, it's a Galaxy Nexus, to what extent could it really get messed up? Nonetheless, in case someone flashes this then puts their phone in the microwave or something and tries to blame it on me, I am not directly responsible for anything that occurs, either negative or positive, from flashing this ROM to your phone. Despite that, I am posting in the spirit of the Android community, a community that I have embraced and belonged to for several years, and I would never try to hurt any of your innocent, beautiful phones. Also, none of the original source for Android belongs to me, nor do any of Google's apps. All preinstalled applications are property of Google, Inc. and I make no claim of ownership to them.
Okay that's about it! THE ROM DOWNLOAD LINK AND A SUMMARY OF ALL FILE DOWNLOADS CAN BE FOUND BELOW!
ROM Download & Changelog
ShinyROM_toro_aosp_080914-125720-signed.zip
MD5: 5844c6e48fb30bbafc976199c5c1effd
Fixes/Changes Included So Far
(older changes)
6/21/14 CHANGES
Updated to Android 4.4.4, KTU84P
8/9/14 CHANGES
Added system-side support for native screen casting
Added Italian translations for the Shiny restart menu (courtesy of XDA user lparcshinoda)
Switched to prebuilt version of CellBroadcastReceiver in an attempt to fix issues with it on toro
Mods
Before installing any of the packages below, please be sure to check out the mod installation instructions in the OP!
Key
To make mod installation more convenient, all mod links will now be color-coded based on the files they change. The key shows what each color corresponds with:
Red - SystemUI.apk
Blue - framework-res.apk
Purple - SystemUI.apk & framework-res.apk
Green - Other
If you install mods that are in the same color group, it is likely that they will overwrite each other. It is OK to overwrite a previously installed mod, but please note that the originally installed mod will no longer be there. If you want to completely revert to stock, flash the "Back to Stock ZIP" mod under the baldwinguy77 mod section. This mod replaces your SystemUI.apk and framework-res.apk files with ones from the stock ROM.
Developer-specific Mods
All of these mods have been provided by some really awesome mod developers who take the time to continue to make updated mods for my newest ROM builds. That being said, they have lives and can't always get the mods out right away, so make sure the date next to their name matches the build you're running! They usually are around the thread and are open to doing custom mods if you ask Be sure to thank them and check out the credits section for more info!
Baldwinguy77 (Updated for 8/9/14 build)
Back to Stock ZIP - Returns you to the stock version of the ROM by removing SystemUI and framework-res mods.
Stock kernel flashable ZIP - Overwrites any custom kernel you have installed with the stock kernel normally packaged with the ROM.
Inmanster (Updated for 3/9/14 build)
36 DPI Nav. Bar - Replaces the stock navigation bar with a smaller (height-wise), 36 DPI version.
Black Dash-style Softkeys - Replaces the stock navigation bar buttons with black, dash-style ones.
Blue Stock Softkeys - Replaces the stock navigation bar buttons with blue-colored ones.
Carrier Text Replacement - Replaces the carrier text on the lockscreen and pulldown notification shade with "Galaxy Nexus".
Extended Battery Framework Mods - Improve accuracy of battery level reporting for those using extended batteries.
2100 mAh (with Carrier Text Replacement mod)
3050 mAh
3800 mAh
5900 mAh (with No CRT-off Animation mod)
Grey Battery Percentage - Enables display of the current battery percentage in the status bar with grey-colored font.
InmanMod - A combination of the 2100 mAh battery, no CRT-off animation, carrier text, 36 DPI nav. bar, and white zenyth softkeys mods.
No CRT-off Animation - Removes the stock, default CRT-like screen off animation.
White Zenyth-style Softkeys - Replaces the stock navigation bar buttons with white, zenyth-style ones.
Universal Mods & Downloads
These mods have been compiled by myself, sometimes in conjunction with the modders above, to always work with any version of the ROM (but not necessarily any device). Therefore, you don't have to worry so much about these being up-to-date because they should always work. If that is ever not the case, simply PM me and we'll get it fixed This section also includes some other Verizon Galaxy Nexus related downloads such as the latest radios and bootloader. You can use these according to the installation instructions in the OP.
Universal Mods
AOSP Web Browser (for Android 4.4) - Installs the AOSP web browser with Chrome bookmark syncing for Android 4.4.
DSP Manager(for Android 4.4) -Installs the DSP Manager app along with the audio libs and configs important to running the service, allowing you to customize the audio equalizer of your device. At the moment, certain apps on Android 4.4 do not work with the modular DSP service.
ClockworkMod Images
Touch 6.0.4.3
Non-touch 6.0.4.3
ClockworkMod Recovery Flashable ZIPs
Touch 6.0.4.3
Non-touch 6.0.4.3
Chainfire's SuperSU Root Control App and ROOT Flashable ZIP (Works with 4.3 & 4.4)
Download (Latest version, v2.02)
Toro Radios[/size]
FK01 & FK02 Radios Flashable ZIP (Latest)
FF02 & FG02 Radios Flashable ZIP
Tuna Bootloaders[/size]
PRIMEMD04 Bootloader Flashable ZIP (Latest)
PRIMELC03 Bootloader Flashable ZIP
Thanks for your roms, they have been the daily driver on my wifes GN since you started posted them way back when.
I've been using this ROM for the last couple of builds (including latest 2/9) and since flashing the ROM I'm sometimes unable to receive phone calls when the phone is plugged into a wall charger.
The first flash I wiped everything, though latest was only cache. I'm using the 4.2.2 (JDQ39) LTE FK01/CDMA FK02 Radios.
Any ideas?
kielby said:
I've been using this ROM for the last couple of builds (including latest 2/9) and since flashing the ROM I'm sometimes unable to receive phone calls when the phone is plugged into a wall charger.
The first flash I wiped everything, though latest was only cache. I'm using the 4.2.2 (JDQ39) LTE FK01/CDMA FK02 Radios.
Any ideas?
Click to expand...
Click to collapse
Are you sure it's only when plugged into a wall charger? If that's true, it sounds like a hardware issue, but I think you probably just happened to notice it at that time. You may want to try out the 1/4 build as that one seems to work well for people with mobile data-related problems in the newer builds.
kielby said:
I've been using this ROM for the last couple of builds (including latest 2/9) and since flashing the ROM I'm sometimes unable to receive phone calls when the phone is plugged into a wall charger.
The first flash I wiped everything, though latest was only cache. I'm using the 4.2.2 (JDQ39) LTE FK01/CDMA FK02 Radios.
Any ideas?
Click to expand...
Click to collapse
How did you flash the radios? Also are you using any mods/3rd party kernels? First step in fixing radio issues for me is to restore back to stock - this makes sure good radio files get installed then after allowing to settle for 24 hours I flash back to a custom Rom then checking without installing any mods for a day.
If unsure that radios flashed cleanly or having strange signal issues that make no real sense it is a good idea to try stock install.
hotrodwinston said:
How did you flash the radios? Also are you using any mods/3rd party kernels? First step in fixing radio issues for me is to restore back to stock - this makes sure good radio files get installed then after allowing to settle for 24 hours I flash back to a custom Rom then checking without installing any mods for a day.
If unsure that radios flashed cleanly or having strange signal issues that make no real sense it is a good idea to try stock install.
Click to expand...
Click to collapse
I flashed the zip files from this thread using CWM before flashing the ROM the first time. I'll try going back to stock for a couple of days to see if it fixes the issue.
To the previous poster, I'm pretty sure it's related to charger somehow. My wife started complaining that should couldn't reach me on my cell during the work day (hmm is this a *feature* or a bug?!). I was sitting at my desk during those times with my phone plugged in. I tried calling the Nexus from my desk phone and it wouldn't ring until I unplugged it. It only started after I flashed the new radios and ROM.
Thanks guys.
kielby said:
I flashed the zip files from this thread using CWM before flashing the ROM the first time. I'll try going back to stock for a couple of days to see if it fixes the issue.
To the previous poster, I'm pretty sure it's related to charger somehow. My wife started complaining that should couldn't reach me on my cell during the work day (hmm is this a *feature* or a bug?!). I was sitting at my desk during those times with my phone plugged in. I tried calling the Nexus from my desk phone and it wouldn't ring until I unplugged it. It only started after I flashed the new radios and ROM.
Thanks guys.
Click to expand...
Click to collapse
By the way I reflashed the 4.1.1 (JRO03O) radios from radio thread without changing anything else and the problem seems to have gone away.
What kernel should I use with this ROM to get the best performance/battery life combo. Link please!
Sent from my 2013 Kindle Fire HD
Is an upgrade to KVT in the works?
UPDATE -- I'm running the latest version with the latest franco and Xposed Framework and - wow. Rock stable, fast and melted chocolate smooth (boom - trademarked.) I don't know why I haven't done this sooner. This is all I need for awhile. Truly happy with my GNex at this moment haha.
RoxRedEye said:
Is an upgrade to KVT in the works?
UPDATE -- I'm running the latest version with the latest franco and Xposed Framework and - wow. Rock stable, fast and melted chocolate smooth (boom - trademarked.) I don't know why I haven't done this sooner. This is all I need for awhile. Truly happy with my GNex at this moment haha.
Click to expand...
Click to collapse
Hey there! I'm sorry, somehow I missed your post earlier! Anyways, glad to hear you're liking the ROM so much There is an updated build available as of today so check the download post. More info is coming in a few seconds
3/9/14 Build Information
Hey there everyone! It seems like it's been awhile since the last time I got make one of these new build posts, and I have to say it feels good to be able to do it again! I first have to apologize for my absence both in terms of development and communication in the thread. I'm getting close to the end of my sophomore year in college, and let's just say it has been keeping me extremely busy. I don't mind it, but I just wish it still left more time for me to do Android-related things! Luckily, I had a whole week off to catch up on a lot of things, including Shiny ROM development. So with that, we have a new build ready to go that includes a very minor update to the AOSP base of the ROM as well as some not so minor updates to the telephony stack. What this means is that mobile data and voice performance/reliability may have some big improvements in this build. We didn't get a chance to do a wide-scale test with these changes, and they're only in the master branch of AOSP, but after reviewing the code I'm hopeful that they'll bring improvements for us. That being said, be sure to leave your feedback here on the thread so we know how it's working! If you experience any problems, try to grab a logcat and let us know about them so we can try to get everything straightened out! So after reviewing the other information and installation instructions below, head over to the download post to grab the new build!
I also want to take this opportunity to point out that Shiny ROM has a new website! For now, the URL/domain is still http://shinyrom.goofball.org/ to stay consistent. The website has a lot of information about Shiny ROM as well as some future plans. It also lists details for the newest build of Shiny ROM along with download links, etc. I'm hoping that this website serves as a good platform for Shiny ROM to grow as we can now deliver a lot of information without having to worry about it getting buried in the forum and whatnot. So check that site frequently for Shiny ROM news and updates as well as information about new builds! There is also a contact form there for everyone to leave their suggestions, report bugs, etc. I hope you all like it!
(You can still access all of the Shiny ROM files here.)
Thanks to everyone for your continued support of myself and Shiny ROM!
Installation Instructions
Download desired ZIP files (ROM, SuperSU*, mods, etc.) and place on internal storage.
Reboot to the latest version of your preferred custom recovery (CWM or TWRP).
Wipe cache.
Wipe dalvik cache.
**OPTIONAL** Wipe data/factory reset (will erase user data like apps and saved games, etc., but may fix strange bugs).
Flash ROM.
**OPTIONAL** Flash other desired ZIPs (SuperSU, mods, etc.).
Reboot.
Enjoy!
*As of 3/9/14, the latest version of SuperSU is v1.93.
baldwinguy77 said:
Hey there! I'm sorry, somehow I missed your post earlier! Anyways, glad to hear you're liking the ROM so much There is an updated build available as of today so check the download post. More info is coming in a few seconds
Click to expand...
Click to collapse
No worries. Thanks for the reply and thank you for your hard work bringing us a stable stock KitKat. Glad I have extra batteries with me - gonna download and flash asap.
Hey @baldwinguy77, can't access rootz right now, but was systemui.apk updated for today's build? I have a home cooked mod from last version that I'd like to use. Thx
ART isn't sticking when I change from dalvik. I flashed on top of the last build. Did not do a full wipe yet.
Sent from my Galaxy Nexus using Tapatalk
asilentcivilian said:
ART isn't sticking when I change from dalvik. I flashed on top of the last build. Did not do a full wipe yet.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
full wipe did the trick. thanks for keeping this ROM alive!
Sent from my Galaxy Nexus using Tapatalk
klobkelosh said:
Hey @baldwinguy77, can't access rootz right now, but was systemui.apk updated for today's build? I have a home cooked mod from last version that I'd like to use. Thx
Click to expand...
Click to collapse
Hmmmm I would just give it a try, I think it will probably work fine especially if it only modifies SystemUI
asilentcivilian said:
full wipe did the trick. thanks for keeping this ROM alive!
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Glad to hear it! Thanks for your support!
baldwinguy77 said:
Hmmmm I would just give it a try, I think it will probably work fine especially if it only modifies SystemUI
Click to expand...
Click to collapse
Yes it worked fine, thanks for the response. Unfortunately, this build is not very nice to my battery
klobkelosh said:
Yes it worked fine, thanks for the response. Unfortunately, this build is not very nice to my battery
Click to expand...
Click to collapse
Glad to hear it! I would give it some time before making any conclusions; charge it up tonight, grab it in the morning and see how it is with normal use
If you want, you can put the APN refresh delay back to its value from the previous build. To do this, you need to be rooted so that you can edit the build.prop. You simply have to remove this line:
Code:
persist.radio.apn_delay=5000
I don't think it should be making a big difference, but that's the only change that could (in theory) have some effect on battery life. Of course, removing that line may come at the price of having longer/trickier data handoffs. Unfortunately, Verizon's network certainly isn't making it easy for us to give everyone good battery life and good data handoffs
baldwinguy77 said:
Glad to hear it! I would give it some time before making any conclusions; charge it up tonight, grab it in the morning and see how it is with normal use
If you want, you can put the APN refresh delay back to its value from the previous build. To do this, you need to be rooted so that you can edit the build.prop. You simply have to remove this line:
Code:
persist.radio.apn_delay=5000
I don't think it should be making a big difference, but that's the only change that could (in theory) have some effect on battery life. Of course, removing that line may come at the price of having longer/trickier data handoffs. Unfortunately, Verizon's network certainly isn't making it easy for us to give everyone good battery life and good data handoffs
Click to expand...
Click to collapse
I'll take that under consideration, but man it was really killing me. Following new rom flash, for everything set up, charged up to 100 percent. Good. Drive to dinner, 30 mins, in and out of 4g and 3g, battery at 80 percent. After 2 hour dinner on 3g, 60 percent. Back home 40 percent, lots of hand offs. She's nearly dead now and I haven't even used her tonight. I love this ROM, but she's not right...
Q&A for [ROM] [4.4.4] [Sep-21] CyanogenMod 11.0 M10 | KitKANG | v1.0 | ART | STABLE
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] [4.4.4] [Sep-21] CyanogenMod 11.0 M10 | KitKANG | v1.0 | ART | STABLE. 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!
insufficient space
Thanks for this... the ROM flush is working perfectly, but I am unable to flash gApps.
I am installing the Nano GApp
I keep getting "Insufficient storage space available..." .
you need 122418 KB system free space...
you only have 15916 KB available
what am I doing wrong and why do I have such low memory space after clean install?
Any help would be appreciated...
DevoOved said:
Thanks for this... the ROM flush is working perfectly, but I am unable to flash gApps.
I am installing the Nano GApp
I keep getting "Insufficient storage space available..." .
you need 122418 KB system free space...
you only have 15916 KB available
what am I doing wrong and why do I have such low memory space after clean install?
Any help would be appreciated...
Click to expand...
Click to collapse
After flashing rom, boot rom. Then install A2SD from terminal, then reboot rom. Reboot into recovery to finally flash Gapps.
Sent from my Nexus™4 ?
thank for the quick reply
installed a2sd, rebooted. It show me messages after reboot that is processing applications.
when done rebooted to recovery mode (4EXT) and flushed GApp.
i get the same message. Exactly the same "you only have 15916 KB Avaialble"
any idea?
DevoOved said:
thank for the quick reply
installed a2sd, rebooted. It show me messages after reboot that is processing applications.
when done rebooted to recovery mode (4EXT) and flushed GApp.
i get the same message. Exactly the same "you only have 15916 KB Avaialble"
any idea?
Click to expand...
Click to collapse
Try to remove ART inside the rom.zip as described in the last post: http://forum.xda-developers.com/showthread.php?t=2549776
And then flash again. *fingers-crossed*
Sent from my Nexus™4 ?
Thanks for this spezi.. However, I do not think this will solve my problem
i installed ES explorer and was able to remove ART files but it is a drop in an ocean. flashing Gapps still fails with the same message, but now it says i have a little more internal space ~20mb while it requires 122 gor GApps
the interesting part is that in the settings, the internal storage says i have 180MB free
see attachment
DevoOved said:
Thanks for this spezi.. However, I do not think this will solve my problem
i installed ES explorer and was able to remove ART files but it is a drop in an ocean. flashing Gapps still fails with the same message, but now it says i have a little more internal space ~20mb while it requires 122 gor GApps
the interesting part is that in the settings, the internal storage says i have 180MB free
see attachment
Click to expand...
Click to collapse
Uuh. Solution is easy. Just use spezi's slim gapps which is linked in rom thread.
Good luck and good night!
Sent from my Nexus™4 ?
trackball wake/proximity sensor
So, I have the proximity sensor problem so many people have and recently installed KitKang and would love to stick to this rom if possible. But my trackball wake isn't working to bring the phone back, as it did on one of the Mildwild ROMs (I forget which one). I've tried Proximity Screen Off Lite, but its hit or miss. It always goes black no matter what, and only sometimes will then snap back to having the phone controls. I have selected end call with power button, so at least now I can leave voicemails without the sound of me pulling out my batter to end the call, but obviously I have no access to the number pad, so any call where I have to press 1 or whatever, obviously I can't do that.
I would love it if someone had a solution for this. The KitKang rom seems to be totally useable with the apps I need, so if I could just get the trackball to wake up the phone during a call, I'd be golden. Or just totally disable this sensor, either would work for me...
Many thanks in advance!
Black Blocks
Hiho,
this ROM is amazing, Android 4.4.4 working on a four years old device!
Unfortunately I have some trouble with graphic failures (black blocks) in different browsers (Dolphin, FF, built in browser). The same with the "Spiegel Online" app, which is nothing than a html parser. If there are these black blocks, there is a high chance that the phone freezes or more graphic failures occur.
Is there a fiix for this problem? Am I the only one?
If it is helpful I will post a video of these failures.
Greets,
Murphy
<edit> I just remembered: I had the some problem with Carbon ROM, which launcher I use does not matter.
Reboot loop
I used 250 for system in hboot, as suggested. However, my phone is always in a reboot loop sometimes with vibrations, sometime snot. As soon as the 'Starting apps' popup appears, it reboots. I've tried full wipe + rom +gaps - reboot, as well as full wipe + rom- reboot. Nothing works. Also the Alpha jellybean hboot link in the main thread doesn't lead to it. I found another one, but that doesn't work as directed and gives an error. Had to use an alternate way to modify hboot...the swiftbootloader.zip method...My bootloader is unlocked.
Hello,
when browsing the Google Play Store with the HTC Desire CyanogenMod 11.0 M10 + GApps by spezi77, some apps can't be installed. Why is that?
For example, the Google Play Store reports Mozilla Firefox and Tetris Blitz as being incompatible with the phone (HTC Desire CyanogenMod 11.0 M10 + GApps by spezi77).
Why is that? And is there a workaround for this?
Also:
Will the ROM be upgraded to CyanogenMod 11.0 M11?
And, I am wondering:
When a CyanogenMod 11 update is being released, like from M10 to M11 for example, do you need to perform a full wipe again (i.e. uninstall M10) and then flash/install M11? Or can you simply flash/install M11 over M10?
Regards
spezi77 said:
After flashing rom, boot rom. Then install A2SD from terminal, then reboot rom. Reboot into recovery to finally flash Gapps.
Sent from my Nexus™4 ?
Click to expand...
Click to collapse
I tried everything again from scratch, downloaded everything again as well and somehow after the 4th or 5th time it worked. I now get the same problem he's talking about...low on space...even though I followed your instructions and used 250mb for system. It said that if you use this, then you can install the gapps directly after the rom, which is what I did. Did A2SD install afterwards. I hope this issue can be managed in a more efficient way, kinda sucks to have potential in a phone to be a smartphone...but not really able to do anything smart
Thank you for the rom!
Issue with Wifi Tethering (KitKANG v1.0 / CM11 M10 - HTC Desire)
Hi spezi77,
i installed the KitKANG v1.0 / CM11 M10 UNOFFICIAL on my HTC Desire, thanks for this great ROM!!
Unfortunately i have the issue that Wifi Tethering is not working properly. Means, i can only connect with clients when Security is disabled, but once i enable WPA or WPA2 it's not possible to connect. Before ROM Installation i did FullWipe and formatted all partitions.
Is this a known issue?
Many Thanks in advance!!
Cheers
htc help needed
I am unable to boot into recovery even when pressing down the down vol key and pressing power button.
I am starting to have issues with htc desire , and wanted to wipe rom and start again but am unable to access recovery....
any help or ideas appreciated.
htc_desire_luke said:
I am unable to boot into recovery even when pressing down the down vol key and pressing power button.
I am starting to have issues with htc desire , and wanted to wipe rom and start again but am unable to access recovery....
any help or ideas appreciated.
Click to expand...
Click to collapse
Try vol up.
Sent from my HTC Desire S using XDA Free mobile app
No ...that didnt work either...got evervolv rom at mo but have been no more updates so am trying to boot into recovery, but in just goes straight to boot., also touch screen seems not to be responding.
am just a bought to buy Samsung galaxy s3.
htc_desire_luke said:
I am unable to boot into recovery even when pressing down the down vol key and pressing power button.
I am starting to have issues with htc desire , and wanted to wipe rom and start again but am unable to access recovery....
any help or ideas appreciated.
Click to expand...
Click to collapse
Can you still access the phone via USB adb? ROM doesn't have to fully boot for that. Then you can reboot into recovery. Or if you get into fastboot mode you can also boot recovery.
Just got "Process system isnt responding- do you want to close it Y/N
but touch screen isnt working properly so doesnt register.
I can not access phone via USB either.
I removed everything I could from system and have now 23 MB free space. Still cannot install gapps, even the smallest pico variant. If anyone could help me please ...
The installer log is attached. Thank you very much in advance!
spezi77 said:
My slim gapps is perfectly aligned for kk roms. It will in total occupy ~18 mb of the system partition.
Edit: There is no magic. The slim gapps installer script frees up ~8mb by deleting:
"/system/app/Email.apk",
"/system/app/Exchange2.apk",
"/system/app/Camera2.apk"
Those apps will later be replaced with the google variants which go below /data.
Let me summarize that:
it is safe to flash my slim gapps package on a kk rom with only ~12mb left on the system partition.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Natural_born_chilla said:
I removed everything I could from system and have now 23 MB free space. Still cannot install gapps, even the smallest pico variant. If anyone could help me please ...
The installer log is attached. Thank you very much in advance!
Click to expand...
Click to collapse
Per Spezi's post, use his gapps. Download link is just below the ROM download.
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
By request, I have made my own LineageOS 13.0 thread. I will work on this when I have time during the evenings and after work.
Thanks
Exynos5420 Dev Team ( @deadman96385 @thompatry @ZakooZ @Orion116 @mosimchah @joshndroid @Andmoreagain @thermskin, @javelinanddart )
@Valera1978 - Setting up the initial build and getting it to device work
@deadman96385 - For continuous support on helping me make a better ROM
@ZakooZ and @javelinanddart - For helping me fix the Camera
@deadman96385 and @javelinanddart - For helping me fix the IR blaster
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Do not ask for ETAs. If you do, I will ignore you and your post.
SEANDROID ERROR
If you see a message at boot about Recovery or Kernel is not SEANDROID Enforcing, you can ignore it. This is just telling you that you are not running Samsung stock software. It has no effect on recovery or the ROM itself nor related to either.
Instructions
1. Install custom recovery Link
1.*I have built a new version of TWRP with the MM kernel. MTP, Vibations, ADB now work and there are performance increases. The rom will need to allow v1awifi naming for flashing in recovery. Link
2. Download the zip(s) - ROM and Google Apps additional package (optional)
3. Backup all partitions in TWRP - this will be your recovery point if things don't install correctly.
4. Full wipe all
5. Flash ROM
6. Flash GApps
Note: Please make sure you have a Lollipop bootloader. Below are the steps to flash it.
Known Issues
Lower than stock audio volumes
MHL out to TV not working
Nightlies
Latest Nightly Date: 12/23/16
Device Builds
GApps
http://opengapps.org/
Platform: ARM
Android: 6.0
Bootloader Information
You need to make sure you have a lollipop bootloader installed or else your device won't boot. Here you can go grab the latest bootloader and odin and flash it in download mode. Read all the steps before you do this.
Make sure you have a full backup because just in case you something fails.
Here are the steps to flash this via ODIN:
Reboot your tablet into download mode. Do this by first switching off the phone, then pressing and holding the volume down + home button together and then pressing the power button. Press volume up button to enter download mode.
Open ODIN on your computer. You’ll see the ID:COM box turning yellow with a COM port number upon successful connection with the tablet.
In ODIN click the BL button, select the bootloader firmware. It's a tar.md5 file.
Make sure Auto Reboot & F. Reset Time options are selected in ODIN
Click on the start button. When the process is completed your phone will reboot.
Sources
In the readme file (see device tree) all instructions for build.
LineageOS: https://github.com/LineageOS/
Device: https://github.com/exynos5420/android_device_samsung_v1awifi
Kernel: https://github.com/exynos5420/android_kernel_samsung_exynos5420
Vendor: https://github.com/exynos5420/proprietary_vendor_samsung
Over clock?
Hi Thom,
want to know if you are able to make this kernel ready for over clock. Further I use Valera s 5.11, which one is faster this or Valera's 5.11. I know that marshmallow are in generally slower then 5.11 so will it make sense to change. I have some applications + movies which do not play/work fine, need a little more performance in GPU and cpu.
Thanks for supporting this device, I love this tablet
Deltabravofoxotango said:
Hi Thom,
want to know if you are able to make this kernel ready for over clock. Further I use Valera s 5.11, which one is faster this or Valera's 5.11. I know that marshmallow are in generally slower then 5.11 so will it make sense to change. I have some applications + movies which do not play/work fine, need a little more performance in GPU and cpu.
Thanks for supporting this device, I love this tablet
Click to expand...
Click to collapse
This rom is really fast. Like faster than 5.1.1. I am still making changes and it is speeding up by the day. I would almost say it is stable and fast enough for videos and apps that you trying to run. Try tonight's nightly and give it a shot and let me know what your thoughts are.
Yes, I was hoping there's a list of launchers compatible with CyanogenMod. I always used Nova Launcher pre-root, but post-root post-adding CM, it crashes constantly to the point of unusability. But I'm not fond of the default launchers included so as I said, I was hoping there's a list somewhere. Thanks.
Thank you for the ROM. YouTube and .gif files aren't working properly in the latest nightly. Used Micro Gapp install. Also web pages very laggy, especially ones that contain a lot of ads.
Just thought I'd report that I installed the latest (4/26) over the top of the earlier april version via a "dirty" install (no wipe). Also installed the latest open gapps stock version with no error message after reboot. That's it so far...
ElsaReyes said:
Yes, I was hoping there's a list of launchers compatible with CyanogenMod. I always used Nova Launcher pre-root, but post-root post-adding CM, it crashes constantly to the point of unusability. But I'm not fond of the default launchers included so as I said, I was hoping there's a list somewhere. Thanks.
Click to expand...
Click to collapse
What device are you on? All these problems you have is not normal. Sure you're on the P900 wifi? I haven't come across one single app ,including launchers, that don't work with this ROM.
i have a problem for downloading the latest build. The link in this forum give me only 3 old builds of the rom. When i use the old link from the old post i can download the 26 apr build. I have downlaoded that one (is the same?) and installed it with latest gaps and so problems so far
thompatry said:
This rom is really fast. Like faster than 5.1.1. I am still making changes and it is speeding up by the day. I would almost say it is stable and fast enough for videos and apps that you trying to run. Try tonight's nightly and give it a shot and let me know what your thoughts are.
Click to expand...
Click to collapse
It's a completely new ROM @thompatry Much snappier and very smooth. No prob with new Gapps and setup wizard. All in all a very promising ROM. Thanks a million!
Hi I installed your latest cm 13 on my sm-p901 and it's very smooth and fast ! Thanks so much ! But I have problem with sound ! When I change the volume with up/down key , tablet freezes for a sec or when I go to settings-sound , tablet freezes, keyboard kepress sound has latency for example , what's wrong with sound ?! Thanks so much again for bringing MM to exynos variant! ?
Edit : I can't play audio files too !! What could it be related to ?? Gapps maybe?! Does anybody else have audio problem?!
Sent from my Nexus 5X using Tapatalk
thools60 said:
What device are you on? All these problems you have is not normal. Sure you're on the P900 wifi? I haven't come across one single app ,including launchers, that don't work with this ROM.
Click to expand...
Click to collapse
Yep, P900 wifi.
It's not the app though, or the rom, or any of that. It's me, technology has always and will always take a sick ammount of pleasure in royally screwing me over in all things everyone else manages perfectly fine.
But if it's me, even if I do exactly as everyone else does, the computer will probably explode in my face.
ElsaReyes said:
Yep, P900 wifi.
It's not the app though, or the rom, or any of that. It's me, technology has always and will always take a sick ammount of pleasure in royally screwing me over in all things everyone else manages perfectly fine.
But if it's me, even if I do exactly as everyone else does, the computer will probably explode in my face.
Click to expand...
Click to collapse
Did you wipe everything clean before you installed?
thools60 said:
Did you wipe everything clean before you installed?
Click to expand...
Click to collapse
Not the files. But Factory Reset, Wipe - Davik, Cache, System, whatever that fourth one listed was called.
ElsaReyes said:
Not the files. But Factory Reset, Wipe - Davik, Cache, System, whatever that fourth one listed was called.
Click to expand...
Click to collapse
Can you save you files on a flash or something?
thools60 said:
Can you save you files on a flash or something?
Click to expand...
Click to collapse
Yeah, but would that even make any difference? It takes like 10 hours to get everything back on, transfers slow, and I'd rather avoid that if this might not even work.
ElsaReyes said:
Yeah, but would that even make any difference? It takes like 10 hours to get everything back on, transfers slow, and I'd rather avoid that if this might not even work.
Click to expand...
Click to collapse
Well, if your device isn't broken in some way, I guess thats the only way to fix it.... You haven't thought about keeping your files in the cloud? 100gb Storage on Google drive is about 2 bucks a month
Anyone managed to get xposed to work? I tried a lot of builds of the app and of the binairy, but every time I open xposed and I click on something, I get a black screen and I need to restart to get my tablet working again.
The new version is very fast. I am, however, having issues with Chrome playing back media (video) and in fact while using youtube got an error message that Android was having trouble playing media. Sometimes it will play video... but often it will not.
Anyone else having that issue, or should I wipe this baby and do a clean install?
shonkin said:
The new version is very fast. I am, however, having issues with Chrome playing back media (video) and in fact while using youtube got an error message that Android was having trouble playing media. Sometimes it will play video... but often it will not.
Anyone else having that issue, or should I wipe this baby and do a clean install?
Click to expand...
Click to collapse
Same here. It's the same issue with play music. Tried everything. Clean install. Full Gapps and second time Pico Gapps and downloaded Play music from Play store. And no go. Installed older build and voila, works again. Must be ROM related.
shonkin said:
The new version is very fast. I am, however, having issues with Chrome playing back media (video) and in fact while using youtube got an error message that Android was having trouble playing media. Sometimes it will play video... but often it will not.
Anyone else having that issue, or should I wipe this baby and do a clean install?
Click to expand...
Click to collapse
thools60 said:
Same here. It's the same issue with play music. Tried everything. Clean install. Full Gapps and second time Pico Gapps and downloaded Play music from Play store. And no go. Installed older build and voila, works again. Must be ROM related.
Click to expand...
Click to collapse
I have problem with sounds too , for example when you go to settings - sound , tablet freezes for a sec , or I can't play music , there is a problem with media !
Sent from my Nexus 5X using Tapatalk