Related
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.
Hello ,
I got my P7 for about 4 Months now,
and I wanted to have the EMUI 3.0 and Lolipop
but I think the Original System is 4.4.2 and Emui 2
I want to ask What can I do to Root or make a ROM (Sorry I really dont know he defrance total newbie ) , but I dont want to lose the support of Google or the Google Market , what should I do , can anyone help me in that ???
give me details and tell me what to do
thanks
look at this: http://forum.xda-developers.com/asc...7en-rom-v3-0-emui-3-0-4-4-2-18-11-14-t2945104
darkzero2022 said:
Hello ,
I got my P7 for about 4 Months now,
and I wanted to have the EMUI 3.0 and Lolipop
but I think the Original System is 4.4.2 and Emui 2
I want to ask What can I do to Root or make a ROM (Sorry I really dont know he defrance total newbie ) , but I dont want to lose the support of Google or the Google Market , what should I do , can anyone help me in that ???
give me details and tell me what to do
thanks
Click to expand...
Click to collapse
If you are newbie than do nothing ! Wait for official upgrade ! Because you will cry !
Sent from my HUAWEI P7-L10
Ziolek67 said:
If you are newbie than do nothing ! Wait for official upgrade ! Because you will cry !
Sent from my HUAWEI P7-L10
Click to expand...
Click to collapse
Really ???? Why ?? Huawei is too slow in making the Updates , all now is Andoird 5 and P7 is stuck in 4.4.2
It's proberly better staying on 4.4.2 than on lolipop. Many bugs on lolipop.
Sent from my HUAWEI P7-L10 using XDA Free mobile app
darkzero2022 said:
Really ???? Why ?? Huawei is too slow in making the Updates , all now is Andoird 5 and P7 is stuck in 4.4.2
Click to expand...
Click to collapse
Ok than lest go to update.... I will waiting for yours requests for help
darkzero2022 said:
Really ???? Why ?? Huawei is too slow in making the Updates , all now is Andoird 5 and P7 is stuck in 4.4.2
Click to expand...
Click to collapse
Wow do you realize android 5 has been out officially for a week or two and pretty much every phone apart from nexus which uses the software directly from Google themselves who make android, still don't run it yet and expect to be running it in 2015.
Not even big teams that use the aosp code directly such as cyanogen or paranoid have got a stable fully functional rom out yet.
It takes time for the 3rd party developers to customize and test android for there devices once the official version gets released as they all use the final source code which only has been out 3-4 weeks.
Also no company apart from Google is much better, Samsung are still rolling out 4.4 to some of there devices with some like the s2 still on 4.2 and end of life presumably others will jump straight to lollipop from 4.3 etc.
Also on rooting what do you wish to achieve by doing so?
Rooting can be very dangerous if you don't know what your doing with devices like ours.
Take a look for example at all the posts in this forum asking to downgrade their l10's from emui 3 to 2 which they upgraded to custom versions etc without thinking and the issues they now have with boot loops and stuff.
If you want to run xposed you can find many people with similar things recently in this forum that can't get it to work.
Also rooting etc you lose the ability for any future updates via OTA and recovery and would need to manually update your device potentially bricking it every single time which bricking means you can no longer use your device and have to buy a new one.
Also are you capible on the PC with using it, command prompt Linux shell etc and doing things like installing Windows and other things.
If not then rooting is not for you.
Also do you know how to code in Linux C etc and know the workings of the Linux os, if not then there is no way you are going to make a custom rom. All you might be able to achieve is just repackaging someone else's ROM with minor edits and even then the tools to do that mainly use Linux to run as it's native windows doesn't have all the stuff Linux has natively in this regard.
Ziolek67 said:
If you are newbie than do nothing ! Wait for official upgrade ! Because you will cry !
Sent from my HUAWEI P7-L10
Click to expand...
Click to collapse
drguild said:
Wow do you realize android 5 has been out officially for a week or two and pretty much every phone apart from nexus which uses the software directly from Google themselves who make android, still don't run it yet and expect to be running it in 2015.
Not even big teams that use the aosp code directly such as cyanogen or paranoid have got a stable fully functional rom out yet.
It takes time for the 3rd party developers to customize and test android for there devices once the official version gets released as they all use the final source code which only has been out 3-4 weeks.
Also no company apart from Google is much better, Samsung are still rolling out 4.4 to some of there devices with some like the s2 still on 4.2 and end of life presumably others will jump straight to lollipop from 4.3 etc.
Also on rooting what do you wish to achieve by doing so?
Rooting can be very dangerous if you don't know what your doing with devices like ours.
Take a look for example at all the posts in this forum asking to downgrade their l10's from emui 3 to 2 which they upgraded to custom versions etc without thinking and the issues they now have with boot loops and stuff.
If you want to run xposed you can find many people with similar things recently in this forum that can't get it to work.
Also rooting etc you lose the ability for any future updates via OTA and recovery and would need to manually update your device potentially bricking it every single time which bricking means you can no longer use your device and have to buy a new one.
Also are you capible on the PC with using it, command prompt Linux shell etc and doing things like installing Windows and other things.
If not then rooting is not for you.
Also do you know how to code in Linux C etc and know the workings of the Linux os, if not then there is no way you are going to make a custom rom. All you might be able to achieve is just repackaging someone else's ROM with minor edits and even then the tools to do that mainly use Linux to run as it's native windows doesn't have all the stuff Linux has natively in this regard.
Click to expand...
Click to collapse
Thanks For your Valuable words,
I really enjoyed them and get my mind open
well I do have Good Experience in linux and Command line , C Programming actually didnt go deep with it really ,
But i think I will stick to your opinion and wait ,and while I do so I will learn more about the whole subject ,and maybe increase my knowledge in this Field . (Android Programming - the C Programming - how things work in Android , ROMS , ETC)
but would you mind telling me from where to start ???
darkzero2022 said:
Thanks For your Valuable words,
I really enjoyed them and get my mind open
well I do have Good Experience in linux and Command line , C Programming actually didnt go deep with it really ,
But i think I will stick to your opinion and wait ,and while I do so I will learn more about the whole subject ,and maybe increase my knowledge in this Field . (Android Programming - the C Programming - how things work in Android , ROMS , ETC)
but would you mind telling me from where to start ???
Click to expand...
Click to collapse
Apologies if I came across about abit hard this forum has had allot of impatient people jumping in recently trying to run Emui 3 on l10's then asking to downgrade as you may have noticed the other teams like paranoid are already dealing with lots of people saying there to slow for not having lollipop out within a hour of aosp.
I had the same issue running a custom Minecraft server that people got really angry then refused to play and bad mouth the server if we didn't update that day when update time for us was about a week given the number of customizations we had 41 plugin's in the end, sometimes longer if there were more changes the mod and custom server devs had to deal with.
Emui 3 and lollipop has more bugs more as it's new from what I found I may start a proper consolidated emui talk thread later for those running it opposed to all the l10 when are we getting it out help me downgrade threads.
The place I think you should start is to download the source code for your version from the emui webpage and start analyzing it out of interest.
There's another Dev on here doing the same thing so you might want to contact him for info.
Also there are tools on Linux that easily let you unpack stock image files and the ext container and repack them.
That way you can see the full file structure and how a rom is packaged.
It's good just to see what's inside roms and how the first roms are usually made by a repackage before source.
I will stress the same as above that while these are starting points you would need to know what you are doing and something more hackable like a cheap nexus or or Chinese tab (about $50 USD) with easy upgradable firmware something would be better to start on.
Also grab down the android tools with eclypse for Linux, the sdk virtual device and have a play around making a app and stuff also you can edit the virtual rom safely etc.
The Linux version of the tools is far superior as you can natively mount the virtual ext cards for host file transfer and do other things which you can't under windows.
By ext above I mean the virtual partition files which are either ext 3 or 4 last time I looked.
I'm not a coder myself and I only did basic stuff in the past as I had a Chinese android 2.2 tablet the MID ones as my first device, I used a custom rom on which was just a repack with file system changes with bloat removed etc.
I looked into this out of interest and curiosity, each rom update I repacked it with the apps I used so I didn't need to reinstall them, there was probably a better (proper) way than just unpacking the ext file system from the img adding my apps in to the deploy folder and repacking.
Also I unpacked a APK weather app etc to make changes and use a custom background and others like themes to grab icons and assets this is a good start with looking at app packages and how that all works as well as making your own app in various tools eclipse for one which is the official tool but there's hundreds of android programming softwares online even to do simple stuff as make a stand alone html5 app from a webpage.
The tools on Windows I found were lacking and harder to find for the rom stuff, with Linux it was built into the system a lot of things.
What Linux is the best for doing Android stuff I don't know so that will need to be researched.
As mentioned devices can be dangerous for custom stuff especially newer ones with bootloader security, the older Chinese style ones and some others you could reflash easily from sdcard with a update.img file as they didn't contain that lock out security on boot and debugging.
I nearly bricked a few devices in the past, once having to rely on the bootloader and Android Commander a powerful tool and device terminal to mount the partition rw while in the bootloader to rename a file backI renamed as a test that caused the system to stop booting.
You can still get some tabs that do that about 50 USD on eBay etc I think.
darkzero2022 said:
Hello ,
I got my P7 for about 4 Months now,
and I wanted to have the EMUI 3.0 and Lolipop
but I think the Original System is 4.4.2 and Emui 2
I want to ask What can I do to Root or make a ROM...
Click to expand...
Click to collapse
I'd strongly advise that you wait. My experience. You can root v4.4.2 VERY easily using vroot. Wait for lollipop, honestly. Is a nightmare recovering your position if you try to move now.
Sent from my HUAWEI P7-L10 using XDA Premium HD app
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
The Unlegacy-Android ProjectIntroduction
Unlegacy-Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy-Android was born.
Installation
It's important that /system needs to be unmounted before installing the ROM - some recoveries tend to leave it mounted after performing operations on it.
If you're planning to install GApps, be sure to read the second post!
Aside from these, installation and upgrading is no different than on other ROMs. As usual, 'espresso' goes for all non-3g versions, 'espresso3g' goes for all 3g versions.
Problems
- Occasional sound stuttering in some games
- No hwrotation (meaning the boot animation is landscape on p31xx). I don't consider this as a problem, as autorotation will take effect after bootup anyways... and most 7" tablets, like the Nexus 7 work this way as well.
- The 7.1 builds are experimental! Means: modem not working perfectly yet.
If you notice anything else, be sure to report it in this thread. While I'm kind of busy, I usually read the thread and acknowledge the bug reports, even if I don't reply directly to them.
Downloads
See: http://builds.unlegacy-android.org
Always use the latest TWRP, to flash Android 7.x, you must use TWRP 3.0.3-0 or newer.
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices. The aim of this project is to create a fast and stable ROM - although, one could use Xposed to add extra features.
As usual, feedback is appreciated
Want to support development? You can consider donating, I spent countless of hours with this
XDA:DevDB Information
Unlegacy Android Project, ROM for the Samsung Galaxy Tab 2
Contributors
Ziyan, Android-Andi
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 7.x Nougat
ROM Firmware Required: The latest bootloader for your device.
Version Information
Status: Beta
Current Stable Version: 4.4, 6.0
Created 2016-07-03
Last Updated 2017-10-22
GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
siealex said:
One more note. DO NOT set up your Google account until you grant all permissions, otherwise you will be stuck on the initial setup.
Click to expand...
Click to collapse
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.
Ziyan said:
GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.
Click to expand...
Click to collapse
Wow, i saw this rom on galaxy nexus section. Does this rom included CMA?
Bastiary said:
Wow, i saw this rom on galaxy nexus section. Does this rom included CMA?
Click to expand...
Click to collapse
No, at least not yet. I think that the big thing for this will be 3.4 in the near future - I made some very good progress with it, aside from camera not working yet, there are only minor problems remaining
Thank you for everything , dear friend ! And for the support of the old device , and what you are doing and Andi for us ordinary users .
I understand correctly , that support will only 6.0.1 Android N and we do not see , because the device and its old base ?
Az-09 said:
I understand correctly , that support will only 6.0.1 Android N and we do not see , because the device and its old base ?
Click to expand...
Click to collapse
Before every new Android release, we devs get all sorts of questions like this. I'd like to say it once and for all: there's no such thing as 'we do not see' the next versions and whatnot. People are being negative for some reason, but we always try and succeed in the end... I'm sure that if you start reading past posts, you'll find a lot of people saying that we1l never see Lollipop or Marshmallow due to the device being too old, lol.
Download link?
It just says look at the top of the page? Is it soon?
Thanks for the new ROM....keep it up!
All the best...
radz_ said:
Download link?
It just says look at the top of the page? Is it soon?
Thanks for the new ROM....keep it up!
All the best...
Click to expand...
Click to collapse
check download tab section.
Hello! The ROM with the codename "espresso" is for the version: Galaxy Tab 2 7.0 Wi-Fi P3110 / P3113 and Galaxy Tab 2 10.1 Wi-Fi P5110 / P5113. Namely we talk about all versions with codename "espressowifi"?!
pickmod said:
Hello! The ROM with the codename "espresso" is for the version: Galaxy Tab 2 7.0 Wi-Fi P3110 / P3113 and Galaxy Tab 2 10.1 Wi-Fi P5110 / P5113. Namely we talk about all versions with codename "espressowifi"?!
Click to expand...
Click to collapse
Yes, that's correct.
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Screeshots
Astro Noid said:
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Click to expand...
Click to collapse
no need for this, it's aosp there isn't any custom features and everybody know how aosp looks
Astro Noid said:
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Click to expand...
Click to collapse
Oh don't worry, I'm working extremely hard in the background almost since like a year... I know a lot about these devices (bought a P5100 specifically for testing 3G on the builds and kernels)
Feature list: well, this is AOSP, and I'd like to keep it this way. Imagine this like the stock ROM on the Nexus devices (with GApps flashed, of course).
Changelog: don't expect anything other than AOSP updates and hardware related fixes and updates - of course, I'm going to write a post each time I release an update, just like I do in the Galaxy Nexus thread however, it's unlikely that I'll add a changelog to the OP (I just don't see the usefulness in it).
Screenshots: will do, but then again, don't expect anything special. Stable and fast pure Android, that is AOSP. As a side note, it's Xposed compatible
I hope everybody likes the new shiny unified forum section! There's still a bit of a work left to do, but I think it looks great and eases maintaining the threads; blame me if you think otherwise :silly:
Thak you for your effort to keep tab 2 alive . Amazing work. Are RRO Layers compatible with this rom?
Ziyan said:
I hope everybody likes the new shiny unified forum section! There's still a bit of a work left to do, but I think it looks great and eases maintaining the threads; blame me if you think otherwise :silly:
Click to expand...
Click to collapse
Hi Ziyan,
I'm glad you mentioned this, as I thought that I was going insane this morning (or just slightly more insane than usual).
Just browsing the new "Unified" forum (to verify my subscriptions) and noticed that the "Dhollmen" threads could be clarified (just like the "Linaro" threads), for example ...
This thread: http://forum.xda-developers.com/showthread.php?t=2176563 could be titled: [KERNEL][P51xx][AOSP] Dhollmen Espresso
This thread: http://forum.xda-developers.com/showthread.php?t=2183830 could be titled: [KERNEL][P31xx][AOSP] Dhollmen Espresso
Just to avoid confusion (I freely admit that I am easily confused).
Thanks.
@mentat no need to have 2 threads, one is enough now in unified section
I also don't know what your question hast to do with this rom [emoji14]
~ All my work, news etc. on http://andi34.github.io ~
Android-Andi said:
@mentat no need to have 2 threads, one is enough now in unified section
I also don't know what your question hast to do with this rom [emoji14]
~ All my work, news etc. on http://andi34.github.io ~
Click to expand...
Click to collapse
Hi Andi,
I only suggested renaming the existing "pair" of threads (they both exist in the Unified Forum) ... Just like the "pair" of Linaro threads (that also both exist in the Unified forum).
The download links in (all four) of the threads (mentioned above) link to unique builds on AFH (for both P31xx and P51xx devices) in this forum: http://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified
@Ziyan, while we're on the subject, the CandySix for P51XX thread: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candysix-v1-1-t3331598 should also be moved to the new Unified forum as well (the CandySix for P31xx thread has already been moved).
Sorry for all the edits (I put the blame on OCD).
Thanks.
mentat said:
@Ziyan, while we're on the subject, the CandySix for P51XX thread: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candysix-v1-1-t3331598 should also be moved to the new Unified forum as well (the CandySix for P31xx thread has already been moved).
Click to expand...
Click to collapse
Done; I guess this is it then. Like the XDA forum admin said, the best way to handle moving both threads is to move them both to this unified section, and close one of them (preferably the one with the less posts). While we could merge them into one thread, the posts would get all mixed through the other threads posts (because of the date order) and we would lose any sense of a flow in the conversation...
Minimum Custom Recovery version?
@Ziyan @Android-Andi Thanks for bringing new life to this old tabs
Is there any minimum requirement for recovery for flashing this ROM? I'm running pretty old CWM v.6.0.5.1. Is it sufficient?
Opening up this thread in hopes some interest can be made.
Since the beta version of Android 13 dropped, I decided to boot into GSI roms to achieve root. To my surprise, not only did the GSI rom boot, but I was able to go through the google setup like a champ. Every now and again, I load different GSI roms to test and I am currently using Google QPR2. As it stands the following works:
What Works
Opening and closing the device actually works and renders content in open and closed state
Cellular/wifi radio works
Touchscreen works but there's issues (see below)
Camera works (albeit not as well as the pixel camera ports)
Notifications fully work
Android Auto works
SMS works
There is a very big problem with using the GSI - the device detects inputs from both screens whether opened or closed. So here's a list of what doesn't work:
Not working
Touch input (as previously described)
Phone features (phone vibrates but dialer never displays)
Battery isn't optimized (given)
If you want to test it and provide some feedback, I am using this GSI rom:
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
As always to install GSI roms, bootloader must be unlocked. To install, use DSU Loader. It's a rather painless process
domineus said:
Opening up this thread in hopes some interest can be made.
Since the beta version of Android 13 dropped, I decided to boot into GSI roms to achieve root. To my surprise, not only did the GSI rom boot, but I was able to go through the google setup like a champ. Every now and again, I load different GSI roms to test and I am currently using Google QPR2. As it stands the following works:
What Works
Opening and closing the device actually works and renders content in open and closed state
Cellular/wifi radio works
Touchscreen works but there's issues (see below)
Camera works (albeit not as well as the pixel camera ports)
Notifications fully work
Android Auto works
SMS works
There is a very big problem with using the GSI - the device detects inputs from both screens whether opened or closed. So here's a list of what doesn't work:
Not working
Touch input (as previously described)
Phone features (phone vibrates but dialer never displays)
Battery isn't optimized (given)
If you want to test it and provide some feedback, I am using this GSI rom:
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
As always to install GSI roms, bootloader must be unlocked. To install, use DSU Loader. It's a rather painless process
Click to expand...
Click to collapse
hello and thank you very much for this feedback. after having watched this forum for a very long time, it is time for me to buy this magnificent smartphone because I have always used gsi pixel experience roms. but I would still like to have your opinion on the sound quality of this beast because on no comment and test nobody talks about it
Bwhite... said:
hello and thank you very much for this feedback. after having watched this forum for a very long time, it is time for me to buy this magnificent smartphone because I have always used gsi pixel experience roms. but I would still like to have your opinion on the sound quality of this beast because on no comment and test nobody talks about it
Click to expand...
Click to collapse
GSI depends solely on a bootloader unlock. Unless you get an older device that hasn't been updated, I wouldn't purchase the device with the assumption that root is easy...
domineus said:
GSI depends solely on a bootloader unlock. Unless you get an older device that hasn't been updated, I wouldn't purchase the device with the assumption that root is easy...
Click to expand...
Click to collapse
Yes indeed I understand that. but I read on the forum that unlocking the bootloader was back on a september update. but the question I ask myself more is the sound quality of the dual speakers. anyway thank you very much for your answer.
Bwhite... said:
Yes indeed I understand that. but I read on the forum that unlocking the bootloader was back on a september update. but the question I ask myself more is the sound quality of the dual speakers. anyway thank you very much for your answer.
Click to expand...
Click to collapse
I'm not sure. THere are some who tried who weren't able to bootloader unlock for the September update or afterward.
Sound quality is subjective but I had zero complaints from the speakers
domineus said:
I'm not sure. THere are some who tried who weren't able to bootloader unlock for the September update or afterward.
Sound quality is subjective but I had zero complaints from the speakers
Click to expand...
Click to collapse
ok thank you for all this useful information.
Sorry for the stupid question, but what is GSI? is this a custom rom?
NeoGoku123 said:
Sorry for the stupid question, but what is GSI? is this a custom rom?
Click to expand...
Click to collapse
Generic System Images (GSIs) | Platform | Android Developers
developer.android.com
domineus said:
Opening up this thread in hopes some interest can be made.
Since the beta version of Android 13 dropped, I decided to boot into GSI roms to achieve root. To my surprise, not only did the GSI rom boot, but I was able to go through the google setup like a champ. Every now and again, I load different GSI roms to test and I am currently using Google QPR2. As it stands the following works:
What Works
Opening and closing the device actually works and renders content in open and closed state
Cellular/wifi radio works
Touchscreen works but there's issues (see below)
Camera works (albeit not as well as the pixel camera ports)
Notifications fully work
Android Auto works
SMS works
There is a very big problem with using the GSI - the device detects inputs from both screens whether opened or closed. So here's a list of what doesn't work:
Not working
Touch input (as previously described)
Phone features (phone vibrates but dialer never displays)
Battery isn't optimized (given)
If you want to test it and provide some feedback, I am using this GSI rom:
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
As always to install GSI roms, bootloader must be unlocked. To install, use DSU Loader. It's a rather painless process
Click to expand...
Click to collapse
Considering this for a x fold plus.
Were you able to fix the issues and if not, to what to extent are the effects. For example, with the battery not optimized how does it last and with the dialer not displaying are you able to answer the call? Touch input I assume is mostly an issue when using the larger screen (i.e. you accidentally input from the front screen).
NikG25 said:
Considering this for a x fold plus.
Were you able to fix the issues and if not, to what to extent are the effects. For example, with the battery not optimized how does it last and with the dialer not displaying are you able to answer the call? Touch input I assume is mostly an issue when using the larger screen (i.e. you accidentally input from the front screen).
Click to expand...
Click to collapse
I wasn't able to fix them but I didn't try. I don't have the dev machine to try and fix the issues and rebuild a LoS GSI to get it working. Which is a shame :/
But given that I have had a really good time with it otherwise because I like the potential of it