yashsingh1/xdaforums huggingface dataset:
[OnePlus 9 Pro] EtherealRemnant:
"This app allows for voice activation with supported voice assistants

Qualcomm Voice Assist provides always-on keyword detection for enabled voice assistants on your device.

It is always-on, low power, and functions even when your device's screen is off."

From the Play Store entry.
[Google Pixel 6 Pro] dilligaf56:
I recently bought a Pixel 6 Pro; after getting it all set up, I noticed that it frequently dropped the carrier signal even in strong signal-strength areas, sometimes requiring a reboot to get it back. Apparently the problem has been reported multiple times. Installing this package:

https://www.apkmirror.com/apk/googl...211206_01_rc00-android-apk-download/download/

has apparently fixed the issue on my phone. This is a BETA version of the Dec. 2021 version of the Carrier Services app. Interestingly, this one fixes the issue, but updating to the Jan 2022 release version breaks it again.

Hope this helps anyone else with this problem!
[Google Pixel 6 Pro] mightyvenom:
Thanks for your input! I am also one of the users with frequent data connection drops EVEN AFTER January update.

Unfortunately for me, updating to this latest Carrier Services Beta (and clearing its cache etc.) doesn't fix anything for me.

In case someone is interested and can have a look, I have managed to capture modem logs at the exact time (hh:mm) when the network drop is happening - see more info here.
[Google Pixel 6 Pro] Texan1:
Make sure you properly forward those to Google as a bug report too.
[Google Pixel 6 Pro] dilligaf56:
Addendum:

After several days, I have found another issue. With the beta version of the Carrier Services app, the phone does NOT ever drop the provider's carrier if Wi-FI is not turned on. If I do turn it on, after some random time period, the phone drops the carrier signal again, and I am NOT able to make Wi-Fi calls. If anyone has a fix for this it would be appreciated. For now, I'm just not using my wireless network... :-(
[Google Pixel 6 Pro] Deleted member 4371576:
'Apparently' is more precise than sometimes a fix works and sometimes it doesn't. Please retitle to maybe.
[Samsung Galaxy M12] ap4ss3rby:
I am deleting this guide since M12 will soon recieve an unofficial build of LineageOS 19.1. Don't ask when, as I'm not the lead developer but I helped with it
[Samsung Galaxy M12] ap4ss3rby:
Update 1: I figured out how to make script run on boot. Instructions revised. If you followed earlier check them again

Update 2: Magisk 24.1 is now stable. Instructions revised.

Update 3: I contacted phh and he implemented the script inside his trebleapp. Instructions revised and modified trebleapp is attached. NOTE: GSIs newer than 7/Feb/2022 will include this workaround by default.

Update 4: This guide is now unnecessary now that unofficial LineageOS is very close to release
[Samsung Galaxy M12] ap4ss3rby:
Amazing work. If you need testers feel free to PM me. As a sidenote, poking in sysfs led me to believe that android is sending the info needed to read the proximity but the kernel is sending garbage which gets interpreted as the sensor not being triggered. Also phh should have added the workaround into his trebleapp starting from phh AOSP 12 v401, so aside from installing magisk no post install workarounds should be needed.

Attached is a photo of what cmd_result reads when a whatsapp voice message is played which reads proximity to play the message in the earpiece and turn screen off when proximity is triggered
[Samsung Galaxy M12] SB3P:
Unfortunately, the commit was reverted as of master branch, so we should prepare for it to stop to work unless phh will work on it before releasing an another version. Also I wrote that the workaround didn't seem to apply itself before unlocking the phone (FBE encrypted) the first time and therefore decrypting sensitive data after boot. For now this makes it an requirement when using PHH app to unlock the phone before it sleeps so the touch is going to be responsive.

Anyway, it seems that even Magisk (v24.1) is not capable of running the services before data is decrypted, so now I have no idea how to bypass that in other way than patching the ROM itself and creating the `initrc` service... Anyway, this is also a hint that what samsung is doing starts before basically everything, so no APK file nor script is going to really fix it since they are meant to start after data is decrypted...
[Samsung Galaxy M12] ap4ss3rby:
I guess for now we have two options:

A: Build custom kernel/vendor specifically for GSIs that correctly reports sensors as GSIs expect them to

B: Fix GSI issues through Magisk services implementing various workarounds in scripts. (an example is the touchscreen sleep/wake issue)
[Samsung Galaxy M12] SB3P:
Also that's interesting those virtual sensors are still present, I personally thought that Samsung made it the way there's an virtual device create as on Linux and there's their proprietary software running somewhere in the system that uses the camera as an input and calculates it to provide the data... On the other hand, when I think about that logic, even some (if not all) virtual devices on Linux (e.g. v4l2loopback) needs to have their module loaded with the kernel to work. I'm glad at least there's no need to reinvent the wheel and no one really needs to recreate the entire algorithm for it if it's going to be in the kernel sources...

I feel like the B option is worse than patching the GSI ROMs, either via flashable ZIPs or on your own... This is because I couldn't find anything in docs that would let me run services before /data is going to be decrypted... Personally, I've made myself a such service using the statically-compiled Linux ARM binary (non-NDK, using GNU libs – yes, it is still runnable on Android as well) – it applies the workaround for now both when screen is turned on and off (I had no idea on which event it should really run, so I made it to run on both just to be safe) by watching the file changes based on (AFAIK) filesystem events – so it has a major advantage over your script, as it won't run in endless loop, yet watch the file responsible for brightness to change and then do its job. But even with that, TSP doesn't seem to make touch available immediately and it is still expected to be revived after 1-2 seconds.

Also, as of the methods of applying these workarounds, the other way could be modifying the ramdisk (maybe with the help of Magisk, which I believe has documented how it's actually doing it itself and how others could modify the root and init as Magisk does to load files before the OS will properly initalize itself. Yet I don't like an idea of messing myself with the boot partition, at least for now...
[Samsung Galaxy M12] ap4ss3rby:
Debug info: I tried flashing stock to grab logs from the touchscreen driver. The logs attached here do not appear at all on an unpatched GSI (I.E flashing the GSI as is without any touch workaround).
[Samsung Galaxy M12] physwizz:
Great guide.

Well done
[Samsung Galaxy M12] matahbeyz:
Thanks for the great guide. Unfortunately, I don't know how to resize tmpfs. Can anybody tell me how to do that? I only have 4 GB or less on my Samsung Galaxy A12 with 64 GB of Storage (it should have, it only shows something like 3 or 4 gigabytes like I mentioned)
[Samsung Galaxy M12] SB3P:
You don't have to resize TMPFS if you don't want to have FBE encryption or have the external SD card (you can use microSD for flashing, which might be a better choice if you need to flash a larger devices). Also you can't resize TMPFS to 64 GB, it uses your RAM to store regular data instead of storage (this is basically the concept of TMPFS). What I was mentioning is that /data won't work under FBE and custom recoveries for now, so you need to use your RAM instead if you don't have any external storage device to save images somewhere via ADB.

As of resizing the TMPFS, you should be able to find some Linux tutorial how to do that, on Android this is works basically the same (even on both Linux and Android you have /tmp directory with TMPFS by default).

Anyway, I've decided to share some stuff that you may need for that. Here's the multidisabler script I was using for flashing GSIs with FBE encryption preserved. I was also working on the native binary that would work as the workaround for the touchscreen so it can be used instead of the script. The advantages are that it actually listens to filesystem events and therefore does not need to read file in loop in order to get the information if brightness has changed. Maybe I'll share it with you once I find it to be ready, right now I'll just share my multidisabler script with patches.

BTW, I've tested LineageOS GSIs (both 11 and 12) and noticed they behave completely different, no matter of variant (the USB actually uses some driver, which is not fully compatible with M12 but close enough to provide basic communication through ADB). I guess pphusson just changed something and now these drivers aren't applied by default, yet I think I've noticed the issues with Bluetooth's HSP/HFP profiles which as I remember was not the case with latest stable pphusson's vanilla Android 12 GSIs. Now I just hope these problems are going to be resolved in the next builds of Android's GSIs with phhusson's patches and with the knowledge that MTP just worked fine on TWRP I used, there's a little hope that we will gain the proper combination of drivers/firmware to have both USB and Bluetooth functional at the same time someday.

I've also approached patching the kernel under newer kernel base 4.19.112, yet I gave up on properly resolving its conflicts. I may work on that as well in order to patch some vulnerabilities, with a hope that I'll succeed updating kernel as closest to the latest patch as possible. The 4.19.112 is going to be just a test if Samsung is capable of actually booting from it and if I may be able to use git with common human logic and my limited programming skills to actually patch it the way it would do so (without much understanding about the code itself, yet basic knowledge about C syntax). For now I've only succeed reproducing the upstream Linux kernel commit structure from 4.19.111, with a single additional commit for Samsung changes and another one for physwizz ones.
[Samsung Galaxy M12] milindbhaliwade:
can anyone guide me how to unlock bootloader on Samsung Galaxy M12G ?
[Samsung Galaxy M12] matahbeyz:
@SB3P Thanks so much. Sorry for my late reply, but thank you! :D
[Samsung Galaxy M12] milindbhaliwade:
Could you explain how you done this.... i mean please explain step by step... i am using Galaxy M12G Varient....thanks in advance
[Samsung Galaxy M12] SB3P:
If you would see the *untested* section at the initial post of this thread, it is unknown whetever this works or not for M127G phones (if it bootloops it might not work at all). Anyway, here's how I did it on M127F (at least how I remember this):

1. I did steps from 1-6, I believe I skipped 7 since I was aware it will mess something up with the data partition.

2. I modified the multidisabler script and pushed it to my phone via the ADB (to TMPFS). You can find this script pushed as xz compressed file. Before executing multidisabler script I have done a backup of the recovery and system partitions (using dd tool) which I am going to reflash later.

3. I rebooted to download mode and flashed TWRP image.

4. After TWRP ended flashing, I booted into the recovery. I flashed the physwizz kernel and then my own GSI image as it was described in the instructions at the initial post. Just remember that /data partition is not functional with FBE and TWRP so you need to push your images somewhere else like microSD card or TMPFS partition. OTG might work here as well, this is something I haven't tested yet through...

5. Once you are done with flashing you need to restore the original recovery partition via the download mode. TWRP won't boot the GSIs with FBE encryption enabled actually it does boot now for me, yet I still recommend switching to stock recovery if your phone bootloops or you need to format/wipe userdata partition. You can then safely format your /data partition with the stock recovery.
[Samsung Galaxy M12] milindbhaliwade:
try to install @phhusson (system-squeak-arm64-ab-vndklite-gapps-secure.img) GSI using above method on Samsung Galaxy M12G (SM-M127G) BUT failed to boot up

facing following issue:

1) unable to boot in OrangeFox Recovery

2) boot in TWRP Recovery but not detected MicroSD Card

3) samehow manage to push Kernal.zip, SystemGSI.img by adb push file_name_with_extension /sdcard BUT not flash properly as TWRP reboot again and again in 2-3 minutes

so friends, don't try this method on Samsung Galaxy M12G (SM-M127G) unless Senior member come up with this specific model
[Samsung Galaxy M12] ap4ss3rby:
For anyone who has starred this thread, I and other devs have released a proper build of LineageOS with /vendor. Aside from VoLTE (which I don't think worked in GSIs anyways) everything should work. Moderators, please close this thread
[Samsung Galaxy M12] SB3P:
LineageOS is not only GSI available, I think someone might still find it useful if they want to flash another ROMs. Also Phhuson's GSI also contains some features that unofficial GSI release don't have (i.e. flashlight control in Phhusson's app), so they still might be useful for someone.

This is why I think it is better to not close this thread and maybe revive original guide.
[Samsung Galaxy M12] ap4ss3rby:
Our rom is built completely from source, not a GSI, and it is more or less a complete replacement of stock firmware. If you want you can use a GSI over that instead, and it should function much better than just replacing stock firmware
[Samsung Galaxy M12] SB3P:
I haven't said GSI are better, I personally use this unofficial LineageOS build. But what I've said, GSI brings much more variety of picking the OS you can install. Even Linux can be installed on phones nowadays using GSI with only Halium-patched kernel as an requirement. This is why I think leaving this tutorial archived (no updates, interest on fixing bugs etc.) is better than removing it.
[Samsung Galaxy M12] M127G User:
Pls bring back the guide now even the lineageos is dead
[Miscellaneous Android Development] heineken78:
PREVIOUS VERSIONS:

https://xdaforums.com/t/lineage-17-1-unofficial-for-fih-sat-ss2-hh1-hh6-hd1-drg.3996951/

LEGAL

https://lineageos.org/legal/

You flash this ROM on own risk!

XDA:DevDB Information

Lineage 18.1 *UNOFFICIAL* for Sharp Aquos S2, S3 (SAT/SS2/HH1/HH6)

Multi ROM from sources supporting devices:

Sharp Aquos S2 4/64 -SS2/C10,

Sharp Aquos S2 6/128 -SAT,

Sharp Aquos S3 -sdm630 (HH1/HH6).

Sharp Aquos P6

Nokia x6 (DRG)

Contributors/Maintainers

heineken78

ROM OS Version: Android 11

ROM Kernel: 4.4

Recovery: TWRP 3.6.0 included.

Device sources: here

Gapps: Not included. Recommend to use only NANO version for normal functionality.

Data Encryption: encrypted;

Do not: use boot(twrp) or vendor with other older/stock roms.

Features:

-live display;

-lineage touch and mostly all hals available in Lineage support.

-adb root;

-safety net pass (with gapps installed);

-Google AR core support;

-Google Device Personalization Services;

Version Information

Status: Release

Created 2022-01-24

Last Updated 2022-01-24

Sources: https://github.com/Eddie07

DOWNLOAD:

GDRIVE FOLDER

Installation

1. First time

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.

2. Next updates/upgrades

Enter twrp and flash new images. If you had installed Gapps, flash same zip file o gapps. Reboot to system.

Pls note: Due to changes in encryption, if you migrate from 17.1 version you will have to format data to be able to use newer roms.

TWRP backup from 17.1 is NOT COMPATIBLE with encryption of 18.1.

Bugs:

-Network manual selection -You will find may be

Communication channel in Telegram (English):

te.me/lossharpus

Please donate if you want to support my work.
[Miscellaneous Android Development] heineken78:
reserved
[Miscellaneous Android Development] Psyl0w:
Thanks Heineken.

You should propose your services to FIH as you have done more to support that device than their dev teams for last years :)

Appreciate your work to maintain our sharp phones uptodate with rock stable firmwares
[Miscellaneous Android Development] eminoe:
Hi Heineken

Thanks for the new rom, I have upgraded with format data from your last 17.1 without problem.

With the 17.1 I had a bug the phone rebooted with a sony wh 1000 xmr3 now in 18.1 no problem :)

Since 2 days no problem battery life is good
[Miscellaneous Android Development] baszek:
Is it stable enough for daily use ?

@heineken78 you have wrote that:

LOS 18.1 almost on the way.

Its not so good as 17.1, but looks fine.

Could you please elaborate?

Do you recommend upgrade from 17.1 for daily use phone or I should still wait for newer 18.1 builds?
[Miscellaneous Android Development] heineken78:
Im using 18.1 on regular basis.

Its up to you what you gonna use.
[Miscellaneous Android Development] baszek:
Your linage 17.1 version is really good - I am using it for quite a long time. If 18.1 version is the same, I will install it right now ;-). I saw that 18.1 has only two builds on your G drive, so I thought it might have still lots of bugs.
[Miscellaneous Android Development] pelitox:
Hi Heineken!

First of all, thanks for an awesome rom! :)

I'm using it daily and i've found a few issues. The report:

-Flashlight is working, but camera apps can't use it in pictures (tried default one and google camera).

-Wired handsfree headphones behave erratic. If plugged in during a call, the call hangs. If previously plugged, sometimes work, sometimes don't. Tested with Panasonic and Xiaomi models.

-USB file transfer doesn't work.

Other than that seem actually great, tested WIFI, BT, GPS, sensors, etc everything fine. No LOS issues and very good performance.
[Miscellaneous Android Development] pelitox:
@heineken78

I'm still using it daily, but lately dialer app is troublesome (freezes) and i need to reboot to get it working again.

Is this rom still active, or no new versions are planned?

In any case, than you for an awesome job!
[Miscellaneous Android Development] heineken78:
Hi I dont have this bug. Which dialer are you using?

Please post logs from device after rebooting after freezing from sys/fs/pstore folder in your device.

Due the war I have moved to another city in my country, Im planning to go on with development from my notebook.
[Miscellaneous Android Development] pelitox:
OMG! I didn't know you're ukranian!

I feel dumb for asking about rom support.

Take care, best wishes :-)

About this bug, i think is related with previous message headset bug. I switched from wired to BT and this is not happening now.
[Miscellaneous Android Development] papapacho:
awesome rom!! thanks a lot
[Miscellaneous Android Development] 自由类者:
Take care. Hope there is no war in the world
[Miscellaneous Android Development] chocobear:
Hi, thanks for providing the lineage rom.

Sorry for the probably stupid question: I am unable to find a TWRP version for the aquos S3 and all the websites i found via google seemed very shady. (So far I only had phones for which TWRP was readily available)

I know it says included, but in the installation instructions it says to boot directly into TWRP? So i guess it has to be installed before?

Any hints where I could find one?
[Miscellaneous Android Development] Psyl0w:
There isn't anymore "war", there are "special operations"

Take the boot image from the Heineken LOS archives and flash or boot it. Recovery is actually in the boot image for A/B systems. You can find all inputs about flashing and booting TWRP in the other Heineken threads.
[Miscellaneous Android Development] chocobear:
Thanks, I'll have a look!
[Miscellaneous Android Development] baszek:
Does anyone know what type of battery I can use for sharp aquos S2 C10 ?

Can I use as a replacement HE332 battery ?

I saw that heineken was using some battery from Nokia, which can replace original battery

https://www.aliexpress.com/item/32995443415.html?spm=a2g0o.productlist.0.0.3504779cYDTxJY&algo_pvid=320056ae-8873-4644-89a2-4a30022fab10&algo_exp_id=320056ae-8873-4644-89a2-4a30022fab10-0&pdp_ext_f=%7B%22sku_id%22%3A%2266889130643%22%7D&pdp_npi=2%40dis%21USD%21%2113.47%21%21%21%21%21%402100bb5116577339026963577eafb4%2166889130643%21sea
[Miscellaneous Android Development] Psyl0w:
Yes HE332 battery is fine. Just check the quality of the battery as lot of failing products are sold on aliexpress.

Opening the phone is easy if you follow Heineken video. Be careful to not hang flex cables on the upper part of the device but the bottom side and around the battery is ok. (see attached pic)

Taking out the old battery is painful as the tape is very strong against tearing off.

Setting up the new battery is easy except the handling of the rubber tape.

I sealed the box with neoprene glue.
[Miscellaneous Android Development] baszek:
I thought that C10 version has got some different battery type. Do you think that this HE332 from alliexpress is legit ? According to AccuBattery right now my battery health is 75% = 2201 mAH
[Miscellaneous Android Development] Psyl0w:
C10 is the European flavor and the rated capacity is specified: 2900mAH

S2 sharp claims the typical capacity: 3000mAH but I think the battery is the same. You can open the housing if you want to check.

2200 mAH is still not bad. Mine was totally dead (cannot be charged). I bought from that seller https://www.aliexpress.com/item/400..._list.0.0.21ef5e5b3ROMbl&gatewayAdapt=glo2fra

I cannot assure it's an orignal battery but it powers my mobile for longer than 1 day.

The pic I posted previously shows the battery from that seller but keep in mind Chinese are very good to copy even the packaging
[Android Q&A, Help & Troubleshooting] Barabba11:
Hi! I've tried dozens of apps but all of them just show me the strengt of *my* operator signals. I need to see all the options around (3G/4G/LTE/5G) to choose the strongest operator for the next internet connection. I'm installing surveillance systems around, sometimes in a very complicated areas, so I need to know the best option available.

Thank you for help!
[Android Q&A, Help & Troubleshooting] Barabba11:
Any help? Thanks
[Introductions] Giuseppe1978:
I'm Giuseppe, and absolutely not tech-savvy like you, I'll be in the group trying to learn something from you.

Thanks again

Sono Giuseppe, e assolutamente poco esperto di tecnologia come voi, starò nel gruppo cercando di imparare qualcosa da voi.

Grazie ancora
[Introductions] blackhawk:
"I'm Giuseppe, and absolutely not tech-savvy like you, I'll be in the group trying to learn something from you.

Thanks again"

Welcome to XDA🤗

English only please...
[Introductions] galaxys:
Salute' Giuseppe! Enjoy the XDA forums!🙂
[General Questions and Answers] Ćwirek:
Hello.

I want to use WhatApp modified .apk with a lot cool features that you can't find within the original app (like themes etc) but I just can't deal with something - with backup restore.

GBWhatsApp, WhatsApp Plus, YoWhatsApp and many more - I just can't restore my chats even with the instructions given on different websites or YouTube tutorials. It simply doesn't work. Oh, and Dr Phone method, or something like that, was also tried without success.

Maybe some of you are using modified WhatsApp and knows how to restore backup from original app? Any help?

Phone and software:

Samsung Galaxy Z Flip3 5G running Android 12 (OneUI 4.0), not rooted.
[General Questions and Answers] bart4714:
Did you find a solution?