[Unofficial] [SODP] Lineage 16.0 for Xperia X Performance [EOL] - Sony Xperia X Performance ROMs, Kernels, Recoverie

Lineage 16.0 for Xperia X Performance based on Kernel 4.4
Based on SODP
By Sjll​
Download Link: AndroidFileHost
Choose the file named "dora"
OEM download : Link
How to flash:
Flash official 41.3.A.2.149
1. Wipe Data and flash in twrp
2. Flash oem in SW_binaries_for_Xperia_Android_8.1.6.4_r1_v17_tone.zip
3. Boot and Enjoy.
Feature: Performance, Gcam support.
For dual model
Add this in build.prop
Code:
persist.multisim.config=dsds
persist.radio.multisim.config=dsds
ro.telephony.default_network=9,1
Also thanks to:
Local_hero
The LineageOS Team
The CyanogenMod Team
The SODP Team.
Everyone involved in working and testing
Source code: Github
XDA:DevDB Information
Lineage 16.0 for Xperia X performance, ROM for the Sony Xperia X Performance
Contributors
Sjll
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: 41.3.A.2.149
Based On: LineageOS
Version Information
Status: Beta
Current Stable Version: 2020.4.6
Stable Release Date: 2020-04-06
Created 2020-04-06
Last Updated 2020-04-16

FEATURES AND ISSUES
Code:
- Boot: Ok
- Bluetooth: Ok
- WiFi: Ok
- WiFi Hotspot: Ok
- RIL - Phone - Data: Ok
- GPS: Ok
- Camera: Ok
- Camcorder: Ok
- Lights: Ok
- MicroSD: Ok
- Accelerometer: Ok
- Compass: Ok
- Gyroscope: Ok
- Sensors: Ok
- Touchscreen: Ok
- FM Radio: NA
- Fingerprint: Ok
- Vibrator: Ok
- Microphone: Ok
- Audio & music: Ok
- Bluetooth audio: Ok
- NFC: Not tested.
- Kernel: Ok
- Graphics: Ok
- 3D Rendering: Ok
- Clock: Ok
- DRM: No test
- Offline Charging: Ok
- USB: Ok
- USB Tethering: Ok
- USB OTG: Broken.
- Encryption: No
- SEPolicies: Permissive

Reserved 1

after a day used.i found the adb can't connect to computer use usb.and the phone is very hot.
on the log these lines are repeat.
04-08 13:02:05.767 5695 5696 I adbd : initializing functionfs
04-08 13:02:05.767 5695 5696 I adbd : functionfs successfully initialized
04-08 13:02:05.768 5695 5696 I adbd : registering usb transport
04-08 13:02:05.769 5695 31447 E adbd : aio: got error submitting read: Function not implemented
04-08 13:02:05.769 5695 31447 E adbd : remote usb: read terminated (message): Function not implemented
04-08 13:02:05.770 5695 5695 I adbd : closing functionfs transport
by the way,thank you very much for your contribution to this phone!

after install device failed verification and cannot boot. can fix this?

Thujian said:
after a day used.i found the adb can't connect to computer use usb.and the phone is very hot.
on the log these lines are repeat.
04-08 13:02:05.767 5695 5696 I adbd : initializing functionfs
04-08 13:02:05.767 5695 5696 I adbd : functionfs successfully initialized
04-08 13:02:05.768 5695 5696 I adbd : registering usb transport
04-08 13:02:05.769 5695 31447 E adbd : aio: got error submitting read: Function not implemented
04-08 13:02:05.769 5695 31447 E adbd : remote usb: read terminated (message): Function not implemented
04-08 13:02:05.770 5695 5695 I adbd : closing functionfs transport
by the way,thank you very much for your contribution to this phone!
Click to expand...
Click to collapse
You are welcome, about adb I will check it in my free time.
asepluffy said:
after install device failed verification and cannot boot. can fix this?
Click to expand...
Click to collapse
This is because of kernel has some prolems, but this doesn't disturb daily use if you boot into system.

Camera don't save photo.

Random reboot. Sertifikation filed.

Any chance to get a stable release? Although, Lineage 15.1 [stable] seems to be more popular, I prefer this ROM. The only downsides are occasionally reboots and Gcam is also NOT working properly.

jediknight23 said:
Any chance to get a stable release? Although, Lineage 15.1 [stable] seems to be more popular, I prefer this ROM. The only downsides are occasionally reboots and Gcam is also NOT working properly.
Click to expand...
Click to collapse
the phone development in xda as well as sony open devices i guess are dead. no news for few months now. i just might trade it with xz1 instead. if this phone is dead, then xz and xzs are also dead too. they belong in a same family, uses same kernel

Check this latest build
https://androidfilehost.com/?fid=8889791610682913360
I've been using it for 2 weeks
I didn't find any heat problem, gcam also works fine
It's my daily driver now

This is great news! Finally something quite stable! I'm glad Sjil is still providing updates for his X Performance roms!
After testing so many buggy roms (SODP or Treble based) in the past for this device, now I want something really stable.
Is Gcam really working now? I mean the problem that it doesn't take photos anymore after a while. Is this now fixed?
If not, i think I will use the updated and now stable Stock-based 15.1 rom.

jediknight23 said:
This is great news! Finally something quite stable! I'm glad Sjil is still providing updates for his X Performance roms!
After testing so many buggy roms (SODP or Treble based) in the past for this device, now I want something really stable.
Is Gcam really working now? I mean the problem that it doesn't take photos anymore after a while. Is this now fixed?
If not, i think I will use the updated and now stable Stock-based 15.1 rom.
Click to expand...
Click to collapse
Gcam works fine
I've tried parrot 7.0 HDR v13, trcamerav5 reborn, pixelcam dise 1.2
I don't have any issue so far

How to build LOS with sodp?

Great to see Lineage OS 16 being brought to the SXXP! Thanks!!
I'm on the 15.1 SODP ROM right now, would you recommend switching to the latest build here? Is there anything I need to do before flashing, considering I already flashed the 15.1 ROM before?

leandrox said:
Great to see Lineage OS 16 being brought to the SXXP! Thanks!!
I'm on the 15.1 SODP ROM right now, would you recommend switching to the latest build here? Is there anything I need to do before flashing, considering I already flashed the 15.1 ROM before?
Click to expand...
Click to collapse
You can factory reset your device (wipe menu>advance>check "data" then proceed the wipe), then flash the rom
It have same OEM , so basically you dont need to flash the OEM image again

I'm stuck with a message "encryption unsuccessful". I tried to wipe dalvik and cache after rebooting in twrp (I'm using twrp-lineage-stock). Too bad I'm so found of lineage since I used it with my old motorola moto... Maybe the trouble come from my previous try with AOSP wich didn't work ?

campanah said:
I'm stuck with a message "encryption unsuccessful". I tried to wipe dalvik and cache after rebooting in twrp (I'm using twrp-lineage-stock). Too bad I'm so found of lineage since I used it with my old motorola moto... Maybe the trouble come from my previous try with AOSP wich didn't work ?
Click to expand...
Click to collapse
First flash your phone with 41.3.A.2.149 firmware
(if you did'nt on that firmware yet and backup your data first before flashing your phone)
And use this TWRP
That twrp doesnt support f2fs format , so format your partition to ext4 , and idk if the rom support f2fs or no

This was working really well for me, but unfortunately I need encryption. Mostly out of curiosity, do you know what's preventing this from working?

amnesia1408 said:
First flash your phone with 41.3.A.2.149 firmware
(if you did'nt on that firmware yet and backup your data first before flashing your phone)
And use this
That twrp doesnt support f2fs format , so format your partition to ext4 , and idk if the rom support f2fs or no
Click to expand...
Click to collapse
Thanks ! Actually for the moment I'm trying to install GSI treble rom project and your twrp helps me a lot, even if I still not quite succeed !

Related

[ROM][P905][UNOFFICIAL] LineageOS 14.1 | Android 7.1.2 Nougat 20180117

I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
This firmware was developed for the p905. It doesn't apply to the p905v at this time because it's bootloader locked and a custom recovery isn't possible.
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
I'm using nano gapps.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Root
Settings -> About tablet -> press 7 times "Build number"
Then Settings -> Developer options -> Root access
Work
Almost all work: calls, mobile data, wifi, bluetooth, sound, vibra, camera (photo), sdcard, mtp, otg, pen, gps, ir
Known Issues
1. Sound issues: volume during a calls
About crash in the dialer
If you upgrade with the old firmware (7 version or less), most likely you will get a crash in the dialer, at least I got it.
There are 2 options to solve the problem:
1. clean install the latest version
2. in any file manager (es explorer, solid explorer or other) as root go to the folder data\data\com.android.dialer\databases and delete both files (dialer.db and dialer.db-jornal). It will be recreated on next dialer launch.
Links
LineageOS Builds:
22: 20180117: security patch level - January 5, 2018: https://drive.google.com/file/d/1Ve3kwcnj-JgcNdNE5R9Uep-bAmUCuMLp/view?usp=sharing
21: 20171212: december security patch: https://drive.google.com/file/d/18vfml3oI3ycWBIVV_wvMpe4BFQ6RzwS5/view?usp=sharing
20: 20171012: version for test, flip cover: https://drive.google.com/file/d/0B-6nm7Jks0W5YnJZdW5raklRTEk/view?usp=sharing
19: 20171011: version for test, latest code + root: https://drive.google.com/file/d/0B-6nm7Jks0W5SHNHQmszdkdlY0E/view?usp=sharing
18: 20171010: version for test, new kernel (based on samsung_msm8974), new device config, offline charging is fixed now: https://drive.google.com/file/d/0B-6nm7Jks0W5ZjJyMEFFbG9vTFE/view?usp=sharing
17.1: 20171005: alternative build (with october security patch) with another kernel: https://drive.google.com/file/d/0B-6nm7Jks0W5RTJrdXc1a1VZNEE/view?usp=sharing
17: 20171005: october security patch: https://drive.google.com/file/d/0B-6nm7Jks0W5eDNCQlpjb3dua2s/view?usp=sharing
16: 20170823: august security patch: https://drive.google.com/file/d/0B-6nm7Jks0W5Zng0X2JFNzVhanc/view?usp=sharing
15: 20170711: experimental build with lt03lte kernel, wifi tethering (thanks davidmueller13), july security: https://drive.google.com/file/d/0B-6nm7Jks0W5WTg5Ry1VeEtUOWc/view?usp=sharing
14: 20170619: experimental build with lt03lte kernel, cm14.0_alt brunch, should be more stable, fixed ramdom reboots on 905m: https://drive.google.com/file/d/0B-6nm7Jks0W5MEh5ZWE0d1Bwd1E/view?usp=sharing
13: 20170606: june security patch, you can use latest opengapps: https://drive.google.com/file/d/0B-6nm7Jks0W5MXJBdVMydU8yMms/view?usp=sharing
12: 20170516: opengapps still dnw, you can use Beans GApps: https://drive.google.com/file/d/0B-6nm7Jks0W5TFBUdlF3TXBRS1E/view?usp=sharing
11: 20170420: android 7.1.2, warning - google apps from opengapps still DNW, for now you can use https://forum.xda-developers.com/android/software/gapps-dynamic-gapps-t3487192 : https://drive.google.com/file/d/0B-6nm7Jks0W5UjMtdmxpczFzRHc/view?usp=sharing
10: 20170411: still no april secury update: https://drive.google.com/file/d/0B-6nm7Jks0W5elB0WDZUdnRfaG8/view?usp=sharing
9: 20170405: https://drive.google.com/file/d/0B-6nm7Jks0W5UkI0M0I2aF8tWjA/view?usp=sharing
8: 20170307: https://drive.google.com/file/d/0B-6nm7Jks0W5ajNSYUhrWnk0MTA/view?usp=sharing
7: 20170127: now with root: https://drive.google.com/file/d/0B-6nm7Jks0W5VTc0Q2tiLU05RGc/view?usp=sharing
6: 20170126: https://drive.google.com/file/d/0B-6nm7Jks0W5bE5USWxTS05JZFk/view?usp=sharing
5: 20170117: https://drive.google.com/file/d/0B-6nm7Jks0W5TldOOWhjc3Y3czg/view?usp=sharing
4: 20170113: https://drive.google.com/file/d/0B-6nm7Jks0W5NWxiZ1VqdUp3eEk/view?usp=sharing
3: 20170108: camera (video recording) - done, microphone in the skype - done: https://drive.google.com/file/d/0B-6nm7Jks0W5MmtmWXpjTmlOdTg/view?usp=sharing
2: 20170105: https://drive.google.com/file/d/0B-6nm7Jks0W5SEdKbWFMbE1IaFU/view?usp=sharing
1: 20161231: https://drive.google.com/file/d/0B-6nm7Jks0W5b0gtQ2V1WktvS1E/view?usp=sharing
CyanogenMod Builds:
18: 20161226: https://drive.google.com/file/d/0B-6nm7Jks0W5U3draHFsTFJBNFU/view?usp=sharing
17: 20161213: https://drive.google.com/file/d/0B-6nm7Jks0W5TEZtczBuN1ZvQzQ/view?usp=sharing
16: 20161207: now android 7.1.1: https://drive.google.com/file/d/0B-6nm7Jks0W5MUZlei1wdFdQRTA/view?usp=sharing
15: 20161205: https://drive.google.com/file/d/0B-6nm7Jks0W5cHpoekNfWlRTc2c/view?usp=sharing
14: 20161129: https://drive.google.com/file/d/0B-6nm7Jks0W5bUV1R3BYcW1WekE/view?usp=sharing
13: 20161120: now enforcing: https://drive.google.com/file/d/0B-6nm7Jks0W5d19VYU9LVml2NDg/view?usp=sharing
12: 20161116: test version, all of the proprietary files updated: https://drive.google.com/file/d/0B-6nm7Jks0W5dW5fSXN4WjhBOGc/view?usp=sharing
11: 20161113: https://drive.google.com/file/d/0B-6nm7Jks0W5UWM0Qm1VaUxWMlE/view?usp=sharing
10: 20161109: https://drive.google.com/file/d/0B-6nm7Jks0W5U19TMG16Q1R2bE0/view?usp=sharing
9: 20161107: https://drive.google.com/file/d/0B-6nm7Jks0W5WUx1UVF0X0Y5eFk/view?usp=sharing
8: 20161106: mobile data work: https://drive.google.com/file/d/0B-6nm7Jks0W5MGZTLVk4VFBtQVE/view?usp=sharing
7: 20161030: initial cm14.1 (Android 7.1), you need gapps 7.1: https://drive.google.com/file/d/0B-6nm7Jks0W5VTFib05mb3JNS3M/view?usp=sharing
6. 20161023: https://drive.google.com/file/d/0B-6nm7Jks0W5UjRUWUFiOUNWYXM/view?usp=sharing
5. 20161019: fix gps: https://drive.google.com/file/d/0B-6nm7Jks0W5eUtvUUJRdTFPOUU/view?usp=sharing
4. 20161018: mobile internet now is working https://drive.google.com/file/d/0B-6nm7Jks0W5NXFhSWxSTEM3UTg/view?usp=sharing
3. 20161016: thank davidmueller13 (fix camera), bluetooth now is working https://drive.google.com/file/d/0B-6nm7Jks0W5THVjalNjNEhRSEU/view?usp=sharing
2. 20161012: kernel update, still working on bluetooth and camera: https://drive.google.com/file/d/0B-6nm7Jks0W5QURJSVdaejJaclE/view?usp=sharing
1. first public, but still very draft version: https://drive.google.com/file/d/0B-6nm7Jks0W5cWRDWEViMVY4RUE/view?usp=sharing
Gapps
http://opengapps.org/
Platform: ARM
Android: 7.1 (or 7.0 for cm 14.0 verions)
Recovery
Official TWRP: http://forum.xda-developers.com/showthread.php?t=2706982
Sources
cm14.0 branch, in readme file (see device tree) all instructions for build.
Sources: https://github.com/CyanogenMod/
Device: https://github.com/Valera1978/android_device_samsung_viennalte
Kernel: https://github.com/Valera1978/android_kernel_samsung_viennalte
Vendor: https://github.com/Valera1978/android_vendor_samsung_viennalte
Thanks
Thanks to CyanogenMod team
@Valera1978: great news... Many thanks...:good:
this is good to see!!
p900 owner, but just as exciting to see 7.0 come so fast! the newer multi window style might get me to finally ditch TW
edit: cm14 still not even available for Qualcomm versions of note 4 -- a newer and more popular device. you were fast indeed!
I'll wait until the build stabilises but it's great to see you working on a Nougat build.
Does it work with sm-p902 ? Similar to p901 , sim card 3g version, thank you by the way
Does this have OTG support or is it treated the same as CM13?
I want this to stabilize and firm up in terms of updates before I jump in but damn I am drooling for that built in multi-window update. Just thinking about the types of modules that will be created that will build off this work is bringing a grin to my face.
Thanks a lot!
One more bug - no data connection.
WiFi works excellent. Stylus works too.
---
@Valera1978
Thank you for this my friend!
You're the best dev ever!
Exiting!
Will install and test soonest.
Many thanks for making our tablet interesting again
WOW! Guys, thanks so much! If I wasnt using my NP12 so much for work right now, I'd be all over this.
@Valera1978
Bro, thank you very much for your AWESOME work!
Nice but WLAN Not working since cm13
just wondering...
So has anyone tried this yet? I really want to try this but curious as when a more stable build will come out & address the known issue... bluetooth & camera the big ones... ALSO are the only known issues with the 3 issues of bluetooth, camera, & no data connectivity? (But wifi works) any replies or comments would help out.
@Valera1978 , really? THIS IS AWESOME MATE!! my 2-year-old NP12.2 is getting nougat faster than my 2016 phone!!
can someone please post screenshots and feedback about the newest version
I'm trying to install the latest version (cm-14.0-20161019-UNOFFICIAL-viennalte) and just after "Patching system image unconditionally" I'm getting:
E:unknown command [log]
E:unknown command [log]
Then it continues to ...done
Should I worry about that?
mrjester said:
I'm trying to install the latest version (cm-14.0-20161019-UNOFFICIAL-viennalte) and just after "Patching system image unconditionally" I'm getting:
E:unknown command [log]
E:unknown command [log]
Then it continues to ...done
Should I worry about that?
Click to expand...
Click to collapse
No, thats an "issue" on all cm14 Roms. Get the same on oneplus3
There wont be an issue in the rom because of that
@Valera1978
Thanks bro for the last update!
The rom is AWESOME!
You are the best dev ever!

[JDCTeam][TREBLE][v6 RC2][Gemini] The Full Treble support project

{
"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"
}
The Full Treble Project for MI5 Gemini
Brought to you by Jflte DevConnection Team​
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We're 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 TREBLE
* SUPPORT before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
What is Project Treble:
Project Treble basically partitions your device into two separate partitions, a system and a vendor: system contains your generic system image, while vendor partition has your device specific files required for booting and running your phone. This way we can easily change the system image and be able to run our device on different system images with the same kernel and vendor partition
Read more about Project Treble
Gemini hardware vs Treble implementation:
Gemini is an ARM64 and A-ONLY device. This means that regarding the GSI images (GSI = Generic System Image) to be used, you need to get ARM64 and A-ONLY system images.
Available GSI downloads:
Up today, thanks to @phhusson and other devs, are available a bunch of Android 9.0 system images that can be flashed on Gemini.
You can find these Gsi at the following links:
- ANDROID Q (Gsi)... Is just a preview... but it works on our Mi5!!
- Phh AOSP 9.0 (Gsi).
- Resurrection Remix v7.0 (Gsi).
- LineageOS 16.0 (Gsi).
- HavocOS v2.0 (Gsi) (Use A only).
- ViperOS v6.0 (Gsi) (Use A only).
- JDC AOSP 9.0 (PURE AOSP Gsi, built from sources, just for testing purpose, no gapps support for this preview version).
- GSI & sGSI List page
Treble implementation and download:
JDCTeam is working from latest months of 2017 to implement on Gemini (un-supported from producer) the full support of Treble.
Thanks to @sir mordred, we reached on MI5 the full working status... from v5 we moved to full versioned vndk v28 (aka PIE support... and Q ready!).
NOTE: just to be clear, it's a work in progress development...
We tested with some available Gsi and we put over here some links to these images.
We are sharing a TWRP flashable zip that include vendor and boot images (flash only through TWRP 3.2.3-0 Official).
NOTE: ONLY with TWRP 3.2.3-0 version is possible to handle the treble flash!​
How to use:
Download the TREBLE zip provided here: Mediafire
Download a GSI image (Remember: ARM64 and A-ONLY version)
Reboot to recovery (TWRP 3.3.1-0 REQUIRED)
Clean the device (wipe Dalvik/Cache/System/Data partitions)
Flash Treble gemini zip
Flash the GSI system image you wish to use
Reboot
---> Video on How to install <---
Screenshots:
Youtube review: (To Be Updated when new links available)
- ANDROID Q Gsi on MI5 (How to Install) ---> Click here to play the video
- ANDROID Q Gsi on MI5 ---> Click here to play the video
- RR v7.0.0 Gsi on MI5 ---> Click here to play the video
- PHH AOSP 8.1 Gsi on MI5 ---> Click here to play the video
- AEX 8.1 Gsi on MI5 ---> Click here to play the video
What's working (... and not working):
The development is now @ an RC status (this is not a rom)... you have the possibility to have a look and test the phone with a GSI rom... let us know what does not work (not related to the GSI itself)!!
Issue reporting:
We already say that this is not the place to report issues or bugs ROM related... but in any case a bug encountered can be linked to the treble support not perfect or missing supported features... be free to post about issues you encountered, and please provide logs with the description of the issue. We will check the logs to understand the reason, and in case of fixes to be done, we will update on post#3 (MISCELLANEA) a kind of todo list for us and for users as a "bug list"... but the meaning is "what has to be checked/fixed to get a better treble support for future".
Any question?
If you have any question about, please check first on the post#2 (FAQ) to see if your question has already an answer... if not, post in the thread and we will give you informations.
Sources
GitHub
Social
YouTube: JDCTeam TV
XDA News: Read article
Credits
JDCTeam
LinageOS
Google
MI5Devs
Special thanks:
@sir mordred (developer)
@musabcel (for his test support)
Team Codefire - JDCTeam-Build03
XDA:DevDB Information
GEMINI Full Treble support project, ROM for the Xiaomi Mi 5
Contributors
smeroni68, sir mordred, mzo, ktulu84
Source Code: https://github.com/Project-Treble-Mi5
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest available
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: v6
Stable Release Date: 2019-03-16
Created 2018-03-10
Last Updated 2019-06-27
FAQ Section...
This is the FAQ (Frequently Asked Questions).
Have a look here before asking in the thread... in the worst case you will not find the answer you are searching!
If this section is useful for most users needs, I'll be glad to continue investing time to update this Q/A list!!​​
Q1:Fingerprint wake/home button works?
A: Yes, now we have the complete support and this feature is available on standard GSI roms (treble support is ready for it)
Q2: How can I revert back from treble to custom ROM whenever required?
A: Just flash the custom rom you like from TWRP and that's all. Custom rom flash will overwrite the boot.img,system and vendor partitions.
Q3: If I revert to a Custom rom, what I need to do to restore treble support?
A: Just flash the Treble zip through TWRP as the first time. Treble support need boot.img and vendor.img to be installed into the phone... nothing more... nothing less...
Q4: Phh GSI rom is quite poor in functionality. Why?
A: The purpose of Phh GSI AOSP rom is not to be a custom/featured rom. It is an experimental project that is born to have a common rom (better to say the same system.img) usable on many devices with treble support.
This support can be native, acquired after an Oreo original update or as we have done a custom integration on an "unsupported" device.
The meaning today of using a GSI rom is not to be a perfect rom for dayly use... or let's say, it can be a dayly rom only for users that like pure vanilla code.
In future we hope that many others custom roms will move to be a GSI (as JDC will try to do), so we will have the treble base to use these new project also on our devices.
Q5: If a new version of treble support is out, did I need to flash it or not?
A: Our project is on the way. This means that if is available a new update from us, it is for sure an enhancement with more support of feature or fixes.
In case you will need to install a GSI rom, check always here if there is any new version and get it.
In case you are running a custom rom without treble support, DO NOT update with treble flash, because most probably you will break your current installation.
Treble flash is 100% safe from the phone point of view... isn't safe for your current installation!! Why? Mainly because your current boot.img will be overwritten with treble support... 99% you will get a bootloop with a not treble rom!
Q6: How to get ROOT on phh gsi?
A: Firstly download the phh-gapps-su image. After installation, go to the market and install "phh superuser" app to manage the su access for the apps that need it. In the other cases, you can flash from TWRP the correct Magisk zip to gain root.
Q7: Where I can find the GSI images available?
A: Have a look in the OP post over here... there you can find the available ones. In any case here the LINK to the Treble Enabled Device Development section on XDA or here on GSI & sGSI List page
Q8: Everytime I entered the password, it says Decryption Unsuccessful!
A: You have internal SD encrypted. If after MIUI stock, you haven't FORMATTED the internal SD (FORMAT is not WIPE... Format will erase all data and files from the phone, so you must know what you are doing before formatting), the phone result as encrypted, so the rom is asking the password to decrypt the datas... Decryption Unsuccesful clearly states that the decryption procedure is not working. Post about the issue on the GSI rom you are using and provide logs to the developer to help digging the problem... if Developer will answer that encryption is not supported, you can only do one thing: backup all your data, files and pictures on an external storage (eg. a PC) and procede with a FORMAT DATA from TWRP to "destroy" the encryption and "free your phone from it"!
Q9: Is Google Camera working on Gsi?
A: Yes. But remember you need to install gapps package to let gcam works as it should.
We tested Gcam up to v6.1.021 on AOSiP Gsi. If you have greenish selfies pics, go in the Settings -> Fix ->and enable the fix for Front Camera and reboot. For SlowMotion, set 120fps.
Q10: Why can't flash a micro gapps and only pico is flashable?
A: If you get an error of Insufficent space on system partition, you need to resize the partition. Do in this way:
Flash the SYSTEM.IMG you wanna use (select a Vanilla based one)
Reboot to RECOVERY
MOUNT the SYSTEM partition
Go in WIPE menu -> ADVANCED WIPE -> select SYSTEM from the list and press the button REPAIR OR CHANGE FILE SYSTEM
select RESIZE FILE SYSTEM
than SWIPE to execute the command...
in case of error (you will see in red), repeat the RESIZE until it goes completed (Resizing... Done)
After this operation, the system partition will be resized to his maximum dimension (on Mi5 is around 2992MB)
before the installation of gapps package, do a REBOOT to recovery and after MOUNT the SYSTEM partition (check that it is really mounted)
Now you can flash the micro gapps without problem.
Q11: Is there any Magisk version working on Treble gsi?
A: Yes, you need to get v18.1 version or newer with treble support (check around).
Q12: VoLTE is working[/B]?
A: Yes. Install this ims.apk to use it!
Q13: ADB Logs are needed in case of Issue reporting...
A: In case you need help and want report an issue (eg. a boot problem), we need logcat of the phone. Just as sample, we report here what to do (but you must able to do by yourself... we are not giving help on how to do...)
prepare a PC (with adb package to support debug via usb connection)
flash on the phone our treble and the GSI image (just these 2 files, not any patch or other stuff)
reboot the phone
connect the usb cable
after the Mi logo screen, wait to hear from PC a sound that means the usb periferial has been recognised
go in a command window and type:
--> adb devices (if the phone is connected, you will see the code written after the command executed)
--> adb shell logcat > bootlog.txt (this will start real time recording of logs into the pc in the bootlog.txt file)
--> when the phone has completed boot/reboot (eg. a boot loop or fastboot), you need to press Ctrl+C from keyboard to stop log recording.
send attached to the issue description post the bootlog.txt
...let's dev check what's happening by reading the logcat.
... list will be updated...
Miscellanea...
Download (public versions history)
Here you can find the shared folder with all the version released of Treble support: GEMINI-TREBLE
Changelog's
v6 (20190316) - Release Candidate 2 full versioned_vndk v28
- VERSİONED_VNDK support is fully implemented
- FIXED NFC support
- FIXED Ambient Display main icon size and settings menu icons style... Thanks to Subezhj for helping fixing.
- FIXED ConfigPanel - Fingerprint settings menu icons style
v5 (20190308) - Release Candidate full versioned_vndk v28
- VERSİONED_VNDK support is fully implemented
- Mostly all library dependencies between system/vendor which are called as violations against treble's rule are succesfully eliminated
- Updated kernel as per treble's kernel docs (enforced)
- Vendor image's version is now 28
- Misc updates and fixes
- GSI Pie roms support (check in OP for some links)
- JDC PIE GSI rom given just as a preview for testing (JDC PIE GSI is build from sources without ANY hack!!)... It's pure AOSP as Google bring to their devices... NOTE: No support for gapps... they do not complete setup... you are advised.
v4 (20180409) - Beta partially versioned_vndk with the following updates:
- VERSİONED_VNDK support is partially implemented
- Lots of library dependencies between system/vendor which are called as violations against treble's rule are succesfully eliminated, only small number of lib dependencies which needs to be resolved are left
- Updated kernel as per treble's kernel docs
- Vendor image is now using google's stock vndk-sp, ll-ndk libs which are called as treble layer libs
- Vendor image's version is now 27.1.0
- Misc updates and fixes
v3 (20180329) - Beta status with the following updates:
- Updated camera Hal from latest qualcomm 8996 repo
- Hexedited more libs and removed more vendor system dependency (better treble and preparation for versioned vndk)
- Updated wifi configs from lates CAF
v2 (20180318) - Still alpha build with the following updates:
- Upstreamed kernel
- Hexedited blobs to correct path (for treble)
- Linker issues fixed
- Vendor overlays
- Latest device tree updates from CAF and miui oreo beta
- Disabled non-working apps (custom xiaomi doze package and configpanel app which were designed to work with LOS APIs)
- Disabled userspace thermal hal initialization which we dont have in cameraHal (faster cam launch)
- Increased jpeg quality parameters
- other misc. dev tree updates
v1 (20180310) - Initial release (Alpha)
Reported/Known Issues
- Camera works perfectly, but on some apk after a shot is taken with Flash active, the camera do not get more pictures... Close the app will clear the issue and you can get other pictures! Suggestion: do not use the flash with this camera apk if you have the issue! ... or use a working camera apk (is a better solution)!
to be updated...
Big thanx and credits also goes to @smeroni68
All of the story is started with the identifying unused CUST partition which xiaomi left on our device Mi5 https://forum.xda-developers.com/showpost.php?p=74702470&postcount=300
And after we determined that the /cust partiton is unused on AOSP roms, we used it as /vendor partition as per the requirement of Full-Treble https://github.com/sirmordred/android_device_xiaomi_gemini-twrp/commit/5faf9c4e162e8144b71f87d6d21c384931b1ac0c nearly 3 month ago
And that is also the reason of nearly all devices which get Full-Treble support via custom implementation, are Xiaomi devices (Redmi Note 4, Mi5S and our Mi5)
Thanx also to my teammates who contributed this project :good:
Our goal is now separating/isolating all vendor <=> system interactions (which will be enforced on future android releases for treble devices) and stabilizing vendor.img while getting closer to pure AOSP sources
Enjoy
...
...
Finally we are out for both MI5 and MI5S... yeah... now let's go ahead...
Thanks for all JDCTeam
Great Job dude! Finally we got treble. Downloading now. Can't wait flashing.
通过我的 MI 5 上的 Tapatalk发言
Thank you Sir, downloading now
Great news ..only one query .. How can I revert back from treble to custom ROM whenever required?
kishan314 said:
Great news ..only one query .. How can I revert back from treble to custom ROM whenever required?
Click to expand...
Click to collapse
Good question... I'll report also in post#2 in FAQ section.
Q: How can I revert back from treble to custom ROM whenever required?
A: Just flash the custom rom you like from TWRP and that's all. Custom rom flash will overwrite the boot.img and the system partition... vendor partition will stay there waiting for your next test!
So... P GSI is coming for the "old" Mi5. Thank u guys! This is the way
atembleque said:
So... P GSI is coming for the "old" Mi5. Thank u guys! This is the way
Click to expand...
Click to collapse
This is something we can try to build... but only when sources of P will be released and will be good to build an AOSP based on them...
Very very thankful
Thanks for your hardwork, downloading now.
When charging, the battery icon won't show. The bug is phh's?
Sent from my MI 5 using Tapatalk
Installed. Yeap, we finally got a vanilla android
For first alpha, it working flawlessly.
Some bugs i founded.
1. After magisk install on stock kernel, got bootloop. Fixed after installing AEXMod latest kernel.
2. Gcam not working. buildprop (vendor folder) doesnt help. Got FC anyway
3. HMP... stock governor settings cant provide smooth scrolling in settings, 820 sd stuttering like 210, okay. It happens on every gemini hmp kernel on 8.1 oreo. Maybe some to perfd related. Need EAS.
4. Gpay wont work, magisk can't help, maybe device id change will help
All other working fine
MichaelPan01 said:
When charging, the battery icon won't show. The bug is phh's?
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
Here it is working.
Have you set the battery icon visibility status under the statusbar settings?
StealthHD said:
Installed. Yeap, we finally got a vanilla android
For first alpha, it working flawlessly.
Some bugs i founded.
1. After magisk install on stock kernel, got bootloop. Fixed after installing AEXMod latest kernel.
2. Gcam not working. buildprop (vendor folder) doesnt help. Got FC anyway
3. HMP... stock governor settings cant provide smooth scrolling in settings, 820 sd stuttering like 210, okay. It happens on every gemini hmp kernel on 8.1 oreo. Maybe some to perfd related. Need EAS.
4. Gpay wont work, magisk can't help, maybe device id change will help
All other working fine
Click to expand...
Click to collapse
1) Phh rom support natively Phh superuser app (from market) with stock kernel and phh-gapps-su gsi image.
2) Gcam require API2/HAL3 support, and on phh gsi hasn't been implemented (as written is an experimental rom with the meaning to be compatible with stock Oreo treble devices). Instead, it has API1/HAL1 support for stock vanilla camera.
3) Stock kernel is HMP. We do not develop till now the EAS kernel on stock treble kernel (we will do for our JDC gsi).
4) Magisk is clearly reported into Phh thread to not be used. In custom development we have a plus, because we can change the kernel (as you have done)...
Thanks for this testing report.

[Treble][ARM64][AOSP][J730X]Project_Spaget X

{
"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"
}
Welcome to Project Spaget X ARM64 Treble For Galaxy J530X/J730X/G610X/J701X/J710X​
Some information you should know..
This is a full Treble ARM64 Vendor/Kernel implementation for the Exynos7870 Supported devices
If you want to report a Bug, read the F.A.Q First Then provide a logCat OR LoggingKit.zip with detailed explanation
Read the instructions and the F.A.Q Before installing the rom or posting a reply.
[FOR DEVS] You are allowed to customize this vendor if you want to use it in ROMs with proper credits. but not to distribute 1:1 copies
- Personal Notes
And here we are, few leaks and reworks later. X is here. i went with a letter this time just because it looks cool. This is officially going to be EOL for ARM64 AONLY vendors that i make (unless a critical bug was here that needed attention) . i dont have alot of time to work on 7870 And when i do i prefer it to be on something more productive than Treble
Anywya, TLDR : alot changed, alot was fixed. its a new vendor, flash and enjoy
Old releases
Alright, The "second" Treble update is here, this time it is FULLY ARM64 compatible. Thanks to the hard-work of @Astrako who managed to boot ARM64 Exynos 7885 bases on our device. This project is HEAVILY based on his work. and i would like to make that very clear. This is not a OneMan job. this took alot of hardwork by many people to make it reach the stage it is at. basically we are official minus the tag. This project is also possible thanks to my dear friends @Kique119 @me2 @SPARTANICUS and my other testers who spent day and night testing this with me.
At this stage, everything is mostly GSI related.
And finally, the cherry on top, is support for 3 more devices. Thanks to the devs who assisted me on adding support for their own devices. mentioned below.
If you appreciate this ambitious project, consider hitting thanks, supporting the thread, and donating (Paypal) to support my development (using cocaine of-course)
- Initial Notes:
Supports ONLY the mentioned devices Above
1. Don't forget to check bugs before asking questions
2. Since most of the GSIs are AOSP, forget about VoLTE, Knox features, Samsung apps, Camera mods or features, or other Samsung related features.
3. You can use any non-treble rom even if you have treble vendor installed, as long as you flash a non-treble kernel. The rom will ignore your vendor and everything will be as non treble.
- General Features :
- based on G965F Vendor with VNDK-28
- Adapted to J730/J530/G610/J710/J701 devices
- latest CronosKernelV5 included with most of the features of OneUI kernel + many more
- misc things enabled in framework overlay for better experience
- Seamless GSI patching, without user intervention
- Seamless setup process, with dynamic Scripts
- And Spaget
- How to Install Project Spaget:
- Flash `Exynos7870_CreateVendor` and reboot recovery
- Flash `Exynos7870_Spaget_X`
- Flash your desired ARM64_AONLY GSI
- Read OPTIONAL below
- What GSIs are support/recommended ?:
- Avoid sGSIs and flash source built GSIs (Such as PHH,PE)
- ARM64_AONLY GSIs only
- I recommend Pixel-experience or evo x and luke GSIs
- if you want a daily rom. avoid sGSIs
- More can be found here : Treble
- I dont have googleapps. what do i do ?:
ONLY for gsis that does not come with google apps
- Download Gapps pacakge from Here (ARM64 > VER > Micro or lower
- Go to TWRP > Wipe > Advanced Wipe > Tick System > Repair > Resize
- Flash opengapps_xxxx
- I need more info. where do i get it ?
Ask in this thread. if you need more , head to
Spaget Notes and support : Telegram Group
General bugs (GSI):
- offline charging is broken in Android 10 roms
- Bluetooth Calls
- Some GSIs might not include a camera, use Footej
- Some camera apps will have stretch
- I dont like it, how do i revert ?:
- Reboot to recovery
- Flash `Exynos7870_RevertVendor`
- Reboot recovery
- Flash any non treble rom or restore your previous twrp backup
Is that all ? I have treble now ? what about all the complicate process before ?
Yes, you now have a project treble device, ready to flash any GSI/sGSI of your choice aslong as it fits in your SYSTEM partition.
The entire process changed and now is much more seamless and noob-friendly. yet take caution as always
What if i didn't boot ?
In some cases, you might be stuck at a bootanimation loop or a splash loop, in this case follow the troubleshooting steps in the F.A.Q post
Credits
@corsicanu For great help with the repartition scripts, GSI patching and tons other throughout the years.
@Astrako for making booting ARM64 a possibility. and allowing this project to exists. kudos
@Kique119 For his awesome testing and documenting this project, without him there would be no spaget
@KassemSYR, for G610F Support and testing.
@Zero_Cool7870 , @DAvinash97 , @mohitsama and ORIGINALNAME123 for J710/J701 support
@SPARTANICUS For his great work maintaining KRAKEN kernel, which supports this project fully
Testers :
@Kique119 @LuanTeles @ion1s @djedjy @vsmhell @fetaiharbin @Mizo2019 @Me2 @LelMwhLwl @@rlukas210
@PedroDomeneghi @DaffyMirror4318 @bien2004official @AleeX157 @Alijouhara
And many more i cant remember the usernames of. please mention
Downloads. Changelogs , F.A.Qs below
OldPost (a64)---
So, i have been hesitated to release this project since last year. GSIs are not the most stable and many J users prove they are unable to read. they just want ready stuff. with this project that is not the case. if you skip the instructions/F.A.Qs and notes, dont bother installing this project as you probably wont be able to get it running.
This is a fully featured VENDOR and KERNEL designed for this device to support project treble, it is based on other Exynos 7870 Vendors and modified to support our devices, i have also added few patches and updates that even official 7870 vendors do not have. to get the best possible experience
I have also added a GSI_PATCH zip that should be used if you want to have the least amount of bugs.
The vendor is pretty much bugles, therefore any bugs you face, Report them to the appropriate Threads of the GSI you installed. or github issues section. as those are not mine to fix. i only provide the vendor and kernel that allows GSIs to run on.
- STEPS FOR INSTALLING TREBLE VENDOR:
Flash “Treble_Jx30F.img” in TWRP as Image (Selecting RECOVERY)
Reboot recovery.
Wipe System, Data, Dalvik and Vendor.
Flash "jxy17lte_Vendor_9.0_v1.0.zip".
- STEPS FOR INSTALLING GSIs:
Download the desired GSI (it MUST be arm_binder64/A64 Variant)
unpack it if it wasn't in .IMG format
Go to TWRP , Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Flash "GSI_Patch.zip".
[OPTIONAL] Flash the “Gapps_patched.zip”
- STEPS FOR INSTALLING GAPPS:
If you flash Gapps, Google will spam you with fullscreen warnings and notifications about your device not being certified. But don't worry, you can certify it.
Just reach the homescreen, then proceed to install the "Device ID.apk". Use it to grab the Google Services Framework ID and paste it here: https://www.google.com/android/uncertified/
And paste the ID there. Then wait a few minutes and reboot. Few seconds after rebooting, you'll be done and you'll be able to normally log in as always.
- [OPTIONAL]STEPS FOR INSTALLING Magisk_GAPPS:
** Note : This gapps is recommended for all **
Download latest gapps from http://opengapps.org
place in /sdcard or /external_sd
flash magisk.zip
flash magiskgapps.zip
- Confirmed working GSIs :
** You can only use ARM_BINDER64 / A64 GSIs **
PHH AOSP V113 : Github
OmniROM GSI : XDA
Liquid Remix : GoogleDrive
Pixel Experience With Gapps : GitHub
Resurrection Remix : RR
XenonHD : TeamHorizon
P.S : only Omni and PHH Do not require the GSI_PATCH_FP The rest do in order to get Fingerprint working
- Known GSI Bugs:
Bluetooth calls are broken
Some 3rd party cameras have stretched pictures
And more here at Github Issue
Credits
@corsicanu For general help through out the years
@prashantp01 For overlay fixes and native camera fix. and other contributions
@Kique119 For his awesome testing and documenting this project
Testers :
@Kique119 @LuanTeles @ion1s @djedjy @vsmhell @fetaiharbin @Mizo2019 @Me2 @LelMwhLwl
And few more that didn't give me their usernames
Downloads. Changelogs , F.A.Qs below
XDA:DevDB Information
Treble, ROM for the Samsung Galaxy J7 (2017)
Contributors
ananjaser1211
Source Code: https://github.com/ananjaser1211/Helios_7870
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest bootloader and modem
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: X
Stable Release Date: 2020-01-13
Created 2019-05-11
Last Updated 2020-01-13
Downloads and changelogs
NewsChannel : Telegram
Come hang with us on our chat : Telegram
Official Treble support Group : Telegram
----------------------------------------------------------------
SpagetX Treble ARM64 Vendor Based on G965F VNDK-28
GoogleDrive : Download
P.S : If you failed to download please login and save the folder
P.S 2 : This requires Pie bootloader and modem on devices that supports them (I.E not j710 or g610)
----------------------------------------------------------------
Spaget Treble ARM64 Vendor V3.0 Based on A750FN Vendor
MegaDrive Download : MEGA
GoogleDrive Mirror : GDrive
Documentation : Here
Spaget X
- ReMade fully based on VNDK-28 S9 Vendor
- Based on Project Pizza Treble (8890)
- included most fixes for audio, webview and others
- added fixes for camera
- removed alot of obsolete hacks
- samsung offline charging added
- Re-did props and features and overlays
- Added patches for Android 10 Roms
- Fixed nuke.sh script on 10 roms
- fixed performance in some GSIs
- Fixed thermal , power , memtrack and other HALs
- Improved OMX fixes
- Removed alot of samsung security services
- Improved Wifi, NFC, graphics , camera and other fixes
- Fixed some reboots on G610
- Fixed Youtube Crashes and OMX issues on most devices
- Addressed alot of random reboots
- Fixed GNSS/GPS on some variants
- Removed HKTweaks due to reboots
- Fixes for J710 Wifi and bluetooth
- Tons of other changes and improvments
[COLOR=""]Spaget V3.0[/COLOR]
- Fully based on A750FN 64Bit Vendor
- Seamlessly integrated ALL patches into the vendor
- No longer do you need customized TWRPs, patches, zips whatever. just the vendor and GSI
- Fixed all the VENDOR related issues we had
- Audio, camera, NFC, everything is redone from scratch and improved
- Supports Android Q booting
- Updated overlays and configs
- Added support for J710/J701/G610
- Updated to Helios V4.0 Kernel with tons of changes and goodies
- Automatic GSI patching at first boot
- New repartition script with extended support. fail safes, backup features and tons more
- Live TWRP patching, so it will patch whatever twrp you have instead of using my own
- And tons more through out the months of testing, using and developing
- Please read the thread agian to understand how to use it
OLD(a64)
----------------------------------------------------------------
Treble Vendor V1.5 Based on Stable A600FN Pie Vendor
Full TREBLE Documentation and guides here : GoogleDocs
Treble folder mirror : MEGA
Treble Vendor V1.0 Based on Stable A600FN Pie Vendor
GoogleDrive Project : Download
Full TREBLE Documentation and guides here : GoogleDocs
Treble folder mirror : MEGA
---------------------------------------------------------------
V1.5
1- HeliosPro 3.1 Kernel
2- Added HKTweaks
3- Fingerprint fix for All GSIs
4- Hotspot fix for All GSIs
5- AdaptiveBrightness
6- Updated included overlays with more features and pie base
7- DualbootPatcher J5/J7 Seperation
GSI_PATCH_V2.0
1- Patch fingerprint libs for all GSIs
2- Switch to samsung fingerprint
3- Add device model number detection
4- replace gsi fingerprint with stock one
GSI_PATCH_FP
1- Special patch for PE/RR/LR and other roms that do not have working FP
2- Do not flash on OMNI/PHH
3- Must be flashed AFTER the Vendor/GSI
Kernel updates
- Updated base to latest pie source
- reworked and updated helios ramdisk tweaks
- Reverted old hacks to fix some bugs
- Performance and battery greatly improved
- F2FS enabled
- LZ4 Enabled
- GPU Performance Greatly improved
- Full CPU/GPU/DEVFREQ/MIF/CAMERA Voltage control and more
- Magisk V19.1 included
Bugs :
1- some users might face SDCard issues while using PE
- if you did , back up its data and format it in PE
V1.0
-initial release
- Helios Kernel 2.8
F.A.Q
Q: Device requirements ?
A : you MUST be on an Pie Bootloader and Modem, otherwise you will have no sim, no lockscreen etc (Devices such as J710 and G610 can use OREO)
Q : Do i need to format internal storage ?
A : No
Q : Can i use the Treble recovery for normal ROMs ?
A : Yes, it is preferred especially when making backups. just be sure to wipe vendor when switching to non treble roms
Q : What Camera is recommended ?
A : Footej and open camera works the best
Q : Can i flash any GSIs ?
A : Any GSI that is ARM64_AONLY is supported [8/9/10]
Additional
One more
Oh God
Great job. Fm radio and volte work?
Xxxnano said:
Great job. Fm radio and volte work?
Click to expand...
Click to collapse
That depends on what GSI you plan to install. Go try one out and let others know.
Xxxnano said:
Great job. Fm radio and volte work?
Click to expand...
Click to collapse
No and No, this is an AOSP project. they dont support Samsung VoLTE or FM
Can anyone will make a video exactly what is this and how to install properly ..
I'm so confused here is so many details ?
Imtiaz ansari said:
Can anyone will make a video exactly what is this and how to install properly ..
I'm so confused here is so many details ?
Click to expand...
Click to collapse
Not the rom for you then. save your time and use something else
Xxxnano said:
Great job. Fm radio and volte work?
Click to expand...
Click to collapse
Volte works in custom rom after this?
Can i install an Oreo GSI or just Pie GSI's?
Anyway i'm gona try one of the images linked on google drive
Congrats guyz :good:
Including the long ears bunny
for j7 neo, please
When I install magicgapps everything seems normal giving me that its succesfully installed but when the system boots I dont have any gapps installed? What am I doing wrong? I installed the RR Rom. I mention that i took the gapps from the official website. I followed every step from the thread...
You are the best ?
Thank You anan Great rom
Well, i've tried all the GSI's linked on the google drive folder of the project and just AOSP booted up and this one have two bugs, all the configurations related to the simcard doesn't work and the simcard don't work, i can't get signal.
Another question, "A64" means "ARM64"? or there's another variant called "A64"?
Yolomean12 said:
Well, i've tried all the GSI's linked on the google drive folder of the project and just AOSP booted up and this one have two bugs, all the configurations related to the simcard doesn't work and the simcard don't work, i can't get signal.
Another question, "A64" means "ARM64"? or there's another variant called "A64"?
Click to expand...
Click to collapse
Type these commands in terminal:
Code:
su
setprop persist.sys.phh.sdk_override /vendor/bin/hw/rild=27
I have tried Omina gsi and it works OK, only the camera images are stretched, but this is a known bug.

[Treble][ARM64][AOSP][J710X]Project_Spaget X

{
"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"
}
Welcome to Project Spaget X ARM64 Treble For Galaxy J530X/J730X/G610X/J701X/J710X​
Some information you should know..
This is a full Treble ARM64 Vendor/Kernel implementation for the Exynos7870 Supported devices
If you want to report a Bug, read the F.A.Q First Then provide a logCat OR LoggingKit.zip with detailed explanation
Read the instructions and the F.A.Q Before installing the rom or posting a reply.
[FOR DEVS] You are allowed to customize this vendor if you want to use it in ROMs with proper credits. but not to distribute 1:1 copies
- Personal Notes
And here we are, few leaks and reworks later. X is here. i went with a letter this time just because it looks cool. This is officially going to be EOL for ARM64 AONLY vendors that i make (unless a critical bug was here that needed attention) . i dont have alot of time to work on 7870 And when i do i prefer it to be on something more productive than Treble
Anywya, TLDR : alot changed, alot was fixed. its a new vendor, flash and enjoy
Old releases
Alright, The "second" Treble update is here, this time it is FULLY ARM64 compatible. Thanks to the hard-work of @Astrako who managed to boot ARM64 Exynos 7885 bases on our device. This project is HEAVILY based on his work. and i would like to make that very clear. This is not a OneMan job. this took alot of hardwork by many people to make it reach the stage it is at. basically we are official minus the tag. This project is also possible thanks to my dear friends @Kique119 @me2 @SPARTANICUS and my other testers who spent day and night testing this with me.
At this stage, everything is mostly GSI related.
And finally, the cherry on top, is support for 3 more devices. Thanks to the devs who assisted me on adding support for their own devices. mentioned below.
If you appreciate this ambitious project, consider hitting thanks, supporting the thread, and donating (Paypal) to support my development (using cocaine of-course)
- Initial Notes:
Supports ONLY the mentioned devices Above
1. Don't forget to check bugs before asking questions
2. Since most of the GSIs are AOSP, forget about VoLTE, Knox features, Samsung apps, Camera mods or features, or other Samsung related features.
3. You can use any non-treble rom even if you have treble vendor installed, as long as you flash a non-treble kernel. The rom will ignore your vendor and everything will be as non treble.
- General Features :
- based on G965F Vendor with VNDK-28
- Adapted to J730/J530/G610/J710/J701 devices
- latest CronosKernelV5 included with most of the features of OneUI kernel + many more
- misc things enabled in framework overlay for better experience
- Seamless GSI patching, without user intervention
- Seamless setup process, with dynamic Scripts
- And Spaget
- How to Install Project Spaget:
- Flash `Exynos7870_CreateVendor` and reboot recovery
- Flash `Exynos7870_Spaget_X`
- Flash your desired ARM64_AONLY GSI
- Read OPTIONAL below
- What GSIs are support/recommended ?:
- Avoid sGSIs and flash source built GSIs (Such as PHH,PE)
- ARM64_AONLY GSIs only
- I recommend Pixel-experience or evo x and luke GSIs
- if you want a daily rom. avoid sGSIs
- More can be found here : Treble
- I dont have googleapps. what do i do ?:
ONLY for gsis that does not come with google apps
- Download Gapps pacakge from Here (ARM64 > VER > Micro or lower
- Go to TWRP > Wipe > Advanced Wipe > Tick System > Repair > Resize
- Flash opengapps_xxxx
- I need more info. where do i get it ?
Ask in this thread. if you need more , head to
Spaget Notes and support : Telegram Group
General bugs (GSI):
- offline charging is broken in Android 10 roms
- Bluetooth Calls
- Some GSIs might not include a camera, use Footej
- Some camera apps will have stretch
- I dont like it, how do i revert ?:
- Reboot to recovery
- Flash `Exynos7870_RevertVendor`
- Reboot recovery
- Flash any non treble rom or restore your previous twrp backup
Is that all ? I have treble now ? what about all the complicate process before ?
Yes, you now have a project treble device, ready to flash any GSI/sGSI of your choice aslong as it fits in your SYSTEM partition.
The entire process changed and now is much more seamless and noob-friendly. yet take caution as always
What if i didn't boot ?
In some cases, you might be stuck at a bootanimation loop or a splash loop, in this case follow the troubleshooting steps in the F.A.Q post
Credits
@corsicanu For great help with the repartition scripts, GSI patching and tons other throughout the years.
@Astrako for making booting ARM64 a possibility. and allowing this project to exists. kudos
@Kique119 For his awesome testing and documenting this project, without him there would be no spaget
@KassemSYR, for G610F Support and testing.
@Zero_Cool7870 , @DAvinash97 , @mohitsama and ORIGINALNAME123 for J710/J701 support
@SPARTANICUS For his great work maintaining KRAKEN kernel, which supports this project fully
Testers :
@Kique119 @LuanTeles @ion1s @djedjy @vsmhell @fetaiharbin @Mizo2019 @Me2 @LelMwhLwl @@rlukas210
@PedroDomeneghi @DaffyMirror4318 @bien2004official @AleeX157 @Alijouhara
And many more i cant remember the usernames of. please mention
Downloads. Changelogs , F.A.Qs below
OldPost (a64)---
So, i have been hesitated to release this project since last year. GSIs are not the most stable and many J users prove they are unable to read. they just want ready stuff. with this project that is not the case. if you skip the instructions/F.A.Qs and notes, dont bother installing this project as you probably wont be able to get it running.
This is a fully featured VENDOR and KERNEL designed for this device to support project treble, it is based on other Exynos 7870 Vendors and modified to support our devices, i have also added few patches and updates that even official 7870 vendors do not have. to get the best possible experience
I have also added a GSI_PATCH zip that should be used if you want to have the least amount of bugs.
The vendor is pretty much bugles, therefore any bugs you face, Report them to the appropriate Threads of the GSI you installed. or github issues section. as those are not mine to fix. i only provide the vendor and kernel that allows GSIs to run on.
- STEPS FOR INSTALLING TREBLE VENDOR:
Flash “Treble_Jx30F.img” in TWRP as Image (Selecting RECOVERY)
Reboot recovery.
Wipe System, Data, Dalvik and Vendor.
Flash "jxy17lte_Vendor_9.0_v1.0.zip".
- STEPS FOR INSTALLING GSIs:
Download the desired GSI (it MUST be arm_binder64/A64 Variant)
unpack it if it wasn't in .IMG format
Go to TWRP , Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Flash "GSI_Patch.zip".
[OPTIONAL] Flash the “Gapps_patched.zip”
- STEPS FOR INSTALLING GAPPS:
If you flash Gapps, Google will spam you with fullscreen warnings and notifications about your device not being certified. But don't worry, you can certify it.
Just reach the homescreen, then proceed to install the "Device ID.apk". Use it to grab the Google Services Framework ID and paste it here: https://www.google.com/android/uncertified/
And paste the ID there. Then wait a few minutes and reboot. Few seconds after rebooting, you'll be done and you'll be able to normally log in as always.
- [OPTIONAL]STEPS FOR INSTALLING Magisk_GAPPS:
** Note : This gapps is recommended for all **
Download latest gapps from http://opengapps.org
place in /sdcard or /external_sd
flash magisk.zip
flash magiskgapps.zip
- Confirmed working GSIs :
** You can only use ARM_BINDER64 / A64 GSIs **
PHH AOSP V113 : Github
OmniROM GSI : XDA
Liquid Remix : GoogleDrive
Pixel Experience With Gapps : GitHub
Resurrection Remix : RR
XenonHD : TeamHorizon
P.S : only Omni and PHH Do not require the GSI_PATCH_FP The rest do in order to get Fingerprint working
- Known GSI Bugs:
Bluetooth calls are broken
Some 3rd party cameras have stretched pictures
And more here at Github Issue
Credits
@corsicanu For general help through out the years
@prashantp01 For overlay fixes and native camera fix. and other contributions
@Kique119 For his awesome testing and documenting this project
Testers :
@Kique119 @LuanTeles @ion1s @djedjy @vsmhell @fetaiharbin @Mizo2019 @Me2 @LelMwhLwl
And few more that didn't give me their usernames
Downloads. Changelogs , F.A.Qs below
XDA:DevDB Information
Project Spaget. Treble ARM64 Vendor, ROM for the Samsung Galaxy J7
Contributors
ananjaser1211, corsicanu, Astrako
Source Code: https://github.com/ananjaser1211/Helios_7870
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest bootloader and modem
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: X
Stable Release Date: 2020-01-13
Created 2019-07-31
Last Updated 2020-01-13
Downloads and changelogs
NewsChannel : Telegram
Come hang with us on our chat : Telegram
Official Treble support Group : Telegram
----------------------------------------------------------------
SpagetX Treble ARM64 Vendor Based on G965F VNDK-28
GoogleDrive : Download
P.S : If you failed to download please login and save the folder
P.S 2 : This requires Pie bootloader and modem on devices that supports them (I.E not j710 or g610)
----------------------------------------------------------------
Spaget Treble ARM64 Vendor V3.0 Based on A750FN Vendor
MegaDrive Download : MEGA
GoogleDrive Mirror : GDrive
Documentation : Here
Spaget X
- ReMade fully based on VNDK-28 S9 Vendor
- Based on Project Pizza Treble (8890)
- included most fixes for audio, webview and others
- added fixes for camera
- removed alot of obsolete hacks
- samsung offline charging added
- Re-did props and features and overlays
- Added patches for Android 10 Roms
- Fixed nuke.sh script on 10 roms
- fixed performance in some GSIs
- Fixed thermal , power , memtrack and other HALs
- Improved OMX fixes
- Removed alot of samsung security services
- Improved Wifi, NFC, graphics , camera and other fixes
- Fixed some reboots on G610
- Fixed Youtube Crashes and OMX issues on most devices
- Addressed alot of random reboots
- Fixed GNSS/GPS on some variants
- Removed HKTweaks due to reboots
- Fixes for J710 Wifi and bluetooth
- Tons of other changes and improvments
[COLOR=""]Spaget V3.0[/COLOR]
- Fully based on A750FN 64Bit Vendor
- Seamlessly integrated ALL patches into the vendor
- No longer do you need customized TWRPs, patches, zips whatever. just the vendor and GSI
- Fixed all the VENDOR related issues we had
- Audio, camera, NFC, everything is redone from scratch and improved
- Supports Android Q booting
- Updated overlays and configs
- Added support for J710/J701/G610
- Updated to Helios V4.0 Kernel with tons of changes and goodies
- Automatic GSI patching at first boot
- New repartition script with extended support. fail safes, backup features and tons more
- Live TWRP patching, so it will patch whatever twrp you have instead of using my own
- And tons more through out the months of testing, using and developing
- Please read the thread agian to understand how to use it
OLD(a64)
----------------------------------------------------------------
Treble Vendor V1.5 Based on Stable A600FN Pie Vendor
Full TREBLE Documentation and guides here : GoogleDocs
Treble folder mirror : MEGA
Treble Vendor V1.0 Based on Stable A600FN Pie Vendor
GoogleDrive Project : Download
Full TREBLE Documentation and guides here : GoogleDocs
Treble folder mirror : MEGA
---------------------------------------------------------------
V1.5
1- HeliosPro 3.1 Kernel
2- Added HKTweaks
3- Fingerprint fix for All GSIs
4- Hotspot fix for All GSIs
5- AdaptiveBrightness
6- Updated included overlays with more features and pie base
7- DualbootPatcher J5/J7 Seperation
GSI_PATCH_V2.0
1- Patch fingerprint libs for all GSIs
2- Switch to samsung fingerprint
3- Add device model number detection
4- replace gsi fingerprint with stock one
GSI_PATCH_FP
1- Special patch for PE/RR/LR and other roms that do not have working FP
2- Do not flash on OMNI/PHH
3- Must be flashed AFTER the Vendor/GSI
Kernel updates
- Updated base to latest pie source
- reworked and updated helios ramdisk tweaks
- Reverted old hacks to fix some bugs
- Performance and battery greatly improved
- F2FS enabled
- LZ4 Enabled
- GPU Performance Greatly improved
- Full CPU/GPU/DEVFREQ/MIF/CAMERA Voltage control and more
- Magisk V19.1 included
Bugs :
1- some users might face SDCard issues while using PE
- if you did , back up its data and format it in PE
V1.0
-initial release
- Helios Kernel 2.8
F.A.Q
Q: Device requirements ?
A : you MUST be on an Pie Bootloader and Modem, otherwise you will have no sim, no lockscreen etc (Devices such as J710 and G610 can use OREO)
Q : Do i need to format internal storage ?
A : No
Q : Can i use the Treble recovery for normal ROMs ?
A : Yes, it is preferred especially when making backups. just be sure to wipe vendor when switching to non treble roms
Q : What Camera is recommended ?
A : Footej and open camera works the best
Q : Can i flash any GSIs ?
A : Any GSI that is ARM64_AONLY is supported [8/9/10]
Enjoy, and please report any issues you face HERE and not in the other threads.
And read the thread few times before asking. Yes this supports your J710Whatever
This is only for J710 Users who got no wifi. BT fix will come later (you can do it yourself by editing the vendor.zip/variant/jx/fs/etc and removing the bluetooth folder.
reflashing vendor + gsi + fix
Wifi FIX : here
Great work sir.
ananjaser1211 said:
Enjoy, and please report any issues you face HERE and not in the other threads.
And read the thread few times before asking. Yes this supports your J710Whatever
Click to expand...
Click to collapse
When I flash these create vendor and project spaget zips, It gives a partition error like this:
Failed to mount "/vendor" (Block device required)
And My phone didn't boot GSI roms because of this.
Anyone tried this with Resurrection Remix (Im getting bootloops here: pastebin.com/raw/NnieJ1Px) or LineageOS (bootloops the same as RR)?
Edit: Every GSI bootloops the same, tried several roms. Stay away until it'll be stable enough.
TRalperenTR said:
When I flash these create vendor and project spaget zips, It gives a partition error like this:
Failed to mount "/vendor" (Block device required)
And My phone didn't boot GSI roms because of this.
Click to expand...
Click to collapse
siemanator said:
Anyone tried this with Resurrection Remix (Im getting bootloops here: pastebin.com/raw/NnieJ1Px) or LineageOS (bootloops the same as RR)?
Edit: Every GSI bootloops the same, tried several roms. Stay away until it'll be stable enough.
Click to expand...
Click to collapse
it has been tested, and this is nothing but user error.
if you are being stuck at splash, go follow the instructions again, as it has booted on several J710 variants already. after you flash the vendor zip you must reboot back to recovery, then check your vendor size in wipe menu, if it is less than 350MB, or doesnt exist, then you had some previous repartitioner installed that broke the process
finally be sure you are downloading arm64 gsi and a tested one, i have not tested RR or LOS (since they are both either outdated or doesnt work on samsung vendors)
flash PE , evox , havoc and so on
ananjaser1211 said:
it has been tested, and this is nothing but user error.
if you are being stuck at splash, go follow the instructions again, as it has booted on several J710 variants already. after you flash the vendor zip you must reboot back to recovery, then check your vendor size in wipe menu, if it is less than 350MB, or doesnt exist, then you had some previous repartitioner installed that broke the process
finally be sure you are downloading arm64 gsi and a tested one, i have not tested RR or LOS (since they are both either outdated or doesnt work on samsung vendors)
flash PE , evox , havoc and so on
Click to expand...
Click to collapse
Suggest fix
ananjaser1211 said:
This is only for J710 Users who got no wifi. BT fix will come later (you can do it yourself by editing the vendor.zip/variant/jx/fs/etc and removing the bluetooth folder.
reflashing vendor + gsi + fix
Wifi FIX : here
Click to expand...
Click to collapse
Waiting for the bluetooth fix sir
Followed all instructions andi am stuck at bootloop.
My j7 2016 is rooted with heilos 2.6 kernel with twrp recovery. Should i install stock rom and reinstall twrp and then the whole mentioned process in this post. Some one guide me please.
Flash “Treble_Jx30F.img” in TWRP as Image (Selecting RECOVERY)
Are you sure that as recovery?
Flash "jxy17lte_Vendor_9.0_v1.0.zip".
Write that zip file damaged.
Any solution?
---------- Post added at 02:09 PM ---------- Previous post was at 01:57 PM ----------
Sulltan Mehmood said:
Followed all instructions andi am stuck at bootloop.
My j7 2016 is rooted with heilos 2.6 kernel with twrp recovery. Should i install stock rom and reinstall twrp and then the whole mentioned process in this post. Some one guide me please.
Click to expand...
Click to collapse
Same me....
Sulltan Mehmood said:
Followed all instructions andi am stuck at bootloop.
My j7 2016 is rooted with heilos 2.6 kernel with twrp recovery. Should i install stock rom and reinstall twrp and then the whole mentioned process in this post. Some one guide me please.
Click to expand...
Click to collapse
NO.....you have to boot to TWRP. Once you're in recovery, you must wipe data, system, cache, dalvik, and vendor, then flash the RevertVendor.zip and after that you can go back to your stock rom or any other non-treble rom.
Sulltan Mehmood said:
Suggest fix
Click to expand...
Click to collapse
Flash pit file with stock rom via odin.
Tried again on my J7 1016, but after flashing vendor, reboot and flashing sparget I cannot mount system. Any solution?
Thanks so much for your work.
There is one problem with this release same as before with roms that used HeliosKernel is that the kernel has no deep sleep and it drains battery like no tomorrow, it drained battery from 80% to 5% in standby over night.
I got error while
- Flashing `Exynos7870_ProjectSpaget_V3.0`
Below is image where error is shown. How can I fix this error please help me.
I got error 255 by flashing image!? Any solution?

[Unofficial] Lineage 18.1 for Xperia X Performance [Treble]

Lineage 18.1 for Xperia X Performance​
Code:
#include <std_disclaimer.h>
/*
* 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.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 11.x (R),
which is designed to increase performance and reliability over stock Android for your device.
All the source code for LineageOS is available in the LineageOS GitHub repo.
And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Official LineageOS website : http://lineageos.org
About LineageOS Legal : http://lineageos.org/legal/
Important Information
1. This ROM has nothing related to ODM images! So you don't need to ask/install anything like that, just follow the instructions.
2. You need to flash Stock 41.3.A.2.149 and boot into it before flashing this ROM.
3. This ROM is suitable for dual and single model
4. You will meet a delay when recognize sim at the first boot.
5. VoLTE is supported, but you need to enable it on stock firmware at first.
6. We support Gcam, but you need to install Gapps at first.
Downloads Links
LineageOS 18.1:
Unofficial: https://sourceforge.net/projects/release-sjll/files/dora/18.1/
Google Applications (optional):
NikGapps: https://nikgapps.com/ (ARM64->Android R->core,)
Information: Flash the GApps before the first boot. If not, a clean flash is recommended.
Flashing and updating
LineageOS clean install:
Download the latest build of LineageOS ROM
Full wipe and factory reset (recommended / backup to make sure not to loose data)
Flash the LineageOS ROM zip from the Recovery
Flash the GApps to have the Google Applications (optional)
Every additional zip you want to flash (optional)
Reboot
LineageOS update/upgrade:
Download the latest build of LineageOS ROM
Wipe cache and dalvik cache
Flash the latest LineageOS ROM zip from the Recovery
Every additional zip you want to flash (optional)
Reboot
About the builds:
Source: https://github.com/linelessos
Issues and reports
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Share a log of the error with CatLog for example
Also thanks to:
The LineageOS Team
The CyanogenMod Team
The SODP Team.
Olivier
Chippa_a
Everyone involved in working and testing
Contributors
@erikcas @Sjll
ROM OS Version: 11.0
ROM Kernel: Linux 4.4.x
Version Information
Status: Beta
FEATURES AND ISSUES
Code:
- Boot: Ok
- Bluetooth: Ok
- WiFi: Ok
- WiFi Hotspot: 2.4 Ghz Only
- RIL - Phone - Data: Ok
- VoLTE: Ok
- GPS: Ok
- Camera: Ok
- Camcorder: Ok
- Lights: Ok
- MicroSD: Ok
- Accelerometer: Ok
- Compass: Ok
- Gyroscope: Ok
- QTI sensors: Ok
- Touchscreen: Ok
- FM Radio: NA
- Fingerprint: Ok
- Vibrator: Ok
- Microphone: Ok
- Audio & music: Ok
- Bluetooth audio: Ok
- NFC: Ok
- Kernel: Ok
- Graphics: Ok
- 3D Rendering: Ok
- Clock: Ok
- DRM: No test
- Offline Charging: Ok
- USB: Ok
- USB Tethering: Ok
- USB OTG: No test
- Encryption: No
- SEPolicies: Permissive
Installed it with stock NicksGapps and it works fine but couple of issues which I reported on other Lineage versions are still there, double tap to wake not working and physical camera key not working. Those should be easily repro-able and I did fresh installation.
I will report more if I find any.
when are you going to support 5ghz wifi bandwith
and does it have support for gcam and if not could i flash camera2api enabler to use it
alohaxz123 said:
when are you going to support 5ghz wifi bandwith
Click to expand...
Click to collapse
5Ghz hotspot? Not sure our hardware support it.
alohaxz123 said:
and does it have support for gcam and if not could i flash camera2api enabler to use it
Click to expand...
Click to collapse
Why not try Gcam and get the answer before you asked this question?
PPGX5II said:
Installed it with stock NicksGapps and it works fine but couple of issues which I reported on other Lineage versions are still there, double tap to wake not working and physical camera key not working. Those should be easily repro-able and I did fresh installation.
I will report more if I find any.
Click to expand...
Click to collapse
Physical camera key needs to be enabled in Settings.
Sjll said:
Physical camera key needs to be enabled in Settings.
Click to expand...
Click to collapse
Aah! Thanks it works now. Is there a way to enable double tap to wake and double tap to sleep?
Is there face unlock in this ROM
And why there no NFC
Can this flash in my XP Docomo global rom?.in lineage 16, the screen goes black didnt appears
URGENT notification! For 20210418 build​Here providea temp fix, for bluetooth, doze issue. I will fix it in next build.
1. Enable USB debug and allow debug as root in developer settings.
2. Run
Code:
adb root
adb shell mount -o remount,rw /vendor
adb pull /vendor/etc/vintf/manifest.xml
3. Open mainfest.xml with text editor, then Remove these codes in it:
Code:
<hal format="hidl">
<name>android.hardware.bluetooth.audio</name>
<transport>hwbinder</transport>
<version>2.0</version>
<interface>
<name>IBluetoothAudioProvidersFactory</name>
<instance>default</instance>
</interface>
<fqname>@2.0::IBluetoothAudioProvidersFactory/default</fqname>
</hal>
4. Save and run
Code:
adb push manifest.xml /vendor/etc/vintf/manifest.xml
adb reboot
Super awesome! Thanks for this ROM!
Any plans on adding NFC functionality?
We support treble now.
trying to update from 20210419 to 20210429 now, but getting stuck in boot loop.. Is a full wipe required?
Edit: oof never mind, I just let it bootloop and when I came back from lunch it was fine
Sjll said:
We support treble now.
Click to expand...
Click to collapse
support treble but how to use it
ota?
syberia os or havoc?
Hmm, so I got round to installing this, lazily didn't reinstall stock and went straight from the SODP Lineage 16 to this. What could go wrong?
Apparently, what could go wrong is that the 'call' screen never appears, so I can't pick up phone calls, OR if I initiate phone calls they work but I can't hang up. Weird. Looks great otherwise, though!
(also, struggling to get GPS fix)
Would actually following the instructions here solve my problems?
EDIT: Aha, just that the default phone app wasn't set. How odd.
after boot, it asked me to enter password but I don't have any password before flashing this ROM. No lock screen, not signed to any google account.
Wasn't this build supposed to be Enforcing?

Categories

Resources