Updated 5/3/13
The Nook Color is now an official CM 10.1 device! This is a huge milestone in the development of a device of this age!
You can now find builds at http://get.cm/?device=encore
I will keep the remainder of the post below for informational purposes but users should click the link above to get the latest builds.
------------------------------------------------------------------------------
Updated 3/17/13
*Beta 2 released, sync'd with latest CM sources
*Further kernel updates, thanks again to steven676 for all his work!
*Bootanimation still funky...
Updated 2/27/13
*Beta 1 released, sync'd with latest CM sources and updated to 4.2.2.
*Latest kernel changes are included. Thanks steven676.
KNOWN ISSUE:
Android 4.2.2 has some new adb security features which require you to authorize the computer that you're connecting to on your device. Please make sure you have the latest adb version (update it via sdk manager). The initial adb auth doesn't always work when connected with MTP - the workaround is to switch to UMS mode (settings-storage-menu) then auth the device (and remember the keys). After that you can switch back to MTP and it'll work from then on for that computer.
*** If you have a non-development related question/comment about 3rd party mods/add-ons then DO NOT post in this thread, it for bug reports and comments on the build provided without modifications. Please keep all user discussion in the thread in general: http://forum.xda-developers.com/showthread.php?t=2170185 ***
Original OP
Following closely on the heels of our official status as a CM10 device, the NookieDevs present CyanogenMod 10.1 Alpha for the Nook Color!
As stated, this is an Alpha release for people to get a sense of the new features in Android 4.2.1. Performance doesn't seem quite up to par as CM10 as yet, and any lingering bugs in CM10 will likely be present in this release. While almost everything is working, we do expect users to uncover some additional bugs. Please take precautions to backup your device/data.
You should be able to flash this over CM10; however, if you run into a bug, please do a full wipe and reinstall before reporting. See Post 2 for wipe procedures and gapps information.
Known issues:
1) Initial boot animation doesn't display correctly
2) Some performance issues (remember this is 2010 hardware we're working with...)
Please read over the CM10 thread as the bulk of fattire's introduction still holds true for this release.
WARNING/DISCLAIMER
Understand that there are likely to be bugs, both known and unknown, and that all appropriate experimental-software disclaimers apply, including the fact that by using or attempting to use this software, you assume all risk for fooling with your hardware. We will not be held responsible for any potential loss of data, destruction of hardware, removal or disappearance of limbs, life, or coins in the couch. We do not claim this software is fit for any purpose, etc. Beware of Dragons.
This said, we do feel that the our work is finally “good enough” for interested people with a tolerance for risk to get their hands on.
Of course credits and thanks to all those who have contributed: fattire, keyodi, sluo, krylon360, dalingrin, verygreen, iomonster, nemith, cicadaman, deeper-blue, thedude, mad-murdock, j4mm3r, unforgiven512, scepterr, rebellos, ryands, kmobs, tonsofquestions, hashcode, arcee, hacdan, drmarble, mateor and many more.
Source:
https://github.com/NookieDevs/android_device_bn_encore/tree/cm-10.1
Download:
Beta2: cm-10.1-encore-b2.zip MD5: 455cf35156feabc6ac630dce51d29454
Previous builds:
Beta1: cm-10.1-encore-b1-stillsomebugs.zip MD5: 1afea80885f349b810b5130a30d6593e
Alpha1: cm-10.1-a1-encore-fullofbugs.zip MD5: aa47473b5c3f743f3033c7cd7ac29f19
Gapps for 4.2.2: http://techerrata.com/file/gapps/gapps-jb-20130301-signed.zip
Mirror: http://goo.im/gapps
If you run into a gapps related issue:
1) Wipe system manually in recovery
2) Flash rom then gapps
If you still run into issues:
1) Wipe system manually
2) Wipe data (factory reset)
3) Flash rom and gapps
Frequently asked questions
Where did the developer settings go?
Where did the performance menu (overclocking settings, etc.) go?
Google and CyanogenMod decided to hide those settings by default in Android 4.2. To enable them, go to Settings->About tablet and tap on the build number seven times.
How do I get the Honeycomb/ICS tablet UI?
You want to use the Auto-Patcher to modify your ROM for the tablet UI. (Don't forget to thank Caldair for maintaining the Tablet UI mod, and mateorod and the rest of the Auto-Patcher developers for building that tool.)
FYI I can report it does install in an SD card. Had to start from scratch. Too many issues flashing it on top of Schizod. But I knew that up front.
Thanks for your efforts!
Am I actually reading this?!? You guys are amazing!!!!!
To build from source, it's like the PA 4.1.2, but instead we use
Code:
repo init -u git://github.com/NookieDevs/android_device_bn_encore.git -b jellybean
Right?
Do I even need the -b jellybean?
And to build the ROM, it's still
Code:
./rom-build.sh encore
THANK YOU!
thejrcrafter2 said:
Am I actually reading this?!? You guys are amazing!!!!!
To build from source, it's like the PA 4.1.2, but instead we use
Code:
repo init -u git://github.com/NookieDevs/android_device_bn_encore.git -b jellybean
Right?
Do I even need the -b jellybean?
And to build the ROM, it's still
Code:
./rom-build.sh encore
THANK YOU!
Click to expand...
Click to collapse
Not quite. If you previously set up your repo for PA then you should re-init for building CM:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
Then perform a sync and modify your your local_manifest.xml to include:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote fetch="git://github.com/" name="gh" />
<project name="NookieDevs/android_device_bn_encore" path="device/bn/encore" remote="gh" revision="cm-10.1" />
<project name="NookieDevs/ti-omap-encore-kernel3" path="kernel/bn/encore" remote="gh" revision="encore-omap3-3" />
<project name="eyeballer/proprietary_vendor_bn" path="vendor/bn" remote="gh" revision="jellybean" />
</manifest>
For now the device repo is still only on NookieDevs - the kernel is up to date on both CM's repo and NookieDevs so you can actually use either for building.
eyeballer said:
Not quite. If you previously set up your repo for PA then you should re-init for building CM:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
Then perform a sync and modify your your local_manifest.xml to include:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote fetch="git://github.com/" name="gh" />
<project name="NookieDevs/android_device_bn_encore" path="device/bn/encore" remote="gh" revision="cm-10.1" />
<project name="NookieDevs/ti-omap-encore-kernel3" path="kernel/bn/encore" remote="gh" revision="encore-omap3-3" />
<project name="eyeballer/proprietary_vendor_bn" path="vendor/bn" remote="gh" revision="jellybean" />
</manifest>
For now the device repo is still only on NookieDevs - the kernel is up to date on both CM's repo and NookieDevs so you can actually use either for building.
Click to expand...
Click to collapse
Yeah, but if I didn't init for PA, would I have to edit the manifest? And I would use the -b cm-10.1, right? Sorry, I'm still a noob.
thejrcrafter2 said:
Yeah, but if I didn't init for PA, would I have to edit the manifest? And I would use the -b cm-10.1, right? Sorry, I'm still a noob.
Click to expand...
Click to collapse
Actually you'd still need to init if you only built CM10 before so that all your repos update to 10.1. Then just update the local manifest with our 10.1 branch for the device.
Putting up a quick review on Youtube:
http://youtu.be/NHl8sib5PUs
Will take about 20 or so minutes to actually load tho
EDIT: OK, it's uploaded.
---------- Post added at 07:21 PM ---------- Previous post was at 06:42 PM ----------
I found a bug:
The multitasking button stopped working (the double rectangle thing), but the holding the 'n' button got me to M.T.ing just fine. Can't get a logcat right now, I rotated the Nook while getting the USB cord, and then it worked fine again after rotating it back. Will try to get a logcat next time it happens.
It works
Thanks Devs, cool to be on the bleeding edge.
Dirty flashed this over the CM10 2/3 weekly, wiped cache and fixed permissions. Boot animation is distorted, squished to top half of screen and right 40% cut off, almost like it was trying to display 600x1024 onto 1024x600 or something, this also happened on subsequent re-boots.
There is no Performance tab in settings - was this intentional?
Most everything seems to work, although seat of pants impression is that it is ~20% slower than the latest CM10 weeklies, not really laggy, just a bit slower, like if CPU clock was running at 800 instead of the 1100 that I'm used to, but Quadrant reports that CPU is at 300 min, 1100 max, maybe carried over from CM10 settings?
Only real buggy thing, other than the boot animation was the new Settings > System > Quick Settings panel tab, the first time I selected it, screen went totally black, then nav and notification bar came back, and then system re-booted, since then it seems to work OK.
I notice that Gallery is not syncing with Picassa, can I flash gapps-jb-picassa-20121011-signed.zip over this? I do not see any newer picassa gapps packages on goo.im?
Overall, pretty impressive, thanks again and great job, I'm willing to stick with it for a while.
webyrd said:
Thanks Devs, cool to be on the bleeding edge.
There is no Performance tab in settings - was this intentional?
Click to expand...
Click to collapse
Go in to settings about tablet and press the build number 10 times. This is a 4.2 feature.
Frank
---------- Post added at 08:04 PM ---------- Previous post was at 08:01 PM ----------
I flashed this over top of 1/27/2013 with the test kernel, updated gapps, cleared cache and dalvik cache and booted. I have not noticed any problems if anything it feels faster than CM10 but maybe because I just booted. I really like the CM lock screen addition of weather.
Frank
webyrd said:
I notice that Gallery is not syncing with Picassa, can I flash gapps-jb-picassa-20121011-signed.zip over this? I do not see any newer picassa gapps packages on goo.im?
Overall, pretty impressive, thanks again and great job, I'm willing to stick with it for a while.
Click to expand...
Click to collapse
Haven't tested it, but it should work just fine, please report back. If you hit a problem, just follow the gapps issue steps in post 2.
webyrd said:
Thanks Devs, cool to be on the bleeding edge.
Dirty flashed this over the CM10 2/3 weekly, wiped cache and fixed permissions. Boot animation is distorted, squished to top half of screen and right 40% cut off, almost like it was trying to display 600x1024 onto 1024x600 or something, this also happened on subsequent re-boots.
There is no Performance tab in settings - was this intentional?
Most everything seems to work, although seat of pants impression is that it is ~20% slower than the latest CM10 weeklies, not really laggy, just a bit slower, like if CPU clock was running at 800 instead of the 1100 that I'm used to, but Quadrant reports that CPU is at 300 min, 1100 max, maybe carried over from CM10 settings?
Only real buggy thing, other than the boot animation was the new Settings > System > Quick Settings panel tab, the first time I selected it, screen went totally black, then nav and notification bar came back, and then system re-booted, since then it seems to work OK.
I notice that Gallery is not syncing with Picassa, can I flash gapps-jb-picassa-20121011-signed.zip over this? I do not see any newer picassa gapps packages on goo.im?
Overall, pretty impressive, thanks again and great job, I'm willing to stick with it for a while.
Click to expand...
Click to collapse
To get the performance and developer settings, go to Build Number in about tablet and tap it. A lot. As for the boot animation, that was reported in the OP, they're prbly fixing that. I haven't had the Quick Settings problem, can you get a logcat or dmesg? And the Picassa, is that for 4.1.2 only, or will it work with any version? I reccomend that you just flash and see what happens.
Installed fine
Installed rom and gapps, wiped cache, and fixed permissions. Everything came up fine. Noticed a little sluggishness, but no complaints for Alpha 1. Great work guys. A sincere congrats and thanks to all who worked so hard. This is so cutting edge my fingers are bleeding, well almost.
:good::highfive::silly::laugh:
Other than the known bootloader logo bug no issues to report. A little bit more lag than cm10, but not enough for me to switch back to it. Will give it a day to see how it goes. Looking good guys, great job!
Well devs, consider this piece of hardware owned, by you. I am really amazed at where you've taken this ebook reader.
Overnight, the battery drain was 1-2%, highly impressive. It continues to perform admirably.
I can confirm the lack of picasa sync in Gallery, but I have not wiped system and reinstalled both the rom and gapps.
Frank
frankusb said:
Well devs, consider this piece of hardware owned, by you. I am really amazed at where you've taken this ebook reader.
Overnight, the battery drain was 1-2%, highly impressive. It continues to perform admirably.
I can confirm the lack of picasa sync in Gallery, but I have not wiped system and reinstalled both the rom and gapps.
Frank
Click to expand...
Click to collapse
Did you try flashing the picasa sync google gallery from cm10? Link is in post 2 of the CM10 thread.
nightlies
Just for information, what is required of a ROM to get it included in the Cyanogenmod nightly builds? Is it a stability issue or something else?
eyeballer said:
Did you try flashing the picasa sync google gallery from cm10? Link is in post 2 of the CM10 thread.
Click to expand...
Click to collapse
That fixed it. I had to go in settings under my Settings/Google/my account and turn on Google Photo syncing and after a bit, the photos showed up. It took some time, a few minutes, but then the Gallery had the pictures.
Edit: Hmm, still syncing after 6 minutes though.
Edit 2: Sync finished after 9 minutes. Call this experiment successful.
Frank
dirty flash
Just flashed this over CM10 and no issues at all so far. I'll tinker around with everything later on and see if anything seems wonky but so far so good. Running Noop scheduler and OC'd at 1100.
Related
CM10 "Jelly Bean" for
Nook Tablet
Alpha 0.08.3 Release
“Seriously, Don’t Try To Sell This... You’ll Really, REALLY Regret It” Edition
Hey all,
So once again it’s time. Introducing the first alpha development preview of CyanogenMod 10 (based on Jelly bean) for the BN Nook Tablet, aka codename: “acclaim”. This preview for the internal “emmc” storage is intended only for developers as it is in a very early development stage and not all features of the device are fully working.
Let’s emphasize that-- THIS IS AN ALPHA, RELEASED FOR YOU TO PLAY WITH AND GET A SENSE OF WHAT’S TO COME. AND SOME THINGS DON’T WORK. REALLY. IF YOU ARE EXPECTING ANYTHING CLOSE TO PERFECTION, WALK AWAY FROM YOUR COMPUTER, LOWER YOUR EXPECTATIONS FOR AN HOUR OR SO, THEN COME BACK. MORE EXCITING DISCLAIMERS/WARNINGS IN ALL CAPITAL LETTERS CAN BE FOUND BELOW. READ THEM.
Also...
If you have troubles and post to this form, please indicate if you use 16GB (1GB RAM) or 8GB (512 MB RAM) model.
WHAT WORKS
3.0 kernel (mostly works, thx to Kuzma)
display
touchscreen
new “CyanoBoot” menu bootloader (thanks to rebellos for most recent enhancements)
accelerometer
data statistics
additional kernel tweaks/improvements/history
bootcount/battery updates & other acclaim peculiarities addressed
sound
video acceleration
hwcomposition
microphone (does it still crash kernel?)
WHAT DOESN’T WORK
- crashes (random reboots - less frequent though)
- battery drain (got also somewhat better)
SUPPORT
You get none. Zero. Zip. We obligate ourselves to providing nothing further. You are on your own and will have to help each other via this thread. This is provided “as-is”, and if you don’t like it... there is always stock and CM7.
We basically lack time to give full dedication to this rom, and we’re looking for skilled devs who know the OMAP4 platform, Android, and/or other things that might be relevant.
Please join us on IRC: some people are on #nook-tablet (freenode).
BUG REPORTS
This is the format for a bug report: “XXXXX isn’t working. Here is how to fix it: [INCLUDE SOLUTION]” Don’t have source? Too bad. You’ll have to wait then.
If you report bugs, please don’t be disappointed if we can’t fix them immediately (or even never). It’s not because we don’t care, but because we don’t have time or don’t know how to fix it.
NOTE: DEVELOPERS WANTED. Please contact us if you are a developer with something to contribute.
INSTALLATION:
Prepare a “bootable” clockworkmod (CWM) recovery SD. There are instructions for doing this in other threads on XDA.
Download a recovery.img (e.g. from CM9) and the update.zip files at the end of this post to your computer from the link below.
Boot into a recovery SD for acclaim and use it to install the update.zip file. Warning: It should overwrite the contents of your emmc, including the stock installation or other operating systems.
From ClockworkMod. perform CWM wipe data and cache (or “restore factory settings”) to clear previous content from those partitions. Again, you will be erasing anything you had on those partitions.
Remove the SD card and select the reboot option. You should now boot into CM10.
At this point, Fattire’s CyanoBoot bootloader can be used to flash recovery.img to the internal mmc.
To install CWM to emmc, download the recovery.img file from CM9 thread and do the following:
Download and install fastboot for your computer’s operating system.
Boot the device and hold the “n” key to get into the cyanoboot menu
From the menu, choose “Enable Fastboot”
On your computer, run: fastboot flash recovery recovery.img.
EMMC? IS THERE AN SD VERSION?
Of course it won’t be hard to do, but don’t look for an SD bootable version from us any time soon. EMMC is our thing, dig?
RETURNING TO STOCK (THEORETICAL-- THIS MAY NOT WORK)
If you have installed above rom and the CWM recovery and you really hate it and want to go back to stock, you may wish to try to flash the original acclaim_update.zip from BN. You have to unzip that file and edit META-INF/com/google/android/updater-script. Drop the first two lines here:
assert(getprop("ro.product.device") == "blaze" ||
getprop("ro.build.product") == "blaze");
Zip the package again. Then go to CWM, flash the zip, wipe, and reboot.
THANKS TO...
chrmhoffmann, hashcode, kuzma, fattire, rebellos, mik_os, nemith, Texas Instruments, BN, and so many others, especially those who helped test cyanoboot.
A special shout out to Bauwks is also in order, who defeated the malevelant locked bootloader with some serious geniusness.
0.08.3:
Changelog:- latest kernel (should roll back the reboot issues). Thanks to kuzma30- CM upstream sync
The files:
cm10-acclaim-0.08.3-full-of-bugs.zip
recovery-0.08.3.img
md5sums:c5fe2a891f3636838da5c1c3a0790cde cm10-acclaim-0.08.3-full-of-bugs.zip554647479d592411779f342d6977e709 recovery-0.08.3.img
-----------------
Older releases:
0.08.2:
- attempt to fix reboot issues differently (cpuidle44xx sync with omap TI kernel and workaround by mik_os/kuzma30. Should maybe also result in a better battery life. Please observe. Thx to both!)
- other kernel fixes: emif from nook hd, IPU deep idle, io tweaks, new governors, etc (thx to mik_os, kuzma30, hashcode). For full kernel change list, please look at kernel source here: https://github.com/Kuzma30/kernel3NookTablet/commits/jellybean.
- cm10 upstream sync
The Files:
cm10-acclaim-0.08.2-full-of-bugs.zip
recovery-0.08.2.img
MD5:
aad0ea1525702f6ed4a8071114daf1ec cm10-acclaim-0.08.2-full-of-bugs.zip
e3cea44fe918560d4780e9e739349227 recovery-0.08.2.img
0.08.1:
- touchscreen driver kernel fix (thanks to mik_os, see here)
- fix reboot into recovery (you also need to flash recovery.img to make this work: fastboot flash recovery /path/to/recovery-0.08.1.img)
- CM10 upstream sync
The Files:
cm10-acclaim-0.08.1-full-of-bugs.zip
recovery-0.08.1.img
MD5:
d00c14c2fc18c3afcd176defef8c2002 recovery-0.08.1.img
4d724adaf878490b8a068d8c4339e2cc cm10-acclaim-0.08.1-full-of-bugs.zip
0.08:
- touchscreen firmware updater app (many, many thanks to mik_os). Handle with care! If you flash back to stock or other roms, remember to flash touch firmware to stock first!)
- kernel updates (mainly drivers taken from Nook HD: many thanks to mik_os, kuzma.)
- cm10 upstream sync
The Files:
cm10-acclaim-0.08-full-of-bugs.zip
recovery-0.08.img
MD5:
5ec4e09e5050d6f75d625674e953b406 cm10-acclaim-0.08-full-of-bugs.zip
868f73098207dab46a5c39f93341e92b recovery-0.08.img
0.07.1
Changelog:
- pvr graphics driver update (IMG DDK [email protected])
- minor kernel changes (check history and contributors at https://github.com/Kuzma30/kernel3NookTablet/commits/jellybean)
- cm10 upstream sync
The Files:
cm10-acclaim-0.07.1-full-of-bugs.zip
recovery-0.07.1.img
MD5:
dcb0e1b4e980f31ca2fceb105727a9ef cm10-acclaim-0.07.1-full-of-bugs.zip
495f89ac4719af8066ddd21369037c47 recovery-0.07.1.img
0.07
Changelog:
- new touchpad driver: a huge thanks to mik_os! This rom and kernel works with newer fw found in other threads here - I personally haven't tried it though. Please beware that upgrading touch firmware might make it impossible to return to stock BN roms. The new driver also fixes issues previously seen in some games (temple run, etc)
- microphone xml config files: does it still crash the kernel?
- cm 10 upstream fixes
The Files:
cm10-acclaim-0.07-full-of-bugs.zip
MD5:
ee2e43591272818a2d9bd65507f580d4 cm10-acclaim-0.07-full-of-bugs.zip
0.06.1
Changelog:
- slightly better screen init (less white flashes on suspend/resume and full bootanim). Not perfect yet, though.
- CM10 upstream sync
The Files:
cm10-acclaim-0.06.1-full-of-bugs.zip
MD5:
5f2411fcf4e72105cc9badef89cb922b cm10-acclaim-0.06.1-full-of-bugs.zip
0.06 (starts to incorporate Android 4.1.2 changes)
Changelog:
- wifi (potential compatibility fixes as described here: https://github.com/loosethisskin/an...mmit/59edc9b57f63d92c228142a026b6ff1ceb6eca8b. Thx to meghd00t.)
- upstream sync with cyanogenmod (4.1.2 as of 10-10-2012)
The Files:
cm10-acclaim-0.06-full-of-bugs.zip
MD5:
2025d35034c50ea8f93413347365aca3 cm10-acclaim-0.06-full-of-bugs.zip
0.05.3
Changelog:
- enable smartreflex (voltage calibration - does this save some power?)
- update SGX
- JellyBean power HAL (thx to Hashcode)
- sync with CM10
- new attempt to fix reboot (cpuidle code from SGSII - device should go into deep sleep again, but reboots ... are they fixed? Guess not.)
The Files:
cm10-acclaim-0.05.3-full-of-bugs.zip
MD5:
4ca4fb6f224237db8af19d78b19fc05f cm10-acclaim-0.05.3-full-of-bugs.zip
0.05.2
Changelog:
- attempt to work around random reboots
(this seems to break proper "deep sleep" as it seems CPU_IDLE related)
- disable a (hopefully) unused regulator (VUSIM)
- dont make the display flash white on startup
- cyanogenmod upstream sync
The Files:
cm10-acclaim-0.05.2-full-of-bugs.zip
MD5:
c5835e6da0aff502ded12187d050c621 cm10-acclaim-0.05.2-full-of-bugs.zip
0.05.1:
Changelog:
- new attempt for 512MB devices for hw video decoding (aka ducati) - thanks to diimka, rebellos.
- less noisy dmesg
- newer su and persistent settings - thanks to meghd00t.
- recovery - thanks to meghd00t, ajayramaswamy.
- IP_NF_RAW - thanks to meghd00t.
- cm10 upstream sync - thanks to the CM folks
The Files:
cm10-acclaim-0.05.1-full-of-bugs.zip
recovery-0.05.1.img
MD5:
ff8254c2fc19f23d02d31cb9eaff0bdf cm10-acclaim-0.05.1-full-of-bugs.zip
0694405ebc452fde673d7e05d1467a5d recovery-0.05.1.img
Thanks as usual: hashcode, rebellos and kuzma30 (they do an __incredible__ job)
0.05:
- updated sgx, wifi
- video hw decoding (aka ducati). Incredible work from: rebellos, ntemis, hashcode, TI (esp. from diimka) and many others. Please report back if it works also on 512MB devices.
- hwcomposition. Incredible work from hashcode.
- cm10 upstream sync
The Files:
cm10-acclaim-0.05-full-of-bugs.zip
(recovery is still broken, so please use older ones or use one from the CM9 thread).
MD5:
2850631a56c6c617c5c917e9515fbfb7 cm10-acclaim-0.05-full-of-bugs.zip
0.04.2:
Changelog:
- updated wifi driver
- cm10 synced with upstream
The Files:
cm10-acclaim-0.04.2-full-of-bugs.zip
(recovery is still broken, so please use older ones or use one from the CM9 thread).
MD5:
5d87970c76c4971a14087b6374c9d4c6 cm10-acclaim-0.04.2-full-of-bugs.zip
0.04.1:
Changelog (aka "fixed"):
- updated SGX driver
- update kernel trying to avoid crashes (thx to rebellos, hashcode), but not successful (random reboots remain)
- sdcard issues after suspend fixed
- USB mount both internal and sdcard (thx to pawitp)
- should also consume less power and sleep deeper
- re-enabled brightness driver
- CM10 upstream changes
The Files:
cm10-acclaim-0.04.1-full-of-bugs.zip
Recovery 0.04.1 removed as it doesn't work (use recovery-0.03.img instead)
MD5:
9335459d3bd3fe56e934b67a90f88039 recovery-0.04.1.img
0.03:
Changelog (aka "fixed"):
- updated wifi and SGX driver
- update kernel trying to avoid crashes (thx to rebellos changes), but not really successful (random reboots seem to remain).
- CM10 upstream changes
- recovery img added
- cyanoboot updates for fastboot improvements
The Files:
cm10-acclaim-0.03-full-of-bugs.zip
recovery-0.03.img
MD5:
5f43b92b836b90df2bc5d9bd1e4bc969 recovery.img
f89e19f31ac6f6f11b3fc6fe53475ca1 cm10-acclaim-0.03-full-of-bugs.zip
0.02:
Changelog (aka "fixed"):
- sound / mic (but mic seems to crash kernel)
- su binary missing (thx hashcode)
- rotation animation (see http://review.cyanogenmod.com/#/c/19182/)
- some typos in cyanoboot (thx fattire/rebellos)
- usb mass storage is default (mtp works also), but only sdcard (not emmc shows up)
- chrome did not show up in market
The Files:
cm10-acclaim-0.02-full-of-bugs.zip
MD5:
5514a0eb67985975748444b0c17934b1 cm10-acclaim-0.02-full-of-bugs.zip
Older releases:
0.01:
The Files:
cm10-acclaim-0.01-full-of-bugs.zip
MD5:
95c3eac13d133feb1ebcf62817d6d866 cm10-acclaim-0.01-full-of-bugs.zip
Reserved for future usage
Wow, awesome! Thanks!
Heh I missed my 3rd post window. Oh well.
fattire said:
Heh I missed my 3rd post window. Oh well.
Click to expand...
Click to collapse
Sorry.......
You have to blame Chris, he posted it on Twitter and I came over quick like.
Ive been on CM9 for what seems like forever. My nook isnt my primary device at the time so all I've gotta say is: Here. we. go.
Sent from my Transformer Pad TF300T using XDA Premium HD app
This "SHOULD" fix your video decoder issue. Needs to go into /system/etc/
http://review.omapzoom.org/#/c/24665/
krylon360 said:
This "SHOULD" fix your video decoder issue. Needs to go into /system/etc/
http://review.omapzoom.org/#/c/24665/
Click to expand...
Click to collapse
wow, WOW WOW ! ! ! The ugliest bug is dead ?
old_fart said:
wow, WOW WOW ! ! ! The ugliest bug is dead ?
Click to expand...
Click to collapse
not sure, I dont have a NT, so I can't test it. but I AM going to modify it for the NC.
gapps-jb-20120711.zip - 72.36 MB This is the gapps for JB.
Sent from my NookTablet using XDA Premium HD app
Can there be a version of this ROM on the 2.6 kernel like there is one for CM9. I use that as my daily driver, wanna use this one similarly too!
NookTabletsPower said:
gapps-jb-20120711.zip - 72.36 MB This is the gapps for JB.
Sent from my NookTablet using XDA Premium HD app
Click to expand...
Click to collapse
I tihnk that may not be the latest... there's a newer one on this thread, it seems.
krylon360 said:
This "SHOULD" fix your video decoder issue. Needs to go into /system/etc/
http://review.omapzoom.org/#/c/24665/
Click to expand...
Click to collapse
It doesn't fix video as the ducati stuff doesn't work. But it fixes audio. Thanks!
To fix audio move attached file to /system/etc:
adb push media_codecs.xml /system/etc/
I believe it random reboots after sleeping for a while. Though to keep it alive, I set the display to go off in 30 min. I use WakeLock also.
The fix to enable chrome and whatnot as described in this post isn't included. Adding that line to your build.prop should enable those apps.
you're awesome guys ...
sound verified
chrmhoffmann said:
It doesn't fix video as the ducati stuff doesn't work. But it fixes audio. Thanks!
To fix audio move attached file to /system/etc:
adb push media_codecs.xml /system/etc/
Click to expand...
Click to collapse
Such a clean build there is no superuser. After I picked up on that 2 minutes later I rebooted again and had sound.
Thanks all!
~frustro
ylixir said:
The fix to enable chrome and whatnot as described in this post isn't included. Adding that line to your build.prop should enable those apps.
Click to expand...
Click to collapse
Done.
ok, i have cwm installed on emmc, i have cyanoboot also, i wiped data/system/cache/dalvic, installed the cm10 zip, and i get boot loop, boot stops during cm9 anim>
Please refrain from posting like this - DEV Thread
Mikey F said:
ok, i have cwm installed on emmc, i have cyanoboot also, i wiped data/system/cache/dalvic, installed the cm10 zip, and i get boot loop, boot stops during cm9 anim>
Click to expand...
Click to collapse
I am not sure what is the intention of your post.
a) If it is a "bug report", you are missing a lot of information...like logs, etc. Let me quote the OP: "This is the format for a bug report: “XXXXX isn’t working. Here is how to fix it: [INCLUDE SOLUTION]” Don’t have source? Too bad. You’ll have to wait then."
b) If you are just looking for support, well then: "You get none. Zero. Zip. We obligate ourselves to providing nothing further."
Please remember, this is a DEVELOPMENT thread, please treat it as such and instead of making posts as this, refer yourself to the Q&A forum, or the General section to post on an existing topic, or make your own topic with questions and/or support related topics.
I'm sure not only I would thank you for that!
Note: THIS IS A DEV thread, not a "I WANT THIS ROM NAU" thread
Local Manifest
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="photon"
fetch="git://github.com/photon-dev-team/" />
<!-- CM Removals -->
<!-- remove-project name="CyanogenMod/android_frameworks_base" / -->
<!-- remove-project name="CyanogenMod/android_system_core" / -->
<!-- remove-project name="CyanogenMod/android_vendor_cm" / -->
<!-- CM Replacements -->
<!-- project path="frameworks/base" name="dragonzkiller/android_frameworks_base" / -->
<!-- project path="system/core" name="dragonzkiller/android_system_core" / -->
<!-- project path="vendor/cm" name="dragonzkiller/android_vendor_cm" / -->
<!-- Photon-Dev-Team Stuff -->
<project path="vendor/moto" name="proprietary_vendor_motorola" remote="photon" />
<!-- Local Projects -->
<project path="kernel/tegra" name="dragonzkiller/daytona-kernel" revision="gb-2.6.32.9" />
<project path="device/moto/daytona" name="iPonyRadio/android_device_moto_daytona" revision="jellybean" />
<project path="vendor/moto/daytona" name="dragonzkiller/android_vendor_moto_daytona" revision="ics" />
</manifest>
Alright, so if you want to help, make sure you have a properly setup CM build enviornment
Code:
mkdir cm11
cd cm11
repo init -u https://github.com/CyanogenMod/android.git -b "cm-11.0"
mkdir .repo/local_manifests/
curl -L -o .repo/local_manifests/daytona.xml -O - L https://raw.guthub.com/iPonyRadio/android_local_daytona/ics/local_manifest.xml
repo sync (this will take a while)
. build/envsetup.sh
brunch daytona
Yoink
This thing is ridiculous
building returns a different error each time
Http://pixelperfectserver.tk/daytona.txt
Been playing around with my x2 back on stock since I have a different main phone. Its not as bad as I remember once you gain root and uninstall the Verizon bloatware.
That being said, I'm looking forward to see what comes of this.
Sent from my LG-LS970 using xda app-developers app
Watching this thread for sure. My X2 has long been shelved but I might break it out for fun if we get a reasonable Alpha build out of this.
I don't have the time nor expertise to help with the build, but I'm always willing to test drive, especially on a device I don't use, and I'm pretty good with logcat.
Thanks for the build thread and good luck!
ajbiz11 said:
This thing is ridiculous
building returns a different error each time
Http://pixelperfectserver.tk/daytona.txt
Click to expand...
Click to collapse
bootable/recovery/minui/../../../device/moto/daytona/recovery/graphics.c:186:5: error: conflicting types for 'gr_text'
http://osxr.org/android/ident?_i=gr_text
meh?
ajbiz11 said:
Note: THIS IS A DEV thread, not a "I WANT THIS ROM NAU" thread
Local Manifest
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="photon"
fetch="git://github.com/photon-dev-team/" />
<!-- CM Removals -->
<!-- remove-project name="CyanogenMod/android_frameworks_base" / -->
<!-- remove-project name="CyanogenMod/android_system_core" / -->
<!-- remove-project name="CyanogenMod/android_vendor_cm" / -->
<!-- CM Replacements -->
<!-- project path="frameworks/base" name="dragonzkiller/android_frameworks_base" / -->
<!-- project path="system/core" name="dragonzkiller/android_system_core" / -->
<!-- project path="vendor/cm" name="dragonzkiller/android_vendor_cm" / -->
[/CODE]
Click to expand...
Click to collapse
You may be able to get dragonzkiller to help you if he is not already working on such or collaborate with him.
Please excuse my noobishness.
When I use the command
repo sync
I get fetch errors for refs/heads/cm-11.0
When I do repo sync -f
I get an error : revision refs/heads/cm-11.0 in proprietary_vendor_motorola not found
The subsequent
brunch daytona
then it fails because the daytona device is not found.
I assume I have to do a rather simple change to a manifest, but being the complete noob I am, I would appreciate
some assistance.
polymath257 said:
Please excuse my noobishness.
When I use the command
repo sync
I get fetch errors for refs/heads/cm-11.0
When I do repo sync -f
I get an error : revision refs/heads/cm-11.0 in proprietary_vendor_motorola not found
The subsequent
brunch daytona
then it fails because the daytona device is not found.
I assume I have to do a rather simple change to a manifest, but being the complete noob I am, I would appreciate
some assistance.
Click to expand...
Click to collapse
Try rm -rf .repo
then the repo init with -f on the end
If not, I may look into it later
smallzfsu said:
bootable/recovery/minui/../../../device/moto/daytona/recovery/graphics.c:186:5: error: conflicting types for 'gr_text'
http://osxr.org/android/ident?_i=gr_text
meh?
Click to expand...
Click to collapse
Dead link
Now that the holiday is pretty much over I'm getting back on my PC...so...YAY!
unimatrix725 said:
You may be able to get dragonzkiller to help you if he is not already working on such or collaborate with him.
Click to expand...
Click to collapse
Tried PM-ing him long ago, still nothing back...
ajbiz11 said:
Tried PM-ing him long ago, still nothing back...
Click to expand...
Click to collapse
he didnt really ever like PM's...
this thread makes me wish i didnt trade the dx2 in for the 5$ at verizon when i bought my gnex lol...or id try and give this all a shot and see what could be done..best of luck friends
pattyboi:) said:
he didnt really ever like PM's...
this thread makes me wish i didnt trade the dx2 in for the 5$ at verizon when i bought my gnex lol...or id try and give this all a shot and see what could be done..best of luck friends
Click to expand...
Click to collapse
Yeah, I figured
And the Nexi will always be a better device than the X2
Also...I've decided to take baby steps towards cm11...I'm working on 10.1 right now
I got it to a point where I need a boot-hijack.zip....I see nothing about one anywhere...
ajbiz11 said:
Yeah, I figured
And the Nexi will always be a better device than the X2
Also...I've decided to take baby steps towards cm11...I'm working on 10.1 right now
I got it to a point where I need a boot-hijack.zip....I see nothing about one anywhere...
Click to expand...
Click to collapse
give me one sec i think i might no where there is one
EDIT: http://d-h.st/1jF :credit to Bluphant
here you go buddy,this is made specifically for cm10.1 already,so that might help a lil,ill try and help you find you anything you need ,i just dont have a test device lol
pattyboi:) said:
give me one sec i think i might no where there is one
EDIT: http://d-h.st/1jF :credit to Bluphant
here you go buddy,this is made specifically for cm10.1 already,so that might help a lil,ill try and help you find you anything you need ,i just dont have a test device lol
Click to expand...
Click to collapse
Alright
Now to see if this will work with the compile by putting it in the OUT dir like the compiler is asking, or if I need to modify the makefiles to zip the device/moto/daytona/hijack/hijack-boot/
ajbiz11 said:
Alright
Now to see if this will work with the compile by putting it in the OUT dir like the compiler is asking, or if I need to modify the makefiles to zip the device/moto/daytona/hijack/hijack-boot/
Click to expand...
Click to collapse
start with having the make compress the hijack. also make clean each time, a pain in the ass as it forces a complete restart but it will hopefully produce more consistant errors. though dont take this for truth, im just making a wild guess from my attemps at building cm10
Lrs121 said:
start with having the make compress the hijack. also make clean each time, a pain in the ass as it forces a complete restart but it will hopefully produce more consistant errors. though dont take this for truth, im just making a wild guess from my attemps at building cm10
Click to expand...
Click to collapse
hi guys, saw the project you all are working on. i'm one of the guys over on dx working on the kk build/development. i know that the dx and the dx2 are different devices with different configurations, but i'm coming here for a possible lead or inspiration on what i need to do to help with our project. http://forum.xda-developers.com/showthread.php?p=48051920 is the link showing our current attempts.
i stumbled across this thread at a good time i think. the issue we're running into does deal with the hijack-boot.zip.
make: *** No rule to make target `home/davidmcleod/android-cm11.0/out/target/product/shadow/hijack-boot.zip', needed by `/home/davidmcleod/android-cm11.0/out/target/product/shadow/obj/ETC/hijack-boot.zip_intermediates/hijack-boot.zip'. Stop.
we keep on running into this same error. any ideas?
palmbeach05 said:
hi guys, saw the project you all are working on. i'm one of the guys over on dx working on the kk build/development. i know that the dx and the dx2 are different devices with different configurations, but i'm coming here for a possible lead or inspiration on what i need to do to help with our project. http://forum.xda-developers.com/showthread.php?p=48051920 is the link showing our current attempts.
i stumbled across this thread at a good time i think. the issue we're running into does deal with the hijack-boot.zip.
make: *** No rule to make target `home/davidmcleod/android-cm11.0/out/target/product/shadow/hijack-boot.zip', needed by `/home/davidmcleod/android-cm11.0/out/target/product/shadow/obj/ETC/hijack-boot.zip_intermediates/hijack-boot.zip'. Stop.
we keep on running into this same error. any ideas?
Click to expand...
Click to collapse
How did you get it to work before?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Lrs121 said:
How did you get it to work before?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That would be a good question. Everything appears to be setup the same as GB and ICS, but it doesn't create the zip. We know its a rule thats missing somewhere, its just a matter of tracking down the correct file that should have the rule in it.
Woah. what luck. I just got a nexus 5, and I was wanting to learn the interals of android. Gave my dad my s3 for his droid x2 to dev on.
I guess i will check this thread out every once and a while
Hi guys. So I've had a few people PM me and ask for help cherry picking features to build a ROM from source. I've decided I might as well post a guide with what I've gathered. I'll outline the procedure for cherry-picking from both gerrit as well as GitHub, and what to do afterwards.
Once you've completed the guide, feel free to post questions/comments/advice in the thread. If you run into any issues, I will be happy to answer them (along with other helpful members of our community). If you think I should add something to the guide or change something, also feel free to let me know. I haven't noticed any good resource concerning cherry-picking on XDA, so discussion is encouraged.
Before we begin cherry-picking, I'm going to be making a few assumptions. I assume that:
you are using Ubuntu (or another Linux distribution) and you have git installed
you have the source code for your ROM downloaded on your PC
you know how to compile your ROM
you are somewhat comfortable using the terminal
Let's get started!
Table of contents:
1. Cherry-Picking from Gerrit
2. Cherry-Picking from GitHub
3. Conflict Resolution
4. Troubleshooting/After the Cherry-Pick
Cherry-Picking from Gerrit
Cherry Picking a feature from Gerrit
To begin cherry-picking, you should first go to the gerrit for your desired cherry-pick and find its entry/entries. I'll cherry-pick Halo from the ParanoidAndroid gerrit into AOSP.
Because I want Halo, I'll open go to ParanoidAndroid gerrit at http://gerrit.paranoidandroid.co and find the Halo entries. This is what it looks like:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You'll notice there are two Halo entries, one titled [1/2] Settings: HALO, and one titled [2/2] Frameworks: HALO. To get this feature, I'll need both, hence the tags 1/2 and 2/2 at the beginning. Here are the links for reference:
[1/2] Settings: HALO
[2/2] Frameworks: HALO
Great, now we have the entries for the two “commits” that we want to add to our ROM. We'll start with the first one. The page may look overwhelming at first, but there are two bits that are most important to us: the Project tag and the Download tab. Here's what they look like:
Look at the project title. It says “AOSPA/android_packages_apps_Settings”. This tells us exactly where in our source code to apply this commit. On my system, I have AOSP downloaded to the folder ~/AOSP. I open a terminal and enter the command “cd ~/AOSP”. Replace “AOSP” with your code directory.
Now, in your terminal, type:
Code:
cd packages/apps/Settings
Now that you're in the right spot, it's time to download the commit and try to apply it. Click the download tab in your browser, then from the dropdown choose “anonymous HTTP” and choose “cherry-pick”. Here's what it looks like:
When you click the clipboard next to the “Cherry-Pick” option, it'll copy to your clipboard. Now, go back to your terminal and press CTRL + Shift + V to paste it.
Code:
git fetch https://gerrit.paranoidandroid.co/AOSPA/android_packages_apps_Settings refs/changes/39/239/14 && git cherry-pick FETCH_HEAD
Chances are, unless you're very lucky, your terminal will do some work and look like this:
To continue, skip to post #4
Cherry-Picking a Feature from GitHub
Cherry-Picking a Feature from GitHub
To begin cherry-picking, you need to find the GitHub “commit” for what you want. A commit is a record of the changes that were made to achieve something, whether it be a new feature or a bug fix.
Today, I'm going to take pure AOSP and cherry-pick ParanoidAndroid's Halo. Because ParanoidAndroid gave up the feature, I can't take it from their GitHub. Conveniently, I have it in my own GitHub and will use that.
Note: you will only find things that have already been added to a project's code on GitHub. ParanoidAndroid gave up on Halo, so it is not added to their code. Because it is not already merged, it will not be in GitHub
First things first, you locate the commit. I know it's in my GitHub, so I'll open that in my browser at http://github.com/jabza-. I already know that Halo requires two commits, one for the settings and one for the frameworks. I'll open the projects “aospa_packages_apps_Settings” and “aospa_frameworks_base”. I'll start with the frameworks.
When you open the page, it's a little confusing. We want to see the commits, so we'll click “commits” toward the top.
Now, I'll have to go down the list to the Halo commit. Here's a link for reference: [2/2] Frameworks: HALO
Note: the commit name has [2/2] at the beginning, showing us that it is the 2nd commit of two. The other is in aospa_packages_apps_Settings
Note: my commit history in aospa_frameworks_base currently has two commits for Halo. The more recent one was a bug fix and I mistakenly left the commit message as it is – you want the older commit for the full change
Scroll down to the bottom of the blue commit message. Below it, there' s a list of the files and the changes made. You may use this for reference later, but it's not important now. What's important is the commit ID, which is listed at the bottom of the commit message.
Now, we go to the terminal. I have my AOSP source in ~/AOSP, so when I open my terminal first enter
Code:
cd ~/AOSP
The project name that we are working from is aospa_frameworks_base. This tells us that the commit belongs in frameworks/base. So, to begin work:
Code:
cd frameworks/base
Now, we have to “fetch” the project so we can cherry-pick the commit.
Code:
git fetch git://github.com/jabza-/aospa_frameworks_base.git
Now that we have the commit history of aospa_frameworks_base, we can tell the terminal to cherry-pick. We must use the commit ID at the bottom that we found earlier. You can copy the commit to your clipboard, and paste it in the terminal with CTRL + Shift + V.
Code:
git cherry-pick ab72e4ab36778474593ffce89150aece01d5f9c6
Obviously, when cherry-picking anything else, replace “ab72e4ab36778474593ffce89150aece01d5f9c6” with the commit ID of that commit.
Now, your terminal will do some work, and it will say it couldn't commit it automatically. It should look something like this:
Now, we get to resolve the conflicts. Continue to the next post.
Resolving Conflicts from Cherry-Picking
Resolving Conflicts from Cherry-Picking
So you've found the commit you want to cherry-pick. You've gone to the right place in your source code to apply it. You've told your computer to apply the cherry-pick. It said it couldn't. Now what?
Well let's see what's wrong.
Code:
git status
Your terminal will now tell you what files have been automatically changed for you and what you need to change yourself. In green are the files that are done, and in red are the files you need to tell it what to do with. Here's what your terminal should look like after “git status”:
If you cherry-picked from gerrit with me and did [1/2] Settings: HALO, it'll look something like this:
If you cherry-picked from GitHub with me and did [2/2] Frameworks: HALO, it'll look something like this:
In looking at the files in red, we see two different tags.
deleted by us – this means that there's a file in the commit that doesn't exist on our computer
both modified – this means that there's a file that was supposed to be modified, but that was modified on our computer from what was expected in the commit
deleted by them – this is a third tag you may see, though it's not here. This means that the commit deletes a file which we stil have on our computer
So, what do we do? Let's start with the ones tagged “both modified”. The first file in red underneath the frameworks/base commit is packages/SystemUI/res/layout/status_bar_expanded_header.xml. We'll open it in our favorite text editor and see what it's all about.
Code:
gedit packages/SystemUI/res/layout/status_bar_expanded_header.xml
Now we search for what's messing with our cherry-pick. It's enclosed in the tags “<<<<<<< HEAD” and “>>>>>>> ab72e4a... [2/2] Frameworks: HALO”. Lines 78-118 look like this:
Code:
<<<<<<< HEAD
android:layout_width="50dp"
android:layout_height="50dp"
android:scaleType="center"
android:src="@drawable/ic_notify_clear"
android:background="@drawable/ic_notify_button_bg"
android:contentDescription="@string/accessibility_clear_all"
/>
=======
android:layout_width="50dp"
android:layout_height="50dp"
android:layout_marginLeft="4dp"
android:scaleType="center"
android:src="@drawable/ic_notify_clear"
android:background="@drawable/ic_notify_button_bg"
android:contentDescription="@string/accessibility_clear_all"
/>
<FrameLayout android:id="@+id/context_button_holder"
android:layout_width="50dp"
android:layout_height="50dp"
android:layout_marginStart="4dp"
>
<ImageView android:id="@+id/halo_button"
android:layout_width="50dp"
android:layout_height="50dp"
android:scaleType="center"
android:src="@drawable/ic_notify_halo"
android:contentDescription="@string/accessibility_halo"
/>
<ImageView android:id="@+id/edit_mode_button"
android:layout_width="50dp"
android:layout_height="50dp"
android:scaleType="center"
android:src="@drawable/ic_notify_edit_normal"
android:background="@drawable/ic_notify_button_bg"
android:visibility="gone"
android:contentDescription="@string/accessibility_clear_all"
/>
</FrameLayout>
>>>>>>> ab72e4a... [2/2] Frameworks: HALO
Between the <<<<<< HEAD and ======== is code that wasn't expected to be there. Between ====== and >>>>>> ab72e4a... [2/2] Frameworks: HALO is the code that was added in by the commit. Here is where we use our judgement to edit the code to what we need. Because I can see that the code between <<<<<< HEAD and ====== is duplicated by the commit, I can just delete that snippet altogether. We also need to delete the tags added by our cherry pick. In the end, the code looks like this:
Code:
android:layout_width="50dp"
android:layout_height="50dp"
android:layout_marginLeft="4dp"
android:scaleType="center"
android:src="@drawable/ic_notify_clear"
android:background="@drawable/ic_notify_button_bg"
android:contentDescription="@string/accessibility_clear_all"
/>
<FrameLayout android:id="@+id/context_button_holder"
android:layout_width="50dp"
android:layout_height="50dp"
android:layout_marginStart="4dp"
>
<ImageView android:id="@+id/halo_button"
android:layout_width="50dp"
android:layout_height="50dp"
android:scaleType="center"
android:src="@drawable/ic_notify_halo"
android:contentDescription="@string/accessibility_halo"
/>
<ImageView android:id="@+id/edit_mode_button"
android:layout_width="50dp"
android:layout_height="50dp"
android:scaleType="center"
android:src="@drawable/ic_notify_edit_normal"
android:background="@drawable/ic_notify_button_bg"
android:visibility="gone"
android:contentDescription="@string/accessibility_clear_all"
/>
</FrameLayout>
Now we can save and quit.
We've resolved the conflict (assuming that was the only one), and now we can mark it as such in the terminal. To do so, we use this command:
Code:
git add packages/SystemUI/res/layout/status_bar_expanded_header.xml
Now, we can do “git status” again and work on the next file we need to modify.
But what about the “deleted by us” files? Well, git is smart. All we need to do is determine if we need those files (hint: unless you really know what you're doing, you do need them). If we need them, git already loaded the files up, so we just have to mark them as resolved by doing
Code:
git add res/values/pa_arrays.xml
You can replace “res/values/pa_arrays.xml” with the rest of the files labeled “deleted by us”. You can also do more than one file at once, like so:
Code:
git add res/values/pa_arrays.xml res/values/pa_strings.xml whatever/files/I/want.java
Continue until you've fixed all the issues.
Note: when you open a file in gedit, it creates a file with the same name but with a ~ added to the end. When you do “git status” these files will show up as “untracked files”. You can either delete them with the command “rm path/to/file.java~” or just ignore them.
Once you do “git status” and all the files turn up green, you have finished resolving the conflicts. Now is the best time to compile your ROM and see if your changes worked. If you're in a rush (or lazy or don't feel like waiting for a ROM to compile or you've already tested it), you can now commit your changes.
Code:
git commit
It'll take you to a screen to write your commit message. It opens it in the in-terminal editor “nano”. You can edit it to say whatever you want, and when you're done press CTRL + X to exit, and then press Y to save the changes. Then your terminal will say you've committed the changes.
Congratulations! You've successfully cherry-picked a commit.
Troubleshooting/After the Cherry-Pick
Troubleshooting/After the Cherry-Pick
Once you've finished adding a cherry-pick, a whole variety of things can happen. You might:
build, and it will stop with some build erros
build, and it will complete, but something will go wrong when you flash it
want to get rid of the cherry-picks altogether
Well, what do you do?
If you build, and it stops building, there will be build errors. Your terminal will tell you what's wrong. Look/scroll up, and there will be something that says:
Code:
path/to/file/problem.java:86: some sort of error ocurred
line.of(code, that causes); a problem {
^
The first thing it says is a file. It will be a path relative to the part it was compiling, so you might have to look for a clue above that to see where it was working on. At the end of the file is a number (in this case 86). That number tells you what line the problem is on in that file. After that, it tells you what the error was that in ran into. Then, it'll print the line that had the error with a carat (^) underneath where it had an issue.
How do you fix it? Just open up the file with something like
Code:
gedit path/to/file/problem.java
and go to line 86 and see what the problem is. Usually it's something pretty straightforward, like mismatched parentheses or a dropped semicolon. Once you've fixed the issue, save the file and build again!
But what about if the build is successful, but it causes bugs in your build? Well, start up your phone plugged into your computer, and use this command:
Code:
adb logcat > errorlog
Once the phone becomes available, your computer will start recording the logcat to the file errorlog. Once you've captured the bug, then you can disconnect your phone and reflash something stable. You can also use CTRL + C to stop the logcat command. Now, you can open the logcat with the command
Code:
gedit errorlog
Reading logcats may take some getting used to. It will take quite a bit of scrolling, but the errors are probably marked with an E at the beginning of the line.
Now, what about if you've got some issues, and you just want to scrap the cherry-picks? Well, it's pretty straightforward. Just use
Code:
repo sync
and all committed cherry-picks will be wiped out and you'll be synced with the source that you're building from/
What if you want to do a repo sync and keep that commit, you ask? Don't worry! Git is smart. It remembers how you resolved the cherry-pick. You can do a repo sync and then cherry-pick again, and it'll automatically try to apply your previous resolution. Neat, huh?
Alternatively, you can fork the project to your own git repository (GitHub accounts are free for students!) and add that to your repo manifest. That's a whole different story, though, and will require extra research.
You should also mention how to cherry pick multiple commits
was looking for a guide like this for modding my build...gr8 guide...
AWSM !!
Just when I decided to make some personal builds, this shows up. Thank you so much! You're awesome!
Sent from my Nexus 7 using Tapatalk
Grarak said:
You should also mention how to cherry pick multiple commits
Click to expand...
Click to collapse
I would like to know this too, when I try to add two commits to the same location, it wants to drop one and add the other. I want to keep both but I cant figure out how to do so. Thanks for your help!
Great guide. It really helps noobs like me xD. One question what are the repositories I should fork from paranoid android into my github to build a ROM for nexus 4. Their github have soooo many repositories like apps and settings, packages, manifest etc etc
Sent from my Nexus 4 using Tapatalk
Grarak said:
You should also mention how to cherry pick multiple commits
Click to expand...
Click to collapse
SleepyS40 said:
I would like to know this too, when I try to add two commits to the same location, it wants to drop one and add the other. I want to keep both but I cant figure out how to do so. Thanks for your help!
Click to expand...
Click to collapse
Cherry-picking multiple commits is pretty straightforward. Once you've resolved any conflicts for one commit, you have to finish by using the command
Code:
git commit
if you want to add another cherry-pick in the same location.
Once you've committed that, you should be able to start the cherry-picking process over again exactly the same. If you have an issue, can you tell me what your terminal says, or post a screenshot?
Walterwhite007 said:
Great guide. It really helps noobs like me xD. One question what are the repositories I should fork from paranoid android into my github to build a ROM for nexus 4. Their github have soooo many repositories like apps and settings, packages, manifest etc etc
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
To build ParanoidAndroid, you first have to download the source to your computer. So you'd have to make a directory and use "repo init -u http://github.com/AOSPA/manifest.git -b kitkat && repo sync" to start the download. It's a big download, so be ready to wait a couple hours. There's a good guide for building ParanoidAndroid 4+ here
However, as far as forking a repository, you only need to fork the repositories that you want to make your own changes to and keep track of. Really, you don't have to fork anything.
Nicely written.
karanrajpal14 said:
Just when I decided to make some personal builds, this shows up. Thank you so much! You're awesome!
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
+100
Took the workds right outta my mouth!!:laugh::highfive:
I have the source code. But when I successfully cherry pick some commits and when I say gitpush it says access denied something. I want to fork pa's nexus 4 ROM sources into my git repository so that I can sync from my github and build. But what are the things I need to fork??
Walterwhite007 said:
I have the source code. But when I successfully cherry pick some commits and when I say gitpush it says access denied something. I want to fork pa's nexus 4 ROM sources into my git repository so that I can sync from my github and build. But what are the things I need to fork??
Click to expand...
Click to collapse
Well yeah, git push tries to send your changes to the repository you took it from - in this case, PA's. For obvious reasons, you don't have permissions to push changes to the PA github. You just have to fork the repos you want to change and add them in your repo manifests. If you want the entire ROM in your git, you'll have to look at all the projects in .repo/manifest.xml and fork every single one. That's a little excessive, so just fork the repos you want to change.
jabza said:
Well yeah, git push tries to send your changes to the repository you took it from - in this case, PA's. For obvious reasons, you don't have permissions to push changes to the PA github. You just have to fork the repos you want to change and add them in your repo manifests. If you want the entire ROM in your git, you'll have to look at all the projects in .repo/manifest.xml and fork every single one. That's a little excessive, so just fork the repos you want to change.
Click to expand...
Click to collapse
Thanks bro. I tried many times cherry picking halo but that always messed up. Now after following this great guide I'll give it another try !!
Say my name
Thank you so much for the awesome thread..:good:
Very good tutorial :good:
But I've two question:
- What does the command "git commit" do? Will the rom compile without the cherry-pick without this command?
- Can I compile a flashable zip for my rom just with the cherry-pick and without compiling the whole rom again?
I was hoping that someone could help me here so the problem is that I am trying to build OMNI ROM for mako but even after following the guide I dont't see any zip out/target/product/mako. I followed this guide http://docs.omnirom.org/Build_for_mako
xxLeoxx93 said:
Very good tutorial :good:
But I've two question:
- What does the command "git commit" do? Will the rom compile without the cherry-pick without this command?
- Can I compile a flashable zip for my rom just with the cherry-pick and without compiling the whole rom again?
Click to expand...
Click to collapse
- "git commit" tells your computer it's done with editing and finishes the cherry-pick process. That is when git saves your resolution, so that if you go back and cherry-pick that commit again it can automatically apply your resolution to the problem. The ROM will compile without this command, but you won't be able to use "repo sync" to update that project or add any other cherry-picks to that location until you run "git commit" or "git cherry-pick --abort", which removes the cherry-pick altogether.
- When you rebuild the ROM, as long as you don't use "make clean" or "make clobber", it will only recompile the parts that have changed. The next build will go much faster. If you want the builds to go even faster, you should use ccache.
DirtyUnicorns for Harpia!!!
Here is DirtyUnicorns (n7x-caf branch), ported to the Moto G4 Play! This ROM as-is is unrooted and without Gapps, so please don't forget to flash some sort of root zip as well as Gapps if you so choose.
As with all development projects, you take full responsibility to what happens to your device. While I will certainly help you fix a problem to the best of my abilities, don't sue me if your alarm doesn't go off and you lose your job or something.
Tested On
-XT1607 (me)
-XT1603, thanks to @EmersonTR
What's Working
-Speaker audio
-Brightness adjusting
-Adaptive brightness seems to be fine
-Calls
-Texts
-SD card (formatted as internal storage)
-WiFi
-Mobile
-Photo taking
-Video recording
-GPS location
-Device encryption (takes longer than usual to encrypt, but works fine afterwards, DOES NOT SEEM TO WORK WITH FIREKERNEL FOR SOME REASON)
-Root (SuperSU may say the su binary is occupied, if this happens just reflash SuperSU in recovery and you should be fine)
-Boot animation (now fits screen and doesn't get cut off)
-Honestly, everything seems fine.
What's Not Working
-For some reason, when I use SomeFeaK 8.00 kernel and any audio comes out of the speaker, I get little clicks coming out as well. I'm going to speak to my good man @facuarmo to see what I can do about this.
-You tell me
Upcoming Features
N/A
Download Links
LINK TO BUILD FOLDER
Source Code
*NOTE* If you are having problems with Jack during compilation, follow this guide to resolve them.
-Link to my harpia device tree for DU
-My local-manifest xml file, so you know what kernel/device/vendor trees (and other tweaks) I used:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- remote names -->
<remote name="aidonnou" fetch="https://github.com/aidonnou-surnia" />
<remote name="losgit" fetch="https://github.com/LineageOS" />
<remote name="tehmuppets" fetch="https://github.com/themuppets" />
<remote name="dunicorns" fetch="https://github.com/dirtyunicorns/" />
<remote name="jasonmerc" fetch="https://github.com/jasonmerc/" />
<!-- harpia stuff -->
<project path="device/motorola/harpia" name="android_device_motorola_harpia" remote="jasonmerc" revision="n7x-caf" />
<project path="device/motorola/msm8916-common" name="android_device_motorola_msm8916-common" revision="du_n7x-caf" remote="aidonnou" />
<project path="kernel/motorola/msm8916" name="android_kernel_motorola_msm8916" revision="cm-14.1" remote="losgit" />
<!-- dependencies -->
<project path="vendor/motorola" name="proprietary_vendor_motorola" revision="cm-14.1" remote="tehmuppets" />
<project path="packages/resources/devicesettings" name="android_packages_resources_devicesettings" revision="cm-14.1" remote="losgit" />
<project path="external/bson" name="android_external_bson" revision="cm-14.1" remote="losgit" />
<!-- du-dependencies -->
<project path="hardware/qcom/audio-caf/msm8916" name="android_hardware_qcom_audio" revision="cm-14.1-caf-8916" remote="losgit" />
<project path="hardware/qcom/display-caf/msm8916" name="android_hardware_qcom_display" revision="cm-14.1-caf-8916" remote="losgit" />
<project path="hardware/qcom/media-caf/msm8916" name="android_hardware_qcom_media" revision="cm-14.1-caf-8916" remote="losgit" />
<project path="hardware/qcom/fm" name="android_hardware_qcom_fm" revision="n7x-caf" remote="dunicorns" />
<project path="packages/apps/FMRadio" name="android_packages_apps_FMRadio" revision="n7x-caf" remote="dunicorns" />
<project path="system/qcom" name="android_system_qcom" revision="n7x-caf" remote="dunicorns" />
<!-- when you believe in things that you dont understand -->
<!-- then you suffer..... -->
<!-- superstition aint the way -->
</manifest>
Special Thanks To (AKA what was in my local-manifest xml file)
-DirtyUnicorns team
-LineageOS team
-"themuppets" GitHub
-"aiddonou" GitHub
And last but certainly not least, a HUGE thanks to @ElDainosor for the one-on-one help he gave me with setting up my build environment and manifest file properly. His assistance and guidance made this possible.
RESERVED
Mega.nz have bandwith limit, i can't download, can you please make a mirror on androidfilehost or google drive?
Thanks.
EmersonTR said:
Mega.nz have bandwith limit, i can't download, can you please make a mirror on androidfilehost or google drive?
Thanks.
Click to expand...
Click to collapse
Thanks for the heads up. I'll move it to my Google Drive, and I'll look into making an AndroidFileHost account for the future
jasonmerc said:
Thanks for the heads up. I'll move it to my Google Drive, and I'll look into making an AndroidFileHost account for the future
Click to expand...
Click to collapse
Really thanks, i will try as soon i can and congratulations for the successful build.
EmersonTR said:
Really thanks, i will try as soon i can and congratulations for the successful build.
Click to expand...
Click to collapse
I just want to let you know that my internet connection is being slow now, so uploading it to Google Drive will take around 20 minutes. I apologize for keeping you waiting, my machine is working as fast as it can
EDIT: Build folder updated, will now take you to Google Drive
Looks like someone else beat me to porting this ROM.
At the moment his build doesn't seem to have the camera working, but once that gets fixed in his ROM it would be pretty pointless for me to continue maintaining my version of this. But for now, enjoy what I cooked up
Guessing no OTA updates?
aaronboy205 said:
Guessing no OTA updates?
Click to expand...
Click to collapse
If you mean continued releases, I'll try to update this ROM regularly until Subhrajyoti fixes the camera issues in his build. If you mean OTAs as in getting updates from the settings menu, you won't be able to download updates from there since this is an unofficial release. Updates will have to be manually downloaded and flashed with each new release.
jasonmerc said:
If you mean continued releases, I'll try to update this ROM regularly until Subhrajyoti fixes the camera issues in his build. If you mean OTAs as in getting updates from the settings menu, you won't be able to download updates from there since this is an unofficial release. Updates will have to be manually downloaded and flashed with each new release.
Click to expand...
Click to collapse
Thanks ?
Working fine here on XT1603, thank you. But the bootanimation is too big
EmersonTR said:
Working fine here on XT1603, thank you. But the bootanimation is too big
Click to expand...
Click to collapse
Why do people keep reporting the animation bug?. Just download any application that allows you to change the boot animation and that's it. You can select the boot animation that you like and forget about it.
Marioandroid777 said:
Why do people keep reporting the animation bug?. Just download any application that allows you to change the boot animation and that's it. You can select the boot animation that you like and forget about it.
Click to expand...
Click to collapse
I like the Dirty Unicorns bootanimation and i already resized, i'm just letting the others know.
EmersonTR said:
I like the Dirty Unicorns bootanimation and i already resized, i'm just letting the others know.
Click to expand...
Click to collapse
I appreciate you letting me know, I was not aware of this issue since I don't really look at my phone while I turn it on anyway. I'll try reducing the size when I push out my next build, which will probably be the last build I do since I think Subhrajyoti is in the process of fixing the camera in his builds now. I set it to 720x1280 before, which is the exact resolution of harpia's screen, but I'll try 540x960 next time (size of Moto E's screen, which should make it all fit nicely)
EDIT: ElDainosor saves the day once again, he showed me how to fix this issue without needing to reduce the resolution down to 540x960. Building right now, will upload to the Google Drive folder once it is done for someone else to test (I'm currently working on Lineage 13 with my harpia). If you're running a previous version of DirtyUnicorns, just flash the new zip and reboot, no need to wipe anything.
New build is up, for whoever wants to fix their boot animation issues
UPDATE: Subhrajyoti has since used these fixes here to fix the camera in his own version of the DU ROM, so I will NOT be updating this ROM anymore. Go to his build if you would like continued support.
*Note: I'm pretty sure you don't have to do a factory reset before flashing his DU ROM if you are coming from my version of DU
ANOTHER UPDATE: Since Subhrajyoti seems to not be maintaining this ROM anymore, and since my Lineage 13 project was cut short due to weird sync errors, I'm going to revive this ROM of mine here and make more builds of this. Check the download link in the first post, as of today I have a build of DU 11.7.2 up and working.
jasonmerc said:
ANOTHER UPDATE: Since Subhrajyoti seems to not be maintaining this ROM anymore, and since my Lineage 13 project was cut short due to weird sync errors, I'm going to revive this ROM of mine here and make more builds of this. Check the download link in the first post, as of today I have a build of DU 11.7.2 up and working.
Click to expand...
Click to collapse
News on O?
NovaKenn said:
News on O?
Click to expand...
Click to collapse
My answer rhymes with "O"
But when it does come out, I'll be moving to a different, "funnier" O project I think you guys will enjoy
My son has a Moto g play from Verizon. Want to make sure this is the same device. Don't know much about Motorola devices. Can someone let me know? Thanks
[10.0_r40/v222] download : https://androidfilehost.com/?a=show&w=files&flid=286761All-in-one: "Regular" #phhusson Quack AOSP 10.0 vanilla build with microG patches, embedded #su /system, and multiple foss apps:
(/system partition requires: [arm64:>1.9Gb] [arm32:>1.3Gb] minimum)
official microG: GmsCore(mapbox) GoogleServicesFramework DroidGuard
addons: NominatimGeocoderBackend DejaVuBackend IchnaeaNlpBackend LocalWifiNlpBackend openbmapRadiocellsOrg LocalGsmNlpBackend
hot-built: emailExchange2 snapMusic calendarEtar Terminal screenRecorder testDevCamera Calculator
prebuilt: Fdroid F-DroidPrivilegedExtension browserQuarks ZxingClient kDI Superuser BromiteWebview NeoLinker
system/bin* : aapt32 grep64(pcre2grep version 10.22 2016-07-29)
Also included are these non-foss 3 Google : Playstore, Calendar/Contact_Sync; like phh-Superuser apk, they are disabled by default, and can be activated via Settings/Apps.
Click to expand...
Click to collapse
not included: Latest compatible Google Maps 9.84.2 optional https://androidfilehost.com/?fid=11410963190603886579
Extra(s): Nfc and Cafeine tiles, basic photoEditor*, experimental WakelockBlocker via Settings/{}DevOptions <USE WITH CAUTION>.
Nota: android Webview v87 is signed & upgradable from Bromite, Terminal is activated via Settings/System/Advanced/DeveloperOptions and Playstore has to be ForceStop-ed once after registration/wizard, and relaunch. F-Droid V.102.3 auto-update needs FDroid/Settings/ExpertMode/Privileged disabled.
After first rom flash and MicroG prim-initialization, for immediate working location, toggle /Settings /Security&Location /Location off&on. Switching between vtm & mapbox can need wipe for apk cache & account re-creation.
All included prebuilds are fdroid signed editions.
donations: Consider prim-origin @phhusson @MaR-V-iN @csagan5(Bromite)
others : @ale5000 @Setialpha #ThibG(DroidGuard)
+info for microG implementation https://forum.xda-developers.com/android/development/microg-unofficial-installer-t3432360
If you need more, please let me know about it, but for more "Google": just switch to phhusson "gapps" flavour...
Bugs reporting
ufOfficial rom includes static & passive app kDI (KalturaDeviceInfo) to list all your device specs (treble, widevine...) in a json, and can help you with GSFid or others info(s). This app doesn't connect to internet, and the json (~Android/data/com.oF2pks.kalturadeviceinfo/files/) should not include any private data or ids; it's up to you to share or not.
If you encounter major AOSP "hardware (not software)" related bugs, please switch to #phhusson vanilla v___ edition and help him with proper focused hardware logs. For Camera2 missing features, take time to check OpenCamera first, aosp DevCamera "sample stub" is included for testing purpose : autofocus... ; full cam specs are also in KalturaDeviceInfo (per each "physical" cam).
Click to expand...
Click to collapse
(Specific Redmi Note 9 Pro overlay_joyeuse & props_ curtana/joyeuse are added)
(Huawei/msm8937 Moto/G7Play Razer/cheryl Sony/XZ3 Realme/X2Pro overlays are switched to aosp FusedLocation)
swappiness =28 & dirty_writeback_centisecs =1500: check #suKAdiutor for other tweaks.
For Treble with root, you can do some tests modifying specifically,
/system/bin/rw-system.sh to change some features on post-fs:
https://github.com/phhusson/device_phh_treble/blob/android-10.0/vndk.rc#L1
check also phh-on-boot.sh & phh-on-data.sh
hot-built links :
Code:
[SIZE="1"]<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="los" fetch="https://github.com/LineageOS/" />
<remote name="of2" fetch="https://gitlab.com/oF2pks/" />
<remote name="qcom" fetch="https://source.codeaurora.org/" />
<remote name="aos" fetch="https://android.googlesource.com/"/>
<project path="packages/apps/ExactCalculator" name="platform/packages/apps/ExactCalculator" remote="aos" revision="master"/>
<project path="packages/apps/Recorder" name="android_packages_apps_Recorder" remote="los" revision="lineage-17.1" />
<project path="packages/apps/Jelly" name="jelly" remote="of2" revision="jQuarksMore" />
<project path="packages/apps/SnapdragonMusic" name="quic/la/platform/packages/apps/SnapdragonMusic" remote="qcom" revision="android_ui.lnx.4.0.r24-rel" />
<project path="packages/apps/Exchange" name="external/gigabyte/platform/packages/apps/Exchange" remote="qcom" revision="caf/LA.UM.7.7.c25" />
<remove-project name="platform/packages/apps/Calendar" />
<project path="packages/apps/Etar" name="android_packages_apps_Etar" remote="los" revision="lineage-17.1" />
<remove-project name="platform/packages/apps/Terminal" />
<project path="packages/apps/Terminal" name="android_packages_apps_Terminal" remote="los" revision="lineage-17.1" />
</manifest>
[/SIZE]
- Bromite latest webView v84, upgradable via F-Droid repo https://fdroid.bromite.org/fdroid/repo
- Optimized browser Quarks ( adBlocker, offline reading mht , print/pdf , share/clipboard target ...) https://gitlab.com/oF2pks/jelly/commits/jQuarksMore. Conversely to embedded WebViewShell, Quarks don't allow permissions for Camera & Microphone capture (WebRTC)
Attached State_Changes___.zip if for rom devs only
Thanks. will definitely see how it works on razer phone 2
Working super great here on OnePlus6 (enchilada), but I noticed a bug with the fingerprint sensor: working fine right after 1st boot, but not anymore after some times (I don't exactly know how to reproduce). Anyone is experiencing the same?
Edit: after a data wipe, fingerprint sensor is working fine during 1st boot but stops working right after any reboot without any modifications to system settings or app installed.
Edit2: it is actually a Quack Phh-Treble issue, confirmed on system-quack-arm64-ab-floss.img .
Edit3: Possible temporary workaround waiting for a real fix: https://github.com/phhusson/treble_experimentations/issues/1432#issuecomment-675568932
@oF2pks is the org.openbmap.unifiedNlpProvider package deprecated and thus can be disabled without any trouble for microG location backend to work?
That's what I think but I would like a confirmation.
Edit: found a confirmation here
https://github.com/FriendlyNeighborhoodShane/MinMicroG_releases/releases
Replaced abandoned FDroid GSM NLP backend with releases from @ploink
Click to expand...
Click to collapse
Thanks for the work, those prebuilds are handful
Everything is running fine here.
there's a problem with google maps download from androidfilehost:
Code:
ava6.androidfilehost.com sent an invalid response.
ERR_RESPONSE_HEADERS_MULTIPLE_CONTENT_DISPOSITION
any chance of a mirror?
edit: nevermind, I've found it
How do I update to more recent build of MicroG GMS Core, for example the one released today?
New home build of GmsCore uploaded in post#1
pvdeejay said:
How do I update to more recent build of MicroG GMS Core, for example the one released today?
Click to expand...
Click to collapse
Due to missing official #MaR-V-iN mapbox.key for extensive use of microG (https://github.com/microg/android_pa...re/issues/1155), I will not maintain home build of 3x microG components, and switch next @phhusson aosp10 (if any ?) to official #MaR-V-iN 3x apk.
( @pvdeejay ) , if you have twrp on your device, I already suggest trying #Setialpha packages with official #MaR-V-iN releases https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928.
Even with a future aosp10 GSi; since I'm using anticipated PlayServices variants to v20.99.99, this will need manual (root #su) cleaning of /data/data/* for all 3 microG apks https://forum.xda-developers.com/showpost.php?p=83540735&postcount=37 or a complete re-install (fastboot erase).
hmm, this is tricky as I have device with no TWRP xiaomi redmi 9 code name galahad.
So I guess I need to tweak the image with new apks and reflash using fastboot. Am I right?
pvdeejay said:
hmm, this is tricky as I have device with no TWRP xiaomi redmi 9 code name galahad.
So I guess I need to tweak the image with new apks and reflash using fastboot. Am I right?
Click to expand...
Click to collapse
For now, use my recent attached. I don't believe a GSi can be tweaked easily. If @phhusson don't update aosp10 anymore (r45 is still on cve Aug 2020 and r46/47 are unfinished by Google), I will re-upload aosp10.0_r40 with official #MaR-V-iN 3x apks, but that would need fastboot erase (or root:#su file manager on /data/data/*).
I'm sorry, I'm getting 404 error on the latest microg upload no matter if I click in the first post or the latest one.
Should I just wait or can you do something about it please?
pvdeejay said:
I'm sorry, I'm getting 404 error on the latest microg upload no matter if I click in the first post or the latest one.
Click to expand...
Click to collapse
AFH link : https://androidfilehost.com/?fid=10763459528675570052
Even I did uploaded it myself on xda , I've same 404E ( @svetius ?). Guess something is wrong with mirrors ( or new xda changes) ?
I am coming back to this after a while.
I don't seem to be able to get google maps work. it always crashes when started.
I have only installed this as an app update and I don't managed to add it as a system app. Might that be a problem?
Latest GmsCore uploaded in post #1 2020-11-19 commits: https://forum.xda-developers.com/attachment.php?attachmentid=5138863&d=1605887888
pvdeejay said:
I am coming back to this after a while.
I don't seem to be able to get google maps work. it always crashes when started.
I have only installed this as an app update and I don't managed to add it as a system app. Might that be a problem?
Click to expand...
Click to collapse
Seems the issue is about cronet JAVA NIO ByteBuffers ; check https://github.com/microg/GmsCore/issues?q=cronet . Latest @MaR-V-iN don't solve it (this issue is not on Webview implementation).
Final(?) release.
Due to missing official #MaR-V-iN mapbox.key for extensive use of microG (https://github.com/microg/GmsCore/issues/1155):
aosp10.0_r40 with official #MaR-V-iN 3x apks is re-uploaded
https://androidfilehost.com/?a=show&w=files&flid=286761{_Names} = {_Apks}
- DroidGuard = org.microg.gms.droidguard
- GoogleServicesFramework = com.google.android.gsf
- GmsCore = com.google.android.gms
(Because of anticipated to v20.99.99 PlayServicesvariants),
TO UPGRADE from previous rom, you need to imperatively apply following steps:
Remove Google account(s) via Settings/Accounts
Uninstall any update via Settings/Apps/3x_apks (microG_Services_Core)
Clear storage via Settings/Apps for 3x_apks
root:#su with GhostCommander (or other or TWRP) to delete 3x_apks for: /data/data/3x_apks
fastboot flash system10.img and reboot
Click to expand...
Click to collapse
I also switch hot-built jQuarks browser to latest F-Droid signed jQuarks (upgradable) edition: be sure to save your possible *.mht archives prior to fastboot flash system.
pvdeejay said:
How do I update to more recent build of MicroG GMS Core, for example the one released today?
Click to expand...
Click to collapse
Once updated, use F-Droid repo or straight https://microg.org/download.html to update microG 3x_apks.
Hello,
I have issues migrating to the microg.org compatible build.
I have no uninstall option for microg gms core so I have only wiped the data and flashed the updated system image.
After rebooting I can see no packages with compatible signature when looking at microg version in f-droid.
So I have manually tried to remove everything related to GMS under /data and /data/app using su and rm over adb.
But still when reflashing and rebooting I do have this.
How would I go about fixing it?
gsf proxy and microg guard helper are both okay as I had no updates to them installed.
Edit:
Granted signature spoofing through Settings -> Apps -> MicroG GMS Core.
However I still have two permissions missing: receive SMS and background location.
When I tap them on the self check activity nothing changes. I can't enable them from the Settings -> apps...
And still F-Droid can find no compatible versions so I suspect I have semi broken install here.
Edit:
I've downloaded latest apk from microg.org and installed it on the top of what I have so far and it sorted it-self meaning that device registration, FCM and unified NLP are all working great. F-droid now correctly shows compatible versions and I expect that it will be able to install updates in the future.
What I have noticed is that I have only few apps that were able to reregister FCM token after this upgrade dance. A lot of apps are still waiting for push messages with the old token e.g. Microsoft Teams, Viber, Element (former riot.im), Revolut, George (Die Ertzte banking) and more. I am looking for a way on how to invalidate their FCM tokens and force these apps to register for push messages again other than clearing their data and logging in and / or setting up them from scratch.
Is there a way around this?
Thanks and greetings
Peter
It appears I can't edit my previous post...
Okay, figured the last bit of the puzzle and now I'm happy with the migration.
Please note that this rom is prerooted thus I fired up ADB and poked a bit with shared preference storage related to the apps I wished to force refreshing their FCM tokens.
I ended up deleting files related to GMS, FCM, firebase and similar such as these....
FirebaseAppHeartBeat.xml
com.google.android.gms.appid.xml
com.google.android.gms.measurement.prefs.xml
com.google.firebase.crashlytics.xml
com.appboy.push_registration.xml
com.appboy.storage.user_cache.push_token_store.37a6259cc0c1dae299a7866489dff0bd.
This is not straight forward, but it's easily done with a bit of common sense.
Out of 10 apps I had to reinstall only one of them.
Also I have discovered in the process that some apps may refresh their FCM token on upgrade as this has happened to me with one of those 10 apps.
pvdeejay said:
However I still have two permissions missing: receive SMS and background location.
When I tap them on the self check activity nothing changes. I can't enable them from the Settings -> apps...
Click to expand...
Click to collapse
These bugs seem fixed in today GmsCore v0.2.15.204713 .
I"ll build android11 soon and check whether it can be flash straight over android10 without any loss.
oF2pks said:
These bugs seem fixed in today GmsCore v0.2.15.204713 .
I"ll build android11 soon and check whether it can be flash straight over android10 without any loss.
Click to expand...
Click to collapse
table tap to wake dont work. viber that had problems with many custom roms, works ok