CM7.2 Pons
Goo.Im Download for Kangs
Dev-Host Mirror
(updated only on request)
MediaFire Mirror
(updated only on request)
Changelog
Gapps
Gapps Mirror
Merged Commits for Gingerbread
Open Commits for Gingerbread
CyanogenMod 7 for the HTC Incredible :: V7.1.0 (9 Oct 2011)
Credits/Thanks
All credit goes to Cyanogen and the rest of the CM team, and especially our HTC Incredible maintainers, as listed by the CyanogenMod site: jistone (aka CUViper/This Guy), slayher, and of course, koush, as well as the authors of the respective open commits.
Why a new the thread? The build bot has retired (as far as CM7 nightlys are concerned), and the current thread at [ROM] CM7.2 Nightlies for the Droid Incredible was designed with the official nightlys in mind. It has since deviated from that original aim, and to keep it from going off topic any further, I have created this thread.
For some reason, I have received several requests to put a donation link in my profile. You can always donate to the CyanogenMod project, but if you feel you HAVE to donate to me, I've put a link in my profile, and all donations will go towards upgrading my computer, so I can stay on top of this for CM9.
Changelog
In case you missed it the first time.
Known Issues/Bugs
Per slayher: "Sometimes things are going to break, sometimes features are going to be removed, then added, then removed, then added back."
Just because it works in one build, doesn't mean it's going to work in the next.
TV-Out doesn't work on CM7 or any AOSP ROM
720P video recording
Theme Chooser causing WL widgets to disappear
FAQ
Q: What's the ETA on....about how long till...when can I expect....?
A: The only rule of CyanogenMod: You don't ask for ETAs.
Q: Now that the Ice Cream Sandwich SDK has dropped, we're getting a port, right?!
A: Take a look at this PSA by Keyan Mobil
Q: What's this CM7.2, Android 2.3.7 business?
A: The kangs are built towards CM7.2, which is Android 2.3.7.
Q: How do I install a CM7.2 kang, coming from non-CM7?
A: The safest (definitely not the only, but my preferred) way is
Download kang from link
Reboot into recovery.
Make a backup/nandroid (to be safe)
Format system and boot under mounts
Wipe Data/Factory reset
Install zip from SDCard
Flash kang.
Flash Gapps (if this is your first time flashing a kang/CM7
Reboot
Enjoy
If any of you have data that you must absolutely save, then and only then should you use Titanium backup (or other backup apps) to restore your data. Please be sure not to restore any data to /system using these apps, as this will mostly likely corrupt your ROM.
Q: How do I update/flash these kangs?
A: The safest (definitely not the only, but my personal) way is
Download kang from link
Reboot into recovery.
Make a backup/nandroid (to be safe)
Wipe Cache
Wipe Dalvik
Install zip from SDCard
Flash kang.
Reboot
Enjoy
Q: How about that 720P? I hear it's handy.
A: Per slayher, "720P recording will not be coming to CM7 at this time. We *MAY* see it later if we get an HTC GB leak, using an MSM device (aka not omap). But for now, if you HAVE to have 720P recording, stick with CM6. The issue is that GB uses stagefright, and the hack it took to get 720p in CM6 wont work with stagefright. (it was done in opencore.) This is why we cant get it. The current driver implementation we have to work with is just not capable. So there you go, you can stop wondering/asking/hoping."
Q: How about CWM3/5? I'm having a problem where....
A: Try deleting the current recovery first.
Q: How do I fix the space error that pops up when I try to install some apps?
A: Per slayher, "If you get a Space error trying to install apps, just try installing again. I have encountered this error also and it is not related to actual free space, (unless you have a cubic crap ton (crapton * crapton * crapton) of apps installed)."
Q: How do I disable the shutter sound?
A: Per mattyg151, "I used root explorer to rename /system/media/audio/ui/camera_click.ogg to camera_click!.ogg ... no more camera shutter sound."
There is also an option at Menu > Settings > CyanogenMod setting > Sound > Mute camera shutter
Q: How do I increase the WiFi scan time to save battery life?
A: Per karnovaran, "One way to reduce battery drain is to increase the WiFi scan interval. It's set to 45 seconds, meaning it will scan every 45 seconds. If you change it to something like 90, obviously it will scan less often and use less battery. To do this, you have to edit the build.prop file in /system. The easiest way is with Root Explorer. Go to /system, mount r/w, open the build.prop in text editor and locate "wifi.supplicant_scan_interval=45" Change that value to 90 or whatever you want. Save the file, mount back to r/o, and reboot."
Q: Those automatic brightness settings are confusing. Anyone know of a good setting/rough guide?
A: This thread looks useful. So does this post
Q: How does that brightness slider thingey-majib work?
A: Per byrong "For those of you trying to figure out the new brightness-adjust-via-statusbar feature, do the following:
1. Settings > CM Settings > Interface > Status Bar Tweaks > StatusBar brightness (I'm guessing you guys already figured this part out)
2. Here's the trick: place your finger on the status bar, but don't drag it down. It will still 'peek' out some, but now you'll want to slowly drag your finger to the left or right while keeping it on the status bar itself. If you drag left, the screen will get darker; right for bright."
Q: I can't send no fancy mms picture messages!
A: Change you APN settings manually, (a popular way is to use GoSMS).
MMSC: http://mms.vtext.com/servlets/mms
MMS proxy: leave empty
MMS port: 80
Any more I should add? Let me know.
Sweetness. Thanks, Pons!
Clean and organized.
Redid the changelog that I use to keep track of the open commits. Linked it to a public viewable google document so I only have to maintain one across different sites.
Let me just say it was painful copying and pasting the thread from Rootz to here. Even after I tidied it up for xda's forum, it still looks terrible to me, especially compared to Rootz. XDA needs to switch forum software.
Thanks for putting these together! Been wanting to go back to something AOSP; this is a great way to get into it.
You're the man! Thanks so much for setting this up and maintaining for us. Your kangs are dope! Just wanted to say thanks man!
Thanks man.
-My life is a shooting range, people never change-
Great idea devoted thread for the kangs. Honestly I did not know you were doing that and I was using #258 still. Who knows what small differences I'll never notice I am missing. Time to flash.
I had to upgrade to a nexus but now I can unleash my Dinc from Verizon and "phone" duties.
I hope this isn't a dumb question, but what are Commits, and what is the difference between merged commits and open commits?
I've been running one of the kangs for a few days now and I love it. I was just curious because I see the survey at the top of the page and a couple links about commits, but I don't know what they are and after just a quick search I haven't found anything.
BlankDEP said:
I hope this isn't a dumb question, but what are Commits, and what is the difference between merged commits and open commits?
I've been running one of the kangs for a few days now and I love it. I was just curious because I see the survey at the top of the page and a couple links about commits, but I don't know what they are and after just a quick search I haven't found anything.
Click to expand...
Click to collapse
CyanogenMod goes through a review process, where anyone can submit code. The code submitted is called a commit. If it passes scrutiny and works, it gets merged into the official CM repository. This approved commit is called a merged commit. All official nightlys (and RC's and stables when they get to that point) only have merged commits.
An open commit is a change to the code that is currently being reviewed and hasn't been approved to be included in the next CM...yet, or ever for that matter. Some open commits get merged eventually (either as they are, or after they've been updated a time or fifteen), other open commits get abandoned. Some users like the additional functionality of these open commits, at the potential cost of stability.
I've started releasing kangs two at a time. One completely stock with only merged commits (just like the official CM7 build bot would have done, may it rest in peace), and the next kang with the same amount of merged commits, plus some interesting looking open ones (most have been requested by users, other merely look like they won't make your phone explode).
And don't hesitate to ask questions, at least after a quick google search.
Pons do you know why we don't have TV out yet? We have kernel source now I thought.
PonsAsinorem said:
CyanogenMod goes through a review process, where anyone can submit code. The code submitted is called a commit. If it passes scrutiny and works, it gets merged into the official CM repository. This approved commit is called a merged commit. All official nightlys (and RC's and stables when they get to that point) only have merged commits.
An open commit is a change to the code that is currently being reviewed and hasn't been approved to be included in the next CM...yet, or ever for that matter. Some open commits get merged eventually (either as they are, or after they've been updated a time or fifteen), other open commits get abandoned. Some users like the additional functionality of these open commits, at the potential cost of stability.
I've started releasing kangs two at a time. One completely stock with only merged commits (just like the official CM7 build bot would have done, may it rest in peace), and the next kang with the same amount of merged commits, plus some interesting looking open ones (most have been requested by users, other merely look like they won't make your phone explode).
And don't hesitate to ask questions, at least after a quick google search.
Click to expand...
Click to collapse
Thank you so much for the response. It makes a lot more sense to me now. I might take a look at what some of those open commits do and test them out, I have not problem having to restore or flash a newer stabler one if needed.
BlankDEP said:
Thank you so much for the response. It makes a lot more sense to me now. I might take a look at what some of those open commits do and test them out, I have not problem having to restore or flash a newer stabler one if needed.
Click to expand...
Click to collapse
Good on ya mate! Take a chance and get cool features that may never be available
Sent from Tapatalk
Thanks, Pons. These KANGs brought me back to CM7 after like 9 months on MIUI builds. Just got tired of the instability and random problems with the new MIUI builds. These CM7 kangs are awesome. Great work!
Kitchen theming not sticking
Sorry if this is a dumb question, I haven't been on CM7 in a while, and hadn't tried using UOT for anything on it before.
I set up a new battery style and applied the zip. It themed over fine after booting up, but eventually it reverted to the stock CM7 battery after an hour or so.
Anyone have any suggestions on getting a new battery style to stick? Thanks.
miketwoms said:
Sorry if this is a dumb question, I haven't been on CM7 in a while, and hadn't tried using UOT for anything on it before.
I set up a new battery style and applied the zip. It themed over fine after booting up, but eventually it reverted to the stock CM7 battery after an hour or so.
Anyone have any suggestions on getting a new battery style to stick? Thanks.
Click to expand...
Click to collapse
You can another way but it may be a little more complicated? Not onto recovery, mount system, then adb pull the systemui.apk, decompile it with apk manager, swap out the png's for the battery with those from the SystemUI.apk, recompile the SystemUI.apk, then pull the png's from the recompiled apk with 7Zip and drop them into the original SystemUI.apk, and adb push it back to the phone.
EDIT: And although I haven't tried this next method, it may work? You could boot into recovery, mount the system, adb pull the SystemUI.apk, explore it with 7Zip, and simply drop the battery png's from the uot (which you are exploring the same way) into the folder the battery png's are located in within the SystemUI.apk and it will overwrite them (provided the files are named the same. They NEED to be named exactly the same). the adb push that systemUI.apk back to the phone. No decompiling or Recompiling done...
So yeah, not sure if that will work do to compression and stuff..
Sent from Tapatalk
thanks. I might give that 2nd option a try.
[CONTEST #5] CDMA Nexus: People's Choice Edition
Vote for The CM maintainer for the OG Incredible Josh Stone aka CUViper.
http://rootzwiki.com/user/25563-cuviper/
He's been great to us and the incredible community; let's try and return the favor.
New kang is up. Check the changelog, and/or download location.
Related
Requirements:
Build #8 and higher: Clockworkmod Recovery 3.0.0.7 or higher is REQUIRED!
You don't have 3.0.0.7 or higher installed I cannot help you out with any issues as these scripts do not play nicely with anything earlier than 3.0.0.7!
You have been warned!
How To Install:
Coming from another ROM or doing a clean install:
Step 1: NANDroid first!
Step 2: Do a full wipe! This means format everything!
Step 3: Flash desired build, wait for install to finish and reboot
Step 4: Enjoy!
Upgrading from nightly #X or ProTekk build #Y using build #8 or higher:
Step 1: NANDroid first!
Step 2: Flash desired build, Dalvik and cache will be wiped automatically!
Step 3: Enjoy!
Google Applications (GApps):
http://goo-inside.me/gapps/
CyanogenMod changelog & merges:
http://review.cyanogenmod.com/#q,status:merged,n,z
Stock Build Download Locations:
http://www.mediafire.com/cm7/inc
Experimental Build Download Locations: Abandoned for now until I have more time/help
http://www.mediafire.com/?8z38p1pgyag72
Experimental Builds With Custom Kernels:
Included kernels:
Incredikernel from 03/06/11
Invisiblek from 03/09/11
SavagedZen no SBC
Tiamat from 03/05/11
Please remember that they are experimental!
With these, ALWAYS wipe Dalvik and cache! No longer needed as it is auto wiped - Build #8 and higher!
Updates:
Experimental builds #8 & stock #8 released @ 00:14 AM EST 03/12/11
Experimental builds #7 & stock #7 released @ 7:30 AM EST 03/11/11
Experimental builds #6 released @ 1:05 PM EST 03/10/11
Experimental Build #5 With Custom Kernels released @ 1:33 PM EST 03/09/11
Build #5 released @ 10:12 AM EST 03/09/11
Build #4 released @ 2:50 PM EST 03/08/11
Build #3 released @ 9 AM EST 03/08/11
Build #2 released 03/06/11
Build #1 released 03/06/11
To-Do List:
Automatically wipe Dalvik and cache prior to installing. Abandoned for the moment. Working properly!
Credits:
CyanogenMod Team for the incredible ROM they've given us
Slayher for many many many fixes and guiding me here and there! Thanks!
Calkulin for his format script - Thank you!!!!!
NilsP for helping me out with the format script
Chad, Invisiblek, SavagedZen team, and Cayniarb for your amazing kernels
If I have forgotten anyone I'm sorry! Let me know and I'll give you credit!
Q: What is this?
A: This is something I have started doing since the buildbot has been on hiatus and I needed to feed my addiction to flashing the most recent build of CyanogenMod 7 I could get my hands on.
I started doing this for myself and saw that there was a pretty big demand for the newest updates possible so I said why not share it with everyone.
Nothing in my builds have been altered so don't worry. It is not a ROM I have customized. All I am simply doing is pulling the source every morning and compiling it.
Q: Wait, so this is the same as the CyanogenMod 7 nightly builds? Why rename it and make it?
A: Great question. Think about it this way. The CyanogenMod team builds nightly right? Well, lately it hasn't been nightly but more random. The advantage of building daily, for me and the people on the east coast, it is much better to have a new build readily available in the morning versus waiting all night for a release or no release at all and wasting time. I am not taking credit for the CyanogenMod team's work and I refuse to as I am simply pulling the source and compiling it. The renaming of my builds is to defer the confusion between the CyanogenMod nightly builds as my builds have nothing to do with how CyanogenMod builds and releases.
Q: Ok, so if I am having issue X,Y,Z who do I report it to?
A: If it is a known issue please post it in the RC 1.5 thread. If it is an issue that is not known and has started with one of my builds please report it here via a post or a PM and I will be more than happy to help out and see if I can fix it.
Q: Uh, if there are nightlies then why would I want to use your builds? Doesn't it make sense to use one of the nightlies?
A: Sure, you are more than free to use one of the official CyanogenMod nightlies! The reason why some use my builds is simply the fact that they want to have the newest updates and merges on their device! The buildbot does not always pump out a new nightly where as I always will be building and compiling every day. Also, the nightlies don't always include the newest merges because of the fact that merges can be push at any time.
Q: If you are building these daily what happens if updates are merged after you build?
A: Haha, I know this is sad but I don't have much of a life but I do have one! I keep on top of all the merges almost like clockwork! I normally check about every hour to see if there are any major updates and fixes. If a major fix is merged I will be pushing out another build as soon as I see that it has been merged! So no need to worry about having the newest build besides downloading it and installing it.
Q: Ok, so nightly #X is released, wouldn't it be the same as your build #Y?
A: This is a little harder to answer but I will make it simple. As I said before and as many have noticed, the buildbot doesn't always push a new build. For example, my builds #1 and #2 are the same as nightly #13. RC 2 and nightly #14 were released and both are just about the same from CyanogenMod. My build #3 includes the new merges after both of those have been built so mine would be newer. I will be working on a log that tracks the differences between the nightlies and my builds shortly.
Q: What's the deal with the kernels? Why are there the same number build but different names?
A: I have noticed that everyone has their own "go-to kernel" after they flash a ROM. I have collected the top 4 gingerbread kernels used and incorporated them into each build I do. There is the stock build which is nothing different than what the CyanogeMod team puts out, Incredikernel, Invisiblek, Tiamat, and SalvagedZen. You can choose whatever one you want to use. The purpose of this is to simplify the install process for the user so that there is no need to be flashing multiple zips just because you're updating to the newest build.
Q: I can't get CWM 3.0.0.x to update on my phone. I don't know what I'm doing wrong. Every time I go to recovery, it says i'm running 3.0.0.x
A: ROM Manager > Menu > Settings > Erase Recovery > Back > All ClockworkMod Recoveries > select 3.0.0.7 or higher
Any other questions? Please let me know and I will include them in this post!
------------------------------------------------------------------------------------------
I personally test out each build as I release them and if there is one posing serious issues I will pull it from my site!
I have successfully used the stock kernel, incredikernel, and Tiamat on my builds without issues.
All my builds will be online and ready to download no later than 10 AM eastern time! I try to get them out as quick as possible for you guys!
As a sidenote and fore more clarification, I am NOT taking credit for the fabulous work that the CyanogenMod team is doing! This is NOT a custom ROM I have edited or made! This is always going to be straight from the CyanogenMod team's source!
I will be doing this past RC 2 and if CyanogenMod 7 gets release as a stable build and solidified I will be building as long as there are updates merged!
Please enjoy it and happy crackflashing to all!
This is great, now I don't have to scroll through the other thread for your builds, thanks Protekk
Sent from my ADR6300 using XDA App
nerogold said:
This is great, now I don't have to scroll through the other thread for your builds, thanks Protekk
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Not a problem! I aim to please!
So what are the "fixes" you mentioned in the other thread that you merged at 9AM? I am doing a fresh install of RC2 because I have been wanting to use one of these themes since RC1, but he doesn't update it for nightlys...
If the fixes aren't anything huge then I will try to stick with RC2 for atleast half a day
GatorsUF said:
So what are the "fixes" you mentioned in the other thread that you merged at 9AM? I am doing a fresh install of RC2 because I have been wanting to use one of these themes since RC1, but he doesn't update it for nightlys...
If the fixes aren't anything huge then I will try to stick with RC2 for atleast half a day
Click to expand...
Click to collapse
If you visit the link to the merged changelog, anything that is there before 9 AM easter time is in this build. This includes a major fix for people having bootloop issues with RC 2. My build #3 can be considered RC 2 + fixes.
So far build #3 seems to be working with the RC2 DTR!
That's good to hear Derrty!
No more SD card damaged with #3, thanks for compiling !!! Now I can decide if I want to try the new kernel from Chad.
The one thing I learned from all this is that it's good to have a backup SD card that has restores on it. That way when your SD card gets F#[email protected]#$ up, you can just put in your other SD card and your up and running.
I have a complete backup of the SD card on my pc
dspcap said:
No more SD card damaged with #3, thanks for compiling !!! Now I can decide if I want to try the new kernel from Chad.
The one thing I learned from all this is that it's good to have a backup SD card that has restores on it. That way when your SD card gets F#[email protected]#$ up, you can just put in your other SD card and your up and running.
Click to expand...
Click to collapse
yeah it is. but it sucks when you have 32gig card and 28gig's are used and you have only usb 1 with a 1.25mb transfer speed.... :'(
cd2573 said:
I have a complete backup of the SD card on my pc
Click to expand...
Click to collapse
but it changes constantly with your apps too. it would be very time conduming to do it everyday
Mozy has a new mobile app coming that will automatically backup your phone.... not sure how it will work, but quite interested.
v941726 said:
but it changes constantly with your apps too. it would be very time consuming to do it everyday
Click to expand...
Click to collapse
Take a look at rsync backup for Android. rsync is my favorite tool for backups since it only copies the changes to the files in question (even large files that are modified but largely the same - rsync only copies the changes). I use that app, combined with Tasker to automate a nightly backup of my sd card as well as instant backup of my dcim dir. when the camera app exits. Oh and to sync podcasts to my phone from my mac. If you're running linux or OSX you've got rsync native on your system (just be careful learning how to use it so you don't clobber any important files). If you're on windows, there are some implementations of rsync (here's one) but I've never tried 'em so I dunno how well they work...
Yeaaaaaa! No more damaged sdcard! Thanks dude!
Sent from my ADR6300 using XDA App
wildland said:
Take a look at rsync backup for Android. rsync is my favorite tool for backups since it only copies the changes to the files in question (even large files that are modified but largely the same - rsync only copies the changes). I use that app, combined with Tasker to automate a nightly backup of my sd card as well as instant backup of my dcim dir. when the camera app exits. Oh and to sync podcasts to my phone from my mac. If you're running linux or OSX you've got rsync native on your system (just be careful learning how to use it so you don't clobber any important files). If you're on windows, there are some implementations of rsync (here's one) but I've never tried 'em so I dunno how well they work...
Click to expand...
Click to collapse
thanks. i've been looking for something like that. using tasker and getting it to work the way you want is more of a chore sometimes though
ProTekk Build #4 on its way. Including the merges from this afternoon.
man you are not playing
cd2573 said:
man you are not playing
Click to expand...
Click to collapse
Not one bit. I'm staying true to my word. I promised the community this so I'm going to do it! Even though the woman is getting annoyed by this I'm still doing it
Update: ETA 10 minutes until completion and +5 for uploading. Get ready!
Update #2: Uploaded and ready on my site! Link is in the first post!
Mediafire link is up as well.
I love how fast these are coming.
I tried the latest build of CM7 done by the Atrix Dev Team and it is awesome. Very reliable, fully functional, etc. I figured I'd give a whirl to compiling the real ICS version to see what that was like.
CM9 build system with the appropriate Atrix Dev Team repos in place actually spit out a working ROM. There are a number of issues aside from the general preview state of CM9. I figured I would share them in case anyone else was as curious as me. Apparently, the internal atrix dev teams are well beyond these issues already, so kudos.
Probably related to CM/atrix specific stuff
- Camera and finger print sensor don't work
- Launcher crashes pretty often
- Some openGL demos don't seem to work right (or at all)
- No mounting the SD as USB storage
Probably related to the specific gapps package I used.
- Maps crashes after 3 seconds (signal 11 - native code crash)
- Maps wants to update, but it can't (sharedId conflict if you actually remove maps)
- Earth won't run (missing the earthmobile library)
- Google Voice Search bombs (signal 4 - illegal instruction - currently suspecting the native packages might have some NEON instructions that the atrix cpu doesnt support)
- Calendar will not sync for google or exchange. App loads, but the sync service is failing
- Lots of null pointer exceptions for the NFC stuff in the log.
Anyway, this is just a build of the code that's out there, nothing special done by me. It might be useful for a dev phone or something but not for use on a real day-to-day device. Obviously it doesn't have the google apps embedded in it.
http://www.multiupload.com/XT9QPPQYF1 thanks xploited for uploading
md5: 670068584eb94bf1d660c0450815ad0d
Personally, I had trouble going back to CM7 afterwards, my clockwordmod backups were screwed up (bad boot.img? cross-linked files on the SD card) and I had a very hard time getting back to the good ole working state. Ultimately, I had to restore the partial backup and then reflash the CM7 image + gapps.
So, if you were curious what building a random repo on the web and installing it on your phone would do, then feel free to try and lose all of your data. There are no updates/support for this, etc. It's just a curiosity... what is the state of this stuff right now?
BTW... I am back on CM7/Atrix now which is AWESOME!!!!
Source Code Links:
https://github.com/CyanogenMod/android
https://github.com/Atrix-Dev-Team/android_device_motorola_olympus
Not sure how the dev team would react to this ..we do not want any bricked phones because of this ..there maybe some experimental dangerous code in there in those sources as of now ..not sure though
Hmm... figured since I spent quite awhile getting a build set up, it might be worth sharing. I am happy to take down if it is inappropriate.
Well I am not the best person to answer that ...but yeah thanks for your work.
Eh, I wouldn't be mad about it, but I think it needs more caution. I would just wait. As you say, it kindof screwed with a lot and wasn't very usable, so why flash it? Maybe ok for someone who wants to look at the code, but I wouldn't flash it.
Awesome news man. Thanks for being a lab rat and giving us an update.
Sent from my MB860 using xda premium
Not so much take it down as change the title of the post.
the current internal atrix-dev-team cm9 is way further ahead of this, we have some different patches. this is missleqading as it makes it sound official and is not.
Could you please change the tittle to [KANG] CM9 Test Build by "your name"
and please link to the sources, as is proper practice for open source projects
thank you
samcripp said:
Not so much take it down as change the title of the post.
the current internal atrix-dev-team cm9 is way further ahead of this, we have some different patches. this is missleqading as it makes it sound official and is not.
Could you please change the tittle to [KANG] CM9 Test Build by "your name"
and please link to the sources, as is proper practice for open source projects
thank you
Click to expand...
Click to collapse
and I guess you guys deserve a Xmas break now ...
It's nice to see that! Thanks for your hard work.
I'm looking forward to the CM9
Thank you for this.
!
Anyways, Just out of curiosity... where can you find the official Atrix Dev team's CM9?
The one been worked on by turl is with him, that is not for public release.
Dont forget to tell him merry xmas!
I always forget what kang means.
Sent from my MB860 using XDA App
wrldsuksgo2mars said:
I tried the latest build of CM7 done by the Atrix Dev Team and it is awesome. Very reliable, fully functional, etc. I figured I'd give a whirl to compiling the real ICS version to see what that was like.
CM9 build system with the appropriate Atrix Dev Team repos in place actually spit out a working ROM. There are a number of issues aside from the general preview state of CM9. I figured I would share them in case anyone else was as curious as me. Apparently, the internal atrix dev teams are well beyond these issues already, so kudos.
Probably related to CM/atrix specific stuff
- Camera and finger print sensor don't work
- Launcher crashes pretty often
- Some openGL demos don't seem to work right (or at all)
- No mounting the SD as USB storage
Probably related to the specific gapps package I used.
- Maps crashes after 3 seconds (signal 11 - native code crash)
- Maps wants to update, but it can't (sharedId conflict if you actually remove maps)
- Earth won't run (missing the earthmobile library)
- Google Voice Search bombs (signal 4 - illegal instruction - currently suspecting the native packages might have some NEON instructions that the atrix cpu doesnt support)
- Calendar will not sync for google or exchange. App loads, but the sync service is failing
- Lots of null pointer exceptions for the NFC stuff in the log.
Anyway, this is just a build of the code that's out there, nothing special done by me. It might be useful for a dev phone or something but not for use on a real day-to-day device. Obviously it doesn't have the google apps embedded in it.
http://goo.gl/39NnA
Personally, I had trouble going back to CM7 afterwards, my clockwordmod backups were screwed up (bad boot.img? cross-linked files on the SD card) and I had a very hard time getting back to the good ole working state. Ultimately, I had to restore the partial backup and then reflash the CM7 image + gapps.
So, if you were curious what building a random repo on the web and installing it on your phone would do, then feel free to try and lose all of your data. There are no updates/support for this, etc. It's just a curiosity... what is the state of this stuff right now?
BTW... I am back on CM7/Atrix now which is AWESOME!!!!
Source Code Links:
https://github.com/CyanogenMod/android
https://github.com/Atrix-Dev-Team/android_device_motorola_olympus
Click to expand...
Click to collapse
Thinks for your works,
Come from Chinese thinks!
i shall say this.. if this is behind where the dev team actually is...things are looking good! and btw.. i believe fruitcaker maker works. installed and is now creating;]
edit: yep. it does.
Thanks man very very good work android congratulations for share work whith comunity
Sent from my MB860 using xda premium
it looks very nice but id needs a bit more work to be a experimental daily driver.
ps: to solve the corrupt backup problem just copy the files to your computer before flashing and copy to your phone before restoring.
good luck!
where can I get google apps for this rom? Tryed gapps for CM7 from CM wiki - fail, setup wizard crashes.
try the one on this link
http://rootzwiki.com/topic/11854-romcm9-encounterics-x-beta-2-with-working-radio-401/
good luck!
---------- Post added at 07:52 AM ---------- Previous post was at 07:47 AM ----------
ilya11g said:
where can I get google apps for this rom? Tryed gapps for CM7 from CM wiki - fail, setup wizard crashes.
Click to expand...
Click to collapse
try the one on this link
http://rootzwiki.com/topic/11854-rom...ing-radio-401/
good luck!
For a preview build it looks pretty nice. Surprisingly stable for what it is. Definitely keeping an eye on this, especially since the code is out there to make DIY kangs with.
samcripp said:
The one been worked on by turl is with him, that is not for public release.
Dont forget to tell him merry xmas!
Click to expand...
Click to collapse
Random SamCripp memory....
"We're rapping them, we're rapping them!!!"
Sorry, guess you had to be there.... aahhh memories... nevermind, sorry for the off topic post.
Thanks though for the effort of getting this ported btw.
Because the CyanogenMod developers decided not to switch to the Linaro toolchain, I decided that I would do it myself. This ROM is very similar to invisiblek's nightlies, but has a few more patches from the CyanogenMod queue applied and other changes made to enable building with GCC 4.7 and -O3. I will try to put up a new build at least once every few days if there is much being merged into the CM9 tree.
The main benefit of using the Linaro optimized ROM is that the UI is faster and snappier. Some applications (especially heavy ones like Google Play) are noticeably less laggy. Also, you get higher benchmark scores. (Yay!)
My kernel is included as the stock kernel in this ROM.
As always, if you are in any doubt whatsoever, you should do a Nandroid backup before flashing this ROM.
Changelog:
8/15/2012
No changes from me; just updates from the CM repo
8/12/2012
Revert the patch increasing the number of cached app pages, as this used more memory and made the launcher homescreens lag
8/10/2012
No changes from me; just updates from the CM repo
8/7/2012
Remove the ext4 sdcard patch because it was causing multiple regressions in handling the sdcard, even though it was still fat32
8/6/2012
Apply patch (http://review.cyanogenmod.com/#/c/20061/) to remove videos intended only for the tuna device
Attempt to workaround the lag issues by making the browser kill itself when the last tab is closed
8/3/2012
Apply patch (http://review.cyanogenmod.com/#/c/20654/) to enable HTTPS Google searches in the stock browser for better privacy
Apply patch (http://review.cyanogenmod.com/#/c/19807/) to allow mounting ext4 sdcards
7/31/2012
Update to the Linaro 2012.7 toolchain
Compile the kernel with "-O3 -fno-tree-vectorization"
7/22/2012
Add TCP MSS iptables filter to the kernel as it seems to be used during tethering
Add the Linaro string processing optimizations to the ROM
7/21/2012
Include my "Lite" kernel with the ROM
Update to a new, unreleased-as-of-yet version of my kernel with more optimizations
7/16/2012
Disable WebGL again. It was causing hardlocks on a number of enabled sites
Apply patch (http://review.cyanogenmod.com/#/c/18490/) to allow for the downloading of "unsafe" attachment files in Email
7/10/2012
Apply patch (http://review.cyanogenmod.com/#/c/18319/) to speed up some app starts
Apply patch (http://review.cyanogenmod.com/#/c/17552/) to add more NEON optimizations to pixelflinger
Enable WebGL
7/8/2012
Apply Evan McClain's libskia update (fixes the blacked-out JPEG issue)
Fix some media players like MX Player (an instruction was missing because it was optimized out by O3)
Apply more optimization flags
6/27/2012
Initial release
Apply CM9 patches to fix compile failures with GCC 4.7 and enable O3 optimizations
Switch to libjpeg-turbo
Disable scrolling cache (increases scrolling smoothness for non-hardware-accelerated listviews)
Issues (specific to the Linaro optimized version):
Turning off Bluetooth causes the Phone app to crash. It restarts immediately, so there are no long-term effects.
Bluetooth file transfer (OPP) does not work. The Linaro team experiences this bug too and is currently looking for a solution. I will update as soon as a solution is found.
You can download the source I use to compile this ROM by following these instructions: https://github.com/invisiblek/android_device_htc_inc/blob/ics/README.md
Compiling Instructions:
These compiling instructions are for Linux. They should work on any distro, but I am using the latest release of (K)ubuntu.
Follow all of the instructions from the source link above except for the last one. This will download the source tree and get you set up to build.
Assuming you are already in the root directory of your source tree ("~/cm9" if you followed the above instructions), run the following commands in the terminal. Some of the git pulls will display a text editor screen. When you get this, just press Ctrl-O, Enter, and finally Ctrl-X.
Code:
cd external/skia
git pull http://review.cyanogenmod.com/CyanogenMod/android_external_skia refs/changes/85/14585/1
git pull http://review.cyanogenmod.com/CyanogenMod/android_external_skia refs/changes/86/14586/1
git pull http://review.cyanogenmod.com/CyanogenMod/android_external_skia refs/changes/87/14587/1
git pull http://review.cyanogenmod.com/CyanogenMod/android_external_skia refs/changes/88/14588/1
git commit -a
git pull http://review.cyanogenmod.com/CyanogenMod/android_external_skia refs/changes/89/14589/1
git pull http://review.cyanogenmod.com/CyanogenMod/android_external_skia refs/changes/10/15810/1
cd ../webkit
git pull http://review.cyanogenmod.com/CyanogenMod/android_external_webkit refs/changes/90/14590/1
git pull http://review.cyanogenmod.com/CyanogenMod/android_external_webkit refs/changes/91/14591/1
cd ../../frameworks/base
git pull http://review.cyanogenmod.com/CyanogenMod/android_frameworks_base refs/changes/92/14592/1
git pull http://review.cyanogenmod.com/CyanogenMod/android_frameworks_base refs/changes/80/17380/2
cd ../../external/freetype
git pull http://review.cyanogenmod.com/CyanogenMod/android_external_freetype refs/changes/54/12654/2
cd ../../build
git pull http://review.cyanogenmod.com/CyanogenMod/android_build refs/changes/58/17358/4
Follow the instructions here to replace your libjpeg with libjpeg-turbo.
Open the file ~/cm9/frameworks/base/core/java/android/widget/AbsListView.java in your favorite text editor. Go to line 753 and change it to read "setScrollingCacheEnabled(false);".
Open the file ~/cm9/bionic/libc/arch-arm/bionic/libgcc_compat.c in your favorite text editor. Go to line 114 and insert two new lines reading "XX(__aeabi_llsl) \" and "XX(__aeabi_llsr) \" below it.
Open the file ~/cm9/build/core/config.mk in your favorite text editor. Go to line 91 and change it to read "COMMON_GLOBAL_CFLAGS:= -DANDROID -fmessage-length=0 -W -Wall -Wno-unused -Winit-self -Wpointer-arith -Wno-error=strict-aliasing -Wno-error=enum-compare". Go to line 312 and change it to read "TARGET_GLOBAL_CFLAGS += $(COMMON_GLOBAL_CFLAGS) -march=armv7-a -mcpu=cortex-a8 -mtune=cortex-a8". Go to line 315 and change it to read "TARGET_GLOBAL_CPPFLAGS += $(COMMON_GLOBAL_CPPFLAGS) -march=armv7-a -mcpu=cortex-a8 -mtune=cortex-a8".
Open the file ~/cm9/build/core/combo/TARGET_linux-arm.mk in your favorite text editor. Go to line 47 and change it to read "prebuilt/$(HOST_PREBUILT_TAG)/toolchain/linaro-4.7.1/bin/arm-linux-androideabi-". Go to line 149 and change it to read "TARGET_GLOBAL_CPPFLAGS += -fvisibility-inlines-hidden".
Download this file and unzip it to ~/cm9/prebuilt/linux-x86/toolchain/linaro-4.7.1
You are finally ready to build! Open a terminal to the ~/cm9 directory, then run ". build/envsetup.sh" and "brunch inc". This will take a long time.
Great, going to try this out. Maybe the keyboard works better, I've shut down pop up and prediction.
Still lags horribly.
Edit: Is gapps included or do I need to flash them?
Edit: Wow.. Maybe some won't notice it, but I've seen an increase of speed and snapiness. Keyboard lag seems to have stopped somewhat.. its still there but its along better.
Sent from my ADR6300 using Tapatalk 2
withbloodskies said:
Great, going to try this out. Maybe the keyboard works better, I've shut down pop up and prediction.
Still lags horribly.
Edit: Is gapps included or do I need to flash them?
Edit: Wow.. Maybe some won't notice it, but I've seen an increase of speed and snapiness. Keyboard lag seems to have stopped somewhat.. its still there but its along better.
Sent from my ADR6300 using Tapatalk 2
Click to expand...
Click to collapse
You still need to flash Gapps. It would be illegal for me to include them.
The best workaround I have found for keyboard lag is to disable spellchecking. You still get autocorrect like in GB; it just doesn't put a red squiggly under misspelled words.
Good work, I'll have to try it out. Any chance you putting this up on goo.im and/or ROM Manager, to expedite the update process?
Very nice work,Thanks for your contribution .
PonsAsinorem said:
Good work, I'll have to try it out. Any chance you putting this up on goo.im and/or ROM Manager, to expedite the update process?
Click to expand...
Click to collapse
I will look at putting it on goo.im.
One last suggestion (for now) before I'm off to flash it: thought of changing the ROM and zip name just slightly so it's not confused with invisiblek? Maybe throw a linaro in there somewhere or something? Right now, they have the same names (and dates, too, shortly) with just the compile times and machines being different. Now off to flash.
PonsAsinorem said:
One last suggestion (for now) before I'm off to flash it: thought of changing the ROM and zip name just slightly so it's not confused with invisiblek? Maybe throw a linaro in there somewhere or something? Right now, they have the same names (and dates, too, shortly) with just the compile times and machines being different. Now off to flash.
Click to expand...
Click to collapse
I'm not quite sure how to do that. Can you tell me?
mamarley said:
I'm not quite sure how to do that. Can you tell me?
Click to expand...
Click to collapse
You'll have to do some tweaking to the bottom of this file. Hard to explain on the phone. As part of my compile script I wrote for my kangs, it sed/replaced the necessary lines with pons (I'd use linaro for yours). Experiment with it till it looks how you want it to. Any questions, let me know.
https://github.com/CyanogenMod/android_vendor_cm
mamarley said:
You still need to flash Gapps. It would be illegal for me to include them.
The best workaround I have found for keyboard lag is to disable spellchecking. You still get autocorrect like in GB; it just doesn't put a red squiggly under misspelled words.
Click to expand...
Click to collapse
I wanted to point out that I got keyboard lag on ICS even on my gnex. There's not much that can be done. I never did try disabling spell checker. Liquid 1.5 helped with its linaro optimizations but what helped more to me was the interactive governor I was using had input boost which boosts frequency upon using the touchscreen to minimize lag rather than wait for it to ramp up. The other part nay have been the go_high setting of 50% load. I'm not using all the technical terms but to high-speed frequency is user configurable and its the speed it will jump to at a specified load. It may exist in our current interactive governor.
I do know that there is no keyboard lag in jelly bean that I can tell.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
I do know that there is no keyboard lag in jelly bean that I can tell.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Its all that butter
Anyway I used DPI and it works but it makes alot of apps force close. I was on 175, the same thing happens on Evervolv's Roms too.
Sent from my ADR6300 using Tapatalk 2
Can i flash this over invisiblek's Cm9 nightlies?
Or do i have to do a full wipe?
I have all my apps and everything just the way i want it.. I really dont wanna wipe.
Gorilla* said:
Can i flash this over invisiblek's Cm9 nightlies?
Or do i have to do a full wipe?
I have all my apps and everything just the way i want it.. I really dont wanna wipe.
Click to expand...
Click to collapse
You can flash over.
I have been flashing over since the CM7 days and have never had any problems. I even flashed the CM9 ROM right on top of the CM7 ROM and only had to clear the data for 2 apps to get everything working again.
Marley, Im booting up now, I flashed it, flashed your Lite Kernel, and USB fast charge zip.
Heres to hoping for some sexy Linaro Goodness!
Ill report back to how this runs.
Gorilla* said:
Marley, Im booting up now, I flashed it, flashed your Lite Kernel, and USB fast charge zip.
Heres to hoping for some sexy Linaro Goodness!
Ill report back to how this runs.
Click to expand...
Click to collapse
Same here. Just booted up. This is legit. Snappier than the CM9 nightlies so far. I didn't flash the USB zip- what will that give me?
statusqu0 said:
Same here. Just booted up. This is legit. Snappier than the CM9 nightlies so far. I didn't flash the USB zip- what will that give me?
Click to expand...
Click to collapse
That enables USB Fast Charge. It will make your phone charge much faster when it is plugged into a PC or some third-party wall/car chargers.
mamarley said:
That enables USB Fast Charge. It will make your phone charge much faster when it is plugged into a PC or some third-party wall/car chargers.
Click to expand...
Click to collapse
Forgive my noob-ness, but will that damage the battery in any way?
statusqu0 said:
Forgive my noob-ness, but will that damage the battery in any way?
Click to expand...
Click to collapse
No, it just makes it charge in the same way it would if you plugged it into the stock wall charger.
seems good so far. a couple slow-downs at first but seem to have gone away.
Yea, seems snappier than the other cm9 rom..
Im just hoping i dont get phantom touchscreen issues.. like the screen typing for me,.
Unofficial CM 10.2 builds for Nexus 4
Hi all,
I decided to post my unofficial builds of CM10.2 for Nexus 4 after being asked by a few people in the CM10.1 Q&A and development threads, in order to consolidate questions and keep clutter down in those threads I decided it was best to make a thread specifically for these builds.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.3 (Jelly Bean), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* 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.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. Your changelog is whatever was merged into gerrit.
How to install:
First time installing or coming from another 4.3 based ROM:
Download the ROM
Download a compatible 4.3 Gapps package (I have been using Banks gapps from here: http://forum.xda-developers.com/showthread.php?t=2012857)
Reboot into recovery
Wipe data/Factory reset
Flash the ROM
Flash Gapps
Reboot
Coming from a previous CM10.2 nightly:
Download the ROM
Reboot into recovery
Flash the ROM
Reboot
Coming from a previous CM10.1 nightly:
Download the ROM
Download a compatible 4.3 Gapps package (I have been using Banks gapps from here: http://forum.xda-developers.com/showthread.php?t=2012857)
Reboot into recovery
Flash the ROM
Flash Gapps
Reboot
Builds:
Built from official CM sources only, no cherry-picks, no changes, no additions. I will not be changing the official sources in any way so don't bother asking.
http://goo.im/devs/thracemerin/cm_builds/mako
Note: These builds are produced by my buildbot at 4am US Eastern time (build + upload takes approximately 90 minutes), the repo will be synced during the build process to ensure that the latest sources are used. The completed file size should be approximately 196MB, so if the latest download isn't it's not fully uploaded yet
Note 2: If the build fails for some reason, I will try to build one later in the day, but if I can't you may have to wait until the following day.
How to get root:
In order to get root access, you need to do the following:
Activate the Developer Settings by going to Settings->About Phone ant tap on the Build Number 7 times.
Go to Settings->Developer Options and change the Root Access to 'Apps and ADB'
You may also need to activate USB Debugging in Developer Options (some people say you do, others say you don't)
Note: If you have flashed a kernel that comes with it's own boot.img package it may not have the correct instructions to start the internal su daemon as a result root will stop working, at the moment the best way to fix this is to not use that kernel. If you absolutely have to use a custom kernel you may need to flash SuperSU for the moment or ask your kernel dev to support this feature.
Known Issues
None that I'm aware of, but keep in mind that these are pre-nightly builds and could contain bugs and/or non-working features at any time.
Thanks
Google
CyanogenMod
F.A.Q
Q: When will official builds start?
A: Soon
CyanogenMod Blog said:
“Who cares about the old, gimme 10.2!”
We have one last internal item on our checklist before we open the floodgates on CM 10.2 nightlies. We fell into an old habit in 10.1 and the settings menu became more cluttered than we would like, and at times confusing both in presentation and in code. We are working to resolve this before 10.2 nightlies begin, so the transition is less jarring than it would down the line. Expect the new layout to be in effect with the first nightlies. If all goes well, we are talking days, not weeks.
In the meantime, the majority of our 10.1 roster have transitioned to being 10.2 capable. This means for you at-home builders, things should be in a fairly good spot for your own personal builds. If you want to checkout all the stuff we’ve merged, click through the pages.
Click to expand...
Click to collapse
Q: What is SELinux?
A:
CyanogenMod Blog said:
What is SELinux?
The project’s official description reads “SELinux is a security enhancement to Linux which allows users and administrators more control over access control.”
SELinux is a set of Open sourced and peer reviewed changes to the core Android Software stack to help prevent apps from performing malicious activities. This is done by establishing a set of policies that act as mandatory access controls (MAC). Depending on the policy, it can do things such as prevent apps from running or accessing specific data, to preventing root access altogether.
SELinux has wide-scale adoption throughout the linux landscape, with Fedora, Red Hat and others incorporating policies to better the system security. The default policies are usually written per distribution, by their maintainers – we have begun this process for CyanogenMod.
We will be working on this policy creation in parallel to Google’s own policies for Android, which we believe will be released with the Android 4.3 source; effectively getting us ahead of the eventual 4.3 source release. As this process is open source, policy creation and suggestions will be handled via our gerrit instance.
What it’s not?
SELinux is not a backdoor for government agencies to spy on you. It is not PRISM, PROMIS, CARNIVORE, The Great Firewall or any other ominous Big Brother-like initiative.
Access Control Modes
By default, we will be shipping with SELinux capabilities enabled in the kernel, but in a Permissive mode. What this means is that your phone will behave exactly as it currently does, with no noticeable change to the user.
There are 3 modes in total, Enforcing, Permissive and Disabled. While in Enforcing mode, SELinux policies are enforced, preventing whatever causes a violation (ie su). Permissive mode logs policy violations, but does not prevent the activity that caused it. Disabled turns SELinux off.
We are using Permissive mode as our default so we can come up with sensible policies. If you submit a log for us to analyze (via JIRA) for SELinux policy improvements, the logged exceptions will be of high value.
This will be an ongoing process as we work to incorporate sensible policies for each device repo. As always our source is available on Github and patches will be peer reviewed via gerrit. For those more attuned to personal data security, you are welcome to watch and audit our efforts. For the rest of you, sit back and relax – no need for pitchforks.
Click to expand...
Click to collapse
Third
amazing mate, keep it up the good work!
Hey, thanks for the builds. Do you have any idea in your great widsom as to why the various Gapps packages vary in size to such a great extent?
First, we have Banks, which is extremely minimalist, at least when compared to official 10.1 Gapps.
Then, we have a 10.2 un-authored Gapps package, often linked in the CM discussion, which is about the size of the official 10.1 one, but seems to require Banks's photosphere add-on.
Lastly we have doomed's version which approaches a whopping 200 MBs.
What on earth can account for such varying sizes, and as the purist that I think you are, why do you use the minimalist Banks Gapps?
Feedback
Nice man, thanks for this work, btw, the front cam is upside down.
floepie said:
Hey, thanks for the builds. Do you have any idea in your great widsom as to why the various Gapps packages vary in size to such a great extent?
First, we have Banks, which is extremely minimalist, at least when compared to official 10.1 Gapps.
Then, we have a 10.2 un-authored Gapps package, often linked in the CM discussion, which is about the size of the official 10.1 one, but seems to require Banks's photosphere add-on.
Lastly we have doomed's version which approaches a whopping 200 MBs.
What on earth can account for such varying sizes, and as the purist that I think you are, why do you use the minimalist Banks Gapps?
Click to expand...
Click to collapse
BaNkS only includes the essential Google Apps that are needed for the Google experience -- working sync services, the Play Store itself, and so on. He provides other Google Apps in the form of an add-on, a separate zip, for the keyboard/camera/etc. Basically, most of the Google Apps are now available to download from the store itself (Keep, Earth, Maps, Voice Search, Search and so on). That wasn't always the case, but still some are releasing a full Google Apps package with everything.
The minimalistic approach is obvious - only install what is necessary, manually get anything else yourself. That is why the banks package is small because it is not forcing other apps that people may or may not use since they could simply download it themselves if they wanted to. I assume the 200mb or more package is simply every single Google APK that comes with the official factory images.
lwkkazz said:
Nice man, thanks for this work, btw, the front cam is upside down.
Click to expand...
Click to collapse
Weird, doesn't seem to be for me.
floepie said:
Hey, thanks for the builds. Do you have any idea in your great widsom as to why the various Gapps packages vary in size to such a great extent?
First, we have Banks, which is extremely minimalist, at least when compared to official 10.1 Gapps.
Then, we have a 10.2 un-authored Gapps package, often linked in the CM discussion, which is about the size of the official 10.1 one, but seems to require Banks's photosphere add-on.
Lastly we have doomed's version which approaches a whopping 200 MBs.
What on earth can account for such varying sizes, and as the purist that I think you are, why do you use the minimalist Banks Gapps?
Click to expand...
Click to collapse
markd0wn basically covered it, but it also depends on what you want in your /system directory, most of the apps that used to come in Gapps packages are now available in the Play Store as stand alone packages so you can still get them if you want them and they get installed as user apps instead of system apps, not that it makes a tremendous difference, but for the most part they don't need to be in /system.
thracemerin said:
Weird, doesn't seem to be for me.
Click to expand...
Click to collapse
It's ok now , Hey man, it is normal that the ROM occupy 4Gb of the memory? (I'm new to Nexus 4, I get my yesterday haha)
lwkkazz said:
It's ok now , Hey man, it is normal that the ROM occupy 4Gb of the memory? (I'm new to Nexus 4, I get my yesterday haha)
Click to expand...
Click to collapse
Android reserves around 4GB of the total space on the device. Yes, it is quite normal.
Glad I picked up the 16GB model.
thracemerin said:
Weird, doesn't seem to be for me.
Click to expand...
Click to collapse
My front facing cam is upside down using focal, but in the stock app its fine
Sent from my Nexus 4 using Tapatalk 4
l.m.prowse said:
My front facing cam is upside down using focal, but in the stock app its fine
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Hmm....it's early for focal still, probably just an oddity.
@thracemerin, any way to know if the CM team are aware of the homescreen shortcut bug? maybe I should search JIRA for it... since I'm not sure they follow all threads here. Doesn't seem to happen to everyone though. Happens to me in every unofficial 10.2 build (gonna try yours now after full wipe). The only thing I'm changing is the number of homescreens from the default of 5 to less (for example 2). After that, it's very easy to reproduce - simply add a few apps from the drawer to the homescreen, also put some apps in folders, then reboot, and you'll see what I'm talking about (in case you don't already know). It also happens randomly without reboots, maybe when Trebuchet is refreshing itself or something, but reboot forces it to happen quicker.
markd0wn said:
@thracemerin, any way to know if the CM team are aware of the homescreen shortcut bug? maybe I should search JIRA for it... since I'm not sure they follow all threads here. Doesn't seem to happen to everyone though. Happens to me in every unofficial 10.2 build (gonna try yours now after full wipe). The only thing I'm changing is the number of homescreens from the default of 5 to less (for example 2). After that, it's very easy to reproduce - simply add a few apps from the drawer to the homescreen, also put some apps in folders, then reboot, and you'll see what I'm talking about (in case you don't already know). It also happens randomly without reboots, maybe when Trebuchet is refreshing itself or something, but reboot forces it to happen quicker.
Click to expand...
Click to collapse
I heard about it, but I always use Apex Launcher so it doesn't happen to me. I'm not sure they want you to put things for 10.2 on JIRA or not (probably not) but its a fairly serious thing, so you could try logging it, worst case they ignore it.
thanks for posting this thracemerin. I've started my own builds (mostly for fun, to see if I could!), but I wanted to try some known good 4.2 builds before I flash one of my own. Your build and instructions are great. It's running smooth except for two things:
- I can't get my titanium backups to restore user apps, it just hangs at 0%. No big deal, I've just been installing from play store manually.
- Installing swype gives an error -24 . I did a clean install of your CM build, so data was wiped; there is nothing from nuance in data/data to wipe. This may or may not be related to the error with TiBu because it also was trying to install swype from a backup. I guess I'll play with the stock keyboard for a while.
thanks again.
nighthawkca said:
thanks for posting this thracemerin. I've started my own builds (mostly for fun, to see if I could!), but I wanted to try some known good 4.2 builds before I flash one of my own. Your build and instructions are great. It's running smooth except for two things:
- I can't get my titanium backups to restore user apps, it just hangs at 0%. No big deal, I've just been installing from play store manually.
- Installing swype gives an error -24 . I did a clean install of your CM build, so data was wiped; there is nothing from nuance in data/data to wipe. This may or may not be related to the error with TiBu because it also was trying to install swype from a backup. I guess I'll play with the stock keyboard for a while.
thanks again.
Click to expand...
Click to collapse
For the titanium backup problem, I switched the backup folder to the legacy selection in the preference menu and was then able to restore. Hope that helps
Sent from my Nexus 4 using xda premium
nighthawkca said:
thanks for posting this thracemerin. I've started my own builds (mostly for fun, to see if I could!), but I wanted to try some known good 4.2 builds before I flash one of my own. Your build and instructions are great. It's running smooth except for two things:
- I can't get my titanium backups to restore user apps, it just hangs at 0%. No big deal, I've just been installing from play store manually.
- Installing swype gives an error -24 . I did a clean install of your CM build, so data was wiped; there is nothing from nuance in data/data to wipe. This may or may not be related to the error with TiBu because it also was trying to install swype from a backup. I guess I'll play with the stock keyboard for a while.
thanks again.
Click to expand...
Click to collapse
Thanks to DJLamontagneIII for this:
Titanium backup Users
1. In tb go to menu>preferences>backup folder location
2. Navigate to storage/emulated/legacy
3. Select your Backup folder and Select "Use the current folder"
4. Then it will ask you to move backup to that folder.... Select that
5. Restart app and restore.
jpreichart said:
For the titanium backup problem, I switched the backup folder to the legacy selection in the preference menu and was then able to restore. Hope that helps
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Beat me to it
Another bug that I think is introduced in the 08-11 build is lockscreen slider shortcuts not saving (but if you changed them on a previous build and updated to 08-11, they'd probably be set up right).
I managed to save them anyway using a workaround. Basically setting them all as 'Empty' and hitting the save button won't do - you'd turn screen off/on and it will still have the default ones. What I did to 'fix' this is set each one to empty and tap save inbetween changing each one, then tap save again after they're all empty, then I tapped the icon that restores all to default, suddenly the 'default' is what I just set up (all empty), then hit save again, and voila, saved successfully. Could probably skip a few of those steps that I did as I'm sure one of them did the trick and the others were just me testing, but at least it works.
Another thing that confirms that they're changing something related to lockscreen shortcuts, is that after achieving this, the lockscreen is now stock-style-behavior. Before, when you set all shortcuts to empty, pressing and holding the lock icon would let you drag it to each spot that became empty but it still appeared as an "empty shortcut". Now, you don't see the spots where shortcuts would normally be, it's just all a circle.
(I'm reporting all of this just in case it helps someone )
markd0wn said:
Another bug that I think is introduced in the 08-11 build is lockscreen slider shortcuts not saving (but if you changed them on a previous build and updated to 08-11, they'd probably be set up right).
I managed to save them anyway using a workaround. Basically setting them all as 'Empty' and hitting the save button won't do - you'd turn screen off/on and it will still have the default ones. What I did to 'fix' this is set each one to empty and tap save inbetween changing each one, then tap save again after they're all empty, then I tapped the icon that restores all to default, suddenly the 'default' is what I just set up (all empty), then hit save again, and voila, saved successfully. Could probably skip a few of those steps that I did as I'm sure one of them did the trick and the others were just me testing, but at least it works.
Another thing that confirms that they're changing something related to lockscreen shortcuts, is that after achieving this, the lockscreen is now stock-style-behavior. Before, when you set all shortcuts to empty, pressing and holding the lock icon would let you drag it to each spot that became empty but it still appeared as an "empty shortcut". Now, you don't see the spots where shortcuts would normally be, it's just all a circle.
(I'm reporting all of this just in case it helps someone )
Click to expand...
Click to collapse
They're doing a fairly significant reworking of the entire settings apk and all of the CyanogenMod settings, it's possible something got added/removed that broke this temporarily. I would expect that certain settings menus, etc... may be broken over the next little while before the official nightlies begin.
I'd like to start this out by stating that these are personal builds. I'm not trying to compete with @transi1's developer prowess; on the contrary, I feel he's done a fantastic job with TWRP 3.0.0 and porting CM13 over to the kindles, and he's part of the reason why I'm motivated to do this side project. I'm releasing these for the purpose of bettering the Marshmallow experience on our aging kindles. I want to see if a different build configuration will help improve performance and reduce lag. I'm also wanting to learn my way through the nuances of ROM development, so I intend on starting small.
Click to expand...
Click to collapse
READ THIS BEFORE PROCEEDING ANY FURTHER
I don't intend to fray any circuits when I compile these builds. However, there's always a chance that something could really go wrong and inadvertently damage your device. In such an event, I (and the awesome XDA community) will try our best to help get you back up and running. However, please don't try to sue me if your device:
doesn't work as a result of flashing this;
initiates a nuclear meltdown, or;
doesn't permit your alarm clock to function normally.
By flashing, you automatically assume responsibility for any loss of data, functionality, or facial hair. Although a 10% tip would be nice if it started printing out money.
Click to expand...
Click to collapse
Downloads:
click the Downloads tab at the top of the page, or just click here. I'm also mirroring this on Google Drive for convenience. Builds will go up on AndroidFileHost. Use this link to find and download the latest releases.
OpenGapps: use ARM, 6.0, package of your choice (I'll create a custom .gapps-config later)
SuperSU: make sure to run echo SYSTEMLESS=false>>/data/.supersu in the TWRP terminal (advanced -> terminal) before flashing SuperSU, or else you'll have to perform a restore via fastboot (credit to @r3t3ch for finding the solution)
Features:
[*]Compiled with UBERTC 4.9
UBERTC toolchain causes the post-compiled builds with the 3.0.72+ kernel to break in a really embarrassing way, so this isn't used for now
based on CM13
more to come!
Known issues in post #2
Changelog in post #3
Feel free to respond to this thread to comment or report a bug. I'm open to all feedback.
Credit where credit is due
@Hashcode, because we wouldn't have CM on our kindles at all without him.
@BuQQzz for some mentoring & advice
@transi1 for porting CM13 and providing some useful fixes for build errors
XDA:DevDB Information
[jem] CM redux, ROM for the Amazon 7" Kindle Fire HD
Contributors
monster1612, Hashcode, transi1, BuQQzz
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2016-03-29
Last Updated 2016-08-07
Known issues
Bugs affecting all CM13-based ROMs on the kindle
Screen artifacts when playing video from Snapchat, Vine, etc.
Audio chops in and out often
Other bugs currently afflicting the other CM13 ROMs for this device
Camera currently doesn't work (although it is functional in the 3/20 RR build and earlier ROMs for jem)
Side note: This camera issue is prevalent w/ transi1's CM13 3/28 build, so it's not specific to this ROM only.
Play Store & Setup Wizard FCs
CM pushed a commit to fix the FCs, so now every ROM built from this point forward should be OK with flashing the latest gapps. (thanks to @r3t3ch for the find)
Changelog
08/07/2016
experimental backtracking to kernel 3.0.84+
July '16 AOSP patches (hoping 8/1/16's patchset made it in there too)
07/01/2016
doing yet another revert to the 3.0.72+ kernel, prior to transi's backporting of the newer one (3.0.101+) that broke the camera
June '16 AOSP patches, plus just about everything CM pushed up until 7/1/16
reverting from UBERTC toolchains to native CM/AOSP one
05/20/2016
defecting to BlissRoms-Devices GH for newest device config files
05/2016 security patches from AOSP, et al.
04/27/2016
refreshing CM sources & obtaining latest sources from transi1
04/09/2016
revert the 4/4 kernel reversion; back to 3.0.101(+)
carry in latest edits from transi1 to try to fix the camera
04/04/2016
revert to kernel 3.0.72+
first build that's been mostly summoned from my local jenkins install - now future builds should automatically upload to the AFH server
03/29/2016
initial build!
Roadmap
The following is a list of features I think will make it onto future builds. Feel free to contribute any suggestions, bug reports, etc.
Layers/RRO theming support
Custom boot animation (or at least one scaled to the kindle's screen size)
Possible removal of some unused stock apps (I'll package them into a separate flashable .zip in case)
Publication of a custom .gapps-config file for use with opengapps packages
I'm going to attempt to resolve the infamous camera bug by starting from a known good point in time and backtracking up through transi's kernel commits. This means a lot more frequent builds (sometimes unstable!) in the next couple days. I hope you guys are ready for more testing.
So far, it seems like transi's github commits to the common device repos may have fixed the camera (thus the reason why I didn't release another backtrack through the kernel commits). However, I don't know for sure, as I haven't tested out today's build yet. Any testers coming from earlier builds should not dirty flash this release; a clean wipe would be preferable. Feel free to let me know how things go.
Today's nightly has nothing special in terms of features, etc. However, I'm going to start implementing features as outlined in the roadmap. As usual, do let me know if there's something you'd like to see.
Some updates...
I still haven't gotten around to trying to bring RRO to this ROM. Apparently, CM's theme engine (which should have been compatible with RRO, but isn't) has conflicts with RRO/layers, and those have discouraged me from bringing RRO in (so far).
I think TWRP 3.0.2 needs to be built for both jem & tate. That release has some important fixes regarding encrypted backups, and even the TWRP people themselves recommend you stop using 3.0.1 if you use encrypted backups. I'm going to build for another ROM (hai there, OmniROM!) and compile against that source for TWRP. EDIT: transi said he'd wait till TWRP 3.0.3 is released to compile it, so we can stand to wait for it.
More updates...
It's been a while since the last build. Obviously, this one I just uploaded is about 2 weeks old at the time of writing. You may be wondering why I took so long to drop this build. It's complicated:
I was seriously curious as to how the camera managed to break down during transi's kernel backporting in mid-/late March. Such curiosity led me to attempt to revert the device repos to a stable state so I could build against 3.0.72+ instead of 3.0.101+.
My reversion efforts were successful (for the most part). I was able to get the process to succeed like normal, but when I tested out the builds (compiled against UBERTC), there was a breaking issue. The camera worked well enough (as I expected), but as soon as I tapped any textbox at all (even the password prompt for a WiFi network that required one), the screen would glitch out and force a reboot. I thought that maybe it was an error on CM's part, so I waited a day or so and compiled again, getting the same issue. At that point, I was baffled and decided to recompile with CM's native toolchain instead of UBERTC.
That build was on 7/1, and is the build that was uploaded an hour ago. I had it built then, but was waiting for a good time to test it out to see if that issue was resolved. Sure enough, when I tested it out tonight, it didn't occur.
Also, you may have noticed that I changed the ROM project name to CM redux. I did this to signify that this project won't be a full-on verbatim port of CM. (right now it is, but that's beside the point.) The name won't officially show up in the ROM itself until the next build, most likely.
Finally, some planned changes:
I'm going to continue with my backtracking scheme. I want to know exactly which commit is responsible for the software failure of the camera.
Obvious name change in the ROM, mentioned earlier.
Replacing CM's theme engine with RRO(?)
CM bloat cleanup. The ROM itself boots in 30 seconds, which is nice and all, but I'd like to try to trim it down a little more.
Good version,thanks. But it often wifi reconnect , can it fix?
wizard_mini said:
Good version,thanks. But it often wifi reconnect , can it fix?
Click to expand...
Click to collapse
I have that same issue with other 6.x ROMs, but I'm not sure what the cause is. Could you get a logcat as soon as that issue pops up again?
monster1612 said:
I have that same issue with other 6.x ROMs, but I'm not sure what the cause is. Could you get a logcat as soon as that issue pops up again?
Click to expand...
Click to collapse
It looks like WiFi 2g link no problems, 5g often reconnect. Let me test more time
Android system cost battery drain more than screen, is it normal?
wizard_mini said:
Android system cost battery drain more than screen, is it normal?
Click to expand...
Click to collapse
That depends on what apps you have installed, how heavily you use the device, and other factors. Try installing BetterBatteryStats as a system app, using it for a few days, and then report back some of the data it collects.
I flash the opengapps pico,when I install G-mail app , it said I must add a Google account,but I already setup my Google account, then I can't open gmail. Why?
wizard_mini said:
I flash the opengapps pico,when I install G-mail app , it said I must add a Google account,but I already setup my Google account, then I can't open gmail. Why?
Click to expand...
Click to collapse
I ran into this same problem using RessurectionRemix. I had to install an older version of Gmail, then update it from the Play Store.
Try this version:
http://forum.xda-developers.com/showthread.php?t=1181033
That's not the one I used, but I used a similar version from here somewhere.
sirp0p0 said:
I ran into this same problem using RessurectionRemix. I had to install an older version of Gmail, then update it from the Play Store.
Try this version:
http://forum.xda-developers.com/showthread.php?t=1181033
That's not the one I used, but I used a similar version from here somewhere.
Click to expand...
Click to collapse
It's a good solution,, I fix it, thanks
monster1612 said:
That depends on what apps you have installed, how heavily you use the device, and other factors. Try installing BetterBatteryStats as a system app, using it for a few days, and then report back some of the data it collects.
Click to expand...
Click to collapse
I use 4hours screen on and 7hours screen off cost 92% battery.
wizard_mini said:
I use 4hours screen on and 7hours screen off cost 92% battery.
Click to expand...
Click to collapse
I have a similar issue when I let my kindle sit overnight. I'm guessing it might be a commit that I reversed when I reverted to the 3.0.72+ source. I'll do a new build within the next few days with a few kernel updates thrown in.
monster1612 said:
I have a similar issue when I let my kindle sit overnight. I'm guessing it might be a commit that I reversed when I reverted to the 3.0.72+ source. I'll do a new build within the next few days with a few kernel updates thrown in.
Click to expand...
Click to collapse
Thanks. I am expecting it!