Since everyone kept asking and I myself wanted it, I decided to start this project. The main reason why I didn't do it earlier was because I needed Asus to release the Oreo build already so I could get the required files. So for now I leave you with this, hope I made your day a bit better and have a great day!
Note: the build you see here is just so I could get the compiler working.
Sweet!! Looking forward to seeing the progress on this.
Nice. Do you think the build will have camera quality issues though?
kekley said:
Nice. Do you think the build will have camera quality issues though?
Click to expand...
Click to collapse
We'll see once I get a debuggable build running. I hope it's smooth sailing, but I can't guarantee anything.
First build?
Is this the first build?
If you want tester I am always available.
Naman Vashishth said:
Is this the first build?
If you want tester I am always available.
Click to expand...
Click to collapse
Nice to hear that you want to test the rom, but unfortunately I still don't have a flashable build. I try to work on it whenever I can to get one out as soon as possible. Do keep in mind I do this in my free time when I'm not busy with school. When I do get a debuggable build out, I'll let this forum know so I can get some testers to test it out (other than myself).
+)KEV1N(+ you are a savior , please help us get rid this sick twisted ASUS stock firmware , it's a mess in every aspect , heat, poor battery life, muffled sound via headphones, enormous amount of services running in the background (loses 20% overnight), complete failure in both firmware and kernel wise cause they massively overclocked that S625 , i can live with a rom without the main camera app , OpenCam will do just fine , just take care of that power consumption please cause on paper it should deliver 12-16h SOT , it's 5000mah with s625 and AMOLED screen for god sake !
Thank you in advance for your effort.
Kevin,
Thanks so much for taking on this project!
Not many have the skills or time to do a project like this. I think I can speak for all Z3Z owners when I say that your work will not go unappreciated.
I am simply observing the work of the gentlemen, let us continue in this to create a lineage.
rinampa said:
I am simply observing the work of the gentlemen, let us continue in this to create a lineage.
Click to expand...
Click to collapse
It is a slow process, especially since this is my daily driver. I just came back from holidays back home and now I'll continue to work on it whenever I get the chance. I'll get a working test build running eventually. Can't guarantee when, just know that as a new developer it'll take time to fix things and put them in place since porting is also not easiest of projects.
I visit this thread multiple times a day, it gives me hope)
Thank u Sir
I'm grateful that you are working on this project.
Take your time & carry on.
I want do downgrade form Oreo to MM, Q: will i need to extract recovery.img form MM zip and flash it separately or the stock Oreo recovery will work with all raw asus builds ?
Build# : ww-11.41.87.2 this is the latest MM update before Nougat update, i'm a little confused cause every build has it's own method so any advice for the safest fastest way to :
1-Downgrade to MM from Oreo
2-Flash Magisk to root and install greenify , viper4android cause i'm done with this Oreo.
3-Do i need to unlock the bootloader ?
4-Do i need twrp to flash migisk?
5-Does twrp work with all versions of android ?
3-What are the cons of this procedure if a custom ROM would fall from heaven and i would want to flash it after i flash MM?
sam.fisher190 said:
I want do downgrade form Oreo to MM, Q: will i need to extract recovery.img form MM zip and flash it separately or the stock Oreo recovery will work with all raw asus builds ?
Build# : ww-11.41.87.2 this is the latest MM update before Nougat update, i'm a little confused cause every build has it's own method so any advice for the safest fastest way to :
1-Downgrade to MM from Oreo
2-Flash Magisk to root and install greenify , viper4android cause i'm done with this Oreo.
3-Do i need to unlock the bootloader ?
4-Do i need twrp to flash migisk?
5-Does twrp work with all versions of android ?
3-What are the cons of this procedure if a custom ROM would fall from heaven and i would want to flash it after i flash MM?
Click to expand...
Click to collapse
Guess what !!!
https://forum.xda-developers.com/ze...nbrick-flash-stock-mm-asus-zenfone-3-t3840702
Its more than 100days now since this "little something" post.
Is there any progress dear KEVIN?
or shall I switch to some other device?
Aditya Tiple said:
Its more than 100days now since this "little something" post.
Is there any progress dear KEVIN?
or shall I switch to some other device?
Click to expand...
Click to collapse
I started at the end of my school year a couple of months back. I had a month-long hiatus in July due to me going back to my family back home. I came back in August and am working on it as a side project. Naman's helping me with this right now and so far we got till the boot animation. And then you have those times when we fix something and you go one step back. It's a slow process since the two of us aren't like 24/7 busy on the project. I usually work on it during weekends, but lately I've been needing my phone more and more since I'm very very busy with other priorities. Again, this is a side project I'm doing because I like coding and I like learning new things. So, I can't say for certainty when we can get a release out, but I work eagerly every time hoping it gets past the boot animation or even gets there if I fix something.
I hope this clears out any misconceptions you may have of me and this project. Have a further great day sir
It's nice to hear from you.
That's d very reason I visit this thread.
Keep ur good work going.
Keep us updating.
All d best
Hello mate, you know the whole world is waiting for this build from xda to 4pda to every other android community so what's the news my friend? can you post the bugs maybe we can help with some of them and learn about the Lineage route you chose.
The midterm examination is about to start and you'll be too busy with the study!
My full appreciation to your work.
Instead of quenching our thirst, op made it worse... Shame no developer decided to code for this device.
Mrkblo said:
Instead of quenching our thirst, op made it worse... Shame no developer decided to code for this device.
Click to expand...
Click to collapse
There is a developer who is willing to port lineage if people will crowdfund the purchase of a Z3Z for them.
https://forum.xda-developers.com/zenfone-3-zoom/help/search-developer-custom-rom-t3793680/page2
Related
"The G2 Dream Team" (and they well deserve that name) has released not one, but TWO lollipop builds for the LG G2. Both ROMs are based on the same build tree, but one ROM is CM12 and the other is a LiquidSmooth 4.0 ROM. Despite being built from the same build tree, they carry different features. They are stable and usable for daily drivers, but they may carry some bugs, like a non-functional video playback, NFC issues for LS/VS980 but it should all be sorted out in the near future. Head over to the threads to read more!:
Liquidsmooth 4.0:
http://forum.xda-developers.com/lg-g2/development/rom-liquidsmooth-v4-0-lg-g2-t2948395
CM12:
http://forum.xda-developers.com/lg-g2/development/rom-cyanogenmod-12-0-lg-g2-t2944269
Older posts:
An increasing amount of devices have been receiving unofficial Android Lollipop 5.0 ports, like the HTC One M8 and the LG Optimus L9. Today another device can be added to the list of phones receiving a treatment with the taste of Android Lollipop, the LG G2. While there generally has been a wide contribution from the community; testing, sharing files and giving ideas, two XDA members stood out in particular in order to create the build, @ylukasy and @InfinitusDesigner. The port is still in a very early pre-alpha stage, and the bugs are barely known yet, but the ROM boots and has even been rooted! While it might be wisest to wait until an official thread has been made before grabbing your devices and start flashing, @ylukasy has already provided a download link for the ROM, and calls for people to help discover the bugs so that they can be eliminated. Please notice that the ROM might not be stable enough to be used as a daily driver, but owners of a LG G2 are officially an important step closer to having a stable Lollipop ROM!
If this post caught your interest and you're willing to take the risk, head over to the last pages in the following thread: http://forum.xda-developers.com/lg-g2/general/unofficial-cm12-nexus-5-posted-t2936398
As previously mentioned, a lot of things are not sorted out yet, and the build might not be for your device number, so make sure you read the entire thread before continuing, or simply wait untill an official thread is made.
Update:
An official thread has been posted and it can be found by following this link: http://forum.xda-developers.com/lg-g2/development/rom-android-lollipop-fast-clean-t2941922
The build is a port of the Nexus 5 ROM, and users of the ROM have been saying that the rom is very fast and fluid, calls work, camera works (although the quality is inferior), but other users have been reporting random reboots and incompatibilities with certain apps such as YouTube or WhatsApp.
by vPro97
This post will be updated regularly when new information regarding Lollipop ports surface.
Fantastic News! Will get round to trying it shortly, thanks for the link!
While I have my doubts about it being functional (or even booting) on my LS980, I'll give it a shot and see what happens.
Nice to see things moving at breakneck speeds these days.
On a side note, I just read the AnandTech review of the Nexus 6 and am happy to report that my well over a year old G2 beats it in several benchmarks so I'm pretty satisfied at the moment, especially considering I got it for free. I mean really...
In before "no build for xxxx?!?!?!?"
Anyone know how to port a d802 rom to d800?
Ready to try it out and see what happened..??
his build is from the same source the other was he doesn't deserve credit for it. it's using cm12 kernel and dev claims it's using nexus 5 port yet requires gapps and no signs of any nexus 5 code at all.
Wouldn't it be alot easier to just post the download link here?
₪LG G2₪
Zyner said:
Wouldn't it be alot easier to just post the download link here?
₪LG G2₪
Click to expand...
Click to collapse
It's not my work, and there are some steps which must be followed in order to make it work. I am just objectively informing any news regarding Android Lollipop for the LG G2.
OP has been updated.
The download link was removed before i could get the v3 version so im stuck with v2 and ive been using it as my daily (yeah it reboots every 5 minuets and i can leave wifi on or it will bootloop) But honestly thats the fun in testing this stuff out
MrNegative370 said:
The download link was removed before i could get the v3 version so im stuck with v2 and ive been using it as my daily (yeah it reboots every 5 minuets and i can leave wifi on or it will bootloop) But honestly thats the fun in testing this stuff out
Click to expand...
Click to collapse
Me too.
Is there anyone that can share privately the V3 version with me ? :fingers-crossed:
here is something better:
http://forum.xda-developers.com/lg-g2/development/rom-cyanogenmod-12-0-lg-g2-t2944269
Jam4l said:
here is something better:
http://forum.xda-developers.com/lg-g2/development/rom-cyanogenmod-12-0-lg-g2-t2944269
Click to expand...
Click to collapse
TY !
Can anyone port the Nexus 5 ROM?
Updating this thread later today if nothing gets in the way.
Hi everybody!!
I need a tester please:
I built pure AOSP for the D802 from sources of Android right now, has anybody time to test it?
It is an experimental build and I didn't test it right now, so I don't know if it is working, please make a backup from your current rom.
The build comes with an built in CWM recovery and should be with root access. It can be flashed with the same instructions like the CM 12 build.
Edit: Bootloop right now ... Anybody, can you take a logcat?
http://builds.hubdroid.com/otherroms/aosp_d802-ota-102.zip
Thank you in advance!! Please anybody who tries it: can you send me a pm?
Flo0008 said:
Hi everybody!!
I need a tester please:
I built pure AOSP for the D802 from sources of Android right now, has anybody time to test it?
It is an experimental build and I didn't test it right now, so I don't know if it is working, please make a backup from your current rom.
The build comes with an built in CWM recovery and should be with root access. It can be flashed with the same instructions like the CM 12 build.
http://builds.hubdroid.com/otherroms/aosp_d802-ota-102.zip
Thank you in advance!! Please anybody who tries it: can you send me a pm?
Click to expand...
Click to collapse
I'd love to test this for you, but I'm on Sprint LS980 Would you mind making a build for us?
iamterence said:
I'd love to test this for you, but I'm on Sprint LS980 Would you mind making a build for us?
Click to expand...
Click to collapse
Yes sure, but right now, I have to solve the bug, that the d802 wouldnt boot, so this may take some more time until I build it for other devices too.
Regards
Hi guys. I want to install a custom ROM on my Grand Quattro. But when i looked at them, I found out that moste are just interface improvements, without actual OS update. What's the problem here? The GQ's bootloader haven't been unlocked yet? Can't any ROM be ported? There is really no actual android update for this device?
Thanks already!
First of all, you should know a few things about Samsung.
1. They dont lock the bootloader, that's one of the reasons they're easy to deal and twiddle with. (The branded, carrier ones although however do, as they're Carrier property)
2. Their in-house processors, the Exynos family, have no documentation on how their built. meaning, developers cannot base their work correctly and have to go trial-and-error reverse engineering, it takes **** loads of time.
3. They don't give a single crap about their low-use phones and barely update them. The last update is a Jelly Bean release that is older then a year.
There is no space to criticize the devs for custom roms. They tried AOSP with no luck on reverse-engineering.
The only critic you can shoot is that the latest Stock ROM is not being used as a base.
PlutoDelic said:
First of all, you should know a few things about Samsung.
1. They dont lock the bootloader, that's one of the reasons they're easy to deal and twiddle with. (The branded, carrier ones although however do, as they're Carrier property)
2. Their in-house processors, the Exynos family, have no documentation on how their built. meaning, developers cannot base their work correctly and have to go trial-and-error reverse engineering, it takes **** loads of time.
3. They don't give a single crap about their low-use phones and barely update them. The last update is a Jelly Bean release that is older then a year.
There is no space to criticize the devs for custom roms. They tried AOSP with no luck on reverse-engineering.
The only critic you can shoot is that the latest Stock ROM is not being used as a base.
Click to expand...
Click to collapse
thank you sir for this explanation i finally understand the reason why no developer could do this ..
karedo said:
thank you sir for this explanation i finally understand the reason why no developer could do this ..
Click to expand...
Click to collapse
Try mete mod rom man nice rom
Sir how to install custom rom
NEED HELP
Hello guys, I'm working on a generic tree for our beloved device Honor 7, but not getting enough success, so each and every of you are invited to help me create a new device tree for AOSP 5.1 ROM or CM 12.1, so that we can taste the Stock Android too.
The benefits of these ROMs are that the device will get more fast and stable as there will be minimum apps and bloatwares installed.
So, it is a humble request, that whosoever have any knowledge about creating a tree from scratch please help me.
I have created a skeleton of the tree but it is not a success too as there are many things we still have to consider.
@sminki and @kenshiwara, we will setup an organization on GitHub so everyone can contribute there only.
Hi,
It will be wonderfull to have CM on our honor7.
Sorry mate. You haven't seen my troubles over the last few weeks then
After my H7 'died', I got a warranty replacement phone, and unlocking was proving impossible, each day was bringing more frustration and anger so i've sold it!
That's it, i'm out of the "honor" business for good (hence the "unsupported" bit on the recovery and kernel threads), but as a parting "gift", here's a few things that may help "the cause".
Sorry, the length of this post got out of control! :silly:
device tree starting point:
https://github.com/TeamWin/android_device_huawei_p8 - it's similar enough, that with a little editing and boom, we had our recovery*
https://github.com/debbiche/android_device_huawei_p8 - another fuller "tree" (wip), again the p8 is similar enough to use as a base
https://github.com/Gibbon99/android_device_huawei_hwgemini - mediapad x2 - another kirin
if you're insane, you could get the dtb files (iirc - i got these from compiling the source) and decompile, but this contains EVERYTHING, theses files are huge, many hundred kb and would take days to get the info out you need (if there is any!)
cm
have a look at codeworkx H6 git, it's the closest device you'll find that has CM actually running on it, albeit CM11 (and abandoned!)
https://github.com/codeworkx/proprietary_vendor_huawei
https://github.com/codeworkx/android_device_huawei_h60-common
other things:
osm0sis' kitchen out of the many boot image unpack/repack tools, this worked the best with huawei boot/recovery images
* with this in mind, anyone running Linux can pull apart my recovery, fix the issues in default.prop, add extra partitions to fstab and repack it. then post it for everyone else to use.
with the sh!tty way fastboot is on these phones, and the way modem binaries get patched, you're going to have to look for a way to write these in recovery (scripted with dd i imagine) so that everyone can use without having the ballache that is B100,B121,B140 etc etc to get to a version that will work with your ROM. this for me is where it's all going to hurt! (and end with bricks!)
final thing - the kernel source is terrible, it is so far removed from AOSP that simple things that you could normally just drop in, like cpu governors won't work. unless you really know C++ and how to debug it's gonna be near stock (like mine funnily enough!)
Good luck chaps :good: it's gonna be a hell of a ride!
sminki said:
Sorry mate. You haven't seen my troubles over the last few weeks then
After my H7 'died', I got a warranty replacement phone, and unlocking was proving impossible, each day was bringing more frustration and anger so i've sold it!
That's it, i'm out of the "honor" business for good (hence the "unsupported" bit on the recovery and kernel threads), but as a parting "gift", here's a few things that may help "the cause".
Sorry, the length of this post got out of control! :silly:
device tree starting point:
https://github.com/TeamWin/android_device_huawei_p8 - it's similar enough, that with a little editing and boom, we had our recovery*
https://github.com/debbiche/android_device_huawei_p8 - another fuller "tree" (wip), again the p8 is similar enough to use as a base
https://github.com/Gibbon99/android_device_huawei_hwgemini - mediapad x2 - another kirin
if you're insane, you could get the dtb files (iirc - i got these from compiling the source) and decompile, but this contains EVERYTHING, theses files are huge, many hundred kb and would take days to get the info out you need (if there is any!)
cm
have a look at codeworkx H6 git, it's the closest device you'll find that has CM actually running on it, albeit CM11 (and abandoned!)
https://github.com/codeworkx/proprietary_vendor_huawei
https://github.com/codeworkx/android_device_huawei_h60-common
other things:
osm0sis' kitchen out of the many boot image unpack/repack tools, this worked the best with huawei boot/recovery images
* with this in mind, anyone running Linux can pull apart my recovery, fix the issues in default.prop, add extra partitions to fstab and repack it. then post it for everyone else to use.
with the sh!tty way fastboot is on these phones, and the way modem binaries get patched, you're going to have to look for a way to write these in recovery (scripted with dd i imagine) so that everyone can use without having the ballache that is B100,B121,B140 etc etc to get to a version that will work with your ROM. this for me is where it's all going to hurt! (and end with bricks!)
final thing - the kernel source is terrible, it is so far removed from AOSP that simple things that you could normally just drop in, like cpu governors won't work. unless you really know C++ and how to debug it's gonna be near stock (like mine funnily enough!)
Good luck chaps :good: it's gonna be a hell of a ride!
Click to expand...
Click to collapse
Thanks, this will help enough and I was not aware of your troubles
I got a device tree working with CM12.1 and USB debugging, but Mali was a showstopper. Now I'm fighting with CM13 instead... Generally, the B313 ROM is far less hacky, but we lose the open source kernel for a while until they release one.
I will set up a GitHub tree with what I have when I get CM13 compiling again, however keep in mind that you need to patch the boot.img manually to use the closed-source B313 kernel until Huawei releases the source for that, which probably won't happen at the very least until it's fully in OTA. I'd love some help from someone who is more experienced, especially with the Mali drivers which are the worst of pains.
EDIT: I got CM13 compiling again. Let's hope for the best.
EDIT2: Mali works! Sadly, that currently depends on Huawei's libgui.so which brings in a huge chunk of Huawei's patched libraries - otherwise, it segfaults in strange places. Any ideas?
Is there any whatsapp group of honor 7.I want to join it.
udayraj99 said:
Is there any whatsapp group of honor 7.I want to join it.
Click to expand...
Click to collapse
Stop spamming
Omg I think I will never receive a Custom ROM for PLK-UL00 as they didn't release source code for that and device tree is way far
Mee too
omkarpranavxxx said:
Omg I think I will never receive a Custom ROM for PLK-UL00 as they didn't release source code for that and device tree is way far
Click to expand...
Click to collapse
As an indian user evwn i feel i made wrong choice....should have gone for one plus x
asiekierka said:
I got a device tree working with CM12.1 and USB debugging, but Mali was a showstopper. Now I'm fighting with CM13 instead... Generally, the B313 ROM is far less hacky, but we lose the open source kernel for a while until they release one.
I will set up a GitHub tree with what I have when I get CM13 compiling again, however keep in mind that you need to patch the boot.img manually to use the closed-source B313 kernel until Huawei releases the source for that, which probably won't happen at the very least until it's fully in OTA. I'd love some help from someone who is more experienced, especially with the Mali drivers which are the worst of pains.
EDIT: I got CM13 compiling again. Let's hope for the best.
EDIT2: Mali works! Sadly, that currently depends on Huawei's libgui.so which brings in a huge chunk of Huawei's patched libraries - otherwise, it segfaults in strange places. Any ideas?
Click to expand...
Click to collapse
Hello, did any of the CM compiled fully to be a flashable zip? if yes, then have you flashed it and took logcat?
Nishadan said:
As an indian user evwn i feel i made wrong choice....should have gone for one plus x
Click to expand...
Click to collapse
Yup lesson learnt snapdragon or nothing frm now on
maybe you know
I post link - http://download-c.huawei.com/downlo...oadId=62086&version=204465&siteCode=worldwide
Honor 7 Open Source（PLK-L01_Android5_0_2_EMUI3_1_kernel_EN)
Any progress?
I hope I can do something,it is nice to see cm for honor 7.
Since it has been a while that any Info came out of this thread I have to ask.. Is anyone still working the tree?
I normaly do not ask for etas but in this case it would be useful if the thread is abandoned that we could know the reasons and Problems so maybe someone else could join in with a different approach
cycovision said:
Since it has been a while that any Info came out of this thread I have to ask.. Is anyone still working the tree?
I normaly do not ask for etas but in this case it would be useful if the thread is abandoned that we could know the reasons and Problems so maybe someone else could join in with a different approach
Click to expand...
Click to collapse
I'm a bit busy to continue my work on the tree, but after my exams I will continue to work on tree with Android 6.0 source. Hope it goes well.
DigiGoon said:
I'm a bit busy to continue my work on the tree, but after my exams I will continue to work on tree with Android 6.0 source. Hope it goes well.
Click to expand...
Click to collapse
good luck with your exams
Until then you can use this
New ROM for Honor 7 PLK-L01.
DigiGoon said:
Until then you can use this
New ROM for Honor 7 PLK-L01.
Click to expand...
Click to collapse
Can we get a kitkat rom if your work with the device tree is done ? I really do miss kitkat[emoji20]
Sent from my PLK-TL01H using XDA-Developers mobile app
muhammad Shohayeb said:
Can we get a kitkat rom if your work with the device tree is done ? I really do miss kitkat[emoji20]
Sent from my PLK-TL01H using XDA-Developers mobile app
Click to expand...
Click to collapse
I will be developing AOSP 6.0, if others can give it a try then maybe we can get it.
I just ask why is that there is no new updates for the roms or new roms especially with Oreo. Is the development for this phone is dead, just asking , or still hope, so maybe I can change to another phone. Thx in advance
hooksha said:
I just ask why is that there is no new updates for the roms or new roms especially with Oreo. Is the development for this phone is dead, just asking , or still hope, so maybe I can change to another phone. Thx in advance
Click to expand...
Click to collapse
It's not dead.
Custom Oreo is working completely, except for Enforcing Selinux. That will also be fixed in the future but @erfanoabdi is sadly the only one who is actually trying to get Oreo on the Moto Z and he is most likely busy with his life.
Besides, official Oreo is around the corner, we can then use its blobs to optimize custom roms based on Oreo.
I am using ElixiumOS(Oreo) and I can say that I couldn't be happier since I don't give a damn about Selinux being set to Permissive. The battery life has been doubled with Oreo(from one day of use to two full days).
Just found a link of a absolutely usable ROM for the N6P - here's the Android Open Sources illusion Projects's latest build (not my work!) which I couldn't find anywhere else, nor any discussion about it.
Posting this only reflects only my deepest appreciation about this work!
If I was blind to not see the corresponding thread I'm sorry!
(Then go ahead and please delete this if any concerns arise, just happy to see work on this almost forgotten devices...)
AOSiP-11-Ravioli-angler-20210311-1938.zip | by voidz-maguro for Nexus 6P
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Enjoy!
GAPPS can be easily found for 11 via Google, I found a nice project on XDA actually, it offers perfect support...
Suggestion from my side:
[Android 13] [GApps] NikGApps [ARM64]
Hi Everyone, Here I'd like to Introduce you with my custom Gapps package that I use on day to day basis when I flash a new Rom. As I've observed many people struggling with finding the correct version of gapps to flash, I decided to build a...
forum.xda-developers.com
Sorry if I did wrong posting this, it's just pure happiness for the community of N6P users!!!
I flashed dirty on RROS 10 with great results! (Edit: flashed clean later on, just to be sure)
My appreciation for this stable 11 build! Let's hope for more good stuff being on the way!
Thanks
Looks great and luv the name Ravioli! Cheers
Sam Nakamura said:
Just found a link of a absolutely usable link for the Android Open Sources illusion Projects's latest build (not my work!) which I couldn't find anywhere else, nor any discussion about it.
Posting this only reflects only my deepest appreciation about this work!
If I was blind to not see the corresponding thread I'm sorry! Then go ahead and please delete this if any concerns arise, just happy to see work on this almost forgotten devices...
AOSiP-11-Ravioli-angler-20210311-1938.zip | by voidz-maguro for Nexus 6P
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Enjoy!
GAPPS can be easily found for 11 via Google, I found a nice project on XDA actually...
Sorry if I did wrong, it's just pure happiness for the community of N6P users, I flashed dirty on RROS 10 with great results!
My appreciation for this stable 11 build! Thanks
Click to expand...
Click to collapse
Love this ROM, thanks to @voidz777 for building "THE ONLY STABLE ANDROID 11 ROM" for 6p at the moment, looking forward to updates on it.
Rom is good but not 100% stable..it has minor bugs such as hotspot is turning off within 10-15 minutes everytime and also phone is charging very slowly..other than that it's stable
Aditya kukreti said:
Rom is good but not 100% stable..it has minor bugs such as hotspot is turning off within 10-15 minutes everytime and also phone is charging very slowly..other than that it's stable
Click to expand...
Click to collapse
I don't use hotspot that much, but for charging issue what i did is i managed to lower down some clock cores and it works just fine without any isse with less heat
New update is up! Thanks @voidz777 for fresh stable update
Works nicely
A few hickups here and there. Did anyone get the smart controls to work?
I am missing the option to add controls, not sure if that is an ASOP thing or something else.
as @Ata Ur Rehman already said, there has been a new update (May 26th), which can be found here:
AOSiP-11-Ravioli-angler-20210526-0638.zip | by voidz-maguro for Nexus 6P
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Also here is the .txt file with a message from @voidz777 (or voidz-maguro):
"I have been interested in other hobbies since March and left 6P alone.
In Japan, the rainy season starts in June and I can only work at home.
Probably I will play with angler for a while.
For the time being, I synced to the May source of aosip.
Device modification corresponds to drm (L3).
selinux is parmissive without change. Because it is very time-consuming to make it enforce. It will take a little longer.
Camera fix? I can't. Find a camera app that you can use without problems.
Even with this, I will spend a lot of time trying in my own way.
Is English strange? It's because of Google Translate.
I want to spend more time on other things than spending time translating into English."
Click to expand...
Click to collapse
本当にありがとうございます (Thanks a lot)
There are admins who make me stupid on the Telegram channel, so I'm not motivated to do anything about angler. Please ask developers other than me that you like to develop angler.
I also gave the device to a friend.
From now on, I'm not involved with angler anymore.
voidz777 said:
There are admins who make me stupid on the Telegram channel, so I'm not motivated to do anything about angler. Please ask developers other than me that you like to develop angler.
I also gave the device to a friend.
From now on, I'm not involved with angler anymore.
Click to expand...
Click to collapse
I am sorry to hear that. And everybody does what they can ^^
I am only temporarily (hopefully) using angler, and for that your ROM is more than awesome to use.
Thanks again and much success on whatever else you are doing.
Amazing job keeping the Angler alive with this ROM. Been using this for a few weeks now.
Ata Ur Rehman said:
"THE ONLY STABLE ANDROID 11 ROM" for 6p
Click to expand...
Click to collapse
Is this still the case or have more options appeared by now?
Sorry, I haven't been following the scene for a while.
I have the problem when I try to flash the ROM , it send the error (Failed to Mount /Vendor (no such device)
Anyone knows how to fix it ???
tonyfierros said:
I have the problem when I try to flash the ROM , it send the error (Failed to Mount /Vendor (no such device)
Anyone knows how to fix it ???
Click to expand...
Click to collapse
Try flashing vendor image manually before flashing the ROM.
Same here. Which vendor image should be flashed?
Could somebody give a step by step advise how to do a clean flash with this ROM, pls?
Thanks.
raubo said:
Same here. Which vendor image should be flashed?
Could somebody give a step by step advise how to do a clean flash with this ROM, pls?
Thanks.
Click to expand...
Click to collapse
I got it installed. The vendor error message remains but the phone is up and running. And there are no problems but one: The German Fidor bank app is not installed, because the device is said to be not compatible. Usually this message comes up if the phone is rooted. Magisk is not installed. Is the phone with this ROM rooted by itself? Any ideas?
The installation seemed to be OK. But stuck in the boot logo when booting to the system. need help.
SLo
Go to recovery and clear data and reboot.
The camera from Gapp works well, but only one is work.
I try Gcam 8.1 from BSG and the Gcam from Play Store, they work will one photo only.
BTW where did you find this ROM? I can't find any in google.
I tried searching for it and couldn't find it either???