As everyone knows mokee official release uses a old kernel build from month of may, while the latest kernel is from sept. So I have made a repack of the latest kernel. As far my primary tests everything is working so just flash it and enjoy the latest one, incase xiaomi updates their kernel and anyone uses it but mokee, I will repack again and update the thread.
Enjoy!
ps: Sorry no flashable zip available. please report any bug you may find!
Steps:
1. enable usb debugging
2. connect to pc and open adb
3. copy the downloaded boot.img file to the adb folder.
4.open cmd, navigate to adb folder and type these lines one by one.
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
5. after reboot, just copy the 2nd downlaoded file "pronto_wlan.ko" to /system/lib/modules/pronto and replace the existing file,
6. change the permission to rw-r-r
7. reboot and enjoy the latest kernel.
If anyone can make a twrp/cwm flashable zip, you can share here.
Download
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thnx to the help from
kapil.git
Thanks for the Wake Up!!
saurabhrck said:
As everyone knows mokee official release uses a old kernel build from month of may, while the latest kernel is from sept. So I have made a repack of the latest kernel. As far my primary tests everything is working so just flash it and enjoy the latest one, incase xiaomi updates their kernel and anyone uses it but mokee, I will repack again and update the thread.
Enjoy!
ps: Sorry no flashable zip available. please report any bug you may find!
Steps:
1. enable usb debugging
2. connect to pc and open adb
3. copy the downloaded boot.img file to the adb folder.
4.open cmd, navigate to adb folder and type these lines one by one.
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
5. after reboot, just copy the 2nd downlaoded file "pronto_wlan.ko" to /system/lib/modules/pronto and replace the existing file,
6. change the permission to rw-r-r
7. reboot and enjoy the latest kernel.
If anyone can make a twrp/cwm flashable zip, you can share here.
Download
Screenshot:
thnx to the help from
kapil.git
Click to expand...
Click to collapse
deadlyindian said:
Thanks for the Wake Up!!
Good Work Brothers !!!!:laugh::laugh::laugh:
Keep it up.....:good::good::good:
But, if I am not wrong Xiaomi has not released any kernel sources and so all of our Devs are using only headers for compiling the ROM and so they are just changing the date in headers. Does this matters in performance, or stability?
Please do correct me, if I am wrong anywhere. I am always ready to learn new things.
Best Regards
BOND
Click to expand...
Click to collapse
SuperDroid-BOND said:
Good Work Brothers !!!!:laugh::laugh::laugh:
Keep it up.....:good::good::good:
But, if I am not wrong Xiaomi has not released any kernel sources and so all of our Devs are using only headers for compiling the ROM and so they are just changing the date in headers. Does this matters in performance, or stability?
Please do correct me, if I am wrong anywhere. I am always ready to learn new things.
Best Regards
BOND
Click to expand...
Click to collapse
xiaomi has not released kernel source dts right, but they are updating kernel while they update miui rom(secure source), devs are actually using that updated kernel which is made by xiaomi. Mokee on the other hand was using a old kernel and they were not updating , so I took the liberty to update it.
saurabhrck said:
xiaomi has not released kernel source dts right, but they are updating kernel while they update miui rom(secure source), devs are actually using that updated kernel which is made by xiaomi. Mokee on the other hand was using a old kernel and they were not updating , so I took the liberty to update it.
Click to expand...
Click to collapse
You did the right thing brother and thanks (I already pressed it for both of you) for keeping us updated.
So, you mean to say that Xiaomi has updated the kernel and sources but its secured only, not public. If it is like this, would you mind linking us to those sources, because there are so many ROMs waiting for some fixed kernel sources or if you can tell us what things have been fixed, can we use single SIM with this code "
Code:
setprop persist.radio.multisim.config none
".
We, all the users, can get several ROM with almost all utmost and best features available. Please do let me know about the kernel, best if we could talk on PM.
Best Regards
BOND
The Kernel gets updates by new Miui releases...i'll give a notable example to prove that !
Before v41.1 there isn't built in Zram implemented but with new kernel (v41.1+) there is Zram Support !
SuperDroid-BOND said:
You did the right thing brother and thanks (I already pressed it for both of you) for keeping us updated.
So, you mean to say that Xiaomi has updated the kernel and sources but its secured only, not public. If it is like this, would you mind linking us to those sources, because there are so many ROMs waiting for some fixed kernel sources or if you can tell us what things have been fixed, can we use single SIM with this code "
Code:
setprop persist.radio.multisim.config none
".
We, all the users, can get several ROM with almost all utmost and best features available. Please do let me know about the kernel, best if we could talk on PM.
Best Regards
BOND
Click to expand...
Click to collapse
The source is secure to xiaomi, they are not releasing to public as of now. Don't know whats the reason for this idiotic move. Anyway I don't have the source, like anyone else, I just repacked with proper module. dts all! Will update when xiaomi releases a new update
saurabhrck said:
The source is secure to xiaomi, they are not releasing to public as of now. Don't know whats the reason for this idiotic move. Anyway I don't have the source, like anyone else, I just repacked with proper module. dts all! Will update when xiaomi releases a new update
Click to expand...
Click to collapse
so is it repack of old ramdisk and new zimage... btw can u please give me link/info about the tool which u have used to repack kernel.. i tried to make kernel unsecure once but cant make it boot... kernel size reduced ~4 mb....
deadlyindian said:
Thanks for the Wake Up!!
Is no need to set permission at pronto wlan ?
Click to expand...
Click to collapse
pgreed said:
Is no need to set permission at pronto wlan ?
Click to expand...
Click to collapse
Nope its automatically set when phone boots...
What are the features of the kernel? This for mokee only? Any version??
This kernel don't work with UNOFFICIAL version of Mokee. When just install w/o wipe dalvik/cache at the middle of boot (before launching apps) phone reboot. If wipe dalvik/cache the font used to say Android update... is very small (as density is around 400dpi!!) and after app is launched phone reboot.
pgreed said:
This kernel don't work with UNOFFICIAL version of Mokee. When just install w/o wipe dalvik/cache at the middle of boot (before launching apps) phone reboot. If wipe dalvik/cache the font used to say Android update... is very small and after app is launched phone reboot.
Click to expand...
Click to collapse
ofcourse it will not work with unofficial version. unofficial version is based on cm11 source and uses that prebuilt kernel. you have to repack it separately for that. This one is only for mokee official release which uses mokee kernel/device files not from cm11, mentioned in OP!
saurabhrck said:
ofcourse it will not work with unofficial version. unofficial version is based on cm11 source and uses that prebuilt kernel. you have to repack it separately for that. This one is only for mokee official release which uses mokee kernel/device files not from cm11, mentioned in OP!
Click to expand...
Click to collapse
No it use the 8 May kernel! (is the sychost unofficial)
Shahi00 said:
The Kernel gets updates by new Miui releases...i'll give a notable example to prove that !
Before v41.1 there isn't built in Zram implemented but with new kernel (v41.1+) there is Zram Support !
Click to expand...
Click to collapse
So you mean Roms above 41.1 have zram implemented? before that it was not available?
Shahan_mik3 said:
So you mean Roms above 41.1 have zram implemented? before that it was not available?
Click to expand...
Click to collapse
Yep...even though we have 1GB RAM it is done that way !
I am very sure that V36 don't have ZRAM and V41.1 and above have it...that's the way they found to currect RAM management !
it causes a bit battery drain & and performance regression !
pgreed said:
This kernel don't work with UNOFFICIAL version of Mokee. When just install w/o wipe dalvik/cache at the middle of boot (before launching apps) phone reboot. If wipe dalvik/cache the font used to say Android update... is very small (as density is around 400dpi!!) and after app is launched phone reboot.
Click to expand...
Click to collapse
link for mokee unofficial plz..
RohanAJoshi said:
link for mokee unofficial plz..
Click to expand...
Click to collapse
Because from Mokee site was deleted all unofficial and experimental version (I dunno why) I've upload the file elsewhere:
Shahi00 said:
Yep...even though we have 1GB RAM it is done that way !
I am very sure that V36 dont have ZRAM and V41.1 and above have it...thats the way they found to currect RAM management !
it causes a bit battery drain & and performance regression !
Click to expand...
Click to collapse
Also I wanted to know. How is it possible to get a stable cm/aosp Roms on Redmi but not on mi3?
Shahan_mik3 said:
Also I wanted to know. How is it possible to get a stable cm/aosp Roms on Redmi but not on mi3?
Click to expand...
Click to collapse
Our developer is good enough for tracking bugs that causes Random Reboots !!
Kra always did that (on previous phone too)
:good:
Related
Hello There!
I am here with a good news and a bad news!
The good news is that I have sucessfully compiled TWRP recovery for our beloved Xperia M!
The bad news is that It is unstable, and I am not able to make it stable. I need help from some developers in order to make it stable.
Please note that this kernel bringup is only for CM11 FXP310.So, dont try it on other ROMs, as your may get into a serious problem after that.
Please bear with me, as I am a noob and will need a lot of help in making this stable for use!
Sources :
The TWRP sources can be found here : https://github.com/omnirom/android_bootable_recovery
The device tree of rebelos(contains commits for TWRP bringup, thanks to him for letting me use the tree) : https://github.com/rebelos/android_device_sony_nicki
The Kernel sources used : https://github.com/freexperia/android_Kernel_sony_msm8x27
Working /Not working
Working :
Normal Touch
Navigation
And Basic operations
Not - Working
Some glitches (sometimes) [that is, the half screen problem]
Screenshots(again, thanks to Bonoboo)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Downloads
New flashable zip(thanks to Bonoboo) : https://www.mediafire.com/?gg84xysk8w64fwc
OLD[not recommended for use] :
boot.img
recovery.img ( I am having problems installing this, via fastboot. Use boot.img)
Changelogs
16-03-2014
Initial Release
17-03-2014
fixed up the bugs in main ROM. i.e, the wifi and RIL bugs.
Credits :
PecanCM - For sources
FXP, for supporting this device officially
rebelos for allowing me to use his updated commits in device tree. His device tree can be found on his github.
Bonoboo for giving the idea of packing the ramdisk(the partition with recovery and the boot.img) and for packing it up for me!
A note : I need help from you all to achieve this task Please help me up.
XDA:DevDB Information
[RECOVERY] TWRP, a Tool/Utility for the Sony Xperia M
Contributors
PixCM
Version Information
Status: Beta
Current Beta Version: 1
Beta Release Date: 2014-03-17
Created 2014-03-16
Last Updated 2014-03-18
lol twrp.. just got real ..
see these commits
https://github.com/freexperia/android_device_sony_nicki/pull/1
these will fix all your issues
rebelos said:
lol twrp.. just got real ..
see these commits
https://github.com/freexperia/android_device_sony_nicki/pull/1
these will fix all your issues
Click to expand...
Click to collapse
Thank You soo much Will compile and post in an hour or so! Got to do something else at the moment
Tried.. But they didnt help :/ Same bugs!
Finally, TWRP! Thanks!
About problems with Wi-Fi and RIL – yes, it's really due compiling kernel on your side.
I extracted from your boot.img ramdisk-recovery.cpio and replaced it in kernel from latest FXP310 build – all fine.
So maybe you do the same in future for avoiding problems?
Recovery bundled in boot.img so recovery.img can't be flashed with saving current kernel.
I think better to post ramdisk-recovery.cpio so users can combine it with needed in their case kernel: stock, modded or whatever.
Here easy tutorial and tool for do these on Windows. Almost same for Linux.
Bugs:
– no mount of any partitions
– screen most time halved
– at screen timeout it don't off
Best Recovery Shown up!
TWRP just the best recovery ever... my fav.
hope this can be fixed soon... thanks for the good job
Good work bro...
Sent from my C1905 using XDA Premium 4 mobile app
Thanks mate for TWRP recovery! Always used this on my GT-I9100
Wating for an update
Sent from my C1905 using Tapatalk
Bonoboo said:
Finally, TWRP! Thanks!
About problems with Wi-Fi and RIL – yes, it's really due compiling kernel on your side.
I extracted from your boot.img ramdisk-recovery.cpio and replaced it in kernel from latest FXP310 build – all fine.
So maybe you do the same in future for avoiding problems?
Recovery bundled in boot.img so recovery.img can't be flashed with saving current kernel.
I think better to post ramdisk-recovery.cpio so users can combine it with needed in their case kernel: stock, modded or whatever.
Here easy tutorial and tool for do these on Windows. Almost same for Linux.
Bugs:
– no mount of any partitions
– screen most time halved
– at screen timeout it don't off
About screenshots.
Please hide them under spoiler – thread very lagre with them now.
Here flashable ZIP with original FXP310 kernel and this recovery.
Click to expand...
Click to collapse
Thanks dude! I will give you another build, check if the mount is working in this one!
Check your PM.
SUM ONE SAY TWRPDDDDDD goddamn, i want try it, but after the bug like wifi-RIL etc fixed
PixCM said:
Thanks dude! I will give you another build, check if the mount is working in this one! .
Click to expand...
Click to collapse
– Now all partitions mounts, switching internal/external storage ok too. Thanks!
– ADB works
– But there no option for USB Mass storage connection
– Screen still halved, affect touch too
– Screen timeout still broken
Here directly captured screenshots.
Please replace screens in first post and hide them under spoiler.
Richardsentosa said:
i want try it, but after the bug like wifi-RIL etc fixed
Click to expand...
Click to collapse
Use this flashable ZIP with original FXP310 kernel and this new version recovery. No bugs in main ROM (CM11).
Bonoboo said:
– Now all partitions mounts, switching internal/external storage ok too. Thanks!
– ADB works
– But there no option for USB Mass storage connection
– Screen still halved, affect touch too
– Screen timeout still broken
Here directly captured screenshots.
Please replace screens in first post and hide them under spoiler.
Use this flashable ZIP with original FXP310 kernel and this new version recovery. No bugs in main ROM (CM11).
Click to expand...
Click to collapse
but now i using HellKat .-.
Updated
Updated OP with new build.
Download : https://www.mediafire.com/?gg84xysk8w64fwc
Special thanks to @Bonoboo for this
@PixCM
Thanks for fixing mounts and hiding screens.
About first post.
1. There no any mention except filename of zip that kernel only for CM11 FXP310. Someone can flash it on stock and get unexpected problems.
2. Imho better remove obsolete yesterday versions because they non-functional and buggy. Just for keep all clean.
3. Direct recovery screenshots here.
BTW, in what format you planned post new versions in future: ramdisk-recovery.cpio or boot.img for CM11?
I need to know because have idea to modify repacking tool to automatically integrate your TWRP in any kernel.
Bonoboo said:
@PixCM
Thanks for fixing mounts and hiding screens.
About first post.
1. There no any mention except filename of zip that kernel only for CM11 FXP310. Someone can flash it on stock and get unexpected problems.
2. Imho better remove obsolete yesterday versions because they non-functional and buggy. Just for keep all clean.
3. Direct recovery screenshots here.
BTW, in what format you planned post new versions in future: ramdisk-recovery.cpio or boot.img for CM11?
I need to know because have idea to modify repacking tool to automatically integrate your TWRP in any kernel.
Click to expand...
Click to collapse
If I will be compiling again, then it would be in any form. You say. Which one is better? I think for people's use, its better to release in boot.img form. Or else, I will do one thing..
I will release it in both the forms.
P.S I will be updating the OP soon. In an hour or so.
And, will you become my tester? I will send you links to build through PM. I am trying to compile omni at the moment.
PixCM said:
I will release it in both the forms.
Click to expand...
Click to collapse
Yes, this will be nice and more flexible: someone can manually add recovery in beloved kernel and CM11 users can directly flash it.
PixCM said:
And, will you become my tester?
Click to expand...
Click to collapse
Recovery – yes, but not ROM, sorry.
PixCM said:
If I will be compiling again, then it would be in any form. You say. Which one is better? I think for people's use, its better to release in boot.img form. Or else, I will do one thing..
I will release it in both the forms.
P.S I will be updating the OP soon. In an hour or so.
And, will you become my tester? I will send you links to build through PM. I am trying to compile omni at the moment.
Click to expand...
Click to collapse
OmniROM with TWRP recovery is brilliant mate! Hope you will release it
Sent from my C1905 using Tapatalk
a new build? i will try it (if i flashed the FXP CM11)
Richardsentosa said:
a new build?
Click to expand...
Click to collapse
Yep, CM11 FXP311 released.
Here flashable zip with kernel from there with integrated this TWRP recovery.
Bonoboo said:
@PixCM
Thanks for fixing mounts and hiding screens.
About first post.
1. There no any mention except filename of zip that kernel only for CM11 FXP310. Someone can flash it on stock and get unexpected problems.
2. Imho better remove obsolete yesterday versions because they non-functional and buggy. Just for keep all clean.
3. Direct recovery screenshots here.
BTW, in what format you planned post new versions in future: ramdisk-recovery.cpio or boot.img for CM11?
I need to know because have idea to modify repacking tool to automatically integrate your TWRP in any kernel.
Click to expand...
Click to collapse
+1 lol... you just wrote what i want to...
now it's being clear...
coz i need to replace the whole cwm from every Roms i've downloaded... yeah... keep it rolling dude :good:
CM11 FXP312 released.
Here flashable zip with kernel from there with integrated this TWRP recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bug list:
GPS & FM
What is working:
Media (IT IS FIXED) But Youtube can be dead
Audio (IT IS FIXED)
RIL (baseband) (IT IS FIXED)
Touchscreen xD
Image decoding
MTP
Webview
Camera
Sensors
Houdini
Wi-FI
Rom features:
It was build from fresh CM12.1 source (November stagefright patch is included)
I used proprietary files from WW 3.24.40.87
I used device tree by quanganh2627 for building so this way community will get all fixes
Custom kernel which was built from X Anwar sources so it has underclock, DT2W, million governors and i/o stuff.
How to flash it:
Step 1:
You should download files for flashing:
File with CM12.1 rom:
Google Drive
ADB v1.0.32: Download from Google Drive
TWRP 2.8.7.0 recovery by quanganh2627 (new December build): Download from Google Drive
Step 2:
1) Unpack archive with ADB and put TWRP image there.
2) Copy file with rom and gapps to internal/external memory of your phone.
3) Then you should reboot your phone in the droidboot mode. (turn off you gadget then press Turn off button and volume + button)
Then go to the ADB folder and hold Shift + Right Mouse button and write this command:
Code:
fastboot flash recovery new-zen5-reco.img
Then you should reboot your phone in the recovery mode. (turn off you gadget then press Turn off button and volume - button)
Step 3:
Then you phone will reboot in the recovery. In the recovery you should instal package with rom.
Step 4:
After flashing, you should format (not wipe) data and cache in the TWRP.
Then you should reboot to system.
Bug reporting:Attach logcat and detailed describe the issue. Send this to me (tank0412)
Credits:@quanganh2627 (i used his device tree for building)
USING MY ROM AS BASE FOR YOUR ROM IS DENIED
IF YOU IGNORE IT, I WILL ASK MODERATOR TO DELETE YOUR THREAD
But you can use my kernel only without any problems.
XDA:DevDB Information
CyanogenMod 12.1 by tank0412, ROM for the Asus Zenfone 5
Contributors
tank0412
Source Code: https://github.com/tank0412/android_device_asus_a500cg-1
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Unlocked bootloader
Based On: CM
Version Information
Status: Beta
Current Beta Version: 2.3
Beta Release Date: 2016-03-16
Created 2016-01-04
Last Updated 2016-03-21
Changelog(16.03.2016):
Trying to update Stagefright patch
Re-add Google Camera
Fixing writing to external memory card using Pixelmaster Camera.
Changelog(14.03.2016):
Apply vibrator.patch by @quanganh2627
Re-add camera app
P.S. I applyed patch but i do not know is it work. (hardware of vibrator is dead on my phone)
Changelog(13.03.2016):
Camera was fixed so it can make video without any problem
More fixes for media
Changelog(12.03.2016):
Audio was fixed
Media was fixed (but you can have few troubles with Youtube)
Changelog(04.02.2016):
Using blobs files from WW V3.24.40.87
And more
Changelog(10.01.2016):
DT2W was enabled
Unsuccessful attempt to totally fix Camera
Unsuccessful attempt to fix audio & media
Anyway, i am working on it.
Changelog(06.01.2016):
Latest fixes from quanganh2627s repo were applyed (commit #b953942e748b4d88f27b202abfc318dbd49161ea)
Changelog(05.01.2016):
Using fresh CM12.1 source
Minor fixes and improvements for audio, (i built libtinycompress and libtinyalsa libs from source, but audio is stay partly dead.)
Removed trash from Asus stock (only Asus Camera is included)
A tonn tweaks by @TecnoTailsPlays was added. (commit #56f91ca1fd3dc3e58d02d48b136a97c3a62567a1 )
Chagelog(04.01.2016):
Initial release
Reserved
Hot-fixesFix of MTP:
https://drive.google.com/file/d/0B-Fin8UxrD6PZWt6UWIxQmdMT3M/view?usp=sharing
Flash it via fastboot (drodiboot)
awesome, i waiting for upload good luck tank0412
milano88 said:
awesome, i waiting for upload good luck tank0412
Click to expand...
Click to collapse
I uploaded it few minutes ago. xD
tank0412 said:
I uploaded it few minutes ago. xD
Click to expand...
Click to collapse
i started download , after finish will immediately install thanks for your work
edited:
Anyone review?
Sent from my ASUS_T00J using Tapatalk
Running on Recreated Remix Ultra 7.2
Dont know,this is the most suitable CM 12.1 based for me,after trying almost all of cm12.1 rom here.
Less freeze after few days using...
Just 3 or 4 times freeze while charging
ShuviterDjogja said:
edited:
Anyone review?
Click to expand...
Click to collapse
Just trust me.
tank0412 said:
Just trust me.
Click to expand...
Click to collapse
Always trus the dev sir
[emoji106]
Always follow the threads..
Sent from my ASUS_T00J using Tapatalk
Thanks for this. I assume this is compiled from the latest source code (as of 2016-01-03), right?
Would you mind putting this on the OP, especially when you has an update version in the future.
I haven't tried this rom, waiting for audio fixed.
One thing that I don't understand, I see other offical cm12.1 rom size is about 250MB, but why zen5 get double size?
Firstly, I thought we will get a very small minimum rom size but it seems not that much different to Asus stock (after remove bloatware).
baszu said:
Thanks for this. I assume this is compiled from the latest source code (as of 2016-01-03), right?
Would you mind putting this on the OP, especially when you has an update version in the future.
I haven't tried this rom, waiting for audio fixed.
One thing that I don't understand, I see other offical cm12.1 rom size is about 250MB, but why zen5 get double size?
Firstly, I thought we will get a very small minimum rom size but it seems not that much different to Asus stock (after remove bloatware).
Click to expand...
Click to collapse
I could not download latest CM source so it was built from October source.
Many trash from Asus stock were added by quanganh2627's device tree.
I agree that this trash must be removed.
tank0412 said:
I could not download latest CM source so it was built from October source.
Many trash from Asus stock were added by quanganh2627's device tree.
I agree that this trash must be removed.
Click to expand...
Click to collapse
why you can't download the lastest CM source ?
i wait for the bug fixed, and will download this ROM. But right now is to much CM12.1 build for Zenfone 5 so i'm confused which one i must flash on my devices.
Awesome. Hope u will build CM13
Is it really that hard to fix GPS and FM Radio for AOSP based ROMs?
I'm dying for a clean AOSP based ROM but I can't flash it in these circumstances; no audio and no GPS :/
gusbalaa said:
why you can't download the lastest CM source ?
i wait for the bug fixed, and will download this ROM. But right now is to much CM12.1 build for Zenfone 5 so i'm confused which one i must flash on my devices.
Click to expand...
Click to collapse
Threre are only THREE CM12.1 builds. First build was made by Tran Huu Tin, second build was made by KnoneNull and third build was compiled by me.
If you find build by other author, you must understand that it was not built from source. It is a just modificated build by Knone or Tran Huu Tin with a minor changes.
So it is an easy choice.
By the way, i can not download latest source due to my Internet provider. I mean i can not use repo tool to sync sources due to it.
Parliamert said:
Is it really that hard to fix GPS and FM Radio for AOSP based ROMs?
I'm dying for a clean AOSP based ROM but I can't flash it in these circumstances; no audio and no GPS :/
Click to expand...
Click to collapse
I plan to fix audio but nobody can fix GPS because Broadcom and Asus have not published enough source code for this yet.
tank0412 said:
Threre are only THREE CM12.1 builds. First build was made by Knone, second build was made by KnoneNull and third build was compiled by me.
If you find build by other author, you must understand that it was not built from source. It is a just modificated build by Knone or Tran Huu Tin with a minor changes.
So it is an easy choice.
By the way, i can not download latest source due to my Internet provider. I mean i can not use repo tool to sync sources due to it.
Click to expand...
Click to collapse
Okay thanks, so i will prepared for download your build if stable versions is released, with fixed bugs.
But what about this one ?
http://forum.xda-developers.com/showthread.php?p=63910968
tank0412 said:
Threre are only THREE CM12.1 builds. First build was made by Tran Huu Tin, second build was made by KnoneNull and third build was compiled by me.
If you find build by other author, you must understand that it was not built from source. It is a just modificated build by Knone or Tran Huu Tin with a minor changes.
So it is an easy choice.
By the way, i can not download latest source due to my Internet provider. I mean i can not use repo tool to sync sources due to it.
Click to expand...
Click to collapse
I'm confused now. Do you mean your compile is also based on Tran's and Knone's source.
If this the case, it is not different to those then.
For sync source code, do you mean your internet provider block github or it is too slow to download latest source?
If it is latter, maybe, someone can help sync source and upload it to other website?
baszu said:
I'm confused now. Do you mean your compile is also based on Tran's and Knone's source.
If this the case, it is not different to those then.
For sync source code, do you mean your internet provider block github or it is too slow to download latest source?
If it is latter, maybe, someone can help sync source and upload it to other website?
Click to expand...
Click to collapse
I denied using my build as base for other custom roms. So nobody will use my build as base for their custom rom.
My build was really compiled from CM source like Knones build or Tran Huu Tins build.
My provider block repo tool so i can not use it. If somebody upload latest CM12.1/AOSP 5.1.1 code to other website, i will download it and this way i will use it for custom rom building.
gusbalaa said:
Okay thanks, so i will prepared for download your build if stable versions is released, with fixed bugs.
But what about this one ?
http://forum.xda-developers.com/showthread.php?p=63910968
Click to expand...
Click to collapse
It is just modificated build by Knone. It was not built from source.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We are launching brand spanking fresh. All new features. New team members. New everything and we have made sure that everything that we are releasing has been polished to our best.
A lot went into this version of Paranoid Android, specially on the CAF side (OnePlus / Non-nexus devices). We ship with custom in-house kernels tweaked to provide the best power-battery combo, new functionalities and designs for hardware-specific options like the alert slider and advanced controls just for OnePlus devices - so feel pretty.
The main features and enhancements that you will probably end up noticing are our custom Quick Settings tile reordering functionality, floating window support, immersive mode, the new on-the-spot interface and CM Theme Engine. There's much more to come, so sit tight!
Feature highlights
Floating mode
Immersive mode
On-the-spot controls
Quick settings re-order
Paranoid OTA (Updates)
Battery styles
Advanced power dialog
Quick pull-down
Theme engine
CAF specifics
Enhanced kernel + control
Advanced buttons control
Ambient display support
Download
Get my latest Xiaomi Mi5 build here.
This Firmware is also required Global Beta 6.9.29 Firmware
Changelogs
As we're getting back into the thread game, keeping up with threads and updating them as per changelogs can be too hectic given our schedule. However, very detailed changelogs always go up on our Google+ page, follow us for constant updates!
For Device specific changelogs, check the second post.
Instructions & requirements
We highly recommend you to follow these instructions very carefully. Users usually tend to skip a few steps and eventually fall in trouble. Are you with me? Good. Let's get this train going.
Just a few things to keep in mind first -
If you're coming from another ROM / Stock, your system data (not internal storage) and cache will have to be wiped. This includes apps, accounts, messages, call logs etc.
There's been some users complaining about different GAPPS variants messing up installs and causing a ton of issues. Upon investigating it seems OpenGapps Mini/Nano work best.
Understand that Paranoid Android is a custom ROM and it might lead to addiction as it's relatively good. We shouldn't be accused of anything just incase your cat starts drinking wine. Things get a little woozy in the Paranoid World.
Some brain might be involved if things go wrong. Not a lot though, as much to solve what's 1+1.
Okay let's get to the main bit -
Once you have all the required files - boot into recovery and wipe the bananas out of your device. Get into the wipe menu and wipe data, system, cache and dalvik cache (basically everything except Internal Storage).
Once wiped, get into the "Install from zip" menu and select the ROM zip. (pa_gemini_6.x...). Once added to the install queue, TWRP will ask you if you want to add more zips into the queue - Click on "add more zips" and select the firmware package.
Swipe the bar on the bottom to flash/install zips. Once both zips are done installing - Reboot into system and set-up your device, after you've let it settle with screen off for about 10 Minutes, do not do anything else! Please let your device settle with screen off for about 10 Minutes after the first boot, otherwise the system wont boot after a reboot!
Once you're done setting up your device - well that's when you're done. One thing though - Make sure you DO NOT INSTALL any other zip in the same queue as the ROM! Meaning, do not flash anything like Gapps, a kernel or a root package while installing the ROM. We recommend you do that AFTER you're done setting up your device.
Important / Useful links
OpenGapps
SuperSU root package
Paranoid Android Community (G+)
As always, we listen to what you have to say. Help me make PA better by submitting good bug reports possibly with a log attached. Learn how to take logs here. Submit bug reports and we'll try to iron out issues as soon as possible - it really helps a lot.
Mention me if you need any assistance and/or when reporting bugs or if you just wanna chat.
Thank you to savadam for the video guide and review below
Quick Review:
Installation Guide:
Cheers and #StayParanoid!
XDA:DevDB Information
AOSPA - Paranoid Android, ROM for the Xiaomi Mi 5
Contributors
33bca (& @bgcngm for the work on CyanogenMod)
Source Code: https://github.com/AOSPA
Device Source Code: https://github.com/33bca/android_device_xiaomi_gemini/tree/aospa-6.0
Kernel Source Code: https://github.com/CyanogenMod/android_kernel_xiaomi_msm8996
Version Information
Status: Beta
ROM OS Version: 6.0.x Marshmallow
Based On: AOSPA
Created 2016-11-10
Last Updated 2016-11-17
Bugs:
Performance issues with battery below 5%
Gapps are not working at first boot (just install them later )
You tell me (but without log, its not a bug!)
Changelog:
10.11.2016
Initial release
13.11.2016
Temporary Performance & Battery adjustments
Rom upstream with PA
Kernel Upstream with CM
Firmware Update to Global Beta 6.9.29
17.11.2016
Rom upstream with PA
Kernel Upstream with CM
3G Fixed
Tricks:
Battery and Performance Increasement
To activate my Battery and Performance Adjustments, excetuce "su" to run the Terminal in Superuse Mode. Then run "sh /system/etc/init.qcom.post_boot.sh" to activate them.
Installing as we speak, nice work bringing PA to mi5!
ota updates? isnt it unofficial
vallabh1994 said:
ota updates? isnt it unofficial
Click to expand...
Click to collapse
Yes, unofficial ota updates
I modified the paranoid hub app to check if i published an update If there is an update, you can download it within the settings
Boot.img with kernel falcon 1.4.1 by harrynowl implemented for rom paranoid OVERCLOCKING 2.5GHz
Running 100% on my Mi5 32GB
With kernel falcon implemented
You already know to download booti.img open zip of the rom and replace the boot.img of the rom with the downloaded ... zip and flash rom
DOWNLOAD: https://mega.nz/#!fN0XjLpT!YwFGdPguVhzv3xDe1S4XgP0Ngp8h9jQKKCpMuoln3sc
33bca said:
Yes, unofficial ota updates
I modified the paranoid hub app to check if i published an update If there is an update, you can download it within the settings
Click to expand...
Click to collapse
So will u release full. ROM updates or just upgrade via ota?
Thank you for supporting MI5
Sent from my MI 5 using XDA-Developers mobile app
vallabh1994 said:
So will u release full. ROM updates or just upgrade via ota?
Click to expand...
Click to collapse
full rom, no delta updates...
Installation is a bit fiddly. Have to follow instructions and give it a time to settle. Then you get an. excellent rom.
Exposed works very well.
Great camera. Take pictures while recording video
Fingerprint works better than any other rom.
Am staying Paranoid .
Thanks dev
4719 said:
Installation is a bit fiddly. Have to follow instructions and give it a time to settle. Then you get an. excellent rom.
Exposed works very well.
Great camera. Take pictures while recording video
Fingerprint works better than any other rom.
Am staying Paranoid .
Thanks dev
Click to expand...
Click to collapse
Which gapps version you use? I was installing this rom, wait for about 10 minutes and install latest opengapps nano and it can enter homescreen for a while then back to bootanimation again.
Sent from my MI 5 using Tapatalk
arif_kholid said:
Which gapps version you use? I was installing this rom, wait for about 10 minutes and install latest opengapps nano and it can enter homescreen for a while then back to bootanimation again.
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
Also latest open nano. Did you set up the rom, before flashing gapps?
arif_kholid said:
Which gapps version you use? I was installing this rom, wait for about 10 minutes and install latest opengapps nano and it can enter homescreen for a while then back to bootanimation again.
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
Can happen, happened to me only one time (the one time i did no logcat...) but after the reboot, it should work
I always use the pico gapps, but its up to you!
which version of twrp do u recommend?
younant said:
which version of twrp do u recommend?
Click to expand...
Click to collapse
its up to you, but i'm useing the newest from the twrp site
younant said:
which version of twrp do u recommend?
Click to expand...
Click to collapse
The best is TWRP-3.0.2-2-gemini.img
Doenload: http://www103.zippyshare.com/v/RHeV3pjE/file.html
---------- Post added at 11:15 AM ---------- Previous post was at 11:12 AM ----------
33bca said:
its up to you, but i'm useing the newest from the twrp site
Click to expand...
Click to collapse
Thanks 33bca for this rom
It's the best rom there is so far
Better even than the JDC
In antutu with kernel falcon implemented 139600 in my Mi5 32GB
From Spain we thank you
Results with Benchmark and falcon kernel implemented on my Mi5 32GB
Awesome work mate, maybe you should try to make this official? After every bug will be fixed :fingers-crossed:
marcoly said:
Awesome work mate, maybe you should try to make this official? After every bug will be fixed :fingers-crossed:
Click to expand...
Click to collapse
Haha no, this wont happen
33bca said:
Haha no, this wont happen
Click to expand...
Click to collapse
Why? You are not interested in this or Paranoid team is not accepting anyone else? :crying:
RR v5.8..0 N WITH JAN 7 SECURITY PATCH
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About Resurrection Remix ROMResurrection Remix the ROM has been based on CM,slim.omni and original Remix ROM builds, this creates an awesome combination of performance, customization, power and the most new features, brought directly to your Device
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to, the CM team,OMNI team ,SLIMROMS and of course to all the supporters
ABOUT THIS PROJECT
Rather that the usual ready to flash port rom,today am here with a change.in fact i was forced to do this.so first of all sorry if the title misguided you
this time am up with a patch so that you can flash the RR v5.8.0(N) rom made for k3 note/a7000 plus/p70 directly to out device
NOTE:this method may work out on a few other MM/N(based on mm libs and kernel) you may try and verify it yourself @ your own risk.please let me know if u successfully boot any other roms
UPDATE: source compiled k3 note Nougat roms with system in system.new.dat format wont get flashed on our device directly,you will need to manually extract it(use superr kitchen or some other alternatives) and try
FLASHING PROCEDURE[MUST READ]
many of you will be enough and more experienced in flashing roms but to boot this rom,follow the method below or else it wont boot in majority of the cases.flash try this at your own risk,please dont do this in case you are not sure about what you are actually doing
step 1:download a sutiable rom.this time lets try with RR v8.5 Nougat
link:here
[all respect&credits to rom developer and his team,please dont spam his post asking about this patch just download
rom from the link and continue reading this thread]
step 2:reboot to recovery do a advanced wipe as usual[data/dalvic/cache/system]
step 3:go flash the rom directly
step 4:flash kernel for a7000
link:here
step 5:reboot to system
step 6:wait for 5+ minutes with bootanimation[imp]
step 7:do a manual reboot to recovery
step 8:mount system and flash the patch(links below)
step 9:reboot to system and see the rom boots and works flawlessly
step 10: once rom booted successfully change display size through setting or using build.prop editor
set lcd density to 320(default)
step 11:thats it you are good to go
note:do not do a reset cause you will have to do all the above steps once again if data is lost!
BUGS
Nothing major however be ready to face few which i might havent noticed.i didnt promise a stable rom with this method
[jio works:set 4g lte only+barer=lte it will work]
A FEW FINAL WORDS
*dont go and spam the threads made for k3 note asking about this patch.they have made the rom for k3 and hence wont have any idea regarding this patch
*neither me nor the developer of rom will have no responsibilities in case you bricked your device
*its my final port-project for a7000 and hence dont expect any updates.however i *may work on kernels and base that too when i have enough and more free time
*after all thanks to all who supported me and my works till date
HAVE A HAPPY FLASHING GUYS:highfive:
LINK[PATCH]:HERE
DONATIONSlike my work?any donations could be made here(paytm)
barcode
*sadly i havent earn any money from any of my works till date :crying:
*Eventhough you couldnt donate please be kind enough to hit the thanks button to encourage me.thats my only benifit from this :good::good:
REGARDS:
ASWIN PRADEEP
XDA:DevDB Information
[rom-port-patch][7.1.1]RR v5.8[N] for a7000, ROM for the Lenovo A7000
Contributors
aswinp222
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Testing
Created 2017-02-03
Last Updated 2017-02-04
Reserved
proof screenshots of booting RR v8.5.0 is given below
reserved
Guys, if you don't want to set screen size manually after booting, here is a zip for you.
https://drive.google.com/file/d/0BxkDSj8MtdPQRmtzTnVfN2t4eDQ/view?usp=sharing
It also changes some values to make it more compatible with A7000, rather than keeping the default values from ME note.
I used this zip myself and I assure you it works as it should.
@aswinp222 Please edit your installation instructions to ask users to download this patch too. If possible, please don't copy paste the link.
Nice ROM bro.:laugh::good:
Edit : @aswinp222 I just discovered a glitch in RR. This build prop fix is compulsory to fix it. Can't be fixed by native nougat DPI feature.
tanish2k09 said:
Guys, if you don't want to set screen size manually after booting, here is a zip for you.
https://drive.google.com/file/d/0BxkDSj8MtdPQRmtzTnVfN2t4eDQ/view?usp=sharing
I used this zip myself and I assure you it works as it should.
@aswinp222 Please edit your installation instructions to ask users to download this patch too. If possible, please don't copy paste the link.
Nice ROM bro.:laugh::good:
Click to expand...
Click to collapse
Users,if u face any difficulty in changing display size you may flash this.
Btw i didnt pre-include it since i made the patch not only for this particular rom and also since this rom and many other N roms have option to change display size by default in settings itself.
@tanish2k09 , any major bugs ?
emil_515 said:
@tanish2k09 , any major bugs ?
Click to expand...
Click to collapse
Hmm. Yes. Since the source is same (k3), LOS bugs are also present in this ROM.
I've also faced issues with titanium backup but that was probably a problem with my backups.
this rom have engineer mode? if not - it's not usable without volume fixing inside engineer mode.
Here is a link to devil kernel for all the users. Latest kernel build as of 3rd Feb 2017.
https://drive.google.com/file/d/0BxkDSj8MtdPQeHF2T0J0bDRVcG8/view?usp=drivesdk
@aswinp222 I have flashed the ROM twice and I recommend you to remove the step 5,6,7 from instructions because they are useless.
What I do : Flash ROM, k3 patch, kernel, build prop fix.
All of these I flash in this order and reboot only once later.
tanish2k09 said:
Here is a link to devil kernel for all the users. Latest kernel build as of 3rd Feb 2017.
https://drive.google.com/file/d/0BxkDSj8MtdPQeHF2T0J0bDRVcG8/view?usp=drivesdk
@aswinp222 I have flashed the ROM twice and I recommend you to remove the step 5,6,7 from instructions because they are useless.
What I do : Flash ROM, k3 patch, kernel, build prop fix.
All of these I flash in this order and reboot only once later.
Click to expand...
Click to collapse
Whoaaaa. Thanks.
tanish2k09 said:
Here is a link to devil kernel for all the users. Latest kernel build as of 3rd Feb 2017.
https://drive.google.com/file/d/0BxkDSj8MtdPQeHF2T0J0bDRVcG8/view?usp=drivesdk
@aswinp222 I have flashed the ROM twice and I recommend you to remove the step 5,6,7 from instructions because they are useless.
What I do : Flash ROM, k3 patch, kernel, build prop fix.
All of these I flash in this order and reboot only once later.
Click to expand...
Click to collapse
U sure??then once try flasing rom and patch only nothing else,even kernel or ur patch and see if rom boots..plz let me know result
Downloaded aicp12. Will give it a shot.
aswinp222 said:
U sure??then once try flasing rom and patch only nothing else,even kernel or ur patch and see if rom boots..plz let me know result
Click to expand...
Click to collapse
Why would you want me to boot it without flashing the kernel??
And yes I'm sure. Tried twice.
I am getting some weird texts in weird places. Do you get these? (Check images)
When WhatsApp notifications arrive from two different chats, the header becomes "this is important because of the people involved".
1) Internal storage shows weird name.
2) In running services, "paste as plain text" and "replace"should not be there. I get these texts even in dialer during call.
Sorry about second SS.
tanish2k09 said:
Why would you want me to boot it without flashing the kernel??
And yes I'm sure. Tried twice.
Click to expand...
Click to collapse
because the patch is preincluded with kernel,and in my testings the patch wont work unless data is created.
emil_515 said:
Downloaded aicp12. Will give it a shot.
Click to expand...
Click to collapse
i have pre-tested that specific rom bro,it wont boot :crying: it wont even flash unless you extract the system.new.dat
@aswinp222
This ROM has the media glitch too. Why do the same bugs exist in RR and los?? Is there a same dev or base or something??
Someone please confirm YouTube video playback. Try playing two videos consecutively.
aswinp222 said:
i have pre-tested that specific rom bro,it wont boot :crying: it wont even flash unless you extract the system.new.dat
Click to expand...
Click to collapse
Is there any way to fix that ?
Because that ROM seems more stable
I'm getting an error sim card is PUK locked
emil_515 said:
I'm getting an error sim card is PUK locked
Click to expand...
Click to collapse
Just wait for sometime. Will get away itself. You just need to get signal for removing that error. Steps for Jio or any 4g-only sim are given in op.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free and open-source operating system for smartphones and tablet computers, based on the Android mobile platform.
This is an unofficial build of LineageOS for the Pixel 2 (walleye). I always liked Lineage (and its predecessor CyanogenMOD) as well as the Google line of phones. Unfortunately having a Google Pixel phone isn't certainty for a lot of custom ROMS anymore, so that's why I decided to compile my own version. It's been quite challeging, but I think I finally have a build that is good enough to share.
About
This ROM is is always built straight from the LineageOS sources found on https://github.com/lineageos. There are only 3 changes in order to get this build:
The binaries for this ROM come from AICP
GApps are compiled with the ROM from MindTheGapps including the Pixel specific bits for unlimited photo upload for instance
Disabled Android Verity Boot (AVB), so we don't get the security warning when booting
I am not a developer, I only build this ROM and it reflects the the current status. If there are any things missing or not working I suggest to contact the LineageOS team, they are the real geniuses here and deserve all the credits. I will try to keep this ROM updated on a regular basis.
First Installation
Installing the ROM can be a little hard, especially the first install. Upgrades will be relatively easy though. This first setup is only needed when coming from a different ROM then this. I can't support you if you did't follow this first installation. Be warned it will wipe your user data in the process
In order to get the initial setup and also to use the same vendor partition as the ROM you have to install the latest stock Pixel 2 image from Google found here. More info on unlocking your phone and installing the latest Pixel image can be found in the excellent post by @nathanchance found here. The bestway to flash a stock ROM in my opinion is @Deuces' script found here. The benefit of this is that it'll flash the image to both slots, so they are both on the latest build, including the bootloader and radio. All instructions for using the script are inside the forum. After flashing the image make sure you reboot at least once (no need to set it up now though).
Place the ROM and optionally the TWRP zip and root from (Magisk or from LineageOS (not tested) on the phone and reboot to recovery by using the command line (fastboot boot twrp.img)
Wipe 'data' and 'Dalvik / Art Cache' from TWRP - Wipe - Advanced Wipe. Optionally you should also delete the Android folder on your internal storage through the TWRP File Manager
Flash the ROM and optionally the TWRP zip and reboot the phone
Upgrades to new version
After the hard initial work to get the ROM installed it's going to be easy for upgrades to new versions.
Download the new ROM and reboot of flash to TWRP
Flash the new ROM and optionally TWRP. If you want to flash another kernel or a root solution you will have to reboot you phone, so it switches slots and let it boot normally. Then go back to recovery and flash in this order: TWRP - kernel - Magisk and reboot
After a monthly update from Google and only when LineageOS also adapted to the latest monthly sources (I will tell you this) you will have to do an extra step:
Download the latest Lineage OS ROM and place it on the internal storage
Download the latest image from the Google Factory Images site and run Deuces' script. No need to wipe your data!
After the script finishes it automatically boots into the bootloader. From here fastboot into TWRP and flash the previously downloaded new ROM, optionally followed by TWRP.
Optionally, after a reboot you can flash Magisk and/or another kernel.
Not working
Substratum
Use Powerbutton for flashlight when Ambient Display is set
Active Edge
Now playing
Downloads
I'm not maintaining this project anymore, download link has been removed.
Happy flashing
Miraculous... Will flash soon. Thank you for keeping Pixel 2 relevant.
Is link not posted yet?
I want to thank you for posting. But, I get the feeling this will just be closed as well really soon. Hope this sticks around, because XDA is not what it use to be, at all!
JCBiznatch said:
I want to thank you for posting. But, I get the feeling this will just be closed as well really soon. Hope this sticks around, because XDA is not what it use to be, at all!
Click to expand...
Click to collapse
Why would it be closed?
JCBiznatch said:
I want to thank you for posting. But, I get the feeling this will just be closed as well really soon. Hope this sticks around, because XDA is not what it use to be, at all!
Click to expand...
Click to collapse
I completely agree...
Any chance for an MD5
jascolli said:
Any chance for an MD5
Click to expand...
Click to collapse
Added in the same folder:
MD5: a28cd4f3cabe627fbe99cbe1485cba3f
TCUofficial said:
Why would it be closed?
Click to expand...
Click to collapse
I don't have a clue. It just seems that anyone who posts a ROM gets the thread closed. It's almost as if they don't want walleye to have any development.
Just check this forum out compared to the pixel XL 2 forum.
Thanks very much for sharing this. I've got it installed and it's running fantastic.
Everyone who has had a rom thread has closed the thread for different reasons, time, family, frustration or lack of support etc...
I see don't see why we should be negative and assumee the same is the case with this build. Every rom thread has produced better and more stable builds as time progressed.
@Joregen2009, I have seen your name around before, appreciate you building!!
razrlover said:
Everyone who has had a rom thread has closed the thread for different reasons, time, family, frustration or lack of support etc...
I see don't see why we should be negative and assumee the same is the case with this build. Every rom thread has produced better and more stable builds as time progressed.
@Joregen2009, I have seen your name around before, appreciate you building!!
Click to expand...
Click to collapse
It's my pleasure. I only wanted to share my build, because I know that many of you much be as frustrated as me for the lack of ROMs for our device.
We'll see how long this thread will hold. If it's up to me I'll try to provide at least a weekly build from the actual sources, or whenever there are some major changes in the sources that are important for our device until the Lineage Team declares our device official. Let's hope that happens soon and that this thread can contribute to that.
Awesome! Thanks for this ROM. Any known issues one should be aware of before flashing?
Does Lineage have Substratum support ?? Having trouble connecting......
Update. Found answer - : no substratum support
@jorgen2009
Hey thanks so much for the ROM. Its working great!
Is there any chance you could link me the kernel source for this specific build? (Pixel2)
I'm trying to figure out how to rebuild it with the drivers for my TP-LINK WN722N V1.
I really don't know what I'm doing but I'm trying to learn.
I'm trying to follow this guide to accomplish this.
https://forum.xda-developers.com/showthread.php?t=2338179
I do have Kali for Magisk up and running just fine.
Lsusb command shows my WiFi Adaptor but the kernel won't let me use it.
Thanks so much for reading, if what I'm trying to do is stupid feel free to let me know why haha. If I get it to work I'll share it with everyone.
redsmith said:
Awesome! Thanks for this ROM. Any known issues one should be aware of before flashing?
Click to expand...
Click to collapse
The only thing that I am aware of is the fact that the battery LED isn't working, but that will be solved in the next build
tkacer said:
Does Lineage have Substratum support ?? Having trouble connecting......
Update. Found answer - : no substratum support
Click to expand...
Click to collapse
Sorry, than I fear it's not supported by LineageOS in general yet, I don't use it myself
gahndii said:
@jorgen2009
Is there any chance you could link me the kernel source for this specific build? (Pixel2)
Click to expand...
Click to collapse
Sure, see LineageOS sources on github, I didn't touch the kernel in this build:
https://github.com/LineageOS/android_kernel_google_wahoo
I am still getting the security warning when booting. Am I the only one so I missed something?
Other question: is the Trusted Faces not working because the used GApps package has not been modified for the Pixel, or the ROM has got some incompatibility issue?
Great job. Just a little bug: Long press power button to turn on torch is not working when Ambient Display is set to always on.
banciii said:
I am still getting the security warning when booting. Am I the only one so I missed something?
Other question: is the Trusted Faces not working because the used GApps package has not been modified for the Pixel, or the ROM has got some incompatibility issue?
Click to expand...
Click to collapse
Are you sure you are on the April vendor? Your vendor version must be the same as the ROM needs (currently the April one).
Trusted Faces is GApps related yes, it's not in MindTheGApps. I'll try to make a build with OpenGApps in to see if that works. Both Face Detection for Media and Face Unlock are in the Nano package (https://github.com/opengapps/opengapps/wiki/Nano-Package)
redsmith said:
Great job. Just a little bug: Long press power button to turn on torch is not working when Ambient Display is set to always on.
Click to expand...
Click to collapse
I'll put it in the known issues list in the OP later this week for an overview
Another build is up. This time I used OpenGapps so you might need to clear the Store cache. I had no problems upgrading myself. The Text-to-speech improved a lot with these Gapps for me.
New in this build is the LED light when charging and some basic stuff for more compatibility with our device and some networks. Also all the normal changes since the last build for LineageOS are in of course. For the download link see the OP. I also adjusted the OP a bit to show the things that are known not to work. Let me know if I missed something so I can adjust the list