yashsingh1/xdaforums huggingface dataset:
[Mogul, XV6800 ROM Development] shield001:
So I tested this and on her u740 she sent me a message and i received it like 10 secs later and it showed delivered at that time. I waited about an hour and opened the message(even though I could read it when it came through) and closed out of my texts which got rid of the notification and it added delivered 10 mins later.

I'm pretty sure this is only a verizon thing and almost every verizon non windows phone is capable of this feature. Also verizon only charges for text messages that are read from the handset if you don't have unlimited texts which is prob why they have this feature.

Maybe it's not a feature available on our phones but It is possible to have.
[Mogul, XV6800 ROM Development] gc14:
Ok well I thought we were talking about straight SMS with no EMS application extension (which is the feature you're referring to).

I'll explain a little about the SMS system.

You get the D notification when it is a subscriber within your network (i.e. Verizon to Verizon as you've been testing), it has to do with a specific signature flag that is triggered from within that network and does not cross networks.

The check mark means the cell tower has received and cached the message on the tower server for queuing to be transmitted. Once the SMS message has left queuing and goes to transit, which means it has left the tower's local server and has been sent to the carrier message manager (or out to a different network), then the D appears saying the message has been delivered. This really means "message has been delivered to the network" not necessarily to the recipient's device. Most of the time it happens so fast it usually hits the person's handset roughly within 3-5 seconds which coincidentally is the same time the queue server will send you the D flag to notify you it's been delivered. It's a pretty accurate indicator, but is completely unrelated. This D does not indicate when the message was read. In some instances, the person's handset can be off and you'll still get the D.

The times and updated times you're seeing on the u740 is part of the Enhanced Messaging Service, or EMS, application extension to SMS. The u740 is an EMS capable device, which is why you're seeing these updates. Windows Mobile devices are NOT EMS capable, which is why you'll never see this feature, nor will you see any workaround or fix. The only way you'll be able to get this feature is if you ditch your Titan for an EMS capable non smart phone, or if in the future they decide to make WM EMS capable.

Hopefully this clears up the confusion a little.

GC
[Mogul, XV6800 ROM Development] KingofX:
Ok, so in essence you are saying that the ability to know when an SMS message is read does not exist, even with EMS capabilities. Why, on Windows Mobile phones, does the ArcSoft MMS Composer give a checkbox to Allow Read Reports for MMS Messages as if that is a feature that works, yet I haven't even seen that work for MMS messages either? Is that just because Verizon's network doesn't support read reports/receipts? I would think that there would be a way of knowing when a message is read (much like read receipts in Outlook, although the recipient has the option to not send the read receipt, but that's neither here nor there).
[Mogul, XV6800 ROM Development] shield001:
EMS phones have read reports, but apparently we don't have an EMS phone
[Mogul, XV6800 ROM Development] gc14:
You are correct.
[Mogul, XV6800 ROM Development] KingofX:
I was doing a little research on the capabilities of EMS and MMS, and came across something interesting in the wikipedia listing for EMS:

EMS is an intermediate technology, between SMS and MMS, providing some of the features of MMS. EMS is a technology that is designed to work with existing networks, but may ultimately be made obsolete by MMS.

What's perplexing there is that we know EMS is an extension to SMS, and it is saying that EMS is intermediate to MMS...so why doesn't MMS include all SMS and EMS capabilities?
[Mogul, XV6800 ROM Development] dcd1182:
it does, but the carrier must choose to configure the mms client and mms server to support those capabilities.
[Mogul, XV6800 ROM Development] michaelk:
apparently at some point MS and VZ planned on ems in wm- the press releases from the 6700 mention ems:

http://news.vzw.com/news/2006/01/pr2006-01-04b.html

but a bit more current:

http://msdn.microsoft.com/en-us/library/aa919404.aspx

seems wm 6 has a regedit to allow ems.

anyone made progress getting ems to work with wm6 (or 6.1) on vz?
[Essential Phone Guides, News, & Discussion] jaylittle:
I can't speak for the rest of you, but I've been waiting for LineageOS to support this phone since I bought it almost a year ago. I saw a post on /r/LineageOS indicating that mata was finally being supported and sure enough here it is:

https://download.lineageos.org/mata

Since there doesn't appear to be a thread on the topic yet, I figured I'd go ahead and create one so all interested parties can discuss it. I probably won't get around to flashing it myself until this weekend and I'd love to hear how it's working for other people prior to that (and if not, hell I'll flash it and roll the dice).
[Essential Phone Guides, News, & Discussion] jowandrys:
I did it and so far looks good
[Essential Phone Guides, News, & Discussion] Djalil87:
Can you give us a link to the procedure that you followed in order to flash it?

Thanks !
[Essential Phone Guides, News, & Discussion] joha386:
https://wiki.lineageos.org/devices/mata
[Essential Phone Guides, News, & Discussion] dazeone:
Do you play any games? I'm having issues with touch in games only so far
[Essential Phone Guides, News, & Discussion] MattCB72:
I think the installation guide is wrong. To unlock the bootloader, the command "fastboot oem unlock" will not work.
[Essential Phone Guides, News, & Discussion] Djalil87:
Yes it didn't for me. I used instead:

> fastboot flashing unlock
[Essential Phone Guides, News, & Discussion] philsner:
Not able to install Gapps. Always get Error 70...
[Essential Phone Guides, News, & Discussion] theycallmetony:
I've specifically noticed touch issues in Pokémon GO. Unable to reproduce the problem reliably, but it seems that after several hours of uptime single-finger touches no longer register (again, only in PoGO -- other apps work flawlessly). Strangely, using 1 finger as an anchor anywhere on the screen, then tapping the intended button with a 2nd finger will register correctly.

Fortunately, I've been able to resolve the intermittent issue with a simple reboot.

Edit: Looks like touch issues in games may have been present back in 15.1.
[Essential Phone Guides, News, & Discussion] Djalil87:
Thanks for this excellent step by step guide. I didn't get touch to work on my TWRP (latest version from TWRP site) so I did use adb shell commands in TWRP but unfortunately I didn't manage to install GApps. I think I'm missing the step 6. you are describing. I have LOS running with root but no GApps.

Any guess on how I can manage to reboot to recovery while I'm in TWRP sideload mode to get back to TWRP again?

Thanks !
[Essential Phone Guides, News, & Discussion] cz829x18:
Another way to use twrp without touch is by using a mouse. If you have one with a type C connector, plug it in and you can flash LOS and the twrp installer. Then boot back to recovery and flash GAPPS. I had to do it this way but I had an adapter for the type C plug so I could use a regular mouse. The adapter came with my Pixel 2XL.
[Essential Phone Guides, News, & Discussion] kah0922:
I kept getting error 70, so I used MindTheGapps, which installed fine. Don't know if there's any adverse effects of doing that though, by my phone seems to be working fine.

Wish there was some way to configure fullscreen on the notch though.
[Essential Phone Guides, News, & Discussion] Rachel030219:
is there a better solution? It no longer registers my touches after several minutes, so I need to reboot my phone to play games every time…Because of the bad optimization of the kernel, before my phone runs smoothly there is some annoying minutes…

And when I try to flash Neutrino Kernel and reboot, all my PH-1 does is stuck in "phone is starting" with a dialog reminding me that there is an internal error with my system, and it never truly enters the launcher… Has anyone tried yet?:rolleyes:
[Essential Phone Guides, News, & Discussion] theycallmetony:
Been running the 20190614 nightly for ~13 hours straight without the need to reboot. Pokémon GO is still running smooth!

Edit: Touch problems started again a couple hours after posting this. Fortunately, a reboot still resolves the issue.
[Essential Phone Guides, News, & Discussion] Hero2457:
Anyone try LineageOS for microg? Keep trying to flash the rom but no dice, just get sent back to twrp.
[Essential Phone Guides, News, & Discussion] john_jacob:
Same here, unfortunately. The first time (this was a clean flash after a full wipe), it showed the boot animation for an hour before going back to twrp. I tried flashing it again after another wipe, and this time it stayed in the boot animation overnight, for at least ten hours. I'm not sure where to send a bug report or what info to attach to the bug report.

The regular (non-microG) LOS on the other hand, works fine.
[Essential Phone Guides, News, & Discussion] psychic_quark:
I was on Q beta 4 and these steps worked for me:

Here's what worked for me:

fastboot flash boot <twrp image from twrp.me>

<boot into recovery>

Touch isn't working, so instead I do: adb shell twrp sideload

adb sideload <lastest lineage rom>

(again) adb shell twrp sideload

adb sideload <twrp installer zip>

adb reboot recovery

Touch worked in twrp!

Proceeded with installing opengapps/nanodroid and all that jazz.

TBH you don't need touch to achieve most (if not all) functionality of twrp.

To reboot back to recover from within twrp (assuming you have already flashed twrp installer after flashing rom), just do: adb reboot recovery
[Essential Phone Guides, News, & Discussion] :
Brillant post [MENTION=5342698]psychic_quark[/MENTION] that was the only guide which worked for me, coming from Q beta 3. Thanks.

Step 1.1 was needed for me to flash boot_a or _b in step 2 depending on the result in 1.1.

[MENTION=7731603]jaylittle[/MENTION] thanks also for telling us. I also waited for a year to get LOS on my PH-1. I got it from the amazon deal and was ran invisiblisk ROM of Dec.
[Essential Phone Guides, News, & Discussion] :
I ran the June 15 ROM with opengapps pico and magisk in recent version and yestersay I updated via OTA to June 18 ROM without loosing root. Thats very cool. With other ROMs I had to install magisk after update again.

Did anyone tried to install twrp permanently?

And my second question is about removing the red warn during booting which has to be ack-ed. I found this https://mata.readthedocs.io/en/latest/ under topic "Removing the Red Verity Warning" did anyone tried this and will this remove root?

Thanks for your help.
[Essential Phone Guides, News, & Discussion] blair.sadewitz:
1) TWRP 3.2.3.0 works as expected. Simply follow dees_troy's instructions.

2) Yes, I have followed that procedure any number of times to remove the warning. I'm not sure what you meant by "has to be ack-ed"--do you mean you have to acknowledge it before it will boot? At any rate, the answer is yes, that fixes it. As to "will it remove root"--of course it will, because "root" is handled by the kernel, and you're flashing a non-functional boot image, so yeah, it will remove root. The phone won't boot, either. ;)

Flash boot.fix.red.img or whatever it's called, then allow the phone to attempt to boot. It won't. After it bootloops, the red notice will be gone, at which time you should flash your original boot image. Everything will work as expected thereafter. If the boot image you flash has been patched with magisk, you'll have root. Otherwise, you'll have to flash magisk again.
[Essential Phone Guides, News, & Discussion] :
Thanks [MENTION=6272167]blair.sadewitz[/MENTION] for the explanation. Correct I meant that I've to acknowledge the boot. This means when I download the current boot, flash the "boot.fix.red.img" and after the red warn is gone, restore the boot, everything should be fine?
[Essential Phone Guides, News, & Discussion] droidian5:
So far so good and just updated to 6/21. Running pico gapps and lineage su.
[Essential Phone Guides, News, & Discussion] :
I observed a few things:

- double tap to activate screen does not work

- lift up device and activate screen is very unsensitive. When i do it (unusually) very fast its working, but do it normal its not working

- is there any option to disable vibration on fingerprint unlock?

- initial connection problems with hidden WiFis (but had this issue in all my lineage roms)

- touch screen: when i use touch with 1 finger and keep it still, the object (scroll bar, picture etc) starts to "flicker" slightly like i would move the finger very fast, but with minimal distance to all directions. I tried the touch screen smoothness option, but with smoothless level 0 it does not flicker but feels slow. Any idea? Do the touch screen misinterprets the input?

Other things are working great.
[Essential Phone Guides, News, & Discussion] limitlesscodes:
I've been using for a few days now and am happy with the performance and haven't had any trouble after it was installed properly.

I am now unable to connect to Android Auto on my car now though, I've tried joining the play services beta and changing the USB mode to file transfer :(.

Has anyone else tried Android Auto?
[Essential Phone Guides, News, & Discussion] sinkoo1979:
if you guys do search on the essential phone forum you will find the touch working twrp.

https://xdaforums.com/essential-phone/how-to/guide-how-to-install-twrp-root-t3841922
[Essential Phone Guides, News, & Discussion] jaylittle:
It took a few weeks but I finally got around to installing Lineage on my PH-1 and so far it looks real real good. I know I promised a quick turnaround on installation in my OP but life of course intervened and said no in the form of a lightning bolt hitting my house and frying a ton of my stuff.

In any event, Lineage is looking real good. Note: I don't do gapps and Lineage seems to work great without it. It's still pretty early though so I'll be sure to post updates regarding any problems I encounter here.
[Essential Phone Guides, News, & Discussion] droidian5:
It's working great for me. Pico gApps, LOS SU, and taking most daily updates.

Wondering if there will be an official thread opened by the maintainers. I bet there aren't many using LOS on Mata so we may be on our own on XDA.
[Essential Phone Guides, News, & Discussion] :
Maybe there is a download statistic ;)
[Essential Phone Guides, News, & Discussion] Djalil87:
Here's the stat ?.
[Essential Phone Guides, News, & Discussion] :
More than i thougt...
[Essential Phone Guides, News, & Discussion] swiftbones74:
I am surprised as well.
[Essential Phone Guides, News, & Discussion] droidian5:
What are you running currently? Have you tried official LOS? How does it compare to other ROMs? I find LOS to be a solid and stable daily driver.
[Essential Phone Guides, News, & Discussion] :
I am running lineage-16.0-20190629-nightly-mata-signed.zip and working in general good. I use it as day driver. The problems I found are described here:
[Essential Phone Guides, News, & Discussion] droidian5:
7/2/19 smooth as silk! Touch is more responsive the past few nightly builds.
[Essential Phone Guides, News, & Discussion] :
Acknowledged. My described "flicker" still exists, but the responsive is much better. Thx for telling us.

Interestingly, nothing about this is mentioned in the release notes.
[Essential Phone Guides, News, & Discussion] jawz101:
Has anyone tried the improved Bluetooth SBC audio feature that someone incorporated into LineageOS? I'm just wondering if there is any noticeable iimprovement in BT audio.

I'm hardpressed to leave the Q Beta for Lineage unless there's some fantastical feature. Seems like stock Android has chipped away at the LOS featureset.
[Essential Phone Guides, News, & Discussion] almo40192:
Looking for help on removing the black bar at the top of the screen.

I can go into settings, set expanded desktop to remove the status bar, but the black bar remains in all apps.
[Essential Phone Guides, News, & Discussion] :
Use this Magisk Module:

https://github.com/itz63c/TopNotch-NotchBarKiller/releases

Don't forget to enable it by going to the notch cutout settings (in Developer Options) and selecting "Notch Killer."
[Essential Phone Guides, News, & Discussion] Sheradrax:
Has anyone using Boost or Spring got 4G working on LOS16? I get 3G out of the box, but no 4G and I can't edit APNs at all.
[Essential Phone Guides, News, & Discussion] droidian5:
Looking closer at that stat page. If you click on a device it shows all the versions of LOS and the number of installs per version. Not one listed is an official version. The count hasn't changed at all since you posted the screenshot so it can't be an accurate count.
[Essential Phone Guides, News, & Discussion] Djalil87:
Oh... thanks for the info.
[Essential Phone Guides, News, & Discussion] almo40192:
I've been looking around to solve this issue, but haven't have much luck. It looks like it's an issue with a good number of ROMs on this phone, but my issue is that after some time, the touchscreen in some games and apps stops working normally.

To have it work, I need to hold one finger on the screen and the other finger will register properly.

The issue can temporarily be fixed by rebooting the phone.

I notice the issue occurring when an app/game accesses the camera. At that moment, issue occurs.

I came across this in my searches: https://review.lineageos.org/c/LineageOS/android_frameworks_native/+/198809

Not sure exactly how to work with that, but I figured I would provide as much info as I can before asking for help. Thanks ahead for the help
[Essential Phone Guides, News, & Discussion] Hero2457:
Anyone have a step by step to install the LineageOS for microg fork? Still can't get it to boot with the latest builds.
[Essential Phone Guides, News, & Discussion] neeksxda:
I'm very happy with how stable the MicroG LineageOS 16 fork's been since flashing it a week ago from https://lineage.microg.org/
[Essential Phone Guides, News, & Discussion] :
So, I thought it would be a good idea to flash the newest factory image sans the system and boot partitions as well as not format userdata. I thought it would be best to have my phone on the latest radio and all. After flashing I flashed the LineageOS zip over it just in case. After boot everything was all glitchy. Some screen elements weren't even loading, stuff was jumping around, and things were not usable at all. I had to go and clean flash everything from the start to fix it.

So, this is just a comment telling people to not do what I did... But also can someone explain why that happened?
[Essential Phone Guides, News, & Discussion] panaderodc:
Hello, Just wondering if you have figured this out yet? In the same boat.

Thanks
[Essential Phone Guides, News, & Discussion] jawz101:
The data partition has to be generated from a ROM based on as ROM's system partition.

The data partition is OS-specific because it's doing all of that ART compilation of your apps, permissions can be different, possibly some unique IDs get generated... Who knows. Bottom line is that it won't play well.

I can only make guesses like this but a lot of operating systems have a similar thing happen. If it was just pics, audio/video, and documents- they would be accessible by any OS as long as permissions are open but since you're dealing with apps and app data there is a higher chance it just can't be swapped around amongst ROMs. Google cloud messaging borks with titanium backup for the same reason because IDs aren't registered properly. You just need to expect setting up all of your apps and settings again when switching ROMs.
[Essential Phone Guides, News, & Discussion] :
Thing is, I essentially flashed the system image but removing the system and boot partition flashing as well as the userdata format. So only things like radio, bluetooth, rpm, stuff like that. Nothing should have changed anything with the data partition, I don't think.
[Essential Phone Guides, News, & Discussion] :
To clarify a bit more, this is how my modified flashall script looked;

fastboot flash nvdef_a nvdef.img

fastboot flash nvdef_b nvdef.img

fastboot flash bluetooth_a bluetooth.img

fastboot flash bluetooth_b bluetooth.img

fastboot flash xbl_a xbl.img

fastboot flash xbl_b xbl.img

fastboot flash abl_a abl.img

fastboot flash abl_b abl.img

fastboot flash dsp_a dsp.img

fastboot flash dsp_b dsp.img

fastboot flash modem_a modem.img

fastboot flash modem_b modem.img

fastboot flash vendor_a vendor.img

fastboot flash vendor_b vendor.img

fastboot flash cmnlib_a cmnlib.mbn

fastboot flash cmnlib_b cmnlib.mbn

fastboot flash cmnlib64_a cmnlib64.mbn

fastboot flash cmnlib64_b cmnlib64.mbn

fastboot flash tz_a tz.mbn

fastboot flash tz_b tz.mbn

fastboot flash hyp_a hyp.mbn

fastboot flash hyp_b hyp.mbn

fastboot flash rpm_a rpm.mbn

fastboot flash rpm_b rpm.mbn

fastboot reboot
[Essential Phone Guides, News, & Discussion] jawz101:
hm... I dunno then. I've been hesitant to flash a custom ROM on this phone. The whole A/B partition thing sounds like a minor hassle, I don't want that bootscreen thing, and I generally don't see many reasons to use LOS anymore. Unless it exposes hardware features or something I really don't have much reason to go custom.
[Essential Phone Guides, News, & Discussion] droidian5:
Not much gained using lineage, but it works great!
[Essential Phone Guides, News, & Discussion] Sheradrax:
Nope... Can't get 4G on anything but stock ROMs. I've changed APN settings, changing the *#*#4636#*#* menu and tried flashing without magisk or gapps. I have a thread started in the Essential Q&A section, but nothing has helped. Its only been an issue since running the Q beta.

Please let me known if you figure it out.
[Essential Phone Guides, News, & Discussion] jabashque:
A fix for this has been merged and will be present in the 08/04 nightly.
[Essential Phone Guides, News, & Discussion] :
Does lineage also provide vendor firmware updates?

Or should i install them on my own with the script privided here: https://xdaforums.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681

Is there a possibility to check my vendor firmware state?

Thanks for your help
[Essential Phone Guides, News, & Discussion] UN5EEN:
Flashed the 8/4/19 Nightly yesterday morning. Was not able to flash gapps so improvised and installed Aurora Store to get my apps. Everything seems to be running solid except today I attempted to use location services to find my local weather and got the following message. I then attempted to use google maps and was unable to get directions anywhere.

Location Accuracy is set on High. Should these services not be working?
[Essential Phone Guides, News, & Discussion] UltraMagnus0001:
When charging with my Qualcomm 3.0 charger, the phone cycles through the charging slowly to rapidly and then settles on slowly. Using the same wire on a regular 2.1a charger I'll get normal charing. I also tried ElementalX-PH1-3.21.zip to see if it would help with no luck. Any suggestions. Also what is the best os for magisk?
[Essential Phone Guides, News, & Discussion] Muledog17:
Same problem here. Did you or anyone else ever manage to fix this?
[Essential Phone Guides, News, & Discussion] marcdw:
[MENTION=2882666]UN5EEN[/MENTION], not really sure but you say you couldn't flash gapps so got got what you needed via Aurora Store. I assume that also means the Google core (Play Services). For full functionality some things, especially Play Services (which I believe handles their location stuff) needs to be a system app. When flashed it sits under /system/priv-app/.

Might be best to find out why you can't flash gapps and find a way to make it so.

Essential PH-1, /e/OS 0.7-n ROM, microG (NoGapps), XDA Legacy
[Essential Phone Guides, News, & Discussion] unseen:
I have received a mention notification from the system, but I am not the right "unseen" :D