yashsingh1/xdaforums huggingface dataset:
[Android General] Lovetz:
Hi. I use it for several hours and I can write a small review.

- the graphic key and the date decoding work in the recovery.

- PC sees the smartphone and files can be transferred.

- works double tap to wake (and sleep) on the screen (can be disabled).

- fingerprint scanner control works. You can also turn on the onscreen buttons - then the scanner control does not work.

- auto brightness works.

- when you take the phone in hand, you can see incoming notifications (ambient) on the screen - you can turn it off.

- turning on the screen for incoming events and connecting the charger (you can disable both).

- You can round the corners (only all four at the same time) and adjust the offset of the status bar icons from the edge.

- You can choose a dark or light theme, plus the color of the accent.

- The status bar is narrow and this has not yet changed.

- extended reboot menu - enabled in developer mode.

- root can be enabled in developer mode.

- Night screen mode and reading mode.

- the built-in apt-x codec, but so far there is no sense from it, since the BT headset only works in talk mode, the music does not go into it - it sounds from a conversational speaker.

- wired headphones work - you can listen to music in them.

- in the settings of the mobile network by default LTE, but if you tap only 2g / 3g to choose from (for now such a bug).

- processor governor by default - performance - so the phone does not sleep and eats battery. If you put the kernel auditor and set the governor in interactive, for example, then everything is normalized.

- when connecting the headset BT there is an icon with the battery level (if the headset support it).

- in the call there is a record of the conversation - writes to amr.

- the led does not work yet, but the author has already solved this problem - we are waiting for fixes.

- Built-in camera works, it has HDR and other chips.
[Android General] HeyM8:
Can I replace my existing Treble 3.3 ROM/Pixel Experience 9 GSI with this new Lineage 15.1/Pixel Experience GSI/Nokia version?

I want to keep using Pixel Experience Pie, but happy to replace the base Treble images if it offers advantages.
[Android General] aingerunn:
I installed several times the first version and the new one. It is installed correctly, but every few seconds it automatically restarts. I don't know if it happens to anyone else. Any advice
[Android General] heineken78:
May be you are using alb/xbl from android 7.1.1? Its written 8.0!

Because cmd is hacked you need only this version.
[Android General] aingerunn:
The base Rom, I installed by OST the 3.1
[Android General] Lovetz:
You can try to make format data. I don't have such problems.
[Android General] indestin:
Mobile and data not working

From treble 3.3 to Release 1.1 by TWRP with full format
[Android General] Lovetz:
Try this fix: https://xdaforums.com/showpost.php?p=78262728&postcount=1707
[Android General] indestin:
Thanks bro. It's worked.

Before early...I got this...
[Android General] indestin:
Gpay and bank app not working, root is disabled

Gcam is good. nightshot ok slowmo ok
[Android General] Lovetz:
Do not pay attention. Does not affect anything. Everyone has this situation on this firmware.
[Android General] heineken78:
this is message, because BUILDFINGERPRINT is used from SS2 WWE firmware. Without it, you will not be able to use googleapps without registration of each device.

If you install magisk it will be gone.
[Android General] Lovetz:
No. I see this message every boot. I have magisk and props module in it for pass safetynet test. Only one difference in this message - if you choose another fingerprint you will see another end of this message.
[Android General] aingerunn:
Nothing. I've done format data. Restart and when I try to enter settings it locks and restarts.

I've installed it 10 times and always the same error.

I don't know what can be, I'm sure it's a system error. The strange thing is that it only happens to me.
[Android General] heineken78:
You have to install v3.3 before. I think there is updated keymaster, used in my Lineage
[Android General] aingerunn:
Solved. I installed the 3.4 and the Lineage 15. It's not blocking anymore.

Two days has cost me to install.........
[Android General] heineken78:
So tell me all bugs. I need to finish linage 15.1, then you will have sources and SAt versioni go for Lineage 16 for ss2 and after i will present my s2 and have my nokia x6 for experiments.

Pls do it fast :)
[Android General] aingerunn:
I try it in two days and answer the mistakes I see
[Android General] heineken78:
Congratulations s2 user. sharp-mobile.tw is no more.

Another foxconn device branded as fake "sharp" is no more, same as Infocus in past and Nokia in closest future.

Foxconn made always uniek and very good hardware smartphones but never. never give a support or care of good marketing.

I think they do it just for phun :)

They are producing own smartphones for free on account of Apple that pays for Iphones. On same factorys in same room with Iphones…

If you keep it for few years it will remain in price, believe me!

I like them and troll them few years. Foxconn really has to share investments for something useful, not for wasting for one year brands...
[Android General] aquos11:
Hello, heineken, it's good to see you back. :) Very happy.

I've got the 1.1 but I've just installed it so I can't say that much.

But the first thing I thought I'm gonna miss is just a detail, but... the rounded corners at the top. It's was a great solution in 3.3. But accidentally I found it in settings - it works very good!

The main problem --> bluetooth headphones :( The phone is connecting via NFC and via bluetooth but the sound goes through the loudspeaker. I'm trying different options but still nothing. Love my headphones so it is unacceptable to me sadly. :(

I've got some problems with mobile (the same error as ndestin had) and with bank and NFC - have to install Magisk but I've got some failure so I needed to install it via TWRP (so I needed to restore wiped copy of data again) - now it seems to work but I'll see when it comes to pay.

And the fingerprint reader - I used to use it instead of navigation bar and here is this option too but it dosen't work the same as in 3.3 - long press - back to the main screen, short press - just back and move to right - see the preview. Not to complain but it would be great to see this again.

I' afraid of the battery - hope the optimalisation is as good as in 3.3.

And also - I miss button for cleaning the memory in the preview - in 3.3 there was a button at the screen centrally at the bottom - now I need to click at the button 'clean everything' at the top right.

For more gonna test it.

Thanks a lot for your work!

And the question at the and - the version 16 will be based on Pie? :)

Greeteings!
[Android General] heineken78:
When i finish 15.1 with no bug, pleasure present with lineage 16.0 will wait for you.
[Android General] aquos11:
You are a great man, you really are. :)

Sorry for urging you but how about the bluetooth sound? You think there is a need for some fix or need to wait for upgrade? Couse on the second case sadly I would need to come back to 3.3 sadly. But for now this ROM seems to be very good, pretty and fast. Thank again! :)

---------- Post added at 12:23 AM ---------- Previous post was at 12:04 AM ----------

And one more thing - the louspeaker seems to crepitate a little. Just like in AOSP firmware. Doesn't sound that worst but it's not as good as in 3.3. But the bluetooth is still the sadest to me. :(
[Android General] semka_tyt:
There is a patch Lovetz spread on 4PDA forum.
[Android General] aquos11:
Hi, thank you very much. I sent you a PM.

Sadly I need to say that it doesn't work.

I downloaded this patch, copied it via TWRP to this location: /ventor/lib64 but still nothing.

I thought maybe /etc in the main folder but it also doesn't bring any effect.

The phone is connecting with headphones but the sound is going through the loudspeaker.

I couldn't even replace this file cause there was no file named like this one so I just pasted it there.

EDIT: when I'm trying with ADB, I receive an error:

remote couldn't create file: Read-only file system

:(
[Android General] aquos11:
I've got also some problem with mobile data. When I'm turning on my phone I see the same communicate as [MENTION=2969196]indestin[/MENTION] did.

I downloaded this patch, copied it to this location: /ventor/lib64 but also still nothing.

I can make a call/ read a message but sometimes I can't send a message - sending ends with failure.

[MENTION=1611492]heineken78[/MENTION]

What else I see in this ROM:

1) Baterry discharges quickly in comparation with 3.3. After 7h in the night just 2% so it's acceptable but in standby mode it seems to be worse - today's morning 1% in every 15-20 minutes. :(

2) What about autocomplete by Google? It's the question of ROM or Google services? In 3.3 it was working really nice, here it doesn't work at all.

Thank you all & greetings. :)
[Android General] Lovetz:
New audio fix for Lineage from [MENTION=1611492]heineken78[/MENTION], now all works as it should be.

Unzip and copy to /vendor/etc/ over previous version.
[Android General] aquos11:
Thanks a lot. Is this the same one that you have published on 4PDA? The one. XML? Cause I have no file named like this one in this folder so I have nothing to repalce. Even after reinstalation. And after paste I don't see any difference. Still music goes through speaker no mather which headphones is connected. Greetings to all.
[Android General] Lovetz:
I published it at 4pda today. This is new version. It can not be that you do not have this file, it is impossible. Look at the picture. Use the correct program with root access to replace the file, or a file explorer in the TWRP with the mandatory subsequent setting of access rights (0644).
[Android General] aquos11:
Hi. Thank you.

I check it when I'll be back home. I've tried to do this via TWRP but there was really no file like this to repalce.

What program to copy this file can you recommend?

Thanks again.
[Android General] Lovetz:
You can use any file manager with root access. For example, SolidExplorer (as on my screenshoot).
[Android General] aingerunn:
I see the file. And it's already replaced. Thank you [MENTION=461614]Lovetz[/MENTION]

---------- Post added at 02:54 PM ---------- Previous post was at 02:47 PM ----------

[MENTION=1611492]heineken78[/MENTION] and those who have installed the Rom 1.1.

When you restart the Sharp consumes 15% of battery and makes some strange noises. It's happened to Me twice.

It's the only thing I can report as (annoying) without being a mistake. That you haven't reported before.

I think a magnificent Rom, could be the definitive, even if it is Lineage 15. The same is lacking details of greater configuration, like the colors in the quick accesses
[Android General] aquos11:
Thank you very much, [MENTION=461614]Lovetz[/MENTION]!

You and [MENTION=1611492]heineken78[/MENTION] are my masters! :D

I found the file through this file manager. It's odd to me that it wasnt visible to any other software.

I had to restart the phone also to see the result.

And the LDAC... here... on this phone! ;) Very happy, really.

But the patch with mobile data - I've replaced the original file but still nothing - I have no problems with network since the beginning but after restart I constantly see this annoying communicate so there is something wrong with this fix.
[MENTION=1611492]heineken78[/MENTION] after few days I can state that the baterry optimalisation is really poor in this ROM. Don't really know why because in 3.3 it was great, much better then in stock ROM. In the meantime I returned the new Asus Zenfone 5Z just because the baterry was totally poor and it wasn't only my problem. (btw Asus approach is unnaceptable in this case).

After charging-up to 100% -> 30 min music via wired headphones, about 20 min attempts with these patches --> 85%. :(

And what else can I say - I miss the face ID from 3.3. Not sure if this is too much for you to implement this solution here but that was something very useful to me.

Summarizing, great job! Really nice, customisable and pretty ROM. But needs some improvement.

Thank you! Not coming back to 3.3 now. :)
[Android General] Lovetz:
Fix for freezing and random closing of application issues for Lineage 15.1 from [MENTION=1611492]heineken78[/MENTION].

The solution was found by the [MENTION=1611492]heineken78[/MENTION].

You must edit /vendor/build.prop

Search for dalvik.vm.heapsize=36m, then replace 36 with 256, save file and reboot.
[Android General] aquos11:
[MENTION=1611492]heineken78[/MENTION] I need to state, that the battery is discharging too fast when the bluetooth is on. Not sure if it's just me but 30 minutes music on my wiredless headphones and 10% is gone just like that. :confused: With mobile data (not LTE just 3G) is the same in camparation to 3.3. And one more thing I really miss but don't know if this is possible to return from 3.3 - double-click on fingerprint sensor to turn the screen off. Just like double-click on home button right now. Greetings!
[Android General] heineken78:
I think using of Aptex codec making such a big Bluetooth drain.

Also if using of latest fix for bt audio, posted by Lovetz.

New update will include many new hardware addons( screen and vibration). Maximum ever made for qcom hardware in kernel and Lineage!

My test S2 got more than 7 hours screen on time test in Pcmark.. so who tells it has low screen time - lies =D
[Android General] aquos11:
Can't wait. :) Especially that current realese is pretty good. :)

This ROM brought a new life into this phone.

Well it could be that the audio codec is guilty here. I use LDAC. Anyway it seems weird to me, 10% in 30 min.

BTW this patch from [MENTION=461614]Lovetz[/MENTION] solved the problem with the loudspeaker - now it sound same as in 3.3.

Thank you all.

Greetings! ;)
[Android General] aquos11:
Correct - the sound from loudspeaker is still poor, not like in 3.3. When I had AOSP the problem was the same.
[Android General] Alex27lara:
Hopefully also solutions the Notch error that looks pretty faith
[Android General] aingerunn:
Problem? I don't see any problem. The status bar is smaller to have more screen. It's how I like it. I don't want it to change
[Android General] tj65:
Hello everybody.

I have a Sharp aquos s2 and want to customize the fingerprint gestures. For now i know, that i can customize single tap, double tap and long tap. But i not found any solution to customize swipe left and swipe right separately. The only Option is one action for swiping. I also have a ZUK Z2 Pro which offers this options. On my ZUK Z2 Pro i have "back" for single tap, "recent apps" for double tap, "force close APP" for long press, "homescreen" for swipe right and "turn screen off" for swipe left. I'm very happy with this configuration and want this on the aquos s2.

Is there any solution?
[Android General] aquos11:
There was a combination similar to this one in 3.3. I mentioned this earlier so we need to wait for heineken and see if this is possible to aplicate here. :)
[Android General] heineken78:
Hi, open vendor/usr/keylayout/uinput-fpc.kl

there is information

#KEY_LEFT SWIPE

key 103 BACK

#KEY_RIGHT SWIPE

key 106 BACK

#FPC_NAV_EVENT_SINGLE_CLICK, BTN_A, 0x130(304)

key 304 HOME

#FPC_NAV_EVENT_HOLD_CLICK, BTN_B, 0x131(305)

key 305 APP_SWITCH

#FPC_NAV_EVENT_DOUBLE_CLICK, BTN_C, 0x132(306)

key 306 POWER
[Android General] NeBlackCat:
"fastboot boot <any twrp image>" doesn't work (general problem)

Hi all.

This is one for the experts, I think (well, more expert than me anyway :confused:).

My SS2 is completely stock (global Oreo), unrooted, unlocked, nothing obviously wrong with it. I need to urgently install Magisk so I can use Google Pay. So I want to boot it into TWRP without flashing, as I've previously done with other phones, using fastboot boot recovery.img. I'd rather not risk flashing TWRP versions that I'm not 100% sure about.

But I can't get it to work, with any available TWRP image. Fastboot says it's successfully downloaded the image and rebooted, but the phone just reboots into the Android system as normal, not TWRP. However it is booting the downloaded kernel (so says Settings -> About Phone), but that isn't in turn starting the downloaded TWRP.

A bit of googling finds this problem on some other phones, after some change in stock firmware, which now reportedly requires an appropriate kernel command line to be supplied in the fastboot boot command.

For example, a Nexus 4 user reports having to use: fastboot -c "lge.kcal=0|0|0|x" boot recovery.img after an OTA update, to make it work. Which seems weird to me as (as far as I can tell) that's just setting screen colours.

Does anyone know about this, and know what kernel command line I should use? I've guessed a few things, with no luck. Also, could someone also please point me to a TWRP image that's

guaranteed

compatible with the above stock SS2 configuration? I can't seem to find one any more.

Suggestions would be greatly appreciated.
[Android General] heineken78:
In new devices there is no recovery image.

Boot image has ramdisk of recovery, so if you if make fastboot boot image it will boot system normally.

You have to flash boot and enter recovery mode. Only the way. Cheers.
[Android General] paulzie:
Is there a way to restore the Oreo ROM and lock the bootloader so the SS2 is as if factory delivered with the updated Oreo ROM?
[Android General] Psyl0w:
I successfully booted AndroPlus TWRP with the following command line (see my post page 152):

fastboot boot twrp-ss2-20180501.img -c "rootwait ro init=/init root=/dev/mmcblk0p79"

My phone was unlocked
[Android General] NeBlackCat:
Can you explain that in baby steps? If you could explain exactly what partitions there are, what's in them, and how the phone boots (subject to keys being held down or not) it would be really helpful. I'm guessing you're one of the few people that actually know, and that the Aquos S2 is considerably different from any other Android phone I've had (all of which have dedicated, standalone recovery partitions with their own kernels etc because, well, that's the whole point of disaster recovery when the normal system might be f*d up).

---------- Post added at 06:35 PM ---------- Previous post was at 05:49 PM ----------

I can boot that too (2080WW), with the caveats:

1) the message "the dm-verity is not started in restart mode. Wait 3 seconds before proceeding" appear as the system reboots.

2) not much seems to work. For example, none of the partitions shown by the "Mount" button can be selected, and Backup doesn't allow you to choose any partitions or Internal Storage / MicroSD / USB-OTG (all show as 0MB).
[Android General] olenomena:
You can find names for the partitions by locating a directory under /dev containing symlinks. This is how I found mine using "adb shell" (yours might differ in name but should still be present):

HH1:/ $ find /dev -type d -name by-name
/dev/block/platform/soc/c0c4000.sdhci/by-name
HH1:/ $ ls -l /dev/block/platform/soc/c0c4000.sdhci/by-name
total 0
lrwxrwxrwx 1 root root 21 1970-10-16 19:55 abl_a -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1970-10-16 19:55 abl_b -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 1970-10-16 19:55 apdp -> /dev/block/mmcblk0p64
lrwxrwxrwx 1 root root 21 1970-10-16 19:55 bluetooth_a -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 1970-10-16 19:55 bluetooth_b -> /dev/block/mmcblk0p34
[snip]

You could also do the same in Termux or similar on the device itself.

HTH
[Android General] paulzie:
Anyone have the stock 7.0 firmware for the SAT S2? Filename might be SAT-135F-0-00WW-B01-update.zip . It's hard to find since Sharp Taiwan links no longer work.
[Android General] Lovetz:
https://xdaforums.com/android/general/sharp-aquos-s2-ss2-sat-thread-t3761071/post78893818
[Android General] paulzie:
[MENTION=8164902]petrOza[/MENTION]vodsk , there are only SS2 firmwares at that paidu.com repository. Am after the SAT firmwares. Anybody have them? Need to downgrade to resolve a 0xc6da error when trying to OST flash newer firmwares. Seems I'm stuck on a 8.0 CN firmware. Arhh!!
[Android General] Lovetz:
https://yadi.sk/d/6Tz4ed8-x1TwuQ
[Android General] paulzie:
Update! FIXED.

Just had to unlock again as per instructions on opening post "BOOTLOADER UNLOCK [MENTION=1494032]ss2[/MENTION]/SAT Bootloader unlock (if you have unlockcode.bin) ". Then could use OST to write Heineken's V3 trebled ROM.

----------

Have unlocked a SAT S2 but cannot use OST. Getting an error 0xc6da. Notice the 'Device critical unlocked" is false.

C:\ost\SUT>fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) [B]Device critical unlocked: false[/B]
(bootloader) Charger screen enabled: true
OKAY [ -0.000s]
finished. total time: -0.000s

C:\ost\SUT>fastboot-android.exe flashing unlock_critical
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s

S3 mini owner here managed to fix this by switching into EDL mode and modified deviceinfo.img.

Have made an EDL cable (wire USB D+ & GND) but haven't managed to get the EDL mode showing in WIndows under ports. Can anybody advise how to do it?

Read OP Oreo doesn't support EDL mode boot. Looks like need to open the unit up to force EDL mode.
[Android General] czarodziej:
Does heineken78s lineage support disabling each simcard separately as in 2040?
[Android General] Lovetz:
I think, yes. Look at the screenshot.
[Android General] paulzie:
[MENTION=416161]heineken[/MENTION], I installed flashSS2-SAT-portS3-1380-system-cda.zip over trebled V3.1 on a SAT phone. It introduces a problem with the camera - torch is greyed out, camera doesn't work nor does flash. I revert back to V3.1 and it all works OK.

Any chance of a fix for this camera issue on the SAT phone?
[Android General] tj65:
I don't want to install Android Pie and i tried to install all available a/b oreo treble roms. The best rom for me is AOKP, because it is clean, without gapps and it have a lot of options, like disable navigation bar and long press kill app.

I really want long press fingerprint button to force close app. In developer options is an option for that. But it only works with the back button from the navigation bar.

My settings for fingerprint gestures are now like i want it. I noticed, that my Zuk Z2 Pro recognize the single tap much faster than the aquos. I also tried stock roms. It's always very slow. My settings for uinput-fpc.kl are:

#KEY_LEFT_SWIPE

key 103 POWER

#KEY_RIGHT_SWIPE

key 108 HOME

#KEY_UP_SWIPE

#key 105 HOME

#KEY_DOWN_SWIPE

#key 106 HOME

#FPC_NAV_EVENT_SINGLE_CLICK, BTN_A, 0x130(304)

key 304 BACK

#FPC_NAV_EVENT_HOLD_CLICK, BTN_B, 0x131(305)

key 305 BACK

#FPC_NAV_EVENT_DOUBLE_CLICK, BTN_C, 0x132(306)

key 306 APP_SWITCH

I don't want to install Xposed and GravityBox, because i want a simple and clean system. Is there any option to enable the long press kill app feature with fingerprint reader? I really don't want to use the navigation bar, because in my opinion that bar is a waste of screen space.
[Android General] paulzie:
Can you, or anybody else, please re-host the SS2 Android 8.0 update? The Taiwan Sharp server that everyone links is down and the about pan.baidu.com link wants to save the download to a network share which is dependent on a login, which requires what appears to be a Chinese phone number for verification.

Any help getting this file is appreciated:

SS2-2080-0-00WW-B02-135F-0-00WW-B01-update.zip
[Android General] Lovetz:
https://yadi.sk/d/ruIbJOK-bnKrBw
[Android General] NeBlackCat:
I'm on the stock global Oreo (SS2), with TWRP and Magisk (18.1) flashed.

But I need to remove Magisk, to see if it's the reason why I can't enable NFC in Settings.

However if I remove Magisk the phone boots into TWRP, never the system, 100% of the time. If I reinstall Magisk again, it boots into the system as normal.

Any ideas?
[Android General] heineken78:
Sharp Aquos S2 kernel

SS2 kernel sources ver.4.4.153 (Android 9.0)

________________________________

https://github.com/Eddie07/kernel_sharp_aquos_s2/tree/Android-9.0

Enjoy!