yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] stillka:
same here...from today, but I did not updated anything...:(

---------- Post added at 04:58 PM ---------- Previous post was at 04:41 PM ----------

update:

[MENTION=8556932]hackintosh5[/MENTION] With a whole bunch of reports of SafetyNet failing both CTS, and basic integrity and also reports of passing at least basic integrity by uninstalling Safetypatcher, I did some testing.

Seems like Google updated SafetyNet with some new checks and your /proc/cmdline bind mount is now a sign of a tampered device. Both SafetyNet checks change to pass if those two lines are removed from your post-fs-data.sh.

Edit: for those that have been guessing, it has nothing to do with the included fingerprint.
[Miscellaneous Android Development] heineken78:
Use this boot its cmdline patched

http://4pda.ru/forum/index.php?s=&showtopic=949903&view=findpost&p=95065580
[Miscellaneous Android Development] stillka:
link doesnt work for me, can you upload it on your google drive?
[Miscellaneous Android Development] heineken78:
This weekend next Los release, with fixed virtual displays and many things I hope also.

And supporting of this never exist device https://www.youtube.com/watch?v=JuLLZMTyDkk
[Miscellaneous Android Development] heineken78:
you can try LOS17.1_HD1_ghost.zip from gdrive already,

but finish version will be tomorrow.

i expect if you have some tests already.

thx
[Miscellaneous Android Development] Qwerqwea:
How can I unlock bootloader ?

Hh6
[Miscellaneous Android Development] chc1212@163.com:
Problems with trying LOS17.1_HD1_ghost.zip

Problems with trying LOS17.1_HD1_ghost.zip:

1. The image link after taking the picture cannot be opened;

2. WeChat fingerprint payment is not available.
[Miscellaneous Android Development] stillka:
google pay (and safetynet) checks fail in HD1 release
[Miscellaneous Android Development] onzem:
You can find it in the general thread of this phone. Google is your friend...
[Miscellaneous Android Development] heineken78:
Google changed algos in safetynet few days ago.
[Miscellaneous Android Development] stillka:
I have Lineage 17.1 installed on another phone (Xiaomi MI MIX 2s) and google pay works fine there...so why same method cant be used on your ROM?
[Miscellaneous Android Development] heineken78:
Does it has selinux enabled?
[Miscellaneous Android Development] stillka:
Selinux: Enforcing
[Miscellaneous Android Development] heineken78:
Thats why.
[Miscellaneous Android Development] stillka:
its not possible to use enforcing selinux policy on your rom?
[Miscellaneous Android Development] heineken78:
You can do it now, but then it will be unstable.

Im working on it.
[Miscellaneous Android Development] xdaillum:
I never got back around to doing this, but in the middle of this whole virus situation I have some more downtime so I am trying to recover it now.

I managed to get the phone into Download mode by using the reboot to bootloader option as per the photo I shared previously.

My computer does not seem to be detecting the phone in any of the USB ports. I have tried installing drivers from here and from instructions here too. This seems to be my problem right now and I am struggling to figure out how to get that. Once I get my phone recognised by ADB/fastboot commands, I think that is one big problem out of the way.

Do you think I can flash the "boot.img" from the LOS 17.1 Daily.zip file to recover?
[Miscellaneous Android Development] xda-yup:
hey if you set selinux to enforcing on HD1 release does safetynet pass? i've set selinux to enforcing on the 20200321c release and it's been super stable for me , but ctsProfile check still fails. wondering whether to jump to the HD1 release yet or wait for future fix.

i had to search this bit a while back while trying to get Viper working, but if anyone finds useful to set selinux enforcing (note- reverts back to permissive after any reboot) in terminal emulator eg. Termux type:

su
setenforce 1
getenforce
[Miscellaneous Android Development] heineken78:
new release with selinux and no magisk needed for gpay from 05.042020 is available.
[Miscellaneous Android Development] stillka:
Hi, rom seems OK, google pay looks fine, big thanks!

I would like to support your work, do tou have paypal account?
[Miscellaneous Android Development] heineken78:
Hi. No my pp is limited to only send payments. But tgx anyway)
[Miscellaneous Android Development] PaladinStu:
You are the best Heineken78. Thank you so much.
[Miscellaneous Android Development] stillka:
hi, what is the best gcam version for this phone/rom?
[Miscellaneous Android Development] heineken78:
Version from 08.04 is available:

-added HD1 dt2wake support;

-fixed more selinux denials ( hight power consumption fix);

-fixed old root detection in some applications;

note: for ss2 c10 use boot.img from previous version
[Miscellaneous Android Development] stillka:
I have S2 (c10) and I used new boot image, what is the problem?

so far I did not noticed anything...
[Miscellaneous Android Development] heineken78:
try open camera..

I have SAT, it uses other config, so im not able to check what is going on for SS2.
[Miscellaneous Android Development] stillka:
yes, camera crashes :)

I will flash old boot.img....
[Miscellaneous Android Development] qba0811:
Camera, Hangouts, Google Keep, Maps, Google Play crashes too :rolleyes:

Going back to previous version doesn't help :rolleyes:

I don't know what to do :(
[Miscellaneous Android Development] stillka:
- flash boot.img from previous release

- reflash google apps

- flash magisk (if you need root)

- clean dalvik cache!!!

- reboot
[Miscellaneous Android Development] qba0811:
Thanks, it looks fine now. Only had to reinstall some apps at Google Play :good:
[Miscellaneous Android Development] atlantix1:
For me, everything on my D10 (SH-D01) runs beautifully and stable with latest release. Big thanks to heineken78! There is only one minor issue: Taking photos with front camera freezes the stock camera app. You can only take photos with 0.4 megapixels. Anything above that results in freezing. Plus: Any other camera app I tried (Open Camera, Google Camera ports etc.) can only take pictures with the front camera up to 4 megapixels. So the front camera sensor seems to be a bit tricky. Otherwise great rom!
[Miscellaneous Android Development] xdaillum:
Hi, does anyone have advice on this issue I am having with Sharp Aquos S2 not being detected by my computer when in download mode and connected via USB? Thanks in advance.
[Miscellaneous Android Development] heineken78:
if it detects in android than it works.

only thing is manually to replace to " Fastboot" driver when its in download mode.
[Miscellaneous Android Development] spootsy:
Thanks so much for your work Heineken, you make these phones actually nice to use :good:

One question, since updating to Los 17.1, I can't make calls through my car's Bluetooth. I can receive them, but I cannot dial out.

This has happened on every Los 17.1 rom I've used, but I've only ever tried them with the updated radio from 5/march. Used to be fine in trebled 3.3. Anybody else get this or know what to fix?

Btw, phone audio is enabled in the phone Bluetooth connection
[Miscellaneous Android Development] drfleckenstein:
Hi, I have the same problem with my hands free in my car (parrot MKi9100).

I can recieve calls but dial out don't work in 9 of 10 times. You hear it dialing but then it nothing more.

Also most of the times the phone don't hand over the network status to the parrot.

Then the display on it says "no network connection", but recieving calls and sometimes dailing out works. :eek:

I'm still on the 20200116 Version of 17.1.
[Miscellaneous Android Development] heineken78:
I would recommend you to install latest version. (make backup before)

Than do reset Bluetooth in reset menu in Android.
[Miscellaneous Android Development] drfleckenstein:
According to your google drive actual version is 20200409

Will gcam work with this version?

If not, boot.img from which version should I take?
[Miscellaneous Android Development] amiali:
Tnx but gsi rom not install gapps
[Miscellaneous Android Development] heineken78:
Please update boot with hotfix. Its temporary.

Fixing continuous wakeup device due to sensor_ind wakecall
[Miscellaneous Android Development] Chazy12:
it's normal that, first boot, is going into the lineage splashscreen from 10 minutes?!
[Miscellaneous Android Development] Chazy12:
.

Inviato dal mio ONEPLUS A6000 utilizzando Tapatalk
[Miscellaneous Android Development] Kazuya5587:
Thank you
[Miscellaneous Android Development] Chazy12:
EDIT: I can't boot to lineage 17 with my Sharp C10.
[Miscellaneous Android Development] Chazy12:
SOLVED: reinstalled the trebled 3.3, then installed and then format data. Now works. Thank you.
[Miscellaneous Android Development] nismohks:
Awesome!

Can this be installed on top of Lineage 16?
[Miscellaneous Android Development] Mozaaa:
Can this rom work on xiaomi redmi note 2 ?
[Miscellaneous Android Development] heineken78:
Unfortunately not, isnt for Xiaomi
[Miscellaneous Android Development] jokolom:
I have compared both files and found differences on a few properties (mostly there are new properties on the Android10 vendor file). However, all combinations I tried in order to fix mifare failed, to the point I'm not sure if the problem is within that file or maybe in some driver itself (don't have much knowledge on the subject so not sure).

For the time being I will not use NFC.

Thank you for your help!
[Miscellaneous Android Development] heineken78:
On last version reported that it works
[Miscellaneous Android Development] jokolom:
I have just flashed vendor from LOS17-aquos-s2-s3-unofficial-161119.zip but unfortunately it doesn't seem to work yet. I'm currently using Havoc3.0. Is there anything that would be needed from either boot or system images in order to fix it?

From what I have read on 4PDA, there was someone who made NFC work on Android Pie with the LineageOS17 libnfc-nxp.conf. At the moment I will remain on Android 10 though as it seems to work better.
[Miscellaneous Android Development] an24mas:
Where download link? Em I blind,
[Miscellaneous Android Development] drfleckenstein:
simply look on the top of the page(black bar) and click on downloads ;)
[Miscellaneous Android Development] paulzie:
[MENTION=1611492]heineken78[/MENTION], thank you once again for your great work in bringing us LOS 17.

Am trying to get fingerprint navigation working in LOS 17 without much luck so far.

The default is:

- LONG TAP=BACK works.

- SHORT TAP is some sort of ENTER. If SHORT TAP on say the launcher screen, it highlights an item. SHORT TAP again and it selects it.

Editting /vendor/user/keylayout/uinput-fpc.kl does not change things.

Any chance of debugging the LOS17 finger print sensor codes so can get them working for navigation?

Thank you
[Miscellaneous Android Development] heineken78:
You messed with file, now it doesnt work.

Thats it.
[Miscellaneous Android Development] paulzie:
The file was modified after the fingerprint sensor didn't provide gestures like stock OREO does in an attempt to correct it.

Maybe you can test fingerprint navigation on your S2 to confirm it's buggy?
[Miscellaneous Android Development] heineken78:
On me it works as in uinput file as usual. Using A10 gestures.

Today LOS17 got Android update. May be I will post fresh build today.
[Miscellaneous Android Development] 自由类者:
That is great!

Thank you very much

But I can't use the ADB command to disable the rounded
[Miscellaneous Android Development] heineken78:
yes this version 20200409
[Miscellaneous Android Development] stillka:
and what s new?
[Miscellaneous Android Development] heineken78:
-lineage up to date;

-selinux denial tricks.
[Miscellaneous Android Development] stillka:
for S2(C10) boot.img is fixed or we should use old one...

update: camera works OK with new boot.img
[Miscellaneous Android Development] qba0811:
Now it works brilliant! Thank you so much!

Only one thing doesn't work with every release (doesn't test on original system). ViPER4Android with plugged in included usb-c=>jack adapter has "unsupported" status. It's hardware or software issue?
[Miscellaneous Android Development] atlantix1:
Quick update: front camera and second rear lense work with Trebled 5.3 on Aquos D10. Replacing libs from vendor ("libchroma*") and camera app from LOS 17.1 with the files from Trebled rom does not help, unfortunately...
[Miscellaneous Android Development] spootsy:
I tried this for my bluetooth issue, but unfortunately it didn't help.

I notice when I disconnect and reconnect bluetooth I can make calls for a couple of seconds before it stops working again. I could probably do a logcat if that's useful.

Is there any way to install just the old radio from 3.3 to see if that works?
[Miscellaneous Android Development] stillka:
second rear lens work? how? its only for "depth" effect...
[Miscellaneous Android Development] heineken78:
13.04. update on your risk as usual

-LOS Android update android-10.0.0_r33 (05.04)

-added Nokia DRG (x6) support :)

-fixed configs media -front camera video fail fix in gcam.

-updated audio configs to Q.

-selinux still in testing.
[Miscellaneous Android Development] atlantix1:
Aquos D10/S3 has dedicated second rear tele camera. It works with Trebled.
[Miscellaneous Android Development] heineken78:
persist.vendor.camera.expose.aux
[Miscellaneous Android Development] atlantix1:
Ah, now I can access tele lens with Google camera. Thanks!
[Miscellaneous Android Development] stillka:
what gcam version?
[Miscellaneous Android Development] atlantix1:
I don't know if it is actually the best option, but latest Urnyx (v1.5) seems to work nicely: https://www.celsoazevedo.com/files/android/google-camera/dev-urnyx05/. However, sometimes night mode crashes, but most of the time it will work.

P.S.: Only flaw ist that front camera only takes pictures up to 4MP, but that's the case with all gcam versions.
[Miscellaneous Android Development] xixuluo:
[MENTION=1611492]heineken78[/MENTION] my sharp ss2 got a wifi connection speed limited up to 13mbps on your works since you have update some thing about wifi in boot.img

i tried 2020.02.04 build,wifi work,and it has fully worked and the speed of wifi downloading is up to 120mbps

it must someting wrong with your boot but not vendor,because i use 0204build vendor successfully booted your 0413 work,and still got wlan speed limited,

finally,i use 0204 boot.img with 0413 vendor and system,wifi limitation disappeared,and it has 120mbps wifi download speed,

i also noticed that the limitation is since 0321 build or maybe earlier,and treble v5.3 has this problem equally,i hope you can roll wifi items back to 0204 build,cause 0204 boot will make camera crash about 1.5seconds,thx

i am a chinese,please forgive my **** make english that may puzzle you
[Miscellaneous Android Development] xixuluo:
warring to ss2 user.

do not flash gdrive folder's individual boot.img，that is drg's boot

when i flashed it，my wlan broken and i rebooted to recovery to wipe data，i found that the recovery was replaced with a hmd recovery..whats more，the title of rec is for drg，20190818 android q，not ss2.

at that moment，my heart stppped.

its thrilling sir，i have flashed drg's boot on my ss2 and not brick my phone expects wifi，and i found that camera seems of great quality

i will repeat it in chinese because i think english cannot express my heart stopping moment well

他妈的吓死我了，我居然给夏普s2刷了个诺基亚x6的boot还成功开机了，千万不要往夏普s2上面刷g盘根目录的那个boot，wifi会炸的，其他问题似乎没有
[Miscellaneous Android Development] xdaillum:
I still can't get my computer to detect my Aquos S2 in Download mode using either "fastboot device" or "adb devices" commands :(

BUT! I've managed to get my device to appear when typing "adb devices" when the phone is in recovery mode in "Apply update from ADB" mode. It shows my Device ID followed by "sideload" next to it.

The instructions at the bottom of my phone says:

Now send the package you want to apply to the device with "adb sideload <filename>"...

If I now take the latest stable LineageOS (LOS17.1-20200204-DAILY-S2-S3? the others have beta/test) then extract then flash boot, system, vendor via this ADB sideload method, will this help me recover my device?

I also notice it says on the first post: Last Updated LOS 17.1 2020-04-13 - but the Gdrive folder link - the latest I can see include betas is LOS17.1-20200321c-beta-S2-S3.7z - where do I get 2020-04-13 version?
[Miscellaneous Android Development] xdaillum:
I've tried to do this by using "adb sideload <filename>" as I figured that since my device is in bootloop it's probably hard to have it screw up even more, haha.

Anyway, this is what happened.

I attempted to do adb sideload boot.img. This is what then appeared on my screen (attached). Basically it looks like "signature verification failed" (I assume it means unrecognised file?), and I was prompted to confirm to proceed with installation anyway, so I pressed "Yes". But it still failed. On CMD, it says

serving: ' boot.img (~0%) * failed to read command: No error

Am I using the wrong boot.img file, or am I not able to use the boot.img file from the zip of the LineageOS I downloaded? Or can I not use ADB sideload for what I'm trying to achieve? I downloaded LOS17.1-20200204-DAILY-S2-S3.zip from the Gdrive folder link of the OP.
[Miscellaneous Android Development] qdaexplorer:
I still could not use the tele lens on S3. When switching gcam mods either crash or use the main one anyway.
[Miscellaneous Android Development] atlantix1:
Hm, I could use tele directly after changing/adding the line to value 1 in build.prop. Btw. I used Magisk Hide Props for that purpose.
[Miscellaneous Android Development] heineken78:
Props hide doest make sense for this

Probably i need to add option aux in settings.

We expect new wifi kernel driver, latest caf drivers from qcom, new battery profile, selinux fixes and los update in next 7z archive.

Only puur qcom sources.
[Miscellaneous Android Development] atlantix1:
Sounds promising! (And, well, the module is called Magisk Hide Props Config, which lets you easily change or add any prop value systemlessly. I added persist.vendor.camera.expose.aux=1 and tele works. Only in gcam, not in stock camera.)
[Miscellaneous Android Development] Kooger111:
Recording with wired earphones will change sound
[Miscellaneous Android Development] xdaillum:
2 main bugs to report for version 2020-04-13, both related to the SIMs/picking up a network signal.

You can't change SIMs or insert SIMs while the device is on - it will not detect any new SIMs and you'll have to restart. It will keep saying, "Invalid card - Emergency calls only" in the corner if you remove SIM while device is on.

The device will sometimes freeze for about 5 seconds, then auto-reboot after being on for about 25 seconds. I can't quite figure out the exact triggers but it seems to be related to the SIM cards and them picking up a signal detailing my findings.

Here is what triggers a reboot:

1 SIM inserted and it connects to roaming

1 SIM inserted and it does not pick up any signal

2 SIMs inserted, and one fails to pick up signal while the other one picks up local signal

2 SIMs inserted, and one fails to pick up signal while the other one picks up roaming signal

2 SIMs inserted, but neither picks up signal

2 SIMs inserted, and both successfully pick up signal, but one is local and one is roaming

This seems to be irrespective of SIM card slot. I tested both card slots for all scenarios.

The reboot still seems to occur, even if you eject the SIM tray in these scenarios before the phone fully boots up. I assume there's a point of "no return" where beyond a certain point in the start up, the device will have already started trying to pick up signals via the SIMs, so if you eject beyond this point, it doesn't seem to help.

Here is what does not trigger a reboot:

No SIM inserted at all (when it says "Invalid card" as opposed to "No service")

2 local SIMs inserted and both pick up signal

1 SIM inserted and it picks up local signal

So going off what I've shared, it seems like it's something to do with roaming and/or not picking up a signal.

That's all I've stumbled upon for now, but it looks like it is otherwise a really nice to use ROM and I'm really happy to have my phone up and running again, regardless!

Btw heineken, how do I contribute/donate?
[Miscellaneous Android Development] xixuluo:
[MENTION=4473370]xdaillum[/MENTION] if u wonna to boot into twrp,you must insert a charger or connect to your computer,then press power and volume up before the apparence of yellow characters

do not use fastboot reboot recovery because the word after <reboot > means a partion,but fih devices have no recovery partion,only a 64mb bootimg included twrp
[Miscellaneous Android Development] xdaillum:
Hey, I don't have an issue with getting into TWRP anymore. I managed to resolve the issue haha.

I'm not sure what you meant by the second paragraph.. FIH devices have no recovery partition but only a 64MB bootimg included TWRP?
[Miscellaneous Android Development] xdaillum:
I have realised that the reboots are not limited to roaming/not picking up signal as I have suggested above.

I now suspect it is to do with attempting to pick up a mobile data signal specifically.

I noticed this because I realised the testing in the reply I posted specifically for the local SIM scenario - my local SIM was not actually picking up a data signal. I then added APN settings as there were none configured, to try and force the SIM to get a data signal. As soon as I did that, the phone rebooted, in the same manner to how it did in all the other scenarios. After rebooting with APN settings configured/saved, it then kept rebooting.

I tried to quickly delete the APN settings after each reboot, but couldn't. So ultimately, I turned on airplane mode on one of the reboots, which still didn't prevent a reboot (as I said, there seems to be a "point of no return") but this final reboot allowed me to delete the APN settings that I had saved. The phone will then stop rebooting provided I do not have the APN settings for this specific local SIM inserted.

Anyone else experiencing this issue?
[Miscellaneous Android Development] xixuluo:
i got a amazing launcher from samsung,it doesnt work on los but working perfectly on trebled v5.3,screen recording makes it crashing,the fact is that it will bring 60fps recent animation to you,i up loaded the preview video to youtb

you can search (one ui launcher magisk module on sharp s2 with trebled v5.3)
[Miscellaneous Android Development] xixuluo:
[MENTION=1611492]heineken78[/MENTION] wifi issue has not fixed on ss2

you said you have updated the wifi driver in boot

，but this issue is not cause by wifi driver maybe

the network still limited in 13mbps，0205boot still works well expects camera

i unpacked your boot both 0205 and 0423 works，and moved 0205's boot/ramdisk/sbin/libwifikeystorehal.so and android.system.wifi.keystore@1.0.so to 0423 then repacked 0423 folder to a boot.img，i hope it may works but still get 13mbps wifi after flashed and reboot even clean up data and reboot

but when i moved 0205's boot.img/zImage to 0423 folder and repacked 0423，its wifi get a rebirth!but also，i got a ? like camera after replaced the zImage

so the conclusion is the issue is due to the zImage

not driver，and 0205 boot is still the best boot for ss2. i dont know how to unpack zImage，so further research is impossible for me
[Miscellaneous Android Development] heineken78:
have you try todays version?
[Miscellaneous Android Development] new_melody:
I got 23.04 version and low wifi speed problem still exists.
[Miscellaneous Android Development] heineken78:
I think you have to reset wifi on both devices, that's it.
[Miscellaneous Android Development] new_melody:
Works.