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.
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.
Yes, this is a discussion thread, but you are not allowed to make "meaningless" posts in here.
If you have made some discoveries post it, but no one in here is interested in "thank you" posts or similiar.
Okay, let's try to get the Android 4.2 gapps working as good as possible on our phone.
As you know Google dropped support of non-neon phones and tablets with Android 4.2.
Our Tegra2 SoC doesn't support these neon instructions, which results in a couple problems with the default gapps package.
We need to replace a couple files with older ones to get everything back working.
Update 27.04: I finally found some time to work on gapps and provide a (hopefully) fully working non-neon gapps package in the second post now!
One example: the biggest annoyance is probably the dying keyboard.
This happens because the gapps package replaces the libjni_latinime.so file included in the ROMs with a proprietary one by Google to enable Gesture input.
Unfortunately it does need neon, so you should remove the file inside the gapps package (/system/lib/) before flashing it.
In the logcat you'll usually see a SIGILL error, like this one:
Code:
A/libc(3910): Fatal signal 4 (SIGILL) at 0x4f6233a6 (code=1), thread 3910 (putmethod.latin)
I/DEBUG(92): signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 4f6233a6
I'm starting this thread to colloborate together on a gapps package with as much stuff working as possible, so if you do have any insights please share them
You can download the CM10 gapps package and get the nonneon files (they're in /optional/nonneon) - but not all of them are still working with Android 4.2.
P.S.: For the love of God, don't call them fapps - fapps is a foss (free and open source) package which uses OpenStreetMaps instead of GMaps and so on.
We still want gapps, just without neon libs.
Okay, here's my non-neon fixed gapps package.
Important: If you already flashed another gapps package do format /system, reflash your ROM then reflash these gapps.
If you don't do that you'll have leftovers from the former package, which results e.g. in a dying keyboard.
Changes compared to the official package:
Fixed the aosp keyboard crashes
Fixed Google Talk videochat crashing
Fixed Faceunlock
Fixed Google TTS
Fixed Google Now & Voice Search crashes on non neon devices & restored hot-word detection
Fixed Talkback
Removed unuseful stuff
Notes:
Swipe keyboard won't work - nothing I can do about that.
Complain to Google for dropping non-neon support
Same thing goes to Photoshpere - no neon: no love.
Don't try to update Google Now - the new version doesn't properly work without neon (not sure if this still applies?)
Download:
http://goo.im/devs/tonyp/non-neon-gapps
If you're interested in more details what parts I changed - here you go.
This will hopefully ensure that future gapps versions will get provided as well
to fix facelock: replace libfacelock_jni.so with non-neon lib (credits: Adam77Root)
to fix the keyboard closing: remove libjni_latinime.so
to fix google videochat: added libvideochat_stabilize.so, replaced libgtalk_jni.so with non-neon lib and removed libgtalk_stabilize.so
to fix TTS: replaced libpatts_engine_jni_api.so with a non-neon lib and GoogleTTS.apk with the apk from the teameos gapps package.
to fix Google Now and Voice Search I replaced the QuickSearchBox.apk with this one by Steady Hawkin.
Note that the newest Google Now version isn't compatible with non neon devices anymore, thus this version disables the auto-update.
replaced Talkback.apk with a working version from the eos gapps package.
Partial credits for steps 1-4 go to bubor who already started with a non-neon gapps package.
Then I reflected these changes in the 70-gapps.sh backup script.
That's important because otherwise updating the ROM will break the gapps!
Why? Updating the ROM does wipe /system - only the files which are in the script will retain.
This means that e.g. the libvideochat_stabilize.so will poof away and the libjni_latinime.so won't get updates anymore.
Additionally I removed the g.prop file in /system/etc to prevent the GooManager from trying to update the gapps package if new (neon) updates come.
To reduce the package size I completely removed the photosphere stuff.
Just a thought here: since our cpu does not support neon instruction set, wouldn't it be an option to patch the P990's kernel with an neon-emulator? This way, the neon instructions will be translated into something the cpu can process. Corrrect me if I'm wrong.
I'm saying this because I've seen something similar happen on Mac OS X, where version 10.8.x requires a cpu capable of SSSE3 (not SSE3) instructions. They have patched the kernel with an SSSE3 emulator so that it works on older hardware and AMD cpus.
Sent from my LG-P990 using xda premium
Robin2 said:
Just a thought here: since our cpu does not support neon instruction set, wouldn't it be an option to patch the P990's kernel with an neon-emulator? This way, the neon instructions will be translated into something the cpu can process. Corrrect me if I'm wrong.
I'm saying this because I've seen something similar happen on Mac OS X, where version 10.8.x requires a cpu capable of SSSE3 (not SSE3) instructions. They have patched the kernel with an SSSE3 emulator so that it works on older hardware and AMD cpus.
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
I'm thinking about the exact opposite - try to disassemble the libs, replace the neon instructions and reassemble. Not sure yet how much work it would take though...
bugadani said:
I'm thinking about the exact opposite - try to disassemble the libs, replace the neon instructions and reassemble. Not sure yet how much work it would take though...
Click to expand...
Click to collapse
this will be an horrendous work. I've seen some projects trying to hack armv6 instructions into the newer armv7 packages - it's really hard as you have to do it in smali as Google won't release it's sources.
I'm extremely full with loads of projects currently - I'm still hoping some people will take this over and try to build a nicely working non neon gapps version. this only requires trial and error, no real technical knowledge. but the interest seems low
Sent from my LG-P990 using xda app-developers app
Developer or not... But since you said yourself that "this will be an horrendous work", allow me include a little something here.
Changelog:
* All apps updated to 4.2.2 versions
* Google Play Store updated to 3.10.14
* Google Play Services updated to 3.0.25
* Gmail2.apk (Gmail) and GoogleEars.apk (Sound Search for Google Play) removed since they are available in the Google Play Store
** May require uninstalling and reinstalling Gmail and Sound Search after flashing.
* Keeps previous version's Photosphere/Picasa sync install on Mako, Manta, and Tuna.
Click to expand...
Click to collapse
From the way I see it, this horrendos work wouldn't really pay off since the earlier version of Gapps has... well... more or less everything the so-called new version has. So why bother if I may ask?
Back to you sir
Soooo, I have been looking into this for the past few days. I think I have got an understand of this that is good enough to make this work.
Since you are working so hard on CM10.1, I'll be willing to put great effort into this. Already started out with some basics, but I am pretty confident that I can make it work by the end of this week.
Will do some proper testing when it has been finished, once everything has been worked out, I'll push it public so you all can have the joy of using it in whatever way you may please
natalya said:
Soooo, I have been looking into this for the past few days. I think I have got an understand of this that is good enough to make this work.
Since you are working so hard on CM10.1, I'll be willing to put great effort into this. Already started out with some basics, but I am pretty confident that I can make it work by the end of this week.
Will do some proper testing when it has been finished, once everything has been worked out, I'll push it public so you all can have the joy of using it in whatever way you may please
Click to expand...
Click to collapse
Any news on your project?
Well, I'm a little disappointed that no one else worked on this - it's basically using Google and trial and error.
Thanks goes to massimo who has offered me some help and did some tests
Anyways, I decided to take matters into my own hands now, as I want to release CM10.1 over the weekend and don't want people to complain because they flashed the wrong gapps packages.
@natalya: If there's anything else you discovered which isn't working please provide it, but as you didn't post what you did in almost 2 weeks now I didn't want to wait anymore.
Changes compared to the official package:
Fixed the aosp keyboard crashes
(note: swipe won't work on non neon devices, nothing I can do about that)
Fixed Google Talk videochat crashing
Fixed Faceunlock
Fixed Google Now & Voice Search crashes on non neon devices & restored hot-word detection
Fixed Talkback
Removed unuseful stuff
Let me explain the steps taken so others can learn what has been done and can update gapps theirselves.
to fix facelock: I replace libfacelock_jni.so with non-neon lib (credits: Adam77Root)
to fix the keyboard closing: I removed libjni_latinime.so
(note: this diables the keyboard swiping - it will never fully work on non-neon devices!)
to fix google videochat: added libvideochat_stabilize.so, replaced libgtalk_jni.so with non-neon lib and removed libgtalk_stabilize.so
to (partially) fix TTS: replaced libpatts_engine_jni_api.so with a non-neon lib
to fix Google Now and Voice Search I replaced the QuickSearchBox.apk and added the libgoogle_recognizer_jni_l.so lib from this one by Steady Hawkin.
Note that the newest Google Now version isn't compatible with non neon devices anymore, so this one disables the auto-update
replaced Talkback.apk with a working version from the above gapps package[/url].
Note the English TTS not working, see below.
Partial credits for steps 1-4 go to bubor who already started with a non-neon gapps package.
Then I reflected these changes in the 70-gapps.sh backup script.
That's important because otherwise updating the ROM will break the gapps!
Why? Updating the ROM does wipe /system - only the files which are in the script will retain.
This means that e.g. the libvideochat_stabilize.so will poof away and the libjni_latinime.so won't get updates anymore.
Additionally I removed the g.prop file in /system/etc to prevent the GooManager from trying to update the gapps package if new (neon) updates come.
To reduce the package size I completely removed the photosphere stuff.
As for the swipe keyboard this feature requires neon-support and will not work properly on our phone, no matter what.
Known bugs:
Google text to speech doesn't seem to work in English. fixed
Download:
http://goo.im/devs/tonyp/non-neon-gapps
If you already flashed another gapps package do format /system, reflash your ROM then reflash these gapps.
This is needed to ensure nothing remains broken from former flashes.
Please give some feedback for this gapps package.
If something doesn't work don't forget to attach a logcat
Okay, I managed to fix the Google-text-to-speech engine as well by replacing the GoogleTTS.apk with the one from the teameos gapps package.
I pushed the new version online and removed the old one.
All bugs I am aware of are now fixed, if you notice anything else that isn't working please give feedback
Time to clean up the OP.
tonyp said:
[*]Don't try to update Google Now - the new version doesn't properly work without neon.
Click to expand...
Click to collapse
Play store is offering me to update Google Search after installing your CM10.1 ROM and this gapps package. Is Google Now part of Google Search so I should avoid this update too?
ciarpame said:
Play store is offering me to update Google Search after installing your CM10.1 ROM and this gapps package. Is Google Now part of Google Search so I should avoid this update too?
Click to expand...
Click to collapse
You can update it and you can use it.
Sadly it has huge lags (as in it freezes from time to time and the waiting times can be taking forever sometimes)
Sent from my LG-P990 using xda app-developers app
For those who want to use the aosp-keyboard, Google recently released Google-keyboard (witch is similar to the aosp, but fully non-neon compatible)
In the US it should be available through the play store, for the others http://dl.androidnext.de/com.google.android.inputmethod.latin.apk
our 2x learns gesture typing
Thread cleaned up.
This is the dev discussion subforum so it's not the right place to ask about specific ROMs.
If you'll find out something new for the non-neon gapps package then you can post in here, everything else goes into the other sections.
Thank you!
P.S.: I've tried extracted the new lib (libjni_unbundled_latinimegoogle.so) from the Google keyboard - it's not compatible to the AOSP one included in ROMs.
If you want to include it into the gapps package you need to rename the apk to LatinIME.apk and add the lib, then it'll overwrite the AOSP keyboard.
(I'm too lazy to update the gapps package in here for a keyboard you can simply install).
I created a non-neon gapps package with the keyboard included.
It will replace the AOSP keyboard by the very similar google keyboard (that fixes gesture typing). Everything else is like tonyps-non-neon-gapps.
Download gapps-jb-20130427-nonneon-tonyp-keyboard.zip
All credits to Google, tonyp and the others mentiont in the first post.
Have fun!
P.S. @tonyp if you want you can put it on the gooserver to the other gapps.
Latest Google Now (26/06/2013) seems to work just fine. I'm not getting those crazy UI lags I got before, if I updated Google Now from the play store
Since the files from tonyp on goo.im are down, here is the working downloadlink for non-neon Gapps:
http://tonyp.basketbuild.com/downlo...on-gapps-/gapps-jb-20130427-nonneon-tonyp.zip
New google keyboard is available: link
DJNoXD said:
New google keyboard is available: link
Click to expand...
Click to collapse
Ah good that you're reviving this thread, I've been meaning to update it with some information.
I never intended to maintain a gapps package and won't do so.
So if someone wants to follow my instructions and offer updated neon-compatible packages for 4.3 and 4.4 go ahead.
The instructions should still apply, but things may have changed a little in the newer versions so they might needs some adaption (e.g. the Talk to Hangouts transition).
Personally I include a mini/tiny gapps neon compatible package in all my ROMs which only contains the most important apps.
I've created the package quite some time ago, it is fully open sourced and can (and already is) used by everyone.
https://github.com/tonyp/android_vendor_google
I update the repo on my own accord, if someone needs a faster update pull requests are always welcome.
But gapps are capable of updating theirselves via the play store, so this usually isn't needed anyways.
I would prefer if others are using my repo and sent pull requests instead of forking and forgetting about the origin, but that's of course your choice.
To include the gapps into your own build you have to add the repo to your manifest and add the following lines to a makefile.
(it doesn't matter which one as long as it's called - an obvious choice would be somewhere in the device tree):
Code:
MINI_GAPPS := true
$(call inherit-product, vendor/google/tiny_gapps_nonneon_tonyp.mk)
P.S.: @DJNoXD This isn't directed at you, I know you're already using my gapps repo in your roms, just a headsup for other potential devs.
tonyp said:
Ah good that you're reviving this thread, I've been meaning to update it with some information.
I never intended to maintain a gapps package and won't do so.
So if someone wants to follow my instructions and offer updated neon-compatible packages for 4.3 and 4.4 go ahead.
The instructions should still apply, but things may have changed a little in the newer versions so they might needs some adaption (e.g. the Talk to Hangouts transition).
Click to expand...
Click to collapse
Hi @tonyp, I hope it's ok to revive this thread again resp. to hijack it a bit from your original intention!? Even if the origin of my following NEON related questions is founded in my lag problems with CM11 2014/11/13 build by @gucky01
gucky01 said:
http://sourceforge.net/projects/lgo...m-11-20141113-UNOFFICIAL-p990.m1.zip/download
Here we go, guys! As promised, here the first build. It`s 100% Tonys work. So we have to thank him for his great work!
All the best to you!
Click to expand...
Click to collapse
I find they fit this thread much better than any other CM10.x/CM11/CM12 ROM XDA thread. Not just one but all of those ROMs are affected by the missing NEON instruction set of the Tegra 2 SOC.
How can one prove wether a current ROM does not call any NEON instructions? Is it sufficient to see that there are no SIGILL entries in the logs?
Let's assume a dev releases a ROM that initially does not call any NEON instructions. Is it possible that updates of Google apps introduce calls of NEON instructions making the ROM misfunctional/unusable?
AFAI understood your trick to assemble non-NEON gapps is to replace shared opjects ( .so files) that call NEON instructions by their (more or less) equivalent non-NEON shared objects. Could there be Google apps or third party apps that call NEON instructions in their core binary?
If so, our P990 will not able to run them, right? I'd like to assemble a list of apps that won't run without NEON support (is there still any list?).
Do calls of NEON instructions on systems that don't support NEON always result in FCs, hot re-boots, or BSODs? Other way round: can calls of NEON instructions on systems that don't support NEON also result in lag or even heavy lag? (gmail 5.0.1 uses to take 10 seconds to start in my recently installed CM11 after the cleanest install possible; I just left the BB and system data/cal un-touched).
I am looking forward for your reply, well-knowing that you don't use the P990 as your daily driver any more for a long time now.
I wish you all a good 2015!
CM12.{0,1} (Lollipop) official/unofficial builds for the Droid 4
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0/5.1 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at any of us for messing up your device, we will laugh at you.
* Collectively, and at the same time.
*/
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. Linked below is a package that has come from another Android project that restore the Google parts. 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 our Gerrit Code Review.
These are WIP builds of porting CM12.{0,1} to the Droid 4 (and also other devices using the same device/motorola/omap4-common-infrastructure). They probably won't work, so don't expect too much. Use on your own risk!
Builds:
Last official build:
http://droid.cs.fau.de/cm-12.1/official/
Old manual builds:
http://droid.cs.fau.de/cm-12.0/pre-alpha-test/new_safestrap/
Changes (only device/family specific, CM base is always synced before build and contains more changes):
2015-04-16:
Switched CM build-target, new nightlies will now be 12.1: http://review.cyanogenmod.org/#/c/94693/
2015-02-01:
No more unofficial builds! See: http://review.cyanogenmod.org/#/c/87596/
2015-01-28:
Mobile data fixes
Remaining com.android.phone crashes on VZW finally fixed (thanks @joojoobee666)
2015-01-24:
Fixed sw-keyboard popup when hw-keyboard is used (thanks @joojoobee666)
Fixed reboot to recovery
Fixed sepolicy for whisperd (dock service)
2015-01-22:
Fixed su-permissions
Crashes on Verizon most likely fixed, please report back
2015-01-20:
Fixed flashlight
2015-01-18:
SELinux updates.
This requires manual action for applications to continue being able to access their own files when upgrading from 2014-01-14 or 2014-01-15 (older versions are fine)!
Due to SELinux-bugs in 2014-01-1{4,5}, you have to relabel your data-partition on the first boot when upgrading from 2014-01-14/-15. This only needs to be done once. To do this, enable adb/usb debugging and grant root to adb (both in developer settings) and execute via an adb shell:
Code:
su -c 'for i in /data/*; do echo "${i}"; restorecon -DFrv "${i}"; done; sync; reboot'
2015-01-1{4,5}:
More fixes for {,umts_}spyder
sepolicy updates
GSM fixes
notable CM changes: su integration fixed
2015-01-11:
Updated SELinux policies (mostly for spyder/umts_spyder)
Added kernel stability fixes
Video decoding fixes
2015-01-09:
Enabled SELinux enforcing
Add SELinux-policies for motorola services
Enable ro.telephony.get_imsi_from_sim on VZW devices (thanks @joojoobee666)
2015-01-02:
Sync CM changes
2014-12-23:
Fixed stock camera
2014-12-22:
Sync CM changes
Fix build due to P2P changes (fix pushed into CM)
Enabled security for adb (keys/not root by default)
2014-11-30:
Added APN fixes for CDMA/LTE
Enabled multiuser mode (might not work yet)
Last update for a couple of weeks
2014-11-27:
Fixed graphics glitches
2014-11-26:
Fixed HW video-decoding
Enabled doze mode (no pickup sensor in the devices!)
CM resync as always
2014-11-23:
Probably fixed mobile data on LTE
Fixed WiFi-tethering
2014-11-22:
Requires a recovery supporting SELinux
What's working:
Phone (tested on Verizon and on GSM/UMTS in Europe)
Mobile data (at least on GSM/UMTS in Europe)
WiFi
WiFi-tethering
GPS
Camera
Playback of DRM-protected content (using Widevine from OnePlusOne)
What's not working:
Probably most everything else, including, but not limited to:
Some connectivity issues (should be solved now)
Data encryption
Gapps (CM-12.0):
Dhacker29 provides gapps for Lollipop:
http://d-h.st/YQG
http://d-h.st/jzr
http://droid.cs.fau.de/cm-12.0/gapps/ (Mirror)
Gapps (CM-12.1):
https://github.com/cgapps/vendor_google/releases/
Installation:
You need a new recovery supporting SELinux
An updated Safestrap (3.75) which supports SELinux can be found here: https://github.com/stargo/android_packages_apps_Safestrap/releases/tag/v3.75
Please read the instructions on how to install this version and follow the order of the steps in it.
GSM users:
To use this CM12.{0,1}-ROM on GSM-networks you should install Mentor.37's GSM patch
Source / Repositories:
maserati device-support: https://github.com/CyanogenMod/android_device_motorola_maserati
omap4-common device-support: https://github.com/CyanogenMod/android_device_motorola_omap4-common
omap4-common kernel: https://github.com/CyanogenMod/android_kernel_motorola_omap4-common
local manifest to build cm-12 for the Droid 4: http://droid.cs.fau.de/cm-12.0/pre-alpha-test/new_safestrap/local_manifest.xml
XDA:DevDB Information
CM 12.{0,1} on Motorola Droid4, ROM for the Motorola Droid 4
Contributors
stargo, Hashcode, Dhacker29
Source Code: https://github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: No Longer Updated
Created 2014-11-23
Last Updated 2016-02-16
thank you @stargo, I am so pleased to see this thread, I was wondering when this thread is going to appear. Looks like I will continue to cling onto my droid 4 for a while, no virtual keyboard can beat a droid 4 keyboard.
Is data encryption enabled by default like on the nexus 6? I read that it greatly reduces the performance of the device. I meant this: http://www.xda-developers.com/android/disable-data-encryption-nexus-6/
Once again, thank you so much for your efforts in keeping this device alive.
sharptv said:
thank you @stargo, I am so pleased to see this thread, I was wondering when this thread is going to appear. Looks like I will continue to cling onto my droid 4 for a while, no virtual keyboard can beat a droid 4 keyboard.
Click to expand...
Click to collapse
Is data encryption enabled by default like on the nexus 6? I read that it greatly reduces the performance of the device. I meant this: http://www.xda-developers.com/android/disable-data-encryption-nexus-6/
Click to expand...
Click to collapse
No, data encryption is not enabled by default (and still doesn't even work for us).
Cheers,
Michael
Flipping sweet thanks y'all rock i love xda
Cast Screen
Hey stargo. thanks a lot for this! :good:
The 'Cast Screen' under settings pull-down menu is not working. It does not find any of the chromecasts that I have nearby.
Not a big deal, and not a priority at all for me, but just wanted to let you know.
Thanks again!
G'day,
just wanted to confirm the procedure for updating SafeStrap, since some people have CM11 in their stock slot:
in the first step (when you say 'go back to stock'), are you saying simply to boot the stock slot, regardless of ROM (since once SS is unistalled the 'slots' don't exist)?
Or do you mean boot to stock ROM, in stock slot?
I'm guessing it's the former, but I'd like to be sure before taking the plunge =)
thanks for your work! I gave the 2011 version a run over the weekend, it worked pretty well all things considered =)
gabhroo123 said:
Hey stargo. thanks a lot for this! :good:
The 'Cast Screen' under settings pull-down menu is not working. It does not find any of the chromecasts that I have nearby.
Not a big deal, and not a priority at all for me, but just wanted to let you know.
Thanks again!
Click to expand...
Click to collapse
May not ever work, IIRC, chromecasting the screen requires hardware we just don't have. :[
Shobai said:
G'day,
just wanted to confirm the procedure for updating SafeStrap, since some people have CM11 in their stock slot:
in the first step (when you say 'go back to stock'), are you saying simply to boot the stock slot, regardless of ROM (since once SS is unistalled the 'slots' don't exist)?
Or do you mean boot to stock ROM, in stock slot?
I'm guessing it's the former, but I'd like to be sure before taking the plunge =)
thanks for your work! I gave the 2011 version a run over the weekend, it worked pretty well all things considered =)
Click to expand...
Click to collapse
assuming that cm11 is currently installed in your stock slot and you want to update to the new test safestrap by stargo:
uninstall the existing safestrap using the original safestrap, for instance, if the existing safestrap is 3.73, you should install safestrap 3.73 and uninstall the recovery.
DO NOT REBOOT YOUR PHONE IN THE PROCESS
after you have uninstalled the existing recovery, uninstall safestrap(3.73), and then install the new safestrap by stargo, and install the recovery.
your safestrap is now updated, and nothing will be wiped.
YOU MUST NOT REBOOT YOUR PHONE DURING THE PROCESS, you can only reboot after a recovery has been installed.
hope you find this useful
thelolotov said:
May not ever work, IIRC, chromecasting the screen requires hardware we just don't have. :[
Click to expand...
Click to collapse
It need some kernel changes... but it should work...original gnex have the same cpu/gpu and they make it work... @lucize was seeing that but i dont know what happend with that
---------- Post added at 07:38 AM ---------- Previous post was at 07:37 AM ----------
By the way....thanks michael for your great work!...please make a donation link to send you some beer money!
Cheers, sharptv, much obliged =)
gabhroo123 said:
The 'Cast Screen' under settings pull-down menu is not working. It does not find any of the chromecasts that I have nearby.
Not a big deal, and not a priority at all for me, but just wanted to let you know.
Click to expand...
Click to collapse
Yes, our GPU driver does not support WFD. And in contrast to the GNEX, Motorola added much stuff to our version, so it's not easy to sync it back with the upstream kernel. Last time I tried that, I ended up with a non-working display and couldn't figure out why...
Shobai said:
just wanted to confirm the procedure for updating SafeStrap, since some people have CM11 in their stock slot:
in the first step (when you say 'go back to stock'), are you saying simply to boot the stock slot, regardless of ROM (since once SS is unistalled the 'slots' don't exist)?
Click to expand...
Click to collapse
Just boot to whatever you currently have installed in the stock slot. And I have to underline what @sharptv said, never reboot your phone in the process (it might work when you have the stock ROM in the stock slot, but it will surely break in every other case).
Cheers,
Michael
Will cm12 be pre-rooted in future? I can't seem to find anything solid on this, hopefully someone will be able to shed some light on this.
This App Camera work fine: https://play.google.com/store/apps/details?id=com.radcam.camera
---------- Post added at 11:34 AM ---------- Previous post was at 11:31 AM ----------
sharptv said:
Will cm12 be pre-rooted in future? I can't seem to find anything solid on this, hopefully someone will be able to shed some light on this.
Click to expand...
Click to collapse
See this thread: http://www.xda-developers.com/android/supersu-beta-lollipop-root-stock-kernel/
Download and install with recovery
I can confirm that at least on my phone that LTE is working. Great work .
flash these zips in recovery for root i got the from my nexus 7 root toolkit
HOPE IT WORKS FOR YOU :good::cyclops:
TheXG6HD said:
I can confirm that at least on my phone that LTE is working. Great work .
Click to expand...
Click to collapse
Yay! Thanks for confirming
It is a really bad hack, but if it works... http://review.cyanogenmod.org/78845
Cheers,
Michael
stargo said:
Yay! Thanks for confirming
It is a really bad hack, but if it works... http://review.cyanogenmod.org/78845
Cheers,
Michael
Click to expand...
Click to collapse
Data doesn't come up on its own, still needs some prodding (selecting the APN) and will go out randomly. Still not ready for prime time, sadly.... :<
It does come up a lot quicker, however.
thelolotov said:
Data doesn't come up on its own, still needs some prodding (selecting the APN) and will go out randomly. Still not ready for prime time, sadly.... :<
It does come up a lot quicker, however.
Click to expand...
Click to collapse
That's VZW weirdness
But if it comes up, then data is actually passing? Because that is what my patch was intended to fix. Before that the data-indicator would show up, but data would not actually get transmitted...
Can you probably send me the output of "ip route list" and "ip addr list" when LTE data is connected?
Would be interesting to see, what is actually happening now. I can only guess from here...
Regards,
Michael
stargo said:
That's VZW weirdness
But if it comes up, then data is actually passing? Because that is what my patch was intended to fix. Before that the data-indicator would show up, but data would not actually get transmitted...
Can you probably send me the output of "ip route list" and "ip addr list" when LTE data is connected?
Would be interesting to see, what is actually happening now. I can only guess from here...
Regards,
Michael
Click to expand...
Click to collapse
LTE was working on first build, just took 10+ mins to connect then worked good.
Sent from my XT907 using Tapatalk
stargo said:
That's VZW weirdness
But if it comes up, then data is actually passing? Because that is what my patch was intended to fix. Before that the data-indicator would show up, but data would not actually get transmitted...
Can you probably send me the output of "ip route list" and "ip addr list" when LTE data is connected?
Would be interesting to see, what is actually happening now. I can only guess from here...
Regards,
Michael
Click to expand...
Click to collapse
The deal is, the data works at first, then at random intervals it breaks and needs to be manually reset. I'm travelling right now so I can't really risk using CM12 right now, but I'll get you some logs when possible. JJB is having the same issue, I'll ask him to try and get you some details.
Make this pretty later
You just made my day
Sent from my Nexus 6
I just confused myself. Should i be flashing the bootloader, radio, etc from a nexus factory image and then flash omni? I have been using 20150605 build without doing this. Should i do this for the nightlies?
subterfugium said:
Code:
I:operation_start: 'Flashing'
Installing '/sdcard/Download/omni-5.1.1-20150623-shamu-NIGHTLY.zip'...
Checking for MD5 file...
MD5 matched
Verifying zip signature...
I:read key e=3 hash=20
I:1 key(s) loaded from /res/keys
I:comment is 1477 bytes; signature 1459 bytes from end
I:failed to verify against RSA key 0
E:failed to verify whole-file signature
E:Zip signature verification failed: 1
Error flashing zip '/sdcard/Download/omni-5.1.1-20150623-shamu-NIGHTLY.zip'
I guess zip verification fails because of test-keys or what does that zip verification stand for?
Click to expand...
Click to collapse
Honestly, I've never used zip verification for all the years I've been flashing ROMs and have never had any issues.
I'm probably wrong but.. My theory is that packed somewhere inside the zip you are trying to flash lies a key, which is compared next a second key once extracted. If they don't match it throws an error and aborts the operation.
Sent from my Nexus 6 using XDA Free mobile app
I've never used zip verification for this exact reason, and therefore have never looked into it. This sounds like something for the TWRP thread that @Dees_Troy could answer maybe.
Does anyone have a rundown of what this Rom has to offer beyond stock aosp? The Rom OP is a bit bare of info. Thanks
The Rom OP is a bit bare of info. Thanks
530farm said:
Does anyone have a rundown of what this Rom has to offer beyond stock aosp? The Rom OP is a bit bare of info. Thanks
Click to expand...
Click to collapse
Off the top of my head... battery icon customization, volume match orientation, volume wake, screenshot delete, advanced reboot menu, hide usb debugging icon, ambient display customization. Also, Omni is the only AOSP ROM where I don't get force closes when taking multiple HDR+ pictures in a row without pause.
Completely stable device functionality with whatever you see on gerrit :good:
I will make a "features list" tomorrow
I saw that the past few builds uploaded were all 0mb. Just wondering what's going on until the builds resume?
Gandalf said:
Completely stable device functionality with whatever you see on gerrit :good:
I will make a "features list" tomorrow
Click to expand...
Click to collapse
Not sure if feature requests are allowed or not, if not then just ignore this..
But I was wondering if the 5 second home button delay on app launchers (such as Swipepad) is something that may be removed? That'd make navigating the phone much quicker for those of us who do use app launchers.
I saw opendelta mentioned in the main thread but I haven't seen any indication it exists within the ROM. Am I just missing it?
Ngo93 said:
Not sure if feature requests are allowed or not, if not then just ignore this..
But I was wondering if the 5 second home button delay on app launchers (such as Swipepad) is something that may be removed? That'd make navigating the phone much quicker for those of us who do use app launchers.
Click to expand...
Click to collapse
jira.omnirom.org :good:
glockliberty said:
I saw opendelta mentioned in the main thread but I haven't seen any indication it exists within the ROM. Am I just missing it?
Click to expand...
Click to collapse
Updates to opendelta have not been merged yet
I am certainly interested in giving OmniRom a try. A couple of questions...
First, I'm attempting to download the Omni 5.1.1 20150725 Nightly (newest as of this writing) and the download is going exceptionally slow (20-30KB/s) on the official dl.omnirom.org mirror. Is there an issue with the server at current or an up to date mirror?
Next, is there an overall feature list for Omni (on Nexus 6)? Many ROMs place a list of their main features as well as any other ROMs/kernels they incorporate (ie based on CyanogenMod 12.1, with latest CM12.1 commits added on every update etc..)).
Thank you!
RanceJustice said:
I am certainly interested in giving OmniRom a try. A couple of questions...
First, I'm attempting to download the Omni 5.1.1 20150725 Nightly (newest as of this writing) and the download is going exceptionally slow (20-30KB/s) on the official dl.omnirom.org mirror. Is there an issue with the server at current or an up to date mirror?
Next, is there an overall feature list for Omni (on Nexus 6)? Many ROMs place a list of their main features as well as any other ROMs/kernels they incorporate (ie based on CyanogenMod 12.1, with latest CM12.1 commits added on every update etc..)).
Thank you!
Click to expand...
Click to collapse
The server is probably being slow. They just upgraded storage/cleaned it up a few days ago and it has been significantly faster, it might be your connection to the server or something else.
As far as a list of features, there isn't one to my knowledge but you can certainly check on gerrit to see what's been merged recently. Just flash it and see for yourself: highfive:
Does this rom have layers?
Omnirom 5.1.1 nightly sudden reboot+supersu freeze+bluetooth headset bugs
I installed Omnirom 3days ago and have to say; nice stuff. runs fluid, batterie's fine and overall i like user experience. BUT
I'm experiencing some bugs.
first of all sometimes there just are random sudden reboots. On stock rom this happened from time to time when battery was below 30% or something so i thought there has to be a powersaving feature or something in kernel that don't works correct.
Then i flashed TWRP+Omnirom and those sudden reboots started happening randomly; regardless of battery.
I googled and found that could be some setting that adapt display brightness(???) and/or some apps bugging/conflicting. and, from previous experience, i know that this could also be a hardware/battery failure(please not; can't send my phone back right now as i need it daily for work and my N5 has a broken touch )
i tried disabling that display feature and also installed and tested if 'Lux' has any impact on that as it, basically, does the same but no change.
i factory reseted my device multiple times and tried to find out what APP could force this but... right now there's only the bare minimum(contacts+ / messages+ / aquamail / maildroid / todoist /calengoo /business calender pro and google stock apps)and still same problem. sometimes even while calling what's very embarassing when having an important customer on phone ...
I gonna try Zen Kernel next just to see if different kernel with different cpu scheduler COULD make any difference.
Then the second bug is my bluetooth headset(Plantronics M165). Can't get it to pair. Before Omnirom this worked very well as it should. Now, most of time he finds nothing and sometimes he finds a mac address of the headset but not the name. Other bluetooth devices are working fine and the headset's still working perfectly well on my gf's HTC M8. Anyone any ideas?
Last bug i experienced is SuperSU. Always an app needs root i can't get SuperSU intercept my choice. I click on allow or deny but nothing happens and after 10seconds superSu autodenies(or allows; depends on settings )right after factory reset supersu just works fine but suddenly stops working. root's still there as i can perfectly tell supersu what to do in its settings. Only the on demand root question can't be answered. uninstalling/reinstalling supersu didn't change anything. It doesn't matter if i install supersu by playstore or by zip through recovery. also unrooting and rerooting doesn't help. only a factory reset helps; for a while.
I don't want to change my Superuser managment as i paid for the pro version ...
Hope to find some help here as it's one of my fav places for everything smartphone related since back in my tytn days
so much knowledge in here.
keep up the good work
update:
sudden Reboot Problem solved, Same for superSu Problem.
just the Bluetooth problem's still there. flashing back to Stock resolves the issue but... stock and I really start liking omnirom...
anyone any ideas ?
Sent from my Nexus 6 using XDA Free mobile app
nightfly.0684 said:
update:
sudden Reboot Problem solved, Same for superSu Problem.
just the Bluetooth problem's still there. flashing back to Stock resolves the issue but... stock and I really start liking omnirom...
anyone any ideas ?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
M builds will be ready soon enough :good:
great news
Do we get the Update for M through opendelta or is a factory reset + reflash needed?
and if i understand right you assume that the Bluetooth Problem should be gone with M?
would be nice as, right now, I sometimes have to pick up important calls while driving ... and... i don't like that at all....
would try the homemade M build IF i wouldn't need it daily for work. about time to repair my n5 i guess
Sent from my Nexus 6 using XDA Free mobile app
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!