yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] jokolom:
I have reinstalled LOS17 to retry these things on my phone, and this is the summary:

- Encryption: OK. I have now verified that after installing the ROM, wiping data and rebooting, data in TWRP shows as encrypted even though password will not match like you say (file names appear as garbled characters) so this seems to be working OK.

- NFC: I still cannot make NFC work. I have installed safetypatch on Magisk, CTS profile and basic integrity show as OK on Magisk. Not sure what makes NFC not work, maybe I'm missing something.

- Notification LED: I cannot see notification LED working after receiving a notification, such as Whatsapp.

- Warning message on boot: a warning message triggers on system reboot. This is a minor detail since it's just an informative message.

Other than that, everything seems to be working correctly. I will keep using this ROM as a daily driver and report any other problem I can see.

Thank you!
[Miscellaneous Android Development] jokolom:
After installing latest version (0611) now NFC card makes sound when it's near the phone and opens NFC app. However, it seems to crash. I have taken a logcat regarding NFC problem. These are the following lines worthy of notice, please tell me if this helps:

11-06 12:35:07.189 11571 11618 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'short android.os.Bundle.getShort(java.lang.String)' on a null object reference
11-06 12:35:07.189 11571 11618 E AndroidRuntime:	at android.nfc.tech.NfcA.<init>(NfcA.java:76)
11-06 12:35:07.189 11571 11618 E AndroidRuntime:	at android.nfc.tech.NfcA.get(NfcA.java:62)

11-06 12:35:07.853 3646 11670 E libnfc_nci: [ERROR:phNxpExtns.cpp(220)] Error Sending msg to Extension Thread
11-06 12:35:07.854 879 879 D NxpExtns: find found MIFARE_READER_ENABLE=(0x1)
11-06 12:35:07.854 879 879 D NfccPowerTracker: NfccPowerTracker::ProcessCmd: Enter,Recieved len :4

11-06 12:35:59.782 10874 10874 I RenderThread: type=1400 audit(0.0:846): avc: denied { execute } for path="/vendor/lib/hw/gralloc.sdm660.so" dev="mmcblk0p80" ino=776 scontext=u:r:untrusted_app_27:s0:c168,c256,c512,c768 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=1

According to logcat, even though it doesn't work, it seems to know the card type (mifare):

11-06 12:35:10.155 758 3327 D NxpHal : NxpNci: RF Interface = MIFARE
11-06 12:35:10.155 758 3327 D NxpHal : NxpNci: Protocol = MIFARE

Thank you!
[Miscellaneous Android Development] heineken78:
release 06/11/19 fixes this issue.
[Miscellaneous Android Development] heineken78:
config nfc-nxp.conf needs to be fixed to new drivers.

unfortunately im not able to use nfc at all on my SAT - antenna is broken.

so someone has to do it...
[Miscellaneous Android Development] jokolom:
I have found this file: /vendor/etc/libnfc-nxp.conf. Is that the file you reference to?

What can I do to help? I have no problem trying thing but I would need some pointers on what should be changed.

Thank you
[Miscellaneous Android Development] paulzie:
Here's : /vendor/etc/libnfc-nxp.conf from 2080WW SAT (stock Oreo).

View attachment 4869289
[Miscellaneous Android Development] jokolom:
I have just tried it. Instead of crashing, it will get stuck while trying to read the NFC card. Moreover, the NFC settings get stuck as well.

Thanks
[Miscellaneous Android Development] heineken78:
that what Im trying to tell you. Paul shared old config, I have put modified to work with new hals.

May be you can compare both and fix it.

My nfc is not working due antenna problems.

Thats it!
[Miscellaneous Android Development] iiandrusii:
[MENTION=1611492]heineken78[/MENTION] Sorry but I can't find link to download rom files in first post (update 2019-11-06 too) . :)
[Miscellaneous Android Development] heineken78:
This is question to XDA designer. Change XDA style page and find tabs, we are on "di-scussion" now, next is " downloads"...
[Miscellaneous Android Development] iiandrusii:
I found ? thx
[Miscellaneous Android Development] heineken78:
new LOS 05.01 I suggest to try.
[Miscellaneous Android Development] paulzie:
Very good ROM. Integrated the 4pda.ru info to get fingerprint gestures working. Fast, good battery life, looks great. Magnificient :)

Incidentally, go a new camera module to fix previous problem. Strange thing is the 12MP camera (and flashlight) only works if I disconnect the second 8MP proximity camera. If keep it connected, then only the 8MP camera works. Any clues on a simple fix? Figure systemboard might have a camera power issue somewhere but no idea where to look without schematic. You look well clued up with the Aquos S2.
[Miscellaneous Android Development] heineken78:
I thought it will be. Something you have damaged on motherboard, power specific (there is not profit in Performance mode, since its cutted by thermal, right). There is less/more power for 2 cameras on same power slot. It might be one of power controllers, or anything on motherboard or even motherboard.

Leave only 12mp, 8 is useless.

To all:

I have made mistake in thermal hal in 05.01 release just before compiling. If you play games and feel phone too hot I suggest to replace this file in vendor/bin/hw and give permissions 755.

Consider that power modes (in settings)above "balanced" are not covered by CPU thermal protection. Only very few- such charging, battery remain. So if motherboard reaches 60C phone will shut down.
[Miscellaneous Android Development] heineken78:
Today we will try LOS 17.1 may be
[Miscellaneous Android Development] rav3n_pl:
17.1 have "pixel drop" feature, do we need it on our non-oled display at all?
[Miscellaneous Android Development] heineken78:
Comment of LOS Director about:

https://www.reddit.com/r/LineageOS/comments/ejvpos/lineage_os_171/
[Miscellaneous Android Development] heineken78:
Btw

All works, need to rebase my patches and add wfd and check.

Really snappy android build.
[Miscellaneous Android Development] paulzie:
[delete]
[Miscellaneous Android Development] heineken78:
LOS 17.1 tezt is out
[Miscellaneous Android Development] heineken78:
LOS 17.1 test 2 11.01

-more vendor implementations, kernel battery fixes,

-new LOS android r23 05.01.20
[Miscellaneous Android Development] heineken78:
here you can try to compare official stock s3 Android 9 (thats now in my LOS 17X libnfc-nxp-hh6.conf) and Android 10 ( I will now attach libnfc-nxp.conf) confs, seems mifare is no more. By analogy you can try to fix conf of s2- libnfc-nxp.conf in LOS17.1 vendor/etc

As you know I don't have nfc antenna, so can't check mifare..
[Miscellaneous Android Development] heineken78:
Boot -twrp for LOS 17.1 s2/s3

Finally power caused lag is beaten.

Battery meter is stable and long.

Fast charge working!

https://drive.google.com/open?id=1h1vgNZ8B4nqmV50iHzJ7sumkQmxiSHbb
[Miscellaneous Android Development] baszek:
Is it stable enough to use as daily ROM ? or you recommend sth else for daily use ?
[Miscellaneous Android Development] rav3n_pl:
OP says it is beta ;)

Will try tomorrow on my S2 :)
[Miscellaneous Android Development] Lovetz:
It is quite stable and suitable for daily use.
[Miscellaneous Android Development] adamuadamu:
is it possible to upgrade from LOS17 25.12 to current LOS17.1? Or clean install only?
[Miscellaneous Android Development] heineken78:
izi
[Miscellaneous Android Development] rav3n_pl:
[MENTION=4377295]adamuadamu[/MENTION] Just flash, no wipe needed (checked :P)

[MENTION=1611492]heineken78[/MENTION] where is source tree for 17.1? Wanted to try complie it by myself, but found only 17.0 on github (and not sure it is complete/ready to compile, reading AOSP build tutorial).
[Miscellaneous Android Development] xdaillum:
I've obviously made a mistake in this process. Currently bootlooping and I don't even seem to be able to access Download Mode or Recovery Mode. Hoping for some assistance.

Prior to attempting flashing LineageOS, my Sharp Aquos S2 could only access Download Mode and Recovery Mode (TWRP). This occurred after attempting to update Magisk from within Magisk Manager.

I decided to use this opportunity to change from the OS I was using at the time (I think it was this: https://xdaforums.com/android/general/sharp-aquos-s2-ss2-sat-thread-t3761071) to LineageOS.

I tried to follow the instructions on the main page as follows:

"Enter twrp or from fastboot and flash images: boot, system, vendor. Reboot back recovery and format data. Install Gapps same time (as option).Reboot to new system."

I was in TWRP, selected flash image, and selected the "boot.img" file from within the Google Drive link and flashed "boot", "system" and then "vendor", one after another. I was in the process of trying to reboot back to recovery. The first reboot, I saw a little splash screen that had a small circle in the middle and it looked like there was text, something like "Winson". After that, it just started bootlooping and I haven't been able to turn it off, get it into recovery mode or download mode. I must've made a mistake here. For example, I first thought that "boot", "system" and "vendor" were 3 different files, and I could only see 2x of them in the GDrive link (boot.img and system.zip). Vendor was nowhere near to be seen. However, after I saw the options in TWRP after selecting flashing boot.img, I thought this step was all to be done from boot.img.

My intention after that was to then flash LineageOS, then flash pico Gapps, then flash Magisk 20.3 (latest version).

Could someone give me some advice to firstly get out of this bootloop? Sorry for the long post but just trying to include as much detail as possible.
[Miscellaneous Android Development] Psyl0w:
Well first off, how can u expect to get a good result by flashing thru a google drive link :confused: and which link by the way

Is it still necessary to remind flashing is not harmless :

Whatever, u can try this:

Unzip localy the latest firmware.

Try to to enter in the download mode by connecting usb and press power+vol down

Flash boot.img with fastboot.

If u cannot get access to download mode your last chance is emergency mode or 9008 one. Check in the sharp s2 thread how to reach it. That will be painful as opening the phone is required likely :(

ÉDIT: after checking myself, I notice I cannot accès download mode with bouton combo anymore. That’s really scary bécots fastboot is a bit the last backup in case of problems
[Miscellaneous Android Development] xdaillum:
Sorry to clarify, I obtained the files from the Google Drive link. It's surely not possible to flash from a Google Drive link lol

I'm referring to the link in the OP under the red text, "Downloading", "GDrive folder". It links to this.

Yes I know it's not harmless. I'm not a pro by any means (obviously LOL) but not a total noob though so I was somewhat confident lol.

Also I wanted to come back and update that I did actually manage to eventually access what looked like recovery mode. I have attached 2 photos of what I saw on the screen. One shows the top of the screen, and the other shows the bottom. This looks much more promising than what I was seeing previously!

Thanks for your help/advice though, but I think given I can access this mode, the chance of recovery should be higher.

Can someone advise what steps I should take from this screen? I would suspect I would need to "reboot to recovery" and try go from there. I will try it later. Would like to ask though, as per my post above, what files am I supposed to be downloading exactly and how do I flash "boot, system, vendor"? Is what I did correct?

Thanks in advance.
[Miscellaneous Android Development] Psyl0w:
Ok fine. Yes you definitely increase your chances of recover proper os with this.

I’m still very surprised by the stuff display on your screenshots. I know there is a certain connection between our sharp and Nokia but the fact you have a recovery with Nokia dragon is surprising. Just for curiosity what is your firmware?

I’m not a super pro but I would select reboot in bootloader to work with fastboot and type the first commande:

Fastboot device to check connection is ok

Then fastboot getvar all to know on which slot is the device.

Then you can flash or just boot a boot image with twrp from fastboot.

Good luck
[Miscellaneous Android Development] heineken78:
Nokia 4050 firmware was taken to pass Google certification, also propertary blobs are taken from.

Puur LOS boot looks like that.

He installed old LOS17.0 daily version, that's don't include TWRP boot.
[Miscellaneous Android Development] xdaillum:
I don't know what firmware I'm on...

I have got around to playing with it yet. Will play with it shortly.

Hey Heineken. Firstly, thank you for your effort/hard work with this!

What do you mean I installed LOS17.0 daily version? I was going to flash from the file called "LOS17.0-20200105-UNOFFICIAL-S2-S3.zip", but this error I encountered was after trying to flash "boot.img" (the one located in root folder of the linked GDrive folder) as boot, system and vendor. Is this the right thing to do? I did not even manage to get to the stage of flashing "LOS17.0-20200105-UNOFFICIAL-S2-S3.zip" because I already encountered this error prior to that.

In what order do I flash, and from what file exactly?
[Miscellaneous Android Development] iiandrusii:
My phone all the time turns off when I charging or watching a movie.
[Miscellaneous Android Development] Psyl0w:
Well I don’t know if I misunderstand what you write or if it’s confuse in your mind, but it seems you haven’t got the trio of images boot system and vendor are included in the los zip file. So u grab for instance https://drive.google.com/drive/mobi...joHM7icESY?usp=drive_open&sort=13&direction=a

You unzip and you flash each image in the correct partition. You will probably need to perform a factory reset and format data (if encryption hasn’t been removed) but you can try without. If you don’t know how to flash images with fastboot or twrp, google will help u.
[Miscellaneous Android Development] pttptuan:
i get bootloop when using sim card sharp SS2

help me fix this bug

i'm try los 17 20200105 and los 17.1 20200116
[Miscellaneous Android Development] heineken78:
you need to upgrade base firmware to use Android 10 - bootloader and modem.

2130 or 2140 for SS2.
[Miscellaneous Android Development] pttptuan:
can you give me this ? thanks alot
[Miscellaneous Android Development] heineken78:
https://fih-firmware.hikaricalyx.com/sharp.html
[Miscellaneous Android Development] pttptuan:
how can i use it ? thank you
[Miscellaneous Android Development] xdaillum:
Oh my god yes I'm the confused one. I have never had to unzip a .zip to "flash" individually. So far, whenever flashing a new ROM (such as this), I've only ever done it by flashing the .zip file itself so I have never even thought to open up the zip file and take the files out individually, or to look inside the zip file individually for boot/system/vendor.

You are correct though - I did not have that trio of images but I can now see it in the .zip file I downloaded.

I'll try that now..!
[Miscellaneous Android Development] Psyl0w:
That’s because you’re used to flashing zips with installers. This one includes images only.
[Miscellaneous Android Development] XsceS3:
Android Service Error

Hi;

I flash last verison 16.11.2020 but system error (says android device error please connect manufacturer ....) and camera app isn't here.Please help.
[Miscellaneous Android Development] xda-yup:
I had the same problem you were having nismohks (LOS bootloops back to TWRP) after following instructions from OP, I was coming from trebled 3.1 . I fixed the issue by flashing 2130 trebled 3.3, then following the OP but this time removing the usb cable during boot to system . Never would have thought to do that so thanks Psyl0w :good: , pretty sure this is the single thing that stopped the bootloop. I am now successfully running 16Jan version LOS17.1 :)
[Miscellaneous Android Development] xda-yup:
My SS2 is running on working LOS17.1 16Jan, all great so far.

i've just noticed i can't create backups or restore backups in TWRP though if i have a password set (whereas i could do so back on trebled 3.3). I think because I can't decrypt internal storage due to bug mentioned above / OP where password doesn't match in TWRP. New backups fail and existing backups just show as encrypted strings when you try to restore. So how do i decrypt storage while in TWRP to fix, is there some default password / pattern i can use? Or do i have to remove passord/saved fingerprints to create new backups / and in the event of system crash, will i be unable to restore and only option to reflash fresh 3x LOS .img again, then restore backup from SD card afterwards?

Screenshot of TWRP backup failure: https:// imgur.com/a/auQ8wo1
[Miscellaneous Android Development] heineken78:
a) You can't do user key encrypted data backups.

b) The bug that twrp can't recognize user key is written on 1st page.
[Miscellaneous Android Development] heineken78:
You can check link to "sources" on first page, just created :p
[Miscellaneous Android Development] Psyl0w:
Update TWRP

I’m really interested in an updated TWRP release if somebody makes a new one for los 17.1.

Updated means with Toybox commands updated. The current twrp includes outdated version 0.76 and lots of commands like TAR are buggy or limited regarding Busybox. The last version 0.82 is definitely improved. Android has already included it in its master branch:

https://android.googlesource.com/platform/external/toybox/+/ce2b356a0746e1203be0cf1ab9c90abdb0394e47

But not TeamWin yet :(

And lots of my backup scripts that uses TAR command cannot work properly with the old version. I would probably try to build an updated version but I don’t have Linux machine so far.

Here is the android.mk from twrp, the pathes towards tar and other commands are still pointing the pending folder but they are now in posix one with the new release. :angel:
[Miscellaneous Android Development] xda-yup:
thanks, i read about user key bug i just don't think i understood the implications of it - ah so that bug means that to make a twrp backup we have to remove password before rebooting to twrp (that's what i've been doing so far). when i remove password, fingerprints removed, Gpay cards removed, so wanted to make sure i wasn't doing this each time without need :) tiny issue though in light of how awesome this rom is to use. i'm really enjoying LOS17.1 16Jan version , all working very smoothly, Gpay and Gcam confirmed working etc . Thanks so much for your work on it!
[Miscellaneous Android Development] rav3n_pl:
This is what exactly we have to do before every update.

Remove lock screen complently,

reboot to recovery,

install update bins (boot, vendor, system)

and zips (gapps and magisk),

clear dalvik

boot :)
[Miscellaneous Android Development] heineken78:
best video on spamtube ;)
[Miscellaneous Android Development] rav3n_pl:
Thats why I have it in my footer :D

Updated to 17.1 01-16, it is till crashing when I want to run AR mode in GMaps... Any ideas?
[Miscellaneous Android Development] heineken78:
reinstall
[Miscellaneous Android Development] rav3n_pl:
Tried, send PW witch logcat.
[Miscellaneous Android Development] drfleckenstein:
Hello,

have installed 17.1 01-16 and everything seems to work except two things:

1. at reboot I got following message when android has booted to home screen:

"There is an internal problem in your device. Please contact your manufacturer"

2. if I select "Expanded Desktop" under display options I jump back to settings overview.

I also changed the "uinput-fpc.kl" to get back the stock fingerprint gestures, but there is no haptic feedback when using the gestures.

Is it possible to get them?

Except these minor "problems" the ROM is awesome :) Thank you
[Miscellaneous Android Development] jonogwil87:
So ive downloaded the images, downloaded the twrp app, transfered all the files onto the phone from my computer.

how do i now flash lineage onto the sharp S3? When i open the twrp app it cant find the img or phone
[Miscellaneous Android Development] dmukhin:
Actually there is no need to remove locking unless you know that something was dramatically changed with encryption or you need to take backup. Some applications affected by removing locking and you have to reconfigure. And Dalvik wipe is not required
[Miscellaneous Android Development] rav3n_pl:
TWRP is not recognizing pin/password and crying that can not decrypt data.

You sure, that I can update system and flash gapps on encrypted data partitions?
[Miscellaneous Android Development] dmukhin:
It's just about data partition, it doesn't change it on update. Of course, all files you choose for installation should be on external card or OTG
[Miscellaneous Android Development] heineken78:
Read about here https://source.android.com/security/encryption/file-based

At first clean boot AFTER FORMATTING, depending from init settings of current Android OS encryption gets enabled only on some folders, not for all internal memory.

In our case, with lockscreen password getting encrypted data/media, data/data only with common random metadata key plus TEE key (hardware), that's makes impossible to decrypt on another device.

Rest of folders remain always encrypted with default key and free to watch.

H/w encryption (tee) of s2 and s3 is different to. s2 uses old qcom implementation with keystore and s3 already new qti.keymaster.

That's why flashing keymaster partition from s2 will brick completely s3 and otherwise.
[Miscellaneous Android Development] dmukhin:
That's really good to know! But it doesn't change some redundancy of what initially rav3n_pl mentioned I believe. There is no need to disable pattern, key or password on each update installation (unless backup should be taken), right?
[Miscellaneous Android Development] heineken78:
You can do experiment because of Magisk. Media and data/data are encrypted by lockscreen key. During the update of system and vendor, data is not used. You will need only source with gapps package zip.
[Miscellaneous Android Development] drfleckenstein:
Today I discovered another problem with my C10.

None of the sensors are working. :(

No rotating, no accelleration sensor,...

I tested with antutu and some sensor testing tools from playstore, but for all sensors they said not supported.

Anyone discovered the same problem with the ROM?

Best regards
[Miscellaneous Android Development] heineken78:
you need to flash persist partition.
[Miscellaneous Android Development] drfleckenstein:
Ok, but from where?

I have a TWRP Backup of the stock 2140 ROM, but without this partition... :confused:

By the way, fingerprint, camera und nfc are working...
[Miscellaneous Android Development] heineken78:
You can take persist from nb0 or service rom and flash via fastboot flash persist
[Miscellaneous Android Development] nismohks:
Just updated to the newest 116 build and on startup it says

Android system

There’s and internal problem with your device.

Contact your manufacturer for details.

Any idea how this can be fixed?
[Miscellaneous Android Development] heineken78:
its OK
[Miscellaneous Android Development] nismohks:
Ah ok I will just ignore it then

Thanks

---------- Post added at 07:32 PM ---------- Previous post was at 06:46 PM ----------

What version can are people using?

Have tried a few but they will just take a photo and then crash without saving the image.
[Miscellaneous Android Development] rav3n_pl:
I'm using LOS 17.1 16-01-2020 on top of 2130 Trebled v3.3

Only issue I found is crashing AR mode in Gmaps.
[Miscellaneous Android Development] drfleckenstein:
This did the trick.

Sensors are working now :D

Thanks

If anyone seeks for the file:

https://4pda.ru/forum/index.php?s=&showtopic=892500&view=findpost&p=91921837

---------- Post added at 07:57 PM ---------- Previous post was at 07:52 PM ----------

I'm using this one for a while now:

https://www.celsoazevedo.com/files/android/google-camera/f/changelog958/

so far everything works and it starts very fast :D
[Miscellaneous Android Development] nismohks:
Awesome, this works great!
[Miscellaneous Android Development] amiali:
After update los 17.1 2020.1.28

Battery percentage gsi pixel experience not work
[Miscellaneous Android Development] heineken78:
Pls cry on gsi thread.