yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Android Development] MSe1969:
I am using the squid kernel (oreo branch), which runs very smooth on my 'cm-13.0' builds - I do not really see a reason to switch (Especially not since I am considering to continue with Nougat builds). Nevertheless, the respective thread also refers to options how to flash the kernel separately, so you are free to give it a try yourself on your own device, if you'd like to do so and report it e.g. here . . .

(But thanks anyway for mentioning, I may keep an eye on that kernel in future, as it seems to receive very positive feedbacks)
[Moto G 2015 Android Development] MSe1969:
Thanks for the feedback, appreciated!

During my testing, I have not faced the described issue - but I have first tested with the "default" build, so after flashing the microG build, the SetupWizard did not launch at all (since I didn't do a factory reset in-between). So I have done another test right now and again - I haven't experienced the described issue. Since I have a quite complicated WiFi password, I skipped WiFi setup in my test.

As far as I remember, the step you have described only happens, if the original Google SetupWizard is present, because the LineageOS SetupWizard checks for the existence of the Google SetupWizard apk and launches it, if it exists - so I have the following suspicion:

Either - me skipping the WiFi setup did the trick already?

Or (this is what I believe you should have a closer look at) - I think when you did a clean install, you only did a "factory reset" in TWRP (i.e. wipe /data but leave Internal Memory intact and wipe cache & dalvik) and you did not explicitly wipe the system partition.

So if you had e.g. Gapps installed before, a gapps "survival script" (or maybe any other stuff as well) in /system/addon.d was obviously present and restored the Gapps or whatever was defined to be restored after flashing.

microG normally does not need to logon to to Google, but it supports certain functionalities requiring it, so microG indeed does have a simple Google logon screen, but not a Wizard offering you to setup a Google account.

(I remember from the SlimKAT ROM for my S3 mini device, that the contacts app - if launched directly and not via the telephony app - calls the microG Google logon screen and if you are in the microG Google logon screen, you indeed do not have a skip option.)

So either, a previous Gapps installation was re-flashed, or you did maybe once flash an unofficial microG ZIP directly over an existing Gapps installation without getting rid of Gapps before, which may cause that the "survival script" always brings theGoogle SetupWizard and some other Google stuff back, together with your microG binaries (which have the same java package name as the original Google stuff).

This is of course wild guessing, but would fit to what you describe.

Fact is, that I could not reproduce your issue.

Curious to learn more about this situation on your device.

Regards, M.
[Moto G 2015 Android Development] jemail:
Hi,

I have been completely GApps free since November last year. No GApps on my device or stored on sdcard. I have tried multiple custom ROMs and always flashed a microg app (shadow53) during clean installs. This has never resulted in the situation of having a microg sign in during setup. I have always configured microg after initial setup has completed.

For me a clean install is always: wipe all partitions except internal sdcard storage. System, data, cache are always wiped.

I think that during setup I activated Wi-Fi as I can remember my Wi-Fi key. I had no option to skip microg sign in. Maybe that was the problem?
[Moto G 2015 Android Development] MSe1969:
Thanks again for your feedback. Seems indeed, that skipping the WiFi setup did the trick, especially if one looks at the code:

https://github.com/LineageOS/androi...od/setupwizard/setup/GmsAccountPage.java#L111

So later today, I will do another test (with 'cm-13.0' and 'cm-14.1') and - if I can then reproduce your issue (I am sure I will for 'cm-13.0', after having looked at the code - 'cm-14.1' works differently so I assume no issue there - maybe you yould test it quickly?) - I'll tweak the SetupWizard for the microG build accordingly.

For the time being - there are two work-arounds for the 'cm-13.0' build:

1. Not setting up WiFi during initial setup

2. Have a look here - but make sure to only remove CyanogenSetupWizard with the script (LockClock has already been "de-googlified", Gello is not present any longer and TimeService needs to be present to deal with keeping the system time after reboot) and execute the sqlite command - alternatively, do it manually in Recovery mode
[Moto G 2015 Android Development] kurapika7:
the reason why I do not flash it separately is because it restarts in bootloader mode. it seems to me good kernel is very stable and very fast hopefully and you still consider making a joint construction of this kernel, thank you for your work. sorry for my bad english.
[Moto G 2015 Android Development] Apurba99:
Please add VOLTE support to Marshmallow or Nougat.
[Moto G 2015 Android Development] MSe1969:
Update

Hi jemail,

I repeated the test with enabled network connection and then I had the same issue as you have described. I have fixed that issue and uploaded a new cm-13.0 microG build to AFH here

Thanks for reporting the issue. Regards, M.

P.S.: Btw, the issue does not happen in my cm-14.1 microG build.
[Moto G 2015 Android Development] MSe1969:
You have asked this already, not keen on repeating myself :)
[Moto G 2015 Android Development] MSe1969:
VoLTE Test version

Hi, have uploaded another test version (cm-13.0) with VoLTE blobs (the 1st build variant, only with microG patch, which can also be used with Gapps). As already outlined before - I can't test myself (does not seem to work with my carrier) - however, some people have reported earlier that it did the job for them.

If it works, I'll make it part of the next regular build, if not, I'll finally give up on the VoLTE topic.

Here we go: https://www.androidfilehost.com/?fid=673956719939829456

(cm-13.0, March Sec.Patches, 6.0.1_r81, patched f. microG, with VoLTE blobs)

Regards, M.
[Moto G 2015 Android Development] MSe1969:
New thread with hardened LineageOS 14.1 microG build

Hi all,

I have created a new thread for LineageOS 14.1

If there still is interest in maintaining the LineageOS 13.0 builds, please let me know and I will be happy to continue posting updates here.

Regards, M.
[Moto G 2015 Android Development] ajaysingh23:
Hi,

Thanks for the test build, I have been using this for past 24 hours now. Volte works flawlessly for me even after multiple reboots. One thing I have noticed is low volume from both loudspeaker (all time)& ear piece (during call). I haven't used the regular LOS13 without volte so I'm not sure if the volume is same, but it's lower then the official LOS 14.1

Regards,

Ajay
[Moto G 2015 Android Development] MSe1969:
Thanks for your feedback, right now on vacation and only mobile access, can't really check - nevertheless, as I cannot use VoLTE myself, difficult for me to look into that. Basically did integrate the VoLTE patch and what was done in cm-14.1 into my build tree. Maybe there is some setting in some config.xml ...
[Moto G 2015 Android Development] MSe1969:
New builds with April ASB (and VoLTE)

Hi all,

uploaded new builds:

April 2018 ASB (Sec. string 2018-04-01)

Android System Webview on M65

VoLTE patch included by default

Default build (with microG patch):

https://www.androidfilehost.com/?fid=962187416754476955

microG-build variant:

https://www.androidfilehost.com/?fid=962187416754476956

A comment to VoLTE:

I can't test myself and I can't guarantee it'll work under all conditions - however, it seems to work in most cases and the worst, which can happen, it that it won't work (and you can switch it off), so why not simply include it?

As mentioned before, my main focus is my hardened LineageOS 14.1 'microG' build.

However - as long as there still is some interest - I'll continue updating the LineageOS 13.0 patches here. Feedbacks welcome...
[Moto G 2015 Android Development] MSe1969:
You may have read this XDA story already. The security hardening of this ROM already takes care, see the dedicated reserved post in this thread.
[Moto G 2015 Android Development] NeoPreacher:
Interest is still there ;) . But there is a problem with low in call volume on both speaker and ear piece. I'm using the "normal" build on xt1541.
[Moto G 2015 Android Development] MSe1969:
I can confirm this issue - found something about it in the squid kernel thread, trying another build later today and will post an update.
[Moto G 2015 Android Development] NeoPreacher:
i got kinda workaround. I'm using arise actually and with it I get the volume on a normal level. Might be something with the mixer_path.xml. I used a mod from somewhere in this forum (motog 2015) a few days ago, where I only used to exchange the mixer_path.xml with a modified one that worked too. Maybe it's a hint. I used the one with the level at 90. https://xdaforums.com/2015-moto-g/development/mod-native-volume-boost-apps-mixerpaths-t3217132 .

cheers
[Moto G 2015 Android Development] MSe1969:
I have successfully built and tested yesterday night the kernel fix, but not yet uploaded (can only do tonight). As squid2 has explained in the squid kernel thread, the commits between release r22 and r22c should not be used on MM, and that did the trick. I have also found the mixer_path.xml patch, but the real fix is to skip certain kernel commits, which correspond to updated N vendor blobs, which obviously are not present in MM.
[Moto G 2015 Android Development] NeoPreacher:
aah, alright. if it's uploaded tonight, I'm going to test it tomorrow.

---------- Post added at 10:57 AM ---------- Previous post was at 10:46 AM ----------

I need one or two hints! I got everything working as it should but the only thing that works kinda disappointing is the location service. and before someone askes, yes I searched, read and tried several things (got it slightly working with mozilla backend for now). but I hope for a hint or fix to get a better result.?
[Moto G 2015 Android Development] MSe1969:
Question:

Which build, which variant? And GPS or coarse? And if 1st variant - with Gapps or other provider?
[Moto G 2015 Android Development] NeoPreacher:
I used the standard variant with nano droid in system, no gapps. for location I'm always using highest precision.
[Moto G 2015 Android Development] MSe1969:
Updated April builds ("low in-call volume" fixed)

I have re-done the builds with a fix in the kernel to get rid of the "low in-call volume" issue.

Found the solution in the quid kernel thread and omitted this time the specific commits for releases r22b/r22c.

I only did a quick check regarding the low in-call volume, no comprehensive test.

default variant

hardened microG build
[Moto G 2015 Android Development] ziko111:
Hi MSe1969, thank you for your work. I'm using your rom for 3 months, and it's very good. I will try your fix for low in-call volume, since you fixed what is the only glitch.

An off-topic question: if I try your android v7 rom, can I switch back to this? Is the v7 rom power efficient at the same level as this rom?

Thank you again
[Moto G 2015 Android Development] MSe1969:
Hi, I am using the N ROM myself as a daily driver and I did not notice any truly significant power efficiency decrease. (I can't obviously foresee any specific issues related to specific apps)

With regards to switching: Of course, you can always upgrade and downgrade as well as switching to a completely different build by doing clean installs. I think however your question is meant whether you can do "dirty" flashes w/o wiping your data. I changed from my own MM to N build w/o wiping and it simply worked. I haven't tried the other way, but I would guess it won't be possible to simply downgrade and keep your data w/o issues.

Make sure to have a proper TWRP backup and try... :)
[Moto G 2015 Android Development] ziko111:
Hi,

I installed the patch and now I have no issues with this ROM. I will try your N Rom only because I trust you!

Thanks a lot.
[Moto G 2015 Android Development] MSe1969:
If you are happy with the cm13 build, there is no real need to immediately upgrade to N. I'll btw do a new build with May patches next week for this ROM. I can however only do spot check tests, as I don't use the MM ROM any more as daily driver. (I have to TWRP backup my N ROM, wipe, install MM, do some tests, restore my N ROM)

So people using it as DD and giving qualified feedback are very welcome.

On the other side, I use my N ROM myself as daily driver, there's nothing wrong with it. So you're more than welcome to give it a try. :)
[Moto G 2015 Android Development] NeoPreacher:
So, everything seems to work as it should. Using your microg build. Messing around with nano droid wasn't my best idea in this case. Now location works right from the beginning. Now I have two minor things. Yalp store shows no network available, which is not the fault of the rom for sure. But I could use some help with this or at least a hint. Could be the adblocker. But I simply don't know what to whitelist. Nothing useful found. And the second thing is the webview, just a guess, doesn't display webpages as it should. Look at the top of the attached pic, can't scroll higher. Any idea?
[Moto G 2015 Android Development] MSe1969:
I have the same issue with Yalp, it has already been fixed, when you look at the github repo of Yalp, but FDroid still needs to pick the update. Seems that Google has changed something rgd. handshake

https://github.com/yeriomin/YalpStore/issues/447

Rgd. Webview, I simply took the webview from cm-14.1 branch, which was valid at build time mid of April (as said, in my recent corrected build I only changed the kernel, nothing else) - if I remember right, there has been a fix in M65, before now M66 was pushed. When I build next week, with May ASB, there also will be a brand-new webview M66.
[Moto G 2015 Android Development] hovnonium:
Could you share apk of webview separately, please?

Thanks.
[Moto G 2015 Android Development] MSe1969:
The webview.apk is signed during the build process, so I anyhow need to produce a build first. If you still want the apk w/o the entire ROM, I'll be happy to provide it here.
[Moto G 2015 Android Development] hovnonium:
It would be great. Thanks for your work.

Edit: Ive noticed in another your thread that you use Cloudflare DNS 1.1.1.1 as deafult fallback in some rom, could you add also this to this rom?
[Moto G 2015 Android Development] MSe1969:
Yes, that will also be part of the next build (microG version)
[Moto G 2015 Android Development] hovnonium:
Can I flash gapps onto microG version? Sadly I have to use google crapy gapps and also I would like to use extra features from microG build ( eg. SQLite 'secure delete' feature enabled, Access to /proc/net blocked for user apps, Enhanced Privacy Guard and others)
[Moto G 2015 Android Development] MSe1969:
You may want to try...? When Gapps are flashed, files are being replaced, so it could work, but I am not really sure.

Just being curious: What functionality you use requires the "original" Gapps?
[Moto G 2015 Android Development] hovnonium:
Ive bought 2 apps years ago and they need play store installed to chceck for the loicence (eg poweramp). They werent licenced when I used microG when it came out.

Well maybe I will try it and also I will find some new music player.
[Moto G 2015 Android Development] MSe1969:
True, this kind of license check requires the "real" play store . . . (it is said that you can use the original Google playstore apk on top of microG - I have tested that even myself one year ago, but I am reluctant to recommending this approach, as it can stop working at any time, since the original Google playstore silently self-updates w/o notification).
[Moto G 2015 Android Development] MSe1969:
New builds with May security patches

New builds available for download:

Default variant

microG build

Features:

Security string 2018-05-01

AOSP tag 6.0.1_r81

System Webview M66 stable

Squid kernel r22 (plus some addl. ASB patches)

The microG build contains the following new security hardening features:

Use cloudflare DNS (1.1.1.1) as default fallback (instead of Google)

Privacy-preferring default settings (SetupWizard: enable PG; don't grant location runtime permission by default to Browser)
[Moto G 2015 Android Development] hovnonium:
It needs to be checked just once and then I can uninstall playstore, thanks for the tip.

Also, can you sahre that webview apk for me, please?
[Moto G 2015 Android Development] MSe1969:
Here we go:

https://www.androidfilehost.com/?w=files&flid=272042
[Moto G 2015 Android Development] hovnonium:
On latest non-microg build when I download pic/video it wont show up automatically in gallery. I have to reboot phone or manualy rescan the media. Can the media storage apk be faulty?
[Moto G 2015 Android Development] MSe1969:
I've had such an issue last year once (don't remember exactly when, but longer ago), I could solve it by purging the app data and cache of the media storage and the mtp app in app settings. Have you tried this?
[Moto G 2015 Android Development] hovnonium:
I deleted data/cache of media storage, external storage, documents and gallery, what exactly is mtp app?

even clean flash doesnt solve it.

Also, flashing gapps onto microg build does nothing, just funny note.
[Moto G 2015 Android Development] MSe1969:
MTP host, com.android.mtp

Seems I have to flash my 13.0 build and do some tests on my own then... (when I find time, so probably when I do another build with June ASB)

What do you mean with the gapps flash remark? Doesn't work? Make sure that before you do so to deactivate/activate first to make sure, no app updates are on the data partition. Otherwise, you have the real gapps on system and microG "updates" on data
[Moto G 2015 Android Development] hovnonium:
Cant find com.android.mtp nowhere.

I think you dont need to because now ive tried to flash previous builds since october and it doesnt work anyway, so It has to be something on my end :(

They got installed but they are not accessible to user.

EDIT: ok it was problem on my end, dont know what exactly was wrong but i reformatted sd card and now it works....

Loving this build now:victory:
[Moto G 2015 Android Development] MSe1969:
New releases with June ASB patches

New builds available for download with June 2018 Security patches:

Regular build: https://www.androidfilehost.com/?fid=818222786056035846

microG build: https://www.androidfilehost.com/?fid=962339331458997401
[Moto G 2015 Android Development] MSe1969:
Future of this cm-13.0 build . . .

Hi all,

as already explained here in March, I don't use this ROM (cm-13.0) myself any more as daily driver for my device. So far, for convenience reasons, I have continued to provide cm-13.0 builds in this thread, as there has been at least some interest. It is a certain amount of work each month to backup my LineageOS 14.1 build, flash and test the cm-13.0 builds and restore later my backup.

Looking at the downloads on AFH in the last weeks, it is more than obvious that the interest in these builds has drastically collapsed - which is absolutely okay (so I am in no way 'disappointed' or anything like that): LineageOS 14.1 runs stable and smoothly, there are no real reasons any more to stick to cm-13.0 - and meanwhile, there seems also good progress being made to bring our device towards LineageOS 15.1 (unofficially).

Therefore, I will stop providing further cm-13.0 builds for the Osprey device. Those, who have been using my builds until now should have a look at my LineageOS 14.1 thread - as already mentioned, I use the hardened microG build myself as a daily driver.

I would like to thank you all for the interest and feedback and look forward to seeing you in my LineageOS 14.1 thread.

Regards, M.
[Moto G 2015 Android Development] MSe1969:
You're right - that app only exists in Nougat . . .
[Moto G 2015 Android Development] NeoPreacher:
Alright, so I also need to move on to cm14.1 builds. I was one of those very few using cm13 hardened for daily driver since weeks. Es war mir ein inneres Blumen pflücken. Time to test the next level. Anyway, thanks so far.
[Moto G 2015 Android Development] MSe1969:
EOL

This is (most probably) the last post from my side in this thread:

Please visit my LineageOS 14.1 thread for the continuation of my Osprey builds for LineageOS 14.1.

(Btw, I have just uploaded builds there containing the July 2018 security patches)
[Moto G 2015 Android Development] engloa:
Thread closed at OP request
[Desire 820 Q&A, Help & Troubleshooting] Phadorn@gmail.com:
HTC 820 cannot get unlock code, Error 152, anybody please help

my token

<<<< Identifier Token Start >>>>

AFE722E4019B309BDDEAAE010FCF74B3

E3F1F81C87EA8C3A287E073C42D21A3A

CD5B9BF2C9C0108B095758B4C838F173

AFAD5ECF49A0ABDB9F2E1D245CF9B794

F5B74613F27AEA2C60BA52B867B45250

9125BF50FD9A6F78FDC75C938C880D04

D2ADB7F27A44F139D373BE6EC3F6EEF4

DD826B9A9C4E0080A4C4A2AB8EE347AB

8F7CF32C49A035472FED3FADFD955479

826EEAF90679FAE95B8A6F727558C980

B661F84583D11A181D2CF159E4E10567

E87B4BD453DB59A86B106423D55BE7EA

34CD22487B10D472433D5DB32A1363FA

BAAB4809270860B4F1BB013DA98A9B82

A2C2CAF67E514E146636FE8F07833514

D2CFFEB2C75465E16364345C96112EDD

<<<<< Identifier Token End >>>>>

Thank you in advance

Phad
[Desire 820 Q&A, Help & Troubleshooting] Phadorn@gmail.com:
Error Code: 152.

Error Reason: Token Information not complete (CID).
[Android Q&A, Help & Troubleshooting] nathan-96:
This might be an odd, or more linux distro like question, but i have a problem when trying to compile RR.

The old instructions don't work anymore because some tools cannot be downloaded anymore. So i have to use the ' new' instruction which point me here: https://github.com/akhilnarang/scripts

Problem is when I'm trying to run the command I get the error: "Please install 'virtualenv2', or make 'phyton' point to python2" and i'm stuck there. Who knows how to do either of those two things on linux mint?
[Android Q&A, Help & Troubleshooting] GuestK0017:
Try putting an alias in your .bashrc like that:

alias python=/usr/local/bin/python2.7

Or you can try a simlink
[One (M9) Q&A, Help & Troubleshooting] Donnie267:
So I've been trying the past couple weeks to root and flash my M9 (AT&T) to no avail. I have ADB, fastboot, sdk and the htc drivers installed on my computer. Thing is, moonshine keeps giving me an error after checking for updates, sunshine is unable to gain temproot, adb won't flash twrp because I have s-on, RUU updates keep failing and I can't get OTA updates to install. I'm on android 5.0.2 with firmware version 1.32.502.9 and did the HTC DEV process to unlock the bootloader. Any help will be much appreciated.
[One (M9) Q&A, Help & Troubleshooting] lucyr03:
re-lock your bootloader with "fastboot oem lock" then you can run RUU and update it to latest firmware.

After that write a message and I'll help you with root, twrp, etc..
[One (M9) Q&A, Help & Troubleshooting] Donnie267:
Thanks for the response. I'll get on it sometime this evening. All I'm concerned about is getting twrp installed so I can use it to flash a custom rom with su already installed and all the bloat are removed.
[One (M9) Q&A, Help & Troubleshooting] lucyr03:
Yeah, but first you need to update the firmware to latest(nougat) because with 5.0.2 firmware you can flash only lollipop and maybe some marshmallow roms and I don't think you want an old rom.

Also you don't need S-OFF for root, twrp, custom roms, so don't buy it if you really don't need it.
[One (M9) Q&A, Help & Troubleshooting] Donnie267:
That's the thing. Every time I've tried flashing twrp, adb spat an error saying that it couldn't because I have S-on.
[One (M9) Q&A, Help & Troubleshooting] lucyr03:
Hmm that's weird, maybe you did something wrong.

You need to boot in download mode(download not bootloader) and do this command "fastboot flash recovery path/to/recovery.img" but first you need unlocked bootloader with htcdev.