Related
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.
Hello,
I am running CM10 on my OB. I'm actually quite satisfied, but I am looking for two things:
1. Is there a way to install/activate the hidden menu? (the #3845*#970 menu) It was mentioned somewhere that there is a flashable zip, but I can't find it.
2. According to the manual, our OB supports cell broadcast messages. It looks like this support was left out of the CM10 build however. Is there a way to add this support anyhow?
Thanks!
[MOD] tabletUI on AOSP/CM10.1/CM10.2 - Auto-Patcher >>UPDATE: AOSP 4.3 supported!!<<
tabletUI for ANY DEVICE running AOSP, CM10.1, or CM10.2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Check out post 2 for way more screenshots!
All you need is to get the latest version of the Auto-Patcher.(or ApG)
Linux/Mac: Check out mateorod's thread for instructions on getting the auto-patcher set up and how to use it.
Windows: Check Kobik77's post on ApG and download the latest version of ApG, which puts everything you need to make these patches together for you automatically!
Once you have that all set up just run your favourite AOSP, CM or SlimBean rom through the auto-patcher, patching for tabletUI. Auto-patcher will automatically detect your rom type and use the appropriate patches. It really could not be any easier!
(In ApG if you must set the rom type then use AOSP for Slim)
Make A Backup Before Trying Any Of These Mods! I will not be responsible for your data loss.
The Auto-Patcher will produce an update.zip and a restore.zip. I recommend moving both to your device before flashing.
Flash the produced update.zip in recovery and reboot.
Enjoy the tabletUI goodness!
If you do experience any issues, or your device bootloops, or you just want to go back to the way things were before applying the tabletUI mod, boot into recovery and flash the restore.zip. This will replace ALL of the original rom files and you should be able to boot up normally.
Confirmed Devices (Roms):
Nexus 7 - 2013 (AOSP/CM)
Nexus 10 (AOSP/CM)
Nexus 7 (CM)
Galaxy Tab 2 (AOSP/CM/SLIM)
Asus Transformer TF101 (CM)
Nook Color (CM)
Motorola Xoom (CM) - Thanks LQQKS!
Acer Iconia A500 (CM) - Thanks rsriram22!
Galaxy Grand Duos GT-I9082 (CM) - Thanks @karipari95! (who says setting dpi to 160 perfects the tablet look!)
If you have just patched a new device, not on this list let me know so I can add it!Known Issues:
This mod is going away from what android has been moving toward for a few months so there are a few issues with some android features. I personally think that the gains outweigh the losses in this, but depending on your device usage YMMV.
Multi-User: If you use multiple users on your device then this mod is probably not going to work well for you. In tests it seems that any user will get the notifications for all users. They can't be clicked but they do come through and can be seen.
Encryption: I have had a report that enabling Security/Encrypt tablet in conjunction with tabletUI mod will lead to a boot loop.
Notifications: Most notifications will work fine, however certain ones will not be seen:
Storage related notifications may not be seen. For instance the popup to enable mass storage when you plug into your computer.
Persistent Alarm Notification will not be seen when you have the alarm set.
Preferences: Sometimes certain options in Settings (having to do with appearance) will either no longer be present, or will have no effect when changed.
Launcher/Apps: On devices with smaller screens and lower resolutions the default launcher may not look very good after applying tabletUI mods. I recommend using a custom launcher from the play store, like Nova/Holo, which let you customize appearances. Also some apps may appear a little odd, or be missing content. This only affects small, low-res screens and is minimal.(see Youtube: missing/squished "Like"/"Subscribe" buttons)
Bugs/Requests:
If you have to report a failed attempt at patching a rom please include as much detail as you can, including the log from auto-patcher (full log please, not copy/paste of terminal output) and the rom and device you are trying to patch for (link to thread/source appreciated)
Please do not report failures for roms other than those stated as working in this thread; currently AOSP, CM10.1, and SlimBean.
Please do not post requests for support for roms which are not currently supported.
Be aware that some roms which are called "AOSP/AOSP based" are actually heavily modified by their developer already and these patches may fail in that case.
If you need to report an issue with some function that worked on your device before flashing the tabletUI mod but isn't working after, a log of the failure can be very helpful in coming to a solution, and is appreciated. Please check the Known Issues above before reporting.
Thanks/Credits
mateorod & pastime1971 for the amazingly versatile Auto-Patcher!
kobik77 for ApG which really makes the Auto-Patcher accessible for everyone!
barrmulio for all his work on tabletUI!
All the happy, willing testers: brGabriel, 138, 19cam92, dlumberg, astro_75, rraaka, tuxafgmur, and anyone else I am forgetting! Without you...:crying:!
All the awesome, talented developers on XDA that bring us these great roms for our devices! Thanks to each and every one of you for helping make this community what it is!
All my fellow tabletUI fans out there, who don't want to accept an awkward user interface!
Anyone else who has slipped my mind at the moment, and anyone who has ever contributed anything to XDA you're great too!:highfive:
Screenshots:
Galaxy Tab 2 7.0: CM10.1 (for more see here)
Galaxy Tab 2 7.0: SlimBean
Galaxy Tab 2 10.1: CM10.1 (for more see here)
Nexus 10: CM10.1
Nexus 10: AOSP
Asus Transformer TF101: CM10.1
one more just in case
Thank you but still getting the same error with Team EOS4 rom (tf101)
http://codepad.org/S3qVlSss
i9apps said:
Thank you but still getting the same error with Team EOS4 rom (tf101)
http://codepad.org/S3qVlSss
Click to expand...
Click to collapse
That's because there aren't patches for Team EOS roms. Right now your choices are either AOSP, CM10.1, or Slim.
"Recent Apps" style?
Maybe I didn't get it right but after patching my CM 10.1 on my Nook Color the "Recent Apps" button still shows the phone style not the tablet one Recent Apps view!? Maybe this should be added to "Known Issues".
SGH-i200 said:
Maybe I didn't get it right but after patching my CM 10.1 on my Nook Color the "Recent Apps" button still shows the phone style not the tablet one Recent Apps view!? Maybe this should be added to "Known Issues".
Click to expand...
Click to collapse
Thank you for the report. I guess to be honest I don't really think of this as an "issue" but I guess that you are right. At best it is still a shortcoming in acheiving what you would expect as tabletUI. I will have to see if I can get it to look like in Honeycomb, where it was a column view, pushed to the left of the screen. That is the way that you mean, right?
@SGH-i200
I think that I got it all sorted out the way you would like. I will try to include this fix in the auto-patcher the next time I update the tabletUI patches. It does look better this way, thanks for the push!
Awesome work Caldair!
Well done. Thanks for helping us Slimbeaners keep our phones secure.
Do you know what the GsmServiceStateTracker.smali does?
I see this error when I am compiling the latest Slim 4.2.2 build 4 patch.
It still completes the patch, and the patch works with no problems. Some people on the Slim thread have reported problems with Google maps, but as I have maps & network location disabled, I can't say.
Oddly it wasn't there on build 2.5
Anyways, thanks again for all your help in making Slimbean a safe rom.
Didgesteve said:
Well done. Thanks for helping us Slimbeaners keep our phones secure.
Do you know what the GsmServiceStateTracker.smali does?
I see this error when I am compiling the latest Slim 4.2.2 build 4 patch.
It still completes the patch, and the patch works with no problems. Some people on the Slim thread have reported problems with Google maps, but as I have maps & network location disabled, I can't say.
Oddly it wasn't there on build 2.5
Anyways, thanks again for all your help in making Slimbean a safe rom.
Click to expand...
Click to collapse
Sorry, I don't know anything about that. I saw your post at the auto-patcher main thread as well and I think you have the wrong impression. This thread is meant to be for discussion of the tabletUI mod part of the auto-patcher. Your question would be better in the main thread, and trust me, those guys are way smarter than me anyway.
Updates were just pulled into auto-patcher. ApG users can try the newest patches right now, otherwise you could pull from Mateor/auto-patcher on github or wait for the next auto-patcher release.
Huge thanks to tuxafgmur for all the work he did on streamlining these patches!:good::good:
These changes help reduce the extra load that tabletUI seems to put on the gpu!
Also fixed the 'latest' symlink in the CM patch so you should be able to use multiple auto-patcher mods together with tabletUI (ie. pdroid)
And I changed the appearance of the recent apps panel so it is more similar to the old style tablet recent apps (similar to the pictures I posted a couple posts back), hope you like it!
hey mate,
i'm trying to patch this mod into my cm10.1 rom on Xoom MZ601 everest.
i've already seen that someone did it successfully on the Xoom wingray.
but when i try : it fails to extract the build prop
hopefully the attached AP log will tell you something
this is on the most recent version of APG
LQQKS said:
hey mate,
i'm trying to patch this mod into my cm10.1 rom on Xoom MZ601 everest.
i've already seen that someone did it successfully on the Xoom wingray.
but when i try : it fails to extract the build prop
hopefully the attached AP log will tell you something
this is on the most recent version of APG
Click to expand...
Click to collapse
From the look of your log I think there is something wrong with your ApG installation.
I have never used ApG, as I don't use windows, so unfortunately I can't really be very helpful with this issue. But the patcher really should be working for that rom.
Maybe you could try completely removing ApG and starting fresh, that may help. I hope!
OK I will try that when I get home
and I've found a patched version that I'm running but I'd like to do it myself as I update CM10.1 frequently
Thanks for the help
Edit: working now \o/ I had a bad download of the rom, everything else was sweet feels like a complete n00b
You can add Xoom MZ601 Everest to list of confirmed working devices (CM10.1) thanks heaps Caldair for the awesome mod \o/
Sent from my rooted Xoom MZ601
running Elemental CM10.1
using XDA Premium app \o/
LQQKS said:
OK I will try that when I get home
and I've found a patched version that I'm running but I'd like to do it myself as I update CM10.1 frequently
Thanks for the help
Edit: working now \o/ I had a bad download of the rom, everything else was sweet feels like a complete n00b
You can add Xoom MZ601 Everest to list of confirmed working devices (CM10.1) thanks heaps Caldair for the awesome mod \o/
Sent from my rooted Xoom MZ601
running Elemental CM10.1
using XDA Premium app \o/
Click to expand...
Click to collapse
Glad to hear it!
And don't worry we all fall victim to the simplest mistakes. They are never simple until you find the solution, and they are usually the most frustrating to solve!
Thanks for sharing your success:highfive: I will add the Xoom to confirmed devices!
@i9apps @rafal.k
For all you teamEOS users out there I have put together a test build of the Auto-Patcher that will patch your EOS roms for tabletUI!
I made test patches for Asus Transformer tf101. These zips are based on the build dated: 2013-05-05 from http://goo.im/devs/teameos/roms/eos4/nightlies/tf101 and must be used on that build and only on the tf101: The top 2 attachments are for the tf101.
I also made test patches for the Motorola Xoom Wingray model. These are based on the build dated 2013-05-04 from http://goo.im/devs/teameos/roms/eos4/nightlies/wingray and must be used on that build date and only on the Wingray: The bottom 2 attachments are for the wingray.
I don't have either of these devices to test and there is no EOS rom for the tablets that I do have so be warned:
These are completely UNTESTED! Be sure to download both the update and restore file and have them both on your device before flashing the update.zip in recovery. This way if you have issues like boot loops all you need to do is get back in recovery and flash the restore.zip to have all the original rom files back.
I hope to get some feedback on whether these patches work or not and then I can procede with getting EOS roms supported in the Auto-Patcher for TabletUI. Then EOS users with any device should be able to make these patches for any build!
I anxiously await your feedback:fingers-crossed:
Edit: Well I got my feedback... and it was not good:crying: To make matters worse I have since read in one of the EOS threads that bigrushdog is working on bringing tabletUI back into these roms anyway, so I am just going to leave this for now. You EOS users should have your tabletUI back before you know it anyway!
ATTACHMENTS REMOVED.
Caldair said:
@i9apps @rafal.k
For all you teamEOS users out there I have put together a test build of the Auto-Patcher that will patch your EOS roms for tabletUI!
I made test patches for Asus Transformer tf101. These zips are based on the build dated: 2013-05-05 from http://goo.im/devs/teameos/roms/eos4/nightlies/tf101 and must be used on that build and only on the tf101: The top 2 attachments are for the tf101.
I also made test patches for the Motorola Xoom Wingray model. These are based on the build dated 2013-05-04 from http://goo.im/devs/teameos/roms/eos4/nightlies/wingray and must be used on that build date and only on the Wingray: The bottom 2 attachments are for the wingray.
I don't have either of these devices to test and there is no EOS rom for the tablets that I do have so be warned:
These are completely UNTESTED! Be sure to download both the update and restore file and have them both on your device before flashing the update.zip in recovery. This way if you have issues like boot loops all you need to do is get back in recovery and flash the restore.zip to have all the original rom files back.
I hope to get some feedback on whether these patches work or not and then I can procede with getting EOS roms supported in the Auto-Patcher for TabletUI. Then EOS users with any device should be able to make these patches for any build!
I anxiously await your feedback:fingers-crossed:
Click to expand...
Click to collapse
I tried the Xoom version and as soon as it enters the OS I get a neverending "Unfortunately System UI has stopped"
I click OK and it immediately pops up again.
Let me know if there's something specific you'd like me to try that will help you debug.
Caldair said:
@i9apps @rafal.k
For all you teamEOS users out there I have put together a test build of the Auto-Patcher that will patch your EOS roms for tabletUI!
I made test patches for Asus Transformer tf101. These zips are based on the build dated: 2013-05-05 from http://goo.im/devs/teameos/roms/eos4/nightlies/tf101 and must be used on that build and only on the tf101: The top 2 attachments are for the tf101.
I also made test patches for the Motorola Xoom Wingray model. These are based on the build dated 2013-05-04 from http://goo.im/devs/teameos/roms/eos4/nightlies/wingray and must be used on that build date and only on the Wingray: The bottom 2 attachments are for the wingray.
I don't have either of these devices to test and there is no EOS rom for the tablets that I do have so be warned:
These are completely UNTESTED! Be sure to download both the update and restore file and have them both on your device before flashing the update.zip in recovery. This way if you have issues like boot loops all you need to do is get back in recovery and flash the restore.zip to have all the original rom files back.
I hope to get some feedback on whether these patches work or not and then I can procede with getting EOS roms supported in the Auto-Patcher for TabletUI. Then EOS users with any device should be able to make these patches for any build!
I anxiously await your feedback:fingers-crossed:
Click to expand...
Click to collapse
Tried with nightly 112 for TF101. Did not work. System UI kept crashing and I could not use the pad. Had to wipe system and reinstall without this.
drewski_1 said:
I tried the Xoom version and as soon as it enters the OS I get a neverending "Unfortunately System UI has stopped"
I click OK and it immediately pops up again.
Let me know if there's something specific you'd like me to try that will help you debug.
Click to expand...
Click to collapse
Gatak said:
Tried with nightly 112 for TF101. Did not work. System UI kept crashing and I could not use the pad. Had to wipe system and reinstall without this.
Click to expand...
Click to collapse
Thanks to you both for testing this! I am sorry that it failed so miserably and you had to wipe and reinstall.
For now I will take a closer look at the patches themselves and the sources. There is definitely more going on in EOS roms than other AOSP/based roms, especially in SystemUI.apk.
Gatak, I would have said your issue could have been caused by the fact that you tried to flash the update over a newer build than the modded files came from, but since drewski_1 had the same exact issue I think the patches are probably not right.
Drewski_1, I am assuming that you did flash the update on a wingray model and that you were running the corresponding build of the rom, dated 2013-05-04. If that is not the case, and you are also using a newer (or older) build, please let me know.
These patches can really screw up when used on different nightly (or weekly or whatever the build frequency is for EOS) builds than they were based on. Devs can change a lot in a week, and these patches contain important core files.
Thanks again to you both, I really want to get EOS working. I see how many downloads there are of these roms from goo.im, just for these 2 devices, so I know a lot of people would benefit from this.
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.
This thread is for the developers to discuss the bugs and problems of the kitkat development for the p990.
Nice that you created a thread for kitkat! Really thanks
So for the progress on cm 11:
It is really difficult to find the cause of the dark screen, because we can't get an adb connection to working. The devices don't show up with adb devices
Maybe it is disabled at the moment
We can't take all changes from your slimroms repo, because cyanogenmod toke another way in handling backward compatibility. So for now we have a dark screen with cm 11 and no adb
Here are some of the threads from other tegra2 devices which I'm following:
Galaxy R: link
Galaxy Tab 10.1: link
Captivate Glide: link
Xoom: link
P990: link
Additional T2 devices where I didn't see any Kitkat related threads, yet:
Eee Pad TF101: link
Atrix 4G: link
All still suffer from the same problems, we need some proper workarounds (in frameworks/native most likely) to fix the hot reboots before we can move on to fix the smaller problems.
I've posted in some of them in order to help with other problems (like the set_metadata one where I send the fix to @DJNoXD as well), but I have no idea how to fix the hot reboots currently.
Personally I don't see a use in fixing various stuff as long as the device is too unstable thanks to the reboots (that's why you won't find any 4.4 thread from my so far).
I'm just collecting some information in this thread to have everything together.
Therefore some more stuff regarding the device stuck at boot which we faced earlier as well:
tonyp said:
The only way to fix the blobs would be an update by nvidia / the vendors - which isn't happening obviously.
So you need to workaround the limitations of the old EGL in the sources to re-add compatibility (which btw had to be done for Android 4.3 and partly Android 4.2 as well).
The reason that CM11 doesn't boot up for you is that CM hasn't merged the required patches.
The commits do exist on CMs gerrit though:
http://review.cyanogenmod.org/#/q/s.../android_frameworks_native+branch:cm-11.0,n,z
They're new implementations of the CM10.2 patches by arcee.
Note that in some first tests the new ones didn't work for me on my tegra2 phone anymore - somethings seems to be broken in them for the tegra2 architechture.
The OmniROM has (had? I think they partly reverted it here) used forwardports of the old CM10.2 patches - which the SlimROM has merged as well in a similiar manner.
But this only fixes booting, I still do have way to many hot reboots so some more stuff has changed in 4.4 - which I didn't manage to fix or workaround so far.
What we need is someone with that kind of deep hardware knowledge.
All in all: Blindly changing blobs or other libs won't help here at all. Just building against different framework/native trees won't either.
The surfaceflinger and probably some more stuff in frameworks/native needs to get worked on in code.
Currently there doesn't exist a tegra2 device which fully works to my knowledge - and I'm following a couple ones like the Galaxy R, the Xoom, the Transformer TF 101, the Atrix and the Galaxy Tab 10.1.
I'm working on the 2x, but have way too less time at the moment to dig any deeper into the code - while the current ROM boots (using my frameworks/native repo here) and has a working ril, wifi & storage it's nowhere near a daily driver thanks to frequent hot reboots.
Click to expand...
Click to collapse
Edit: Reminder: Do not spam in this forum section!
I will delete all "thanks" posts or similiar non-development related ones without a comment.
When i use the sources for frameworks native from @DJNoXD, i have less then 2 hot reboots a day. I even use it as daily driver with a work around for wifi.
I think if we could find the commits that broke the stability we could search for a work around or fix. I already tried it only for the sufaceflinger but i had no success, because it still worked properly, so it maybe is related to libgui or i think libui?
Took me hours for the surfaceflinger, so it will take even more time for all other in framework native. When i found some time during the week, i will try.
But KitKat is awesome related to RAM, Multitasking and performance.
Gesendet von meinem LG-P990 mit Tapatalk
Evervolv frameworks/native etc were no help getting the tf101 to boot omni. So far we're at Boot Animation
thx to
kishoreinme said:
Having the 3 perfhud .so files in /lib/egl/ causes this. Delete them and it boots
Click to expand...
Click to collapse
from this thread: http://forum.xda-developers.com/showthread.php?t=2517719&page=9
http://forum.xda-developers.com/showthread.php?t=2489841&page=7
Firtecy said:
When i use the sources for frameworks native from @DJNoXD, i have less then 2 hot reboots a day. I even use it as daily driver with a work around for wifi.
Gesendet von meinem LG-P990 mit Tapatalk
Click to expand...
Click to collapse
Is that the frameworks from slimrom or from https://github.com/DJNoXD/frameworks_av1 ?
dlumberg said:
Is that the frameworks from slimrom or from https://github.com/DJNoXD/frameworks_av1 ?
Click to expand...
Click to collapse
These are the repos that I use for slimrom:
https://github.com/p990-slimrom/
Here is the GalaxyR Omni 4.4.2 development link
http://forum.xda-developers.com/showthread.php?t=2576793
Eeeeh, have I been gifted with a special P990?
I've flashed Tonyp's 4.4 build named cm-11-20131213-UNOFFICIAL-p990 and I am pretty much facing no bugs. Only bug I could find on this fine evening was that USB doesn't get mounted, it charges when connected though.
Sound works, camera works, external SD card works, WiFi works, I bet GPS works but testing that will have to wait till the morning. All of this is on a clean CM11 build without doing any modifications at all. I too am still shocked over this and since I couldn't believe it myself, so I figured I'd post a video bringing this to light.
Short YouTube footage of my P990 running KitKat: YouTube
Could someone do a full wipe and see what they come up with by flashing that same build? It seems rather surreal if 4.4 only works this well on just my phone.
Please note, I have not been under the developmental processes of this project. This is simply testing - all credits to the developers!
USB tether will not work under windows because there are no drivers found. And it works fine under linux. How to fix the hardware id (vid,pid)?
Sent from my XT875 using XDA Premium 4 mobile app