yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III General] bengalih:
This is a general question about people's experience with Internet speeds on the device.

I have used several different ROMs, both stock and cooked and fine that Internet browsing is very slow.

I usually am getting either 3G or H coverage with 3-4 bars. If I open up the forum site for instance, it could be a good 2 minutes before the browser is responsive enough for me to type anything in. It's almost like the device is so busy rendering the page that it can't even download.

I don't think this is a speed issue, because when I tether my laptop I generally get pretty good speeds, and that same page will come down on my laptop in 15 seconds.

I know that PIE isn't the best browser, but is it really PIE that is causing such slow browsing? I honestly haven't tried opera yet as it seems to always be in a beta and I have read posts about many issues with that browser as well.

Do other's have such a slow time browsing? It's almost embarrasing when I have to pull my device out to look for something quick and it takes 5-10 minutes to get some info of the web.

Again, I don't think this is radio or ROM specific, since I have more or less the same experience on all... I am wondering if there is something up with the connections in my area, although I find this hard to believe as I don't live out in the boonies.

thx.
[Tilt, TyTN II, MDA Vario III General] Isaygarcia:
Use opera :D

yes iexplorer is slow..

i use opera and 3G :D its fast !
[Tilt, TyTN II, MDA Vario III General] bengalih:
I guess it's time I give it a try. There are apparently some new versions floating around from the Diamond? Do these work or should I stick with an older one?

If you could recommend which version I should try for a better experience I would appreciate it. I'll then comment on the differences in speed.

thx
[Tilt, TyTN II, MDA Vario III General] Isaygarcia:
i use the "old" one, but the Diamond one seems to work :)
[Tilt, TyTN II, MDA Vario III General] redbandana:
I'm trying the newer one. I like the 8.5 version better ( I think that was the one). It was more user friendly.

However, whenever I attempt to open this forum on my device it takes about 3-5 minutes just to get into the Kaiser section.

I typically only use my internet browser for information that can be found in any daily newspaper, which only takes a minute or two during each session to find.
[Tilt, TyTN II, MDA Vario III General] bengalih:
I think there might be some type of script on the (forum) page that slows it down. Once or twice after about 2-3 minutes of waitintg PIE popped something up that said a script was taking longer than expected.

What is so bad is that it locks the whole browser not letting you click "stop" and just browse what has already bee downloaded (which is usually enough). When it does stop, it usually takes you back to last page to start all over again :).

I guess I shouldn't be so surpried to think that PIE is crud.... although not all pages are horrible...google and google news and wikipedia aren't too horribly slow.
[Tilt, TyTN II, MDA Vario III General] NFRCER:
Bengalih Gsleon3 posted the opera 781 diamond build. In there you will find the 1004 build in pages 3 or 4. I recommend you use opera too, either one will do good, im currently browsing and posting this comment from opera 9.5.

yeah, i have that problem with Pie too, hence why i found my new default browser, opera 9.5.

here is the link:

http://xdaforums.com/showthread.php?t=393947
[Tilt, TyTN II, MDA Vario III General] bengalih:
i am typing this now on 9.5 on a slower Edge connection and it is much faster.

however it does seem a little hard to navigate especially without the stylus.

am i corect in assuming you can't interact (click) on the scren when it is zoomed out? that you must first zoom in?

also i miss the URL dropdown like on PIE are there aditional shotcuts so you don't need to go back into the settings menu each time?

thx
[Tilt, TyTN II, MDA Vario III General] NFRCER:
yeah i noticed that too, i gotten used to the opera functions, indeed sometimes is hard to click links without the stylus. can you provide me a link to the drop down menu? AFAIK even the search button up the page works. it maybe different i guess.

hey all browsers have its shortcoming and i wished this one use the touch flo scrolling.
[Moto G5 Plus Questions & Answers] Shonilchi:
Is there a way to remove a custom sound/audio mod in any of the custom PIE roms? Should I check something in the ETC folder as well?
[Moto G5 Plus Questions & Answers] Wolfcity:
Not enough information.

What mod?

How installed?

What ROM?

Rooted?

You have to help the users to help you.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] pipyui:
[IMG="lineageos_logo"]https://upload.wikimedia.org/wikipedia/commons/thumb/e/e5/LineageOS_Wordmark.svg/1920px-LineageOS_Wordmark.svg.png[/IMG]

What This Is

This is a personal project to get Lineage OS running on my Pixel 3a. As such it is provided as is, though I will endeavor to provide regular builds and offer limited support as I am able.

What's Been Tested

This is my daily driver, so I've flashed ElementalX kernel and openGapps Pico over stock.

T-Mobile (at least), camera, wifi, bluetooth, gps are used regularly without issue.

What Was Not Tested

Root

Squeeze sensor

Gapps beyond Pico

Known Issues

eSIM doesn't work and has been removed

If flashing Gapps, an app downloaded at first-time setup Data Transfer Tools will crash constantly and needs to be uninstalled. This may mean you can't transfer data from an old phone to this one via setup.

Downloads

Lineage OS 16.0 Unofficial

Installation

I have not had success with an installable zip for TWRP yet, so the rom images must be flashed via fastboot. You should be familiar with fastboot before attempting to install this rom. It is recommended that you back up your current OS before installing a new one.

Installing this or any rom will void your warranty.

After unlocking OEM and your bootloader, boot into bootloader either with fastboot reboot bootloader or by holding VOLUME DOWN + POWER from power off, plug your phone into the computer.

If running on a linux machine with fastboot installed you can execute the flash-all.sh script included in the download. Alternatively or otherwise:

fastboot flash boot boot.img

fastboot flash dtbo dtbo.img

fastboot flash vbmeta vbmeta.img

fastboot flash system system.img

fastboot flash vendor vendor.img

fastboot -w (to wipe cache and data)

After installing, Gapps (ARM64, 9.0, see note in Known Issues), kernels, Magisk (UNTESTED) and other zips can be installed as normal via TWRP.

I Wanna Go Back

Up-to-date stock images are provided by Google and can be reflashed from bootloader.

Just follow the instructions at the top of the page.

Sources

LineageOS

Vendor proprietary packages (thanks to Dirty Unicorns and ZVNexus)
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
Nice work! I'll have to wait until tonight to test it.

I've been working on my own builds. The June firmware worked well, but after updating to July firmware and vendor, WiFi calling isn't working. The camera had always been a little fickle. I can't wait to test...
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] koichirose:
Does it support Google Camera fully (with motion and everything)?

Any hope of making it official?

Great work!
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] pipyui:
Let me know what you discover! I haven't tested wifi calling (wouldn't even know how) wifi calling works fine on T-Mobile, and while I looked through my logcat, I can't say I was entirely confident in my ability to read it...

Mostly 'access denied' errors on some gpu libraries and an error reading the squeeze sensor config (but only when I'm connected to adb). :confused:

Thanks! I hadn't tested google camera motion till now, but it doesn't look to be working works with Google Photos installed. Haven't had trouble with pictures and video otherwise through it though.

In regards to making it official, maybe with some polish. I'm new to the android dev scene so not too confident in my ability to maintain a project like this yet. :p

But I'll look into the process.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
Yes, I get a lot of selinux errors in the logcat too. I haven't had time to research them.

The squeeze issue is odd, perhaps some uid is conflicting. I think these are set up in the init files.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] pipyui:
Nevermind [MENTION=2781306]koichirose[/MENTION], camera Motion works fine once I installed Google Photos. :good:

It's odd that it only shows up when I connect to logcat via adb. Local terminal logcat doesn't show me these squeeze errors.

Also, wifi calling working on T-Mobile :good:
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Chronzy:
Thanks for building. I had issues installing apps from the play store, lots of download pending despite force stopping play store and several reboots. Also magisk doesn't appear to work when flashed through twrp. I didn't try patching the kernel through magisk manager though. Good first look though!
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] pipyui:
I ran into this same issue - had to remove Data Transfer Tools (don't need root for this, since it was downloaded by gapps) and do a cache wipe to be able to download apps again. I think it blocks you from using the play store until you complete google's first-time setup, and this app blocks that (not to mention it crashes frequently).

I'll test out Magisk when I'm able. You may need to enable root access to apps in dev settings, but I'm unsure.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Tiebe:
OMG thank u so much! Was waiting for this forever, hope you can make twrp zip
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Tiebe:
Getting "Sim not Found" on both rooted and unrooted
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Uzephi:
Have you checked OP? eSIM doesn't work. Need physical SIM
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Tiebe:
I have a physical sim. I solved the problem tho. I just had to reflash the stock radio image
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] dwa91:
Thanks for putting a build together! Provides even more incentive for me to make the switch over to a 3a :D Keep up the good work.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] GuestK00262:
Is the device showing as certified without root?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Dreamsocks66:
Could anybody who has been testing out this rom give me any idea of what their battery life is like? I feel like mine has been much worse since flashing this. Dropped 10% overnight with nothing running and in airplane mode.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Geo411m:
any chance for a 3aXL port? I've been wanting to do one myself but I'm in the middle of a kitchen remodel so not much time to setup a build environment.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] pipyui:
It is not certified.

I get about 2 days out of a charge on ElementalX kernel, but I'm sorry to say I've hardly tested vanilla LoS kernel.

In my experience I usually have to go through a full charge cycle on a new rom then restart my phone for battery life to stabilize.

While I should be able to build an XL port, I won't be able to test it myself. Let me know if you'd like to run a build in beta.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Geo411m:
I'll test for you
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] pipyui:
Neat, I'll get a build together for ya tonight then.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] GuestK00262:
Any chance of a flashable zip for the official twrp?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] CAExempt911:
Has anyone tested if root works?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Pogo:
Yes it work fine, just flash Magisk from TWRP.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] ZVNexus:
Wrong thread lol
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] :
Lol i meant flashable zip of this rom
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] pipyui:
Some trouble with vendor binaries, still cooking.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Geo411m:
Awesome, thanks so much.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] klingels:
I can't flash the vendor.img

It hangs without feedback at the last line of the script.

+ /home/aUser/dev/Sargo/platform-tools_r29.0.1-linux/platform-tools/fastboot flash boot boot.img
< waiting for any device >
Sending 'boot_b' (65536 KB) OKAY [ 2.424s]
Writing 'boot_b' OKAY [ 0.428s]
Finished. Total time: 3.426s
+ sleep 10
+ /home/aUser/dev/Sargo/platform-tools_r29.0.1-linux/platform-tools/fastboot flash dtbo dtbo.img
Sending 'dtbo_b' (8192 KB) OKAY [ 0.360s]
Writing 'dtbo_b' OKAY [ 0.118s]
Finished. Total time: 0.706s
+ sleep 10
+ /home/aUser/dev/Sargo/platform-tools_r29.0.1-linux/platform-tools/fastboot flash vbmeta vbmeta.img
Sending 'vbmeta_b' (4 KB) OKAY [ 0.120s]
Writing 'vbmeta_b' OKAY [ 0.064s]
Finished. Total time: 0.382s
+ sleep 10
+ /home/aUser/dev/Sargo/platform-tools_r29.0.1-linux/platform-tools/fastboot flash system system.img
Sending sparse 'system_b' 1/6 (262140 KB) OKAY [ 9.239s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 2/6 (262140 KB) OKAY [ 9.029s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 3/6 (262140 KB) OKAY [ 9.009s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 4/6 (262140 KB) OKAY [ 8.779s]
Writing 'system_b' OKAY [ 0.370s]
Sending sparse 'system_b' 5/6 (262140 KB) OKAY [ 9.239s]
Writing 'system_b' OKAY [ 0.371s]
Sending sparse 'system_b' 6/6 (163656 KB) OKAY [ 5.729s]
Writing 'system_b' OKAY [ 1.561s]
Finished. Total time: 54.634s
+ sleep 10
+ /home/aUser/dev/Sargo/platform-tools_r29.0.1-linux/platform-tools/fastboot flash vendor vendor.img
Sending sparse 'vendor_b' 1/3 (262140 KB)

I cannot even quit my terminal via Ctrl+C.

Yet LineageOS is booting up afterwards and everything seems to be OK, but I guess I miss the vendor.img.

Any ideas?

Ubuntu 19.04, tried to run the script in zsh and bash.

fastboot --version

fastboot version 29.0.1-5644136

Installed as /home/aUser/dev/Sargo/platform-tools_r29.0.1-linux/platform-tools/fastboot

Connected via USB-C in Thunderbolt 3 port (with USB 3.1 Gen 2 support) of XPS 13 9350 (0704).
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
Try rebooting your laptop and just flashing the vendor partition.

I think this version will work with either version of vendor- stock or aosp. If you are coming from stock or most other ROMs, you will probably have the stock vendor. If you flash this version of lineage, you will have the aosp vendor.

I think you call tell with

getprop ro.product.vendor.model

stock will have something like Sargo by Google, aosp will be aosp on Sargo.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] klingels:
Thank you for your reply.

It hangs even even after a rebooting my laptop. When I try to restore stock image https://dl.google.com/dl/android/aosp/sargo-pq3b.190705.003-factory-55d7c2c4.zip it is hanging at the same line and strangely enough also in this case I can boot up stock which seems OKish.

adb shell getprop ro.product.vendor.model
Pixel 3a
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
Maybe try re-downloading the vendor image? And just flash that - fastboot flash vendor vendor.img

Otherwise, it's probably OK, as long as you don't start flashing exotic vendor images from the dark corners of the web. Once this gets packaged as a flashable zip, it'll be easier to install.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] klingels:
I tried to install the extracted vendor.img from the stock image zip via `fastboot flash vendor.img` - no luck.

I'll nevertheless try to use it as a daily driver from today on.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Geo411m:
How's the stew ^_^
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
Not OP, but I've been cooking sargo. I'm trying to build bonito currently, but it's a blind build. I just changed sargo to bonito and removed any files that caused errors.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] pipyui:
Sorry, vanished for vacation this week, back on it tonight (tho it sounds like gee one's already putting the garnish on his build)

Awesome!

I'd been having trouble with bonito vendor bits (I think? can't be too sure cooking blind as I am myself). Excited to see what you got!
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Geo411m:
gotcha, it's cool. I pulled out one of my laptops and got a build environment setup. Since I haven't built lineage in a long time I'm having trouble as well. Got Breakfast bonito going with no errors but cant get proprietary stuff without errors. maybe we can exchange notes.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
I did hear that the battery drain was higher than other roms, so that's not surprising. It might lose as much a 1%-2% per hour while idle.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Pogo:
[MENTION=6840005]pipyui[/MENTION]

I'm using Lineage since day one as my daily driver and have no complains. I've been using Lineage (and CyanogenMod) on all my Android phones and tablets at least for a while and I'm happy user. This version work surprisingly well and is already pretty mature and stable.

Just have few questions:

1. will e-sim support be added in the future versions?

2. any chance to add Randomize MAC Address (wi-fi, Developer Options)?

3. any plans for releasing ROM without Gapps included? (I'm using microG)

4. the Setup->Display->Style->Style option 'Automatic {time of the day)' it seems doesn't work or I don't know how to set it up. Any insight?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] kop316:
Hello!

I was trying to compile this from source to make it myself, and I am stuck on the step:

"$ breakfast sargo"

and I get this Error:

"build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_sargo".

08:03:05 dumpvars failed with: exit status 1

build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_sargo".

08:03:06 dumpvars failed with: exit status 1

** Don't have a product spec for: 'lineage_sargo'

** Do you have the right repo manifest?"

I assume that you place the Lineage.dependencies somewhere, but where do you place them? Is that how you got around the problem?

Thank you!

UPDATE: I solved the Issue and compiled it! I am following up with another post.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
PM sent
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] kop316:
I was able to compile LineageOS from Source with a functional ROM for the google Pixel 3a! I think using this guide as a framework will also get the Google Pixel 3a XL to work too.

https://wiki.lineageos.org/devices/sailfish/build

Follow the above guide until "Prepare the device-specific code"

Where is says

source build/envsetup.sh
breakfast sailfish

Instead, do

source build/envsetup.sh
breakfast sargo
breakfast bonito

Sargo's code is largely dependent on bonito, so this saves a step. Both "breakfast sargo" and "breakfast bonito" will error out (this was the source of my earlier question).

Then, do (This is VERY important and skipped in the build guide, this actually syncs the dependendencies):

repo sync

You now need to run

breakfast sargo

Again! This is because the repo sync did NOT add the kernel dependency. Doing breakfast a second time adds that dependency. Note that "breakfast sargo" will succeed, but trying to compile now will have the compiler error out on "no Kernel to compile".

Now that the kernel dependency is run, sync the repo again:

repo sync
breakfast sargo

This should now have it ready to compile, with the exception of the propreitary files You can then come here:

https://source.android.com/setup/build/requirements#binaries

And download the specific device binaries for Sargo. At the time of writing, I believe LineageOS is on the July AOSP snapshot, so you need to add those binaries. But, adjust for month/build fingerprint.

Add them to the root of the repo (~/android/lineage in the example)

Extract both .tgz files and run them (they are shell scripts to force to you accept the license terms) at the root of the repo (~/android/lineage in the example). Now, run

make clobber

(That comes from here: https://source.android.com/setup/build/building . It recommends running make clobber here.) Now, you are ready to compile! Run:

croot
brunch sargo

and start compiling.

The outputs will be in ~/android/lineage/out/target/product/sargo/

and look like:

lineage-16.0-20190727-UNOFFICIAL-sargo.zip

subsituting "20190727" for date of compiling.

To install, follow this guie:

https://wiki.lineageos.org/devices/sailfish/install

Making the appropriate substitutions of course.

I am not confident that the vendor.img was install, so you may have to flash that via

fastboot flash vendor vendor.img

on the bootloader.

Couple of open things:

- The Bonito dependency looks to be tracked to June instead of July. Not sure what to do to fix that? (As of: 29 July 2019)

- The kernel is pulled from LineageOS versus AOSP. I personally would prefer to get it from AOSP directly. (As of: 29 July 2019)
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
Great write up! I think los without any changes won't build the vendor image so I think you will have to flash this manually. You only need to do it when the rom is updated for the new software (fingerprint/build ID change), or when switching between roms that require or use the stock google vendor image.

I didn't add the qcom binaries to my rom... I'll have to see what is in there.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] kop316:
Thanks!

Right now everything seems to work well for it. The things I see as potential issues are:

- The Bonito dependency looks to be tracked to June instead of July. Not sure what to do to fix that? (As of: 29 July 2019)

- The kernel is pulled from LineageOS versus AOSP. I personally would prefer to get it from AOSP directly. (As of: 29 July 2019)

For the kernel: It appears that it pulls source code from the LineageOS Github (https://github.com/LineageOS/android_kernel_google_bonito). You can pull the AOSP kernel from https://source.android.com/setup/build/building-kernels . So I am thinking there is a way to pull it into the build so you have the upstream kernel.

For the Bonito Dependnecy: AOSP has it in device/google/bonito/ . I am curious as the differences between the AOSP Bonito device and the LineageOS one. Since it is on the June patch levels, you can pull it can probably directly compare on Linux. It looks like there are some extra files and that is it?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
You can change the kernel source in .repo/local_manifests/room service.xml. You'll also need to add a remote stanza to identity the aosp repo. Don't forget to repo sync.

In the device tree, you have to change the kernel source and config in Boardconfig-common.mk.

Also, the lineage build system might get confused so you might have to edit lineage.dependencies so that it doesn't keep trying to pull in the los kernel.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] kop316:
Thanks for the heads up! I will look at it later, my main concern is the official one looks like it was last updated June 6th, and I would like to keep things current. RIght now I have little experience with github, so I guess sometime I will have to figure out merging and all that fun stuff.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] kop316:
I hate to say, I found an issue with it. I was able to recieve SMS/MMS for the first hour or so when it was loaded, but it eventually stopped recieving any. I had to load it into a different phone before I got the messages.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
Is that with your build or mine?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] dpryor88:
Your builds have never done this to me. I use tmobile. Not sure if that has anything to do with it.