yashsingh1/xdaforums huggingface dataset:
[Moto G 4G Android Development] IronTechmonkey:
I'm not experiencing increased battery drain in June 25 build but every usage case is different. for what this is worth, a recent fix to an issue where some MP3s would skip during playback might (or might not) cause increased battery drain when playing MP3s. The details are in this Jira ticket: https://jira.lineageos.org/browse/REGRESSION-577?filter=-2. (I've not yet re-visited the ticket to confirm that the skipping is fixed and inquire a bit more about possible battery drain but plan to do so later today).

If you want to dig deeper into the source of battery drain you can try Better Battery Stats which is a great app for that and it's XDA thread is very helpful: https://xdaforums.com/showthread.php?t=1179809. [MENTION=7785396]mrLoma[/MENTION] makes a good point about Gapps - sometimes there can be power consumption issues between Gapps and ROM usually related to Google services, and which might be revealed by Better Battery Stats. Also, clean flash.

---------- Post added at 12:04 PM ---------- Previous post was at 12:01 PM ----------

I was just joking about thread topicality. No Xposed for Peregrine? Bummer.

---------- Post added at 12:36 PM ---------- Previous post was at 12:04 PM ----------

On Peregrine (which is my main device) I toggle Wifi manually as needed, which incidentally avoids such issues. That being said, there have been reports in the XDA Moto Otus LOS 14.1 thread about simar issues, although on that device I do leave it on Wifi all the time (dedicated webcam) and it never disconnects.
[Moto G 4G Android Development] kalava:
Thank you, but all steps you mentioned here I already did ( as I mentioned, that I did it via twrp and fastboot with specific roms for restore method, meaning I already did steps you mentioned here).

Only I am not sure I used this source of roms, but so far I found same files are shared over different places. I've from here https://firmware.center/firmware/Motorola/Moto G (1st gen-2013)/Stock/XT1039/ 4.4.4 KK roms.

Ok, thanks for yor help and efforts anyway, I very appreciate that.

Rom I've set back to LOS, so daughter at least cann you as "play tool" :)

Communication only via Viber and wifi, so looking either for Moto G5, or G5 plus.

It is a pity, that Moto G 4G "ended days as mobile phone", as I liked it very much, and this leaded to aquire another 2 Moto's in family (3rd gen).

So far, so good, thank you once again.

---------- Post added at 10:39 PM ---------- Previous post was at 10:33 PM ----------

I am testing, only once I've got mobile radio not working after one week of use ( everything was working perfectly), I've tried to get back radio service with stoch roms and upgrades.

As I didn't suuceded to get radio working currently in any stock rom, I've installed back LOS, which is working perfectly (except radio service)
[Moto G 4G Android Development] IronTechmonkey:
Incidental to something I saw in the Osprey Kernel thread, there was a report of someone loosing radio or WiFi because they were flashing SuperSU after custom kernel. It sounds like you are not doing either of those things so that might not be relevant, but the vague similarity in the circumstances led me to mention it.
[Moto G 4G Android Development] Pupet_Master:
I'm sorry we couldn't find a solution. I really do like this phone very much as well, but at least wifi still work and your daughter will be happy with L-OS :)
[Moto G 4G Android Development] jay20tee17:
I'm not playing mp3's anymore. I just flashed the latest version of gapps. Hope that works out. If not, I'll check Better Battery Stats to find oud what's going on, like you suggested.
[Moto G 4G Android Development] tutticlandestini:
goodmornig,

first, for battery drain:

mrLoma have battery drain after flash 08 june update (full or delta?). I have battery drain for play service after flash 01june zip delta update (i was in 25 may clean new flash). after flash of 08june and 15 june the battery drain go out and now i have a great battery experience.... randomly flash beahvior?

for deep report: i try install first delta zip from upgrade service.. during shotdown make a preparing procedure... reboot.. but stopping after reboot in twrp... i have to install manualy... after reboot my sd is no mounted and after change in a incomprehensible name (M-.^_M-:v{? etc) but work normally... no change on reboot or after over flash.....

for kalava's radio problem: stupid question.. have you try the sim in another phone, or another sim in peregrine?

sorry for my english, is not my native language
[Moto G 4G Android Development] mrLoma:
Wel TBH I hardly ever do a clean flash. I know a clean flash is a better way to make sure you don't get weird side effects but I simply don't always have the time. Just telling my phone to do the standard update automatically is easier. Let's just say I'm testing that way of updating :p.

On that note the download tends to fail a lot saying it got corrupted somehow.

I'll have to check what my last clean flash was. Probably a few weeks ago.

The battery issues I had last week were also play services and android OS.

Yup it was the 8 June build with the battery drain. Again updated using the settings update menu. So I'm guessing you call it a delta.
[Moto G 4G Android Development] IronTechmonkey:
You bring up a good point about using dirty flash as a way of testing that update path because we are supposed to be able to do that however... once there are problems, the dirty flash casts doubt on any test results. At that point, to properly troubleshot and report bugs the issues should be tested in a clean flash. For example, particularly when there are issues with Google services: What if the native Google components in the ROM were updated and after that a clean flash is required that one time in order to get back to dirty flashing successfully? I've seen issues like that before. Yes it's a lot of work but troubleshooting dirty flash issues still usually (but certainly not always) has to go through a clean flash to yield good bug testing results.

-----------

On a different subject: The LOS native SU packages have been updated with new names (and perhaps other changes?) and I had problems earlier today when using the older LOS SU package with today's LOS release for Osprey. Anyone using LOS SU should make sure to download the new LOS SU package.
[Moto G 4G Android Development] kalava:
Yep, tried, this sim works in any other phone, and no any other working sim do not works on this moto g.
[Moto G 4G Android Development] codeisforhumans:
Apologies if I should have RTFM, but I'm not sure where that is and I have two questions:

a) should I just install the latest nightly or is there a more "stable" release?

b) are updates pulled over the air, or do I have to download and flash my device every time I want bugfixes/updates?
[Moto G 4G Android Development] Pupet_Master:
If you are talking about L-OS.. then there is no Stable release yet (as far as i know)

CM13 how ever, the latest is the snapshot so..
[Moto G 4G Android Development] IronTechmonkey:
More issues with LiveDisplay, with possible connection to GPS-on for a certain duration. Details in the comment at Jira: https://jira.lineageos.org/browse/B...issuetabpanels:comment-tabpanel#comment-15286.

Details from Jira ticket (Note: these observations are from the June 15 build so it's possible there have been changes, although nothing at jira or in the change logs indicates that there has been an additional fix. Just worth keeping an eye on):

It seems that there may be more parts to this issue than the twilight mode part that was fixed. For the past 2 consecutive days in Peregrine June 15 build night mode did not invoke when expected. Yesterday a reboot fixed it. Today an exploration of time settings reveals that Live display is an hour or so behind the system time. eg Should change to full night mode at approximately 8:30 PM but does not until clock is set to approximately 9:30pm. The previously suggested toggling of airplane mode did not fix it, but a reboot with time and time zone set to automatic put LiveDisplay back on schedule.

The same thing does not occur on a very similarly configured Osprey device running the same build, Gapps and user apps. The only notable differences between the devices are

1) Osprey has no SIM card inserted, but past experience implies that this might be dismissed as a factor.

2) This issue occurred on Peregrine, perhaps not coincidentally, exactly on 2 days during which I ran GPS continuously for over an hour to track rides (which I had not been doing before).

Note: The duration of the GPS "on" state may be significant because quick GPS fixes (which I perform frequently for testing) have never induced this before. I cant help but think there is some connection to the legacy of this feature once being dependent on GPS.

Unfortunately cycling in NYC traffic is not a good time to log Android issue but I hope those details help pin it down.
[Moto G 4G Android Development] danibus:
Good day

My parents have both motorola G 4G with stock rom (5.1.1 I think)

Whatsapp always eat their internal space, "no space" message every 3 months, then delete everything...

Is this rom ok for daily use? Just light use: make calls, whatsapp, make photos.

Is this rom able to use SD as "internal space" to avoid whatsapp eat all free space?

Thanks
[Moto G 4G Android Development] kalava:
So, and the "happy end of no service" is following - I've got radio working again, yay!!

So far, after different tries to install stock roms without success get radio working, I've concluded HW fault, and didn't bother any more.

Till yesterday - installed latest LOS, nothing changed, but once again downloaded lollipod radio fw, eu and spain twrp version.

I've tried just to try, because I did this already ton of times.

So far, both installations failed on step erasing modemst1, so I expected to be breaken something more after that.

BUT for my big wonder, aftef reboot I found radio working, and carrier back!!!!

No clue, why stock roms didn't made it work, but now Moto again fully functioning with LOS behind.

So far, so good, I 'll observe, how long this time it will work
[Moto G 4G Android Development] 239:
Yes, but it might reboot occasionally (roughly once a week for me). I'm using it daily (with Open GApps pico) since January and it's great otherwise.

You can format the card as internal storage in the settings. My advice is to use a card with at least UHS speed class 3 (U3) for that.
[Moto G 4G Android Development] jay20tee17:
Updating gapps did not fix it. Clean flashing did :)
[Moto G 4G Android Development] IronTechmonkey:
Physical keyboard: Auto-replace, Auto-capitalization, Auto-punctuate settings do not persist after leaving the setting panel and they don't function in any tested scenario. First noticed in June 15 Peregrine and Osprey. Reproduced in June 29 Peregrine and Osprey. Logged in June 29 Peregrine. Details in this Jira ticket: https://jira.lineageos.org/browse/BUGBASH-761.

[EDIT] Clarification: This would apply to most external (AKA - physical) keyboards which, when used on Android devices, preclude the need for the on-screen keyboard and therefore are more dependent on auto-correct. This is what the options in Settings > Languages & input > Physical keyboard are supposed to handle but do not. To witness it you can test it as described in the jira ticket: with "USB keyboard attached via OTG, or with BT keyboard attached." Even without any external keyboard attached the issue is clear by doing what is described in the ticket in re logging the issue:

- With no physical keyboard attached.

- Open Physical keyboard settings through main settings panel.

- Enable the settings in question.

- Back button to Languages & input.

- Open Physical keyboard settings again = the settings are no longer selected.

-----------------------------

Live Display: In June 15 builds of Peregrine (and Osprey) I was able to reliably reproduce LiveDisplay issues by using GPS (previously mention here https://xdaforums.com/showpost.php?p=72854670&postcount=916). When GPS is used previously in the same day LiveDisplay does not invoke night mode at proper time, and is at least an hour behind (or does not invoke at all) until reboot. Details in the last few comments in this Jira ticket: https://jira.lineageos.org/browse/BUGBASH-226. The pattern is now clear although the cause is not (to me at least), although as mentioned in one of my comments in that ticket: it is hard not to think this relates to the fact that LiveDisplay once depended on GPS fix. With June 29 builds now on both Peregrine and Osprey I'll try to reproduce again.

[EDIT] Reproduced in June 29 builds on both Peregrine and Osprey. More notes in Jira ticket.
[Moto G 4G Android Development] IronTechmonkey:
Another possibility in re auto correct for physical keyboard is that it may be a depreciated feature to be removed from the ROM, in which case we would be dependent on apps supporting the red underline spell check but it seems that there are fewer and fewer apps which support that. The native Messaging app supports it as does the XDA Labs app but surprisingly many text editors and word processors do not. I certainly hope it's not depreciated and that it can be fixed.
[Moto G 4G Android Development] matthias1976:
Location wrong

Sometimes my location is wrong.....

Im in Bielefeld Germany an location says im in Poland.....

see Screenshot
[Moto G 4G Android Development] 239:
Used it for driving and hiking navigation many times and never had this issue.

There is no location icon in the status bar...

Which location mode are you using? GPS + networks or just GPS / networks?
[Moto G 4G Android Development] IronTechmonkey:
Good question. If it is "Device only" it should be fairly accurate if it gets any fix at all. If it is "Battery saving" (AKA networks only - not using the GPS radio) it could be inaccurate for a variety of reasons having to do with the service providers or wifi networks being used, or aspects of the device such as if VPN or firewalls. I would expect "High accuracy" mode (networks + GPS) to be no more accurate than Device only. IDK if the status bar icon would appear for all three modes; It does appear for "Device only" but only when an app is using it. When using "Device only" I get sustained accurate location for tracking rides and trips (but I only use Device only for such activities because it is none of Boogle's business how fast I get around town by bike or who I'm visiting).

I think [MENTION=6076637]239[/MENTION] is onto something in regards to the status bar icon and Location mode. Try "Device only" and see what happens.

-------------------

[EDIT] Since we're talking about GPS, I've done some more testing of LiveDisplay and it has become completely clear that using "Device only" location (and maybe other location modes, but won't use them) causes LiveDisplay to be 1 hour behind schedule. I've ben packing notes about this in the old Jira ticket but it has not been re-opened so I've collected logs and will create a new one next weekend.
[Moto G 4G Android Development] matthias1976:
im on powersave location service.....testing now high accuracy
[Moto G 4G Android Development] Benfll:
You haven't mentioned needing to wipe anything in the installation instructions, which seems odd to me. Is that true?

Also, does the ROM come with root? If not, which one works best for this ROM?
[Moto G 4G Android Development] sevenrock:
Finally there is proof that Bielefeld does not exist ;) SCNR.
[Moto G 4G Android Development] IronTechmonkey:
If you are coming from a recent version of the same ROM (and Gapps) you may be able to dirty flash but I always clean flash (even when updating the ROM every week).

- Clear dalvik & system caches.

- Full wipe (factory reset).

- Flash ROM, Gapps and SU package in same TWRP Recovery session.

- Clear dalvik & system caches.

- Reboot to system.

You can find advice about flashing by doing general web searches, and maybe by checking the LOS wiki.

LOS has its own SU package, available in the Extras section at the bottom of list of supported devices on the download page.
[Moto G 4G Android Development] eminga:
Does anyone else have problems with the recognition of their SD Card?

My SD Card is formatted as internal storage and worked fine until nightly 20170622. With nighlies 20170629 and 20170706, Android doesn't mount it anymore.

Under "Storage", there is an entry "SanDisk SD card" which says "Not inserted" and gives me the option to forget the card. When I reinsert the card, for some seconds another entry "SanDisk SD card" appears which says "Checking...".

In contrast to Android, TWRP detects the card and lets me access the files stored on it.

Any idea how to solve this problem?

EDIT: When trying to create an image of the SD Card with dd, it fails after 2.6GB with an Input/Output error. So I guess, the card is just dying...
[Moto G 4G Android Development] eteles:
Hello guys... I was on cm 13 (android 6.0.1) and after updting I got the no sim card detected error... How can I fix it? Didn´t find anything about it in this thread. Please help! Thanks!

EDIT: Solved. Sim card was a little oxidated. Used a pencil rubber to remove oxidation and it worked. Sorry for the trouble... :)
[Moto G 4G Android Development] IronTechmonkey:
LOL, I was just about to reply while you were editing. Glad you got it sorted out. I've not used the pencil eraser trick for cleaning contacts for a long time (before Androids were a thing). Nice to know it works for this as well.

---------- Post added at 03:14 PM ---------- Previous post was at 03:05 PM ----------

I don't want to take this thread too far of topic but: There could be corrupted sections, or impending failure, or a legacy of encryption and formatting done by the adaptable/internal storage feature (which I'm not a fan of). You might be able to suss out the specific problem by doing some forensics on the drive, eg sector scans, re-partitioning reformatting (some of which may be limited if there is still an encrypted partition on it). There are XDA threads and other forums which may offer advise about those things.
[Moto G 4G Android Development] IronTechmonkey:
July 6 build review of reported bugs (and not bugs).

Clean flash, July 6 LOS Peregrine, with July 6 Open Gapps Pico and LOS SU

-------

Increasing system fonts size pushes countdown timer backspace button off screen; https://jira.lineageos.org/browse/BUGBASH-300:

A particularly easy bug to reproduce, but getting few votes. It would be great if anybody else would vote on this one. It can be easily and safely reproduced by setting system font size to Largest and witnessing the disappearance of the back button in the countdown timer in portrait orientation.

-------

LiveDisplay does not apply the blue screen at night when set to automatic; https://jira.lineageos.org/browse/BUGBASH-226: This is fixed. Also, in regards to night mode being invoked an hour later after using GPS....that may be an intended behavior and I apparently had this backwards in re the remaining partial dependency on location fix.

After a reboot LiveDisplay uses whatever information is available which in my case had the transition occur an hour early (which I thought was the correct time for the transition), and then after a GPS fix it adjusts to make the transition at the proper time (which I thought was the wrong time for the transition). The GPS adjusted time for the transition may be correct one, but I suppose time zones and daylight savings might be a factor. I'm remembering an article or old CM12.1 commit which describes this but cannot find it and would be interested in any available explanation of the mechanism,as well as at which time the transition to night mode is complete for devices at the same latitude as New York City. In any event, LiveDisplay seems to be functioning reliably and serves its purpose when the transition is made at either time.

-------

Physical keyboard: Auto-replace, Auto-capitalization, Auto-punctuate settings do not persist:

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

Apparently the auto-correct settings for physical keyboard which seem to be reverting are actually just indicators of whether they are being used by the input method (the AOSP on screen keyboard). Unfortunately the native AOSP Keyboard does not support auto-correct when physical keyboard is attached. It is possible that third-party keyboards would support it but I'm not certain of that. The explanations of this is in the Jira ticket.
[Moto G 4G Android Development] mateusgpell:
Does Lineage run with the Zer0 byte kernel?

Which one do I install first?
[Moto G 4G Android Development] Rob...:
Yes.

First ROM than Kernel.

Don't forget Gapps!
[Moto G 4G Android Development] IronTechmonkey:
Minor regression in clock + button.

Notification of set alarm pushes the pink add button (+) higher on display where it persists across all clock panels until clock is closed by back button and opened again. A few screenshots below. More details and screen shots in Jira ticket: https://jira.lineageos.org/browse/REGRESSION-821. Should be easy to reproduce if anyone would like to vote for it.
[Moto G 4G Android Development] morph027:
Does anyone knows where to find the experimental build for dirty flash from CM13? My wife won't let me reset her phone ;)
[Moto G 4G Android Development] mrLoma:
I think it's removed due to incompatibility issues.

I use Titanium backup to keep settings and app data.

You could take a nandroid backup too. You should be able to set the phone back to the current state with it, though I have no experience with it, so I'm not sure.
[Moto G 4G Android Development] morph027:
Hm .... what a pity ... looks like i need to ask multiple times which app to keep ;)
[Moto G 4G Android Development] mrLoma:
Haha that sounds too familiar :).

Some apps already backup their own data, mostly Google apps.
[Moto G 4G Android Development] IronTechmonkey:
Spousal inclinations excepted, at this point it really would be better to clean flash LOS 14.1 than dirty flash from CM13.1. To [MENTION=7785396]mrLoma[/MENTION]'s point, TitaniumBackup can back-up and restore app data across the transition and nandroids. I've been hopping through Android and CM/LOS versions this way since Kitkat/CM11.

I use TiBu heavily for apps and app data but not for OS settings. What items do you backup in TiBu to save those settings?

Also, how is your sensor working these days? I've been using Oruxmaps to track rides and the compass has not had issues (although my periods of use are not as long as yours were and therefore less likley to induce the issue).
[Moto G 4G Android Development] mrLoma:
The settings I saved apart from app data are Bluetooth and wi-fi. Don't remember but I think Bluetooth didn't work as well. But Bluetooth is easier to set up again, since I have a whole lot of wi-fi credentials saved by now and only about 3 Bluetooth devices I care about.:)

I thought Google saved the WiFi settings but I'm not sure so I do the tibu to be sure.

It's been a while since I last tested. So quickly checked a few things. The gyro looks like it's working very well (spotlight app works smooth).

Skymap still complains about the compass accuracy being unreliable, not sure why.

GPS looks fine. Google now sometimes reports my vehicle to be parked somewhere on my way to work, but I think that has to do with when the app or GPS wakes or checks or is put to sleep. Don't really care too much about that, I prefer have decent battery life, like we have now. On average I have about 1 day and 16 hours. Since I can put it in the charger while sleeping it's a nice 2 day cycle.

Some days is only 1 day, but I never really feel battery anxiety ?.