Hi all,
Please consider using official Resurrection Remix GSI instead of this!
I've made my work on AOSP Phh-Treble as modular as possible, so that it can be reused on other ROMs.
As part of this effort, I'm releasing GSIs of Resurrection Remix.
This is a GSI, and true to the GSI spirit. It aims at supporting a maximum number of devices, but only with AOSP-available hardware features.
All credits obviously goes to Resurrection Remix developers
v5: (2018-06-27)
Image for ARM64 A-only device with gapps
Image for ARM64 A-only device vanilla
Image for ARM64 A/B device with gapps
Image for ARM64 A/B device vanilla
Image for ARM32 A-only device with Android Go gapps
Image for ARM32 A-only device vanilla
v4: (2018-05-19)
Image for ARM64 A-only device
Image for ARM64 A/B device
Image for ARM32 A-only device
Image for ARM32 A-only devices, with Android Go gapps
V3: (2018-04-05)
Image for ARM64 A-only device
Image for ARM64 A/B device
Image for ARM32 A-only device
ChangeLog:
v4 (2018-05-19):
- Update to latest AOSP Phh-Treble patches
- New Android Go variant with gapps
v3 (2018-04-05):
- Fixed S9 backlight control
- Resize /system to maximum size on first boot
v2 (2018-03-26):
- Failed build
How to build:
Code:
git clone https://github.com/phhusson/treble_experimentations
mkdir RR; cd RR
bash ../treble_experimentations/build-rom.sh android-8.1 rr
I'm assuming that this build works with the G965F now?
Keep up the good work!
Woaw...thanks a lot for the Rom...
Savoury said:
I'm assuming that this build works with the G965F now?
Keep up the good work!
Click to expand...
Click to collapse
Well, this RR hasn't been tested much, and even AOSP hasn't been tested on G965F as far as I know.
But it's supposed to work.
Feel free to report your results
does this include gapps for a/b devices
Feel free to PM me, and we'll test AOSP if you want to.
thanks for your work, A-only version running smooth on S9+. GAPPS and if possible root would be nice.
Great Work!
Thanks! Working fine in Xiaomi Mi5 but some small bugs
Ohhhh man @phhusson this ROM is pure love, was desperately waiting for this, thankyou so much
Any idea how to flash Gapps onto the rom?
chen8894 said:
Any idea how to flash Gapps onto the rom?
Click to expand...
Click to collapse
Reboot Recovery after you flashed the Image, then install Opengapps of your choice. (Depends on free space on /System for some Devices, for Mido the Micro Gapps are to big)
panchovix said:
Thanks! Working fine in Xiaomi Mi5 but some small bugs
Click to expand...
Click to collapse
How many bugs?
ohwarumbloss said:
Reboot Recovery after you flashed the Image, then install Opengapps of your choice. (Depends on free space on /System for some Devices, for Mido the Micro Gapps are to big)
Click to expand...
Click to collapse
Sorry... didn't clarify. My device is mate 10 pro.
GerWonder said:
thanks for your work, A-only version running smooth on S9+. GAPPS and if possible root would be nice.
Click to expand...
Click to collapse
I guess the cameras don't work as with stock ROM? thinking of example the 2x zoom.
rafizulhasan said:
How many bugs?
Click to expand...
Click to collapse
Backlight buttons, VolTE and home fp button, well i mean they are not vital at all except maybe for VolTE (here in Chile at least VolTE isn't implemented yet, so no worries)
Just wondering tho, the GSI LOS and AOSP have backlight buttons since it has the options in the "buttons option", but not on RR GSI
panchovix said:
Backlight buttons, VolTE and home fp button, well i mean they are not vital at all except maybe for VolTE (here in Chile at least VolTE isn't implemented yet, so no worries)
Just wondering tho, the GSI LOS and AOSP have backlight buttons since it has the options in the "buttons option", but not on RR GSI
Click to expand...
Click to collapse
Yeah the button backlight patches don't apply on RR, and patch fails are ignored at the moment (because ROMs might already include patches. For instance lineage already has this button backlight patch.
I'll try to fix it, but that's quite low on my product priority list.
phhusson said:
Yeah the button backlight patches don't apply on RR, and patch fails are ignored at the moment (because ROMs might already include patches. For instance lineage already has this button backlight patch.
I'll try to fix it, but that's quite low on my product priority list.
Click to expand...
Click to collapse
No problem man! i'm just thankful of your work, it is just a minor thing for me at least
Thanks!Working on the mi 6 but can't set the password.
Great!
Related
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
3rd PARTY ADDONS/MODS
While we have no issues with people using supersu/magisk/xposed/custom kernels/etc, we can't provide support for users who have them installed.
This thread is not the right place to discuss about mods/addons.
HOW TO INSTALL LINEAGEOS
- Make sure your phone is running Oreo firmware (from OxygenOS 5.0)
- Remove custom encryption pins/passwords else decryption will fail!
- Download the LineageOS zip(s). (see Downloads)
- Copy the LineageOS zip to internal sdcard.
- Unlock bootloader and install TWRP.
- Boot into TWRP.
- Perform a backup of your current ROM. (Optional)
- RECOMMENDED: Do a factory reset! No support if you didn't!
- Flash LineageOS.
- Optional: Install the Google Apps addon package. (see Downloads)
- Reboot
HOW TO UPDATE LINEAGEOS (15.1 -> 15.1)
- Download the LineageOS zip(s). (see Downloads)
- Copy the LineageOS zip to internal sdcard.
- Flash LineageOS.
- Reboot
DOWNLOADS
Lineage 15.1: https://download.lineageos.org/dumpling
Firmware: https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/dumpling/firmware/
Vendor images: https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/dumpling/vendor/
Unofficial: SourceForge
SU-Addon: https://download.lineageos.org/extras
Google Apps: https://sourceforge.net/projects/unofficial-opengapps-8-1/files/arm64/ | http://opengapps.org/
TWRP: XDA | twrp.me
DEVELOPER RESOURCES
https://github.com/LineageOS/android_device_oneplus_dumpling
https://github.com/LineageOS/android_device_oneplus_msm8998-common
https://github.com/LineageOS/android_kernel_oneplus_msm8998
HOW TO CONTRIBUTE?
Send your patches up for review: https://review.lineageos.org/
At SourceForge (found at downloads link above) we also occasionally provide firmware zips or custom built TWRPs.
We use them when developing and also make them available to others, but please note they are unsupported.
They are good enough for us developing but might not be good enough for everyone's usecases.
@codeworkx is trying to upstream the changes we did to TWRP and created a thread for that, if you need some more help.
https://forum.xda-developers.com/oneplus-5t/development/recovery-twrp-3-2-1-0-oreo-8-0-8-1-t3729673
bronderb said:
Is this pre-official?
Click to expand...
Click to collapse
Yes, i am one of the Lineage OnePlus5(T) maintainers and this is what you will get, when official nightlies are starting.
Only difference though is, that i am building with "sdclang", official build servers build using the default toolchain.
// edit
to clear up confustion, previously my github and general username was "Evisceration", nowadays it is "amartinz".
Bit off topic, will Lineage get exchange support in the future?, as now its missing in all oreo roms (not gmail with addons)
Thanks for new rom and your hard work. It is nice to see on op5t forum great devs
btw, until official builds, there will be few more builds ? Thanks
DocRambone said:
Bit off topic, will Lineage get exchange support in the future?, as now its missing in all oreo roms (not gmail with addons)
Click to expand...
Click to collapse
Forwarded that question, will let you know once i get some answers
marko94 said:
Thanks for new rom and your hard work. It is nice to see on op5t forum great devs
btw, until official builds, there will be few more builds ? Thanks
Click to expand...
Click to collapse
Yes, there will be more builds.
we put up builds whenever we see fit, means if there are new features or things to test or if more fixes are in.
We do not want to waste people's time with flashing roms when there are no changes at all
Super glad to see you here! I also see codeworkx has already uploaded the TWRP for 15.1 (8.1) and can't wait to try this when I have an off day to mess around with it!
@Evisceration What is yours suggestion for root ?
DocRambone said:
Bit off topic, will Lineage get exchange support in the future?, as now its missing in all oreo roms (not gmail with addons)
Click to expand...
Click to collapse
Alright, so it seems that it is not on the bringup item list.
It seems CAF did a single commit regarding exchange in 2017 so seems not a high priority for them as well.
And the people who usually worked on exchange are not active since some time, so it does not look promising.
Seems everyone is shifting focus to gmail or other third party apps.
MrIndieJ said:
Super glad to see you here! I also see codeworkx has already uploaded the TWRP for 15.1 (8.1) and can't wait to try this when I have an off day to mess around with it!
Click to expand...
Click to collapse
Thanks for your warm welcome
I hope you do not run into troubles that you need the whole day and can actually also enjoy it the rest of the day
marko94 said:
@Evisceration What is yours suggestion for root ?
Click to expand...
Click to collapse
I personally use the built in root via adb.
Magisk should be fine but it annoys me when i have to reflash it everytime when i flash a new kernel.
That Kingoroot thingy from china seems really suspicious to me and i would not even touch it with a pole.
Though, use whatever you see fit, I provide some limited support helping out to get stuff running if someone runs into troubles but my support time is not infinite
Evisceration said:
Alright, so it seems that it is not on the bringup item list.
It seems CAF did a single commit regarding exchange in 2017 so seems not a high priority for them as well.
And the people who usually worked on exchange are not active since some time, so it does not look promising.
Seems everyone is shifting focus to gmail or other third party apps.
I personally use the built in root via adb.
Magisk should be fine but it annoys me when i have to reflash it everytime when i flash a new kernel.
That Kingoroot thingy from china seems really suspicious to me and i would not even touch it with a pole.
Though, use whatever you see fit, I provide some limited support helping out to get stuff running if someone runs into troubles but my support time is not infinite
Click to expand...
Click to collapse
Ok, thanks for letting me know, i use the exchange/email package from CM/Lineage 14 and its still fully functional.
As for root: SuperSU-v2.82-201705271822 still the best.
Do you know when the migration from 14.1 to 15.1 will start? Tom is running beautifully but I'm missing so many features.
Ok, tried flash clean with magisk, without no verity ( I am decrypted) , got bootlop.
New try : clean , rom, gapps, magisk 15.2, no verity booted fine
Everything seems fine, fingerprint working, camera also.
Some pictures
adame09 said:
Do you know when the migration from 14.1 to 15.1 will start? Tom is running beautifully but I'm missing so many features.
Click to expand...
Click to collapse
You can best follow the current development state by having a look at the Code Review.
Many features are in work, listing some below as example
Deskclock - https://review.lineageos.org/#/q/topic:deskclock-o
Live Display - https://review.lineageos.org/#/q/topic:oreo-mr1-livedisplay
Download speed and manual pause/resume support - https://review.lineageos.org/#/q/topic:oreo-mr1-download-provider
Button lights (not interesting for the 5T though) - https://review.lineageos.org/#/q/topic:oreo-buttons-lights
Even more button settings - https://review.lineageos.org/#/q/topic:oreo-mr1-buttons-redux
Long press to kill app - https://review.lineageos.org/#/q/topic:oreo-mr1-kill-app
Advanced reboot menu - https://review.lineageos.org/#/q/topic:oreo-mr1-rebootmenu
bfqio (will have a look at adding it to our kernel as well) - https://review.lineageos.org/#/q/topic:oreo-mr1-bfqio
CDMA - https://review.lineageos.org/#/q/topic:cdma
so these i found with just having a quick look at the review pages, took me 20 times longer to write this than actually find it
Things simply take time, but are processing good.
marko94 said:
Ok, tried flash clean with magisk, without no verity ( I am decrypted) , got bootlop.
New try : clean , rom, gapps, magisk 15.2, no verity booted fine
Everything seems fine, fingerprint working, camera also.
Click to expand...
Click to collapse
glad to hear!
i am encrypted though, modifications like removing encryption etc are not tested by us.
I did a clean wipe, format data, then flashed rom with 8.1 unofficial pico gapps and 15.2 magisk. When i boot up, the phone boots back into the recovery. Using the 8.1 recovery from the OP.
Any ideas?
Great work! I'm very happy to see this! Downloading...
Evisceration said:
ROM might be unified with Oneplus 5T in future (not sure yet).
Click to expand...
Click to collapse
Is this supposed to say "OnePlus 5"?
Questions:
What's the status of Privacy Guard?
I assuming we're currently encrypted with keymaster1. Will be be migrating to keymaster3 at any point in the future?
Thanks!
alienwolf426 said:
I did a clean wipe, format data, then flashed rom with 8.1 unofficial pico gapps and 15.2 magisk. When i boot up, the phone boots back into the recovery. Using the 8.1 recovery from the OP.
Any ideas?
Click to expand...
Click to collapse
Did you flashed the no verity zip?
This is great news!
Will try this rom tomorrow. Great work!
inzaghi75 said:
Did you flashed the no verity zip?
Click to expand...
Click to collapse
No. I assumed that was required if one wanted the rom decrypted or something.
alienwolf426 said:
I did a clean wipe, format data, then flashed rom with 8.1 unofficial pico gapps and 15.2 magisk. When i boot up, the phone boots back into the recovery. Using the 8.1 recovery from the OP.
Any ideas?
Click to expand...
Click to collapse
Just flash rom and gapps, reboot and setup device. Then reboot to recovery and flash root.
Hi all,
I've made my work on AOSP Phh-Treble as modular as possible, so that it can be reused on other ROMs.
As part of this effort, I'm releasing GSIs of LineageOS
This is a GSI, and true to the GSI spirit. It aims at supporting a maximum number of devices, but only with AOSP-available hardware features.
All credits obviously goes to LineageOS developers
v5: (2018-06-27)
Image for ARM64 A-only device with gapps
Image for ARM64 A-only device vanilla
Image for ARM64 A/B device with gapps
Image for ARM64 A/B device vanilla
Image for ARM32 A-only device with Android Go gapps
Image for ARM32 A-only device vanilla
v4: (2018-05-19)
Image for ARM64 A-only device
Image for ARM64 A/B device
Image for ARM32 A-only device
Image for ARM32 A-only devices, with Android Go gapps
V3: (2018-04-05)
Image for ARM64 A-only device
Image for ARM64 A/B device
Image for ARM32 A-only device
ChangeLog:
v4 (2018-05-19):
- Blackview A20 edition! Thanks to blackview for giving me this Android Go test device
- Fix Accents
- Update to latest AOSP Phh-Treble patches
- New Android Go variant with gapps
v3 (2018-04-05):
- Fix Galaxy S9 backlight control
- Support exfat sdcards on devices with exfat support in kernel
- Resize /system to maximum size on first boot
v2 (2018-03-26):
- Fix Galaxy S9 backlight control
How to build:
Code:
git clone https://github.com/phhusson/treble_experimentations
mkdir Lineage; cd Lineage
bash ../treble_experimentations/build-rom.sh android-8.1 lineage
Great Work!
Thanks for your work. I'll try this rom this weekend (I had problems with your other AOSP roms, I can't boot except the v9 one. I hope this version will boot).
iBen68 said:
Thanks for your work. I'll try this rom this weekend (I had problems with your other AOSP roms, I can't boot except the v9 one. I hope this version will boot).
Click to expand...
Click to collapse
I doubt it will boot.
What device is this? Could you get logs?
phhusson said:
I doubt it will boot.
What device is this? Could you get logs?
Click to expand...
Click to collapse
Huawei Mate 10 Pro BLA-L09. I will try to get logs when I try this rom.
Great work
bootloop on xperia xz1
i flashed it on stock rom and wipe userdata,cache on fastboot and also tried on twrp factory reset and cache,cache dalvik(i tried your aosp v9 v10 v11 it also doesn't work)
phhusson said:
I doubt it will boot.
What device is this? Could you get logs?
Click to expand...
Click to collapse
How can I get logs at this point?
eggimong said:
bootloop on xperia xz1
i flashed it on stock rom and wipe userdata,cache on fastboot and also tried on twrp factory reset and cache,cache dalvik(i tried your aosp v9 v10 v11 it also doesn't work)
Click to expand...
Click to collapse
Can you try this?
https://www.google.fr/amp/s/forum.x...l/how-to/treble-roms-pixel-2-xl-t3764851/amp/
What's the precise behaviour you're witnessing?
Do you get the White Android bootanimation, or only sony's logo?
Does it actually reboot when looping? You see the sony logo reappearing?
Does the device reboot to bootloader mode?
phhusson said:
I doubt it will boot.
What device is this? Could you get logs?
Click to expand...
Click to collapse
When I try
Code:
adb logcat
I got this:
Code:
PS C:\ADB> adb logcat
- waiting for device -
The adb daemon seems not to be started while the bootloop. When I go back to the AOSP v9 rom, I can see logs with the same command but it's pointless since this rom is booting well.
iBen68 said:
When I try
Code:
adb logcat
I got this:
Code:
PS C:\ADB> adb logcat
- waiting for device -
The adb daemon seems not to be started while the bootloop. When I go back to the AOSP v9 rom, I can see logs with the same command but it's pointless since this rom is booting well.
Click to expand...
Click to collapse
Does adb devices -l sees it?
phhusson said:
Can you try this?
https://www.google.fr/amp/s/forum.x...l/how-to/treble-roms-pixel-2-xl-t3764851/amp/
What's the precise behaviour you're witnessing?
Do you get the White Android bootanimation, or only sony's logo?
Does it actually reboot when looping? You see the sony logo reappearing?
Does the device reboot to bootloader mode?
Click to expand...
Click to collapse
Only sony's logo and it reappearing until I turn off the phone
eggimong said:
Only sony's logo and it reappearing until I turn off the phone
Click to expand...
Click to collapse
And did you try what's in the link I've given you?
phhusson said:
And did you try what's in the link I've given you?
Click to expand...
Click to collapse
can't flash on vbmeta partition with error
fastboot flash vbmeta vbmeta.img
FAILED <remote: Flashing is not allowed for partition>
Is it possible to build this w/ MicroG?
LiveDisplay and LED while charging do not work on Mido everything else work just fine
NadavCE said:
Is it possible to build this w/ MicroG?
Click to expand...
Click to collapse
Assume you're asking due to the news about Gapps and 'Uncertified Device' problems.
Seems like a lot more is riding on MicroG now ...
Also, pretty sad that Google have done this ... Treble was probably the best thing they've done for Android since its inception, both for custom ROM development and potentially speeding up software updates for those who don't tinker with their phones.
mudnightoil said:
Assume you're asking due to the news about Gapps and 'Uncertified Device' problems.
Seems like a lot more is riding on MicroG now ...
Also, pretty sad that Google have done this ... Treble was probably the best thing they've done for Android since its inception, both for custom ROM development and potentially speeding up software updates for those who don't tinker with their phones.
Click to expand...
Click to collapse
Well custom ROMs are whitelisted and so far I have not reported any issue with the Uncertified Device stuff on this GSI nor on RR GSI either, both by phhusson of course
patrick395x said:
Well custom ROMs are whitelisted and so far I have not reported any issue with the Uncertified Device stuff on this GSI nor on RR GSI either, both by phhusson of course
Click to expand...
Click to collapse
I don't think that is expected to remain the status quo. In fact if you read the screen / article, people running custom ROMs are expected to manually register their devices with Google ... and whether that is just a registration or additional tracking is unclear.
mudnightoil said:
I don't think that is expected to remain the status quo. In fact if you read the screen / article, people running custom ROMs are expected to manually register their devices with Google ... and whether that is just a registration or additional tracking is unclear.
Click to expand...
Click to collapse
I know, I read the article, but until we receive the Android ID registration we can keep using custom ROMs in an uncertified manner, once we are required to registrate our device we will see what happens
I really love Mokee.Have someone compiled Mokee for A only?
Unfortunately my computer is 32 bit:crying:And I am also unfamiliar with Linux...
Thanks in advance.
hujialun2002 said:
I really love Mokee.Have someone compiled Mokee for A only?
Unfortunately my computer is 32 bit:crying:And I am also unfamiliar with Linux...
Thanks in advance.
Click to expand...
Click to collapse
Here you go, vanilla MoKee without any modifications:
arm64 a-only MoKee
I don't recommend using it though, as MoKee ROMs are known to contain suspicious closed-source applications built-in…
remixn said:
Here you go, vanilla MoKee without any modifications:
arm64 a-only MoKee
I don't recommend using it though, as MoKee ROMs are known to contain suspicious closed-source applications built-in…
Click to expand...
Click to collapse
Thanks for the treat, . . . Ive been a mokee user back in lollipop days and is willing to comeback from it.
Have you tried the rom? Hoped the battery is good.
remixn said:
Here you go, vanilla MoKee without any modifications:
arm64 a-only MoKee
I don't recommend using it though, as MoKee ROMs are known to contain suspicious closed-source applications built-in…
Click to expand...
Click to collapse
Thanks so much for the help!
Wondering what are these close-sourced applications intended for?
Sent from my Honor 9 using XDA Labs
What does gsi mean
Mar-cel said:
What does gsi mean
Click to expand...
Click to collapse
use google..
[email protected] 2002 Excuse me "arm64 a-only MoKee" this GSI you brush into the phone will not sound, I use the underpack "eu" is the card in the second screen, and finally use "miuipro" to successfully enter the system, but only after the first boot or reboot the first call only sound, then call again will not be silent Voice, do you have this bug, Ps, I also brush gapps Pico and magic17.1, thank you.The model of my cell phone is MIMAX3.
I compiled the code lineage by nicknitewolf in 64bit mode.
My hope is to encourage experienced developers to create 64bits stable roms.
*** I have no experience in developing roms.
Source Code for review
local_manifests: https://github.com/Redmi2BR/local_manifests
Kernel: https://github.com/Redmi2BR/android_kernel_wingtech_msm8916_64
Device tree: https://github.com/Redmi2BR/android_device_wingtech_wt88047_64
common tree: https://github.com/Redmi2BR/android_device_cyanogen_msm8916-common
Vendor: https://github.com/Redmi2BR/proprietary_vendor_wingtech64
TWRP: https://github.com/Redmi2BR/device_wingtech_wt88047_64-twrp
Mandatory Installation Requirements:
ROMs 64bits need Twrp 64bit:
[TWRP 3.2.3-0][64bits][29/november/2018]:
https://www.androidfilehost.com/?fid=11410963190603861795
Resize the system partition to 1.5GB, (I resized to 2GB):
https://forum.xda-developers.com/showthread.php?t=3803042
Download ROM:
https://androidfilehost.com/?w=files&flid=283111
.
I am not responsible for bricked devices or dead SD cards.
Use at your own risk.
Secret bonus post:
Experimental Treble ROM Arm64 for Redmi2. For limited time!
This rom is just a test done by someone with little experience. So do not have a dedicated Thread, who should create are the creators of the project.
It was build using as base the source code from wt88047-treble github project from @karthik km and @mkfslsxbin.
Note:
This ROM can be installed on a system partition with 1GB of space.
But other GSI ROMs Arm64 usually have 1.5GB, 2GB or more.
Requirements:
Use Treble Twrp 64bits oem-Cache:
[02/november/2018]https://www.androidfilehost.com/?fid=11410932744536993167
Install the LinkerFix when using other GSI images (currently support oreo only):
[22/october/2018]https://www.androidfilehost.com/?fid=11410932744536985475
Download Treble64 ROM:
[18/october/2018]
https://www.androidfilehost.com/?fid=11410932744536983003
I am not responsible for bricked devices or dead SD cards.
ok ill try
Camera and volte are working or not
This is good, keep it up
interesting
@Cecell3000, what will happen if we don't resize system partition? couldn't installed??
xehed said:
@Cecell3000, what will happen if we don't resize system partition? couldn't installed??
Click to expand...
Click to collapse
probably wiil get error in TWRP when install (look my /system with 5 modules magisk, only one more of 10mb)
with 1,5gb, is possible install a nano open gapps without errors :good:
camera = freeze
try opencamera=freeze
but this rom is very fast, thanks dev..
Devlopment Of 64bit Oreo ROMs Would be better if some advance dev notice that work..
Thanks Your First Devlopment Of 64bit oreo..
update:
[12/October/2018]: fix camera
https://www.androidfilehost.com/?fid=1322778262904026669
.
Cecell3000 said:
update:
[12/October/2018]: fix camera
https://www.androidfilehost.com/?fid=1322778262904026669
.
Click to expand...
Click to collapse
Very good rom but Volte not working
Will it lag on 1/8?
- GPS not working, or take too long to position fix. I've waited 10mins and nothing
- Mobile data not working
Otherwise ROM is very fast and stable, good work!
deleted
Update
Experimental Treble ROM Arm64 for Redmi2.
(In the second post)
For limited time!
Cecell3000 said:
Experimental Treble ROM Arm64 for Redmi2.
(In the second post)
For limited time!
Click to expand...
Click to collapse
Why limited time
Rbqttp said:
Why limited time
Click to expand...
Click to collapse
aggressive marketing strategy
Cecell3000 said:
aggressive marketing strategy
Click to expand...
Click to collapse
:laugh:
Cecell3000 said:
Experimental Treble ROM Arm64 for Redmi2.
(In the second post)
For limited time!
Click to expand...
Click to collapse
just installed it on 1 Gb ram version.
Rom seems faster and so far everything run well.
great job dev, keep up development.
Lineage OS 16 For Xperia X [Treble]Based on Sony Open DevicesI am not responsible for bricked devices, dead SD cards,.Suitable for F5121 and F5122Reboot after your first boot please!
Opinional files:
Disable ForceEncrypt:Link
Required files:
[Tested]
V20190323:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v6_loire.zip
[OEM-Files]
Download Link
How to flash
Read README.txt in zip file please.
Optional step If you want to use a GSI
Flash a GSI compatible System image and boot!
Code:
fastboot flash system < Path of GSI-System.img >
Because of Anti-Rollback, If you want to Use GSI, You need to choose the same or newer one as the treble build date.
Update and known BUG:
V20190323:
Bugs:
1. Quick Charge is broken, you can use computer USB port charge.
2. Camera doesn't work on first boot, you need to reboot.
Source Codes
Sjll Script
Contributors
Sjll @infixremix
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Paypal
I am very happy to receive your donation.
Version Information
Status: Testing
Created 2019-03-31
Last Updated 2019-03-31
I've used your Treble Pie for a while and it's awesome. Gotta try this as well. Thanks a lot for all the work!
P/s: Can you make a custom overclocked kernel for your Pie ROMs? I've been using Extreme Kernels (for stock Oreo) and they are amazing. I wonder if Pie can also get a similar kernel.
Yeah bro thanks for this work..can you optimize kernel to make sodp rom usable
LOLisLIFE said:
I've used your Treble Pie for a while and it's awesome. Gotta try this as well. Thanks a lot for all the work!
P/s: Can you make a custom overclocked kernel for your Pie ROMs? I've been using Extreme Kernels (for stock Oreo) and they are amazing. I wonder if Pie can also get a similar kernel.
Click to expand...
Click to collapse
lookmanns14 said:
Yeah bro thanks for this work..can you optimize kernel to make sodp rom usable
Click to expand...
Click to collapse
I will try to build a optimize kernel in free time.
Hi,
Can you please help me with the download from the GSI? Where can I get the right file from?
after install, bluetooth and settings tell me that it stops all the time and sim cant be detected. Also there is some encryption so i can't access data or system anymore with twrp... even magisk can't be installed. great...
After running into a ton of errors, I think I've done something wrong. I have a few questions:
1. Where does Disable ForcedEncryption (DFE) go to in the installation process? If I flash the zip before Lineage (or not flasing at all), the phone encrypts itself right on boot. If I flash DFE zip after Lineage, the camera (and all the sensors) die permanently.
2. Regardless of the phone's encryption status, sometimes the phone just fails to recognize all the sensors (except Wifi, battery and GPS). That means no accelerometer, no screen rotation, no compass or light sensor. Rebooting fixes this on Lineage (for a while), but on RR once it occurs all sensors die permanently. Also GPS reception is terrible, as I haven't got a single fix.
Hope anyone who has been using Treble roms could give me an answer. Thanks in advance.
iH8Ecchi said:
After running into a ton of errors, I think I've done something wrong. I have a few questions:
1. Where does Disable ForcedEncryption (DFE) go to in the installation process? If I flash the zip before Lineage (or not flasing at all), the phone encrypts itself right on boot. If I flash DFE zip after Lineage, the camera (and all the sensors) die permanently.
2. Regardless of the phone's encryption status, sometimes the phone just fails to recognize all the sensors (except Wifi, battery and GPS). That means no accelerometer, no screen rotation, no compass or light sensor. Rebooting fixes this on Lineage (for a while), but on RR once it occurs all sensors die permanently. Also GPS reception is terrible, as I haven't got a single fix.
Hope anyone who has been using Treble roms could give me an answer. Thanks in advance.
Click to expand...
Click to collapse
Trust me....its weird (this is what i do with every pie Rom I DONT GUARANTEE SUCCESS ON TREBLE ROMS BECAUSE I WASNT ABLE TO TEST THEM YET)
Flash OEM image which is advertised here
Flash the Rom without anything
Reboot
Go back to recovery by Holding
Power + vol up
Screen turns black= quickly switch to
Power + vol down
Flash disable force encrypt
Reboot
Done!
(Remember to flash anything else that you want)
Some random said:
Trust me....its weird (this is what i do with every pie Rom I DONT GUARANTEE SUCCESS ON TREBLE ROMS BECAUSE I WASNT ABLE TO TEST THEM YET)
Flash OEM image which is advertised here
Flash the Rom without anything
Reboot
Go back to recovery by Holding
Power + vol up
Screen turns black= quickly switch to
Power + vol down
Flash disable force encrypt
Reboot
Done!
(Remember to flash anything else that you want)
Click to expand...
Click to collapse
I only run into these problems on Treble roms. No problem with sensors or encryption with native ones, such as AOSP or Paranoid.
iH8Ecchi said:
I only run into these problems on Treble roms. No problem with sensors or encryption with native ones, such as AOSP or Paranoid.
Click to expand...
Click to collapse
Hmmmmm
Well like that it worked with all pie ROMs that I used
I've been trying to flash this ROM but couldn't flash the Lineage OS Zip file. It says "Zip treble compatibility error!"
"Invalid zip file format!"
can someone please help me out?
Fardin Rehman said:
I've been trying to flash this ROM but couldn't flash the Lineage OS Zip file. It says "Zip treble compatibility error!"
"Invalid zip file format!"
can someone please help me out?
Click to expand...
Click to collapse
Use Twrp-Q (Ask Simeone for Link)
Some random said:
Use Twrp-Q (Ask Simeone for Link)
Click to expand...
Click to collapse
Yeah I have TWRP-Q just need to flash recovery and then try again. Thank you very much for helping
Can anyone please tell me which Gcam can i use on this ROM?
New version of LOS 16 + Treble
This version of LOS is outdated and does not work on latest Treble.
An updated LOS build (with Expanded volume and latest security patch) can be downloaded on this thread and installed over latest Treble.
Since this phone requires arm64 A-only GSIs to boot, the compatible version should be lineage-16.0-2019xxxx-UNOFFICIAL-treble_arm64_avN.img.xz.
Installation tutorial: Click here. Keep in mind that system.img refers to the LOS build above.
Getting Magisk to work: Click here.
iH8Ecchi said:
This version of LOS is outdated and does not work on latest Treble.
An updated LOS build (with Expanded volume and latest security patch) can be downloaded on this thread and installed over latest Treble.
Since this phone requires arm64 A-only GSIs to boot, the compatible version should be lineage-16.0-2019xxxx-UNOFFICIAL-treble_arm64_avN.img.xz.
Installation tutorial: Click here. Keep in mind that system.img refers to the LOS build above.
Getting Magisk to work: Click here.
Click to expand...
Click to collapse
Thanks man the ROM is great! But is it possible to make the camera work like it did on the original Xperia X stock ROM. I mean the camera is pretty dark on all custom ROMs is there any fix for that?
Fardin Rehman said:
Thanks man the ROM is great! But is it possible to make the camera work like it did on the original Xperia X stock ROM. I mean the camera is pretty dark on all custom ROMs is there any fix for that?
Click to expand...
Click to collapse
You can use Chippa_a's Unofficial LOS16 instead. That one has some heating issues and gaming performance might not be optimal (due to CPU throttling), but camera and battery life is almost identical to stock. In fact, I only use Treble LOS as daily driver because I play games on my phone quite a lot.
If you still insist on using Treble however, you can check out Google Camera ports (scroll down a little bit on Treble page). With HDR+ or Night Mode the picture quality is stellar, but taking pictures might be a bit slow. As far as I know it only runs on Treble and Omni.
iH8Ecchi said:
You can use Chippa_a's Unofficial LOS16 instead. That one has some heating issues and gaming performance might not be optimal (due to CPU throttling), but camera and battery life is almost identical to stock. In fact, I only use Treble LOS as daily driver because I play games on my phone quite a lot.
If you still insist on using Treble however, you can check out Google Camera ports (scroll down a little bit on Treble page). With HDR+ or Night Mode the picture quality is stellar, but taking pictures might be a bit slow. As far as I know it only runs on Treble and Omni.
Click to expand...
Click to collapse
Yeah I am using the gcam port and I get pretty good pictures with it but not very good video quality so I guess I'm gonna give it a try to Chippa_a's Unofficial LOS16.