LineageOS for microG

Search This thread

kurtn

Senior Member
Jan 28, 2017
4,089
1,777
Small town in Bavaria
I've spent the last few days testing microg in two devices:
- Redmi Note 4 (mido) LOS 16.0
- Poco F1 (beryllium) LOS 18.1

In the oldest phone, I still couldn't find a single bug. Location works very well, even gps works when using openstreetmap-based apps.
In the Poco F1 however, location is not working that well, I can't seem to get my location detected by google maps. That causes some nuisance as some apps rely on google maps to provide their services.
Considering that it works in one phone and not in other, it can't be a microg limitation. I suspect that it's just a bug that still hasn't been squashed in this fresh releases of android 11. I'm curious what are other people's experiences.

Apart from that, I must say I'm pleasantly surprised on how smoothly everything works in a google-free phone! Thank you microg developers!
You use location and GPS as synonyms. A phone with microG has many sources of location data. Not only GPS. Check your microG settings, go outdoors, install SatStat app and give your phone 10 minutes for location detection.
 
Hi, Im still unsure about a safe upgradepath to 18.1 with MicroG.
Im running OrangeFox recovery which should be fine ?
So from what I understand I remove my PIN (so it wont get stuck).
Then I flash the newest MIUI recovery to get all firmware/vendor updates.
After that I flash the offical 18.1 to confirm everything is working and then I flash the 18.1 for Micro G ?
 

kurtn

Senior Member
Jan 28, 2017
4,089
1,777
Small town in Bavaria
Hi, Im still unsure about a safe upgradepath to 18.1 with MicroG.
Im running OrangeFox recovery which should be fine ?
So from what I understand I remove my PIN (so it wont get stuck).
Then I flash the newest MIUI recovery to get all firmware/vendor updates.
After that I flash the offical 18.1 to confirm everything is working and then I flash the 18.1 for Micro G ?
Upgrading the microG fork should be exactly the same as upgrading official lineageOS - skip the optional GApps part. You will find a guide for your device in wiki.lineageos.org
 

Uumas

Senior Member
Jul 27, 2014
473
214
The latest lineage microg build for oneplus3 is from 20210411 while the official los is at 20210503. Why is that? Are the builds going to return soon?
 

humpty321

Member
Jun 12, 2015
15
1
Today I updated from lineage-18.1-20210409-microG-cheeseburger to lineage-18.1-20210506-microG-cheeseburger.
Before this update AFWall did work, after the update it keeps crashing. Here is a little excerpt of the very long list of errors that keep going on all the time:
[05-07 20:36:05.473 4205:4252 E/AndroidRuntime] FATAL EXCEPTION: pool-2-thread-1 Process: dev.ukanth.ufirewall, PID: 4205 java.util.concurrent.RejectedExecutionException: Task com.topjohnwu.supe[email protected]9ec6587 rejected from [email protected][Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0] at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2086) at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:848) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1394) at com.topjohnwu.superuser.internal.ResultImpl.callback(ResultImpl.java:56) at com.topjohnwu.superuser.internal.PendingJob.lambda$submit$1$PendingJob(PendingJob.java:68) at com.topjohnwu.superuser.internal.-$$Lambda$PendingJob$bS70F1tiBbXB-YYIpfktjueOJJc.onShell(Unknown Source:6) at com.topjohnwu.superuser.internal.MainShell.lambda$get$2(MainShell.java:71) at com.topjohnwu.superuser.internal.-$$Lambda$MainShell$8inlSh_vRXGe0Jv5ZVlXowIFgYw.run(Unknown Source:4) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) at java.lang.Thread.run(Thread.java:923) [05-07 20:36:05.474 4205:4205 E/AndroidRuntime] FATAL EXCEPTION: main Process: dev.ukanth.ufirewall, PID: 4205 java.lang.RuntimeException: Unable to start service [email protected] with Intent { cmp=dev.ukanth.ufirewall/.service.LogService }: java.util.concurrent.RejectedExecutionException: Task com.topjohnwu.supe[email protected]59f3ba1 rejected from [email protected][Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0] at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:4338) at android.app.ActivityThread.access$1800(ActivityThread.java:237) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1951) at android.os.Handler.dispatchMessage(Handler.java:106) at android.os.Looper.loop(Looper.java:223) at android.app.ActivityThread.main(ActivityThread.java:7660) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947) Caused by: java.util.concurrent.RejectedExecutionException: Task com.topjohnwu.supe[email protected]59f3ba1 rejected from [email protected][Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0] at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2086) at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:848) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1394) at com.topjohnwu.superuser.internal.ResultImpl.callback(ResultImpl.java:56) at com.topjohnwu.superuser.internal.PendingJob.lambda$submit$1$PendingJob(PendingJob.java:68) at com.topjohnwu.superuser.internal.-$$Lambda$PendingJob$bS70F1tiBbXB-YYIpfktjueOJJc.onShell(Unknown Source:6) at com.topjohnwu.superuser.internal.MainShell.get(MainShell.java:53) at com.topjohnwu.superuser.internal.PendingJob.submit(PendingJob.java:65) at dev.ukanth.ufirewall.service.LogService.initiateLogWatcher(LogService.java:312) at dev.ukanth.ufirewall.service.LogService.startLogService(LogService.java:243) at dev.ukanth.ufirewall.service.LogService.onStartCommand(LogService.java:197) at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:4320) ... 8 more [05-07 20:36:05.499 2768:2768 E/SubscriptionInfoUpdater] Cannot manage subId=1, carrierPackage=com.android.carrierconfig [05-07 20:36:05.712 2768:2768 E/GsmCdmaPhone] [0] Invalid cdma_roaming_mode settings: -1 [05-07 20:36:05.722 2768:2768 E/RILJ] setSignalStrengthReportingCriteria ignored on IRadio version less than 1.2 [PHONE0] [05-07 20:36:05.722 2768:2768 E/RILJ] setSignalStrengthReportingCriteria ignored on IRadio version less than 1.2 [PHONE0] [05-07 20:36:05.788 2768:2768 E/ImsPhoneCallTracker] [1] cacheCarrierConfiguration: No carrier config service found or not active subId = -1 [05-07 20:36:05.805 985:2091 E/RILQ] (1/985): RIL[1] processRequest: ImsRadioImpl::processRequest - Error 0 [05-07 20:36:05.805 985:1606 E/RILQ] (1/985): RIL[1][event] qcril_qmi_imss_request_set_ims_config: ..invalid parameters for the config items value [05-07 20:36:05.805 985:1606 E/RILQ] (1/985): RIL[1][event] qcril_qmi_imss_request_set_ims_config: radio config error: 2..sending empty response [05-07 20:36:05.809 2768:2768 E/ImsManager [1]] updateImsServiceConfig: com.android.ims.ImsException: changeMmTelCapability(CCR) at com.android.ims.ImsManager.changeMmTelCapability(ImsManager.java:2054) at com.android.ims.ImsManager.updateImsServiceConfig(ImsManager.java:1351) at com.android.internal.telephony.GsmCdmaPhone.handleMessage(GsmCdmaPhone.java:2766) at android.os.Handler.dispatchMessage(Handler.java:106) at android.os.Looper.loop(Looper.java:223) at android.app.ActivityThread.main(ActivityThread.java:7660) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947) Caused by: android.os.RemoteException: ImsServiceProxy is not ready to accept commands. at com.android.ims.FeatureConnection.checkServiceIsReady(FeatureConnection.java:217) at com.android.ims.MmTelFeatureConnection.changeEnabledCapabilities(MmTelFeatureConnection.java:421) at com.android.ims.ImsManager.changeMmTelCapability(ImsManager.java:2038) ... 8 more [05-07 20:36:05.810 985:2091 E/RILQ] (1/985): RIL[1] processRequest: ImsRadioImpl::processRequest - Error 0 [05-07 20:36:05.810 985:1606 E/RILQ] (1/985): RIL[1][event] qcril_qmi_imss_request_set_ims_config: ..invalid parameters for the config items value [05-07 20:36:05.810 985:1606 E/RILQ] (1/985): RIL[1][event] qcril_qmi_imss_request_set_ims_config: radio config error: 2..sending empty response [05-07 20:36:05.810 2768:2768 E/GsmCdmaPhone] [1] Invalid cdma_roaming_mode settings: -1 [05-07 20:36:05.814 2768:2768 E/RILJ] setSignalStrengthReportingCriteria ignored on IRadio version less than 1.2 [PHONE1] [05-07 20:36:05.814 2768:2768 E/RILJ] setSignalStrengthReportingCriteria ignored on IRadio version less than 1.2 [PHONE1] [05-07 20:36:05.833 0:0 E/[20210507_20:36:05.833368]@1 synaptics,s3320] all finger up [05-07 20:36:06.281 1131:1603 E/RILC] oemHookRawInd: oemHookService[0]->mOemHookIndication == NULL [05-07 20:36:06.312 1547:3636 E/PHONE] ServiceState.getRadioTechnology() DEPRECATED will be removed ******* [05-07 20:36:06.949 1131:1603 E/RILC] oemHookRawInd: oemHookService[0]->mOemHookIndication == NULL [05-07 20:36:06.992 1547:2709 E/PHONE] ServiceState.getRadioTechnology() DEPRECATED will be removed *******

After I reinstalled Magisk AFWall now is working again. Does this mean that from now on I would have to install Magisk afresh after each update?

I'd very much would like to downgrade to 16.0, because after that version every new one grew more instable than the previous one.
a) Is there a way to downgrade without loosing data and settings?
b) Alternativly, does anyone , who is reading know if there are installable keys available to reverse to LineageOS (without microg) ?
 
Last edited:

kurtn

Senior Member
Jan 28, 2017
4,089
1,777
Small town in Bavaria
Today I updated from lineage-18.1-20210409-microG-cheeseburger to lineage-18.1-20210506-microG-cheeseburger.
Before this update AFWall did work, after the update it keeps crashing. Here is a little excerpt of the very long list of errors that keep going on all the time:
[05-07 20:36:05.473 4205:4252 E/AndroidRuntime] FATAL EXCEPTION: pool-2-thread-1 Process: dev.ukanth.ufirewall, PID: 4205 java.util.concurrent.RejectedExecutionException: Task com.topjohnwu.supe[email protected]9ec6587 rejected from [email protected][Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0] at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2086) at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:848) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1394) at com.topjohnwu.superuser.internal.ResultImpl.callback(ResultImpl.java:56) at com.topjohnwu.superuser.internal.PendingJob.lambda$submit$1$PendingJob(PendingJob.java:68) at com.topjohnwu.superuser.internal.-$$Lambda$PendingJob$bS70F1tiBbXB-YYIpfktjueOJJc.onShell(Unknown Source:6) at com.topjohnwu.superuser.internal.MainShell.lambda$get$2(MainShell.java:71) at com.topjohnwu.superuser.internal.-$$Lambda$MainShell$8inlSh_vRXGe0Jv5ZVlXowIFgYw.run(Unknown Source:4) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) at java.lang.Thread.run(Thread.java:923) [05-07 20:36:05.474 4205:4205 E/AndroidRuntime] FATAL EXCEPTION: main Process: dev.ukanth.ufirewall, PID: 4205 java.lang.RuntimeException: Unable to start service [email protected] with Intent { cmp=dev.ukanth.ufirewall/.service.LogService }: java.util.concurrent.RejectedExecutionException: Task com.topjohnwu.supe[email protected]59f3ba1 rejected from [email protected][Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0] at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:4338) at android.app.ActivityThread.access$1800(ActivityThread.java:237) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1951) at android.os.Handler.dispatchMessage(Handler.java:106) at android.os.Looper.loop(Looper.java:223) at android.app.ActivityThread.main(ActivityThread.java:7660) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947) Caused by: java.util.concurrent.RejectedExecutionException: Task com.topjohnwu.supe[email protected]59f3ba1 rejected from [email protected][Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0] at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2086) at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:848) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1394) at com.topjohnwu.superuser.internal.ResultImpl.callback(ResultImpl.java:56) at com.topjohnwu.superuser.internal.PendingJob.lambda$submit$1$PendingJob(PendingJob.java:68) at com.topjohnwu.superuser.internal.-$$Lambda$PendingJob$bS70F1tiBbXB-YYIpfktjueOJJc.onShell(Unknown Source:6) at com.topjohnwu.superuser.internal.MainShell.get(MainShell.java:53) at com.topjohnwu.superuser.internal.PendingJob.submit(PendingJob.java:65) at dev.ukanth.ufirewall.service.LogService.initiateLogWatcher(LogService.java:312) at dev.ukanth.ufirewall.service.LogService.startLogService(LogService.java:243) at dev.ukanth.ufirewall.service.LogService.onStartCommand(LogService.java:197) at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:4320) ... 8 more [05-07 20:36:05.499 2768:2768 E/SubscriptionInfoUpdater] Cannot manage subId=1, carrierPackage=com.android.carrierconfig [05-07 20:36:05.712 2768:2768 E/GsmCdmaPhone] [0] Invalid cdma_roaming_mode settings: -1 [05-07 20:36:05.722 2768:2768 E/RILJ] setSignalStrengthReportingCriteria ignored on IRadio version less than 1.2 [PHONE0] [05-07 20:36:05.722 2768:2768 E/RILJ] setSignalStrengthReportingCriteria ignored on IRadio version less than 1.2 [PHONE0] [05-07 20:36:05.788 2768:2768 E/ImsPhoneCallTracker] [1] cacheCarrierConfiguration: No carrier config service found or not active subId = -1 [05-07 20:36:05.805 985:2091 E/RILQ] (1/985): RIL[1] processRequest: ImsRadioImpl::processRequest - Error 0 [05-07 20:36:05.805 985:1606 E/RILQ] (1/985): RIL[1][event] qcril_qmi_imss_request_set_ims_config: ..invalid parameters for the config items value [05-07 20:36:05.805 985:1606 E/RILQ] (1/985): RIL[1][event] qcril_qmi_imss_request_set_ims_config: radio config error: 2..sending empty response [05-07 20:36:05.809 2768:2768 E/ImsManager [1]] updateImsServiceConfig: com.android.ims.ImsException: changeMmTelCapability(CCR) at com.android.ims.ImsManager.changeMmTelCapability(ImsManager.java:2054) at com.android.ims.ImsManager.updateImsServiceConfig(ImsManager.java:1351) at com.android.internal.telephony.GsmCdmaPhone.handleMessage(GsmCdmaPhone.java:2766) at android.os.Handler.dispatchMessage(Handler.java:106) at android.os.Looper.loop(Looper.java:223) at android.app.ActivityThread.main(ActivityThread.java:7660) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947) Caused by: android.os.RemoteException: ImsServiceProxy is not ready to accept commands. at com.android.ims.FeatureConnection.checkServiceIsReady(FeatureConnection.java:217) at com.android.ims.MmTelFeatureConnection.changeEnabledCapabilities(MmTelFeatureConnection.java:421) at com.android.ims.ImsManager.changeMmTelCapability(ImsManager.java:2038) ... 8 more [05-07 20:36:05.810 985:2091 E/RILQ] (1/985): RIL[1] processRequest: ImsRadioImpl::processRequest - Error 0 [05-07 20:36:05.810 985:1606 E/RILQ] (1/985): RIL[1][event] qcril_qmi_imss_request_set_ims_config: ..invalid parameters for the config items value [05-07 20:36:05.810 985:1606 E/RILQ] (1/985): RIL[1][event] qcril_qmi_imss_request_set_ims_config: radio config error: 2..sending empty response [05-07 20:36:05.810 2768:2768 E/GsmCdmaPhone] [1] Invalid cdma_roaming_mode settings: -1 [05-07 20:36:05.814 2768:2768 E/RILJ] setSignalStrengthReportingCriteria ignored on IRadio version less than 1.2 [PHONE1] [05-07 20:36:05.814 2768:2768 E/RILJ] setSignalStrengthReportingCriteria ignored on IRadio version less than 1.2 [PHONE1] [05-07 20:36:05.833 0:0 E/[20210507_20:36:05.833368]@1 synaptics,s3320] all finger up [05-07 20:36:06.281 1131:1603 E/RILC] oemHookRawInd: oemHookService[0]->mOemHookIndication == NULL [05-07 20:36:06.312 1547:3636 E/PHONE] ServiceState.getRadioTechnology() DEPRECATED will be removed ******* [05-07 20:36:06.949 1131:1603 E/RILC] oemHookRawInd: oemHookService[0]->mOemHookIndication == NULL [05-07 20:36:06.992 1547:2709 E/PHONE] ServiceState.getRadioTechnology() DEPRECATED will be removed *******

After I reinstalled Magisk AFWall now is working again. Does this mean that from now on I would have to install Magisk afresh after each update?

I'd very much would like to downgrade to 16.0, because after that version every new one grew more instable than the previous one.
a) Is there a way to downgrade without loosing data and settings?
b) Alternativly, does anyone , who is reading know if there are installable keys available to reverse to LineageOS (without microg) ?
There are reports from official lineageOS 18.1 users that loose magisk in ota update, too. Best workaround so far: manual update with flashing magisk.

I have seen I can dirty install L4M and official back and forth with lineage recovery

Going to 16.0 needs a clean flash and cuts you off from security patches - or you find a updated unofficial version.
 
  • Like
Reactions: humpty321

CrewParking

Member
Aug 19, 2020
35
2
Upgrading the microG fork should be exactly the same as upgrading official lineageOS - skip the optional GApps part. You will find a guide for your device in wiki.lineageos.org
I want to double check because, knowing me, I'll nuke all my data from orbit trying to do this.

I'm on Guacamole upgrading from 17 to 18.
So in other words, follow the exact same instructions here, but use the MicroG zip file lineage-18.1-20210508-microG-guacamole.zip instead?


Edit: That worked. Only issue is that I now have to deal with Magisk, forgot to prep the thing for the update. Thanks kurtn, for the confirmation.

Would be nice if the information was updated on the LOS MicroG website in the Installation section, only tells users what to do if upgrading from 15 to 16.
 
Last edited:
  • Like
Reactions: kurtn

Bifidusse

New member
May 4, 2021
2
0
On my klte I had to install the microG recovery. With the LOS 18 stock recovery, I couldn't sideload the LOS18-microG zip file (signature verification failed). With the supplied recovery from microG, it worked. I guess it's signature-spoofing related.
 

kurtn

Senior Member
Jan 28, 2017
4,089
1,777
Small town in Bavaria
On my klte I had to install the microG recovery. With the LOS 18 stock recovery, I couldn't sideload the LOS18-microG zip file (signature verification failed). With the supplied recovery from microG, it worked. I guess it's signature-spoofing related.
No, it is build signature related. In lineage recovery you get the message that the signature of the zip file does not the expected signature. You can confirm to install despite mismatch.
 

Ninive

New member
May 27, 2021
4
0
Hello,

the latest build for Mi 8 lite (Platina) is 2021/04/11 when the latest lineageOS build is 2021/06/03. Will there be an update soon ? Thanks in advance.
 

iooxda

Member
Dec 1, 2019
43
15

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    I'm not using Google Services or any apps from Mountain View company, so I will not use LineageOS. Newest LineageOS for microG for Pixel 5 is from 4th July: https://download.lineage.microg.org/redfin/ and this is the second in a row release without wi-fi working on Pixel 5...
    You can run https://mirrorbits.lineageos.org/fu...neage-18.1-20210707-nightly-redfin-signed.zip without GApps
    1
    thank you very much kurtn! so my only option is to install magisk? ok i will try it so I go back reading !

    UPDATE: so with adb root i can still use prerooted apps ?
    No, adb root is not root for apps.
    1
    Will the new added devices to the list of official lineageos 18.1 be added to Lineageos Microg too? I have a LMI / Poco F2 pro / Redmi K30 pro and hope it will be supported.
    Yes. Devices get automatically added. No guarantee for success in building.
  • 151
    Android experience relies heavily on Google's Play Services. The microG project creates an alternative to installing Gapps, which install and execute closed-source blobs on our phones. MicroG however requires a patch called "signature spoofing", which allows microG's apps to spoof themselves as Google Apps. LineageOS currently does not include the patch due to different opinions among the developers. (further information can be found here)

    This makes microG installation difficult on LineageOS and other ROMs. Our ROM is a fork of LineageOS with just the necessary changes to have microG built-in. We ship weekly builds for all the LineageOS supported devices..

    You can find us on https://lineage.microg.org

    XDA:DevDB Information
    LineageOS for microG, ROM for all devices (see above for details)

    Contributors
    Simon94, ncorna, n1zzo, LineageOS, MaR-V-iN
    Source Code: https://github.com/lineageos4microg

    ROM OS Version: Android 10
    Based On: LineageOS

    Version Information
    Status: Nightly

    Created 2017-11-06
    Last Updated 2020-08-28
    24
    Just to give a small heads up. As you may noticed some of the project members the priorities have shifted to other projects.

    I was and am still willing to take over some of the tasks, but as microG lacked some bugfixes and support for LineageOS 17.1 i was not sure whether its worth it to spend more time into LineageOS for microG. Once marvin released the new microG update, we still had to check with our team, how we'll proceed.

    For now i've taken over the responsibility of the Android Build process, merged some of the fixes and integrated LineageOS 17.1 support. New builds are on their way, both LineageOS 16 and 17.1 based.


    Best
    Simon
    15
    Hey guys. You are right with your findings. We were testing yesterday LineageOS 15.1. But we rolled it back. Now we have almost everything ready for Lineage 15.1 - In fact there is one minor change outstanding before we're going to release. After release we'll start building the complete LineageOS weekly build roster again.
    13
    Current device list which will be built tomorrow:
    Code:
    a6020,angler,armani,athene,bacon,bullhead,cancro,capricorn,cheeseburger,clark,condor,crackling,d855,
    deb,dragon,falcon,flo,flounder,gemini,h815,h850,hammerhead,harpia,herolte,here2lte,hlte,i9100,
    i9300,jfltexx,kenzo,klte,libra,lux,m8,mako,mido,oneplus2,oneplus3,onyx,osprey,otus,paella,pme,
    serranoltexx,shamu,thea,titan,victara,wt88047,yuga,Z00L
    13
    today i got my weekly(?) update with november security patches via ota notification.
    thanks for that!

    Yes they are rolling out new builds again :) Thank you everyone who is contributing to this :good:

    Oops. They only build Oreo right now.

    We have decided to build every device weekly (like before), as we don't have the capacity to build for ~75 devices daily and nightlies are quite useless to the end users. We will build for all the ~200 devices, ~30 devices per day, from top to bottom of the usual hudson devices list (which means that 15.1 builds will appear in the first part of the week and 14.1 in the second one).

    As usual, new devices will be automatically added to the build list, no need to ask for them, just wait some days.