Project treble for Xperia X [ android 10]
Based on Sony Open Devices
Based on Pavel's works
I am not responsible for bricked devices, dead SD cards,.
This is built as dual model, but it could also work on F5121.
Required files:
[OEM file:] Download link
Recommend: V9
[Treble files:] Download link
[Twrp-Q] Download link
How to flash::
First: Flash Twrp I built which supports a Vendor Partition
Code:
fastboot flash recovery < Path of recovery.img >
Second:Format Data and Cache in twrp
Flash treble images in fastboot mode:
Code:
fastboot flash:raw boot < Path of boot.img >
Code:
fastboot flash cache < Path of vendor.img >
Third: flash SW_binaries provided by Sony.
You can also download it from Sony official website.
Code:
fastboot flash oem < Path of OEM.img >
Fourth: Flash a GSI compatible System image and boot! Notice: GSI should be arm64 A/B type
Code:
fastboot flash system < Path of GSI-System.img >
Source Codes
Kernel
Contributors
Sjll @Cubbins
ROM OS Version: 10.0 Q
ROM Kernel: Linux 4.9
Version Information
Status: Testing
Donation:
Paypal
Created 2020-10-25
Last Updated 2020-10-25
Res
Thanks for sharing that
it's working on my F5121
but there's no sound on calls.
HTML:
Duronsoft said:
Thanks for sharing that
it's working on my F5121
but there's no sound on calls.
Click to expand...
Click to collapse
Tested on LineageOS 17.1 GSI, sound is fine when calling.
Duronsoft said:
Thanks for sharing that
it's working on my F5121
but there's no sound on calls.
Click to expand...
Click to collapse
this is a known issue, I will fix it soon
pls help me, i flashed my phone ok but at home sreen notice "
There's an internal problem with your device. Contact your manufacturer for details."
how to fix it?
thank you bro
Tested on F5122 ( Dual ), confirmed Lineage, Havoc and PE, AOSP can be used daily/
However if anyone planning to listen some music on it, use .flac format, .mp3 give you no sound, also Viper not working
---------- Post added at 08:28 AM ---------- Previous post was at 08:24 AM ----------
Noname_90 said:
pls help me, i flashed my phone ok but at home sreen notice "
There's an internal problem with your device. Contact your manufacturer for details."
how to fix it?
thank you bro
Click to expand...
Click to collapse
did you flashed an OEM system image
did you flashed an OEM system image
=> yes, i did it
and no sound for call
my device is f5122
Noname_90 said:
did you flashed an OEM system image
=> yes, i did it
and no sound for call
my device is f5122
Click to expand...
Click to collapse
only a few chance that OEM image would fully functional, i recommend using Official phhusson GSI, currently running Havoc 3.8 and calling have sound
no in-call sound is not an oem or blobs issue, but audio HAL.
I would be glad if someone opened all the issues in the bug tracker, then I will not forget about anything and it will be easier for you to track their current status. Thanks.
Best regards,
Pavel
Phone doesn't awake from deep sleep. I was put it on my desk than pressed power button 10 minutes later and phone waited with black screen than rebooted itself. Anyone has this issue?
Cubbins said:
no in-call sound is not an oem or blobs issue, but audio HAL.
I would be glad if someone opened all the issues in the bug tracker, then I will not forget about anything and it will be easier for you to track their current status. Thanks.
Best regards,
Pavel
Click to expand...
Click to collapse
I've created an issue in bug tracker and i will update all of them there ( in future )
TechnoHT said:
I've created an issue in bug tracker and i will update all of them there ( in future )
Click to expand...
Click to collapse
I noticed it. Thanks. Will see what I can do
Hello, thanks for the amazing work :victory:. The only issue is that I cannot add any fingerprint, tried with descendant x and havoc 3.8.
Other than that, everything is working for me, thank you
for anyone getting .mp3 crashing/no audio, please try to install Viper4Android and turn on Legacy mode in settings
( for further bug + fix just visit bug tracker )
@Sjll
Boot and vendor are cross-compatible for X-Compact (vendor at least is)? Please advise, or port and I will test (when you have a moment).
&(*) said:
@Sjll
Would you be willing to do a Kugo (X-Compact) port (when you have a moment, if possible)?
Click to expand...
Click to collapse
Pretty sure the vendor.img in cache will boot with X-Compact as the partitions are identical. I have a modified boot with the path set for vendor in kernel (hardcoded). Please advise.
&(*) said:
@Sjll
Boot and vendor are cross-compatible for X-Compact (vendor at least is)? Please advise, or port and I will test (when you have a moment).
Click to expand...
Click to collapse
Some things are different. You need another build. Otherwise you can damage your hardware.
If you are interested, I can make a build. But it will be Android 11
Cubbins said:
Some things are different. You need another build. Otherwise you can damage your hardware.
If you are interested, I can make a build. But it will be Android 11
Click to expand...
Click to collapse
That'd be nice (AOSP 11); I think devs like @Sjll don't consider requests or the reasons why || are too busy with other devices. Currently, my hardware is not capable of producing builds or I already would have done it on my own. I attempted to produce the vendor.img and always got a soong 21 error without reasonable debug info leading me to believe RAM is the issue. Regardless, X-Compact needs some attention as everything available is not up to date. I think the kernel and AOSP 10 dev's device bit the dust and the tree is no longer being maintained.
&(*) said:
That'd be nice (AOSP 11); I think devs like @Sjll don't consider requests or the reasons why || are too busy with other devices. Currently, my hardware is not capable of producing builds or I already would have done it on my own. I attempted to produce the vendor.img and always got a soong 21 error without reasonable debug info leading me to believe RAM is the issue. Regardless, X-Compact needs some attention as everything available is not up to date. I think the kernel and AOSP 10 dev's device bit the dust and the tree is no longer being maintained.
Click to expand...
Click to collapse
I have the kernel, device tree, everything. So soon you will get a build. But I only have Xperia X, so you will be my eyes and ears
Related
This LineageOS 14.1 ROM is built from source for Blu R1 HD.
Some features of this LineageOS 14 rom are:
- Hardware rendered LiveDisplay (no UI lag in night mode)
- Android security patches up to October
- Security hardened kernel (including BlueBorne bluetooth patches)
- Kernel patched for Nougat (Nougat compatible SELinux)
- No Chinese spyware
Credits:
zhaofengli (major thanks for getting the rom booting + hotspot/GPS fix, among other things!)
vampirefo
danielhk (GPS fix)
DeckerSu(Initial device tree, MTK patches)
Sources:
Code:
[URL=https://github.com/blumonks/android_device_blu_p6601]Device Tree[/URL]
[URL=https://github.com/blumonks/android_kernel_mediatek_mt6735]Kernel Source[/URL]
[URL=https://github.com/blumonks/android_p6601]Build Manifest[/URL]
[URL=https://github.com/blumonks/twrp_device_blu_p6601]Recovery device tree[/URL]
Downloads:
LineageOS 14.X Downloads
TWRP Recovery
Click to expand...
Click to collapse
Installation Guide:
1) Flash TWRP recovery (See downloads)
Code:
fastboot flash twrp-3.1.1-0-p6601.img
This TWRP recovery has a different device name than previous versions of TWRP.
2) Boot into recovery (Hold vol up when booting and use vol keys to select recovery)
3) If coming from a non lineageOS rom, please format system, data, and cache in recovery before flashing this rom. Otherwise stale files from previous roms may cause bugs.
5) Flash lineage rom
6) Flash gapps (obtain here: http://opengapps.org/)
Current bugs:
Camera does not work. It is still under active research and development.
Bluetooth
Github Issue Tracker (Please do not open duplicate issues)
Please note that support will be limited.
UPDATED BUILD 24 AUG 2020.
If anyone is still using this device, here is an updated build with the August 2020 Android Security Bulletin & all merged LineageOS changes since October 2017. MAKE SURE YOU FLASH USING THE TWRP IN THE ORIGINAL POST! You can flash over any builds in this thread, the camera still doesn't work and I have no interest in fixing it.
https://www.mediafire.com/file/dbdmk...p6601.zip/file
https://gofile.io/d/vTddMJ
Vulnerability said:
Nice! Can't wait to test it! Any screenshots?
Click to expand...
Click to collapse
It's the same as any other lineage rom. Updated OP.
How well does Bluetooth Audio work? Does it make you sound like a Chipmunk?
Is enforcing SELinux supported? Or only permissive?
EDIT: Don't worry I saw the issue tracker post
I'm gonna try this rom
It's nice to see development alive!!!
Hope you could a finally fix the broken camera
Does anyone know anything about the KRACK vulnerability?
zombie_ryushu said:
How well does Bluetooth Audio work? Does it make you sound like a Chipmunk?
Click to expand...
Click to collapse
I don't know, nor do I have the accessories to test it. I would appreciate if you could try it and report back.
zombie_ryushu said:
Does anyone know anything about the KRACK vulnerability?
Click to expand...
Click to collapse
Yes.. Please see download link for latest rom. It includes the KRACK security fixes from lineageOS.
jianC said:
I don't know, nor do I have the accessories to test it. I would appreciate if you could try it and report back.
Yes.. Please see download link for latest rom. It includes the KRACK security fixes from lineageOS.
Click to expand...
Click to collapse
Thanks for the updated version.
Urg, but I just finished downloading the original release
jianC said:
I don't know, nor do I have the accessories to test it. I would appreciate if you could try it and report back.
Yes.. Please see download link for latest rom. It includes the KRACK security fixes from lineageOS.
Click to expand...
Click to collapse
Does this fix also apply to the LineageOS 13.x Rom? I need the Front facing camera working, and that works under Marshmellow and not Nougat.
Just wanted to thank you for your hard work and dedication on this ROM project and wish you good luck with the camera as well.
Not that I find the camera on the R1 HD all that useful as it takes pretty lame photos, but the lack of camera is basically the only thing keeping me from ditching Blu software altogether.
I really hope you manage to get a 100% operational LineageOS for the R1 HD.
Yesterday I called Amazon and complained about the software that collected our personal information and data and submitted it to Blu headquarters in China. They said that I could return the phone for a full refund so at this point I am seriously contemplating doing that. The only problem is that I don't have a backup phone.
The lack of resources from MTK based processors is such a deal breaker. I was not aware it would be so difficult to get development going for it when I bought my phone last year.
Now I'm contemplating getting an used phone with better development support after I return my R1 HD.
I really wanted to wait until OnePlus released their new device with a better display and hopefully a near bezel less display and at least IP67 water resistance. That's the reason why I didn't go for the OP5. The upside-down screen was also another one.
If you could get the camera working in LOS than I'd hold on to my R1 HD for a a while longer. But I'm not keeping my hopes up... Just being realistic. Haha!
Thanks again!
Thanks for your support!
As of now, I've been studying the leaked MTK camera sources for other devices and using IDA to see what extra symbols and logic the stock libcameraservice.so and libcamera_client.so has. It appears that replacing these two libs was the key to fixing camera in cm-13 ports.
Thank you!
Oh, I didn't know camera support was fixed for CM 13 on the R1 HD. Maybe I didn't see it here. But I'd much rather have a non Blu version of Android with all security patches even if it's just on marshmallow.
Three days ago I just realized that Blu had a frigging app collecting my personal data and sending it back to China.
It had sent over 5.9MB of data since July 21st. I think it's a lot of data for text only transmissions.
Anyhow, I've been seeing people using Footej on other ROMs in which they could not get the camera working with stock camera app. Is that what you mean by getting the camera to work?
Stuck here guys!!!
Which recovery version do I have to install to properly flash this rom?
khyr said:
Stuck here guys!!!
Which recovery version do I have to install to properly flash this rom?
Click to expand...
Click to collapse
Dang! That's old! I guess devs should be more organized in doing a walk through with links to the files and recoveries needed to flash their awesome work.
Here's mine that I've just uploaded to zippy. I think it's the latest available and should be compatible with all ROMs.
Please report back with your findings and opinions on the ROM.
Please try to use both SIM cards to see if they work okay.
http://www8.zippyshare.com/d/p4HMiDRq/41954/R1_Port_3.1-TWRP.img
khyr said:
Stuck here guys!!!
Which recovery version do I have to install to properly flash this rom?
Click to expand...
Click to collapse
Which version of the ROM is installed on it now? Modified or stock? Which recovery is on the phone? Stock or TWRP?
I can't post pictures but it gives me an error saying that the package is for p6601 and the updated twrp image says device is Life_Max
frosted.efizzle said:
I can't post pictures but it gives me an error saying that the package is for p6601 and the updated twrp image says device is Life_Max
Click to expand...
Click to collapse
Did you download and flash the image I've just shared above?
AndroidBR said:
Did you download and flash the image I've just shared above?
Click to expand...
Click to collapse
Same error
With they recovery You provided above
Thanks for your support!
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
This is AOSP for Sony Xperia XZ1 (Poplar) (G8341)
SonyAosp build will always mainly based on AOSP with some Material stuff
Code:
/*
* 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.
*/
Code:
IMPORTANT: Make sure you have an unlock Bootloader
Please if you have Locked Bootloader you may check this http://developer.sonymobile.com/unlockbootloader/
Code:
WORKING
- RIL
- Mic
- Sound (Speaker and Headset)
- LED
- Thermal Manager
- Audio and Video Decoders/Encoders
- Camera (WIP)
- Recovery (Only for flash signed zips)
XDA:DevDB Information
[Oreo 8.1.X][XZ1 - G8341] Android Open Source Project, ROM for the Sony Xperia XZ1
Contributors
davidteri91
Source Code: http://Github.com/SonyAosp
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP
Version Information
Status: Stable
Created 2018-03-25
Last Updated 2018-03-25
Download
Follow me for be adviced for new builds
This ROM has included GAPPS
Steps for Flash
Code:
[FONT="Arial"][SIZE="3"] fastboot flash oem xxxxx.img [/SIZE][/FONT]
[FONT="Arial"][SIZE="3"] fastboot flash vendor vendor.img [/SIZE][/FONT]
[FONT="Arial"][SIZE="3"] fastboot flash boot boot.img [/SIZE][/FONT]
[FONT="Arial"][SIZE="3"] fastboot flash recovery recovery.img [/SIZE][/FONT]
[FONT="Arial"][SIZE="3"] fastboot flash system system.img [/SIZE][/FONT]
[FONT="Arial"][SIZE="3"] fastboot flash userdata userdata.img [/SIZE][/FONT]
Please make sure your device is updated to latest sony software present on flashtool due to loader requeriments
To flash oem partition you should download odm.img from https://developer.sony.com/develop/open-devices/latest-updates/
You don't need flash userdata everytime .... only first time ..... userdata.img will wipe your data... you may be adviced
Hello, is the fingerprint sensor working on this build? Thank you
Thank you for your work and providing us with AOSP. Is there a build coming for the G8342 Dual?
Yeaaaah boiisss! Now we get full worki aosp! Thank u brother!
Jenkins started new build ... Release probably tonight ... Follow me to get the news .... Stay tuned
Sent from my Xperia XZ1 (AOSP) using Tapatalk
some screens ?
davidteri91 said:
Jenkins started new build ... Release probably tonight ... Follow me to get the news .... Stay tuned
Sent from my Xperia XZ1 (AOSP) using Tapatalk
Click to expand...
Click to collapse
Twitter?
Fingerprint working
Micro SD working
Sony's aosp not support over iso 800(uditrawat's build can install magisk module to use high iso. but install on this build 'camera stopped'
kojak1989 said:
some screens ?
Click to expand...
Click to collapse
Here you go...
Everything's great so far, camera's fine, fingerprint's fine as well.
Just remember to register your device as a certified device for Google services.
SirHydarnes said:
Here you go...
Everything's great so far, camera's fine, fingerprint's fine as well.
Just remember to register your device as a certified device for Google services.
Click to expand...
Click to collapse
System Apps are from aosp oraz Google? Can you make screenshot from app drawer?
Is the fingerprint scanner working consistently? For me it says hardware not found after a few uses and it takes forever to scan my finger.
Bugs?
kojak1989 said:
System Apps are from aosp oraz Google? Can you make screenshot from app drawer?
Click to expand...
Click to collapse
Yes it comes with preloaded gapps. Minimal but efficient, it also includes google's setup wizard. Doesn't include the pixel live wallpapers. I'm working on a Flashable pack that flashes the necessary google stuff like the blue theme that can't be found in Gapps. As for gapps, I suggest you either flash aroma gapps and set it not to flash camera, or just not flash gapps since the builds include google camera and it's working just fine.
GaM3RAndroidIOS said:
Bugs?
Click to expand...
Click to collapse
From what I can gather, a bug exists and my guess is that it is because fingerprint wake and unlock is enabled. It's a feature that keeps the fingerprint sensor on when the screen is off and if you just touch the sensor without turning the screen on, the device automatically turns on unlocked. I tried finding a way to disable it but had no luck. If you try unlocking when the screen is off(touch the sensor) a few times the screen won't turn on and a force reboot is needed.
Another bug, or just a glitch is in the ui where toast messages(notifications) background color ia changed from white which is the default color to black but the text is still black and the padding in the box is more than usual.
Other than that, everything's working for me.
I've installed the march 27th build + supersu and opengapps stock and my own pack that I mentioned.
I've been waiting for a build like this and I'm keeping it on my device.
Also, one thing I noticed was that there is no battery tile, in fact there is one embedded into SystemUI but it seems to be replaced with a battery saver tile instead which is useless. I hope I either find the time to solve these problems or someone else does.
Either way, huge thanks to OP.
Thankyou very much!!!
This is my best phone so far!!
Bugs and bugs and bugs !
Sorry but since i installed your image, i keep on having bugs !
First, fingerprint is not working (works at first boot then not functionnal after a short time)
Secondly, the phone crashes all the time so i have to reboot it several times a day.
I also noticed a weird effect on the ear speaker. when i talk to my friends, i can hear myself out of the speaker. Very annoying and irritating !
I am more than surprised that no one talks about theses stuffs ...
Klonoa76 said:
Sorry but since i installed your image, i keep on having bugs !
First, fingerprint is not working (works at first boot then not functionnal after a short time)
Secondly, the phone crashes all the time so i have to reboot it several times a day.
I also noticed a weird effect on the ear speaker. when i talk to my friends, i can hear myself out of the speaker. Very annoying and irritating !
I am more than surprised that no one talks about theses stuffs ...
Click to expand...
Click to collapse
You know right that this ROM is still in the stable beta stage, and that your issues is related to lack of 100% configured & enhanced drivers from the AOSP device tree for the MSM8998 chipset (this is purely at Qualcomm and Sonys end).
This ROM is pretty much stable as it is, for now. So.
xFirefly93 said:
You know right that this ROM is still in the stable beta stage, and that your issues is related to lack of 100% configured & enhanced drivers from the AOSP device tree for the MSM8998 chipset (this is purely at Qualcomm and Sonys end).
This ROM is pretty much stable as it is, for now. So.
Click to expand...
Click to collapse
Be sure i appreciate the work you've done on this release but sorry i can't consider the rom stable regarding all the stuffs i related.
What do you think about the crashes ? Is there a workaround to fix this ?
Thanks
Klonoa76 said:
Be sure i appreciate the work you've done on this release but sorry i can't consider the rom stable regarding all the stuffs i related.
What do you think about the crashes ? Is there a workaround to fix this ?
Thanks
Click to expand...
Click to collapse
What crashes are you talking about?
xFirefly93 said:
What crashes are you talking about?
Click to expand...
Click to collapse
After a while, i can't turn the screen on. No response at all. So i have to press Vol up + Power button to switch off the phone and restart it afterwards.
Am i the only one to experience such issues ???
Hi
After LeMax2 Project Treble port, I decide to bring up to our device too. Since I've x720 6/64 variant this project was possible to me tho due to QFIL tool in case of bricks, but wasn't need thanks for god.
Project Treble as Work in progress, please read the OP before flash/bla.
and let's the party begin. check sreenshots in "Screenshots" or in the second post.
READ ME FIRST:
it's a buggy rom: I don't care about that, since I put [WIP] that mean new fixes will coming up.
Respect works of devs because they spend time and energy to do these things.
I did not tolerate ETA.
Compatible Devices:
x720: yes.
x722: yes.
x727: yes.
How is possible:
click here.
How I done:
Porting patches of TWRP to our one that I will release one for us too.
Applying the kernel patch from LeMax2 one to mount vendor on ZL1.
Compile the whole rom with Project Treble flags in device tree and proprietary blobs.
Works
Audio.
ADB.
Bluetooth.
Camera.
Display.
Fingerprint.
Graphics: hwcomposer & gralloc.
Internal Storages.
Hardware navigation buttons.
LeEco Extras.
Lights.
NFC.
RIL
Sensors.
USSD Codes: seems works
Wifi.
Bugs
Tell us more, all credits goes to codeworkx fir his fixes and works .
Installation Guide:
Copy my unofficial los to internal storage
Download my own TWRP and flash it via fastboot.
Download the partition.zip from linked thread. credits: @shivatejapeddi
Flash the whole partition.zip (don't panic if give the error it's ordinary administration.)
Go back to Wipe->uncheck all partition except the vendor, tap swipe to wipe it then.
Optional: you can go to Mount to see if mounted.
Wipe: dalvik, cache, data and system.
Now flash the whole rom that will install the vendor.img automatically, reboot device once finish installing then.
Enjoy Project Treble.
TWRP
Click here.
Credits:
LePro3 Developers.
LeMax2 Developers, without them wasn't possible for the unsed partition.
Sources:
https://github.com/hak86
XDA:DevDB Information
Treble x72x, ROM for the LeEco Le Pro3
Contributors
haky 86
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.18.x
ROM Firmware Required: EUI 20s or Newer
Based On: LineageOS
Version Information
Status: Testing
Stable Release Date: 2018-07-25
Beta Release Date: 2018-07-25
Created 2018-07-25
Last Updated 2018-07-24
** Note **
reservedddddddddddddddddddddddddddddddddddddddddddddddddddd
** Note **
Can I flash GSI by Phhusso:
I didn't try it yet, our device is ARM64 System A.
How to Flash GSI:
Download your favorite GSI rom.
Flash via TWRP or fastboot. BUT please keep attention to not wipe vendor or will not get booted, you are allowed to update vendor partition only if I release new build with fix things.
How Can I flash Android P Developer Preview 5:
Click on the following link.
Download ARM64 System A image. and 3 zips for post GSI.
Flash the system.img of Android via fastboot (recommend).
Reboot to TWRP.
Go to Mount-> check Vendor partition.
Flash the 3 zip as they arranged (1-2-3),
Reboot, enjoy Android P DP5.
NOTE:
This project has nothing to do with official updates, I did Project Treble by my initiative that will not affect with official roms. Might someone will reconsider supporting Treble even with official update tho?
Damn Congratulations!
I can't do it today. But, I will definitely try it this weekend. Thanks for sharing these test builds. I am definitely looking forward to checking it out!
Thanks again!
I will go ahead and download it and get started ASAP.
---------- Post added at 08:48 PM ---------- Previous post was at 08:41 PM ----------
haky 86 said:
Can I flash GSI by Phhusso:
I didn't try it yet, our device is ARM64 System A.
How to Flash GSI:
Download your favorite GSI rom.
Flash via TWRP or fastboot. BUT please keep attention to not wipe vendor or will not get booted, you are allowed to update vendor partition only if I release new build with fix things.
Click to expand...
Click to collapse
I just want to say again, that you are awesome for doing this, I didn't think it was possible with this phone. I am blown away! Nice job!
Hmmm can I shirk off my plans and install this right now? lol!
---------- Post added at 09:07 PM ---------- Previous post was at 08:49 PM ----------
I have a question about Gapps, Magisk and firmware.
I assume Firmware is not an issue since it would still get flashed to the correct partition. With Magisk, I assume that you would prefer that we use 16.7?
What should we use for Gapps? Do you have a specific Gapps in mind?
Wonderful Work~
Its a great! Wonderful work, now wait to fix all bugs now.
I have a doubt. Is the known bug caused by the PT partition? If flash Android P, will those bug still exist?
what should i say , it is great job !!!!!
haky 86 said:
reservedddddddddddddddddddddddddddddddddddddddddddddddddddd
Click to expand...
Click to collapse
Hi bro all fixes are completely done ,just use my trees here ,github.com/chityanj , recommend not to make changes to common tree, use as it is, where as for zl1 try make changes as per my x2 tree, yeah cam requires a blob edit in vendor, I can help u that
Any info about IR support and NFC Smartcard Service?
Most hyped project for now, congratulation. Peoples don't even woke up and already you haven't 2 pages of comments and 15 likes. Congratulation! If everything will be good I'll buy you a beer
Crystal-L said:
I have a doubt. Is the known bug caused by the PT partition? If flash Android P, will those bug still exist?
Click to expand...
Click to collapse
let me fix all those bugs and I can port the rom you want then.
shivatejapeddi said:
Hi bro all fixes are completely done ,just use my trees here ,github.com/chityanj , recommend not to make changes to common tree, use as it is, where as for zl1 try make changes as per my x2 tree, yeah cam requires a blob edit in vendor, I can help u that
Click to expand...
Click to collapse
congrats for fixes, hmm I will give a look right now. :good:
edit: what about the error in domain.te in system/sepolicy? I had to remove coredomain to let compiling go.
qqzwc said:
Any info about IR support and NFC Smartcard Service?
Click to expand...
Click to collapse
NFC already fixed just check "Works"
D1stRU3T0R said:
Most hyped project for now, congratulation.... If everything will be good I'll buy you a beer
Click to expand...
Click to collapse
O...M...G....! I see the bricking season has begun, already in summer?
Role reversal: if it (Oreo) [almost] works ......f**k with it!:good:
Good luck!
xen2001 said:
O...M...G....! I see the bricking season has begun, already in summer?
Role reversal: if it (Oreo) [almost] works ......f**k with it!:good:
Good luck!
Click to expand...
Click to collapse
) hopefully will work on x722, bcs always there is the problem.
haky 86 said:
let me fix all those bugs and I can port the rom you want then.
congrats for fixes, hmm I will give a look right now. :good:
edit: what about the error in domain.te in system/sepolicy? I had to remove coredomain to let compiling go.
NFC already fixed just check "Works"
Click to expand...
Click to collapse
Can you answer the question about Gapps?
Is a version of Gapps available for this yet?
haky 86 said:
let me fix all those bugs and I can port the rom you want then.
congrats for fixes, hmm I will give a look right now. :good:
edit: what about the error in domain.te in system/sepolicy? I had to remove coredomain to let compiling go.
NFC already fixed just check "Works"
Click to expand...
Click to collapse
hi be on permissve for now some sepolicy need to be rewritten and nuke that causes compliation issues
shivatejapeddi said:
hi be on permissve for now some sepolicy need to be rewritten and nuke that causes compliation issues
Click to expand...
Click to collapse
alright, I also forget to edit the mk files like Android.mk in the proprietary blobs probably that's why buggy.. I'll post new screenshots once got fixed :angel:
Damn, I sell my device.
Thank you for your support.
lazye53 said:
Damn, I sell my device.
Thank you for your support.
Click to expand...
Click to collapse
too late <3
well let's give this a go on x722 and see what happens .. Thanks for the hard work, it's highly appreciated !
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.