Develop Bugs

[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.

[DEV][ROM][UNOFFICIAL] LineageOS 14.1 (Android 7.1.2) for Raspberry Pi 3 B

Here’s my build of LineageOS 14.1 for Raspberry Pi 3 Model B. It is unofficial and unsupported by the LineageOS team. It’s for advanced users only.
{
"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"
}
https://konstakang.com/devices/rpi3/CM14.1/
lineage-14.1-20180817-UNOFFICIAL-KonstaKANG-rpi3.zip
https://www.androidfilehost.com/?fid=1322778262903982504
md5:affa35dd70b51e4b70c9acb996f7304b
Sources:
lineage-rpi
Thanks:
peyo-hd and everyone who’s contributed to android-rpi
LineageOS team & everyone who’s been working on CM14.1

How to install:
Follow the official Raspberry Pi instructions for writing the image to the SD card (Linux, Mac, Windows).
FAQ:
Q: I can’t find developer options, why?
A: Settings -> About phone -> Click ‘Build number’ several times
Q: I don’t have reboot options in power menu, why?
A: Settings -> Developer options -> Advanced restart
Q: I have no root, why? What is that hashtag on my status bar?
A: You need enable root access under Settings -> Developer options -> Root access. Root management is now integrated as part of LineageOS’ Privacy Guard and you can manage per app permissions under Settings -> Developer options -> Manage root access. You’ll have a persistent notification in the status bar when you’re running an app that uses root permissions.
Q: I have official 7” LCD display and touchscreen. What should I do?
A: Execute following commands in ‘adb shell’/serial console/terminal (you can enable built-in terminal app from Settings -> Developer options -> Local terminal) and reboot your device:
Code:
su
rpi3-display.sh
Q: Settings -> Storage shows xx GB used by system. There’s unallocated space on my sdcard. What should I do?
A: This is a 4 GB image, remaining space on your sdcard will remain unallocated. Settings app shows unallocated space as used by system which in reality it is not. You can use e.g. GParted and extend /data partition (/dev/block/mmcblk0p3) to cover the unallocated space. Resizing the partition manually will break support for encrypting /data. Format /data in TWRP recovery (Wipe->Format data) after resizing to leave required space for crypto footer.
Q: Raspberry Pi doesn’t have power button, how do I power off/reboot my device?
A: Following keyboard keys work as Android buttons: F1 = Home, F2 = Back, F3 = Multi-tasking, F4 = Menu, F5 = Power, F11 = Volume down, and F12 = Volume up. You can also use one of many third party reboot applications.
Q: How to boot to TWRP recovery?
A: There’s currently no proper way to boot between Android and TWRP, but this can achieved by renaming the ramdisk you want to boot. Execute following commands in ‘adb shell’/serial console/terminal (you can enable built-in terminal app from Settings -> Developer options -> Local terminal) and reboot your device:
Code:
su
rpi3-recovery.sh
If mouse cursor doesn’t appear, try replugging your mouse.
Q: How to boot out of TWRP recovery?
A: Flash my recovery2boot zip in TWRP.
Q: How to install Google apps?
Download open_gapps-arm-7.1-pico-xxxxxxxx.zip and save it to your device’s internal storage or use an external USB drive
Boot to TWRP recovery (see FAQ)
Install open_gapps-arm-7.1-pico-xxxxxxxx.zip from your selected storage
Wipe->Factory reset!
Boot out of recovery (see FAQ)

Merged commits not mentioned in the changelog.
17.8. changelog:
include TWRP 3.2.3-0 custom recovery (see FAQ how to boot)
fix Gallery app crashing (and likely various third party apps as well)
add support for encrypting the device
merge AOSP kernel/common android-4.4-n branch to have proper Android Nougat kernel
update to Linux 4.4.148 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 August 2018 (merged)
15.6. changelog:
add support for USB webcams (UVC) with third party USB webcam apps
default to noop I/O scheduler
update to Linux 4.4.137 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 June 2018 (merged)
15.4. changelog:
update audio HAL (fix USB microphone, etc)
add support for external USB GPS dongles (1546:01a7 U-Blox AG, etc - GPS dongle must be plugged-in while booting the device)
update to Linux 4.4.127 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 April 2018 (merged)
18.1. 2018 changelog:
add support for I2C devices
enable Android low-RAM configuration
add lights HAL to control display brightness from Android on offical RPI display (version 1.1)
update to Linux 4.4.112 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
Android security patch level: 5 January 2018 (merged)
17.11. changelog:
fix wifi reconnect on boot (thanks to Google)
update to Linux 4.4.97 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
patch recently disclosed BlueBorne and KRACK vulnerabilities (merged)
Android security patch level: 5 October 2017 (merged)
10.8. changelog:
update to Linux 4.4.80 kernel
merge AOSP kernel/common android-4.4 branch to have proper Android kernel
enable sdcardfs
add BFQ i/o scheduler and enable it by default
Jelly browser (merged)
Android security patch level: 5 August 2017 (merged)
16.4. changelog:
add support for wifi tethering
add support for Widevine DRM
improve Play Store compatibility
Android 7.1.2 (merged)
Android security patch level: 5 April 2017 (merged)
11.4. changelog:
initial relase
Previous builds:
AndroidFileHost

I cannot boot out of recovery after installing Gapps in TWRP. When I run rpi3-recovery.sh boot I got Segmentation Fault error. Please help. Thanks

Project999 said:
I cannot boot out of recovery after installing Gapps in TWRP. When I run rpi3-recovery.sh boot I got Segmentation Fault error. Please help. Thanks
Click to expand...
Click to collapse
Please read the FAQ! It doesn't say to run the same script, it says to flash recovery2boot zip in TWRP.
I'm aware of the segfault.

Ok, I was doing both ans will only flash the zip file next try.

Yes. It worked this time after only flashing the recovery2boot zip file. Thank you.

Its possible to update ROM via recovery?

laharl_22 said:
Its possible to update ROM via recovery?
Click to expand...
Click to collapse
No, not currently. Partition structure (especially boot partition) on this device is different than on Android devices usually (well, as Raspberry is not an Android device to begin with). It would require some quite significant modifications to LineageOS build system to build recovery flashable ROM zips for this device (it's all open source so you're welcome to have a crack at it). There's also no proper way to cold boot (from power off) to recovery which makes it less useful than on other devices. I only included TWRP recently and it's currently mostly just used for installing gapps.

KonstaT said:
No, not currently. Partition structure (especially boot partition) on this device is different than on Android devices usually (well, as Raspberry is not an Android device to begin with). It would require some quite significant modifications to LineageOS build system to build recovery flashable ROM zips for this device (it's all open source so you're welcome to have a crack at it). There's also no proper way to cold boot (from power off) to recovery which makes it less useful than on other devices. I only included TWRP recently and it's currently mostly just used for installing gapps.
Click to expand...
Click to collapse
So no way for updating ROM without loose data?

laharl_22 said:
So no way for updating ROM without loose data?
Click to expand...
Click to collapse
No, not currently and who said there was going to be any updates.
Well, you can actually restore your previous /data partition in TWRP after you've installed a new image.

Sorry, double post.

Hi.
Is there a GPIO support? Everything is working great, but I build it into my car, and I have some pushbuttons connected. I would like to use it for opening apps or shutdown etc. Any ideas? couldn't find anything on google? Thanks

ulfdogg said:
Hi.
Is there a GPIO support? Everything is working great, but I build it into my car, and I have some pushbuttons connected. I would like to use it for opening apps or shutdown etc. Any ideas? couldn't find anything on google? Thanks
Click to expand...
Click to collapse
Yes, that should be possible but you need to do a little work for that.
4.4 kernel used in LineageOS 14.1 doesn't have gpio-key overlay (https://github.com/raspberrypi/linux/commit/7bc9c88a0eb043c5387a23d4ade23359749398e0) but I have already enabled KEYBOARD_GPIO that is also needed for this. So you need to build that overlay, copy it to device, and configure it in config.txt depending on what GPIO pins you're using. There's also another similar approach (different overlay) that's been reported working. https://stackoverflow.com/questions/50224010/using-gpio-keys-interrupt-to-wake-up-screen-on-rpi3

Does this build support 3b+?If not,how to ?

zhengyw said:
Does this build support 3b+?If not,how to ?
Click to expand...
Click to collapse
No, you can use LineageOS 15.1 build instead.
This build uses Linux 4.4 kernel and Broadcom added support for 3B+ only on later kernel versions (4.9 and 4.14). 4.4 is actually the newest that Android Nougat supports (https://android.googlesource.com/kernel/common/) and there's some network issues using newer ones. 4.9 is the newest for Oreo and 4.14 for Pie. So the Linux kernel in LineageOS 15.1 is actually too new for the Android version. There's no major changes between Oreo and Pie kernels, though.
Android kernel versions lag behind mainline because chipset manufacturers (Qualcomm, etc) need to make significant modifications to support their hardware. Android devices usually stay with the Linux kernel version they initially shipped with so there also needs to be quite long support time (4.4 is still supported with Pie).

KonstaT said:
No, you can use LineageOS 15.1 build instead.
This build uses Linux 4.4 kernel and Broadcom added support for 3B+ only on later kernel versions (4.9 and 4.14). 4.4 is actually the newest that Android Nougat supports (https://android.googlesource.com/kernel/common/) and there's some network issues using newer ones. 4.9 is the newest for Oreo and 4.14 for Pie. So the Linux kernel in LineageOS 15.1 is actually too new for the Android version. There's no major changes between Oreo and Pie kernels, though.
Android kernel versions lag behind mainline because chipset manufacturers (Qualcomm, etc) need to make significant modifications to support their hardware. Android devices usually stay with the Linux kernel version they initially shipped with so there also needs to be quite long support time (4.4 is still supported with Pie).
Click to expand...
Click to collapse
Thank you..So I have to wait till los 15.1 go stable

Hi, thanks for this build, I might have done something wrong as I can't past the setup wizard, after security setup it comes back to lineageOS startup screen and the begin button to start again the setup wizard

s1lex said:
Hi, thanks for this build, I might have done something wrong as I can't past the setup wizard, after security setup it comes back to lineageOS startup screen and the begin button to start again the setup wizard
Click to expand...
Click to collapse
I've heard about this but can't reproduce it myself and I haven't seen any logs (logcat). You could try using another faster sdcard. Some people have also removed the SetupWizard apk from the image manually.

Hi there,
Thanks for amazing work!
The only issue I'm experiencing is some flickering in graphic heavy and full screen apps. Am I doing something wrong or it's a known issue?
I just noticed that it's happening more when I use: "dtoverlay=vc4-fkms-v3d,cma-256"
But with dtoverlay=vc4-kms-v3d,cma-256 composite video output is not there. Any solutions?

[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?

[ROM][13.0][Daredevil] LineageOS 20.0 [UNOFFICIAL]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS for Nokia 7.2
About LineageOS
LineageOS is a free and open-source operating system for set-top boxes, smartphones and tablet computers, based on the Android mobile platform. It is the successor to the custom ROM CyanogenMod, from which it was forked in December 2016 when Cyanogen Inc. announced it was discontinuing development and shut down the infrastructure behind the project. Since Cyanogen Inc. retained the rights to the Cyanogen name, the project rebranded its fork as LineageOS.
LineageOS was officially launched on December 24, 2016, with the source code available on GitHub. Since that time, LineageOS development builds now cover more than 185 phone models with over 1.9 million active installs,having doubled its user base in the month February–March 2017 And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Whats working?
Wi-Fi
RIL
Volte
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint
FM radio
Sound
vibration
Bugs ?
Let me know if you see anything else. Especially please mention the issue and attach the logcat.
Installation process
Click Here for Installation process
Credits
* LineageOS Team for rom source
* Nokia for kernel source​
Download Rom
Download TWRP
Join Community Group
Android OS version: 13.0
Security patch level: 2023-01
Build author: Raghu varma
Kernel source code : android_kernel_nokia_LC-SDM660
Source code: https://github.com/LineageOS

Note - please take your data backup and do clean flash as per the instructions linked in the main thread. On top of it, my builds will boot on any stock firmware as base. So there is no special recommendation towards which stock rom you need to be on.
Changelog - Sun Jan 22 19:01:23 UTC 2023
============================
• Initial Android 13 build
• Based on android-13.0.0_r20
• Improved system stability
• User interface enhancements
• Google security patch 2023-01
• Selinux enforced
• Vendor built from Source
• Imported CTS profile patches
• Safety net pass by default & no need zygisk
• Updated build fingerprint from Pixel 7 Pro (cheetah)
Reminder - for reporting bugs please mention the issue and attach the logcat.
Thank you!

Awesome..!

Any chance it would run on Nokia 8.1 after unlocking/rooting with Hikari files ?
I'm mean ... someday / when updates are over .

Changelog Sat Apr 3 08:41:31 UTC 2020
===================================
1. Initial stable build
2. March security patch
3. Comes with stock kernel
4. Linux version 4.4.194
5. Vendor image from 2250
6. System blobs from 2250
7. Ota support available
Note- Installation process changed so please go ahead and follow the instructions as I mentioned in installation section

I tested now and I found Google Services - are GApps included? I installed lineageos in this build to AVOID this. Or did I make something wrong?

overclockA said:
I tested now and I found Google Services - are GApps included? I installed lineageos in this build to AVOID this. Or did I make something wrong?
Click to expand...
Click to collapse
Thanks, saved me some time. Defeats the entire purpose for me.

xe500linux said:
Thanks, saved me some time. Defeats the entire purpose for me.
Click to expand...
Click to collapse
I wrote to Raghu varma for the same question.
Technically it seems to not be that simple - if lineage 17.1 has been compiled without gapps and the build process was done by using private keys, flashing gapps would brick the device or the lineageos installation.
So Raghu varma compiled the version with gapps included to avoid this.
So I took his scripts from github and I built lineageos 17.1 on my own (with private keys and without gapps as I don't think about flashing them afterwards) - this worked fine.
Now I couldn't find his scripts for Daredevil on his github profile anymore - maybe they will come back for the 7.2 build process.

overclockA said:
I wrote to Raghu varma for the same question.
Technically it seems to not be that simple - if lineage 17.1 has been compiled without gapps and the build process was done by using private keys, flashing gapps would brick the device or the lineageos installation.
So Raghu varma compiled the version with gapps included to avoid this.
So I took his scripts from github and I built lineageos 17.1 on my own (with private keys and without gapps as I don't think about flashing them afterwards) - this worked fine.
Now I couldn't find his scripts for Daredevil on his github profile anymore - maybe they will come back for the 7.2 build process.
Click to expand...
Click to collapse
Ah I see. Any chance you still have a copy of your non-g build?

xe500linux said:
Ah I see. Any chance you still have a copy of your non-g build?
Click to expand...
Click to collapse
This should be OK. I'll upload a copy and send a link.
Be aware that the security patch level is dated on march 2020 and doesn't include the latest Google security patches from june.

overclockA said:
This should be OK. I'll upload a copy and send a link.
Be aware that the security patch level is dated on march 2020 and doesn't include the latest Google security patches from june.
Click to expand...
Click to collapse
Much appreciated!!

i posted already in the twrp thread of my problem "touch not working with twrp", that's still persisting.
so i got another idea. i used adb commands to control twrp. like you know, adb shell twrp sideload and then do the adb sideload commands for installing lineageos 17.1.
what did i do so far is:
*flash twrp 3.4.0
*boot up to twrp 3.4.0
*use adb shell twrp remountrw
*use adb to sideload lineageos 17.1 zipfile with commands (adb shell twrp sideload and then adb sideload lineageos.zip) - but the progress bar only goes to 47% and say like it would have "finished" - i dont believe in it
*use adb to sideload vendor zipfile zipfile with commands (adb shell twrp sideload and then adb sideload vendor.zip) - that one works normally
*changed slot from B (i was on before) to A on fastboot and flashed the vbmeta to current slot (A)
*reboot without wiping system partition and installing lineageos only brings up normal stock rom
*even wiped system partition one time (or should i say system_root?) - and installed lineageOS via adb sideload. but nothing was in the system_root folder as i mounted it back again
*wiping system partition and reboot only brings up android one loading screen endlessly
so basically, the installer says it has installed the rom, but in reality it didnt seem to touch the system partition at all. am i doing something wrong or may it be that because i dont have touch access i miss to move some unlock slider which is not implemented via adb shell twrp? i think something along these lines might be the case but.. i was able to adb shell twrp wipe system. so basically it should not be a big deal to write to system partition or system_root in general.
oh and of accusation that the adb sideload probably doesnt send data correctly (from which i heard lots of stories of the past), i even pushed the zip file via adb push to / and installed it with adb shell twrp install /lineageos.zip. same result.
what i would really like to see is an debug log of the installer zip. you only see "part 1 and part 2" installing and percentage, but no informations what the installer is doing currently. this would help a lot if there would be a switch for the installer like "verbose information"
edit again.
I finally managed to do the install. You know what? it is possible without the touch gui. what i did was:
*reflashed via fastboot the stock rom
*booted normally, installed the latest upgrade (Stock ROM OTA - took a long while) - (may be obsolete)
*booted to fastboot, flashed newest twrp to boot
*booted to recovery
*adb shell twrp remountrw
*adb shell twrp remountrw (the /tmp/recovery.log showed interestingly at first remountrw the page set of readonly, at second time not - why?)
*adb shell
*entered in adb shell mount /system
*adb shell twrp wipe data
*adb push lineageos.zip /data/
*adb shell twrp install /data/lineageos.zip
*adb push ddv.zip /data/
*adb shell twrp install /data/ddv.zip
*adb shell getprop ro.boot.slot_suffix (to get the actual boot slot)
*adb reboot bootloader
*fastboot --set-active=_a (for me i was on b before, so i needed to go to a)
*fastboot flash vbmeta_a --disable-verity --disable-verification vbmeta.img
*fastboot reboot
*then the phone - now on lineage - asked me to factory reset, i did
*booted finally successfully up to lineage 17.1 - wlan, mobile network working just fine
if you want gapps on it, install them ideally direct after your custom rom is able to boot. in my case gps didnt worked with gapps and other apps till i did another factory reset. and the original launcher that comes with the cust-rom doesnt work anymore after installing the gapps. use the pixel launcher instead. after that, it works like a charme
in conclusion: a bit odd how the install not works as in the description was told. maybe the TA-1196 is just a bit different.

Hello Together,
i've installed LineageOs yesterday and i realy like it . I just can't find an camera App that supports the wideAngle Camera at the back.
Open Camera only recognizes 2 Cameras, and GCam 7.0 Nokia 7.2 Mod can't seem to access it either.
Is there a solution to this?
Best regards
Alex

Changelog Fri Nov 13 23:24:47 IST 2020
==============================
- based on latest lineage sources
- November 2020 security patch
- fixed bluetooth audio
- fixed mic
- fixed RIL
- fixed headset
- based on android 10 prebuilt vendor for now ( DDV2.340 )
- Comes with stock kernel
- linux version 4.4.192
- compiled using gcc
- fixed battery drain
- fixed styles and wallpapers
- selinux enforced
- banking apps working
- use NikGapps

Got brand new nokia 7.2 yesterday, developer loaded old android build 1_130 and unlocked bootloader, didnt recommend twrp as this wol break wi-fi. Can I flash this OS on my phone directly without twrp ? will wifi and camera work as it should? Sorry for the questions I am new here and just started reading this Thank you

Nokia is nowadays very slow in giving security patch updates to its devices. Its a high time we switch to custom rom..?
I'm waiting for my phone's warranty to get over. Anyways, do anyone have any eta on when this rom will get official?

I have managed finally to install it, but sorry, nothing mentioned work: no double tapp sleep or wake up, no fingerprint, no slinux enforced, camera is not worth to mention at all and i still didnt test bluetooth or microphones yet. ..

dariuslapsys said:
I have managed finally to install it, but sorry, nothing mentioned work: no double tapp sleep or wake up, no fingerprint, no slinux enforced, camera is not worth to mention at all and i still didnt test bluetooth or microphones yet. ..
Click to expand...
Click to collapse
I agree for tapp to wake up and selinux.
Nevertheless, bluetooth and microphones and fingerprint sensors are working like a charm.
NFC is not mentioned anywhere, but I don't need this function at all.
I installed the build from 14/11.
@Raghu varma: Can we help you out sending logfiles for some issues? Do you need testers?

Raghu varma said:
Note - Iam Not Responsible for bricked devices
About LineageOS
LineageOS is a free and open-source operating system for set-top boxes, smartphones and tablet computers, based on the Android mobile platform. It is the successor to the custom ROM CyanogenMod, from which it was forked in December 2016 when Cyanogen Inc. announced it was discontinuing development and shut down the infrastructure behind the project. Since Cyanogen Inc. retained the rights to the Cyanogen name, the project rebranded its fork as LineageOS.
LineageOS was officially launched on December 24, 2016, with the source code available on GitHub. Since that time, LineageOS development builds now cover more than 185 phone models with over 1.9 million active installs,having doubled its user base in the month February–March 2017 And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Installation procedure
Note - I don't recommend you people to flash any other custom kernels on this ROM untill Nokia release kernel sources. Because this ROM supports only stock kernel .
1. Download Rom.zip , twrp.img & vbmeta.img
2. power off your phone boot in to bootloader mode and flash twrp
3. Boot in to Twrp
4. Format data by typing yes
5. Wipe everything
6. Flash rom.zip & vendor.zip
7. Now tap on reboot and check your current active slot.
Example - if twrp shows current active slot A change to B if B change to A
8. Tap on reboot and tap on bootloader ( this will reboots your phone to bootloder mode )
9. Now open cmd in pc flash vbmeta using this command
for slot-a > fastboot flash vbmeta_a --disable-verity --disable-verification vbmeta.img
for slot-b> fastboot flash vbmeta_b --disable-verity --disable-verification vbmeta.img
( thanks to @singhnsk for this step )
10. now type fastboot reboot
and wait for 3 min rom will boot up
Credits
* LineageOS & CO (For Source Code)
* All the authors in my git sources
* Nokia For Prebuilt Vendor & Kernel Source
* Moderators (For Giving Freedom To Post Threads)
* My entire Nokia 7.2 community Thank you all for your massive support Again
​Join Nokia 7.2 Community​
​
Download Rom
Download Vendor
Download vbmeta
Download GApps
Download Official Twrp
Android OS version: 11.0.0_r17
Security patch level: November 2020
Build author: Raghu varma
My build script: https://github.com/RaghuVarma331/scripts
Kernel Source code: https://github.com/RaghuVarma331/android_kernel_nokia_sdm660
Source code: https://github.com/LineageOS
Click to expand...
Click to collapse
When i install this rom volte function not proper working outgoing not work incoming volte works reply what is this

When i install this rom volte function not proper working outgoing not work incoming volte works reply what is this

[ROM][UNOFFICIAL][alpha] LineageOS 17.1 for Redmi K30 5G (picasso) (20200419)

{
"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"
}
WARNING
DO NOT try to install this on the non-5G version of Redmi K30. This ROM is ONLY intended for Redmi K30 5G and they are NOT the same device. Their difference is more than just 5G or non-5G.
Introduction
This is an UNOFFICIAL port of LineageOS 17.1 (based on Android 10) for the device Redmi K30 5G, codenamed Picasso.
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's working
- All basic mobile phone features (Wi-Fi, Bluetooth, Cellular Data, Phone Calls, SMS, etc., incl. 5G and VoLTE)
Known Issues
- (For Chinese Users) NO Alipay / WeChat Pay fingerprint support, and no plan to add support for them. Ask Alibaba / Tencent to support the standard Android biometrics API, not me to make my ROM support their API.
- 3.5mm jack does not work for some reason. (Will be fixed in the next release) Fixed since 20200311
- Wi-Fi display is not implemented since I have no device to test it on
- VoWiFi is not tested since I have no carrier support
- No 5G toggle. You cannot disable / enable 5G support. It's on by default and it goes to 5G if it can. (Note: there seems to be a dedicated network type option now in settings - mobile network for 5G NR, but I checked AOSP source code and that's only for 5G SA, and 5G NSA still falls under LTE, not the NR type)
- CTS does not pass because xiaomi's build fingerprint is not CTS-verified. You are on your own finding a solution to this. (Hint: Magisk modules)
- (For Developers) I cannot build a working DTB image from the sources provided by Xiaomi. I do not know the exact reason and for now I'm using prebuilt DTB and DTBO images, which you can extract from the official ROM and its boot.img.
- I'm not sure if there is any other issue, but at least nothing deal-breaking for me.
Instructions (Install / Upgrade) (IMPORTANT)
Side Note: I am fully aware that there is a TWRP port for this device, however it seems to be based on a modified version of TWRP whose source code I cannot find. The official TWRP repository (that I can see) does not even support Android 10 dynamic partitions yet, let alone porting it to this device. Of course it is possible that the author of that TWRP port has access to some internal testing version of TWRP, but since I cannot access the source code either way, I cannot do tests on the TWRP port. The LineageOS recovery I ported is adjusted specifically for this ROM and I have only tested the ROM on my LineageOS recovery port. If you choose to use the TWRP port, you are on your own, and do not ask me for problems you may encounter by using that port.
1. Install LineageOS 17.1 Recovery following my guide in the other thread (https://forum.xda-developers.com/re...covery-lineageos-recovery-17-1-redmi-t4059879), DO NOT use TWRP because it will NOT work for devices with dynamic partitions.
2. Reboot to LineageOS Recovery, wipe all data (skip if you are upgrading) (BACKUP ALL YOUR DATA TO A COMPUTER BEFORE FLASHING)
3. Flash required OFFICIAL MIUI version via adb sideload before flashing LineageOS 17.1. (consult the Downloads section for the corresponding MIUI version required for each LineageOS release)
- Flash OFFICIAL, not Xiaomi.eu or any other modified version.
- You can skip this step if you already have the required MIUI firmware + vendor version flashed before (e.g. if you upgrade from an older release of my LineageOS port and I did not change the required MIUI version)
- You can choose to try installing LOS on non-tested MIUI versions, though they are not tested so expect some hiccups or even disasters.
- DO NOT just flash the firmware of the required MIUI version. Always flash the full MIUI ROM (no additional wiping needed if you do not actually boot into MIUI). This ROM depends on the vendor partition provided by MIUI to work. You will need to flash at least the firmware PLUS the vendor and odm partition images of its required MIUI version for the ROM to actually work.
4. Flash LineageOS 17.1 zip via adb sideload
5. Reboot to Recovery (If you want to install Magisk or OpenGAPPS or both, else just reboot to system
6. Select "Mount /system" in the rebooted Recovery, ignore any error that may pop up on the screen
7. If you would like to, install Magisk (you MUST use a version later than or equal to 20.4)
8. If you would like to, install patched OpenGAPPS zip (available in Downloads section. You MUST use the patched OpenGAPPS for now.)
9. Reboot and enjoy. Magisk may cause your phone to double-boot (i.e. auto-reboot after the logo disappears) on first boot. If your phone boots up the second time then it will be fine.
Downloads
20200419: https://mega.nz/file/LAJjCYDT#L1Rd-WFJQ7SaU3vfAxU2y7AJsfH9qZ3fSAKMTQhgPWM
(MIUI firmware / vendor version tested on: miui_PICASSO_V11.0.11.0.QGICNXM_65ec88895f_10.0)
Changelog:
- Updated LOS source (April patch)
- You can now install the OFFICIAL version of Magisk >= 20.4 without modification
20200311: https://mega.nz/#!iB53SIKQ!ewdfMNFHmHjOemDDuYcgQO2t1KgrB9hx6YXYAdLKxU4
(MIUI firmware / vendor version tested on: miui_PICASSO_V11.0.11.0.QGICNXM_65ec88895f_10.0)
Changelog:
- Fixed 3.5mm jack support
- Lowered minimum allowable brightness to match the auto brightness curve
- Synchronized LineageOS 17.1 March Security Patch update
20200307: https://mega.nz/#!KQ5jkbAQ!dJspI92ls3BiVGk8FIGbVf4b4QBkwaaLUUr_NKX020A
(MIUI firmware / vendor version tested on: miui_PICASSO_V11.0.11.0.QGICNXM_65ec88895f_10.0)
Patched OpenGAPPS 20200306 (2): https://mega.nz/#!2EwVzAJR!NmBbO1_ao5ziyup6UVx64lZK06_VGNXSsFDA9T4sOO0
(Changelog: added `sync` after flashing to ensure everything is actually written to /system; also added a flag to `tar` to ignore creation times because that seems to break sometimes in our recovery)
Patched OpenGAPPS 20200306: https://mega.nz/#!2NgHXL6T!Z7J6AbJ7i4y9AuflIF0v_7KLbAO8XVV4ACsk13oz380
(What's patched: the `busybox` included in OpenGAPPS cannot mount the system partition as Read-Write in LineageOS Recovery for some reason. I edited the install script to use the `mount` command provided by the recovery instead of busybox. Also I removed the unmounting at the end of installation since it seem to stall the whole recovery, which means you will have to flash OpenGAPPS at the very last of your flashing process.)
XDA:DevDB Information
LineageOS 17.1 for Redmi K30 5G, ROM for the Redmi K30 5G
Contributors
PeterCxy
Source Code: https://github.com/PeterCxy/android_device_xiaomi_picasso
ROM OS Version: Android 10
Version Information
Status: Alpha
Created 2020-03-08
Last Updated 2020-03-08

I've been trying to compile the os from your device tree these days...now it's a waste of time
Anyway, I've followed you on GitHub. Thank you for doing so much!

zhufucdev said:
I've been trying to compile the os from your device tree these days...now it's a waste of time
Anyway, I've followed you on GitHub. Thank you for doing so much!
Click to expand...
Click to collapse
Sorry for that, you need some additional patches in LineageOS to actually build it successfully (you can search for patches by me on LOS gerrit: https://review.lineageos.org/q/owner:peter%40cxy.moe). Also I haven't uploaded the prebuilt DTB / DTBO image in my device tree. You will need to extract those on your own (or maybe you can help me figure out why the official open-source version does not work)

PeterCxy said:
Sorry for that, you need some additional patches in LineageOS to actually build it successfully (you can search for patches by me on LOS gerrit: https://review.lineageos.org/q/owner:peter%40cxy.moe). Also I haven't uploaded the prebuilt DTB / DTBO image in my device tree. You will need to extract those on your own (or maybe you can help me figure out why the official open-source version does not work)
Click to expand...
Click to collapse
I'm sorry but I am basically a noob on ROM porting. I'm only familiar with some basic linux commands and Android developing.

Hi, there! There is something I can't figure out:
Is there any checksums for ROM?
BTW, is there any force encryption feature in LineageOS?
However, thanks for your ROM.

RiverYKB said:
Hi, there! There is something I can't figure out:
Is there any checksums for ROM?
BTW, is there any force encryption feature in LineageOS?
However, thanks for your ROM.
Click to expand...
Click to collapse
No checksum, but since Mega.nz uses end-to-end-encryption it should do checksum on its own. Also you can verify the package against testkeys.
Force encryption is of course enabled by default.

PeterCxy said:
No checksum, but since Mega.nz uses end-to-end-encryption it should do checksum on its own. Also you can verify the package against testkeys.
Force encryption is of course enabled by default.
Click to expand...
Click to collapse
I'm just worrying about my downloaded ROM. Because you know some of E2EE file send platforms (such as Mega.nz) is being blocked by Chinese Gov. ?So I have to download with VPN.
But it's just fine.

Do not try it on the non 5G K30, oh ok means now I definitely have to try it.

Ya_SG said:
Do not try it on the non 5G K30, oh ok means now I definitely have to try it.
Click to expand...
Click to collapse
You may have better luck trying a K20 ROM on non-5G K30 than trying this one. The non-5G K30 shares the same kernel source tree with K20 instead of K30 5G. (of course, existing K20 kernels and thus ROMs do not even support dynamic partitions, so you would probably not be able to boot either way)

Hi!
I know I'm a really noob, but I ran into a problem.
So before I flash LineageOS, my /sdcard and /data is already encrypted.
And I backed my files to /sdcard, then I wiped /data and flashed LineageOS.
I can boot to LineageOS properly now, but I can't access my backup files in /sdcard, it's all garbled.
Is there any way to help?
Thank you very much.

RiverYKB said:
Hi!
I know I'm a really noob, but I ran into a problem.
So before I flash LineageOS, my /sdcard and /data is already encrypted.
And I backed my files to /sdcard, then I wiped /data and flashed LineageOS.
I can boot to LineageOS properly now, but I can't access my backup files in /sdcard, it's all garbled.
Is there any way to help?
Thank you very much.
Click to expand...
Click to collapse
looks like you have wiped the encryption keys for some reason. Unfortunately, there's nothing I can do to help in this case.

RiverYKB said:
Hi!
I know I'm a really noob, but I ran into a problem.
So before I flash LineageOS, my /sdcard and /data is already encrypted.
And I backed my files to /sdcard, then I wiped /data and flashed LineageOS.
I can boot to LineageOS properly now, but I can't access my backup files in /sdcard, it's all garbled.
Is there any way to help?
Thank you very much.
Click to expand...
Click to collapse
Hi RiverYKB
The point I guess is to decrypt the data partition, which can be easily done using a TWRP recovery. So I suggest flashing TWRP via fastboot with your computer. You should be able to decrypt your data with the password set before lineage os was flashed.

Updated 20200311

PeterCxy said:
Updated 20200311
Click to expand...
Click to collapse
it looks like bootloop after flash 0311 version, logcat file below
htdeletemetps://drive.google.com/file/d/1INO9nNnEyR_JxmJRvZzhNrOVfWrDIuwv/view?usp=sharing

Cedric1223 said:
it looks like bootloop after flash 0311 version, logcat file below
htdeletemetps://drive.google.com/file/d/1INO9nNnEyR_JxmJRvZzhNrOVfWrDIuwv/view?usp=sharing
Click to expand...
Click to collapse
Your issue seems gapps-related. Make sure you flash my patched version of gapps, not the official version. Did you upgrade to 0311 from 0307 or just flash 0311? If you upgraded, make sure you re-flash gapps after the upgrade.

I will try when next update comes, thank you for your great rom port
PeterCxy said:
Your issue seems gapps-related. Make sure you flash my patched version of gapps, not the official version. Did you upgrade to 0311 from 0307 or just flash 0311? If you upgraded, make sure you re-flash gapps after the upgrade.
Click to expand...
Click to collapse

This rom working on poco x2 4g?

fromjeet said:
This rom working on poco x2 4g?
Click to expand...
Click to collapse
of course not

It looks like if I set a password for Hotspot, other devices can not connect this hotspot
if no password for hotspot, it works perfectly

Thanks for your ROM since I have been using it for a couple of days with no critical problem found. However,
1. Since 5G NSA falls under LTE, is it possible to make it displaying "NR" or something else to indicate that the phone is on 5G network? If impossible, is there any other ways to know whether the phone is on 5G or not?
2. Is there a working root solution for it?
Thank you for your time and effort