yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3a Guides, News, & Discussion] PGHammer:
There should be VERY little modification required from sargo to bonito as one is simply a different size than the other. (I'm actually surprised that nobody ever compared the two in terms of hardware (especially since their simultaneous release).
[Google Pixel 3a Guides, News, & Discussion] anonym12:
I have built pure lineageos 17 according to https://xdaforums.com/pixel-3a/how-to/guide-easily-build-install-lineageos-17-t4048063

The esim manager has to be disabled or you have to stop enforcing SELinux.

Download:

https://drive.google.com/drive/folders/19MD_1CZrhejh29ui3Q12Ypqfp-mU3dlt?usp=sharing
[Google Pixel 3a Guides, News, & Discussion] gee one:
If you include gapps in your build, the esim manager should stop crashing. If running gappless, I remove esim and hotword enrollment from the proprietary files.
[Google Pixel 3a Guides, News, & Discussion] spinxen:
Hello!

I have also built & installed lineageos 17 according to the guide above, thanks!

Now i like to install Gapps, but how? Booting to linage-recovery and flash from internal storage wont work as it refuse to mount? And adb sideload'ing gapps-nano-zip gives a error message about to little space available? Any ideas?
[Google Pixel 3a Guides, News, & Discussion] fireclaw722:
The issue is the new dynamic partition scheme doesn't leave enough room to install any extra system apps. There is a patch on the Lineage Gerrit, but it hasn't been merged (https://review.lineageos.org/c/LineageOS/android_device_google_bonito/+/261941).
[Google Pixel 3a Guides, News, & Discussion] spinxen:
Thanks for letting me know, so as of now there is no workaround to get GApps work with this branch after it has been installed?
[Google Pixel 3a Guides, News, & Discussion] fireclaw722:
Not that I know of. You either have to create space for G-Apps, or bundle G-Apps with the ROM.
[Google Pixel 3a Guides, News, & Discussion] gee one:
I include gapps when I build the ROM. I have a vendor tree that is based off of opengapps pico. I just unpacked this pico zip and mimic'ed what it installed, plus something like pixel migration tool.
[Google Pixel 3a Guides, News, & Discussion] spinxen:
Would you mind to share your zip? Thanks!
[Google Pixel 3a Guides, News, & Discussion] gee one:
https://opengapps.org/
[Google Pixel 3a Guides, News, & Discussion] spinxen:
This is somewhat above my level of knowledge, if you have a complete build zip with Gapps, do u mind sharing this with me?
[Google Pixel 3a Guides, News, & Discussion] noky76:
How to install?
[Google Pixel 3a Guides, News, & Discussion] PGHammer:
LioneageOS 17.1 for Poxel 3a: Notes from the front

Because of the issues, I have stuck with those versions that include GApps (invisiblek's simple LineageOS 17.1 works a treat, and is cloneable for those looking to build their own). Until beta 3 of Android 11 drops, I'm running this. Still no TWRP, or root, or anything else. Other than Pixel Launcher, I'm basically running stock Lineage.
[Google Pixel 3a Guides, News, & Discussion] P1x3l3d:
Hi guys,

Just built my own image according to the 'easy' method (using docker). Took about 5 hours, and seemed to have gone well, almost no errors ;)

I started out by flashing the Pixel 3a with the lastest Android 10 Factory Image from Google (QQ2A.200305.002, Mar 2020) to be sure it's as clean as possible. Booted into Android 10 once, enabled Developer Settings et cetera.

Then followed the 'Install' steps from https://github.com/SolidHal/Build-lineageos-sargo:

- boot into bootloader (fastboot mode)

- run 'fastboot flash boot boot.img'

- reboot into recovery -> Apply update -> Apply from ADB -> run 'adb sideload lineage-17.1-20200404-UNOFFICIAL-sargo.zip' (in my case)

When entering recovery mode I noticed an error at the botton of the screen: 'E:[libfs_mgr]Failed to mount /data: Invalid argument'. Despite that I could continue and sideload/install my self built lineageos zip, which finished without error (status 0). After installation the phone went back to into recovery mode (as described on the Github guide). Unfortunately, when I continued and picked 'Reboot System Now' I got thrown into the bootloader with enter reason: 'error boot prepare'. Every time the phone boots I see this error now.

Does anybody have a clue what I could be doing wrong? Any help is appreciated, thanks!

Edit: Okay, seems my problem is solved. When flashing the self-built boot.img, in my case I also had to specify which boot part to flash to: boot_a or boot_b. After having done that, booting now works.

Thanks SolidHal for providing your docker file and making it easy to built your own LineageOS 17.1 image! :)
[Google Pixel 3a Guides, News, & Discussion] barqs_root:
Working and Running Smoothly

Thanks for posting this.

I was also able to build and install this successfully using the easy method. Yes, it takes a long time and requires an ample amount of memory and storage.

The battery life is excellent compared to the other roms/kernels I've tested so far. Started with a factory flash of Android 10.0.0 (QQ2A.200305.002, Mar 2020) (https://developers.google.com/android/ota). Then I followed the instructions here.

I also had the E:[libfs_mgr] error but it still installed correctly after the second try. Specifying boot_a or boot_b may have been what got this to work for me. Thanks to P1x3l3d.

Rooted by patching the boot image with Magisk (https://xdaforums.com/pixel-3a/how-to/how-to-root-pixel-3a-preferred-t3938783).
[Google Pixel 3a Guides, News, & Discussion] PGHammer:
Did you build in Linux? If so, which version? (I'm not used to building Docker - and especially in Linux - and I'd rather do it right; therefore WHICH version of Linux has everything to do it right is critical.)
[Google Pixel 3a Guides, News, & Discussion] barqs_root:
PGHammer, I don't think it's going to matter too much what distro you use because you're going to have to install the latest platform-tools and install docker from a repo anyways. Just use something recent. Ubuntu comes to mind if you're not a huge GNU/Linux guy.

I built using Debian Stretch and had no issues other than my ram got all used up so I had to create more swap and add

vm.swappiness=60 to /etc/sysctl.conf

You need 100+GB HDD, 16GB+ RAM, and a fat swap space (I used a 20GB Swap file)

Also someone (anon12?) already posted a ~700MB zip of their build in this thread and I can confirm it works.
[Google Pixel 3a Guides, News, & Discussion] swagglepuff:
How did you you get this to install, I get signature verification failed, error:21. Then abd aborts the installation. I confirmed the integrity of the images with the provided checksum files. I even downgraded back to February's update because I was on Aprils update and thought that maybe that was the issues.

The steps I did are as follows:

Unlock bootloader

Enable debugging

Booting into the boot loader- run ./fastboot flash boot_a boot.img( ./ before is required due to being stuck on windows while I work from home.) Successfully installs to boot_a in 2.5sec.

Booting to recovery

Wipe/factory reset

Apply update from ADB- ./adb sideload lineage-17.1-20200222-UNOFFICIAL-sargo.zip

This is the following errors

E: failed to verify whole-file signature

Update package verification took 35.0 s (result 1).

E: Signature verification failed

E: error: 21

Install from ADB completed with status 2.

Installation aborted.
[Google Pixel 3a Guides, News, & Discussion] barqs_root:
Try some different things

The steps I followed were roughly this:

Flash factory image (QQ2A.200305.002, Mar 2020)

Boot up, enable developer settings, usb debugging, etc.

Reboot into bootloader/fastboot

DON'T erase/wipe user data DON'T specify boot_a or boot_b

fastboot flash boot boot.img

adb sideload lineage-17.1*.zip

It took me a few tries to get this and I'm going off memory here.

Just keep trying you should get it.

If needed I can also upload a ZIP of my build.
[Google Pixel 3a Guides, News, & Discussion] swagglepuff:
Was able to get it installed! Now the phone has been booting for 45 minutes. What was your initial boot time after install?
[Google Pixel 3a Guides, News, & Discussion] barqs_root:
Dang. Sorry to hear it.

My boot time was very quick, definitely faster than the factory image maybe 60-120 seconds. Try rebooting a few times and re flashing. If you have issues I'll upload my build.
[Google Pixel 3a Guides, News, & Discussion] swagglepuff:
This thing is booting at all. Even flashing the march update and no such luck. If you want to upload your image that would be awesome. I am in no place to build it my self with my current setup.

Edit: gave it one last go before be on the april firmware and son of ***** it actually worked this time. About crapped my pants when the windows sound for a device plugging in went off lol.
[Google Pixel 3a Guides, News, & Discussion] reini_from_nl:
Hi,

i followed the easy way and on this point:

docker build --tag solidhal/docker-lineage-cicd .

I got this Error:

Cloning into 'OpenDelta'...
fatal: could not read Username for 'https://github.com': No such device or address.

Does anyone have a idea wy this happens?
[Google Pixel 3a Guides, News, & Discussion] ptn107:
I get the same error. It's because

android_packages_apps_OpenDelta

does not exist in

https://github.com/omnirom/

Its gone you can see here.

I don't know what to do now other than quit the docker way and try it the manual way this week.
[Google Pixel 3a Guides, News, & Discussion] gee one:
Are you building omni or lineage?

Never used docker, but maybe there are some leftovers in the fridge.
[Google Pixel 3a Guides, News, & Discussion] DehDehDeh:
Anyone succeeded in building using the easy way lately? Could the missing package (https://github.com/omnirom/android_packages_apps_OpenDelta) be replaced by this one: https://github.com/lineageos4microg/android_packages_apps_OpenDelta ..?
[Google Pixel 3a Guides, News, & Discussion] guestuser123:
Has anyone made a build with Gapps Pico? I don't have the hardware to make my own
[Google Pixel 3a Guides, News, & Discussion] gee one:
You can build this on a VPS like linode, aws, or google cloud. Linode would probably be a few dollars to build, just be sure to delete the vps when you're done so you get charged any more.

I think google gives you a $300 credit when you sign up... That's plenty to build with.
[Google Pixel 3a Guides, News, & Discussion] SolidHal:
For everyone here experiencing the opendelta /github invalid username issue, it is fixed :)
[Google Pixel 3a Guides, News, & Discussion] blitzn0r:
Hi could you explain how you mimic'ed what it installed? I'd like to compile lineage with minimal gapps and I'm currently stuck because I don't know how to include the gapps properly.
[Google Pixel 3a Guides, News, & Discussion] gee one:
Here's an example of how to do it. I think there is an remove packages option too.

The basic steps are download pico gapps, unpack it, create a tree with pico gapps using the structure in shag gapps. Modify for your use case.

https://gitlab.com/shagbag913/vendor_gapps

You could also just add this to your build, if you just want gapps.

I haven't actually used this particular repo, but it'll at least give you some hints.
[Google Pixel 3a Guides, News, & Discussion] ur_blocked:
Oops i accidentally posted this already, but to the wrong thread >_<

I tried to build lineage for my phone (sargo) using the hard way instructions, but, sadly it did not build due to this:

FAILED: out/soong/.intermediates/system/netd/resolv/dnsresolver_aidl_interface-api/checkapi_2.timestamp (out/soong/host/linux-x86/bin/aidl --checkapi system/netd/resolv/aidl/dnsresolver/1 system/netd/resolv/aidl/dnsresolver/2 && touch out/soong/.intermediates/system/netd/resolv/dnsresolver_aidl_interface-api/checkapi_2.timestamp) || (cat system/tools/aidl/build/message_check_compatibility.txt && exit 1)
ERROR: system/netd/resolv/aidl/dnsresolver/1: No API file exist

ERROR: Backward incompatible change detected on AIDL API
Above AIDL file(s) has changed in a backward-incompatible way, e.g. removing a method from an interface or a field from a parcelable. If a device is shipped with this change by ignoring this message, it has a high risk of breaking later when a module using the interface is updated, e.g., Maineline modules.

I'm not clear on what the problem is; those files do exist at least:

$ tree system/netd/resolv/aidl/dnsresolver/ system/netd/resolv/aidl/dnsresolver/
├── 1
│ └── android
│ └── net
│ ├── IDnsResolver.aidl
│ └── ResolverParamsParcel.aidl
└── 2
└── android
└── net
├── IDnsResolver.aidl
└── ResolverParamsParcel.aidl

6 directories, 4 files

However, I am not familiar with AIDL enough to know if they're supposed to be in a specific format or something; all I did was follow the directions.

Any clues what to do about this?
[Google Pixel 3a Guides, News, & Discussion] Pogo:
I'm using this build since February and is rock solid and I am wondering do you or someone else on forum have some up to date build? My PC need more RAM for successful build and I have hard time finding right components :(. I prefer no Gapps or MicroG version, if possible.
[Google Pixel 3a Guides, News, & Discussion] gee one:
I switched to an aosp build recently, but before that, I was using lineage on a gappless build, and then a microg build.

I'll see about updating and pushing my repos. Probably after the July update and sources get pushed out.
[Google Pixel 3a Guides, News, & Discussion] pauliusval99:
Any tips on camera? Do you need full gapps for the camera to work properly? Maybe there's a way to install only GCam but not the other gapps?
[Google Pixel 3a Guides, News, & Discussion] pauliusval99:
The stock camera doesn't work at all in my build, but I found a Gcam port that works.

And I have a question: where does the rounded screen corners overlay come from? I don't think it comes from AOSP, as setting sysui_rounded_size in secure settings doesn't change anything. Is there a patch I can revert to remove the overlay?

And I know it won't remove the roundedness altogether, I just want to remove the overlay. I've already reduced the display height with "wm size" but the corners are still rounded.
[Google Pixel 3a Guides, News, & Discussion] sahim82:
failed to verify whole-file signature

Thank you for that great guide to build sargo!

I created the first build half easy docker build (which failed after some time) and "resuming" that build the hard way (brunch sargo). It works great.

Now i made a new build the hard way and it also build successfully .

But when i want to sideload the zip i get the error "

failed to verify whole-file signature

". Installing anyway (there is a prompt) fails immediatelly with

Error applying update: 26 (ErrorCode:: kDownloadMetadataSignatureMismatch

Solution: the problem is that i did not sign the later build with the releasekey. Signing the build with the right keys should make sideloading possible
[Google Pixel 3a Guides, News, & Discussion] tvoneicken:
Thanks to [MENTION=7774134]SolidHal[/MENTION] and [MENTION=9901562]anonym12[/MENTION], things are working pretty well so far for me!

One issue I have is that I end up with 2 camera apps: com.android.camera2 and org.lineageos.snap and both have the same icon :(. How can I get rid of or hide com.android.camera2 ?
[Google Pixel 3a Guides, News, & Discussion] bubbyj:
Disable it (long press, then info, then disable)
[Google Pixel 3a Guides, News, & Discussion] tekhedd:
Updated update: I see lineage has released a nice official build for Pixel 3a, so... hooray?

Dirty flash to the 2-Feb-2020 daily build: boots normally. Endless "keeps crashing" popups from SIM Manager just like the self-built version. Got Magisk working and disabled it and noticed I now have two "SIM Manager" system apps. Once both were disabled, the SIM Manager popup went away. So this is good.

I believe this may result in my "phone didn't ring" issues when roaming. Oh well. The other fix for this bug is to install GApps and that is not happening. :) Maybe Microg will fix it as well? Anyway, hope this helps.

Old message below:

Update: I've been unable to get the docker build working for the last month or so. Have started working on a "hard way" build but I mean they're not kidding when they say it's the hard way. Might save time if I took the "hard way" instructions and turned them into a script...

I suspect people in this thread are people like me who enjoy having a pure lineage build, possibly with no-google and/or no-microg (I have no-both and love it). Has anybody found a community built ROM as a better option? Did Lineage start supporting 3a properly when I wasn't looking? I'd love to get an update or two...
[Amazfit] grillote:
Hi. I have an Amazfit Nexo Global Versión (AC1817). And it has the 1.0.0.0 firmware version.

I read some information, and I see other people in the same situation.

I know that there is more actual version of this firmware. I send an email to Amazfit Europa and confirm to me that there is newer version of this firmware.

I try to update via OTA from the watch and from the app, and always have the message that I am in the newest version.

I try to make hard reset.

I try to send a report to Amazfit

I try everything that Amazfit explain to me in his email.

No results

Amazfit said to me that contact to my reseller, but this is difficult to me.

Any one has a solution?

Any one knows where can I download the new firmware and how to install it via PC?

I look for information in the net and I can't find anything.

Thanks in advance.

Enviado desde mi Mi9 Pro 5G mediante Tapatalk
[Xiaomi Mi Max 3 Questions & Answers] brasscupcakes:
Hi there, I've got my (rooted) MI max 3 Volte & wifi calling working with the ATT variant of Tracfone and want to switch to a different ATT MVNO (loved Teltik/ TMO but neither worked and calls intermittently went straight to VM on 5 bars reception)

I'd love to use Pure Talk if poss since they have a good rep rep and I hate ATT prepaid customer service... Tracfone is also bad. And I heard Red Pocket porting can go horribly wrong sometimes.

If you have Pure Talk are Volte and wifi calling and MMS all working consistently? I also have a Redmi Note 5 (Whyred) I could use instead of Max 3 if I must.

I have seen reports stating that even though they use ATT Towers these features don't always carry over when people switch to Pure Talk.

(Not really an XDA topic but there weren't enough Xiaomi users in Howard Forums and the Pure Talk rep on Reddit didn't know)

If you heartily recommend some other prepaid ATT MVNO I'd love some tips. I'm a light data user, don't require Int'l, want tether and wifi calling for emergencies

Many thanks!

.
[Touch Dual, MDA Touch Plus ROM Development] shortyboy:
im getting to flash and test some neon roms and was wondering where i can find official release roms if i ever wanted to go back to them?thanx

or if anyone is willing to rebuild me a flashable rom with my raw files please do so..hehehe...thanx
[Touch Dual, MDA Touch Plus ROM Development] wmn79:
I can give it a try if you provide me the files.
[Touch Dual, MDA Touch Plus ROM Development] neotekgeek:
Too little too late

NEON300

Had I read this before blowing out the OEM ROM I'd have tried to dump it first.

*sigh*

Contacted HTC, who indicate they are not providing any sort of OEM ROM to revert to factory specs. Disappointing but not surprising I suppose.

It'd be nice to have an OEM ROM on hand however.
[Galaxy Tab S2 Q&A, Help & Troubleshooting] ivanox1972:
Is there any way to know and read tab s2 t710 (probably same for t713) display id or name or how to call it?

I am in situation to buy old t710 for really funny price but device is white and screen black. Clearly changed. No problem for purpose I plan for it just if screen is original...

Thanks
[Huawei Watch] mm79k:
Just received my classic version of the watch GT2 with brown leather strap. I really like how this watch looks. but coming from Wear OS (Motorola) and Tizen OS (Samsung), I am unpleasantly surprised to discover that the Watch GT2 does not have a pattern (or a pass code) lock screen.

Anyone can view my notifications, favorite contacts, etc. and there is no way to have a lock screen with a pattern or a pass code.... Not really good for privacy.

I am more surprised that nobody is talking about this serious issue!
[Huawei Watch] gagi75:
If is on hand nobady can see...
[Huawei Watch] mm79k:
And if you take it off, leave it somewhere, or lose it.... your notifications, contacts and call log are available to everybody!
[Huawei Watch] gagi75:
But why to take off man too much wory

Btw do you have sicrets ?
[Huawei Watch] adamelphick:
I started with LG Watch, then Moto 360, then Huawei Watch 1.. all Wear OS / Android Wear, and none of them had a lock screen that I was aware of? You lifted your hand and the watch popped alive....

This is supposed to be a 24hr wearable that monitors you as well as alerts you. I take mine off to shower as I have a full cover case and don't want water under it, but the rest of the time it's on my wrist.
[Huawei Watch] mm79k:
Both Wear OS and Tizen OS can be locked automatically as long as you are not wearing the watch. You simply wear the watch and unlock it while on your wrist and it will stay unlocked as long as you are wearing the watch. The watch will automatically lock itself as soon as you take it off so no one can view your conversations and other stuff. This feature was available on my Moto 360 and Samsung Galaxy Gear Sport

Please check the attached pics from Tizen and Wear OS.
[Huawei Watch] adamelphick:
Ok never noticed or used that function.
[OnePlus 6T  Questions & Answers] Deleted member 8538501:
Hello guys,

I recently updated from OOS Pie to OOS 10.3.1 and when I wanted to clean preinstalled google bloat, I found that Titanium Backup can no longer do it. Tried a few other root uninstallers, also failing every time.

Has anyone found a working workaround to remove specific google apps?

Thanks,
[OnePlus 6T  Questions & Answers] Deleted member 8892904:
Try this. Download MixPlorer from XDA. And Grant it Root Explorer Permission. Now navigate to /system and delete the apps you want. On Android 10, most of the Google Apps are located in /system/product/app & /system/product/priv-app. Alternatively, some apps are also in /system/app & /system/priv-app
[OnePlus 6T  Questions & Answers] Deleted member 8538501:
Tried it with solid explorer /w root privs.

Says its unable to delete/rename files from specified locations.
[OnePlus 6T  Questions & Answers] lazye53:
Try;

https://xdaforums.com/oneplus-6/how-to/adb-oxygen-os-debloat-solution-t4015733
[OnePlus 6T  Questions & Answers] Deleted member 8892904:
Yeah only MixPlorer works.
[OnePlus 6T  Questions & Answers] Deleted member 8538501:
This! :D

This has indeed made my life a lot easier.

Much appreciated, thank you!
[OnePlus 6T  Questions & Answers] lazye53:
You are welcome :p