yashsingh1/xdaforums huggingface dataset:
[Android Software Development] dced:
I tried both!

So I sifted through the logs, and I'm pretty inexperienced, but it seems like there's a new permission privilege not being granted(?) I got this from a logcat:

W/PackageManager( 2358): Privileged permission android.permission.CHANGE_DEVICE_IDLE_TEMP_WHITELIST for package com.google.android.gms - not in privapp-permissions whitelist

, which causes the system to boot to recovery. Adding

<permission name="android.permission.CHANGE_DEVICE_IDLE_TEMP_WHITELIST"/>

in /system/etc/privapp-permissions-com.google.android.gms.xml seems to do the trick.

However, this change is also not in klte, so I'm not sure if this is the correct fix. :confused: Also, I still seem not to be able to add my Google account, which might be a separate issue though
[Android Software Development] kurtn:
Klte
[Android Software Development] yaomtc:
Does the migration ZIP work with the LineageOS Recovery, or do I need TWRP installed? I haven't used that Recovery before (and I can't until #818 is fixed) so I'm wondering if "Install Update" works the same as TWRP's "Install".
[Android Software Development] kurtn:
Nobody uses lineageOS recovery
[Android Software Development] areshinakya:
Partially true.

Flashing TWRP is not supported on A/B devices, it is always booted via "fastboot boot" temporarily. On those devices lineage recovery handles system updates.

(pioneer for example)

In any case doing advanced stuff needs twrp, no matter if temporarily or flashed.
[Android Software Development] yaomtc:
At a minimum, everyone who does a fresh install of official LineageOS 16 on a Moto X4 has LineageOS Recovery.

Thanks for the helpful response areshinakya, I'll use fastboot for a workaround.
[Android Software Development] carlosfl8:
Hi everyone, IDK if this is the right place to ask so sorry in advance... Yesterday, I tried to flash (Clean Flash) Lineage OS microg for my Honor 5X (Kiwi), I'm using Twrp 3.3.0.0 version (Just realized there's an updated version) but anyway, it turns out the ROM was flashed but I can't pass through the first screen because the phone is unresponsive, I mean the touch screen doesn't work, only the power and volume buttons... I tried to got TWRP recovery and It was the same, the touch screen won't work... So I'm stuck there... I'm not at home and I won't be for a least another month and I don't have a PC to try to flash another recovery image... I read that connecting a keyboard to a OTG cable the touch would "suddenly" work, I don't have any of those! ? / Is there a way to fix it? Thank you.
[Android Software Development] kurtn:
I've seen twrp that started recognizing touch after idle tome screen off.

Or slap your phone on your palm if it's a hardware issue.
[Android Software Development] carlosfl8:
I went to sleep and left it untouched for about 8 hours and nothing happened, still the same... I have slapped the *&-it out of it (but calmly) still, no response. :(
[Android Software Development] _ric_:
OTA-Update 2019-06-17 done, everthing fine

I have done the OTA-Update 2019-06-17 a few minutes ago on my Oneplus One (bacon) and everthing is running fine.

Many thanks to the devs!
[Android Software Development] dced:
So this was just committed yesterday in b2c3b23, and should be in 0617 builds. This fixes the boot problem for gemini and probably a few other devices as well, so give it a shot if builds since the new microg update have not been working for you.

Also, updated commits to GsmCore after the 0.2.7.17455 release has fixed login to Google accounts for me. I can upload my compiled apk based on commit 73fd85a later today if anyone is interested.
[Android Software Development] wilten:
Just bumping if there has been any update on this? I haven't been able to get in touch with however is operating the build server.

Anyone know where I should be looking?
[Android Software Development] Lordlight:
Help me please !!!

How can I odex this ROM ?

My device is running Android 7.1
[Android Software Development] kurtn:
Why would someone wish to odex a rom?
[Android Software Development] Lordlight:
Hmmm

I want more free space on my device .

I don't want to mod or change system ... etc so I want to odex to make device faster.

- Sorry for my English -
[Android Software Development] vildevilde:
Maybe I'm wrong but as I remember a rom needs to be deodexed to be able to have signature spofing to be able to use microG. If that's right you should use a rom without microG,
[Android Software Development] areshinakya:
As a workaround for the boot problem it is also possible to install the update from the f-droid microg repo and then update lineage to the broken build. the f-droid installed version will be used then.
[Android Software Development] kurtn:
Yes and no. If you have a not odexed ROM, you can easily patch for signature spoofing. The whole idea of lineage4microG is to apply that patch before building the ROM. So building an odexed ROM does no harm. Oreo and pie are odexed. Nought is not. [MENTION=9380885]Lordlight[/MENTION] i don't think odex will give you more space in /data partition. To get any profit, you would have to repartition. Not recommended.

The only gain of speed is in first boot after installation AFAIK.
[Android Software Development] Lordlight:
Hmmm

My device is old and for some private reason , I want more free space .

At least 120MB I can have if I odex .

I still want to odex .

Could you show me how to do it, please ?
[Android Software Development] kurtn:
Start reading there: https://xdaforums.com/apps/superr-kitchen/kitchen-superr-s-kitchen-v1-1-50-v2-1-6-t3597434
[Android Software Development] ncorna:
Unfortunately builds for charlotte keeps failing. We had this problem also on our old build server, so I suspect it is an issue from LineageOS.

Sadly I don't have time to dig deeper by myself, if you have any idea here you can find the tail of the build log. Let me know.

(The same issue affects also berkeley, logs are similar)
[Android Software Development] Elder Lyons:
Im on the latest build on Onyx, clean flash with all microg options enabled. When I try and verify safety net it says google play services can not be started, I get an authentication error in Pokemon Go as well when I try to log in. How do I fix this? I tried flashing again but it did not work.
[Android Software Development] kurtn:
In nanodroid there is said:
[Android Software Development] Elder Lyons:
Oh, so we need to wait for an update to Droidguard then, or is there another way to pass safetynet at the moment? :)
[Android Software Development] Lordlight:
I don't see anything related to odex, only deodex ?

Thanks for help !
[Android Software Development] kurtn:
The way to pass safetynet was always: stay with stock ROM. No Google account, maybe.
[Android Software Development] cipojadij:
Hi, can someone confirm if the 06/18/19 build for pioneer work? Last ones caused bootloops
[Android Software Development] LucN31:
Report a bug in snap application

Hi,

I use Lineageos for microG on an Galaxy S5 device (klte). It works fine except some minor problems on apk using google API (from Google play via Aurora).

org.cyanogen.snap is a very nice application that I only see in this ROM, but I don't know were report à bug relative to the directory where photos are saved.

I don't know if this setting is the default or if it is changed when the apk is included in this ROM.

May I have some help to report ?

Luc.
[Android Software Development] kurtn:
Looks like you have an old ROM. Now it is called org.lineageos.snap. It is an original app, not modified by microG people. S5 has good community support here in XDA.
[Android Software Development] kendallgreen:
I hate to be a PIA, but nash didn't get a build last week. I have tried to build it myself from the docker files, but I can't get a lineage 16.0 device list and it defaults to 15.1. I have attached my docker file lineage16microG.txt and I have tried "DEVICE_LIST=nash ", proprietary_vendor_motorola/nash, etc. with the same results
[Android Software Development] piernodoyuna:
applications related to home automation stopped working in the previous version. Changing to google.gsm.3280012 was resolved. In this latest version, this solution does not work. Google home recognizes the account, but it stops working. The associated applications (smart life, Tuya Smart, etc.) do not work either. Any suggestions?
[Android Software Development] LucN31:
Hi kurtn,

Thank's for your help.

I am newbie an I can't post link on this forum.

Since 22 of june my ROM is an updated ROM by OTA on 2019-06-18 update. It seems to be the last version on download section :

https:\\download.lineage.microg.org\klte\lineage-16.0-20190618-microG-klte.zip

In information data about the camera application it is : version 2.02.015(eng.root.20190618.044028-30) of org.cyanogenmod.snap. Is there something wrong ?

I like this apk which have a lot of settings on direct access, is it the same with the new application lineageos.snap ?

The only problem is the folder used to store photos : Android/data/org.cyanogenmod.snap/files instead of DCIM/camera and I don't find howto change in settings.

Luc.
[Android Software Development] kurtn:
[MENTION=4122877]curiousrom[/MENTION] could you please have a look at this?
[Android Software Development] curiousrom:
16.0 Snap Camera Micro SD Card folder

This is normal on LineageOS 16.0 @ the present: in stock Snap camera if > Storage > SD Card is selected it will save photos & videos in: /storage/{Micro SD Card ID}/Android/data/org.lineageos.snap/files/ & S5 dev haggertk is working on some patches to change that as you can see in the LineageOS Gerrit (Active & not Merged yet @ the present): 248663: Snap: Save SDCard photos to legacy path.

So be patient as it will be ready when it is ready. ;)

***
[Android Software Development] LucN31:
Ok, thank's.

Luc.
[Android Software Development] kendallgreen:
Thanks for the 6/25 build for nash. I think I found an answer to my problem building lineage4microG. I followed the directions for setting up the docker image at https://manojnaironline.com/2018/10/12/build-a-lineageos4microg-rom-using-docker-on-ubuntu/ It seems to work building a lineage16.0 version for nash.
[Android Software Development] Sidney Sol:
Please, update security patches for devices with LOS 14.1
[Android Software Development] h4waii:
If any maintainer is reading this, can "shieldtablet" stay on the build roster? Lineage has just dropped official support due to issues moving to 16.0, but monthly security patches are better than nothing.
[Android Software Development] stukka2006:
hi

one question :

if I install this rom https://download.lineage.microg.org/kiwi/

will my device get the normal lineage updates via OTA as usual?

thks for answering
[Android Software Development] kurtn:
You will get weekly ota updates from original lineageOS sources built by microG team. If you install 16.0
[Android Software Development] stukka2006:
thanks for you help!

I have already installed lineage 16 official for kiwi with pico gapps

just to to ensure that I have understood the process:

install the kiwi lineage microg with full wipe

reboot

and afterwards I will get normal updates via OTA from the official lineage 16 for kiwi regularly?

thks for answering!
[Android Software Development] kurtn:
Yes. Wipe /system and /data is best method to get rid of GApps. If you have another method, you can follow installation guide for dirty flashing.

You will not get official OTA updates. But OTA will work exactly the same. MicroG people have set up their own update server.
[Android Software Development] Chris56:
S4 mini GT-I9195I

S4 mini VE variant GT-I9195I

To the wizards that create these great roms:

There are roms for the S4mini, thanks for that. E.g. you find

serrano3gxx

serranoltexx

but not the variant

serranoveltexx (GT-I9195I)

Before they stopped support, also this variant was being supported by lineageos.

Could the person that did the other serrano roms also compile the serranoveltexx variant.

That would be great.

Thanks in advance for the valuable work!!

Chris
[Android Software Development] bege10:
Hi,

some months ago I reported that updates fail. The TWRP log shows error when installing ZIP '@/cache/recovery/block.map'

This can be fixed by wiping the cache, but it is annoying because this error happens with every update on Samsung Galaxy S5 Plus (SM-G901F), LineageOS for microG 16 (Android 9). Do other users with this phone have the same issue? If not, what may be the reason for this problem? I have Play Store from NanoDroid installed (nothing else from NanoDroid).
[Android Software Development] DaniPhii:
I'm still waiting for this pull request to be merged. When it is done, [MENTION=4316015]Simon94[/MENTION], I can tell you so you may add piccolo in the devices list to build LineageOS for microG 15.1 for it, ok? :)
[Android Software Development] wgnix:
LTE Not Working on Google Pixel (Sailfish)

Fresh install of LineageOS+microG on a Google Pixel (Sailfish) with CDMA SIM card on Ting Mobile. Cannot connect to 4G LTE towers and use data. I can only connect to some 3G networks. Calling, texting, web surfing work on 3G but can't do anything on LTE. This phone is not rooted. Did everything Ting knows to do for troubleshooting.

Everything is else is working flawlessly. Ting is shipping me two new SIM cards both CDMA and GSM to try. Any ideas of what I'm missing? Thanks for making this great option for us.
[Android Software Development] kurtn:
This ROM is in most parts identical to official lineageOS. So please have a look in that thread.
[Android Software Development] wgnix:
I posted there but they said they won't help because I'm using an alternative build. Where does one get help for this issue? thanks
[Android Software Development] kurtn:
It is always a good recommendation to start bug investigation with a clean install and try to reproduce the bug. So why don't you start with original build? And keep a backup of your current /system and /data.
[Android Software Development] BenG7:
Hi

I got a new LG phone (H930DS and it is now running lineage 16) so my good old H870 is going to my son so I need to switch back from LineageOS for MicroG back to plain Lineage

1) where can I find the latest plain lineage 14.1 rom - it is not hosted on the lineage site any more

2) any particular steps I should follow (I used migration key when I switched from lineage to lineage for microG - are there migration keys too to go from LµG to L?

thanks

[Edit] indeed, flashing the latest lineageos doesn't do it!

Guidelines welcome

Thanks
[Android Software Development] topaza:
Hi,

I tried to install the patched play store from Shadow53 as I need some apps to verify licenses / in app purchases.

But when I install the zip via TWRP, the play store does not show up in LOS at all. I also cannot find it in /system/priv-app (although I am not sure what exactly is supposed to be in there)

Any ideas how to get the play store installed an MicroG LOS?
[Android Software Development] SGE2010:
LOS for microG 15.1 santoni Self-Check "network-based location" not checked

I have LineageOS for MicroG 15.1 santoni on my Xiaomi Redmi 4x. After clean install I run the Self-Check where I have three check boxes under "UnifiedNlp Status" (see attch.) where every box is checked but for the one on the very bottom: "Network-based location enabled:"

microG Settings --> UnifiedNlp Settings shows me

Configure location backends

Configure address lookup backends

"Configure location backends" shows me "Mozilla Location Service" with the screenshot of "Mozilla UnifiedNlp Backend". Of course als boxes are checked.

"Configure address lookup backends" shows me the Nominatim Geocoder Backend screenshot. As Nominatim APO Server I chose "OSM", because with MapQuest I am asked for a developer key which I don't have.

Do you have any suggestions?

EDIT: Thx to LjL (#microg irc on freenode) for pointing out the solution:

it was not an microG thingy but Android itself under --> Settings --> Security & privacy --> Location is switched from "ON/Device only" to "high accuracy" and now the Self-Check runs perfectly and has all boxes checked :) thx so much
[Android Software Development] SGE2010:
microG and Android Auto?

Now, having a working device (s. post above) my next Question would be if I can get to run Android Auto on my Lineage for microG?
[Android Software Development] kurtn:
Sorry, no

https://github.com/microg/android_packages_apps_GmsCore/wiki/Implementation-Status
[Android Software Development] SGH-i200:
Threema: "Migration from GCM to FCM" is listed in the changelog of the new "Threema 4.0 for Android": https://play.google.com/store/apps/details?id=ch.threema.app&hl=en

Can I use the new version with the current official microG version?
[Android Software Development] ralle-666:
Works for me without problems
[Android Software Development] jayloofah:
So, I've been testing this on Sailfish and have found only a few issues (that seem to be quite frequent issues most encounter) and wanted to ask about the status/other development info about this one functionality.

GCM - I realized something was up with Signal/Messenger and even after multiple attempts at enabling GCM properly, uninstalling, reregistrating - it's random whether GCM messages are received consistently under any particular environment (I've noticed that Androids Power Saver mode breaks incoming GCM). I think Signal itself is responsible for some finicky behavior but I feel like the incorporation of GCM resistration/activity could be more transparent per app.

Side note - how do I keep microG updated? Stick to F-Droid's updates? Thanks ahead of time to those far more informed who could shed some light on this.
[Android Software Development] kurtn:
This ROM ships with a f-droid that has microG repository included. There you get gms core updates.

No idea about messaging. I use WhatsApp without gcm. Just disable battery optimisation.
[Android Software Development] panaderodc:
I am in the same position with my ph-1, mata. No option to update prl or profile, either. Did you find a solution yet?

thanks.
[Android Software Development] kurtn:
Ask [MENTION=9125253]jayloofah[/MENTION]
[Android Software Development] panaderodc:
Apologies, I apparently quoted the wrong post. Meant this for [MENTION=10024320]wgnix[/MENTION].

Appreciate the answer, though. I have run into a wall with this. One thread saying CDMA is closed source, so no 4g on los, but I seem to recall 4g on a previous phone with los.
[Android Software Development] kurtn:
Closed source is no show-stopper for lineageOS. It only makes device maintainer's job harder. To get an official status, all that binary code has to be tricked into working with lineageOS.
[Android Software Development] Exabyter:
I currently use LoS for MicroG v14.1 on a LG v20 using CDMA. (Verizon)

It works "OK" but some things are weird. (Eg, you cannot see the active phone # in the usual place in settings, and oftentimes signal-strength bars bear no resemblance to reality)

I've resigned myself to the fact that probably 99% of open-source Android ROM devs have no access to a CDMA carrier and no CDMA device so they do not bother to test on CDMA devices at all. Meaning if they release a ROM compatible with such devices CDMA usage is "as-is/where-is" or they just never release such a ROM at all.
[Android Software Development] n76:
Could be. The issues you mention seem more like Lineage than microG.

I've read that Verizon is dropping CDMA and migrating to an all LTE network in the very near future. If true then your current problems will go away and you may be looking for a newer phone.
[Android Software Development] Exabyter:
I have no doubt those are regular LoS issues.

Verizon has been working on that transition for at least 8 years. I don't know of a modern Verizon-compatible smartphone that doesn't support GSM/LTE as well. The difference is that on a traditional VZW-compatible phone the CDMA "identity" is the primary identity rather than the GSM SIM card. And they support VZW LTE bands like b13 FDD.
[Android Software Development] SGE2010:
necessary to update LOS for microG, regularily?

in Settings --> System --> About phone --> LineageOS updates, I find weekly updates which are downloadable. Am I supposed to do this on a regular basis? If yes, do you guys do this manually every week?
[Android Software Development] kurtn:
After download the download button changes to "install". All you have to do is one tap and one to confirm. The rest is done by an open recovery script.

If that's to much for you, you should tap threedotmenu and change interval to monthly. So you get up to date security patch level.
[Android Software Development] Strel0ka:
Looks like the automatic build, at least for beryllium, needs to be fixed. LineageOS includes the firmware/vendor files since the official 2019-08-02 nightly, todays LOS+microg update doesn't seem to include the changes.

This results in broken installation, I tested different vendors/firmware combos, too. I'll stay on last weeks update in the meantime.
[Android Software Development] kurtn:
Oha!

lineage-16.0-20190802-nightly-beryllium-signed.zip

sha256 781.97 MB

2019-08-02nightly16.0 lineage-16.0-20190731-nightly-beryllium-signed.zip

sha256 503.67 MB

https://review.lineageos.org/252265
[Android Software Development] JamesKinds:
Same issue for me. Thankfully by reinstalling vendor-firmware (10.3.6.0) and the last working LOS (20190729) I was able to revive the system.
[Android Software Development] ncorna:
You are right, I've just experienced the same issue with Mi 8 (dipper).

I've blacklisted the builds for beryllium, dipper and polaris (and removed the broken images from the downloads) until I find a solution.

I don't understand what went wrong though, I cannot find any new information regarding the builds for these models and the build log seems clean. Any idea?
[Android Software Development] JamesKinds:
As [MENTION=8853544]Strel0ka[/MENTION] and [MENTION=8031265]kurtn[/MENTION] noted, the firmware/vendor files have started being included in the beryllium LOS images starting from the official 2019-08-02 nightly. The size of the zip has gone from aprx. 500MB to 780MB.

I'm not sure why, but I am pretty certain that this change is responsible.

Thank you for investigating.
[Android Software Development] kurtn:
[MENTION=8701777]ncorna[/MENTION] that firmware assumption is not confirmed yet.

---------- Post added at 11:45 AM ---------- Previous post was at 11:13 AM ----------

Same for polaris. I've got device list from here

https://review.lineageos.org/q/topic:%22mi845-building-vendor%22
[Android Software Development] ncorna:
The vendor partition included in our build is much smaller, attached the diff.
[Android Software Development] Shobit Joura:
Heads up notification is broken in tissot builds , notifications work fine but heads ups are broken.
[Android Software Development] Strel0ka:
https://review.lineageos.org/c/LineageOS/hudson/+/253051

Looks like Xiaomi builds are in for a ride...
[Android Software Development] JamesKinds:
Do we understand the main issue yet?
[Android Software Development] ncorna:
It seems that somehow our internal proprietary repository went out of sync, without any indication from the logs. I have deleted and re-synced the sources and done a test build for dipper which seems OK, however I won't be able to test it for a week.

However the Xiaomi's TheMuppets repo has been taken down by DMCA request (temporary hopefully), so builds for Xiaomi devices are paused anyways.
[Android Software Development] JamesKinds:
Thank you for the update
[Android Software Development] rayman95:
N9005 Hlte LOS16.0 is officiall now, is it possible to add it back...

Thanks a lot..
[Android Software Development] RockyTV:
You can always host your own repo, though. Is there a mirror up?
[Android Software Development] ncorna:
Yes but, as it has been taken down by a DCMA request, we are definitely not going to host our own one.