yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
I'm enjoying this rom! I have a question about Autoplay when plugging into USB on a Windows 10 laptop. I have Autoplay set to ask me what to do every time. When I select Default USB Configuration of PTP, Windows asks what I want, and I choose 'Open device to choose files'. Then File Explorer shows the internal storage of PH-1. This is what I expect. But when I select File Transfer instead of PTP, Windows does not ask me what I want to do. It immediately brings up the Microsoft Photos app and displays "Looking for new photos and videos". And File Explorer does not show the internal storage. I'd like it to ask me what I do.

I have several other devices, and this is the only one with this behavior.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Oh okay, it is still unclear to me how you came up with such a (confusing) acronym to simply say "stock ROM", but it doesn't matter.

To avoid any issues, you should flash my ROM on top of either the latest stock, or official LineageOS (which includes the required modem firmware, etc.). So if you've had problems with flashing stock or whatever, and should you decide to reflash my ROM, I suggest flashing an official nightly of LineageOS 19.1 in both slots, and then my ROM on top of it (in just one slot, then boot that slot. The other slot will be overwritten by the first OTA update you'll perform).

So basically PTP is detected as MTP (file transfer mode) by the computer, and vice versa? Weird. I never use Windows, but I can try this.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
I didn't state it clearly enough. There are really 2 parts to this. One is that Windows has options for Autoplay. I can tell it to do one of several things when connecting the USB cable, like take no action, ask me every time, import photos, open device to choose files, and a couple other things.

If I tell Windows to ask me every time, It works properly for PTP, i.e. it asks me, I pick open device, and File Explorer does show internal memory with only folders DCIM and Pictures. That makes sense for PTP. But for File Transfer, even though I told it to ask me, it does not ask...it automatically brings up the Photos app, as if it though I had told Windows to import photos.

But if I don't tell Windows ask me every time and tell it to open device to choose files for both PTP and File Transfer, it does that for PTP (and again File Explorer shows DCIM and Pictures). But for File Transfer, it does the same as before, i.e. it brings up the Photos app.

So it's not exactly doing what you said about vice versa. PTP is good, no matter whether I tell Windows to ask me or to open device. But File Transfer overrides whatever I tell Windows to do and assumes import photos.

Sorry to be so wordy, but I hope that helps you. Not sure how you'll figure it out without Windows!
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
More clarity is always good, thank you. I have Windows, so I can try, it's just that I normally never use it. I'll let you know!
[Essential Phone ROMs, Kernels, Recoveries, & Other] Port r:
the stock roms that i downloaded were labled bts and back to stock. maybe those rom version had problems or something, which give me issues sometimes on installng custom roms maybe i donon.

i was about to reinstall stock rom and try to ota update to latest stock if the ota still worked or search for more for stock on the internet but if flashing latest lineageos works then good, thanks. i'm about to flash it again. i wanted to extract the boot.img for patching with magisk and somehow got the redboot and after flashing the redboot patch i cant get out of bootloop. so no choice but to reflash everything.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Hi, I think I can reproduce this. The problem is that in AutoPlay's settings (reachable by opening the Start Menu, typing AutoPlay and choosing the first search result), each time you plug the PH-1 in (with File transfer, i.e. MTP, selected as the default USB configuration), a new PH-1 entry is created with the default action set to Open in file manager, so even if you change it, the next time you plug the phone in, it is detected as a different device, and the your previous choice is not honored.

You said other devices do not suffer from this issue. What are these devices? Bonus points if any of them is running Lineage, it'd really help me fix this.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
Apologies, Tomoms. I think I have us on a wild goose chase because of duplicate entries in autoplay, as you mentioned.

The devices that were working are 2 Leeco Le Pro 3 devices. They both have Aicp Android 11 on them.

Strangely enough, in autoplay, I have 5 entries for Essential Phone MTP and 2 for PH-1. (Before long, I'm going to go to the registry and get rid of some of them as suggested in some forums. But I'm not doing that yet).

When I read your post now, I went to the autoplay settings and told it to reset them all. So now, it asked me each time what I wanted to do, and if I selected open device to view files, it did that. And if I change all 7 of those to specifically say open device to view files, that works also.

So it was my fault for not looking further into those autoplay entries. The same problem may happen again if it keeps creating more entries. But at least I have it doing the right thing now. Thank you, and again, apologies.
[Essential Phone ROMs, Kernels, Recoveries, & Other] jionny:
My apologies first. Might as well say I am new to this since I have not done anything to this phone since 2019. It is unlocked and rooted. How do I install this ROM? I didn't see the installation procedure. It was probably right in front of me but I did not see it. Can someone please point me in the right direction. Thank you
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Hi, my fault, I've never explicitly specified it in the first post of the thread: since my ROM is simply an unofficial flavour of LineageOS, Lineage's official installation instructions apply. https://wiki.lineageos.org/devices/mata/install

Simply, you use my builds (available here) and my recovery image (available here, you can pick the most recent one, even though it doesn't match the date of the build you're flashing) instead of the official ones :)

Everything else stays the same (including the recommended Gapps package)
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
Since we're on the subject, I've been sideloading TWRP after every ROM flash so as not to lose the custom recovery (TWRP installs itself on both slots), then rebooting into TWRP (after selecting the other slot) to sideload Magisk. Did I explain myself? 😁

With the lineage recovery, is all this still required? Is just sideloading the ROM enough? Need to sideload Magisk all the time as well? Need to change slots?
[Essential Phone ROMs, Kernels, Recoveries, & Other] jionny:
Thanks!!
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Before I reply, since we're on the subject :) I think that in the past I promised I would develop a brand new, properly working TWRP for the PH-1. That's not going to happen. TWRP's code is a mess and I have already fought enough against it. I won't touch it ever again.

1. If you use Lineage recovery to sideload my new updates, from within the recovery you need to reboot again to recovery after flashing a new build (if an update has just been installed, slots will be switched automatically when you reboot again to recovery), and then sideload Magisk.

2. If you use the OTA updater to update to newer builds, you must to use the Magisk app to install Magisk to the inactive slot (there is a dedicated option for this), and then reboot (slots will be switched automatically).

Note that since the recent release of Magisk v26.x, flashing Magisk from the recovery is not enough to install it. So if you depend on modules that must be always loaded on boot, to avoid glitches and other problems (e.g. I have installed MicroG as a Magisk module), you either have to use method #2, or you have to use method #1 but flashing Magisk v25.2 via the recovery, instead of the latest version, and then update later through the app.
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
No sweat about dropping TWRP.

As to #2, when does one install Magisk to the inactive slot? Just before the OTA?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Immediately after the updater finishes installing the update. Instead of rebooting right away, you open Magisk and install it to the inactive slot first.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Just leaving a quick note to say that the 360 cam has been broken in the last few builds, but the next one, which will be released as soon as May's security patches are published, will finally fix not only this issue, but all the other issues of Klik's that were left to fix!
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Hi, a new build is available, with May's security patches and, *drumroll*... Fixes for all of Klik's issues! Everything is working now, including the 360 cam, and there are no more crashes when switching to B&W mode or to the front cam.
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
#2 worked perfectly. Thanks 👍🏻
[Essential Phone ROMs, Kernels, Recoveries, & Other] LineArc:
Is it only me or is it a rom error. I can't get audio in Whatsapp and messenger (the audio isn't recorded at all). Need solution please
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
This post is of interest for everybody

.

Sorry, this is my fault. I forgot to mention that in my latest build, I've modified the audio configuration of the device, to bring it closer to the stock ROM's. This is intended to fix the speakerphone issues some people were still facing, and it indeed fixes some speakerphone/video calling use cases, but unfortunately breaks mic input in some other scenarios. I've included these modifications because I estimated that the number of use cases they fix is greater than that of the use cases they break.

You can easily revert the modifications by yourself. Just enable USB debugging and debugging with root access in the Developer options, then download & unpack this archive: https://mega.nz/file/AtMAFYJb#b_0ttoLO6h2ZyxiIsXA70AaD6LnP1Vs6dMyy9bIgjf0

Then run the following commands:

adb root
adb remount
adb push mixer_paths_tasha.xml /vendor/etc/
adb shell sed -i "s/fluencetype=fluencepro/fluencetype=fluence/" /vendor/build.prop

You'll want to copy-paste them and not type them by yourself, to avoid making mistakes.

Mind that you do not need to be rooted, you just have to enable the "deugging with root access" option in the Developer options.

Then reboot, and the audio situation should revert back to that of my previous build.

I apologize again for the inconvenience! Eventually I'll find a final fix that addresses all issues at once...
[Essential Phone ROMs, Kernels, Recoveries, & Other] LineArc:
Will

Try tomorrow and let you know of the results.
[Essential Phone ROMs, Kernels, Recoveries, & Other] LineArc:
it is not working for me at all, need your help.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Hi, I've released a new build, since there's some interesting stuff to try and June's security patches are likely to become available later than usual, because of the QPR3 release from Google.

This build brings the Charging Control HAL, that is a new LineageOS feature still under development. You can use it to limit charging to a given percentage, in order to protect your battery, and have the phone stop charging at that percentage. Then, the battery will start to discharge even if you keep the phone plugged in, and it'll resume charging after the battery level has dropped by 10% below the charging limit you set. Other available options include smart, gradual charging overnight up to 100% based on the alarm's time, and a fully automatic option that will give you a percentage of 100% at 6 AM, IIRC.

Some of the default AOSP apps have been converted to Material You and/or Monet colors, although this still needs a bit of polishing: Messages' and Contacts' top bar coloring doesn't match the status bar tint they set, while Calculator and Dialer look ok (even though the same problem occurs in Dialer in the screen that is shown during a phone call). Gallery looks ok too, although its accent color is slightly too bright wrt the aforementioned apps' accent color. I wouldn't say any of these apps looks ugly, but there's still room for improvement and polishing.

This build also supports Contacts Scopes, from GrapheneOS.

@LineArc in what exact scenario(s) are you facing mic issues? WhatsApp voice message recording/call with and/or without speakerphone/videocall?
[Essential Phone ROMs, Kernels, Recoveries, & Other] LineArc:
whatsapp audio messages and calls

instagram audio messages and calls
[Essential Phone ROMs, Kernels, Recoveries, & Other] LineArc:
tried your latest build but still no sound in whatsapp messages
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
@LineArc

The microphone in WhatsApp audio messages works perfectly for me. Can you provide a log? If possible, use ADB and avoid the various logcat apps, since they often format the log in ways that make it hard to read for me.

Run adb logcat -b all -c, reporduce the problem by sendig a WhatsApp vouce message, and then run adb logcat > whatsapp_audio_message.txt and send me the text file. Bonus points if you repeat the procedure for the other scenarios in which you face issues, the more logs I have, the better I understand the nature of the problem.
[Essential Phone ROMs, Kernels, Recoveries, & Other] LineArc:
hope the log I have provided is of any help.
[Essential Phone ROMs, Kernels, Recoveries, & Other] 0xBADDCAFE:
I have encountered multiple issues:

The game does not work: https://play.google.com/store/apps/details?id=com.YostarJP.BlueArchive or https://play.google.com/store/apps/details?id=com.nexon.bluearchive This app worked on the Stock ROM, but on the Official LineageOS, the screen does not display anything except for sound, and hangs on this ROM.

When connected for a certain period of time with scrcpy, the screen sometimes gets stuck. This issue did not occur on the Official LineageOS.

I understand that resolving these issues may be challenging due to their specific nature, but I wanted to report them.

Thank you for the development of this fantastic ROM.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
I try to do my best to fix all issues. I may or may not be able to fix yours. Logs for the second one you reported would be appreciated. Just let it get stuck and then grab a log.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Odd_Duck:
How after installing MicroG do I do the Below?

"If you have installed MinMicroG in system mode, open an ADB shell and run the npem command, then reboot. It should grant all the necessary permissions."
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Enable "USB debugging" and "Debugging with root access" in Developer options, connect the phone to your PC, open a command prompt window, type adb root and then adb shell npem.

Check the device as it might ask for permission to accept debugging commands from your computer. Grant the permission, of course.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Odd_Duck:
TY
[Essential Phone ROMs, Kernels, Recoveries, & Other] Odd_Duck:
Hey, wanted to say thanx again. My phone now accepts payments or lets me use my cc nfc,... ;)
[Essential Phone ROMs, Kernels, Recoveries, & Other] 0xBADDCAFE:
> Logs for the second one you reported would be appreciated. Just let it get stuck and then grab a log.

I Grabbed some logcat logs and put the marker `STUCK` for stuck timing in each log file.

> When connected for a certain period of time with scrcpy, the screen sometimes gets stuck. This issue did not occur on the Official LineageOS.

Regarding the previous information, I would like to add the following:

The screen that gets stuck is the scrcpy screen. The device's actual screen remains unstuck and responsive.

Running logcat concurrently also gets stuck at the same time.

Connecting logcat when the scrcpy screen is stuck sometimes causes the previously stuck screen to start moving again.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Thanks. If you have some time to perform an experiment (which involves clean flashing many times, unfortunately), you could roll back to previous builds of mine until you find the first one that is affected by this issue. Let me know if it's feasible for you.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
A new build is available, featuring Android 13 QPR3 and some visual polishing here and there.

The charging limiter now works in bypass mode: once the battery reaches the charging threshold, the phone starts drawing current directly from the charger, and the battery remains stable at the target state of charge.
[Essential Phone ROMs, Kernels, Recoveries, & Other] 0xBADDCAFE:
I can try to rollback but I don't know how long to detect which build has issue. I'll report if detect which build has issue. However, if it takes too long or if I'm unable to allocate time for it, I will also report that.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Hi, I've uploaded a new build, featuring July's security patches and a few other minor changes.

EDIT: the new build has been pulled due to an issue with the Updater. I'll re-release it soon.

EDIT 2: okay, all good now!
[Essential Phone ROMs, Kernels, Recoveries, & Other] mateusxd:
Im using june update and this New one dont show in updater
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Whoops, my fault! To fix this:

make sure the Updater is closed

enable USB debugging and "Debug with root access" in developer options;

connect the phone to your computer;

run the following two commands: adb root, adb shell setprop lineage.updater.uri https://raw.githubusercontent.com/Tomoms/OTA_Updates/t-mata/update.json

disable USB debugging and "Debug with root access".

You should then be able to see the new update.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mateusxd:
Thanks, it worked :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Hi, I've released a new build, with August's security patches and a new memory allocator which should both be faster and have a lower overhead than the one we were using previously.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mateusxd:
IToday I tryed install the update and got stuck in recovery
[Essential Phone ROMs, Kernels, Recoveries, & Other] mateusxd:
I coudnt install july update got this error:

I tryed flash clean install august update and got the same result :(
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Very strange. It works fine here. Make sure you can boot the previous build, which resides in the inactive slot. Switch to the inactive slot using fastboot (fastboot set_active other) or using the recovery (if you can access it). Did you install the update using the OTA updater?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Can you please check the integrity of the zip file you downloaded? The md5sm should be 0ca177734fc563caf2c711dfc1e9afeb, the sha1sum fd5088ed8f996f56f4fd58cadcbb923bc883f22e.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mateusxd:
i changed slots but it both are with august update, how can I roll back to july update?
[Essential Phone ROMs, Kernels, Recoveries, & Other] mateusxd:
md5 its same
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
I also had no problem installing. But I'm unusual in that I do it "manually" and with TWRP recovery. I don't think this is the way most people do it, but it makes sense for me. @Tomoms, thanks so much for your great work.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
I think you have to wipe data/factory reset again, and erase system from the bootloader using fastboot erase -w system, then switch slots, and run this command again (you must erase both system_a and system_b). Let me know if this works.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mateusxd:
I dont know what im doing wrong, but after doing this in both slots it still denny install the older build. I tried again install august build with mindthegapps, but freezes and restarts in the start configuration, then I realize that the bug is when the essential connects in mobile antenna, just after get signal from operator it restarts, i remove the simcard and its working now.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
How strange! But if you finally managed to set up your phone, please enable USB debugging, connect the phone to the PC and run "adb logcat > log.txt". While the command runs, without disconnecting the phone from the PC, pop out the SIM tray and insert the SIM in your phone (the PH-1 supports hot-swapping SIMs like this, while it is turned on). According to what you've observed, the OS should crash at this point. The adb command will automatically stop running and you'll have a log.txt file, please send it to me. Thanks.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mateusxd:
here
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
I'll look into it tomorrow. Sorry for the inconvenience. I hope we can fix this soon!
[Essential Phone ROMs, Kernels, Recoveries, & Other] mateusxd:
Thank you!
[Essential Phone ROMs, Kernels, Recoveries, & Other] EumeI:
Hi,

i tried updating via OTA update. After restarting the device i can enter my sim and device pin. Shortly after that, the devive will automatically shutdon (you can see the shutdown message). After the restart the device is booting into recovery. I can try a restart but this repeats the same process. Switching the slots via fastboot worked for me. If anyone need it:

1. Hold Power button and Volume down

2. When in bootloader connect the phone with your computer

3. Enter the following command in cmd: fastboot --set-active=a

4. Replace a or b with the slot which is currently not active (you can check that by entering fastboot getvar all)

I remain with a big thank you for maintaining this beautiful device :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Hi, since you've faced this problem as well, I will pull the update, fix the issue and release it again.

EDIT: yeah, I found what is needed to fix this issue! My bad guys, I apologize again...
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
@mateusxd @EumeI I've released a new update which should fix the issue. Please let me know. Thanks.
[Essential Phone ROMs, Kernels, Recoveries, & Other] EumeI:
Thank you very much for your effort. Now it worked as expected.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mateusxd:
Now its working! Thanks alot
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
I am trying out T-Mobile home internet 5G so that I could replace another internet service. With your rom, I am unable to connect to that gateway. I have several other Android devices, and they all connect successfully to it. An Ooma telephone device also connects easily.

I am wondering how to give you any more information to help debug this. I don't know if logcat would help. Let me know if you have heard any others mention this issue. I can't really be sure, but it looks like it tries for a few seconds. Then it reverts to connecting to the SSID of the router that I was using before. Thanks.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Please connect your phone to a computer and use adb to capture a logcat after trying to connect: adb logcat > log.txt

Then, if you have the time and will, flash official LineageOS 20 and try to see if the issue persists.