yashsingh1/xdaforums huggingface dataset:
[Moto G 4G Android Development] mrLoma:
Last weeks build had all sorts of weird little things indeed. This feels smoother, I hope it stays smooth ?

Last weeks build I had;

-"Google play services" go crazy with the battery usage. I wiped it's cache and rebooted which seemed to fix it.

-Some WiFi lock ups and hiccups throughout the week. Sometimes it fixed itself sometimes a disable/enable did the trick.

-I had my phone shutdown at +-15% battery, but it really seemed flat. I had to recharge it a bit to even get it started. After that it seemed fine. Maybe the battery just needed to recalibrate.

-I had WhatsApp not responded for like a minute. I could minimise it return it etc, but not use anything of the app itself and than all of a sudden it all worked again.

All weird little issues, but nothing really of a big though. For me the build of 2 weeks ago was way better than last weeks.

Like I said today's build looks smoother so I cross my fingers :fingers-crossed:

Btw I love the hold power button to use the torch thing. But it's still in it's own little separate "gestures" setting section while, both those settings in there should be under buttons IMO.

... OK so the gallery still crashes if you try to view your freshly made screenshots with it.
[Moto G 4G Android Development] IronTechmonkey:
Thanks (out of officials). I saw Google Services related processor revving in Jan 31 but not in Feb 7, but different usage patterns can yield different experiences. I'll flash Feb 14 within a day and compare notes.
[Moto G 4G Android Development] panxof10:
Hello everyone, I think i need some help from you guys. The thing is that I installed the last nightly avilable for my moto G lte. After finished, I have no signal, and the phone does not read any sim card, so i think I made something wrong. The bootloader is unlocked and I have last twrp, but i made it from stock 4.4.4. What can i do?

Thanks a lot.
[Moto G 4G Android Development] Pupet_Master:
You need to upgrade the bootloader to the stock lolipop and the radio too
[Moto G 4G Android Development] jdegreef:
I've flasted the latest nightly (20170214) and I still have this problem with the unlock screen that I've already reported : after reboot and after entering the sim card pin code, when I swipe to top to enter my sim code to unlock the phone I'm returned to the lock screen before I finished entering the code.

Am I alone to face this ?

I've dirty flashed the nightly.

If I find time I'll try a clean flash unless someone clean flashed the nightly and have the same problem.
[Moto G 4G Android Development] GlennBrownie:
Migrating SMS/MMS Data from CM13/AOSP To Retain Old SMS/MMS

Hi there,

Obviously we have Titanium Backup... but it does not work to restore sms, but restored everything else fine.

So, this method is based on you have backed up your SMS through Titanium and you still have the backup files for SMS (com.android.providers.telephony-(date)-(time).tar.gz - I think ?)

Also, please note, even after doing this, the stock messenger does not show any sms but my Chomp SMS does, which is what I had previously used so you may find similar issue but just open your 3rd party client and all should be there.

** Please Note, I am NOT responsible for you phone gaining consciousness and murdering anyone or so on. **

This is because in Android 7, they moved the mmssms.db and mmssms.db-journal files to:

so, what you need to do is:

1) install RAR (WinRar for Android basically)

2) Open RAR, Navigate to your Titanium Backup folder, open com.android.providers.telephony-(date)-(time).tar.gz

3) Click through folders, until you get to Databases

4) Click and hold on mmsms.db and then also select mmsms.db-journal and extract the files using arrow at top of screen.

5) exit RAR and open your Root Browser, or ES File Explorer, you get the idea...

6) Delete the contents of /data/user_de/0/com.android.providers.telephony/databases and the app_parts folder, then reboot.

7) move of your attachments into /data/user_de/0/com.android.providers.telephony/app_parts and the .db files into /data/user_de/0/com.android.providers.telephony/databases

8) Then reboot again BEFORE opening your SMS or messaging app

and woolah, your off. hopefully
[Moto G 4G Android Development] IronTechmonkey:
I'm not sure if this is a ROM or Gapps issue, or if some settings or dependencies have changed since previous versions of Android/CM/Lineage, but there seems to be no way to install additional Google Text-to-speech voices. The settings icon (gear) is not present for Google TTS in the ROM's "Text-to-speech Engine" settings. A 3rd party text reader app is able to invoke the "Google TTS voice data" settings through which additional languages can be downloaded and used, but I would expect that setting to be available in the ROM. This is on clean flashed Feb 14 weekly with native SU package and Feb 14 open gapps pico.
[Moto G 4G Android Development] soulchen:
Can't read my sim card, It had been in stock lollipop sometime . I don't know why, and what's else com.android.phone (FC) XD anyone else have been got same problem? XD

---------- Post added at 09:00 AM ---------- Previous post was at 08:58 AM ----------

Can ur phone read the SIM card. Mine com.android.phone (fc)
[Moto G 4G Android Development] IronTechmonkey:
Yes. SIM works on model XT1045. Calling, voice mail, SMS and call recording were all OK.
[Moto G 4G Android Development] akiraware:
Working on XT1040 too
[Moto G 4G Android Development] FabTheZen:
I updated to latest, wiped cache+dalvik, but the wifi always locks up and as you said it gets fixed itself but most times i have to toggle wifi... :\
[Moto G 4G Android Development] mrLoma:
I haven't had any obvious WiFi issues with this weeks build. I'm on a xt1039, but sure if that is of importance.

What I have noticed is that a site via chrome sometimes just freezes for a while. I can't even scroll it. But everything else works. After a little while the site works again, could be related to this WiFi issue.

The phone did get really slow after a few days. So I had to restart it. Which could indicate memory leaks, although this is pure speculation.

The pixel assistent is fun to play with even though it misunderstands me a lot, but that mainly because I'm not a native speaker.

OK I also still have WiFi issues. Just had Spotify stuck on loading until I reset my WiFi. But it didn't happen that much tbh
[Moto G 4G Android Development] GlennBrownie:
I have clean flashed from CM13 to this Valentine days build, I like the features but do feel it is missing bits still...

My main issue is that the phone randomly locks up if I am doing anything high RAM usage, like loading navigation or games, sometimes I give up and just hold power until device restarts it takes that long, lol.
[Moto G 4G Android Development] m60miguel:
How to root?

Can anybody say me if is possible root the rom.

I want that the NavBar take a Pixel Style

Thanks
[Moto G 4G Android Development] Rob...:
On the lineage page is written:

We will NOT be shipping root baked into the ROM.

Root will be a downloadable zip based install similar to gapps installation (only need to flash it once).

https://download.lineageos.org/extras

Addonsu arm you need
[Moto G 4G Android Development] IronTechmonkey:
2 issues in Feb 23 build

1) Tap "Cellular networks" results in FC. This issue has also been reported in Otus https://xdaforums.com/showpost.php?p=71164873&postcount=684. I dont see anything that I can identify as being related to this in the change-log or at Lineage Jira. Will attempt to log and create ticket.

2) Increasing system font size pushes Google TTS configuration button (gear icon) off screen. Reproduced in Feb 14 and Feb 23 releases.

At Normal font size.

At Large font size.

At Largest

I filed a Jira ticket for item 2 (https://jira.lineageos.org/browse/REGRESSION-108) but it is likely to be rejected because this is not actually a regression and Lineage Jira seems to only be accepting regression reports at present. [MENTION=4173406]Kayant[/MENTION], if there is some other route through which this sort of thing should be reported besides jira or this thread please say so.

Also, can anyone confirm whether or not item 1 (Cellular Networks FC) occurred in Feb 14th or earlier version?
[Moto G 4G Android Development] Kayant:
Also far as am aware no. That font bug is an interesting bug.
[Moto G 4G Android Development] akillenb:
The fc on clicking cellular networks only seems to happen for me if there is no sim in the phone.
[Moto G 4G Android Development] Libor1:
Can't access my USB stick via OTG from ES File Manager receiving repeatedly request to allow it but immediately disapering before I can do that. Any advice ? Thanks.
[Moto G 4G Android Development] devil1511:
Hi,

could someone please explain me why my zip signature verification always fails (refer screenshot)? And how can I fix it again?

I'm using the twrp-3.0.2-3-peregrine for flashing the ROMs. The MD5 check is ok (refer screenshot) and flashing CM14 works without a verification error. :confused:

Things I already try:

- flashing twrp again

- flashing cm-14.1-20161222-NIGHTLY-peregrine (boot system) -> lineage-14.1-20170126-experimental-peregrine-signed -> lineage-14.1-20170126-nightly-peregrine-signed (boot system) -> lineage-14.1-20170131-nightly-peregrine-signed.zip (or later build)

When I try to flash lineage I get always a signature verfication error. :eek: :confused:
[Moto G 4G Android Development] _that:
Lineage builds are now signed using their own private key. TWRP's signature check only supports the AOSP test keys. So you have to turn off signature verification for now.
[Moto G 4G Android Development] IronTechmonkey:
As a user of large fonts (Android) or low screen resolutions (Windows and other) I'm accustomed to hitting limits of an OS' ability to accommodate it's own large font sizes but this one is a bit different as it only seems to affect that one field.

At Large font size the text "Google Text-to-speech Engine" should wrap but there is more to it because it does wrap at Largest font size and the button still gets pushed off. This has occurred with Open Gapps Pico and Delta Gapps basic packages for what that is worth. I might have a chance to test a different device for the same thing within a day or so.

[EDIT] A fix has been merged https://review.lineageos.org/#/c/163258/

---------- Post added at 07:32 PM ---------- Previous post was at 07:30 PM ----------

Thanks for clarifying. I had flashed with SIM in device but had not tested this until after removing SIM.
[Moto G 4G Android Development] mrLoma:
This weeks build looks more stable than last week's.

But I still have some issues.

I use the pixel launcher with Google now.

The Google now app seems to stop updating leaving the list empty. I have to restart the phone or clear the Google app's cache to fix it.

Also the Bluetooth audio streaming had gotten choppy, I don't use it very often, do I have no clue when it broke. I closed every app other than Spotify, had memory to spare but it still skipped a second every minute or so. I was only 2 or 3m away from the BT receiver, that used to work flawless under the cm14.1 build afaik.
[Moto G 4G Android Development] FabTheZen:
I don't understand why but I got a complete screwup of my phone after a "quick reboot", when my phone turned back on, it got stuck in a boot loop so I hard rebooted it (held power button) and at its reboot google launcher was reset, it asked me to enter a google account, home and recent buttons won't work, notifications don't show up (but sound+vibration work), and other minor quirks. It's the second time it happens and I'm pretty upset about it. I'm now attempting a full wipe of my phone once again in the hopes this won't affect me ever again.

Also, does anyone have any idea why entering recovery now takes around 5+ minutes? Is it normal? If not, any idea how to fix it?

Edit: Just finished full wipe+reflash, TWRP is consistently much faster to boot, taking the usual ~5 seconds to boot up. Perhaps it was some leftovers from the CM->LOS procedure that gave me problems. I just hope from now on my LOS experience will be smoother ^^'
[Moto G 4G Android Development] mrLoma:
Tbh twrp takes about a minute for me to startup.

I never had problems with reboots or file corruption. I hope everything is stable for you from now on.
[Moto G 4G Android Development] FabTheZen:
Yes [MENTION=7785396]mrLoma[/MENTION], thanks for your interest. It was a radical solution but it worked. For anyone having similar problems now or in tbe future, I suggest a FULL wipe from TWRP and a reflash of ROM+GApps. Again probably the migration tool was less than perfect or I simply misused it. Wi-Fi has been stable these two days and no other problem has come back yet ^^
[Moto G 4G Android Development] _that:
If you have many files on /data, that's because TWRP scans your /data partition to calculate the backup size, and the "stat" syscall is slow with f2fs.
[Moto G 4G Android Development] Abhimm:
Hey

i have Philz Touch recovery on my moto g Xt1033

i can use this for flashing this ROM or i should switch to TWRP?

Appreciate for the Help!!
[Moto G 4G Android Development] aha360:
1. You're at the wrong forum section - the Motor XT1033 is for the non-LTE version of the Motor G phone.

2. Flashing LineageOS is preferably done via TeamWin Recovery - attempting to flash it via PhilZ or Clockworkmod is done at your own risk.
[Moto G 4G Android Development] IronTechmonkey:
FYI No CM File Manager for now: https://review.lineageos.org/#/c/156347. The commit mentions a workaround: "1) Use the Downloads launcher 2) Settings > Storage (select volume) > Explore", although many of us prefer other file managers. That being said, the CM file manager was nice, especially for testing 3rd party file managers without having to clutter the device with yet another 3rd party file manager just to test the first one.

Anyhow, a clean flash of the March 2 ROM with March 2 Open Gapps and native LOS SU package went smoothly and performance was good until I abandoned to regroup in re file manager testing without CM FM. The misplaced Google TTS settings butting has been fixed.
[Moto G 4G Android Development] _that:
I don't like this development at all. First they removed root (from the official builds), now they removed the root-enabled file manager. All these are features why I'm running a custom ROM in the first place.
[Moto G 4G Android Development] schrickz:
doesn't the CM file manager get replaced with AOSP file manager ?
[Moto G 4G Android Development] IronTechmonkey:
Nor do I, although I dont fully understand what is going on with root and SU. It was my understanding that before the native SU permissions were added, CM was natively rooted but required something else (SuperSu) to manage SU permissions.

Is the ROM without the new SU package any less rooted than it was before CM got native SU within the ROM?

That being said, the new SU method, (even though in a separate package), and fact that apps are finally catching up to it have allowed me to stay with native SU without requiring SuperSU for some apps. I can even understand why they might want to have a completely unrooted version (LOL, spell-check called that "uprooted" with is an apt description)... as long as the separate package is not just a step towards the end of native root and SU management in LOS.

In re File Manager, Although not as critical to the ROM as a whole, the loss of a robust native file manager is having an immediate and ongoing impact on various bits of testing.

---------- Post added at 02:34 PM ---------- Previous post was at 01:54 PM ----------

Described at a link 2 posts above your post.
[Moto G 4G Android Development] _that:
As far as I understand, the ROM without any SU or SuperSU add-on is not rooted at all so that people can use apps that are deliberately incompatible with a rooted device. I've never used older CM versions.

Currently it doesn't look like the end of native root.

Until they eventually notice that their su package is unmaintained like their file manager and they kill it...
[Moto G 4G Android Development] IronTechmonkey:
It may have been more of a process or workflow distinction. For the old Moto Atrix HD with CM11/KK4.4.x, I remember rooting the device with some ADB utility (which apparently did give the device root status) and then later installing SuperSU. I did not even realize you could use SuperSU for full root and SU management by flashing it (or maybe that was a year later). Also, more recenlty while SuperSU was adjusting to systemeless there were sometimes problems installing it via play-store route so flashing became the way to go. By the time I got to Moto Otus and Peregrine on CM12.1/L5.1.1 there was no independent way to root so I flashed SuperSU on those.

Speaking of old ROMS and the demise of CM File Manager, it was adding insult to injury to see CM FM shortcuts (some of which I've that I've maintained since early CM12.1) look like this (icon labels deleted for privacy).
[Moto G 4G Android Development] jdegreef:
I've clean flashed 20170302 nightly and I still have this problem.

BTW, I don't really understand the previous posts about SU. SU is integrated again in the ROM , no need to flash the addon anymore.

And concerning the file manager, Total Commander rulez :cool:
[Moto G 4G Android Development] IronTechmonkey:
:confused: You partially answered your own question in one of your posts in a SuperSU thread: "You don't have ADB & Apps in Developers Option > Root because you didn't flash the su add-on that comes with LineageOS" from here: https://xdaforums.com/showpost.php?p=71090092&postcount=9189. which conversely implies that you must have the SU package installed on your device.

Are those screenshots from clean flash without SU package and without SuperSU?

Where is is stated that there is no need to flash the SU add-on anymore? If this is true then I'm wondering when and how was SU put back into the ROM after it was broken out into the additional installer, and why SU installer and uninstaller are still available. Is there any commit that describes this?
[Moto G 4G Android Development] mon0tron:
SIM unlock not working

Just installed this ROM on a phone I inherited from a family member - runs super smooth, I love it! However, SIM unlocking doesn't work. I insert the SIM from my new carrier, enter the code provided by the old carrier to unlock the device, and the phone just gets stuck on the "Requesting SIM service provider unlock" screen, requiring a reboot to get out of it. Could this be a bug with the ROM (i.e. should I flash back to stock to unlock the phone, then reinstall Lineage), or something else? Thanks.
[Moto G 4G Android Development] aha360:
Go back to STOCK ROM to do that - there's a reason as to why I never do things like this on custom ROMs and that is one of them.
[Moto G 4G Android Development] jdegreef:
AFAIK the sim card code is specific to the sim card. If you've changed carrier you should have received a new sim code with your new sim card.
[Moto G 4G Android Development] IronTechmonkey:
I don't have experience locking/unlocking SIMs (which I assume is different from unlocking the bootloader in preparation for flashing) but your advise sounds reasonable. That being said, I would want to know if this was done in a clean flash before troubleshooting further.
[Moto G 4G Android Development] jdegreef:
The sim card unlock process has little to do with what rom you use.

If I understand you well, I have the feeling you are not entering the right sim code for your new sim card.
[Moto G 4G Android Development] IronTechmonkey:
If this is not just a matter of getting the correct SIM code from your provider, and you find yourself re-flashing...Then returning to stock before re-flash as previously suggested might help. In the past a stop at stock has been known to help with GPS and radio issues during a device's 1st jump to CM/LOS ROMS. Also the return to stock forces a clean flash. IMO in many cases it is actually the later (clean flash) that fixes the issue so...

Even if you don't go back to stock, at next flash make that you are doing a clean flash.

Clean flash (with 1 or 2 extra steps):

- No prior fiddling with device partitions, particularly radios.

- No mods or hacks of any kind.

- Have SIM in phone during flash. I've successfully flashed Peregrine and other ROMs with and without SIM but for this one doing it with the SIM is best.

- Wipe dalvik/system caches.

- Full wipe. Aka, Factory reset.

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

- Wipe dalvik/system caches.

- Reboot into OS.

- Immediately test SIM before making any settings changes or installing any apps.

Don't take it personally that I'm beating the clean flash drum in this response. This week in Osprey thread several people chased a problem for someone who claim to clean flash but had installed custom kernel and still claimed clean flash.

---------- Post added at 01:14 PM ---------- Previous post was at 12:38 PM ----------

That is what I was assuming. Thanks for confirming.

I'm not the one who reported this problem nor have I ever experienced this problem. As I said in my post (restated here with annotation):

"your advise sounds reasonable" (in re SIM unlock code)

and

"I would want to know if this was done in a clean flash before troubleshooting further. " (Just in case this is not related to using wrong SIM code)"
[Moto G 4G Android Development] MisterDM:
On my peregrine (stock firmware Android 5) I have the problem of the internal memory being full all the time, even though I don't have that many apps installed. I'm thinking of installing this ROM. I don't have much experience with this and have some (newbie) questions:

- does adoptable storage work properly, so I no longer have the problem of running out of storage space?

- I see there are nightly builds released on a regular basis. How should I interpret that, are there a lot of bugs or is it very stable? Why the need for so many changes/fixes all the time? And is the latest nightly the right build to pick, or is it better to wait a little bit?

- my feeling is that it would be best to choose the official Lineage rom for stability. Do you agree?
[Moto G 4G Android Development] mrLoma:
Lineage os is still "young" and still in development.

For me it's stable enough as a daily driver.

-Adoptable storage works, but not for all apps. It still needs to be enabled by the app developer.

-this weeks build feels stable to me, last few weeks we had some WiFi lockups and BT stutter, nothing bad enough to go back to stock though.

Since new features are added, bugs can be made, that is development. So constant fixes are a part of this. But you are free to keep a stable build installed for as long as you want.

It's smoother than the stock os and leaves more free space. Plus you can choose to not install the crappy fb apps.

Since you have to install the Google apps yourself you have the choice to not install apps you don't use.(opengapps)

The nighties are actually weeklies . Every week a new build is made.

You can see the build changes here

https://www.cmxlog.com/14.1/peregrine/
[Moto G 4G Android Development] jdegreef:
Sorry, I think I didn't pay enough attention when replying :o

---------- Post added at 11:03 ---------- Previous post was at 10:46 ----------

I remember that post and it was the case with previous nighly.

I didn't flash the su addon this time because I forgot and I was surprised to see that it was rooted.

I didn't find any commit or info concerning the fact su was included in the rom.

I made a factory reset but didn't wipe system manually. Is it possible that su survived the flashing process ?

I assume system is overwritten when flashing, no ?

The screenshots have been made right after flashing the rom and Gapps micro.

Edit : I've just found this http://www.cyanogenmods.org/forums/topic/how-to-root-lineage-os-13-14-1-marshmallow-nougat-rom/

Is it possible they just build the nightly with this flag enabled ? That would explain there's no commit about it.