yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] adityak1303:
What I meant to say was for locking the bootloader you need to be on stock firmware. Only after installing stock firmware you'll be able to lock the bootloader.
[Moto G 2015 Original Android Development] KrisM22:
How would you lock it? I didn't know that was possible for the Moto G3...
[Moto G 2015 Original Android Development] Gravemind2015:
Here you go.

Sorry for OT.

Broadcasted from Zeta Reticuli
[Moto G 2015 Original Android Development] ci92ccio:
I've just flashed this rom, but now wifi doesn't turn on.

Prev ROM: Cyano 14. I have made Wipe Data, calvik, system and Internal storage (I think)

How can I fix this issue?
[Moto G 2015 Original Android Development] KrisM22:
a) you don't need to wipe "internal storage" - that is that little bit of storage that you can access like the SD card. - The ROM uses that space to store some info ("android" folder), and various apps like backups put stuff there. Generally good NOT to wipe that or SD card.

EDIT: Generally, don't wipe "internal storage" or SD card as this is where TWRP puts its backups/nandroids.

b) As to the wifi - I have no idea - What gapps did you flash?

EDIT: didn't you use wifi during the install?

I guess I would try to reflash - wipe, advanced, dalvik/art, data, system, cache - flash rom, flash gapps, flash root if you use one, reboot.
[Moto G 2015 Original Android Development] limitedMUSCL:
Try going into Settings > Wi-Fi > {the three dots on right upper corner} > Advanced and change the Wi-Fi region code. I live in Brazil and changing to Europe made it start working.

---------- Post added at 10:05 PM ---------- Previous post was at 10:02 PM ----------

Anyone having issues with the audio (ringer, speaker) not working after unplugging the headphones?

I once made it work back with http://www.tomshardware.com/answers/id-2431845/moto-sound-headphones.html but today it didn't work.

It appears that this is related to a call going into mute (I see the silence notification icon) and than after call is ended audio does not get back (notification icon is still there).
[Moto G 2015 Original Android Development] KrisM22:
To make sure the jack itself isn't stuck I would plug and unplug something many times.

I popped my headphones in and out many times and the only thing I noticed was that when I unplug them the player (google play music free) pauses. always. I can always get noise by pressing play - speakers or headphones.

What player are you using and what audio add-ons?
[Moto G 2015 Original Android Development] Edinho376:
I have a XT 1543. Since my fist Lineage install i've been using just 1 SIM card. Last week i started using 2 SIM cards, and have issues when i want to restart the device. The phone freezes, and i had to force reset.

Also, i noticed that when the phone reboots i have to select preferred SIM for SMS and mobile network again, cause it clears these settings...
[Moto G 2015 Original Android Development] KrisM22:
It is my understanding that there are issues with LineageOS and MotoG with 2 sims. It is my hope that you will take logs of these errors and file bug reports so we can get it more stable. Thanks.
[Moto G 2015 Original Android Development] balrasmart:
First of all I would thank all the developer for making this awesome rom for our device as the rom is good but I noticed few bugs. When I was capturing pic of my notebook on my Moto G3. I noticed a bug when the flash was on the pics went blurry but in flash off mode the pics were fine. Plz help. And also in official motorola camera on play store the touch does not work properly.

Second While I was transferring file on my pc using usb cable some of the latest files were not visible on my pc but they shown in my phone. Please solve these bugs in the latest build of this rom.
[Moto G 2015 Original Android Development] pjc123:
I get this issue on and off with various ROMS, including it happening with Lineage (happens mostly with TWRP and Titanium files) where I either don't see the files or the transfer to the PC fails. When that happens I do my transfers either when I am in TWRP or via an adb pull and I can get them onto my PC. Also make sure you have the latest and correct Windows drivers (Both the regular and Google USB driver if you use that as well).

I do not have this issue. I can't speak for the Motorola app, as I don't use it.
[Moto G 2015 Original Android Development] KrisM22:
If you do a refresh, they will appear. Some app like media re scan.
[Moto G 2015 Original Android Development] rahul9999:
New update is up for download - https://mirrors.dotsrc.org/lineageos/full/osprey/20170504/lineage-14.1-20170504-nightly-osprey-signed.zip

Changelog - https://www.cmxlog.com/14.1/osprey/
[Moto G 2015 Original Android Development] PixCrow:
any issues with dual sim model XT1550?
[Moto G 2015 Original Android Development] drkhalidomer:
Can't see New App "Jelly" in new Build 04052017 as it is quite evident from recent changelog ! ? May we will get in next one ?
[Moto G 2015 Original Android Development] Subinsmani:
sry bro it was added.. as the app is early stage so there is so many bugs... so they revert back jelly browser.. still it is in under developing..

https://review.lineageos.org/#/c/170490
[Moto G 2015 Original Android Development] drkhalidomer:
Yeah ! Forgot to see this commit

Thanks
[Moto G 2015 Original Android Development] Molu4u:
Can't install the latest nightly version through update
[Moto G 2015 Original Android Development] KrisM22:
3 dots delete updates and try again. If not, download to PC and copy to phone.
[Moto G 2015 Original Android Development] Molu4u:
Deleted the download no use of it still not downloading
[Moto G 2015 Original Android Development] KrisM22:
repeat: download to PC and copy to phone.
[Moto G 2015 Original Android Development] Molu4u:
After downloading process to install thg twrp
[Moto G 2015 Original Android Development] arbasakbar:
A blue light splashes on my lock screen. Anyone feeling like this ???

Only when i wake up my phone and on lock screen
[Moto G 2015 Original Android Development] KrisM22:
what are you asking?
[Moto G 2015 Original Android Development] Molu4u:
How to install through twrp
[Moto G 2015 Original Android Development] KrisM22:
boot to TWRP

TO DIRTY FLASH... BOOO!

tap install, point to thing you just downloaded and copied to SDcard.

swipe

tap reboot.

TO CLEAN FLASH... YAY!!!

tap wipe

tap advanced

select dalvik/art, data, system, cache. DO NOT SELECT internal storage or sdcard.

swipe

back to main menu

flash rom as above.

flash gapps as above (get from opengapps arm 7.1)

flash root if you have/want.

reboot (if at main menu tap system after reboot.

step 5 in

https://xdaforums.com/2015-moto-g/g...gin-how-to-t3599251/post72111431#post72111431

---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------

I bet you're using a theme engine! ? :)
[Moto G 2015 Original Android Development] arbasakbar:
No
[Moto G 2015 Original Android Development] KrisM22:
rats - that would have been so easy. I don't see it here. We'll see if anyone else notices it...
[Moto G 2015 Original Android Development] Hedied4me:
People post this same statement every single week.
[Moto G 2015 Original Android Development] rafaelbarreto22:
I have a problem, when I try to restart the phone from the shutdown menu the ui freezes and I have to apply a forced restart

This is normal?
[Moto G 2015 Original Android Development] kaushiknadig:
This happens randomly on all ROM's
[Moto G 2015 Original Android Development] IronTechmonkey:
No that's not normal. I experience the same thing sometimes when restarting or shutting down. It seems to occur when the SD card is being unmounted but that is a guess. What size and format of External SD do you use? In any event, if you can reproduce this reliably, IMO it would be worth logging and creating a Jira ticket for it.

---------- Post added at 05:51 AM ---------- Previous post was at 05:38 AM ----------

That is an oversimplification. It would be more accurate to say this occurs occasionally in some ROMs under some circumstances.

This seems to be a more acute and clearly defined issue. Freezing upon shutdown or reboot over 50% of the time (as is the case on my Osprey device when I'm not testing kernels or kernel settings) does not seem random, and is worth a proper and bug report.

Also, it may (or may not) be the case that the LMK stuff I'm testing might mitigate these freezes, but first things first - More about LMK tomorrow. As to the shutdown/reatart freeze, logs from people who experience it would be helpful.
[Moto G 2015 Original Android Development] figg2blet:
Hello, I did a clean install with latest 20170504 firmware and just like 20170427 firmware there is still phone network problem. Lte working a while, then h+ shows up, sometimes losing network signal, then back to edge, h+ but never back to lte.

The only solution I find is to go to settings/network and refresh the network, or reboot.

Am I the only one having this problem?
[Moto G 2015 Original Android Development] xfahim:
Hi, is anyone else facing this battery issue? Doze is not working at all, battery drain in the background is a constant issue for me even with the newest build. I run no modifications or tweaks, not rooted, just the lineageos rom. I've attached a list of my applications and battery graph. I'm ready to provide further information if needed! Thanks!

Imgur mirror in case attachments doesn't work: http://imgur.com/a/kdmIK
[Moto G 2015 Original Android Development] mateusdalmeida:
I'm using the soft settings in lmk and I do not have the freezes.
[Moto G 2015 Original Android Development] IronTechmonkey:
Thanks for the information. Maybe that tweak fixes more than one issue. A couple of questions for you: By "Soft" do you mean "light" or "very light in Kernel Aduitor, or are you using something else to change them, in which case, what are the amounts of RAM designated for the various categories:

Foreground Applications

Visible Applications

Secondary Server

Hidden Applications

Content Providers

Empty Applications

Also, did you see the shutdown freezes before changing the LMK settings?
[Moto G 2015 Original Android Development] KrisM22:
your screen/display is at 15% - this is not a battery issue - you are keeping your display on a lot.

---------- Post added at 11:38 AM ---------- Previous post was at 11:37 AM ----------

Run a log and file a bug please.
[Moto G 2015 Original Android Development] Hedied4me:
That's a hefty list of apps, many of which will run in the background causing battery loss unless you use an app like Greenify or Servicely. Just my two cents.
[Moto G 2015 Original Android Development] IronTechmonkey:
20 hours running with 9 potential hours to go actually does not seem bad for medium to heavy usage scenarios on Osprey. That being said, a rough gauge of battery efficiency is the % used by screen which in your case is relatively low. Bluetooth is definitely eating some of it. If during that time you were playing music (especially if to a BT headset) that actually seems like OK battery life. Osprey does not have the best battery life.

In any event, one of the best utilities for diagnosing battery consumption is Better Battery Stats, which puts little to no additional load on system and collects stats which might help you find process hogs, wake-locks or, usage patterns that might be tweaked to get more battery life. https://xdaforums.com/showthread.php?t=1179809.
[Moto G 2015 Original Android Development] xfahim:
And about Bluetooth, yes I use Bluetooh headsets/speakers and a watch which is connected all time time.

This is surprising for me. I guess I'll have to clean up some applications since I have them on my primary phone already.

I think my main issue is standby time. For example, I lose around 15~18% at night. I'll look into Better Battery Stats. Thanks!

---------- Post added at 02:54 AM ---------- Previous post was at 02:52 AM ----------

Most of the apps are one time usage kinda app honestly (ordering stuffs/tickets etc.) Which ones should I greenify in your opinion? I Just looked into Greenify and it seems promising.

---------- Post added at 02:57 AM ---------- Previous post was at 02:54 AM ----------

At that time screen on was 2h 21 minutes. Is that normal for osprey? Thanks for pointing out my lack of knowledge about this! I kinda want better Standby time.
[Moto G 2015 Original Android Development] IronTechmonkey:
Makes sense, that percentage (as opposed to something like 30% or more) seems more like a wakelock than some kind of processor revving. Look for wakelocks in BBS.

That's what I thought (about one time usage). As to Greenify, IMO even though in some cases it may help people keep more apps installed, in the case of ROM testing it can obscure results. If you are interested in maximizing battery life with Greenify you can problay find many good suggestions in a Greenify thread somewhere.
[Moto G 2015 Original Android Development] KrisM22:
a) I would say 20% would be normal for night - I shut mine off because If I'm asleep I don't need it.

b) greenify might help you by 5% but if the screen is on a lot, I wouldn't expect much more. But I haven't used it in years.

c) years ago I used BBS betterbatterystats a lot and it was essential because the ROMs then were always leaving something on, or waking up frequently to check something. But the only reason I checked was that my battery was taking a dive (so it was essential to have spare removable batteries to swap in). With this one I haven't felt the need - the only time the battery goes down is when I have the screen on [edit: add "a lot".] I leave it on all day and charge over night. I rarely see it go below 90% - 80% if I'm testing /flashing a lot. If I have a serious rom problem I'll leave it plugged for the hours I'm playing with it.

EDIT: I don't feel/notice a difference in battery use from the 1 year of 6.0 stock and a bunch of months of LinOS. EDIT: LinOS is actually better because I wasn't hammering ROMs and TWRP all the time then, like I am now.
[Moto G 2015 Original Android Development] xfahim:
So I install BetterBattery Stats, at night, I leave the phone and take a dump of the stats in the morning to check wakelocks, am I right?

Oh then I won't bother with Greenify right now. I'll use better battery stats for now and see if I gather something.

---------- Post added at 03:25 AM ---------- Previous post was at 03:19 AM ----------

a) But I have friends with android that doesn't lose *any* or a very low amount of battery at night. I sometimes use the phone to set an alarm in case my bluetooth speaker fails or SO doesn't wake me up.

b) Then I'm not bothering with Greenify right now.

c) Yes I'm gonna use BBS tonight, so if I got it correct, charge phone up, unplug, sleep, wake up, then share the dump file to check? (Does the battery need to be 100%?)

Reply to edit: Could also be physical battery itself!
[Moto G 2015 Original Android Development] KrisM22:
lot of repetition here but that's ok. probably not physical battery. You might do 2 nights worth of tests - one with partial battery, one with full. Yeah, I agree - BBS first, greenify later. Compare actual screen on use with your friends'!

---------- Post added at 05:30 PM ---------- Previous post was at 05:28 PM ----------

if you leave your phone on all night, when do you charge it to full?
[Moto G 2015 Original Android Development] IronTechmonkey:
To each usage case its own, but 20% is on the high side of most recommendations for an idle overnight period of eight to ten hours. Something like 1.5% per hour seems to be a common report when the device is not used (in human hand) for that whole time. If I can resist reading news on-line before going to sleep I often see 1% per hour over night (5-8 hours). Of course a lot of this has to do with different battery charging and usage cycles such as you describe when doing more or less ROM flashing.

To your point "...the only time the battery goes down is when I have the screen on", I think that is the nature of Osprey with it's bigger screen and faster processor but approximately same overall weight to Peregrine (which I get more battery life out of even though it is on Mobile data and Osprey is not) - Osprey seems to idle OK but burn battery quickly when in use.

---------- Post added at 05:56 PM ---------- Previous post was at 05:51 PM ----------

I'm seconding [MENTION=2945516]KrisM22[/MENTION] on this. That seems more like usage or background activity than bad battery. When you start to notice parts of the battery consumption range drop precipitously and repeatedly, such as first 10% always used in just a few minutes, then it might be a physical battery issue, although even then a few full charge cycles might help.
[Moto G 2015 Original Android Development] KrisM22:
added the words "a lot" to the end of that sentence. type not = think/meant.
[Moto G 2015 Original Android Development] IronTechmonkey:
Assuming that is a reference to the mention a page or 2 ago that the screen was on a lot during that overnight period.. it is to the point indeed - not a battery issue. Also not a ROM issue, so I'm off to do some LMK, night-mode, and camera testing.

---------- Post added at 11:42 PM ---------- Previous post was at 11:38 PM ----------

You may have just diagnosed the source of your battery drain.;) Look for things related to that in the BBS.
[Moto G 2015 Original Android Development] limitedMUSCL:
I'm using the stock player, but the same behaviour happens with google play, or even the notifications, call speaker, etc. Everything disappears as if, even without the headphones, the phone is still reading a "headphone plugged in" status.

The trick on the link I provided help revert this status.
[Moto G 2015 Original Android Development] KrisM22:
so changing ringer volume?

So I would ask that you file a bug (weekend) possibly one log would start at speaker already not working, and you change the vol and it works - so short log.

Another log would be one where it's working, it breaks (remove headphones?), and then change vol and make it work.

It would be important to specify what headphones you are using - if it happens with different ones, that would help.

Also use stock apps if at all possible, but state if prob occurs with other apps..

Thanks.
[Moto G 2015 Original Android Development] IronTechmonkey:
LMK with apps installed

In re Lower LMK settings improving performance https://jira.lineageos.org/browse/BUGBASH-480:

The commit about "content provider" items being mistakenly killed (https://review.lineageos.org/#/c/169885) did not improve the intrusive app killing. I'm still seeing user apps that are normally resilient being killed and not bouncing back under Osprey's default LMK settings. Getting into diagnosing this with apps installed on the device. The apps that are most noticeably impacted (and therefore become indicators that something may be amiss) are:

1) LMT Launcher, which usually rebounds from being killed (eg during sustemui crashes in previous ROMS) but is now killed until app manually opened.

and

2) Tasker, which is being killed and removed from the status bar but has enough hooks into the system to wake up and restore the Tasker status bar icon when called in the background. It has been very rare to see Tasker go down like this.

I'm using the taking of a panorama picture as a reliable inducement for the issue but there are other apps and combinations of apps that can induce it. Through over 10 tests (over 20 if "default" and "medium" LMK profiles are counted separately) my apps were noticeably killed as described above every time under Osprey default settings and never under Kernel Adiutor's medium profile.

Each of the attached logs (at jira) spans the following actions:

- Return to home-screen from matlog.

- Open camera.

- Switch from regular to panorama mode.

- Take panorama picture.

- Swipe to view new picture, swipe back to camera.

- Back button to home screen.

OspreyLoadedLMKdefault = Osprey with user apps installed, using default LOS LMK settings (red line in attached chart)

OspreyLoadedLMKmedium = Osprey with user apps installed, using Kernel Aduitor's medium profile (light orange line in attached chart)

Also, an issue where the device freeze just before rebooting (requiring button presses to force reboot - no ADB in that state) may be incidentally fixed by the LMK tweaks but I have to remove SD card as a factor (hypothesis - unmounted before reboot goes bad) and log this across power cycle.

Previously posted details in re LMK:

https://xdaforums.com/showpost.php?p=72086094&postcount=4416

https://xdaforums.com/showpost.php?p=72124036&postcount=4446
[Moto G 2015 Original Android Development] GadgetManIRL:
Have the latest update installed on my xt1541, still having issue with data dropping off with only a reboot fixing it. Has a proper fix for this been found yet?
[Moto G 2015 Original Android Development] KrisM22:
Have you filed a bug report for it yet? If not, probably no.
[Moto G 2015 Original Android Development] GadgetManIRL:
I was just thinking others would be having the issue already. I will get a logcat of next time. Just regarding the logcat. Should I start it now and let it run in the background until it happens again? I presume only starting the logcat when the data has already failed is too late? Would logcat drain the battery much if ran for a prolonged period? Sorry about all the questions. Thanks in advance.
[Moto G 2015 Original Android Development] Hedied4me:
That's strange, I assumed this had been fixed as I stopped having the issue ~2 months ago and there have been a lot less complaints of that here.
[Moto G 2015 Original Android Development] KrisM22:
yes, let the log run, but note the times when signal strength changes and put that info in the jira report. If it's something that supposedly happens over many hours, the more info you can give, the better.
[Moto G 2015 Original Android Development] KrisM22:
Also you may want to should specify signal strength - settings/about phone/status/sim status/signal strength

rather than just the size of the triangle thing. at each point.

EDIT: I would also suggest you go on to playstore and search "signal strength": - you might install things like "Phone signal" by InPocket and Network cell info lite by Wilysis or whatever hits your eye.

I just ran Phone signal by InPocket and after only a few minutes got this - I'm in Boston area and expected it to be steady.

Posting the sig str graph for the whole duration on the bug would be huge bonus!
[Moto G 2015 Original Android Development] KrisM22:
A continuation - less than an hour and a bunch of cell tower handoffs (red vertical bar)(always? 2 in a row). Understand this phone is not moving more than 16" (inches) from a point on my computer desk. (remember -80 is stronger than -100)

I post this here to show that there is a ton of stuff going on that folks are unaware of - even when we're "doing nothing"!!!
[Moto G 2015 Original Android Development] gh0s8:
sorry to borher guys but after latest update my phone gets the same home screen if someone calls. I do get ringtone so I have to press dialer and it shows > go to main, return to call etc..any solution for this
[Moto G 2015 Original Android Development] Subinsmani:
set phone app as default and reboot the device..
[Moto G 2015 Original Android Development] elangek:
Help

In the link appear several options to download .but you have to download all. Or only the first help:llorando:
[Moto G 2015 Original Android Development] xfahim:
It's my secondary phone, so usually during the day.

---------- Post added at 12:52 AM ---------- Previous post was at 12:48 AM ----------

Possibly. I think it's just a mix of Google Now updates in the background, location reporting, Network Location Provider when it comes to wake-locks and battery drain when the screen is off. But you're right about osprey using a lot more battery power when the screen is on, but nothing really can be done, right?