yashsingh1/xdaforums huggingface dataset:
[Touch Cruise General] mihaaa:
Hello all... got kind of a big problem that i at the moment don't have an answer to,..

inastalled advanced configuration tool 3.2 on HTC Polaris, the first crash i had was when I enabled animation for menus... (the start menu turned black and the polaris froze), but when i managed to start the advanced configuration tool i unchecked it and it was ok,...

the MAJOR PROBLEM accured when I set the touch screen sensitivity, because the touch part of the screen is inresponsive,.. meaning it does not work at all,.. tryed very hart pressing but it doesn't do it.. the problem is because i can't reach eg start menu or the lower 2 shortcuts with hard button cursor (the wheel)... gestures work however, so i can call the touch flo cube but am not able to select anything, and sam thing goes for enetering pin,.. so i'm not able to make phone calls at the moment.. did few hard resets, and uninstalled the adv. conf. tool but nothing helped... can anyone tel me where (and how to get there) can i adjust this back to normal, i wanted to do this in the advanced configuration tool 3.2 but the problem is you cant make any changes since the screen doesn't work,.. same with reinstalling the program, i can select to install it on a card but canot "click" on next since the screen doesn't do it and the hard keys "can't go there"

so

really really someone help me please

... :confused:

thnx
[Touch Cruise General] hambola:
Are you sure you hard reset and this problem went away or did you mean soft reset?

Maybe aligning the screen will help reset the pressure? Click the button in the middle of the wheel and the GPS button at the same time, the Windows align screen pops up. See if that helps.

I find it very hard to believe that you hard reset and the touch screen sensitivity is still not there. That can't be right.
[Touch Cruise General] mihaaa:
Hi,

thanx for the reply,... another problem that accoured afterwards was that my friend held the end button (wich locks the keys, screen) and the phone was additionally locked... and literally nothing (again NOTHING :D) helped, spent 5 hours trying to save the situation,.. i did soft reset (so your assumption was right) but when later tryed hard reset it probably wasn't done since the instructions say you do it with holding gps and iExplorer buttons while soft reseting it... this resulted in getting the "hard reset screen" wich says to confirm hard reset with hitting the send button, wich unfortunatelly i wasnt able to find in hard keys, and nothing else but this warning text was on the screen as well.. so in the end it probably ended upo wit soft resetting it, anyways it didn't help,... i decided to reinstall the rom i downloaded on htc official site,... it went thru ok and the phone is , though out of the box at least functional,... but in the end, i must admit that am a little surprised this happened with this tool pack (i actually avoided altering the registers just in order to avoid this kid of situations since i don't really know much about these things)... was expecting it to work (in my case) a bit better, more stable. All i wanted really was to get a bit louder speaker volume when ringing and ability to alter the HTC home toolbar, since i find the weather screen totaly irreliable and never really use it, so i thought I would have sth there that i might really have some use of..

well nevertheless.. the phone is working, that's all that matters at the mom so i can again start finishing my phd wich i am defending in a week :eek:

PS. the fact that you can not do practically anything without the touch screen just sucks big time, if i compare it to the mouse on pc,... i saved the situation many times with the keybord .. in 1 word strange :D

take care
[Touch Cruise General] gastonfama:
My Mobile

Perhaps you should have tryied out the "My Mobile" aplication that allows you to use your mobile from a PC.

It shows a windows with the mobile screen and you can touch it and use the mobile like if you was touching the REAL mobile...

Late for that solucion, perhaps another with that problem can solve it this way...

Chears
[Touch Cruise General] mihaaa:
@gastonfama: am not sure this would help, since a friend that has htc diamond has this tool pack on and it work k ok on his phone,.. that's why i predicted that it is going to be stable enough on mnie as well,.. so in my thinking, if the 2 htc that are rather alike had such different "reaction", than an emulation would be even less comparable to mine, thanks though
[Touch Cruise General] maka_szn:
Had the same problem with Schaps_AdvancedConfig and wrong HKEY_LOCAL_MACHINE\Drivers\TouchPanel\PressureThreshold setting.

XML I used had "200" as advised value (system default is 2908!),

after changing you could hit it with a hammer and nothing.

Managed to set is back to recommended value 9000 using MyMobiler app and all problems gone.

See also HKEY_LOCAL_MACHINE\Drivers\TouchPanel\PressureThreshold

sys default is 18866, I use now 19866 and I'm happy

Check tips&tricks thread
[Touch Cruise General] francosiu:
I got the same problem, I wanna to install "My Mobiler" but due to the screen is locked, I can't continue the installation, any help ? :(
[Touch Cruise General] mihaaa:
well as far as I see here (forgot how i installed it after previous post) you have an exe here :

http://www.mymobiler.com/downsafe.aspx

so you will install it from the pc anyways, but how will you make the confirm on where to install it (mybe if you put storage card out and there will be only 1 memory option, but you will still have to confirm installation i guess).. i wasnt able to confirm without the screen on polaris,.. maybo on some other phone
[Touch Cruise General] mihaaa:
double post...mistake
[Touch Cruise General] gatecrasher71:
I had that same screen not working problem after tweaking the phone with advanced config 3.3, 3.2, 3.1, only hardware buttons work.

Problem can only be solved by Hard Reset. Version 2.2 I think is the only one that works (not thoroughly tested though)
[Realme X7 Max 5G] bakshish007:
I've tried installing multiple versions of OnePlus launcher in this phone, but none of them works.

If anyone has a working one please share.....
[Touch Diamond, MDA Compact IV General] The Jones:
When I try and send a text but dont have any reception, the sending fails (obviously) and the message gets moved into the Drafts folder.

What I want is for the device to try resending the message automatically. Or when failing for the message to stay in the Outbox. Or something similar to that. The current behaviour is not the most useful.

Can anyone help?

Thanks!
[POCO M3 Pro / Redmi Note 10 / 10T 5G] william liu:
Hi guys i created my own splash screen for this device (Android one splash logo)

I got fastboot picture from this

https://xdaforums.com/t/splash-screen-boot-logo-amazing-splash-screen-for-mi-9.3997365/

To install Just do "fastboot flash logo logo.bin"

DONT USE IT ON LOCKED BOOTLOADER IT WILL CAUSE GLITCH
[POCO M3 Pro / Redmi Note 10 / 10T 5G] william liu:
I will upload the file to google drive
[POCO M3 Pro / Redmi Note 10 / 10T 5G] william liu:
https://drive.google.com/file/d/11Q9qyzU2AotrXK-GtSKEN-YnpQ3jWC4E/view?usp=drivesdk here the files just download it
[POCO M3 Pro / Redmi Note 10 / 10T 5G] 1miguelillo1:
Hi William Liu,

Can you make the splash screen black?
[POCO M3 Pro / Redmi Note 10 / 10T 5G] wetito:
Is more safe and Simply download themes from store with custom boot logos
[Touch Diamond, MDA Compact IV General] EvgeniyKo:
Halo? please copy phcanOverbmp.dll from your device (in Windows). It is file for icon status on top bar (GPRS & batary and some other) Please!!! :confused:
[Touch Diamond, MDA Compact IV General] chribruu:
Are you asking someone to post the file you are mentioning here ?
[Touch Diamond, MDA Compact IV General] EvgeniyKo:
Yas, I wish that someone who would be overlaid this file for download in the poste
[Touch Diamond, MDA Compact IV General] chribruu:
Here you go..
[Touch Diamond, MDA Compact IV General] EvgeniyKo:
Thenk you!!!
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
GSI baseline image for Essential Phone​

Android 12 updated in #3

As you know, from Android 9, there is a project called Project Treble with the aim to bring newer Android versions faster to the user. Together with the time movement, Google also introduces HIDL. It is a concept separating Android hardware and software.

Now, you also know, the Essential Phone PH-1 is on the list of supported devices in Project Treble. Unfortunately, this device requires specific storage mapping in the kernel so that it might not be able to use LineageOS as the baseline image.

In order to overcome this inconvenience, you must build a stock AOSP image and disable verity. It is somehow complicated for newbies. Therefore, I am here to make it easier for you.​

[Window only] Driver for Essential: https://drive.google.com/file/d/1ofTm8cprzuc0i4SWxMrdlrATB3JpSRR9/view?usp=sharing

Following step-by-step guidance here will make GSI work for you.

Step 1:

Download prebuild Stock AOSP build here.

Link: AOSP_11.zip

Step 2:

Extract the download file into a folder. It contains three different files: boot.img, system.img and vendor.img.

Step 3:

Boot your device into bootloader (fastboot mode) by holding Power and Volume Down at the same time.

Step 4:

Unlock bootloader (If you have done, skip this step)

fastboot flashing unlock
fastboot flashing unlock_critical

Step 5:

Flash the above images

fastboot flash boot_a boot.img
fastboot set_active a
fastboot flash vendor_a vendor.img
fastboot flash system_a system.img
fastboot format userdata
fastboot reboot

Step 6:

After reboot, connect your phone into computer and run the followings.

adb root
adb disable-verity
adb reboot bootloader

Step 7:

Download any GSI image you want. You can refer in this page.

I have tested with Google GSI Android 11 and DotOS.

If you want to try Google GSI, please use this link: https://developer.android.com/topic/generic-system-image/releases

Step 8:

Extract the downloaded file in step 7 into a folder. Make sure that you have the system image, whose size is more than 1GB.

Step 9:

Go to the above folder and run the following commands.

fastboot flash system_a system.img
fastboot format userdata
fastboot reboot

Step 10:

Now your device will boot new os. Congratulation!

Know issues:

Almost every thing works fine.

SELinux: Permissive

Kernel: https://github.com/EssentialPhone/linux

Device: https://github.com/EssentialPhone/device_essential_mata

If you love my work, buy me a coffee at:

Paypal: paypal.me/nguyenquangduc2000

Thank you so much!
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
Many thanks for supporters:

1. Botany Lane Pottery

2. Mariusz Stanczak
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
Android 12 GSI

Last updated: Feb. 10th 2022

The process of flashing Android 12 GSI is almost the same as the one of Android 11. But you need to replace some above steps with these following ones.

Step 1:

Download prebuild Stock AOSP here. [AOSP_Feb_10.zip]

...

Step 7:

Download your favorite Android 12 GSI rom. You can also refer here.

...

Step 10:

If your device boots up, you are lucky. Congratulation!

Know issues:

Almost stable

SELinux: Permissive

If you love my work, you can give me a hug at:

Paypal: paypal.me/nguyenquangduc2000

Thank you so much!
[Essential Phone ROMs, Kernels, Recoveries, & Other] svaethier:
the android 12 july beta gsi still works on the ph1 but i think this phone needs an updated kernel to support a12 going past that beta.
[Essential Phone ROMs, Kernels, Recoveries, & Other] death1246:
Quick and easy guide for all the new guys and the people getting back into it. So just a heads up. A OS 12 still does not have support but I can install a google maintained GSI version of android 11?
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
Yes, you can install any GSIs which based on Android 10 and Android 11.
[Essential Phone ROMs, Kernels, Recoveries, & Other] hedgecore44:
Heyhey dotOS is working good so far! I have it rooted using Magisk boot img patcher. I have not tried TWRP yet. I still have some experimenting to do but so far I have not seen any issues - calls, texts, BT, WiFi all work.. I did need to get the notch display fix Magisk module.. .... . It also took a few hours for the lagginess to go away. But its pretty snappy now. Thanks for this. Also ..... notification lights work AND no crappy speakerphone mic bug. Finally. Thanks!!! Coffee coming your way..

Update: Fast charging did not work and had some weird call issues dropping on BT. I switched to CorvusOS and am much happier (so far!). I will update if Corvus has any issues but none so far.

Update2: Bluetooth calling/music works good (on Corvus). But I don't think VoLTE works at all. And stock alarm clock does not wake up screen on alarm.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
Thank you so much bro <3
[Essential Phone ROMs, Kernels, Recoveries, & Other] death1246:
Got OS 11 from google GSI but no boot. Weird.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
Have you tried the suitable version?

Anyway, please look at this link: https://developer.android.com/topic/generic-system-image/releases

Choose the ARM64 + GMS version.

Good luck to you!!!
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
Speaking of newbies, just to make sure I understand and then follow your instructions correctly: Step 8 refers to a file downloaded in Step 6, but Step 6 does not point to a file. Please clarify. Also, from among the available GSI ROMs should I choose a VNDK variant, or non-vndk. Thanks.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
Oh, sorry. I have corrected my typing mistake. Step 8 refers to a file downloaded in step 7.

The second, I see "Starting from Android 9, VNDK is mandatory" at here https://source.android.com/setup/build/gsi?hl=el#vendor-binaries-and-vndk-dependencies.

And with this method, I have only tested with Android 10&11. Therefore, I think VNDK is required.

You can help me test this method with Android 9 or lower. Thank you so much.
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
Thank you! Mine is a daily, and only phone, and seeing the problems reported on other ROMs, I'm still on the original (QQ1A.200105.032) Android 10, but I'm encouraged by the progress you've made. Thanks again.
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
One more clarification, if I may. So the image downloaded in Step 7 is to be renamed and flashed as system image (in Step 9), so in effect one would be flashing the system partition twice, once with the 'system.img' from your AOSP build, and once with some GSI image. Do I get that right?
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
In some case, after extracting the zip file in step 7, you will get the system image with other name. In this case, I recommend you to rename it.

In case you wanna try Google GSI Android 11, after extracting, you will see a file named “system.img”. And you dont need to rename anything.

About your last question, dont worry! When you flash a new system image, the fastboot command will automatically earse the old system before flashing. So, please feel free to try :)))
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
So, how has been your experience with CorvusOS after a couple of days? Still all good?
[Essential Phone ROMs, Kernels, Recoveries, & Other] hedgecore44:
It's great! I am keeping it as a daily for now. Only issue so far is that screen cast does not work. I will test Bluetooth calling more during the week and will update if I have issues.
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
That's great to hear!

Why then all the other ROMs devs (including Lineage?!) have so many problems here and there with PH-1's hardware? I suppose that's a rhetorical question.

Thank you for the clarifications, and I did try, but unexpectedly, things went sideways from the very start:

C:\Users\MarS\Downloads\-Save-\PH-1\GSI\try>dir
Volume in drive C is OS
Volume Serial Number is 9E8D-C135

Directory of C:\Users\MarS\Downloads\-Save-\PH-1\GSI\try

2021-09-06 16:20 <DIR> .
2021-09-06 16:20 <DIR> ..
2020-07-16 15:58 5,193,216 adb.exe
2020-07-16 15:58 97,792 AdbWinApi.dll
2020-07-16 15:58 62,976 AdbWinUsbApi.dll
2020-07-16 15:58 <DIR> api
2021-08-29 10:35 25,658,664 boot.img
2021-09-06 09:56 3,568,287,744 Corvus_v16.8-Avalon-treble_arm64_ab_vndklite-Gapps-25082021-Beta-Official-0000.img
2020-07-16 15:58 248,320 dmtracedump.exe
2020-07-16 15:58 427,008 etc1tool.exe
2020-07-16 15:58 1,396,224 fastboot.exe
2020-07-16 15:58 43,520 hprof-conv.exe
2020-07-16 15:58 <DIR> lib64
2020-07-16 15:58 231,594 libwinpthread-1.dll
2020-07-16 15:58 493,056 make_f2fs.exe
2020-07-16 15:58 1,157 mke2fs.conf
2020-07-16 15:58 752,640 mke2fs.exe
2020-07-16 15:58 362,313 NOTICE.txt
2020-07-16 15:58 38 source.properties
2020-07-16 15:58 1,201,664 sqlite3.exe
2021-08-29 10:38 1,915,573,044 system.img
2020-07-16 15:58 <DIR> systrace
2021-08-29 01:37 401,711,336 vendor.img
18 File(s) 5,921,742,306 bytes
5 Dir(s) 153,889,607,680 bytes free

C:\Users\MarS\Downloads\-Save-\PH-1\GSI\try>adb devices
List of devices attached
PM1LHMAxxxxxxxxx device

C:\Users\MarS\Downloads\-Save-\PH-1\GSI\try>adb reboot bootloader

C:\Users\MarS\Downloads\-Save-\PH-1\GSI\try>fastboot flash boot_a boot.img
fastboot: error: Couldn't parse partition size '0x'.

C:\Users\MarS\Downloads\-Save-\PH-1\GSI\try>fastboot flash boot boot.img
Sending 'boot__a' (25057 KB) OKAY [ 0.865s]
Writing 'boot__a' FAILED (remote: 'No such partition.')
fastboot: error: Command failed

C:\Users\MarS\Downloads\-Save-\PH-1\GSI\try>fastboot --set-active
Slot _a does not exist. supported slots are:
a
b

C:\Users\MarS\Downloads\-Save-\PH-1\GSI\try>fastboot --set-active a
Slot _a does not exist. supported slots are:
a
b

C:\Users\MarS\Downloads\-Save-\PH-1\GSI\try>

Weird. BTW, I'm running stock only rooted with Magisk. Nothing else. Could you offer any suggestions?
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
I forgot to tell you that, there is no wifi display (screen cast) in Android 11 for SoC snapdragon 835 until now. All Snap835 devices running Android 11 are facing the same problem.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
Have you updated stock to Android 10?

In case you use Windows Os, please use adb and fastboot coming with driver. You can download driver here: https://storage.googleapis.com/essential-static/Essential-PH1-WindowsDrivers.exe
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
Yes, I did update to the latest official version (A10), and you're a lifesaver!

Thank you for your ongoing assistance.
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
I've been 'costing' on my old dev-kit setup for too long a time. ;-)

After your pointers, things went well. After trying DotOS first (not quite ready to play nice with Gapps, which I need), and then CorvusOS (nice, but I was intrigued by the dynamic root implementation of CaOS), I loaded CaOS next. What a nice surprise all around, from the easy "on-boarding", to the refreshing modesty of the overall approach to mods. And, what really counts, for the way I use my phone everything worked out of the box!

Thanks for opening up the GSI lifeline to our PH-1s.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
You are welcome :D
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
Above, I meant to say 'coasting' ;-)
[Essential Phone ROMs, Kernels, Recoveries, & Other] hedgecore44:
Awesome! Maybe I will try CaOS as well. Does VoLTE work for you on that rom?
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
It seems so, although I do not see this information being explicitly surfaced, but I'm on LTE most of the time and have no trouble with calling. One thing that must be mentioned is SELinux is in permissive mode. I'm waiting the dev reply
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
If you want to change SELinux, you can root your Android by Magisk and then install a package in that application.

To root your phone using Magisk, copy the boot.img (in step 1) to your phone, open Magisk, choose that image to patch. Then use the patched image to flash boot_a.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sambow23:
How is the compatibility with GSIs from other OEMs?

Such as OxygenOS or MIUI from: https://sourceforge.net/projects/nippongsi/files/
[Essential Phone ROMs, Kernels, Recoveries, & Other] hedgecore44:
To see if VoLTE is working go to settings-->about phone-->sim status and see what it says for mobile voice network type. See if it changes too while making a phone call. I am not on LTE for voice on Corvus
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
Thanks. After installing Magisk, SELinux went from "Permissive" to "Disabled", and I do not see any Magisk module that would allow me to modify it. I suspect there's more to it, but I'll leave that for a separate note.
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
You are right, that display is dynamic, and it shows the phone switching from LTE to GSM for the duration of a call. Drat (but I'm OK with that ;-)
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
Nguyen,

I could use your help with something related to your mod for A11. Is it possible to go back to stock? It's not an abstract question for me.

Long story, but embarking on this switch, I relied on 'Swift Backup' to move my apps+data. It worked rather well, but for a handful of apps it did not. One of those apps, 'Last Pass Authenticator" is crucial for me, as you can immagine, and the company provided method has failed as well (I'm still dealing with their CS).

So, I tried to temporarily switch back to stock using an old BTS image, which failed. I've re-flashed CaOS and now, every time I reboot, I get a message about my device not being trusted, maybe even corrupted, and I'm asked to press power button to continue, which it does, and after that, all seems OK. Maybe nothing to be concerned about, but I worry about wearing out my power button ;-)

BTW, I do have the log of that adb/fastboot session, and the files/script that I used.
[Essential Phone ROMs, Kernels, Recoveries, & Other] nguyenquangduc2000:
As you know, Essential Phone has A/B dynamic partition, so that if you are on stock and follow my guidance, the original rom is still last on the B partition. To switch back to original, just change the active partition by typing:

fastboot set_active b

Remember to do backup first, because switching between roms requires format userdata.

In case you cannot find the stock rom, you can use this: https://drive.google.com/file/d/1Kjq9bm-Z6jvfH1T5lA3unbnRX9MBizqu/view?usp=sharing. After download the file, extract it and execute flashall.bat (or flashall.sh if you are using linux).
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
Thanks a bunch.
[Essential Phone ROMs, Kernels, Recoveries, & Other] hedgecore44:
I was able to get VoLTE working on Corvus. There is an option in the roms settings: "install the IMS APK for qualcom vendor"... there is also a setting there that creates a new IMS APN. Selecting that new apn gave me working VoLTE. I am sticking with this rom!

-update: VoLTE stopped working not sure why and I cannot get it back
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
Thanks for pointing this out. A similar set of settings is in CAOS as well, although I did not have to explicitly select a different APN for it to work.

Does Corvus ROM passes Safety Net?