yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Wants2Learn:
Hello,

I'm not sure if this goes here or where actually. When I did a search on the site " LineageOS MicroG Drivers / LineageOS Essential PH-1 / Essential PH-1 Drivers" only LineageOS popped up. If this isn't supposed to be posted here, please inform me and I'll remove it, and please tell me or suggest where this post should live.

So, I'm 100% new to this. I have a Essential PH-1 that now has LineageOS MicroG Mata 16.0 on it. I was walked through the installation from a helpful hand on reddit. I learned alot and Life was GREAT !! I recently ( yesterday ) had some PC issues, and completely wiped the entire system. Now, with my very very limited knowledge I'm trying to put adb - fastboot and TWRP back on my computer, so when updates come around or whatnot I will be ready.

I've achieved having getting adb and fastboot to work or so it seems that way when I execute the commands .\adb.exe devices the output is the same from before. This is where I assume its the drivers bc when I execute .\adb.exe reboot bootloader I do reboot into the bootloader but my phone in windows goes from the connection of PH-1 to disconnected and MATA is connected, but says there are no drivers. So, my phone simply sits in the bootloader mode and I'm stuck there. When I go into device manager in Windows I the little yellow caution sign under other devices on Mata / PCI Serial Port / PCI Simple Communications Controller.

I have searched and there are so many sites that pop up, I'm not sure which one is legit or not. I hope I was clear explaining all of this. I really need any help, suggestions, or anything at this point. Its that frustrating feeling that I can't find that one simple thing ( assuming it drivers) to fix this issue.

Thanks Everyone !!
[Android Software Development] Keule-Tm:
I would have a look in the respective forums of your device for driver and TWRP issues. This is likely not connected to LineageOS or MicroG.
[Android Software Development] bege10:
On Samsung Galaxy S5 Plus (SM-G901F), LineageOS for microG 16 the display freezes after deactivating GPS. Currently it looks like this does not happen if Mozilla backend is deactivated and only the installed local location service works. Maybe there is something wrong with that location service, but I need some more investigation to be sure.
[Android Software Development] kurtn:
Where do you deactivate GPS?
[Android Software Development] Keule-Tm:
Location > "Energy saving mode" or something like that (German: "Energiesparmodus").

Either of the other two will depend on GPS (at least partly).
[Android Software Development] kurtn:
Sounds like lineageOS 15.1
[Android Software Development] Keule-Tm:
Well, err, actually it's 14.1 ?
[Android Software Development] Wants2Learn:
I did I finally figured it all out and got everything up and running again.
[Android Software Development] bege10:
I was not clear enough. I meant this:

If I use navigation with GPS everything works fine. But the very moment I deactivate location in the quick tiles the UI freezes and after several minutes the phone reboots. This does not happen if Mozilla backend is deactivated in the microG settings.

Beside Mozilla location service I use Dejavu and GSM location service which both use local databases. But I did not yet test every combination of these three and online/offline mode to exactly say in which the phone freezes resp. not.
[Android Software Development] kurtn:
Sounds like something is broken in Mozilla location. Do you block some internet traffic? Has Mozilla all permissions? What's your device?
[Android Software Development] Topicat:
For some reason my Galaxy S4 with LOS for MicroG 16 would not update via the settings updater. Had to update via "Sideloading from Recovery" (https://wiki.lineageos.org/devices/jfltexx/update)

Problably a bug from LOS right?
[Android Software Development] kurtn:
Probably outdated twrp. Or are you using lineageOS recovery?
[Android Software Development] Topicat:
Yeah I'm using LOS recovery.

EDIT: Ok I just ****ed up the phone. Tried to encrypt through the settings and now it says the Android system might be corrupt...

Need to do a factory reset. Thankfully I have almost all my data backed up.
[Android Software Development] kurtn:
Not a bug. I think it's a feature of lineageOS recovery. They check integrity of ota file and refuse to install anything else than official signed lineageOS.

You can export the update and in recovery tap apply.. Choose.. LineageOS.. And get signature verification failed. Install anyway works
[Android Software Development] kendallgreen:
No update for lineage4microG nash (Moto Z2 Force) since 1/9/20. any idea why or when the next update will come?
[Android Software Development] kurtn:
That's a job for [MENTION=8701777]ncorna[/MENTION]
[Android Software Development] Topicat:
[MENTION=8031265]kurtn[/MENTION] yup, that is exactly what I ended up doing, including the failed authentication haha. Maybe there should be a warning on the LOS for MicroG website that the updater either doesn't work or may not work. It just makes it even harder for more casual people to get into the "scene".

Since the latest update (at least I think that's when it started) I've noticed the app Signal has become quite sluggish. Plus now the phone has a bug where sometimes it shows as if I don't have any SIM card in the phone.

Do you guys know how I can get in touch with the developers of LOS for my phone model? Basically how can I report bugs that are not related with MicroG?
[Android Software Development] kurtn:
[MENTION=3044346]arco68[/MENTION] is active in XDA
[Android Software Development] Topicat:
Today I finally tested GPS/Location on my Galaxy S4. I tested with OsmAnd~ and with an app to pay parking in the city. With OsmAnd~ the phone finds a location nearby but when I try to set a destination and drive, the location doesn't update. It stays stuck in that initial point.

With the other app, the option to find my current location doesn't show up. It's the only app I have that is not from F-Droid so I guess they use some Google technology that microG is not spoofing.

Any tips on how to make location work? I have both the backends activated by the way.
[Android Software Development] kurtn:
Try satstat app to decide what location you see

Mozilla needs network. GPS needs good sight and much time for first fix in S4
[Android Software Development] Topicat:
Could you be more clear on what I should do with SatStat? I don't have a problem with the first location "fix". The problem is the location doesn't update as I drive around in the car.

Thanks.
[Android Software Development] kurtn:
Go to map and see color
[Android Software Development] phivo_:
I would also vote for that. ;)

Especially as with the update from 20200109 fingerprint reader does not work.

My other nash with newer lineage version (20200121 and 20200203) and OpenGApps(nano) works fine.

Big Thanks for the work anyway! :good:

Regards

Phil
[Android Software Development] Topicat:
Finally took the time to try it out. Now it seems that my phone doesn't even get an initial position fix. Either with SatStat or OsmAnd~.

EDIT: Ok I got a position fix and it was blue on SatStat (location from network provider). The GPS picks up satellites but never fixes a position. Is it some problem with my phone or is this normal on S4 GT-I9505?

EDIT2: It seems like my phone model is not the only one with GPS problems on LOS: https://gitlab.com/LineageOS/issues/android/issues/1132
[Android Software Development] pmko1917:
Lineage os 15.1 with microg for Moto g4

Hi

I wanted to know if there is a Lineage os 15.1 with microg for Moto g4?

Thanks
[Android Software Development] kurtn:
Like that? https://download.lineage.microg.org/athene/
[Android Software Development] pmko1917:
Thanks!!!
[Android Software Development] ldoolit:
Nash is only one of the missing builds

nash is only one of four or five failing builds.

See my "issue" #71 on docker-lineage-cicd (github, I can't post a link here).

Where are "we" supposed to get information about build status, and is there any way to help?

If I were to build an image myself (not impossible) that would change the signing keys, which is more than a small inconvenience these days.
[Android Software Development] kurtn:
Please PM me, if you are willing to maintain the build server.
[Android Software Development] ldoolit:
I might be able to help some. Details in PM.
[Android Software Development] k8n:
Updated builds for dipper?

Any chance to get current builds for dipper?

(especially regarding the security updates that were included)

Previous builds were once a week, so just wondering if there is anything specific preventing the new builds?

Also big thanks to the whole microg team for the best ROMs ever!

Is there some way to support you? (small donations etc.., didn't see anything on microg.org..)
[Android Software Development] ldoolit:
I have the same question but for a different device.

The builds that failed last week are

* nash

* payton

* dipper

* gemini

If anyone knows how to access the build logs, so k8n and I can take a look and help diagnose the failure, please explain!
[Android Software Development] hussaint:
Does anyone have problems with OTA updates when their device is encrypted?

I have a OnePlus 2 running LineageOS for microG and the device is encrypted. I have TWRP 3.2.1.

If I do an OTA it reboots to recovery automatically and performs the update but then goes into a boot loop. The only way out I have found is to boot to recovery, wipe the system and data partition (able to keep internal storage) and flash the rom update fresh. Of course I then have to reinstall all apps.

I doubt this is specific to LineageOS for microG and would probably be the same for straight LineageOS .

This has happened to me on 4 successive attempts with LineageOS for microG 16. As such I tend to update infrequently for the fear of having to reinstall apps and setup again.

Some may say take a backup and restore apps. However, I know from experience that apps do not necessarily register for push notifications correctly with LineageOS for microG if restored rather than installed fresh. (I use Titanium Backup).

In case there might have been a fix in some code, the version I am currently running is LineageOS for microG for OnePlus 2 build date 31/10/2019. I can't remember the version I had installed prior to that which resulted in my boot loop when upgrading to this version.

Anyway, it's now Feb 2020 and I'd like to get patched up without going in to a boot loop next time and having to wipe my system and data partitions and start installing and setting up apps again.

Does anyone have any ideas how can perform an update on an encrypted device and avoid a boot loop? If not, maybe someone else can let me know if they have a similar experience with a OnePlus 2 or any other device, OR, if indeed it has worked for them.

Many thanks in advance to anyone who can shed any light on my situation.
[Android Software Development] kurtn:
Only some ideas for failed ota

- twrp version is too old for handling encrypted phone

- encryption and ota does not work for your device

-you installed addons, maybe suggested by twrp that break ota.
[Android Software Development] hussaint:
Thanks for giving feedback. Thoughts...

TWRP is latest for this phone and handles encryption in that it requests password without a problem and can then access storage. When having to flash ROM after loop, I am doing so to partitions after in decrypted storage.

Hadn't thought about my phone not supporting OTA when encrypted per se as none of my searches have uncovered any such occurrences for any device, but would love to build a picture of what others are experiencing. Is your phone encrypted? If so, does it work with OTA ? If so, what phone.

I have not flashed anything else via TWRP not installed any additional root modules but I have rooted my phone using Magisk

Any further thoughts from yourself or anyone else would be gratefully received. I would especially like anyone to feedback if OTA updates have our have not worked for them with encrypted storage.
[Android Software Development] githyanki:
Have you tried flashing the update rather than doing OTA update?

I always do that rather than using OTA.
[Android Software Development] kurtn:
Yes, magisk is one of the addons I had in mind. Try addonsu instead.

I don't encrypt my phone. I've seen too many bug reports in the past.
[Android Software Development] hussaint:
Thanks. On next update I will try simply downloading, then reboot to recovery and then flash from recovery. I'll report back in any case (maybe a couple of weeks as its my daily driver).

---------- Post added at 04:14 PM ---------- Previous post was at 04:10 PM ----------

I've not gone down the road of addonsu since I first tried Magisk, as the as the control with Magisk is so much better. Indeed, I believe LineageOS are dropping addonsu and propose users go with Magisk for LineageOS 17. This was written up in XDA article https://www.xda-developers.com/line...-addonsu-implementation-favor-magisk-manager/
[Android Software Development] kurtn:
Fake news from xda. The lineageOS way to do root things in 17.1 is over adb. They will continue to refuse bug reports with magisk installed.
[Android Software Development] hussaint:
Manual dirty flash of updated ROM from TWRP with device encryption and Magisk installed worked perfectly. Initiating from OTA update menu in settings seems to be the problem. I have no doubt this is either device encryption for my OP2 and/or Magisk installed... not in a position to debug further and state exactly which it is as this is good enough and is worth a try for anyone else who experiences a problem with OTA updates on an encrypted device with (or without) Magisk installed.

Thank you for the suggestion [MENTION=1631192]githyanki[/MENTION] !
[Android Software Development] Hetherington:
Had the same problem on Xiaomi Pocophone F1 (beryllium). Problem gone after update from 20200127 to 20200224.
[Android Software Development] bege10:
Thanks for the notice. Because for my phone (Samsung Galaxy S5 Plus (SM-G901F)) the latest version is 20200219 I'll wait for the next update and hope to have it solved, too.
[Android Software Development] ldoolit:
weekly rebuild status

The L4M build run that started on 2020-02-24 seems to have stuck/crashed on I01WD.

Th good news is that dipper and gemini builds succeeded, so these are (probably) refreshed with the 2020-02-05 security patches.

The bad news is that nash and payton are still woefully out-of-date, with no new information on whether or not their build will succeed.
[Android Software Development] bigsatan:
Still have the same issue with version 20200302 on POCO F1
[Android Software Development] KilgoreTroutMask:
No new builds have posted for payton / Moto X4 since January. Issue is posted to the Github page also.
[Android Software Development] Master One:
I am sorry for jumping right in and in case this should have been mentioned previously, but with one of the recent weekly updates to LineageOS 16 for microG for the OnePlus 5 and OnePlus 6 the folder /system/app/webview (= /system/system/app/webview on the OnePlus 6) has disappeared.

That's the folder the Bromite SystemWebView APK (renamed to webview.apk) has to be copied to.

I am not sure what the reason is for this folder to have disappeared, and for now I have created a folder named webview in which I have put the webview.apk which I then copy over to /system/app/ after every ROM update, but I'm curious why that folder supposedly is not needed anymore in a standard installation of LineageOS 16 for microG.

Any ideas what's up with this?
[Android Software Development] kurtn:
Hmmm? Maybe [MENTION=4187311]Setialpha[/MENTION] has an opinion to that.
[Android Software Development] guest4711:
It's probably moved to /system/product/app/webview (or /product/app/webview).
[Android Software Development] Master One:
Indeed, it's now in /system/product/app/webview. Any idea why that changed? So that's the folder to copy the renamed BromiteSystemWeview.apk then instead of copying the created webview folder containing the renamed BromiteSystemWeview.apk to /system/app, right?
[Android Software Development] kurtn:
It's all here in XDA.
[Android Software Development] jeisonp:
Can you add support for the LG G2 Mini smartphone (g2m) too?

Thanks!
[Android Software Development] hb045:
Bootloop with WiFi on

Hi,

Everything works fine (and self-check shows 100%) until i switch on WiFi: as soon, as the phone is connected via Wifi, it freezes for 1-2sec, then it reboots. When it's up again, it again connects to the wifi, and ... reboots.

Xiaomi MI5S, wiped everything before installing lineage-14.1-20171116-microG-capricorn

Any ideas for workaround/fix? Would love to use this ROM, but obviously not possible like that...

Cheers, HB
[Android Software Development] kurtn:
You can try to switch off GSM location services in microg NLP settings. If that doesn't work you should check with official lineageOS. Try to find similar build date.
[Android Software Development] Subhojit:
I have installed Lineage MicroG rom on my Nexus 6P.

Now, that it has encrypted my device, will it wipe out the internal storage if I flash any other room which doesn't not encrypt by default?

How do I decrypt my device?

Please advise.

TIA
[Android Software Development] mtbbobo@googlemail.com:
Hi,

would it be possible to build it for Maguro ? (old Google Nexus)
[Android Software Development] Simon94:
All valid device requests are included in next build i just started now ;)

Building CM-13.0 is not possible as of now, but we are working on it.

Regarding Z00A build: I checked the logs and found out, we have a missing dependency in our docker container. We're going to fix that, maybe this or next build.

Best Simon
[Android Software Development] queloo:
Possible to add LG G6 "h870" ?
[Android Software Development] Fuzzypumper:
What the...I factory-reset my LG V410 before installing lineage-14.1-20171118-microG-v410.zip, but upon reboot I find that this is not the microG ROM at all -- it's regular LineageOS with no microG Settings...still using Google Play Services and such. I don't get it.
[Android Software Development] fixios:
Had the same behavior and was successful after wiping System before install as well.
[Android Software Development] guenterlause:
huashan

I was so waiting for LineageOS+MicroG! Thanks a lot!

Can you please include huashan (Sony Xperia SP) builds?
[Android Software Development] fm0:
Could you add builds for Motorola Photon Q (xt897) please?
[Android Software Development] kurtn:
Quick counting result: We have reached more than 1000 active installations. Is this a reason to keep microG in german Wikipedia?

https://stats.lineageos.org/model/bacon/	171

https://stats.lineageos.org/model/i9300/	109

https://stats.lineageos.org/model/mido/	183

https://stats.lineageos.org/model/osprey/	102

https://stats.lineageos.org/model/klte/	95

https://stats.lineageos.org/model/titan/	47

https://stats.lineageos.org/model/kenzo/	140

https://stats.lineageos.org/model/athene/	83

https://stats.lineageos.org/model/hammerhead/	132
[Android Software Development] SlaveJobs:
Please add i9305 to the build list.

Thanks
[Android Software Development] Fuzzypumper:
Yeah -- tried again, even doing a dalvik/cache wipe after install just for good measure (don't just wipe it -- wipe the hell out of it! :D)

That did the trick. Looking forward to getting it set up and running smooth!

Thanks again to you for your help, and to the developer for their work on this LOS variant!
[Android Software Development] rohitdave:
Which version of MicroG / Nanomod installed with this ROM, the version with Google play store around 28 MB, or the version with Fdroid only around 5 MB.

I ask this because I have a number of paid play store apps.

Presently I use the MicroG version where play stare is installed on the official RR ROM with the patcher and it works well.

However would like to try this ROM.

Thanks
[Android Software Development] kurtn:
This ROM comes without play store. First thing I would try is to install yalp store from f-droid. In yalp store you can login with your Google account and try access your paid apps.

PS.: there is no nanomod in this ROM.
[Android Software Development] bojack_horseman:
Can you add galaxy tab 3 8.0 codename sm-t310?

Thanks
[Android Software Development] RockStar8:
I was thinking if you could add rootless substratum support to this ROM. LinageOS devs probably won't add it. I wish you could add it! Thanks for your awesome project and effort.
[Android Software Development] LibertatisPrius:
Could you please build for the w7 (LG L90)? Thanks!
[Android Software Development] guest4711:
I noticed it on LOS17 a few weeks ago. And yes, I replaced its contents using bromite and it works.
[Android Software Development] the_Pan:
Hi everyone! Coming from AOSIP, I'm now on the latest LOS16-weekly for essential ph1, but experiencing a very poor battery life(about 10% per hour). For me it seems LOS is not using the deep doze at all, until I battery-optimise the microg core. Of course I can't get any push messages then.

Is this an "normal"/known issue on los for microg?

What else I can I do to get back an normal battery consumption?
[Android Software Development] githyanki:
That's unusual. I got about 1%/hr idle drain. Do you have the latest bootloader and radio installed?

Did you do a clean install? (Wipe system and data)

Anything else installed?
[Android Software Development] the_Pan:
Yes I did an clean install and the system is full setup, so there are other apps installed as well. But as I wrote, if I left microg-core unoptimized, you can sit and watch the battery drain. If optimized, I loose about 6-8% over night(~ 8hrs), which is normal to the phone, at least it was on AOSIP with the same apps installed.

EDIT: Strange, after rebooting deep doze again won't apply, even with optimized microg-core?:confused:
[Android Software Development] githyanki:
N/m.