yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] IronTechmonkey:
Even though we should be able to dirty flash, when there are problems the first thing to do is test in a clean flash, of course also making sure there are no third-party factors involved such as substratum or Viper audio magisk modules.

One more consideration FWIW. All of the kernel and device specific stuff recently mentioned by squid2 was added 2 builds ago in the July 21 build, and that is the build which I'm running OK. Since then there has been a big batch of new stuff which is not devices specific added to the July 28th build.
[Moto G 2015 Original Android Development] strugart:
The security patches have never required any clean flash. I updated to the build with the squid2 merge and started having problems. Reverted back as said (all of this dirty flashing) and no issues. Clearly there are a lack of testing of the merge commits.

You dont merge, you do pull request. You tests your code and merge, and test some more. I already did the clean flash, i have no time to waste for bad code hygiene. or bad maintainers etiquette.

Sad if squid2 becomes the official maintainers with these practices.
[Moto G 2015 Original Android Development] IronTechmonkey:
I've been running that build (July 21 2018) for over a week with no problems, nor have there been other similar reports here or at LOS jira.

You've not even established that there is actually a problem with the ROM, which of course logically means you are in no position to criticize the developer. In fact, even if you had clearly established this to be a ROM issue it's still out of bounds to throw such blindly uninformed and non-constructive criticism.

The bad practices here are yours. If you do some research you'll see see that squid2's work has propped up a substantial branch of Moto devices for years, including ROMS, kernels and recoveries across several CM/LOS versions. We're lucky to have anyone, no less squid2, working on this device.

BTW: Here is a bump of a tentative roadmap: https://xdaforums.com/showpost.php?p=77118310&postcount=5876
[Moto G 2015 Original Android Development] strugart:
[MENTION=6485916]squid2[/MENTION]: I decided to go this route and the random reboots are still happening. I am using the build 20180728.

I will provide a logcat in the morning.

Thanks.
[Moto G 2015 Original Android Development] rafaelbarreto22:
I am in exactly the same build (20180728) and I used it first in dirty flash since the previous build and I had no problem with ramdom reboots, I am currently in the same build in clean flash (change gapps from nano to pico) and I do not have that problem you mention ... squid2 is doing a great job as he has always done, does not deserve a negative criticism in that way
[Moto G 2015 Original Android Development] x389sadas2:
Just here to confirm the same. No issues with random reboots since the initial dirty flash of the 20180721 build and none with the current 20180728 build as well. The ROM is running here stable as always.
[Moto G 2015 Original Android Development] prazola:
Camera not working with current 20180728 build.

Edit, reverting to 20180721 won't fix the problem. Saving on external SD works, but telegram and whatsapp photos are black. I gonna try 20180714.

Edit2, back to 20180714 and camera still not working in apps like telegram. It worked before the update to 20180728 so I don't know what is going on.
[Moto G 2015 Original Android Development] Komapatient:
20180728 build rooted with LOS su:

No random reboots, no black pictures in whatsapp or telegram, video working in whatsapp (never had issues)

Edit: I just want to point out this bug, which is really annoying.

https://jira.lineageos.org/browse/BUGBASH-444

I think this was not fixed with all the WiFi updates.
[Moto G 2015 Original Android Development] pjc123:
No problems whatsoever here with dirty flashing either the 07-21-2018 or 07-28-2018 builds. In fact I have been dirty flashing builds for 15 months, every time a new set of kernel updates are released or an Android Security Update is added to Lineage. In all that time I have not had any troubles with my phone, unlike stock Google Android where I had several problems. I am also super thankful to squid2 and Alberto97 for extending the life of my phone.
[Moto G 2015 Original Android Development] visakhmv:
WhatsApp video sending issue seems to be fixed in 20180721 build also Boomerang (Instagram) seems to be working fine.
[Moto G 2015 Original Android Development] Ellahi:
How to get certified device?
[Moto G 2015 Original Android Development] Pic@rd:
Storage exeption

Hello, I have a serious problem with my storage. First this problem came with Firefox, I was not able to download anything. I ignored it and used other apps. Finally I anted to make a Signal backup and the app isn't able to write anything to storage. Does anyone knows any starting point where I could take a look to resolve this problem? Thank you!
[Moto G 2015 Original Android Development] rajchevli999:
Check privacy guard whether storage permission is disabled or not
[Moto G 2015 Original Android Development] sandor clegane:
What is the latest version of the recent nightly?
[Moto G 2015 Original Android Development] Pic@rd:
Thank you! Got it already yesterday evening with exactly your solution. :eek:

After trying to correct file and folder permissions with adb and no solution I got into permission manager. The permission for storage was granted but the sub-permission "Read external storage" in "Privacy" was set to forbidden...

Is this a bug? I checked and unchecked the permission for memory several times and it didn't change the behaviour of the sub-permission. To be honest I assume that I have set this sub-permission to forbidden anytime in the past.
[Moto G 2015 Original Android Development] rajchevli999:
No its not a bug...
[Moto G 2015 Original Android Development] hadrrr:
I've got a problem with the camera and launcher performance in this LineagesOS release.

Every time I open the Camera and make a photo or scroll through the latest shots and then press the home button all icons and widgets on the homescreen reload. It doesn't happen with any other app.

Is this known issue and is there maybe a solution for it already? I use a Moto G falcon (2013) with LineageOS too and there is no such problem.

I tried the stock camera app, the Motorola camera, the stock trebuchet launncher and Google Now launcher.

I have this issue with lineage-14.1-20180728-nightly-osprey-signed.zip and lineage-14.1-20180707-nightly-osprey-signed.zip. Did not try the other releases.
[Moto G 2015 Original Android Development] Komapatient:
1GB or 2GB RAM?
[Moto G 2015 Original Android Development] rajchevli999:
May b due to high ram usage
[Moto G 2015 Original Android Development] rafaelbarreto22:
It is because of the high consumption of ram, in the moto g 2015 of 1gb of ram it is normal that this happens, normally it has to kill processes to give priority to the app that requires more ram, in lineageos 14.1 for osprey the lmk (low memory killer) is more agressive and this can be mitigated slightly by changing the lmk values with root to lower levels with kernel adiutor or other kernel modifier
[Moto G 2015 Original Android Development] IronTechmonkey:
+1 to that. There's a Jira ticket with various graphs and a description of the LMK issue (https://jira.lineageos.org/browse/BUGBASH-480)... Although I now think it's just another symptom rather than the cause - since I've seen 1GB devices with similarly aggressive LMK settings exhibit better camera performance. To your point though: Even if the default LMK values are not the cause of the issue, tweaking them does seem to mitigate the issue.

Additionally, the LOS camera seems poorly suited to 1GB devices where it does not perform as well as most other camera apps or as well as it does on 2GB devices.
[Moto G 2015 Original Android Development] scattey:
Maybe this could help you https://xdaforums.com/2015-moto-g/general/guide-pass-safetynet-custom-roms-t3603609
[Moto G 2015 Original Android Development] hadrrr:
It's 1 GB. But the Moto G 2013 I am using too has also only 1GB and I don't have that behavior there.

Is there a good tutorial how to change that LMK or check which value is set on my older Moto G 2013, where this issue doesn't apear?

Thanks! Going to check this.
[Moto G 2015 Original Android Development] Ellahi:
Any news los 15.1 official..?
[Moto G 2015 Original Android Development] IronTechmonkey:
:rolleyes:

The news is right there in the post you quoted - a roadmap for official LOS Osprey 15.1 is described and it is stated that there is no time frame. No time frame means no time frame so your question is answered right there.

FYI, asking for ETAs is near the top of the list of things that are considered inappropriate in development forums. Asking for an ETA while ignoring the post you quoted which contains the answer is even worse.

If you are interested in the next step for LOS 15 on Osprey, or if you want to contribute to its development (which is the purpose of this thread) then stay tuned to see when the test builds (that were mentioned in the post that you quoted) are released, then test them and provide bug reports about the things that need to be fixed before it is made official.

[EDIT] It occurs to me that LOS 15.1 for Osprey might appear in a new XDA thread so in addition to watching for any news about that here in this thread, we can also watch for new threads created by squid2 or Alberto97. At transitional times like this (between android/LOS versions) it can be informative to occasionally review the recent posts of the maintainers and developers for news of updates or progress.
[Moto G 2015 Original Android Development] squid2:
WiFi Test Build

I'm in the process of wrapping up the last remaining bugs on this ROM, to bring it to a good final state I can consider finished. Two remaining bugs include Bluetooth briefly cutting out when going out of WiFi range, and a rare issue where the device refuses to go to sleep when connected to certain WiFi networks. The latter issue has been present since the CM12.1 days, but it was fairly rare (only seemed to occur on my office WiFi and almost nobody else complained). A recent bug report reminded me of that issue, and I thought I should try squashing it. This test build contains some WiFi driver updates that should hopefully address these issues.

Areas to focus on testing are:

Scanning WiFi networks

Connecting to various WiFi networks

WiFi tethering

Going in and out of range of WiFi, disconnects and auto-reconects

Using Bluetooth while going in and out of WiFi range

If things went well, apart from the Bluetooth issue that I hope this resolves, everything else should work the same as before for most users. It should also fix the sleep issue on my office WiFi, which I'll test next week when I return home.

Download link: http://www.mediafire.com/file/b60s6l9eu52r36c/lineage-14.1-20180809-UNOFFICIAL-osprey.zip/file
[Moto G 2015 Original Android Development] JoshinPl:
[MENTION=6485916]squid2[/MENTION] The ROM in download link contains the same changes as listed here: https://www.lineageoslog.com/14.1/osprey ?
[Moto G 2015 Original Android Development] hovnonium:
Its irrelevant because its wifi test build...but I would say so.
[Moto G 2015 Original Android Development] squid2:
It contains all the changes listed there, plus a number of unmerged changes up on Gerrit.
[Moto G 2015 Original Android Development] diego aleson:
Test build

Wifi don´t work..... (obtaining ip andress....)
[Moto G 2015 Original Android Development] IronTechmonkey:
WiFi working fine for me in clean flash of the new unofficial build with OpenGapps Pico and LOS SU. Tested OK on 2 different wifi routers with static IP assigned to device's MAC address by the primary router which handles DHCP. Also tested OK with automatically assigned IP addresses (which were confirmed to be different addresses).

You've provided no information that supports the possibility that this is a ROM issue, and the aforementioned testing seems to indicate that it is not a ROM bug. That being said, this is not to say it could not be a bug but if you want to establish it as such and help fix it then you should provide the expected bug testing details including the following:

- Confirmation of proper flash method used; Eg no 3rd part factors, description of process.

- Description of Wifi circumstances; Eg Wifi/LAN configuration.

- Log captured while issue occurs.
[Moto G 2015 Original Android Development] squid2:
Adding on to what [MENTION=5119654]IronTechmonkey[/MENTION] said: one of the changes in this build apparently caused DHCP issues for a small number of users back in the CM12.1 days, which is why we reverted it. It also happened to cause the sleep issue that seemed to affect nobody but me on my office WiFi. Back then, reports were very vague as to what was wrong, but the revert seemed to make most people happy (apart from myself). We never properly investigated this.

I would appreciate seeing a logcat of the period where you are trying to connect to WiFi and obtain an IP (I find it easier to find the section of interest when I don’t have to parse 10k lines of logcat where the problem happened around 30 minutes ago...). I would also like to know the WiFi network configuration, including router brand, router custom firmware if in use, authentication type (eg. WPA2 Enterprise), and type of IP the router usually assigns (IPv4 or IPv6, subnet mask).

Also, just to be clear: this is a network you can connect to without issue on regular official weekly builds, right?
[Moto G 2015 Original Android Development] Shreeram02:
ok this is agust update and i have set pattern but as soon as i open my phone opens directly.
[Moto G 2015 Original Android Development] IronTechmonkey:
Since this seems to be a usage issue rather than a ROM development issue please post in the general Q&A thread here: https://xdaforums.com/2015-moto-g/help/rom-official-lineageos-14-1-qa-thread-t3545422. Please don’t reply to this post in this thread. If you want to reply to this post please use the Q&A thread for that as well.
[Moto G 2015 Original Android Development] IronTechmonkey:
Getting into the testing nitty gritty of the moment.

- Scanning WiFi networks:

Implied by previous testing to be OK. One note though. There was an instance or 2 where - when wifi was switched on then off in fairly rapid succession, the indicator showed wifi as being disabled while the lower part of the screen said "scanning"; As if it was stuck in some in-between state. That was easily rectified by waiting a few seconds and toggling. I've seen this occur before on different ROMs/devices and don’t think it is a bug. Just wanted to flag it in case it relates to anything else later discovered.

- Connecting to various WiFi networks:

OK on 2 different Wifi routers, where each router is managing its own wifi access with different authentication on each, and all the LAN management being done by one of the routers.

- WiFi tethering:

Although I have no SIM (so, not testing all facets) Osprey did successfully host a hotspot to which another Android device was able to connect and through which a webcam was viewable.

- Going in and out of range of WiFi, disconnects and auto-reconnects:

Good auto switching when moving between 2 routers which have some overlapping range and some exclusive range. Back and forth, 4 passes, each time the switch occurred fairly quickly after the signal of the presently connected router dropped. It should be noted that since my device has no SIM there is no complication or additional lag of mobile data being involved in the switching.

- Using Bluetooth while going in and out of WiFi range:

Remained connected to a BT keyboard while reproducing the wifi connects/disconnects described above. Note: This was with display on all the time and not a good approximation of what might occur with a BT headset while the display is off.

FWIW by comparison to the problem cases: I'm connecting to following wifi routers.

1) TP link TL-WR720N router running latest commercially available update to native firmware (several years old). Wifi MAC filtering disabled.

2) TP Link WR740N router running latest compatible WRT Firmware (several years old) . Wifi MAC filtering enabled. This router is also handling DHCP & other LAN services.

Lastly and on a different track, revisiting the old misnamed "LMK" issue. Although I don’t experience the issue as much now when browsing multiple tabs in webview type browser (Naked Browser) this could be due to a lighter load on the device as it is now used as a phablet with no SIM. That being said, basic use of the native camera, even just opening menus, still does cause significant killing of other apps and services which does not occur in Moto G 4g 2014 Peregrine with same RAM (1GB). I'm not trying to push this onto any to-do lists but am still available to test it if there is any direction to run with it.
[Moto G 2015 Original Android Development] squid2:
Your thorough testing and detailed reporting is much appreciated. I’ll let a few more people try out the test build since the old DHCP issues appeared to only affect a small percentage of users (or more likely a small percentage of routers).
[Moto G 2015 Original Android Development] IronTechmonkey:
Replied in Q&A thread: https://xdaforums.com/showpost.php?p=77343925&postcount=444. Please take any follow up over there for now.
[Moto G 2015 Original Android Development] Vvk380:
[MENTION=6485916]squid2[/MENTION] i know ur working on los 15.1.but i want to draw ur attention to couple of bugs/issues which are still in los 14.1

1.Copying file from Internal memory to SD card shows some random size and if we try to open it..show curropted while actually its copied properly.

This bug was there in oreo rom also but there is commit to fix it..so pls check if that fix will work with N also..

Here is that commit that fixes that copy issue-

https://github.com/rahul9999xda/and...mmit/c72ef8712fc5b7d3a89617b9c7c0849892c6d2c3

2.Play store is not certified-so we cant use some payments app like Google tez(pay)..also its fixed in oreo..

And sorry if i said something Noob-Friendly

Thank You !!
[Moto G 2015 Original Android Development] hovnonium:
Dont know anything about the 1st problem but to the 2nd one- my device is certified and Ive just flashed opengapps.

Squid, will there be any other changes to los 14.1 or is this the ''final'' form?
[Moto G 2015 Original Android Development] Vvk380:
See this ss... And for 1st problem copy any zip file from internal memory to sd card
[Moto G 2015 Original Android Development] Ellahi:
Only osprey 14.1 is not certified.....

But Merlin is see certified ...... :(
[Moto G 2015 Original Android Development] rtrock:
Screen is not turning off while on call

I just flashed the latest build of THE ROM and while i was on phone call ... i guess an issue with proximity sensor occured .

I even tried to wave my hands in front of the sensor but the screen was not turning off .

What might be the issue ?

Anybody's will be much appreciated .

Thanks :)
[Moto G 2015 Original Android Development] :
for about 2 months updates - clean flash always my camera has FC after taking a 1-2 photos
[Moto G 2015 Original Android Development] IronTechmonkey:
This may or may not be an actual bug with the ROM. If you think it is a bug with the ROM (rather than an issue introduced by a 3rd-party factor or modification then you should create a proper bug report including step-by-step details about how to reproduce the issue as well as a log taken while you reproduced the issue. You can file the bug report at

at LOS Jira https://jira.lineageos.org) official problem ticket system for Lineage OS) as well as in this thread.
[Moto G 2015 Original Android Development] IronTechmonkey:
It seems unlikely that this is an actual ROM bug. On my Osprey in clean flash of most recent build, camera seems fine and is not experiencing FC in various picture modes. I would suggest reviewing your clean flash process to make sure that you are actually clean flashing and not doing some of the many things that some people falsely claim is clean flash. If you want help reviewing your clean flash process you could search the Osprey LOS 14.1 Q&A thread where there are some descriptions of proper clean Flash and you could post questions about flashing there. This thread would not be The appropriate place for that stuff. If you do think this is an actual ROM bug then you can file a proper bug report as described in the previous post.

[EDIT] One note about the LOS camera on Osprey: The LOS camera is a resource hog disproportionate to anything else in the ROM and does not always perform well on 1GB devices, and it may fare a bit worse on 1GB Osprey devices. Normally the symptoms of this would be the killing of other non native apps and services (in my case, Tasker app and LMT launcher) but not camera FCs. IMO this is not likely to be a factor in your case but it is worth keeping in mind.
[Moto G 2015 Original Android Development] rtrock:
Well Thanks for looking up into the issue which I stated and I appreciate that a lot :)

Eventually , before getting ur reply , i did another phone call and the proximity sensor was working as I checked that by waving my hand in front of the sensor .

Maybe the phone was playing some kinda game with me ...LOL
[Moto G 2015 Original Android Development] rtrock:
Information regarding the nightly updates

There are some doubts which I need someone to clear for me .

1. Can we download and Install the nightlies automatically or do we have to do it manually via twrp recovery?

2. While updating the latest build via recovery , will our phone's memory and the apps which are there on the phone still remains ?

3. Do i have to re-root again after updating my phone with the latest nightlies ? Currently I am using Magisk for Rooting .

Thanks :)
[Moto G 2015 Original Android Development] IronTechmonkey:
I'd be glad to answer as would (probably) others, but that is a Q&A question. Please post in Q&A thread (Iink at the top of each page as viewed in web browser).
[Moto G 2015 Original Android Development] rtrock:
Ok ... THANKS :)
[Moto G 2015 Original Android Development] Mugesh ML:
Do not disturb access during call issue

Hi, During incoming and outgoing calls Do not disturb access is automatically enabled so when I recive another call when I am talking to someone it does not shows and call waiting also has error(i am using jio sim). Mine is lineage os 14.1 Moto G3 2015 osprey . Please do needful:)
[Moto G 2015 Original Android Development] anjanikmr39:
When will lineage OS 15.1 will come officially?
[Moto G 2015 Original Android Development] IronTechmonkey:
Even if asking for ETAs was not a no-no that is a Q&A question so a reply has been posted in the Osprey LOS 14.1 Q&A thread. https://xdaforums.com/showpost.php?p=77676896&postcount=460.
[Moto G 2015 Original Android Development] angel6700:
battery life in last nightly

Hello,

I've been using this version since more than one year without any problems, even lots of updates with the LineageOS updater.

But with last nightly (29-09-2018), I'm getting suddenly power-off with battery level greater than 50% and cannot switch-on again until I plug a charger.

So, the question is if anyone else is experiencing the same behaviour with this version. I know about battery calibration (which seems of no help here) and battery ageing. But one week ago (with a version from August ) I was not experiencing anything like this.

Thank you.
[Moto G 2015 Original Android Development] rtrock:
Maybe , itz the battery hardware problem .

Sudden drop of battery level and then the phone getting switched off is a sign of swollen battery .

It happened with my earlier devices .