we're ready, just pending code-review from other maintainers.I know we are not supposed to ask, but sorry I can't resist. Any ETA of when will the official for Mata roll out?
It's still WIP, we are trying to decide which to use. Tomoms is trying to fix Klik but if he can't we will fall back to Aperture.Hey! I recommend we begin to use the Aperture camera APK in place of the essential phone application. The Lineage-based application works great as of now (Feb 2nd, 2023)!
Well of course but it's also broken at the moment, so anything is better than broken haha.Since Klik will have code specific to the camera in Mata, won't that be better?
Dude lol it's been less than a month - builds roll monthly and the ASB dropped yesterday.
no worries lolLol, sorry. I had thought it was an unofficial nightly build schedule considering the past habits (by looking at the time between builds in your page). I am sorry if it came across as ungrateful, or anything along those lines. It was not my intention whatsoever.
yes
That's good to hear. I am waiting for the official builds to get 13 on mine.well done devs! previously newer android builds don't run that well on much older hardware, but things seem to turn north with A13, both my mipad 4 on sd660 and essential ph-1 on sd835 run A13 based off aosp / lineage os very well with respectable battery life, many thanks for giving these old hardware a literal new life!
sadly no - this is why we're working on keeping the essential one around :/Hey, was curious if any camera apps besides the essential one works with the 360 camera accessory?
Yeah, probably wouldn't have hit these issues with Lineage Recovery following the wiki guide ;pJust a shoutout to the devs here, I'm thuroughly impressed with this build. This phone has been my "mess around with" phone for years, and im super excited to see it get LineageOS 20.
Through my flashing journey today, I thought I would just leave some comments on issues I hit trying to go from whatever I was running prior to the build i flashed today which was the Feb 2023 lineage-20.0-20230209-UNOFFICIAL-mata.zip
I did make sure my OEM unlocking was enabled from the dev menu, then enabled usb debugging. So it turned out I had wiped my windows install since my last time messing around with android flahing, so i did need to install the platform tools over again, and I will note that at first i tried the generic fastboot files i found online but i did encounter some issues with those especially when trying to run the fastboot -w command, so I would HIGHLY suggest downloading the essential windows drivers (i got them here) Essential-PH1-WindowsDrivers.exe
next I'm pretty sure I messed up when flashing TWRP, i basically flashed it to both a and b. you shouldn't do this. learn from my mistakes. This was recoverable however. I just ended up downloading the Android 10 BTS Folder from: https://forum.xda-developers.com/t/...sential-stock-firmware-and-rom-dumps.3701681/
I then ran the flashallwipe.bat from that extracted folder and that got me back into a healthy install state. I did log into the phone after restoring this to make sure it could still get into android. i tloaded back fine (i did double check oem unlocking was still set and renabled adb usb because i'm lazy and adb reboot bootloader is easier than holding buttons.
Finally now that my install was good I followed the steps to install TWRP. My getvar current-slot was A so i flashed it using something like fastboot flash boot_b twrp-3.2.3-0-mata.img and when i booted it into TWRP i did end up having the problem where the touchscreen controls wouldn't work. I did end up finding TWRP_Boot_Jan.img online which apperently fixed this issue, although it DID still have a problem where I couldn't use the passcode i set for my install to mount my filesystem, however I didn't care about anythign on this phone at this point i just wanted to flash this rom, so i just proceeded without the passcode.
From a working TWRP I was able to flash this rom using a command like: adb sideload lineage-20.0-20230209-UNOFFICIAL-mata.zip and while it took a few mins, it transferred successfully and installed without a problem.
The only noteworthy thing after the install was that... the gesture navigation didn't work for a few mins? I honestly have no clue what was going on here, it feels like it took as long as the "optimizing android apps" usually takes after doing an OS upgrade, but during that time i could not pull down the notifications bare, and i could not do the swipe up gesture. I even tried temporatily switching to 3 button navigation and that only showed the one triangle back button. You can still get mostly around the UI while this is happening, and i have no idea what i did to resolve it, the only activities i did in the meantime was connect the wifi and do the play store updates, which, i don't think would have fixed this problem? But after like i said the amount of time i would have expected the "optimizing android apps" dialog would have taken to go away, everything started working.
Now this device is working great. It'll make a great backup device. I just really want to show appreciation to the devs working on this. kudos, look forward to seeing this device live on.
Upgrade to the newest from Google.Hello Everyone, I have not used ADB and used a custom ROM in a number of years. I still have ADB 1.039 and FastBoot 0.0.1-4500957 on my desktop computer from the original Essential website I think. Do I need newer versions for this task? Thank you!
Nope. We are waiting on the final maintainers sign off.Any update on this? Sorry to ask again but I prefer the official one with minimal Google apps
Hello Friends,
I think I have everything working. However I see an oddity. Google Chrome and Brave both show Android 10 while the About Phone shows Android 13. Is this normal or should I start over?
Thank you!
The reason it showed this is because I spoof some things for safety netYeah, that's quite normal so there is no need to worry.
Chrome Canary does show precisely the same thing.
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
we're ready, just pending code-review from other maintainers.I know we are not supposed to ask, but sorry I can't resist. Any ETA of when will the official for Mata roll out?
Think I fixed it for the next build.same, no BT audio routing to wireless. on other phones a setting can be changed in dev options to fix it but it's greyed out on my ph1.
Yes, as Nolen has said, we are taking care of this. I was working on this issue lately, but then I briefly put it aside to work on other stuff. I know this has been a long-standing bug, but with a little patience (almost?) everything is going to be fixedAnyone else having the stock camera app crash when taking hdr pictures?
Yeah, factory reset each time, per the instructions.
I have a second Essential phone still running Official LOS 19.1. I'll try installing on it and see what results I get.
Figured it out - working on it. Give me 4 Horus, new build should work.That's a given, but I went a step further once more. I re-flashed the last OEM (.032), then your recovery (lineage-20.0-20221105-recovery-mata) and latest vendor (vendor-QQ1A.200105.088) to both slots, and then side-loaded your latest (lineage-20.0-20221110-UNOFFICIAL-mata.zip), and .... same thing as I described above. We have a puzzler here, huh?