[ROM][UNOFFICIAL][7.1.2] DirtyUnicorns for G4 Play - Moto G4 Play ROMs, Kernels, Recoveries, & Other De

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

Related

[ROM] CyanogenMod 10.1 Nightly Builds for NookColor [5/3/13]

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.

[Q] How to add the device to "lunch" menu

Hi, i'm trying to compile AOKP 4.3.1 fir htc hd2. I have downloaded the device tree, kernel, and other stuff needed. But now i wan't to compile it, and i don't have full_leo-userdebug in my menu. Any help?
lolerpro8 said:
Hi, i'm trying to compile AOKP 4.3.1 fir htc hd2. I have downloaded the device tree, kernel, and other stuff needed. But now i wan't to compile it, and i don't have full_leo-userdebug in my menu. Any help?
Click to expand...
Click to collapse
Try using a local manifest and pick up the device and kernel from another project - check out github for latest repositories for htc_leo. I found device and kernel from Evervolv's repositories. Local manifest would look something like this:
<manifest>
<project name="Evervolv/android_device_htc_leo" path="device/htc/leo" remote="github" revision="jellybean-4.3" />
<project name="Evervolv/android_kernel_htc_leo" path="kernel/htc/leo" remote="github" revision="jellybean-4.3" />
</manifest>
You might also need the vendor repository for leo, in which case add another project line to the manifest for cmhtcleo/android_vendor_htc_leo (path="vendor/htc/leo" revision="jellybean").
misterjaytee said:
Try using a local manifest and pick up the device and kernel from another project - check out github for latest repositories for htc_leo. I found device and kernel from Evervolv's repositories. Local manifest would look something like this:
<manifest>
<project name="Evervolv/android_device_htc_leo" path="device/htc/leo" remote="github" revision="jellybean-4.3" />
<project name="Evervolv/android_kernel_htc_leo" path="kernel/htc/leo" remote="github" revision="jellybean-4.3" />
</manifest>
You might also need the vendor repository for leo, in which case add another project line to the manifest for cmhtcleo/android_vendor_htc_leo (path="vendor/htc/leo" revision="jellybean").
Click to expand...
Click to collapse
I have them all installed dude, i just don't have *it* in my lunch menu
Apologies for the post above if it's teaching granny to suck eggs - I only realised after I posted that you were more experienced; and also that you're using AOKP (I wrongly read it as AOSP).
---------- Post added at 08:45 PM ---------- Previous post was at 08:41 PM ----------
lolerpro8 said:
I have them all installed dude, i just don't have them in my lunch menu
Click to expand...
Click to collapse
Okay, I see - in my case, I tend to use brunch to do a build when in this scenario - I don't pick from a menu, e.g.
breakfast leo
brunch leo
(My use case is not leo though!)
misterjaytee said:
Apologies for the post above if it's teaching granny to suck eggs - I only realised after I posted that you were more experienced; and also that you're using AOKP (I wrongly read it as AOSP).
---------- Post added at 08:45 PM ---------- Previous post was at 08:41 PM ----------
Okay, I see - in my case, I tend to use brunch to do a build when in this scenario - I don't pick from a menu, e.g.
breakfast leo
brunch leo
(My use case is not leo though!)
Click to expand...
Click to collapse
It can't find it, seas i don't have right repo manifest. Is it possible to manualy add it by modifying files?
lolerpro8 said:
It can't find it, seas i don't have right repo manifest. Is it possible to manualy add it by modifying files?
Click to expand...
Click to collapse
Sorry, I haven't done an AOKP build, but from what I can tell it's similar to CM:
. build/envsetup.sh
brunch leo
I might try AOKP as my next build to see what the difference is in the build experience.
lolerpro8 said:
Hi, i'm trying to compile AOKP 4.3.1 fir htc hd2. I have downloaded the device tree, kernel, and other stuff needed. But now i wan't to compile it, and i don't have full_leo-userdebug in my menu. Any help?
Click to expand...
Click to collapse
Have you added your device in the vendor/aokp/vendorsetup.sh?
Roladriz said:
Have you added your device in the vendor/aokp/vendorsetup.sh?
Click to expand...
Click to collapse
Nope. Thank I will try that.
Sent from my NexusHD2 using xda app-developers app
As well as adding to the vendorsetup.sh file, you'll need to copy/create the <device>.mk in the vendor/aokp/products folder. You may also need to edit the device.mk file (e.g. change full to aokp).
AOKP on TF201 built
Thanks for the inspiration - I've now built AOKP on the Android Transformer Prime (TF201) and installed it successfully on the device
Just need to add some apps and see if AOKP is any good compared to CM :fingers-crossed:
Adding target to the Lunch-menu
misterjaytee said:
Apologies for the post above if it's teaching granny to suck eggs - I only realised after I posted that you were more experienced; and also that you're using AOKP (I wrongly read it as AOSP).
---------- Post added at 08:45 PM ---------- Previous post was at 08:41 PM ----------
Okay, I see - in my case, I tend to use brunch to do a build when in this scenario - I don't pick from a menu, e.g.
breakfast leo
brunch leo
(My use case is not leo though!)
Click to expand...
Click to collapse
Hello, You mentioned pulling the repository with your local manifest. I managed to do so and I have the correct vendor android.mk, blob, and proprietary information; however, I can't seem to figure out how to add them to the lunch-menu through the vendorsetup.sh script. Could you explain what you mentioned earlier?
(I'm working with Samsung Galaxy Note 4 SM-N910T - codename trlte)
I have tried to google this question as well and that`s what I can say: you have to extract the device blobs, you`d better check up the tutorial on how to do it

[ROM][DEV][4.4][UNOFFICAL] CM11 Development Project

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

[ROM][6.0.1][Unofficially | CM13.0 For Huawei Ascend G760] [2016-04-01]

/*
* 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.
*
*/
local manifest
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remove-project name="CyanogenMod/android_packages_apps_CMUpdater" />
<project name="mparus/android_device_huawei_g760-caf" path="device/huawei/g760" revision="master" />
<project name="mparus/android_kernel_huawei_msm8916-caf" path="kernel/huawei/msm8916-caf" revision="g760_sensors" />
<project name="mparus/android_vendor_huawei_g760-caf" path="vendor/huawei/g760" revision="master" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" revision="cm-13.0" />
</manifest>
Devs :
@surdu_petru
@desalesouche
@dianlujitao
Bob the Builder - @mparus
Downloads:
https://www.androidfilehost.com/?w=files&flid=51281
Not working: any bugs?
Latest build:
cm-13.0-20160430-UNOFFICIAL-mparus-g760.zip
https://www.androidfilehost.com/?fid=4996503000517181848
for changes, see cm-13.0 changelog
Previous builds:
cm-13.0-20160406-UNOFFICIAL-mparus-g760.zip
https://www.androidfilehost.com/?fid=24459283995314422
fix torch, fm radio sound, mic volume in recorder, incall volume set, latest security patch
cm-13.0-20160405-UNOFFICIAL-mparus-g760.zip
https://www.androidfilehost.com/?fid=24459283995313611
nothing special - cyanogen changes and little sound changes
maybe better battery life in doze mode
cm-13.0-20160404-UNOFFICIAL-mparus-g760.zip
https://www.androidfilehost.com/?fid=24459283995312509
fix f2fs
cm-13.0-20160403-UNOFFICIAL-mparus-g760.zip
https://www.androidfilehost.com/?fid=24459283995312201
latest cyanogenmod changes, add call recording, f2fs /data filesystem support, also previous audio fixes
cm-13.0-20160401-UNOFFICIAL-mparus-g760.zip
https://www.androidfilehost.com/?fid=24459283995310081
add cm13 changes, add trim settings to build.prop, fix headphones audio out, fix handset-mic sensitive, fix audio in Music Player, fix handset volume
XDA:DevDB Information
[ROM][6.0.1][Unofficially | CM13.0 For Huawei Ascend G760], ROM for the Huawei Ascend G7
Contributors
mparus
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Stable
Created 2017-02-01
Last Updated 2017-02-01
Some bugs?
Oh great, looking forward to getting your working.
Sent from my HUAWEI G760-L01 using Tapatalk
Thanx for your hardwork but I don' t hearing music in Music Player.
Eduardo58 said:
Thanx for your hardwork but I don' t hearing music in Music Player.
Click to expand...
Click to collapse
Yes, I upload new version with fix.
mparus said:
Yes, I upload new version with fix.
Click to expand...
Click to collapse
Thanx! You are an awsome developer! But when I took picture, it was become inverse in build 30032016. What can I do?
Yesterday I had a problem with the battery indicator in the version.
Notification bar in 80 % , 78% in recovery.
'll try to release you today released.
follow you
Eduardo58 said:
Thanx! You are an awsome developer! But when I took picture, it was become inverse in build 30032016. What can I do?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24459283995310081
New build bug :
hardwork but I don' t hearing music in Music Player and Olay Music.
But Poweramp sound coming
freeforce said:
New build bug :
hardwork but I don' t hearing music in Music Player and Olay Music.
But Poweramp sound coming
Click to expand...
Click to collapse
you download cm-13.0-20160401-UNOFFICIAL-mparus-g760.zip with this md5 sum 6ecfe26db9d3101837b7b9cd46ef7723 ?
mparus said:
you download cm-13.0-20160401-UNOFFICIAL-mparus-g760.zip with this md5 sum 6ecfe26db9d3101837b7b9cd46ef7723 ?
Click to expand...
Click to collapse
Yeah, I installed version. Sound comes only with poweramp
When he pulled horizontal image looks inverted image.
No sound on calls with a headset.
I encountered these errors now
freeforce said:
Yeah, I installed version. Sound comes only with poweramp
When he pulled horizontal image looks inverted image.
No sound on calls with a headset.
I encountered these errors now
Click to expand...
Click to collapse
for audio - replace mixer_paths_qrd_skuh.xml in /system/etc/ from attchments
Do I have to make any changes to install on L-03?
Enviado desde mi unknown mediante Tapatalk
mparus said:
for audio - replace mixer_paths_qrd_skuh.xml in /system/etc/ from attchments
Click to expand...
Click to collapse
My English is not good. I did not understand
freeforce said:
My English is not good. I did not understand
Click to expand...
Click to collapse
My also
copy mixer_paths_qrd_skuh.xml file to the phone - to catalog /system/etc/
reboot phone
check audio
mparus said:
My also
copy mixer_paths_qrd_skuh.xml file to the phone - to catalog /system/etc/
reboot phone
check audio
Click to expand...
Click to collapse
File can not be downloaded.
Do you copy the writings
freeforce said:
File can not be downloaded.
Do you copy the writings
Click to expand...
Click to collapse
Kardeşim dosya üzerine gelip sağ tıkla ve ''Farklı kaydet'' e bas.
В голове голове здравствуйте шаг..
Отправлено с моего G760-L01 через Tapatalk
mparus said:
for audio - replace mixer_paths_qrd_skuh.xml in /system/etc/ from attchments
Click to expand...
Click to collapse
No change with your xml attachement. My voice in call not heared by contact
Sent from my G760-L01 using Tapatalk
sajadzare said:
No change with your xml attachement. My voice in call not heared by contact
Sent from my G760-L01 using Tapatalk
Click to expand...
Click to collapse
I dont understand you. You use headset microphone? Handset microphone?
Sent from my G760-L01 using Tapatalk

[AOSP 10.0_r40][all-in-one] microG ufOfficial (cve Aug, 2020) arm32/64

[10.0_r40/v222] download : https://androidfilehost.com/?a=show&w=files&flid=286761​All-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

Categories

Resources