{
"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 is a free, community built, aftermarket firmware distribution of Android 13 (T), 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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
GPL compliance:
Device tree source code: LineageOS/android_device_xiaomi_polaris
Kernel source code: LineageOS/android_kernel_xiaomi_sdm845
Working:
Camera (and flashlight)
WiFi
NFC
Bluetooth
Telephony (Calls and Data)
IMS (RCS, VoLTE and WiFi Calling)
Audio (Record and Playback)
Video Playback
Sensors
GPS
Encryption (FBE)
WiFi Display
Broken:
Nothing (?)
Compatibility:
Compatible with all Xiaomi Mi MIX 2S variants.Builds are based off the Xiaomi's Android 10 firmware with proprietary blobs from MIUI v12.0.3.0 global stable package.
Device wiki:
Official wiki link
Downloads:
Official download links
Installation:
Follow instructions found in the respective wiki page
Hi, is there a way how to modify the brightness curve without manually building the lineageOS? The minimum brightness is way too low. It is really annoying problem at least for me.
android_device_xiaomi_polaris/config.xml at lineage-20 · LineageOS/android_device_xiaomi_polaris
Contribute to LineageOS/android_device_xiaomi_polaris development by creating an account on GitHub.
github.com
Edit: Removed the build.prop info
howpathetic said:
Hi, is there a way how to modify the brightness curve without manually building the lineageOS? The minimum brightness is way too low. It is really annoying problem at least for me.
Click to expand...
Click to collapse
Write a simple overlay app and install it as a magisk module. The one I wrote and shared here should still work fine. It sets minimum brightness to about 30%. It just overlays brightness values in the res/values/config.xml file. (I have only tested it in LOS18.1 and LOS19.1 but the res/values/config.xml file hasn't changes so it should work fine)
MiniBlu said:
Write a simple overlay app and install it as a magisk module. The one I wrote and shared here should still work fine. It sets minimum brightness to about 30%. It just overlays brightness values in the res/values/config.xml file. (I have only tested it in LOS18.1 and LOS19.1 but the res/values/config.xml file hasn't changes so it should work fine)
Click to expand...
Click to collapse
Thanks for the advice but I am not rooted, and I am not using magisk. I modified the build.prop in the recovery where I remounted system as readwrite.
Its really low brightness, could be upped directly in the LineageOS/android_device_xiaomi_polaris repository.
howpathetic said:
Thanks for the advice but I am not rooted, and I am not using magisk. I modified the build.prop in the recovery where I remounted system as readwrite.
Its really low brightness, could be upped directly in the LineageOS/android_device_xiaomi_polaris repository.
Click to expand...
Click to collapse
Auto brightnesss works fine on some devices and not on others so I don't think it will get changed. If you don't use magisk you can use recovery to put the PolarisBrightFix.apk into \system\product\overlay\PolarisBrightFix\ folder. This worked in LOS18.1 probably will still work.
LOS 20: Any experience so far?..
MiniBlu said:
Auto brightnesss works fine on some devices and not on others so I don't think it will get changed. If you don't use magisk you can use recovery to put the PolarisBrightFix.apk into \system\product\overlay\PolarisBrightFix\ folder. This worked in LOS18.1 probably will still work.
Click to expand...
Click to collapse
It is in the android_device_xiaomi_polaris repository. So only polaris devices are built with this repository. Other devices wont be impacted.
I will try your method after @bgcngm response.
howpathetic said:
It is in the android_device_xiaomi_polaris repository. So only polaris devices are built with this repository. Other devices wont be impacted.
I will try your method after @bgcngm response.
Click to expand...
Click to collapse
I believe that some of you already know that I no longer have this device. If you find that there is a better brightness config, let me know and I will commit it to the repository.
howpathetic said:
It is in the android_device_xiaomi_polaris repository. So only polaris devices are built with this repository. Other devices wont be impacted.
I will try your method after @bgcngm response.
Click to expand...
Click to collapse
When I say on some devices I mean some Mi Mix2s. In my case, It was terrible but after I replaced the screen and gave all the sensors a good clean the Auto Brightness levels improved a lot, its still not great, but acceptable. If I get time I will try to test for an optimal profile as the values in my overlay are just a hack to increase minimum values to about 30%. Once done, we can get a few people to test it as an overlay and if it seems better over a few devices we can pass the new config to @bgcngm .
MiniBlu said:
Write a simple overlay app and install it as a magisk module. The one I wrote and shared here should still work fine. It sets minimum brightness to about 30%. It just overlays brightness values in the res/values/config.xml file. (I have only tested it in LOS18.1 and LOS19.1 but the res/values/config.xml file hasn't changes so it should work fine)
Click to expand...
Click to collapse
Hmm, it does not work. The system is not booting. I will make own overlay once I found out how. It's a long time when I worked with android ROMs. Things changed I do not know how to create overlay, do you know about some guide ?
MiniBlu said:
When I say on some devices I mean some Mi Mix2s. In my case, It was terrible but after I replaced the screen and gave all the sensors a good clean the Auto Brightness levels improved a lot, its still not great, but acceptable. If I get time I will try to test for an optimal profile as the values in my overlay are just a hack to increase minimum values to about 30%. Once done, we can get a few people to test it as an overlay and if it seems better over a few devices we can pass the new config to @bgcngm .
Click to expand...
Click to collapse
The pixel experience does not have this problem, maybe take values from there ?
https://github.com/PixelExperience-...rameworks/base/core/res/res/values/config.xml
howpathetic said:
Hmm, it does not work. The system is not booting. I will make own overlay once I found out how. It's a long time when I worked with android ROMs. Things changed I do not know how to create overlay, do you know about some guide ?
Click to expand...
Click to collapse
Probably due to modifying the system with out magisk. Last time I tested it that way I think I replaced an existing overlay as described here . That post also has a good guide for compiling the overlay app. I have attached the overlay app source for your reference.
MiniBlu said:
Probably due to modifying the system with out magisk. Last time I tested it that way I think I replaced an existing overlay as described here . That post also has a good guide for compiling the overlay app. I have attached the overlay app source for your reference.
Click to expand...
Click to collapse
I make the package. The system booted, but once I changed some property like
config_maximumScreenDimRatio to 0 the os did not boot up. I am missing something but I do not know how to debug this. I tried to adjust the array values for config_autoBrightnessLevels. The system booted but I did not have any affect. When I changed array values in config_screenBrightnessBacklight the system again did not boot up.
Attaching not working apk if you want to check.
happyass**** said:
LOS 20: Any experience so far?..
Click to expand...
Click to collapse
Yup, working as expected including the flaky auto brightness. Upgraded from 19.1 to 20, the Mi MIX 2S is my daily driver. No issues encountered yet, even the PayPal app works again. Happy user here!
Yes, it's working pretty well except the already mentioned auto brightness. And since the latest OTA update the screen sometimes takes very long to wake up (stayed black 2 times).
But overall amazing work, so thanks everyone involved!
It's working really well for me. Didn't notice any issues.
@bgcngm
First, thank you for your ongoing support of the MiMix2s, very much appreciated.
Everything works very well, the only flaw of the current LOS20 (and since 17.1) is the too dim brightness in low light condition. I happen to have a spare MiMix2s with me and would be glad to help eliminating this bug. I'm no programmer, but could flash provided test-builds and test.
Currently it has PE13+ flashed and especially the initial brightness after turning on the screen in low light is way better, so settings could be adopted from PE13.
Regards username-xda
MiniBlu said:
Probably due to modifying the system with out magisk. Last time I tested it that way I think I replaced an existing overlay as described here . That post also has a good guide for compiling the overlay app. I have attached the overlay app source for your reference.
Click to expand...
Click to collapse
Did anyone get this to work? I get bootloops both when I install the zip as a magisk module (I have magisk 25.2 installed and working fine) and when I extract the apk and put it into a new /system/product/overlay/PolarisBrightFix/ folder.
Martin995 said:
Did anyone get this to work? I get bootloops both when I install the zip as a magisk module (I have magisk 25.2 installed and working fine) and when I extract the apk and put it into a new /system/product/overlay/PolarisBrightFix/ folder.
Click to expand...
Click to collapse
Hello,
this does not work, neither magisk module nor copy file manually in recovery, sends MiMix2s in bootloop.
Regards username-xda
howpathetic said:
The pixel experience does not have this problem, maybe take values from there ?
https://github.com/PixelExperience-...rameworks/base/core/res/res/values/config.xml
Click to expand...
Click to collapse
I would love to give the LOS20 a try, but I had bad brightness experience with 18 (or 19?) already, so I am stuck with an old 17.1 so far - and if the problem remains with this LOS20.0 build, there is no point in testing really.
Is there anything speaking AGAINST taking the values from PE as howpathetic suggested?
Related
{
"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 is a free, community built, aftermarket firmware distribution of Android 11, 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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.Instructions:
Reboot to TWRP
Wipe data, system (/system_root) and cache
Flash the ROM and the GApps
Reboot and enjoy!
Downloads:
Builds: https://github.com/mt8695/android_device_amazon_sheldon/releases
GApps: Open Gapps (arm/11/tvmini)
Reporting Bugs:
DO NOT Report bugs if you're running a custom kernel, you installed Xposed or you installed Magisk
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Known issues:
Dolby Digital Plus™ E-AC-3
Netflix
Notes:
SELinux is in Permissive mode
The ROM supports both sheldon (Fire TV Stick Lite) and sheldonp (Fire TV Stick 3rd gen)
Do not ask for ETAs
How do i...
Unlock and install TWRP?
Follow the instructions of the unlock thread
Go back to the original/stock ROM?
Download the stock update.bin (sheldon | sheldonp) and flash it using TWRP
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Contributors
R0rt1z2, k4y0z, t0x1cSH, diegocr
Source Code: https://github.com/mt8695
Kernel source: https://github.com/mt8695/android_kernel_amazon_mt8695
Screenshots
Reserved
Great Work!
Hello, many thanks for this rom, it's awesome, I thought I'd never get rid of that Amazon garbage
In case anybody else gets stuck in the remote pairing, just press the home button for 10+ seconds.
Edit
Anybody knows how to adjust display size?
bloot said:
Hello, many thanks for this rom, it's awesome, I thought I'd never get rid of that Amazon garbage
In case anybody else gets stuck in the remote pairing, just press the home button for 10+ seconds.
Edit
Anybody knows how to adjust display size?
Click to expand...
Click to collapse
I'm not sure with what do you mean by adjust display size but you can try to change it through ADB with adb shell wm size 1080x1920 (you can change the 1080x1920 part).
Rortiz2 said:
I'm not sure with what do you mean by adjust display size but you can try to change it through ADB with adb shell wm size 1080x1920 (you can change the 1080x1920 part).
Click to expand...
Click to collapse
Hello, I mean changing the size of the displayed area, not the resolution itself, in my TV the stock display size is too large and I'm missing part of the content
bloot said:
Hello, I mean changing the size of the displayed area, not the resolution itself, in my TV the stock display size is too large and I'm missing part of the content
Click to expand...
Click to collapse
I see, I think there's an option somewhere in the Settings (I can't check right now, sorry), it was called OverScan if I'm not mistaken. If it's not there, I'll include it in the next build.
Rortiz2 said:
I see, I think there's an option somewhere in the Settings (I can't check right now, sorry), it was called OverScan if I'm not mistaken. If it's not there, I'll include it in the next build.
Click to expand...
Click to collapse
I've been looking all over the settings but found nothing to adjust it, maybe I missed it though.
bloot said:
I've been looking all over the settings but found nothing to adjust it, maybe I missed it though.
Click to expand...
Click to collapse
Disabling overscan is typically a setting that can be configured on your TV.
Usually it's where you can also set aspect ratio for video sources, sometimes it's called "Just Scan"
k4y0z said:
Disabling overscan is typically a setting that can be configured on your TV.
Usually it's where you can also set aspect ratio for video sources, sometimes it's called "Just Scan"
Click to expand...
Click to collapse
How dumb I feel, I never found an overscan setting on my TV, it turns out the 16:9 aspect ratio does indeed an overscan, just changed to "screen fit" and it did it. Thanks.
It work like a charm , thank you for your hard work @Rortiz2
Everything work for me except Netflix ,could you upload your functional apk please ? since it's not on the Playstore and I get signature mismatch when I try to install the original amazon one (netflix.ninja) , I can connect with the Aptoide one but no video playback.
AMAZING! Smooth operation, nice and clean layout with the launcher present giving the Android TV theme with working playstore and modest settings menu. This rom has totally transfomred this device. Good work
Cheers again Roger + co
Regards
Out of interest is this a full 64-bit os instead of Amazon's 32-bit on top of a 64 bit processor?
Tech0308 said:
Out of interest is this a full 64-bit os instead of Amazon's 32-bit on top of a 64 bit processor?
Click to expand...
Click to collapse
This is a 32-bit OS
yacinecino said:
It work like a charm , thank you for your hard work @Rortiz2
Everything work for me except Netflix ,could you upload your functional apk please ? since it's not on the Playstore and I get signature mismatch when I try to install the original amazon one (netflix.ninja) , I can connect with the Aptoide one but no video playback.
Click to expand...
Click to collapse
I'll try to extract the APK later
Hi, I was wondering whether there is also a rom in the works for mantis, the fire tv stick 4k. If there is, I'd be happy to help test it on my own firestick.
If there isn't, could I do anything to make the sheldon one work on mantis (I know the general answer is absolutely no, so not holding my breath here)?
famus484 said:
Hi, I was wondering whether there is also a rom in the works for mantis, the fire tv stick 4k. If there is, I'd be happy to help test it on my own firestick.
If there isn't, could I do anything to make the sheldon one work on mantis (I know the general answer is absolutely no, so not holding my breath here)?
Click to expand...
Click to collapse
Unfortunately there is no way this ROM will work for mantis as sheldon's firmware is completely different. We actually tried to boot the sheldon firmware on mantis, but the kernel didn't boot at all (it failed to initialize some stuff). A friend of mine is willing to do 14.1 for mantis, we'll see if he pulls it off.
Rortiz2 said:
Unfortunately there is no way this ROM will work for mantis as sheldon's firmware is completely different. We actually tried to boot the sheldon firmware on mantis, but the kernel didn't boot at all (it failed to initialize some stuff). A friend of mine is willing to do 14.1 for mantis, we'll see if he pulls it off.
Click to expand...
Click to collapse
Thank you for the answer! That would be quite nice if your friend succeed. Had part of the work for 14.1 on mantis already been done, making it more viable than 18.1? And do you know if there are ''fundamental'' feature differences between both (a non-objective term obviously).
Hello, how can you come back to FireOS if wanted/needed? Cheers!
{
"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 is a free, community built, aftermarket firmware distribution of Android 11, 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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
Install LineageOS on pdx203 | LineageOS Wiki
wiki.lineageos.org
Downloads:
https://download.lineageos.org/pdx203
Known Issues:You tell me
Device Trees:Device Tree: https://github.com/LineageOS/android_device_sony_pdx203
Common Tree: https://github.com/LineageOS/android_device_sony_sm8250-common
Kernel Source: https://github.com/LineageOS/android_kernel_sony_sm8250
Credits:Huge thanks to:
Luk1337 and Sjllls for their help on debugging and fixing issues and device trees as references
Changelog:
Code:
- 2022-10-13
- So many things, see commits for details :)
- 2022-08-08
- Added High Brightness Mode (HBM) in livedisplay
- Added High Touch Reporting Rate (120Hz) switch
- 2022-08-02
- Fixed color settings in the Settings application (Thanks to cramfs28)
- Note that toggling "Creator Mode" in extra settings application will change the color setting
- Fixed an issue related to call microphone on T-Mobile sim cards
- Fixed echo cancellation in loudspeaker mode when in call
- 2022-07-27
- EXPERIMENTAL BUILD: May contain some extra functionalities that does not appear in final build
- Added extra setting application
- Added H.S. mode from Sony stock
- Added creator display mode
- Change default network type to 5G
- 2022-07-21
- **IMPORTANT:** You will need to flash the recovery.img BEFORE you flash the ROM
- Some ROM props changed, need to update the recovery
- Added double tap to wake
- Enabled picture enhancement feature in livedisplay
- Fixed dual-SIM detection
- Enabled touchscreen in recovery
- Check other updates in commit logs
- 2022-07-18
- Kernel
- Imported kernel source code from sony 58.2.A.7.55
- Merge CAF Tag LA.UM.9.12.r1-14300-SMxx50.0
- Enabled wireguard driver (Need testing)
- Initial merging of linux-stable (to 4.19.158)
- Update files for 58.2.A.8.92
- Check other updates in commit logs
- 2022-06-29
- Fixed microphone too low problem in some applications
- Fixed an issue causing the usb selection menu to grey out
Nice work! Thank you!
Should I "fastboot set_active a" before"fastboot flash boot boot.img"?
19920129 said:
Nice work! Thank you!
Should I "fastboot set_active a" before"fastboot flash boot boot.img"?
Click to expand...
Click to collapse
You can set the slot if you want, but honestly I don't think it is necessary.
clfbbn said:
You can set the slot if you want, but honestly I don't think it is necessary.
Click to expand...
Click to collapse
Hi，I just see two 20220609 roms，which one can I flash，any bugs？
19920129 said:
Hi，I just see two 20220609 roms，which one can I flash，any bugs？
Click to expand...
Click to collapse
There is a file with a suffix "_new", try that one. Flash it using lineage recovery.
Bug: Call Volume Change - Does not work for now
I think I have fixed other bugs.
Well I have found a significant bug that's going to prevent daily use. In-call microphone doesn't work at all, even on speakerphone. Using the recorder app, I can pick up audio but it is very very quiet. Everything else seems to work well so far, though, besides the in-call audio fixed max volume.
I am on the XQ-AT51, and have flashed MindTheGapps provided by LineageOS
citysurrounded said:
Well I have found a significant bug that's going to prevent daily use. In-call microphone doesn't work at all, even on speakerphone. Using the recorder app, I can pick up audio but it is very very quiet. Everything else seems to work well so far, though, besides the in-call audio fixed max volume.
I am on the XQ-AT51, and have flashed MindTheGapps provided by LineageOS
Click to expand...
Click to collapse
Are you using the latest build? I think I have fixed issues regarding the call volume.
The microphone in the recorder app is quite, I can confirm it, though.
I used 20220922 rom，but I can't use usb for transfer，only can charge。。。。
19920129 said:
I used 20220922 rom，but I can't use usb for transfer，only can charge。。。。
Click to expand...
Click to collapse
This is a known issue. Will be fixed along with the microphone problem.
You can try adb push as a workaround for now
Just installed LOS 19.1 on my Xperia XZ1 Compact, and really miss the WireGuard kernel feature on my Xperia 1 II, where I can have multiple tunnels active at the same time. Do you have any plans to add the WireGuard kernel module in a future release?
Anyways, great release! I have not personally encountered any bugs/issues yet. I use microG Installer Revived (with whew-inc's FakeGApps fork and, LSPosed Framework), Universal SafetyNet Fix, and MagiskHide Props Config with the bundled Xperia 5 II build fingerprint to fully pass a SafetyNet Attestation Check.
nixigaj said:
Just installed LOS 19.1 on my Xperia XZ1 Compact, and really miss the WireGuard kernel feature on my Xperia 1 II, where I can have multiple tunnels active at the same time. Do you have any plans to add the WireGuard kernel module in a future release?
Anyways, great release! I have not personally encountered any bugs/issues yet. I use microG Installer Revived (with whew-inc's FakeGApps fork and, LSPosed Framework), Universal SafetyNet Fix, and MagiskHide Props Config with the bundled Xperia 5 II build fingerprint to fully pass a SafetyNet Attestation Check.
Click to expand...
Click to collapse
Thanks for the report. Since I haven't used wireguard before, can you detail the information that can show whether this module is present in kernel or not?
clfbbn said:
Thanks for the report. Since I haven't used wireguard before, can you detail the information that can show whether this module is present in kernel or not?
Click to expand...
Click to collapse
When you enter settings in the WireGuard app, it will ask for root access to enable more features via the kernel module. Also if you run ls /sys/module/ | grep wireguard in a root terminal it will return wireguard.
I am not very well versed with Android kernel development but it seems as though the latest android-4.19-stable merge into the sony_sm8250 kernel tree happened before Google merged WireGuard into the android-4.19-stable kernel tree, and the sony_sm8250 kernel tree does not seem to have been updated since; thus /drivers/net/wireguard/ is missing, and gki_defconfig does not contain CONFIG_WIREGUARD=y.
nixigaj said:
When you enter settings in the WireGuard app, it will ask for root access to enable more features via the kernel module. Also if you run ls /sys/module/ | grep wireguard in a root terminal it will return wireguard.
I am not very well versed with Android kernel development but it seems as though the latest android-4.19-stable merge into the sony_sm8250 kernel tree happened before Google merged WireGuard into the android-4.19-stable kernel tree, and the sony_sm8250 kernel tree does not seem to have been updated since; thus /drivers/net/wireguard/ is missing, and gki_defconfig does not contain CONFIG_WIREGUARD=y.
Click to expand...
Click to collapse
The driver is there, see https://github.com/hellobbn/android_kernel_sony_sm8250/tree/lineage-19.1_new/drivers/net/wireguard
I have enabled the wireguard in my latest build, and you can try that out.
That said, not all upstream changes have been backported.
clfbbn said:
The driver is there, see https://github.com/hellobbn/android_kernel_sony_sm8250/tree/lineage-19.1_new/drivers/net/wireguard
I have enabled the wireguard in my latest build, and you can try that out.
That said, not all upstream changes have been backported.
Click to expand...
Click to collapse
Ignorant me did not think about there being multiple branches.
With the latest build the WireGuard app asks for root and all the features of the kernel module backend seem to work.
Dear dev, I have flashed lineage-os-19.1-2022-0718, but dual sim not work
RealNoobKanger said:
Dear dev, I have flashed lineage-os-19.1-2022-0718, but dual sim not work
Click to expand...
Click to collapse
Thanks, I can confirm this problem. Will look into it.
EDIT: Could be expected behavior if you first boot the rom with single SIM and then insert the other card.
Temp Solution (After each boot):
1. Enable Root Debugging in Developer Options
2. Enter adb shell:
Code:
adb root
adb shell
3. Type the following command:
Code:
/odm/bin/sony_ext_uim_ctrl
EDIT2: The next release will fix this problem.
clfbbn said:
Thanks, I can confirm this problem. Will look into it.
EDIT: Could be expected behavior if you first boot the rom with single SIM and then insert the other card.
Temp Solution (After each boot):
1. Enable Root Debugging in Developer Options
2. Enter adb shell:
Code:
adb root
adb shell
3. Type the following command:
Code:
/odm/bin/sony_ext_uim_ctrl
Click to expand...
Click to collapse
thanks for your reply bro, should we set 1 to the /sys/class/devices/sony_ext_uim_ctrl/sony_ext_uim_ctrl_type ?
I tested it on your latest lineage os 19.1 build, dual sim works well now. thank you !
RealNoobKanger said:
thanks for your reply bro, did you means write 1 to the /sys/class/devices/sony_ext_uim_ctrl/sony_ext_uim_ctrl_type ?
I tested it on your latest build, dual sim works well now, should we add to the init to set " /sys/class/devices/sony_ext_uim_ctrl/sony_ext_uim_ctrl_type" when device use dual sim (aka. dsds)
Click to expand...
Click to collapse
I set the "/sys/class/devices/sony_ext_uim_ctrl/sony_ext_uim_ctrl_type" to 1 on my device with your lineage os build, ril works well not only dual sim but single sim (ss). should we set this value to "1" defaultly ?
No matter what, thank you from the bottom of my heart for your good rom, device tree and kernel source !
RealNoobKanger said:
I set the "/sys/class/devices/sony_ext_uim_ctrl/sony_ext_uim_ctrl_type" to 1 on my device with your lineage os build, ril works well not only dual sim but single sim (ss). should we set this value to "1" defaultly ?
No matter what, thank you from the bottom of my heart for your good rom, device tree and kernel source !
Click to expand...
Click to collapse
Maybe this is related to SD card / SIM card detection, so I am not sure whether SD card will work properly if we set this always to be 1.
The exec file "/odm/bin/sony_ext_uim_ctrl" should take care of this. I forgot to label this exec file so it does not get executed when system boots, which causes the second sim not being detected. I have corrected that mistake now. If you are interested: https://github.com/hellobbn/android...mmit/68b69ac284cf3e4abe5464a2a70f37701581060f
Hi Y700 owners, of future owners
So to have a dedicated forum for the Y700, we need to open threads in other "remotely related forums" and have some interesting discussions.
Therefore opening this one as an attempt to get a little more organized Y700 posts and, especially, to get visibility and get our own forum
I'm not too much familar in 2022 with ROMs and other stuff (i was playing with those things a few years back and a lot has changed since), but i understand there are some GSI (generic system image) ROMs that are available, from what i understand, for several devices that don't have a dedicated ROM. That is something new to me i have to say.
@FIERA03 , i hope you don't mind me quoting you here, but as you have done some interesting testing, to give it more visibility, i'll paste your results here from another thread.
I have flashed a lot of GSI on this tablet so far.
Here is a summary of the bugs and other issues that I have noticed in them.
※All of them are Android 12L except for the ones without special notes.
①Corvus OS, Descendant OS...Lock screen does not rotate. Probably because it is based on Google Pixel ROM. Corvus also does not have face unlock.
②Ancient OS(Android 12.0)...Lock screen does not turn to landscape. Also, when I change the username or photo at the top of the settings, the settings app crashes. Also note that the settings app crashes if you change the username or photo above the settings.
③Proton AOSP...When I restarted to set up Magisk, the settings app repeatedly stops. Deleting app data and cache had no effect.
④Havoc OS(Android 11)...The startup logo does not appear in the first place and comes back to the bootloader.
⑤Superior OS...It started, but the FPS dropped extremely. I judged that it is difficult to use regularly.
⑥Pixel Experience…The screen is still not landscape. Also, it seems that it is not optimized for tablets any more than Descendant, and when I call the dock while launching an app(the feature of 12L), the icon looks like it has been split in half.
⑦All of NipponGSI...Like Havoc OS, it comes back to the bootloader. It may be a bad compatibility.
⑧Lineage OS…There was a switch "Rotate lock screen" in the settings. But I don't use it, because the "su" binary is still in the root file and can't delete it ,so interferes with SafetyNet.
⑨Arrow OS...This also allows the lock screen to be turned landscape and is also very light. Although the lack of face unlock is a demerit (LSPosed module didn't work→https://forum.xda-developers.com/t/11-universalauth-face-unlock-for-all-roms.4419343/).But there are few complaints for me. So I'm using it regularly.
I'm sorry if it's hard to read because I'm not good at English. Thank you.
Click to expand...
Click to collapse
Thanks a lot @FIERA03 for these information. Very valuable for anyone interested in flashing its Y700.
This was your status on May 22nd.
Of course you need to unlock the bootloader, which you can do after entering IMEI and email at this website: https://www.zui.com/iunlock (Thanks for @NisseGurra for posting this link in another thread).
Are there any other interesting experience that anyone can share with either those GSI or other images?
Thanks a lot for your contributions to have some kind of Lenovo Legion Y700 community started
For the GSI Y700 users, there is an treble app update from phh (attached). It enable magnetic cases wake and close screen.
I'm pleased to report that I have tested a ROM that I had not tried before and have confirmed that it meets all of my requirements.
The Nazim's crDroid GSI is the best ROM for the Legion Y700 (I didn't like the logo, so I didn't use it until now).
Below is a list of the outstanding features of this ROM.
・It doesn't have a fixed lock screen in portrait orientation like Corvus or Descendant.
・It doesn't contain superfluous and undeletable files like "su" like Lineage.
・It includes face unlock unlike ArrowOS (by the way, crDroid and ArrowOS are built by the same person, I wonder why he didn't include face unlock in the latter).
・It doesn't cause any noticeable glitches like ProtonAOSP or Pixel Experience (it still runs the Alpha version of the Lawnchair Magisk Module without crashing).
・This ROM is so customizable that you don't even need the Magisk or LSPosed module that you have been using. The status bar can be customized, and even the volume step can be adjusted.
・The default wallpaper of this ROM is very beautiful (my personal opinion ).
・It can pass SafetyNet. most other 12L GSIs could not do this.
Of course, this ROM alone is still not enough in some areas, but I think that can be improved with the App placed by Mr. @NisseGurra and the modules in this link
(Click the "Magiskモジュールのダウンロード" button to jump to Google Drive and download it). This module enables automatic brightness change of the screen, and also allows assignment to the right switch (originally the game mode activation switch) using the Button Mapper.
I hope all Y700 users will use this ROM. Thank you.
Thanks for the report Fiera03.
How about streaming services with GSI ROMs? Netflix and other are working fine in HD?
I don't know because I'm not registered with Netflix, but according to Mr. SMART ASW (who I showed in the module link), you can get HD playback if you forge the model name using MagiskHide Props Config (he forged a Yoga Tab to a Pixel 6). However, he says that doing this may cause DT2W to stop functioning. So be careful.
I get 1080 at amazon prime, can seem to get 4 k tho
NisseGurra said:
I get 1080 at amazon prime, can seem to get 4 k tho
Click to expand...
Click to collapse
Well, my Galaxy tab s6 has the same resolution and doesn't get 4k, which makes sense since these devices aren't 4K (1440p is a good fit in YouTube but it's not an option in prime video if I'm not mistaken)
@FIERA03 can you provide an instruction "how to install crDroid to Y700"?
vanaduym23 said:
@FIERA03 can you provide an instruction "how to install crDroid to Y700"?
Click to expand...
Click to collapse
OK. here's a installing process.
①Unlock bootloader with SN.img. This procedure is the same as for other Lenovo tablets such as the Xiaoxin Pad, so I'll skip this step.
②Put the tablet in Fastboote"d" mode. I usually enter this mode by pressing and holding the volume down and the power button to activate fastboot mode, then selecting "Enter Fastboot" from the recovery menu.
③You have to download the arm64 version from the CrDroid GSI link that the text my first post in this thread. I recommend arm64-BgN-vndklite.
④I will assume that you have already configured Android Studio. Start a command prompt and type the command fastboot flash system (the img file you downloaded and unzipped) You can also do this by dragging and dropping the img file into the window before flashing system.
⑤Operate the tablet; proceed to Enter recovery→Wipe data/factory reset to initialize the tablet's data. Otherwise, it will freeze at the title.
⑥Reboot system now and after a while CrDroid will start.
If you have any stumbling blocks, please ask me again.
By the way, is anyone using Phusson's AOSP with Y700?
I want to know if it has been improved, because I had a bug before and the screen didn't come on after sleep.
FIERA03 said:
I'm pleased to report that I have tested a ROM that I had not tried before and have confirmed that it meets all of my requirements.
The Nazim's crDroid GSI is the best ROM for the Legion Y700 (I didn't like the logo, so I didn't use it until now).
Below is a list of the outstanding features of this ROM.
・It doesn't have a fixed lock screen in portrait orientation like Corvus or Descendant.
・It doesn't contain superfluous and undeletable files like "su" like Lineage.
・It includes face unlock unlike ArrowOS (by the way, crDroid and ArrowOS are built by the same person, I wonder why he didn't include face unlock in the latter).
・It doesn't cause any noticeable glitches like ProtonAOSP or Pixel Experience (it still runs the Alpha version of the Lawnchair Magisk Module without crashing).
・This ROM is so customizable that you don't even need the Magisk or LSPosed module that you have been using. The status bar can be customized, and even the volume step can be adjusted.
・The default wallpaper of this ROM is very beautiful (my personal opinion ).
・It can pass SafetyNet. most other 12L GSIs could not do this.
Of course, this ROM alone is still not enough in some areas, but I think that can be improved with the App placed by Mr. @NisseGurra and the modules in this link
(Click the "Magiskモジュールのダウンロード" button to jump to Google Drive and download it). This module enables automatic brightness change of the screen, and also allows assignment to the right switch (originally the game mode activation switch) using the Button Mapper.
I hope all Y700 users will use this ROM. Thank you.
Click to expand...
Click to collapse
Its been a few months since you made this post, thank you!
I was wondering if you have any updates on this. Is this still your recommended Rom?
If not, which one are you running now?
I noticed the developer of crdroid has a lot bunch of newer builds available, have you tried those?
Thanks for your input keeping this device alive
stokedcrf said:
Its been a few months since you made this post, thank you!
I was wondering if you have any updates on this. Is this still your recommended Rom?
If not, which one are you running now?
I noticed the developer of crdroid has a lot bunch of newer builds available, have you tried those?
Thanks for your input keeping this device alive
Click to expand...
Click to collapse
I've also tested several Android 13 ROMs, and none of them seem to be optimized for tablets yet (at 1st I found a severe bug in the standard launcher).
Therefore, I still consider crDroid GSI's 8.13 to be the most suitable ROM for this device. The next best is Mr. AndyYan's LineageOS (Secure), which is easy to use.
@FIERA03 could I ask where you found your IMEI on this device? I got the stock rom switched over to english but I cannot find the IMEI anywhere :/
stokedcrf said:
@FIERA03 could I ask where you found your IMEI on this device? I got the stock rom switched over to english but I cannot find the IMEI anywhere :/
Click to expand...
Click to collapse
Is there a sticker writing device's information on the tablet ?
The number under the barcode is the S/N=IMEI.
Anyone else notice the unlocking website no longer accepts the serial number?
{
"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"
}
FIERA03 said:
OK. here's a installing process.
①Unlock bootloader with SN.img. This procedure is the same as for other Lenovo tablets such as the Xiaoxin Pad, so I'll skip this step.
②Put the tablet in Fastboote"d" mode. I usually enter this mode by pressing and holding the volume down and the power button to activate fastboot mode, then selecting "Enter Fastboot" from the recovery menu.
③You have to download the arm64 version from the CrDroid GSI link that the text my first post in this thread. I recommend arm64-BgN-vndklite.
④I will assume that you have already configured Android Studio. Start a command prompt and type the command fastboot flash system (the img file you downloaded and unzipped) You can also do this by dragging and dropping the img file into the window before flashing system.
⑤Operate the tablet; proceed to Enter recovery→Wipe data/factory reset to initialize the tablet's data. Otherwise, it will freeze at the title.
⑥Reboot system now and after a while CrDroid will start.
If you have any stumbling blocks, please ask me again.
Click to expand...
Click to collapse
Hi, I am a noob who's trying to try update the rom as per your instruction. However my y700 is came with 'global rom' which is installed by Aliexpress seller. It seems the machine already unlocked. Is it ok/safe to follow your instruction guide even it's not ZUI original chinese rom? I would much appreciated. Currently Having trouble to having google playstore error on games, and experiencing strangely lagging speed on loading microSD card.
stokedcrf said:
Anyone else notice the unlocking website no longer accepts the serial number?
View attachment 5768701
Click to expand...
Click to collapse
I have encountered this too when I was thinking to unlock my y700
hi, i success install rom following your guide, can you help me to root the device
FIERA03 said:
I'm pleased to report that I have tested a ROM that I had not tried before and have confirmed that it meets all of my requirements.
The Nazim's crDroid GSI is the best ROM for the Legion Y700 (I didn't like the logo, so I didn't use it until now).
Below is a list of the outstanding features of this ROM.
・It doesn't have a fixed lock screen in portrait orientation like Corvus or Descendant.
・It doesn't contain superfluous and undeletable files like "su" like Lineage.
・It includes face unlock unlike ArrowOS (by the way, crDroid and ArrowOS are built by the same person, I wonder why he didn't include face unlock in the latter).
・It doesn't cause any noticeable glitches like ProtonAOSP or Pixel Experience (it still runs the Alpha version of the Lawnchair Magisk Module without crashing).
・This ROM is so customizable that you don't even need the Magisk or LSPosed module that you have been using. The status bar can be customized, and even the volume step can be adjusted.
・The default wallpaper of this ROM is very beautiful (my personal opinion ).
・It can pass SafetyNet. most other 12L GSIs could not do this.
Of course, this ROM alone is still not enough in some areas, but I think that can be improved with the App placed by Mr. @NisseGurra and the modules in this link
(Click the "Magiskモジュールのダウンロード" button to jump to Google Drive and download it). This module enables automatic brightness change of the screen, and also allows assignment to the right switch (originally the game mode activation switch) using the Button Mapper.
I hope all Y700 users will use this ROM. Thank you.
Click to expand...
Click to collapse
aisidetpipo said:
hi, i success install rom following your guide, can you help me to root the device
Click to expand...
Click to collapse
This guide (use google translate for english) should work: https://smartasw.com/archives/15704
Hi everybody.
I've also bought now the Y700 (to replace my old MiPad 4) and installed as recommended the crDroid image from Nazim. Really like it a lot, only miss adaptive brightness.
I've therefore tried to install the Magisk module from smartasw (guide is here).
Does is work for you @FIERA03 or anybody else?
The re-mapping for the game button has been successful, but I cannot see any automatic changes in the brightness nor any additional settings entry (not sure if such a thing should be expected).
It seems that the overlay apk cannot be installed correctly. Tried to debug using this and it has a problem with the idmap:
Code:
TB-9707F:/ $ cmd overlay dump me.phh.treble.overlay.lenovo.y700
me.phh.treble.overlay.lenovo.y700:0 {
mPackageName...........: me.phh.treble.overlay.lenovo.y700
mOverlayName...........: null
mUserId................: 0
mTargetPackageName.....: android
mTargetOverlayableName.: null
mBaseCodePath..........: /system/product/overlay/treble-overlay-lenovo-y700.apk
mState.................: STATE_NO_IDMAP
mIsEnabled.............: true
mIsMutable.............: false
mPriority..............: 15
mCategory..............: null
mIsFabricated..........: false
}
IDMAP OF me.phh.treble.overlay.lenovo.y700
<missing idmap>
Does it work for any of you guys?
Hi All,
This is a revival of the original MagiskHide Props Config module.
I've been working on this all day and its finally ready to start taking fingerprint submissions so i thought id open a new thread here to reach more people.
Disclaimers -
I have copied and pasted from the original thread with a few changes where relevant.
I fully intend on handing this back over to @Didgeridoohan if they ever decide to take the reign again. Im simply just stepping in to fill a much needed void in the custom rom space.
As with any Magisk Module. This comes with risk. You can very easily break your device. I myself have a Samsung Note 10 Plus so i will be testing on my own device prior to making any releases.
I have no intention of collecting donations at all. This project depends upon the community more then myself.
What's this?
If you are wondering anything about what this module can do and how it works or if you're experiencing issues of some kind, take a look at the documentation on GitHub and see if whatever you wonder about is covered there (most things are). If they're not, look again and then post in the thread.
If you're wondering about the latest and greatest after an update, take a look at the changelog and accompanying release notes.
Prerequisites
Magisk v20.4+.
Installation
Install through the Magisk Manager Downloads section. Or, download the zip (attached below) and install through the Magisk Manager -> Modules, or from recovery. Combine a recovery installation with the use of the module configuration file and you can set up a certified fingerprint and any custom props you want without first booting on a clean flash. Instant settings.
Usage
After installing and rebooting, run the command props in terminal (you can find a terminal emulator on F-Droid or in the Play Store), and then follow the instructions to set your desired options (also see the documentation on GitHub). You might have to call su before running the command.
You can also run the command with options. Use -h for details.
Submitting Fingerprints
Now this is where you lovely people come in. There is no way ill be able to spend all my time gathering fingerprints and i have absolutely no intention of doing so. However i've made it very easy to submit your fingerprints in a way that i can process them with very little effort.
How to find your fingerprint
Submit your Fingerprint
Source
GitLab - All scripts are completely opensource and your free to download it yourself directly from source
Download Repository
MHPC Releases & Archive
Support
Discord Invite Link - For the time being i will only be able to support users either on here and Discord.
Credits and mentions
There are lots of people to thank for this project. I've included the main two below
@topjohnwu, for Magisk
@Didgeridoohan, for creating MHPC and maintaining it for so long
Original Module Thread
Link to Original Thread
@vithuselservices You forgot to attach the module in your post.
devnoname120 said:
@vithuselservices You forgot to attach the module in your post.
Click to expand...
Click to collapse
Hi. There haven't been any official releases just yet. ETA for the first beta releases are the end of this week but that's only if everything goes well and I see no issues on my tests. So far there are only Experimental releases that i have stopped uploading to the release fileshare.
Once the new build is ready I can begin working on integrating new Fingerprints from the submissions that have been given to me.
@vithuselservices I tried the latest master, and I rebooted. If I type `props` in Termux it says `No command props found`. I have the same issue with the original module though.
Any ideas how to fix this issue?
Edit: typing `su` before solves the issue..
devnoname120 said:
@vithuselservices I tried the latest master, and I rebooted. If I type `props` in Termux it says `No command props found`. I have the same issue with the original module though.
Any ideas how to fix this issue?
Click to expand...
Click to collapse
type su first
I have a really weird question:
I have a poco f3 (europe) phone. I extracted the props from the phones original system (MIUI 13.0.8.0 EEA). I editet the original printlist in the original magisk module, added the
POCO/alioth_eea/alioth:12/SKQ1.211006.001/V13.0.8.0.SKHEUXM:user/release-keys__2022-08-01
line to it, Then flashed the modified zip, and applied the new prop settings. The YASNAC apps says it passes safetynet, and i can use all my banking app except google wallet, and there is no netflix in the ploay store. If I change the props to a value that was part of the original printlist
POCO/alioth_eea/alioth:11/RKQ1.200826.002/V12.5.3.0.RKHEUXM:user/release-keys__2021-06-01
the google wallet works and the netflix app shows itself in the play store.
Is it something that I missed from the prop values? I cannot understand this behavior.
Any advice?
Is this project still alive? I haven't seen any updates for a few weeks. Did OP just ghost us?
neelchauhan said:
Post has been removed by a Moderator
Click to expand...
Click to collapse
Hi.
This is not the case. Can you please remove this post as its highly inaccurate?
Im still here. Apologies for the lack of updates.
Ive had a lot of work come in so its delayed things somewhat but the final version is indeed ready.
Theres a final bit of testing to be conducted prior to making a official release as the last thing i want is bricked phones or settings being dropped.
The first beta release will be out by sunday.
In future can you please give more then 2 hours prior to making such a claim? Its considered rude to make such a claim without reaching out to a dev with sufficient time to reply. Your welcome to fork it yourself. Thats your right. But be more thoughtful when you spread messages like this
dickta said:
I have a really weird question:
I have a poco f3 (europe) phone. I extracted the props from the phones original system (MIUI 13.0.8.0 EEA). I editet the original printlist in the original magisk module, added the
POCO/alioth_eea/alioth:12/SKQ1.211006.001/V13.0.8.0.SKHEUXM:user/release-keys__2022-08-01
line to it, Then flashed the modified zip, and applied the new prop settings. The YASNAC apps says it passes safetynet, and i can use all my banking app except google wallet, and there is no netflix in the ploay store. If I change the props to a value that was part of the original printlist
POCO/alioth_eea/alioth:11/RKQ1.200826.002/V12.5.3.0.RKHEUXM:user/release-keys__2021-06-01
the google wallet works and the netflix app shows itself in the play store.
Is it something that I missed from the prop values? I cannot understand this behavior.
Any advice?
Click to expand...
Click to collapse
Hi.
I believe google is now blocking basic Attestation on newer firmware. This is something im looking into as part of my android 13 upgrade. Certain devices will work better then others. Im sorry i cannot give you a solid answer at the moment. But once im done with my current release and the fingerprints have been updated i can work on this issue. Its likely going to require device specific configurations as newer phones come out. Some people have had luck. but it seems android 12 is the turning point.
vithuselservices said:
Hi.
I believe google is now blocking basic Attestation on newer firmware. This is something im looking into as part of my android 13 upgrade. Certain devices will work better then others. Im sorry i cannot give you a solid answer at the moment. But once im done with my current release and the fingerprints have been updated i can work on this issue. Its likely going to require device specific configurations as newer phones come out. Some people have had luck. but it seems android 12 is the turning point.
Click to expand...
Click to collapse
I understand your point but I don't think its about luck. I did the same thing with my OnePlus 6. In the original prop module the the latest fingerprint is:
OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2109171635:user/release-keys__2021-09-01
and with that all apps and wallet was working fine as intended, an netflix and revolut was present in the play store.
I also edited the original print.sh file and added the latest available fingerpint extracted from a latest full OTA rom which is this:
OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2111252325:user/release-keys__2021-11-01
It also did the exact same behavior as on the Poco F3: YASNAC reports that the Basic Integrity and the CTS Profile match is "PASS", normal banking apps works (local banks like OTP, Erste etc. with NFC payment), but Google Wallet reports that the phone is modified and not certified. Play store also lacks netflix, put reports the device is certified.
The results are the same when I create a printlist file in the root directory in the phone to use my fingerptints as a "Custom" one.
It seems it only happens when I manually add the fingerprint myself, but never with the inbuilt fingerprints. That's why I think something is missing when I use "my" fingerprints. It also the same under android 11. Tested with a Redmi Note 5 Pro LineageOS.
I'm not a dev but if I can help, I'm sure I will.
dickta said:
I understand your point but I don't think its about luck. I did the same thing with my OnePlus 6. In the original prop module the the latest fingerprint is:
OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2109171635:user/release-keys__2021-09-01
and with that all apps and wallet was working fine as intended, an netflix and revolut was present in the play store.
I also edited the original print.sh file and added the latest available fingerpint extracted from a latest full OTA rom which is this:
OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2111252325:user/release-keys__2021-11-01
It also did the exact same behavior as on the Poco F3: YASNAC reports that the Basic Integrity and the CTS Profile match is "PASS", normal banking apps works (local banks like OTP, Erste etc. with NFC payment), but Google Wallet reports that the phone is modified and not certified. Play store also lacks netflix, put reports the device is certified.
The results are the same when I create a printlist file in the root directory in the phone to use my fingerptints as a "Custom" one.
It seems it only happens when I manually add the fingerprint myself, but never with the inbuilt fingerprints. That's why I think something is missing when I use "my" fingerprints. It also the same under android 11. Tested with a Redmi Note 5 Pro LineageOS.
I'm not a dev but if I can help, I'm sure I will.
Click to expand...
Click to collapse
How odd.
Ill raise that as a issue on my Git and have a look at it. It likely wont be this week but ill aim to do some testing on it next week. Are you certain the build date is correct?
vithuselservices said:
How odd.
Ill raise that as a issue on my Git and have a look at it. It likely wont be this week but ill aim to do some testing on it next week. Are you certain the build date is correct?
Click to expand...
Click to collapse
Absolutely! I own all the 3 phones , I also did a full stock rom recovery on all to run the getprop command to make sure the fingerprint and the patch date is correct.
Ohh and almost forgot: thank you!
Beta release is now available!
You can download it via the download repo in the first post. Please let me know if you come across issues. For this first release I do not recommend upgrading daily driver devices just yet as there could still be issues.
Not much has been changed in this release. I'm working on improving the verification process during the install process. I know a lot of people are keen to get fingerprints updated so ill be focusing on that over the next few weeks.
vithuselservices said:
Beta release is now available!
You can download it via the download repo in the first post. Please let me know if you come across issues. For this first release I do not recommend upgrading daily driver devices just yet as there could still be issues.
Not much has been changed in this release. I'm working on improving the verification process during the install process. I know a lot of people are keen to get fingerprints updated so ill be focusing on that over the next few weeks.
Click to expand...
Click to collapse
I tried it right now: the installation has a little problem: it says the installation is failed but it installs it.
{
"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"
}
After that it seems the module can't access for some files and it not really working after that.
I attached a log to help.
dickta said:
I tried it right now: the installation has a little problem: it says the installation is failed but it installs it.
View attachment 5759567
After that it seems the module can't access for some files and it not really working after that.
View attachment 5759575
View attachment 5759571
I attached a log to help.
Click to expand...
Click to collapse
How odd. It works for me. Ill have a run through the logs and get it sorted. Thank you for reporting back!
vithuselservices said:
How odd. It works for me. Ill have a run through the logs and get it sorted. Thank you for reporting back!
Click to expand...
Click to collapse
Same for me. After assigning a fingerprint, reboot will clear it and it reverts back to original
This is still being looked into.
Its coming to the end of the year so im having to process a lot of projects to completion in my day job. Sorry for the delay!
New Beta Build is up. This should fix the install issues users have been having.
Ill be uploading a load of fingerprints very soon. Just finishing off testing the ones i have to hand.
For the moment. Android 13 support is very hit or miss. I'm working to find a solution to this.
A future update will need the deletion of the existing module so it can properly overwrite the new install files. This will also be completed with the next update.
The module now installs without problem, but in the app itself the behavior is the same: it not applies the selected fingerprint, always shows that "not accessible file" error in all activity. It's a good start, keep up the good work
dickta said:
The module now installs without problem, but in the app itself the behavior is the same: it not applies the selected fingerprint, always shows that "not accessible file" error in all activity. It's a good start, keep up the good work
Click to expand...
Click to collapse
Can you try uninstalling the original module and do a clean install of this one?
Im afraid i am not able to recreate the issue at all on my device which is quite infuriating
{
"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 is a free, community built, aftermarket firmware distribution of Android 13, 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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions :
https://wiki.lineageos.org/devices/instantnoodlep
Downloads :
https://download.lineageos.org/instantnoodlep
GPL compliance :
https://github.com/LineageOS/android_kernel_oneplus_sm8250
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Thank for the new release!
Just flashed it. No issues so far.
I have just noticed that the "unlocked bootloader" message returned after flashing latest oos13 firmware. So, every time i restart my device i get the following "your device has been unlocked and can't be trusted". Just wanted to make sure that this is normal (since it was gone in oos12 firmware) and to alert other people about it.
For people who will root and need to pass safetynet the good old methods work however i was unable to find an android13 fingerprint using propsconfig. Instead i used a fingerprint for android 12 and i was able to pass all safetynet checks.
desosav said:
I have just noticed that the "unlocked bootloader" message returned after flashing latest oos13 firmware. So, every time i restart my device i get the following "your device has been unlocked and can't be trusted". Just wanted to make sure that this is normal (since it was gone in oos12 firmware) and to alert other people about it.
Click to expand...
Click to collapse
It's normal:
[Unlocked Bootloader][OOS13/OOS 13 based ROMs] How to remove bootloader unlocked message for OnePlus 8 Pro
This is a guide to remove the ugly "Your device has been unlocked and can't be trusted" or "The bootloader is unlocked and software integrity cannot be guaranteed" for OP8 Pro. This message was removed on OOS 12 which was one great thing by OP...
forum.xda-developers.com
desosav said:
For people who will root and need to pass safetynet the good old methods work however i was unable to find an android13 fingerprint using propsconfig. Instead i used a fingerprint for android 12 and i was able to pass all safetynet checks.
Click to expand...
Click to collapse
I want to ask about this
I've been using magisk, and have been unable to pass safety check on the stock ROM and thought Magisk stopped trying to beat safety net, so I stopped trying also.
It seems you have resolved this.
Can I ask you for direction on how to do this myself after I move to lineageos?
I don't necessarily need full instructions and would appreciate any guidance you can offer me.
Thanks
JustinChase said:
I want to ask about this
I've been using magisk, and have been unable to pass safety check on the stock ROM and thought Magisk stopped trying to beat safety net, so I stopped trying also.
It seems you have resolved this.
Can I ask you for direction on how to do this myself after I move to lineageos?
I don't necessarily need full instructions and would appreciate any guidance you can offer me.
Thanks
Click to expand...
Click to collapse
I haven't tried on 20 yet, but:
root with magisk then add the following modules:
propsconfig and change the fingerprint to a pixel 6 pro
kdragons safetynet patch
Make sure play store and other services are on the magisk deny list.
There are more detailed instructions in various threads specific to each step, but this is the gist of it.
No issues with following the lineage os version upgrade procedure to keep from needing to format data? The upgrade procedure didn't have about needing oos13 firmware beforehand, so I wasn't sure if it'd make a difference.
-update-
No issues yet after following the upgrade procedure without flashing oos13 stock fw first.
I still have some weird issue where it makes me have to sign in to the T-Mobile network. I think it's because I had a Verizon sim in sim slot 2 at one point.. it'll probably require a network settings reset to fix..
Is the 48MP sensor on the camera still locked? Just wondering considering the changes with the camera app and API with LOS 20.
d3viou5 said:
I haven't tried on 20 yet, but:
root with magisk then add the following modules:
propsconfig and change the fingerprint to a pixel 6 pro
kdragons safetynet patch
Make sure play store and other services are on the magisk deny list.
There are more detailed instructions in various threads specific to each step, but this is the gist of it.
Click to expand...
Click to collapse
hi, @d3viou5 how did you root?
I've updated from LOS19 to LOS20, following the official procedure.
Now. I've
- Installed Magisk (tried both canary and stable)
- extracted the boot.img with Payloader-Dumper-Go
- patched boot.img with Magisk
- flashed patched boot.img, system is NOT rooted
- tried to boot (not flash) the patched boot.img, again system NOT rooted
I'm missing something?
thx!
Installed manually coming from LOS 19.1. Did not update firmware, but did the DTBO and VBMETA flashing to be on the safe side. No issues and running very smooth so far. New camera app gets good pics with good lighting. Low light is 2014 quality.
miramax001 said:
hi, @d3viou5 how did you root?
I've updated from LOS19 to LOS20, following the official procedure.
Now. I've
- Installed Magisk (tried both canary and stable)
- extracted the boot.img with Payloader-Dumper-Go
- patched boot.img with Magisk
- flashed patched boot.img, system is NOT rooted
- tried to boot (not flash) the patched boot.img, again system NOT rooted
I'm missing something?
thx!
Click to expand...
Click to collapse
If you go into recovery, sideload magisk apk. That's what I did with 25.2 and it's rooted.
mattgyver said:
If you go into recovery, sideload magisk apk. That's what I did with 25.2 and it's rooted.
Click to expand...
Click to collapse
Thanks @mattgyver
The problem WAS the WORK profile (with SHELTER).
I had to remove my WORK PROFILE (from SETTINGS->ACCOUNT)
And then, sideload magisk.apk (renamed as magisk.zip) and now I'm rooted again.
ThX!
roaringcrown said:
Installed manually coming from LOS 19.1. Did not update firmware, but did the DTBO and VBMETA flashing to be on the safe side. No issues and running very smooth so far. New camera app gets good pics with good lighting. Low light is 2014 quality.
Click to expand...
Click to collapse
Hi, I'm guessing you "dirty flashed" LOS 20 over 19.1 through the LOS recovery?
I was hoping to avoid factory resetting/formatting...
Thanks!
Kuronosu said:
Hi, I'm guessing you "dirty flashed" LOS 20 over 19.1 through the LOS recovery?
I was hoping to avoid factory resetting/formatting...
Thanks!
Click to expand...
Click to collapse
yes, just follow the official guide
Upgrade LineageOS on instantnoodlep | LineageOS Wiki
wiki.lineageos.org
How to install the rom with twrp? i.m using oneplus 8 pro global varient ty
@LuK1337
Thanks for the great work!
I'm currently trying to build LOS 20 myself and as far as I can tell everything compiled properly.
However in the last steps of the build I receive the following error:
Bash:
The following HALs in device manifest are not declared in FCM <= level 4:
[email protected]::IEffectsFactory/default
[email protected]::IDevicesFactory/default
[email protected]::IBootControl/default
[email protected]::IMediaCasService/default
[email protected]::ICryptoFactory/wfdhdcp
[email protected]::ICryptoFactory/widevine
[email protected]::IDrmFactory/wfdhdcp
[email protected]::IDrmFactory/widevine
[email protected]::ICryptoFactory/clearkey
[email protected]::IDrmFactory/clearkey
[email protected]::IHealth/default
[email protected]::IDevice/qti-default
[email protected]::IDevice/qti-dsp
andro[email protected]::IDevice/qti-gpu
[email protected]::IDevice/qti-hta
android.hardware.power.IPower/default (@1)
[email protected]::IRadio/slot1
[email protected]::IRadio/slot2
[email protected]::ISecureElement/SIM1
[email protected]::ISecureElement/SIM2
[email protected]::ISecureElement/eSE1
[email protected]::ISoundTriggerHw/default
[email protected]::IUsb/default
android.hardware.vibrator.IVibrator/default (@1)
android.hardware.wifi.hostapd.IHostapd/default (@1)
android.hardware.wifi.supplicant.ISupplicant/default (@1)
[email protected]::IWifi/default
INCOMPATIBLE
stderr:ERROR: files are incompatible: Runtime info and framework compatibility matrix are incompatible: No compatible kernel requirement found (kernel FCM version = 5).
For kernel requirements at matrix level 5, For config CONFIG_DEBUG_FS, value = y but required n
For kernel requirements at matrix level 6, For config CONFIG_ANDROID_PARANOID_NETWORK, value = y but required n
: Success
Any idea why this is happening?
sToRm1nG said:
@LuK1337
Thanks for the great work!
I'm currently trying to build LOS 20 myself and as far as I can tell everything compiled properly.
However in the last steps of the build I receive the following error:
{code}
The following HALs in device manifest are not declared in FCM <= level 4:
[email protected]::IEffectsFactory/default
[email protected]::IDevicesFactory/default
[email protected]::IBootControl/default
[email protected]::IMediaCasService/default
[email protected]::ICryptoFactory/wfdhdcp
[email protected]::ICryptoFactory/widevine
[email protected]::IDrmFactory/wfdhdcp
[email protected]::IDrmFactory/widevine
[email protected]::ICryptoFactory/clearkey
[email protected]::IDrmFactory/clearkey
[email protected]::IHealth/default
[email protected]::IDevice/qti-default
[email protected]::IDevice/qti-dsp
[email protected]::IDevice/qti-gpu
[email protected]::IDevice/qti-hta
android.hardware.power.IPower/default (@1)
[email protected]::IRadio/slot1
[email protected]::IRadio/slot2
[email protected]::ISecureElement/SIM1
[email protected]::ISecureElement/SIM2
[email protected]::ISecureElement/eSE1
[email protected]::ISoundTriggerHw/default
[email protected]::IUsb/default
android.hardware.vibrator.IVibrator/default (@1)
android.hardware.wifi.hostapd.IHostapd/default (@1)
android.hardware.wifi.supplicant.ISupplicant/default (@1)
[email protected]::IWifi/default
INCOMPATIBLE
stderr:ERROR: files are incompatible: Runtime info and framework compatibility matrix are incompatible: No compatible kernel requirement found (kernel FCM version = 5).
For kernel requirements at matrix level 5, For config CONFIG_DEBUG_FS, value = y but required n
For kernel requirements at matrix level 6, For config CONFIG_ANDROID_PARANOID_NETWORK, value = y but required n
: Success
{code}
Any idea why this is happening?
Click to expand...
Click to collapse
You seem to be doing something wrong, e.g. building -user instead of -userdebug or something else.
LuK1337 said:
You seem to be doing something wrong, e.g. building -user instead of -userdebug or something else.
Click to expand...
Click to collapse
Yeah, you're right... I was building user isntead of userdebug.
Thank you so so much for this! ♥ It works like a charm and it's so so much better than OxygenOS 13 (I can minimize notifications omg!!!1!).
The only thing I personally am missing, is the classic LOS 18 style quick shortcuts in the pull-down notification menu. I always used 1 row with 6 circles, but since LOS 19 it changed to 2 rows with only 4 large shortcuts. But oh well, I guess you can't have everything!
Thank you for maintaining this device @LuK1337 !
@LuK1337
Thank you for your great work.
Not only for your work for this great Oneplus 8 Pro device, but also for other devices before!
You are really one of the most important and best device maintainers.
haxorinjector said:
How to install the rom with twrp? i.m using oneplus 8 pro global varient ty
Click to expand...
Click to collapse
TWRP is only available for A11 and lower. It does not work on A12 or A13.