Related
Here is first attempt to build LineageOS 14.1 for XiaoMi MiPad
Current state is: mostly working
I finally found solution to fix old mipad stock graphic blobs to load on cm13 and Los 14.1. This build is proof of concept to show it is possible to have Nougat on old good MiPad.
What working:
WiFi (better than 12.1, now using opensource wpa_supplicant)
Sensors (autorotation works)
LEDs
audio including microphone
hardware accelerated video playback
camera
What not working:
audio (currently plays only some system sounds, all other failed because of wrong PCM format)
camera
[*]lineage Music add doesnt play anything (3rd paty players seems to work fine)
[*]windevine drm not working (need updated liibs, to be done in next build)
[*]probably hardware acceleration playback (missed symbols for some omx libs)
[*]not enough space to install gapps into /system partition
[*]random crashes going to system ui restart loop
webview crashing with ERROR:gl_fence_egl.cc(63)] Failed to wait for EGLSync. error:EGL_BAD_MATCH (gapps and play market unusable)
Github links:
Device tre (cm-14.1 branch)
Vendors blobs (cm-14.1 branch)
Kernel (cm-14.1 branch)
2017-02-16
Download:lineage-14.1-20170216-UNOFFICIAL-mocha.zip
Changelog:
Initial release
2017-02-20
Changelog:
Audio fixed
Using patched webview, gapps should work now
SD card and usb mounting fixed
Download: lineage-14.1-20170220-UNOFFICIAL-mocha.zip
2017-02-26
changelog:
random crashes and black screens resolved
new Audio HAL based on opensource tinyhal (microphone works now)
big system partition (1.2Gb). You have to install it on merged system1 and system2, if you have already merged just install.
SD card mount fix included (access to SD card from all apps)
hardware accelerated video playback now works
cleaned some useless blobs like powerservice daemon
updated wifi firmware
Download:lineage-14.1-20170226-UNOFFICIAL-mocha.zip
2017-03-03
Changelog:
Fixed mp3 and flac playback in Music app (disabled offloading since it broken for mp3 and enable ffmpeg for other formats)
Updated wvm libs, Widevine DRM L3 now works
Download: lineage-14.1-20170303-UNOFFICIAL-mocha.zip
2017-03-11
Changelog:
KeyDisabler (alow to enable navbar and disable hardware buttons)
Vibrator intensity control
hwui props in build.prop makes screen more stable in browsers (black pixels on screen issue)
Updated LED capabilities (RGB notification, settings for battery and notification colors, button backligth brightness)
Userspace cpuquiet governor by default. Looks like this is best option to get smooth playback. (cores dosnt switches off but only changes its freq)
Fixed offline charging mode. Now shows animaton with current battery level. Also previous 14.1 builds cant be offline charged from PC USB port, now this issue resolved
return glcomposer compositor. Now looks stable, it should be because of hwui right props added. *broken*
Download: lineage-14.1-20170311-UNOFFICIAL-mocha.zip broken
2017-03-12
composer changed back to surfaceflinger. Solves issues with blck screen or reboots in 20170311 build
Download lineage-14.1-20170312-UNOFFICIAL-mocha.zip
2017-04-21
test version with Nexus 9 blobs
webview slow work resolved with new graphic blobs
Browser replaced with Gelllo
lineage code updated up to 7.1.2
Known issues:
Bluetooth broken
Doesnt load proper mac address
Some graphic issues in general user interface
Download: lineage-14.1-20170421-UNOFFICIAL-mocha.zip
Download fixed boot.imgboot-20170429.img - fixes wifi and bluetooth issues on 2017-04-21 lineage 14.1 build.
2017-05-02
Changelog:
camera works now
Browser replaced with Gelllo
lineage code updated up to 7.1.2
Known issues:
this build still uses old graphic blobs, so webview apps is laggy.
if camera doesnt work after dirty flash try to delete /data/nvcam folder from adb root console or root file manager
Download: lineage-14.1-20170502-UNOFFICIAL-mocha.zip
Webview apk is one patched to work on broadcom GPU with same problem as ours: https://github.com/manumanfred/android_external_chromium-webview
2017-09-11 NEW!
Changelog:
Lineage OS 14.1 sources updated
Webview updated and rebuilt with only changes necessary for Mi Pad. Most of webview related issues now resolved. Faster and smoother scrolling in webview based apps, some apps now startings works, like Gogle Books. See webview patch applied below.
device tree cleaned for proper work with proprietary blob files. Now they can be extracted from stock rom or device and makefiles can be properly generated in vendor.
Using opensource version of libbt-vendor - maybe some changes in bluetooth perfomance.
Download lineage-14.1-20170911-UNOFFICIAL-mocha.zip from Google Disk or from MailRu mirror
Webview patch applied:
Code:
diff --git a/gpu/config/gpu_driver_bug_list.json b/gpu/config/gpu_driver_bug_list.json
index b8f5489ce086..6bf7f9250237 100644
--- a/gpu/config/gpu_driver_bug_list.json
+++ b/gpu/config/gpu_driver_bug_list.json
@@ -1,6 +1,6 @@
{
"name": "gpu driver bug list",
- "version": "10.93",
+ "version": "10.94",
"entries": [
{
"id": 1,
@@ -2542,6 +2542,19 @@
"features": [
"rely_on_implicit_sync_for_swap_buffers"
]
+ },
+ {
+ "id": 236,
+ "description": "MiPad Nvidia drivers g_ignore_egl_sync_failures work around",
+ "cr_bugs": [123456],
+ "gl_vendor": "NVIDIA.*",
+ "machine_model_name": ["MI PAD"],
+ "os": {
+ "type": "android"
+ },
+ "features": [
+ "ignore_egl_sync_failures"
+ ]
}
],
"comment": [
special patched webview prebuilts located here https://github.com/HighwayStar/android_external_chromium-webview (branch cm-14.1-mocha)
Merge partitions
Mi Pad by default has 2 /system partition, each 640Mb. It is not enogh to install LineageOS and Gapps. To install 2017-02-25 build and newer you have to merge 2 system partition in one 1.2Gb system partition. To dod this follow instruction http://en.miui.com/thread-118294-1-1.html
Root Access
If you want root access flash addonsu-arm-signed.zip from https://download.lineageos.org/extras
XDA:DevDB Information
LineageOS 14.1 for Xiaomi MiPad (mocha), ROM for the Xiaomi Mi Pad
Contributors
highwaystar_ru, highwaystar_ru
Source Code: https://github.com/HighwayStar/android_device_xiaomi_mocha
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod, LineageOS
Version Information
Status: Alpha
Created 2017-02-16
Last Updated 2017-09-11
Reserved
If you have problem installing newer latest build, or just to be sure it will install fine check you system partition with DiskInfo app. It should show System partition at least 1337564160 bytes.
First! Holy ****, I never thought I'd see the day...
@highwaystar_ru Is there not enough space in /system even after merging system1 and system2?
EDIT: If anyone wants root: https://download.lineageos.org/extras
Unbelievable
Damn dude, you rock....!!
the future of mi pad 1 is getting brighter because of you.....!!
drakonizer said:
First! Holy ****, I never thought I'd see the day...
@highwaystar_ru Is there not enough space in /system even after merging system1 and system2?
Click to expand...
Click to collapse
On merged system it is enogh space, but now /system in rom configured to match stock /system. Not sure for now if it possible to remove LineageOs stock app like browser and email and free some space or just use bigger /system and require to repartition.
Woah
Impressive.
highwaystar_ru said:
On merged system it is enogh space, but now /system in rom configured to match stock /system. Not sure for now if it possible to remove LineageOs stock app like browser and email and free some space or just use bigger /system and require to repartition.
Click to expand...
Click to collapse
We could do that...remove some unnecessary packages from https://github.com/LineageOS/android_vendor_cm/blob/cm-14.1/config/common.mk with a PRODUCT_PACKAGES -= line in the device.mk.
But asking users to repartition to install gApps is better in my opinion, for future official Lineage support. There could be a check in the updater_script to verify the user has repartitioned.
I am pretty sure there is no re-configuration necessary to support repartitioned /system partitions.
Does that mean CM12 development is dropped?
MiliWanili said:
Does that mean CM12 development is dropped?
Click to expand...
Click to collapse
Do you want the latest nougat or old lolipop
OMG... unbelievable....first 7.1.1 on mipad...
Xiaomi, shame on you
and thank you! highwaystar!
AbhaYsinGH007 said:
Do you want the latest nougat or old lolipop
Click to expand...
Click to collapse
Lollipop if it comes faster.
If it possible to make los14.1 run stable and sound working it is better to go with los14.1. At least it has upstream support, and some things here works better. I cant make opensource wpa_supplicant working on 12.1, but here it works. Microphone in cm12.1 is also hard to fix, because there is only LD_PRELOAD for lib and microphone require MonoPipe class from 4.4 to work, but it will break other things. On cm13 or los14.1 it is possible to use LD_SHIM_LIBS to fix only broken libs and not break working.
For now I'm trying what cause los14.1 unstable, sometimes it may work for hours, but when it crashed to black screen and buttons backlight it starts endless bootloop.
Unbelievable
Never expected los14.1 on mi pad.
Awsome,, nice work bro
Xiaomi Mi Pad with the latest OS. Awesome Dev!
Awesomeeeeeee! Highwaystar. You are simply awesome. never expected the lineageOs, that too for Mi pad. and now you are our only hope.
Holy moly... Would be flashing this baby once we get the camera and hardware acceleration sorted out... This is why I LOVE XDA and the developers here....
drakonizer said:
First! Holy ****, I never thought I'd see the day...
@highwaystar_ru Is there not enough space in /system even after merging system1 and system2?
Click to expand...
Click to collapse
Did you tried least gapps.
---------- Post added at 12:26 PM ---------- Previous post was at 12:25 PM ----------
drakonizer said:
First! Holy ****, I never thought I'd see the day...
@highwaystar_ru Is there not enough space in /system even after merging system1 and system2?
Click to expand...
Click to collapse
Did you tried gapps Pico version
awesome awesome awesome unbelievable ::good::good::good::good::good:
{
"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.
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?
WirusMOD Nethunter Kernel for StockOreo, StockPie, StockQ, LineageOS 16.0 & 17.1, Treble [End Of Life]
Samsung Galaxy S7 / Edge
Code:
I am not responsible for bricked devices.
If you going to flash it, you accepted it.
Of course your warranty is void.
This thread is only for herolte . If you have Edge go here
Nethunter Features:
BadUSB
HID gadget keyboard/mouse (with possibility to temporarily disable)
DriveDroid
USB WiFi, mac80211 (Monitor mode, packet capture, packet injection) [Compatibility List]
support rtl88xxau USB WiFi
Ethernet
F2FS
Bluetooth HCI USB support
RTL-SDR DVB support
Extra:
Boeffla wakelock blocker v1.10
Wireguard
Download:
Latest version G93XF here.
Old download link G93XF here.
Installation:
1. TWRP Backup your ROM
2. Flash Nethunter Kernel
3. Flash latest Magisk
4. Install busybox can be one from Magisk repository
5. Install Nethunter Store
6. Install NetHunter apk, NetHunter Terminal, NetHunter KeX from Nethunter Store
7. In NetHunter apk go to Kali Chroot Manager and install chroot.
7. Extract Nethunter_Binaries.7z and binaries to folders:
Firmwares: system/etc/firmware and give permissions to every file rw-r--r--
hid-keyboard binary: system/xbin/ and give permissions to it rwxr-xr-x
8. Reboot
Loadable modules:
Modules_Nethunter_WirusMOD_vX.X.7z extract only modules for your version of kernel.
In every kernel folder are modules and firmware. You need only modules which you want to use.
For example if you don't want use tuners and dvb-frontends. Don't load modules from /modules/drivers/media tuners and dvb-frontends
In firmware are compiled firmwares for some of modules to use they you need to copy they to system/etc/firmware.
basic commands:
insmod 88XXau.ko - load module
rmmod 88XXau.ko - unload module
lsmod - list loaded modules
Some modules depend on another modules. If you want load rt2800usb.ko, you need first load rt2800lib.ko.
Another way to load modules is Module Loader
Copy modules to storage and choose modules which you want to load (load they more than 1 times, this apk load modules from up to down it don't look at dependence from modules)
Extra:
In Utilities.7z are wifi testing tools binaries like aircrack-ng(Not needed for Nethunter only for test tools direct from android without Nethunter)
DriveDroid without bugs made by disabling HID Patch:
To disable HID Patch: use this command in terminal: "echo Y > /sys/module/g_android/parameters/hid_disable"
Changing mode isn't instant after changing module status. Use DriveDroid (mount iso -> dismount) to active hid_disable.
To enable HID Patch: "echo N > /sys/module/g_android/parameters/hid_disable" and use DriveDroid like with disabling HID Patch.
HIDPatchSwitch this is simple script which can switch between HID enabled and disabled and show changed status.
If HID attacks / USB keyboard(.apk) don't work at Linux. After plugin, change USB mode to MIDI or USB-tethering.
Old Installation:
1. TWRP Backup your ROM
2. Flash Nethunter Kernel
3. Flash latest Magisk
4. Install busybox can be one from Magisk repository
5. Install Magisk Nethunter module from repository it have all apps which are needed to get fully working Nethunter (Another version of Nethunter apk link)
7. Extract Nethunter_Binaries.7z to folders:
Firmwares: system/etc/firmware and give permissions to every file rw-r--r--
hid-keyboard binary: system/xbin/ and give permissions to it rwxr-xr-x
8. Reboot
Screens:
{
"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"
}
Credits:
morogoku for his MoRoKernel source
ananjaser1211 for his USB modes fix with OneUI based ROMs
Nethunter creators for the best portable penetration testing tool.
XDA:DevDB Information
[KERNEL] [G93xx] WirusMOD [Nethunter AiO], Kernel for the Samsung Galaxy S7
Contributors
Svirusx
Source Code: https://github.com/Svirusx/Nethunter-s7-kernel-WirusMOD-AiO
Kernel Special Features: Powered by MoRoKernel
Version Information
Status: Stable
Created 2019-06-27
Last Updated 2021-08-10
2021.08.10 - v2.7
Upstream to MoRoKernel v8.8.1
2021.06.05 - v2.6
Upstream to MoRoKernel v8.8
2021.06.03 - v2.4
Temporary back to v2.4 due flashing problems
2021.05.30 - v2.5.1(Removed due flash problem)
Used build script from MoroKernel.
Upstream to MoRoKernel v8.7
2021.04.30 - v2.5(Removed due flash problem)
Upstream to MoRoKernel v8.7
2021.01.13 - v2.4
Upstream to MoRoKernel v8.6.1
2020.11.17 - v2.3
Upstream to MoRoKernel v8.5
2020.09.20 - v2.2
Added rtl8188eu driver
2020.08.04 - v2.1
Upstream to MoRoKernel v8.4
2020.05.09 - v2.0
Enabled Netfilter Target TTL
2020.04.18 - v1.9
Cleaned HID patch
Upstream to MoRoKernel v8.1
2020.04.08 - v1.8
More modules integrated in kernel.
Fixed samsung code.
Removed unnecessary debug and log modules from kernel.
2020.04.06 - v1.7
support rtl88xxau
loadable modules support (due to size of boot.img)
updated to latest morokernel source 8.0.1
2020.03.06 - v1.6
Pie OneUI ROMs USB modes fix
2019-12-06 - v1.5
Added DVB drivers.
2019-11-30 - v1.4
Update kernel source to MoRoKernel AIO v7.6.1
2019-11-06 - v1.3
Update kernel source to MoRoKernel AIO v7.5
2019-10-19 - v1.2
Update kernel source to MoRoKernel AIO v7.4
2019-09-25 - v1.1
Update kernel source to MoRoKernel AIO v7.2
2019-08-26 - v1.0
Initial AiO release
Reserved
Will this work for samsung s7 with viperos and android pie 9?
Destroyer55 said:
Will this work for samsung s7 with viperos and android pie 9?
Click to expand...
Click to collapse
This is only for Stock Ported ROM look at answer in WirusMOD Oreo ROM
Destroyer55 said:
Will this work for samsung s7 with viperos and android pie 9?
Click to expand...
Click to collapse
Read that title
Should you just flash it or do you have to do some steps before, like deleting data ?
Dav21t said:
Should you just flash it or do you have to do some steps before, like deleting data ?
Click to expand...
Click to collapse
This is only kernel. Normally you can flash it on your Note port ROM without data wipe but backup is alltime recommended.
NFE V4
Thank you Bro, I was waiting for it.
My question is : Is it working with NFE BD V4 ? and with an External adapter, I have a TP-Link WN722N
nawfalino said:
Thank you Bro, I was waiting for it.
My question is : Is it working with NFE BD V4 ? and with an External adapter, I have a TP-Link WN722N
Click to expand...
Click to collapse
This kernel is based on MoRoKernel. If MoRoKernel is compatible with NFE BD V4 than it too must work.
Compatibility depends at version of TP-Link WN722N do you have. You need test it.
Backup before flash is recommended.
Hey I'm having problems with usb HCI it does not work for me. Any solutions ?
Thanks for this!
Just wondering whether its possible to include kvm support for this kernel.
@Svirusx Wait what toolchain did you use to compile this? Whenever i try to compile it goes for about 20mins and then gets up to compiling net/built-in.o and then just stops. No errors or anything. All i changed was i enabled kvm support in the morokernel defconfig.
Jack_Rickwood said:
@Svirusx Wait what toolchain did you use to compile this? Whenever i try to compile it goes for about 20mins and then gets up to compiling net/built-in.o and then just stops. No errors or anything. All i changed was i enabled kvm support in the morokernel defconfig.
Click to expand...
Click to collapse
Hey, i use normal google android toolchains.
Are there any benefits to have kernel virtual machine support in this phone?
I have compiled kernel with kvm support for test, based on last lines of this source. Not tested only compiled, i don't know if all those modules are needed to run kvm.
@Svirusx Hey, thx so much! KVM can be used with limbo (https://github.com/limboemu/limbo/wiki/KVM), which could possibly allow for virtualization of windows 10 arm, linux, etc, and possibly other upcoming emulators that use virtualization, from within a vm on android.
---------- Post added at 04:12 AM ---------- Previous post was at 04:03 AM ----------
The way you can tell if it worked is by seeing if the directory /dev/kvm exists.
Jack_Rickwood said:
@Svirusx Hey, thx so much! KVM can be used with limbo (https://github.com/limboemu/limbo/wiki/KVM), which could possibly allow for virtualization of windows 10 arm, linux, etc, and possibly other upcoming emulators that use virtualization, from within a vm on android.
---------- Post added at 04:12 AM ---------- Previous post was at 04:03 AM ----------
The way you can tell if it worked is by seeing if the directory /dev/kvm exists.
Click to expand...
Click to collapse
Thanks for link with official instruction i going to try integrate it and test. If it going to be stable with S7 i push as release for next version of kernel.
Alright, thx
Svirusx said:
This kernel is based on MoRoKernel. If MoRoKernel is compatible with NFE BD V4 than it too must work.
Compatibility depends at version of TP-Link WN722N do you have. You need test it.
Backup before flash is recommended.
Click to expand...
Click to collapse
Will there be a new version based on Morokernel 7.0.1 ?
Thank you in advance !
What's the comparison betqeen he s7 exynos8890 and the a8 exynos7885 kernels ?
Is it possible to compile a kernel on my phone
Just a week ago I flashed everything for installing the fully updated to 9.0pie samsung galaxy s7 sm-G930w exynos8890.
Finally a working nethunter phone smoother than my worn out nexus 6p. which I could not get to update nethunter past android 7.1.
But I lost my phones and my s7 yesterday and now I am stuck with an exynos7885 samsung a8(2018) .
which is a ok phone considering it has an unlockable boot loader here in Canada where the s9s and s10s all switched to Qualcomm.
Anyway.
I am not much of a coder or an app developer but I am very good at finding exploits.
I want to try and take the kernel of my sm-a530w a8 and possibly patch the nethunter from another samsung exynos kernel perhaps the s7.
Is it possible or does anyone know of a solution for me. I don't have a computer anymore either.
I just want to build my own kernel but I have no clue how especially with no laptop at hand. Thanks
Sent from my Samsung Galaxy A8 (2018) using XDA Labs
Svirusx said:
This kernel is based on MoRoKernel. If MoRoKernel is compatible with NFE BD V4 than it too must work.
Compatibility depends at version of TP-Link WN722N do you have. You need test it.
Backup before flash is recommended.
Click to expand...
Click to collapse
New Moro pie release
MoRoKernel v7.1 (EDGE & FLAT)
https://www.androidfilehost.com/?fid=6006931924117939132
Can you help me install your kernel with F2F2 support ?
WIPE/ADVANCED WIPE/DATA
CHANGE FILE SYSTEM/F2FS
That enough ?
https://gitlab.com/hackintosh5/TrebleInfo
Credits
https://github.com/8890q/ for LineageOS 19.1/18.1 device tree, kernel, hardware support, blobs
https://forum.xda-developers.com/t/treble-aosp-g930x-g935x-project_pizza-trebleport-v2-0.3956076/ for libsensor blobs
https://github.com/osm0sis/ for anykernel, used for the twrp patching zip
Special thankshttps://github.com/ExpressLuke for hero2lte testing
https://github.com/00p513-dev for suggesting using squashfs for vendor partition, making it possible to skip partition table modding
https://github.com/phhusson for looking into the double tap to wake issues with phh GSI
https://github.com/ivanmeler for prompting me to look into lpm again, now it is migrated into /vendor
Notes:
I do not own a hero2lte(edge)
I'll mostly work on this only during weekends/holidays
and on that note the hero2lte build is not tested by myself
for vndk30 based vendor (LineageOS 18.1), use with android 11 and up GSIs
for vndk32 based vendor (LineageOS 19.1), use with android 12L and up GSIs
2022-06-12 the CACHE partition is now used as vendor, the HIDDEN patition is now used as cache, no more partition table mods required
Updates:
2023-02-23
added store_mode.zip flashable that uses "/sys/class/power_supply/battery/store_mode" and "/sys/module/sec_battery/parameters/store_mode_max" interfaces for limiting battery charging
flash to limit battery charging to 70%, flash again to disable charging limitafter flashing, charging limit can be adjusted at "/system/etc/init/8890_store_mode.rc" by changing "70" on the line "service enable_store_mode /system/bin/8890_store_mode 1 70" to other percentage values
2023-02-15
include libaptX_encoder.so in patchers
adding patches to support phh android 13 GSIs:
includes lineage lmkd, LineageOS/[email protected] seems required for lmkd to work on this kernelfix bluetooth audio by disabling sysbta (generic in-system bluetooth audio implementation), see phhusson/treble_experimentations#2519disable full disk encryption and quota when booting android 13, 8890q/[email protected] 8890q/[email protected] ; FDE still works when using android 12 GSIsdisable healthd offline charging service, conflicts with lpm
2022-10-04
update gps blobs from https://github.com/8890q/proprietary_vendor_samsung/commit/698ddd9acd7bdca78ecea93e06fd78a0d9dbc407
2022-09-05
adding keystore fixes to a12_patcher.zip:
https://github.com/LineageOS/android_system_security/commit/356c125115c0a9b9f9670b5b86b6e291c5ec5404
https://github.com/8890q/patches/commit/9a322b4e71ca784d4a2f71494d1ef0e52f835efe
which fixes keystore apps and device encryption on Google 12L GSI, might also fix some keystore apps issues on phh GSI
2022-07-10
moved lpm to vendor partition
2022-06-26
rebased vndk32 on 2022-06-24 build from ivan
new smaller vendor flasher, flashes only boot and vendor
2022-06-24
lpm_installer.zip should work with Phh and Andy Yan GSIs better now
2022-06-18
vndk30 prop changes, might help booting exotic GSIs
2022-06-13
android 12 data usage meter now works with a12_patcher.zip
2022-06-12
fixed neural network api hal
fixed fingerprint sensor
switched vendor image to squashfs, no CreateVendor required anymore with it's small size
new twrp patcher zip, should no longer cause "twrp is stuck after flashing CreateVendor"
bigger GSIs should fit better now with the original ~4.5GB SYSTEM partition; device native roms can be used without RevertVendor
2022-05-31
fixed wifi tethering
vndk32: rebased on 2022-05-26 12L build from ivan
phh_wifitethering_patcher.zip for wifi hotspot on phh GSIs
2022-05-26
added vndk32 based release
lpm_installer.zip for offline charging
fixed keystore errors on android 12 GSIs, lock screens work now
2022-02-15
rebased on February build from 8890q
January android updates
2021-12-16
install libaudioroute into /vendor/lib
December android updates
2021-12-10
move properties to /vendor
Tested GSIs
vndk30
https://github.com/phhusson/treble_experimentations/releases/tag/v313 (vanilla/bvS)
https://github.com/phhusson/treble_experimentations/releases/tag/v413 (vanilla/bvS)
https://developer.android.com/topic/generic-system-image/releases (android 12 gsi, with a12_patch.zip flashed after)
vndk32
https://github.com/phhusson/treble_experimentations/releases/tag/v413 (vanilla/bvS)
https://developer.android.com/topic/generic-system-image/releases (android 12 gsi, with a12_patch.zip flashed after)
important: system as root builds, you'd want ab build GSIs
Known issues:
some GSIs like official google GSIs lacks the /efs mount point, it has to be added manually or it will boot loop at samsung logo failing to mount /efs
some android 12 GSIs does not boot due to the lack of ebpf on the 3.18 kernel, android 12 GSIs needs to have patched bpfloader and netd, see below
https://github.com/8890q/patches
https://github.com/phhusson/platform_system_bpf/commit/c81966c23d79241458ebf874cfa8662f44705549
https://github.com/phhusson/platform_system_netd/commit/3a6efa1ff3717a613d1ba4a0eff5e751262d1074
data usage stays at 0 MB used on android 12 GSIs, because ebpf is used for metering
a12_patcher.zip attempts to fix the above issues by creating /system_root/efs and importing bpfloader+netd from https://github.com/8890q/patches
a11_patcher.zip creates /system_root/efs if required
usb adb does not work on android 12 GSIs
a legacy implementation of usb adb is required for this kernel, see https://review.lineageos.org/c/LineageOS/android_packages_modules_adb/+/326385
as a workaround, disable usb adb and use wifi adb
Wifi tethering does not work on phh GSIs <= 414
https://github.com/phhusson/vendor_hardware_overlay/tree/pie/Tethering conflicts with our Tethering overlay
flash phh_wifitethering_patcher.zip after installing phh GSIs
Alarm clock not working on aosp GSI
it should be fixed on phh 414 and up, it is not a vendor issue. If you are using an older aosp GSI, flash deskclock_powersaving.zip to fix that. See https://github.com/LineageOS/androi...mmit/8dd096c4cfb647960be1695a57246727878b8c8d
Google android 13 GSIs do not work
post-build patching got more involved in android 13 since on-java patches are now required, stick with phh/treble droid GSIs which already include build time patches for bpf-less kernel support
Disk encryption does not work on android 13 GSIs
full disk encryption is removed in android 13, file based encryption not available currently https://github.com/8890q/android_de...mmit/3cbcf972465419c18bf4850d26320896df465b18
Installation
If you are using the old partition table mod zip heroxlte_CreateVendor_2.0.zip from older versions, first flash heroxlte_RevertVendor_2.0.zip, or revert your partition table other ways such as odin. Skip this step if you have never touched your partition table
Install twrp-3.6.2_9-0 from https://eu.dl.twrp.me/herolte/ (s7) or https://eu.dl.twrp.me/hero2lte/ (s7 edge), as of rignt now newest(twrp-3.7.0_9-0) is too big for flashing
Flash twrp_patcher.zip to enable system.img flashing, it'll reboot to recovery once it's done, tested on 3.6.2_9-0 but newer versions should work unless recovery.fstab changes
Flash vndk32 for android 12.1(api level 32) and android 13.0(api level 33) GSIs, flash vndk30 for android 11(api level 30) and 12(api level 31) GSIs, herolte for s7 and hero2lte for s7edge
Flash the system.img of your choice
If you are using phh GSI version <= 414, flash phh_wifitethering_patcher.zip
If you are using phh GSI version <= 414, flash phh_dt2w_patcher.zip to fix double tap to wake
If you are using phh GSI version <= 413 or pure aosp, flash deskclock_powersaving.zip to fix alarm clock
If you are using an android 12/12L GSI, flash a12_patcher.zip
If you are using an android 11 GSI, flash a11_patcher.zip
If you are using a phh/treble droid android 13 GSI, flash phh_aosp13_patcher.zip
Updating vendor
Flash vndk32 for android 12.1(api level 32) and android 13.0(api level 33) GSIs, flash vndk30 for android 11(api level 30) and 12(api level 31) GSIs, herolte for s7 and hero2lte for s7edge
Undo twrp_patcher.zip and revert to device native romsThis is not required for using device native roms, however OTA updates might require this
Flash the newest twrp again
Format cache using wipe -> select cache -> repair or change file system -> change file system -> ext4
Flash a device native rom
Buildinglineage_build_herolte_vendor_part, lineage_build_hero2lte_vendor_part, lineage_build_herolte_vendor_part_18.1 and lineage_build_hero2lte_vendor_part_18.1 builds lineageos along with treble vendor using https://github.com/lineageos4microg/docker-lineage-cicd
you'll need ~15GB of free ram, ~300GB free disk space and podman
# create directories
mkdir src
mkdir zips
mkdir logs
mkdir ccache
# builds lineage 19.1 along with vndk32 for herolte (s7 flat exynos)
bash lineage_build_herolte_vendor_part
Reporting issues besides the known ones:
You can report them over https://github.com/Kethen/herolte_treble/issues
Downloadshttps://github.com/Kethen/herolte_treble/releases
katharinechui said:
Creditshttps://github.com/8890q/ https://forum.xda-developers.com/t/...e-spoofing-ota-updates-for-s7-exynos.4368995/ for LineageOS 19.1/18.1 device tree, kernel, hardware support, blobs
https://forum.xda-developers.com/t/treble-aosp-g930x-g935x-project_pizza-trebleport-v2-0.3956076/ for libsensor blobs
Notes:
I do not own a hero2lte(edge)
I'll mostly work on this only during weekends/holidays
and on that note the hero2lte build is not tested by myself
for vndk30 based vendor (LineageOS 18.1), use with android 11 and up GSIs
for vndk32 based vendor (LineageOS 19.1), use with android 12L and up GSIs
Updates:
2022-05-26
added vndk32 based release
lpm_installer.zip for offline charging
fixed keystore errors on android 12 GSIs, lock screens work now
2022-02-15
rebased on February build from 8890q
January android updates
2021-12-16
install libaudioroute into /vendor/lib
December android updates
2021-12-10
move properties to /vendor
Tested GSIs
vndk30
https://github.com/phhusson/treble_experimentations/releases/tag/v313 (vanilla/bvS)
https://github.com/phhusson/treble_experimentations/releases/tag/v413 (vanilla/bvS)
https://developer.android.com/topic/generic-system-image/releases (android 12 gsi, with a12_patch.zip flashed after)
vndk32
https://github.com/phhusson/treble_experimentations/releases/tag/v413 (vanilla/bvS)
https://developer.android.com/topic/generic-system-image/releases (android 12 gsi, with a12_patch.zip flashed after)
important: system as root builds, you'd want ab build GSIs
Known issues:some GSIs like official google GSIs lacks the /efs mount point, it has to be added manually or it will boot loop at samsung logo failing to mount /efs
some android 12 GSIs does not boot due to the lack of ebpf on the 3.18 kernel, android 12 GSIs needs to have patched bpfloader and netd, see below
https://github.com/8890q/patches
https://github.com/phhusson/platform_system_bpf/commit/c81966c23d79241458ebf874cfa8662f44705549
https://github.com/phhusson/platform_system_netd/commit/3a6efa1ff3717a613d1ba4a0eff5e751262d1074
You can attempt to copy bpfloader and netd binaries from phh GSIs
a12_patcher.zip attempts to fix the above issues by creating /system_root/efs and importing bpfloader+netd from phh android 12 v413
usb adb does not work on android 12 GSIs
a legacy implementation of usb adb is required for this kernel, see https://review.lineageos.org/c/LineageOS/android_packages_modules_adb/+/326385
fingerprint sensor does not work, the vendor blob segfaults when it can't access /data/biometrics due to vndk selinux compliance
neuralnetworks hal does not work, perhaps it can be fix by linking it with another c/c++ library, missing a symbol that should be included in libc++ but not vndk libc++
phhgsi_arm64_ab:/ $ ldd /vendor/bin/hw/[email protected]
linux-vdso.so.1 => [vdso] (0x7138c71000)
CANNOT LINK EXECUTABLE "linker64": cannot locate symbol "__cxa_demangle" referenced by "/vendor/bin/hw/[email protected]"...
lpm/power off charging does not quite work, /system/bin/lpm links libandroid.so (violates vndk) and looks for media assets in /system
charging powered off will likely send you to recovery/system
flash lpm_instasller.zip after installing gsi if power off charging is desired, it might or might not work depending on GSI (tested on phh 413)
$ readelf -d proprietary/bin/lpm | grep NEEDED
0x0000000000000001 (NEEDED) Shared library: [libcutils.so]
0x0000000000000001 (NEEDED) Shared library: [libbinder.so]
0x0000000000000001 (NEEDED) Shared library: [libutils.so]
0x0000000000000001 (NEEDED) Shared library: [libsuspend.so]
0x0000000000000001 (NEEDED) Shared library: [libhardware.so]
0x0000000000000001 (NEEDED) Shared library: [libandroid.so]
0x0000000000000001 (NEEDED) Shared library: [libmaet.so]
0x0000000000000001 (NEEDED) Shared library: [libsxqk_skia.so]
0x0000000000000001 (NEEDED) Shared library: [liblog.so]
0x0000000000000001 (NEEDED) Shared library: [libc++.so]
0x0000000000000001 (NEEDED) Shared library: [libc.so]
0x0000000000000001 (NEEDED) Shared library: [libm.so]
0x0000000000000001 (NEEDED) Shared library: [libdl.so]
InstallationThere are two requirements for testing this treble build:
A /vendor partition that is at least 250 MB
A recovery that is aware of the /vendor partition
You can fulfill these requirements by:
Install twrp normally
Flash heroxlte_CreateVendor_2.0.zip from https://forum.xda-developers.com/t/treble-aosp-g930x-g935x-project_pizza-trebleport-v2-0.3956076/ , it will create a ~400 MiB vendor partition and patch the current twrp you have
Or:
Modify the partition table manually and add a 250 MB partition named VENDOR, build/modify twrp manually to support the new partition
Once that's fulfilled, flash the zip in this release, herolte for flat and hero2lte for edge. The zips comes with an install of LineageOS 19.1/18.1. After Installing the zip you can write any system.img of your choice
After writing system.img, flash lpm_installer.zip if poweroff charging is needed. Note that that has been tested on phh v413 and google android 12 gsi
a12_patcher.zip replaces /system/bin/bpfloader and /system/bin/netd with phh versions, also creates /system_root/efs if required, allowing google android 12 gsi to boot
Building/SourcePlease refer to manifests_herolte_vendor_part/roomservice.xml and manifests_herolte_vendor_part_18.1/roomservice.xml on https://github.com/Kethen/lineage_build_scripts for your own builds
Download
Release 2022-05-26 · Kethen/lineage_build_scripts
18.1 herolte native build does not need patches
github.com
Click to expand...
Click to collapse
Excellent work.
katharinechui said:
https://gitlab.com/hackintosh5/TrebleInfo
Credits
https://github.com/8890q/ for LineageOS 19.1/18.1 device tree, kernel, hardware support, blobs
https://forum.xda-developers.com/t/treble-aosp-g930x-g935x-project_pizza-trebleport-v2-0.3956076/ for libsensor blobs
https://github.com/osm0sis/ for anykernel, used for the twrp patching zip
Special thankshttps://github.com/ExpressLuke for hero2lte testing
https://github.com/00p513-dev for suggesting using squashfs for vendor partition, making it possible to skip partition table modding
https://github.com/phhusson for looking into the double tap to wake issues with phh GSI
Notes:
I do not own a hero2lte(edge)
I'll mostly work on this only during weekends/holidays
and on that note the hero2lte build is not tested by myself
for vndk30 based vendor (LineageOS 18.1), use with android 11 and up GSIs
for vndk32 based vendor (LineageOS 19.1), use with android 12L and up GSIs
2022-06-12 the CACHE partition is now used as vendor, the HIDDEN patition is now used as cache, no more partition table mods required
Updates:
2022-06-13
android 12 data usage meter now works with a12_patcher.zip
2022-06-12
fixed neural network api hal
fixed fingerprint sensor
switched vendor image to squashfs, no CreateVendor required anymore with it's small size
new twrp patcher zip, should no longer cause "twrp is stuck after flashing CreateVendor"
bigger GSIs should fit better now with the original ~4.5GB SYSTEM partition; device native roms can be used without RevertVendor
2022-05-31
fixed wifi tethering
vndk32: rebased on 2022-05-26 12L build from ivan
phh_wifitethering_patcher.zip for wifi hotspot on phh GSIs
2022-05-26
added vndk32 based release
lpm_installer.zip for offline charging
fixed keystore errors on android 12 GSIs, lock screens work now
2022-02-15
rebased on February build from 8890q
January android updates
2021-12-16
install libaudioroute into /vendor/lib
December android updates
2021-12-10
move properties to /vendor
Tested GSIs
vndk30
https://github.com/phhusson/treble_experimentations/releases/tag/v313 (vanilla/bvS)
https://github.com/phhusson/treble_experimentations/releases/tag/v413 (vanilla/bvS)
https://developer.android.com/topic/generic-system-image/releases (android 12 gsi, with a12_patch.zip flashed after)
vndk32
https://github.com/phhusson/treble_experimentations/releases/tag/v413 (vanilla/bvS)
https://developer.android.com/topic/generic-system-image/releases (android 12 gsi, with a12_patch.zip flashed after)
important: system as root builds, you'd want ab build GSIs
Known issues:
some GSIs like official google GSIs lacks the /efs mount point, it has to be added manually or it will boot loop at samsung logo failing to mount /efs
some android 12 GSIs does not boot due to the lack of ebpf on the 3.18 kernel, android 12 GSIs needs to have patched bpfloader and netd, see below
https://github.com/8890q/patches
https://github.com/phhusson/platform_system_bpf/commit/c81966c23d79241458ebf874cfa8662f44705549
https://github.com/phhusson/platform_system_netd/commit/3a6efa1ff3717a613d1ba4a0eff5e751262d1074
data usage stays at 0 MB used on android 12 GSIs, because ebpf is used for metering
a12_patcher.zip attempts to fix the above issues by creating /system_root/efs and importing bpfloader+netd from https://github.com/8890q/patches
a11_patcher.zip creates /system_root/efs if required
usb adb does not work on android 12 GSIs
a legacy implementation of usb adb is required for this kernel, see https://review.lineageos.org/c/LineageOS/android_packages_modules_adb/+/326385
as a workaround, disable usb adb and use wifi adb
lpm/power off charging does not work
lpm related blobs sadly has to be installed on /system, flash lpm_instasller.zip after installing gsi if power off charging is desired, it might or might not work depending on GSI (tested on phh 413 and 313)
Wifi tethering does not work on phh GSIs
https://github.com/phhusson/vendor_hardware_overlay/tree/pie/Tethering conflicts with our Tethering overlay
flash phh_wifitethering_patcher.zip after installing phh GSIs
Alarm clock not working on aosp GSI
it should be fixed on phh 414 and up, it is not a vendor issue. If you are using an older aosp GSI, flash deskclock_powersaving.zip to fix that. See https://github.com/LineageOS/androi...mmit/8dd096c4cfb647960be1695a57246727878b8c8d
Installation
If you are using the old partition table mod zip heroxlte_CreateVendor_2.0.zip from older versions, first flash heroxlte_RevertVendor_2.0.zip, or revert your partition table other ways such as odin. Skip this step if you have never touched your partition table
Install the newest twrp from https://eu.dl.twrp.me/herolte/ (s7) or https://eu.dl.twrp.me/hero2lte/ (s7 edge)
Flash twrp_patcher.zip to enable system.img flashing, it'll reboot to recovery once it's done, tested on 3.6.2_9-0 but newer versions should work unless recovery.fstab changes
Flash Lineage 19.1 for android 12.1(api level 32) GSIs, flash Lineage 18.1 for android 11(api level 30) and 12(api level 31) GSIs, herolte for s7 and hero2lte for s7edge
Flash the system.img of your choice
If you are using a phh patched GSI, flash phh_wifitethering_patcher.zip
If you are using an android 12/12L GSI, flash a12_patcher.zip
If you are using an android 11 GSI, flash a11_patcher.zip
Flash lpm_installer.zip to enable poweroff charging
If you are using an aosp GSI that is not phh patched or older than phh 414, flash deskclock_powersaving.zip to fix alarm clock
If you are using phh GSI version <= 414, flash phh_dt2w_patcher.zip to fix double tap to wake
Undo twrp_patcher.zip and revert to device native romsThis is not required for using device native roms, however OTA updates might require this
Flash the newest twrp again
Wipe cache
Flash a device native rom
Buildinglineage_build_herolte_vendor_part, lineage_build_hero2lte_vendor_part, lineage_build_herolte_vendor_part_18.1 and lineage_build_hero2lte_vendor_part_18.1 builds lineageos along with treble vendor using https://github.com/lineageos4microg/docker-lineage-cicd
you'll need ~15GB of free ram, ~300GB free disk space and podman
# create directories
mkdir src
mkdir zips
mkdir logs
mkdir ccache
# builds lineage 19.1 along with vndk32 for herolte (s7 flat exynos)
bash lineage_build_herolte_vendor_part
Reporting issues besides the known ones:
You can report them over https://github.com/Kethen/herolte_treble/issues
Downloadshttps://github.com/Kethen/herolte_treble/releases
Click to expand...
Click to collapse
on my phone nfc is not working what the hell should i do now?
the files are so much different to other devices i don't can handle....
aljoscha81 said:
on my phone nfc is not working what the hell should i do now?
Click to expand...
Click to collapse
wdym not working? what the hell did you do? mine is working, at least in terms of reading smart cards
(like seriously, what did you do to end up with non-working nfc)
{
"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"
}
please send a logcat to https://github.com/Kethen/herolte_treble/issues
katharinechui said:
wdym not working? what the hell did you do? mine is working, at least in terms of reading smart cards
(like seriously, what did you do to end up with non-working nfc)
View attachment 5640219
please send a logcat to https://github.com/Kethen/herolte_treble/issues
Click to expand...
Click to collapse
ok i will get with matlog app if it help?
by the way it don't react while some machine is reading my blood.....
it is a freestyle libre sensor to monitoring diabetis .....
katharinechui said:
wdym not working? what the hell did you do? mine is working, at least in terms of reading smart cards
(like seriously, what did you do to end up with non-working nfc)
View attachment 5640219
please send a logcat to https://github.com/Kethen/herolte_treble/issues
Click to expand...
Click to collapse
sry here it is ....
forgot my git logging....
it is nfc enabled and running sensor scan modus with freestyle libre 3.3.1 app ...
the phone does not get any signal from device it is as doesn't have been real no error message ..... nothing....!
aljoscha81 said:
sry here it is ....
forgot my git logging....
Click to expand...
Click to collapse
sorry, the log is not helpful at all, all it shows is you have some kind of broken gapps installed and it kept crashing, and nfc scanned something
please capture log with `adb logcat`
what GSI are you using? can you check if nfc works with ivan's lineage 19.1?
like not existence....
katharinechui said:
sorry, the log is not helpful at all, all it shows is you have some kind of broken gapps installed
please capture log with `adb logcat`
what GSI are you using? can you check if nfc works with ivan's lineage 19.1?
Click to expand...
Click to collapse
ok ...
i'm on cr droid 8.5 nazim has post few min ago 8.6....
but adb must?....
broken gapps? it is inbuild... so .... oh nooooo
i got an other device is ran into same issue
can you send link to los 19.1 .....?
i ll give it a try
i will try adb log wait i must have a beer it is a long time for me like to have a12 gsi up and running ....... elstway?
aljoscha81 said:
ok ...
i'm on cr droid 8.5 nazim has post few min ago 8.6....
but adb must?....
broken gapps? it is inbuild... so .... oh nooooo
i got an other device is ran into same issue
can you send link to los 19.1 .....?
i ll give it a try
Click to expand...
Click to collapse
Ivan's LineageOS 19.1
LineageOS 19.1 (Android 12L) [Signature Spoofing][OTA updates] for S7 Exynos
LineageOS 19.1 for herolte /* * 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...
forum.xda-developers.com
also try other GSIs, test https://developer.android.com/topic/generic-system-image/releases#android-gsi-12 ARM64+GMS if you need gapps, remember to flash a12_patcher.zip, deskclock_powersaving.zip and lpm_installer.zip after flashing that particular gsi
katharinechui said:
Ivan's LineageOS 19.1
LineageOS 19.1 (Android 12L) [Signature Spoofing][OTA updates] for S7 Exynos
LineageOS 19.1 for herolte /* * 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...
forum.xda-developers.com
also try other GSIs, test https://developer.android.com/topic/generic-system-image/releases#android-gsi-12 ARM64+GMS if you need gapps, remember to flash a12_patcher.zip, deskclock_powersaving.zip and lpm_installer.zip after flashing that particular gsi
Click to expand...
Click to collapse
ok i see .. the los in the link you post is different to the one i installed i think i have installed before and got response to the nfc sensor but also only few times then no more nfc working also no android beam from other device....
aljoscha81 said:
ok i see .. the los in the link you post is different to the one i installed i think i have installed before and got response to the nfc sensor but also only few times then no more nfc working also no android beam from other device....
Click to expand...
Click to collapse
I had a look at the sensor app, it has 3 apps for 3 different sensors from abott, are you using the correct version?
The FreeStyle Libre 2 app is only compatible with FreeStyle Libre 2 Sensors. Learn more about compatibility at http://FreeStyleLibre.com
Click to expand...
Click to collapse
You can only use the FreeStyle Libre 3 app with FreeStyle Libre 3 Sensors. It is not compatible with FreeStyle Libre or FreeStyle Libre 2 Sensors.
Click to expand...
Click to collapse
katharinechui said:
I had a look at the sensor app, it has 3 apps for 3 different sensors from abott, are you using the correct version?
Click to expand...
Click to collapse
yes that is not harmfull for me
i use freestyle libre 3.......
that is forced to be not bypassing cause of decrypt of some company?
whiteanywaysomethingcryptingsomehow?...
you know?
?
aljoscha81 said:
?
Click to expand...
Click to collapse
if you have a FreeStyle Libre 3 sensor, you need a FreeStyle Libre 3 app
if you have a FreeStyle Libre 2 sensor, you need a FreeStyle Libre 2 app
if you have a FreeStyle Libre sensor, you need a FreeStyle Libre app
yes i do