yashsingh1/xdaforums huggingface dataset:
[Moto G 4G Android Development] ncc1701a:
Thanks for testing TWRP.

Generally, it would be nice to wipe Dalvik/Cache after restoring a backup (not just after flashing LOS/GApps, if the backup will be restored), because the most users don't wipe Dalvik/Cache before creating backups. Another way, it is possible, that after restoring a backup, system will has an obsolete ART cache: theoretically, it will handle this with updating ART cache for new system apps, but, by practice...

The simplest way to check, that the backup has old ART cache is:

- change the file extension for data.f2fs.win (or for all data.f2fs.win00x files) to .zip extension for using unzip programm;

- if the archive has no empty /dalvik-cache folder (or /data/dalvik-cache folder, if there are multiplies data.f2fs.win00x files), the old ART cache is here.

And do not forget about some patcher programs, which has abilities to patch app on ART cache level: this programs may leave some garbage. Generally, after system update, it is recommended to wipe Dalvik/Cache and then repatch needed apps again.
[Moto G 4G Android Development] IronTechmonkey:
Running with the topical OT a bit further:

This aspect of flashing, particularly the dalvik/system cache wipes is undervalued (IMO). Although it is a bit time consuming, I wipe the caches before and after every backup or restore or ROM or mod flash. Over the long run I think that has been time well spent; Resulting in greater stability and more accurate actual ROM bug reporting.
[Moto G 4G Android Development] 239:
Which patcher did you refer to and how to repatch?

That's exactly what I always did but apparently it causes the card ejection for me and I don't get why. How can cache clearing be even disadvantageous?

I will try to clear caches on next update again and see if it is reproducible. Not sure if this is a TWRP/LOS bug or just a special case on my device.
[Moto G 4G Android Development] ncc1701a:
Original message has been edited. Reason: offtop
[Moto G 4G Android Development] IronTechmonkey:
[EDIT2]Tx.
[Moto G 4G Android Development] BitingChaos:
I don't know where to report issues, and searching dozens of terms hasn't gotten me any closer to finding a solution.

The carrier string has been bugged in builds for weeks/months.

On my device, toggling airplane mode will change the carrier name from "FreedomPop" to "No Service| FreedomPop", to "No Service". It's the middle No Service| FreedomPop that isn't right. (I'm using the FreedomPop "Global SIM")

No Service is ran together with a pipe - "No Service|". It seems like a string issue. I can't even find the source file the strings for carrier names are in, as searching for "No Service|" gives me tens of thousands of unrelated pages, as the pipe is ignored in searches. I don't know if it's an issue for just FreedomPop, or all builds for Peregrine.
[Moto G 4G Android Development] IronTechmonkey:
I've been flashing LOS 14.1 on three devices including this week's build on Peregrine XT1045, and have never seen the provider name in the status bar, or anywhere in the settings except for the old "phone info" panel. On the same device in stock (naturally updated to L5.1) the provider name was present in the status bar (T-Mobile).

Where are you seeing the provider name in LOS? Is it in the phoneinfo screen?

In any event, if you think you've got a real LOS 14.1 bug in a clean flash with no 3rd party mods, you could try creating a Jira ticket.
[Moto G 4G Android Development] gasston:
@ IronTechmonkey: The network provider name is present on lockscreen and on quick setting since very long time

[IMG="settings"]http://world.compagnie.free.fr/images%20forum/informatique/telephone/MotoG4G%20XT1039/Screenshot_20171225-184627.png[/IMG][IMG="lockscreen"]http://world.compagnie.free.fr/images%20forum/informatique/telephone/MotoG4G%20XT1039/Screenshot_20171225-184503.png[/IMG]
[Moto G 4G Android Development] IronTechmonkey:
Ahh, thanks for clarifying. Indeed the provider is there on the lock-screen of my device as well.

[MENTION=3975238]BitingChaos[/MENTION], it could be an issue specific to FreedomPop as you mentioned, but issues involving the interaction between telecom provider and ROM could go either way as to cause. It really might be worth creating a Jira ticket for this to see how it goes, but first, try searching LOS Jira for tickets containing FreedomPop. There are several tickets which mention FreedomPop, where people have been unable to invoke the hidden "testing" > "phone info" screen with code [*#*#4636#*#*], and had other problems.

Also, while reading the tickets I saw a statement saying that FredomPop uses T-Mobie infrastructure, which is amusing since IIRC T-Mobile uses AT&T infrastructure, but this is still consistent with the different ways that providers may manage service across the same infrastructure.

FWW, my provider is T-Mobile US prepaid and T-Mobile does show in lock screen (thanks again [MENTION=333300]gasston[/MENTION]).
[Moto G 4G Android Development] Piksou:
Hi I am having a look at this for my Father who still owns a Peregrine.

From what i see in the topic, most things seem very OK, are there any serious bugs still present ?

Also, I saw a lot of messages about issues with adoptable storage, but almost none in 2017. Is anybody using adoptable storage with this LineageOS without issues ?

Thanks a lot :)
[Moto G 4G Android Development] 239:
Yes, since early 2017. It's pretty much mandatory when using apps like WhatsApp that won't you let set storage to SD card.
[Moto G 4G Android Development] ahmadsamhann:
been using this ROM for 2 days now. everything works, but sometimes the rotation is buggy. I have to retoggle the rotation setting so it will remember that I've enabled screen rotation. not really a big issue, but kinda annoying. other than that, great ROM! better than lost's Stock 5.1 Peregrine (my previous ROM)
[Moto G 4G Android Development] macmobile:
This is a great Rom![emoji108]Except for some rare reboots, no problems at all so far.
[Moto G 4G Android Development] pplu00:
Hi,

I'm using in my xt1039 CM13 by Kajant (million thx again for him, again) along two years and working perfectly for me until two days ago.

Trying to update some apps in Google Play, it began to reboot continiously, and I could only repair it loading a backup with TWRP.

I tried a backup from december, and another from august too, taking care don't update automatically Google Play nor G.Framework nor G.Services, but it comes down to the same result, and it does not matter which application I try to update.

My last attempt was a factory default reset, but after a lot of reboots, it reaches an unstable state, not usable, so I think that in a recent update of some Google component, CM13 was found some incompatiblity.

Well, CM13 development ended several months ago so...

please, can you confirm this ROM still works with Google Play updates without problems?

Thanks in advance.
[Moto G 4G Android Development] Rob...:
It works, I can confirm. Importantly use the latest GAPPS.
[Moto G 4G Android Development] IronTechmonkey:
Those problems should like issues with dirty flashing, or 3rd party factors, or problems with the process.

Peregrine LOS is running fine on 2 Peregrine devices here: Device 1 running August 17 2017 build, having received all available Google services updates and app updates since then, and Device 2 running Dec 22 2017 build.

---------- Post added at 09:33 PM ---------- Previous post was at 09:32 PM ----------

Yes, and also clean flash.
[Moto G 4G Android Development] IronTechmonkey:
This Week's Build

FYI: I'm not sure what time the builds usually are released but it seems as if a day or 2 of builds from from klimtwifi to r7sf (including Peregrine) are completed but in some stalled state in the build queue and not available for download even though later builds (eg Surnia) are available. We (and a bunch of other devices) might be skipped this week.
[Moto G 4G Android Development] mrLoma:
Usually the new build is on Fridays afternoon.

You can check the build servers on

https://jenkins.lineageos.org

But to find out why the build failed, you'll need to track down the peregrine build. There are build logs for each build.

This one is for the current build queue

https://jenkins.lineageos.org/job/android/
[Moto G 4G Android Development] IronTechmonkey:
I said I don't know the weekly release day just as a conversational lead-in but I should have been more clear.

Those web pages are exactly where I saw the details which told us our build would be skipped this week (errors in the queue and some system maintenance). I'm surprised more people don't use those resources. Thanks for sharing the links.

BTW if you poke around you might be able to find an index page which shows folders for each device in a raw HTML index, in which you can tell what was updated recently by folder date (except when old builds are deleted, which also changes the folder date).

OT: BTW, it's great to be back on Peregrine. After Motorola forced obsolescence on my past one with a simslot spacer that damage the contacts I found what must be one of the last new Peregrines available in my area and scooped it up. It's my daily phone and it has demoted Athene (Moto G4) to wifi phablet. Another reason is Peregrines full compliment of actual sensors and native ANT+ compatibility.
[Moto G 4G Android Development] sevenrock:
Imho you can add its Cortex A7 CPU which is not affected by meltdown/spectre :)
[Moto G 4G Android Development] IronTechmonkey:
That makes my cerebral cortex cpu feel good!
[Moto G 4G Android Development] default_user0815:
I hope that I'm not completely wrong with my question in this thread: I installed the latest Lineage 14.1 build (complete reinstall from scratch via TWRP). Everything works fine so far except connecting my sports watch via Bluetooth. This should be done with the Suunto Movescount App. Initial pairing works. I can Exchange data between the watch and my XT1039 and push notifications are transferred to my watch. But after being disconnected once Movescount app cannont reconnect the two devices although Android system settings show the watch being connected to the Smartphone (f.ex. it is recognized under "Smart Lock").

With the condensed stock ROM provided in this forum I didn't have These issues.

What could I do in order to get the connection working under LineageOS? Could anyone point me in the right direction?
[Moto G 4G Android Development] ncc1701a:
Hi.

I found the uncritical bug with Hotspot connection: after reboot, the first attempt to enable Hotspot failed.

The steps for reproducing the bug:

- before rebooting, disable Wi-Fi and Hotspot connections;

- after rebooting, the first attempt to enable Hotspot failed: is seems like RF-module does not enable Wi-Fi module (according the Hotspot icon bright state, it enabled, but another devices can not find this Hotspot);

- disable Hotspot and enable it once again: successful.

Please, somebody test it and confirm.

The JIRA ticked has been opened here.
[Moto G 4G Android Development] IronTechmonkey:
Coincidentally yesterday I was testing tethering for another reason (having to do with the client device) and did not see this behavior in the previous LOS Peregrine build. That being said, there have been many changes since the last build and I was not necessarily following your test process. I'm planning to flash Peregrine in the next day or two and will try to reproduce your test then will add any pertinent notes to the jira ticket. Thank you for taking the time to create the ticket.

[EDIT] [MENTION=5295657]ncc1701a[/MENTION], Nice catch. Reproduced like this:

Reproduced on my Peregrine XT1045 as well, like this:

- Configure hotspot on Peregrine.

- Test with Device #2 as guest to confirm hotspot working, then disconnect Device #2.

- Disable, hotspot, wifi, and mobile data on Peregrine.

- Reboot.

- Wait for boot and media scans to complete.

- Connect to mobile data.

- Start hotspot from QT = indicates on.

- Device #2 Wifi cannot see Peregrine hotspot even though Peregrine hotspot appears in saved networks on Device #2..

- Device #3, which had never been connected to the hotspot cannot see the Peregrine hotspot either.

- On Peregrine, from QT start and stop the hotspot.

- Hotspot appears in Wifi connections of both Osprey and Athene.

Notes added to jira ticket. Thanks again.
[Moto G 4G Android Development] ncc1701a:
Hi, IronTechmonkey. Thanks for confirmation and for participating on JIRA!
[Moto G 4G Android Development] IronTechmonkey:
My pleasure. Thanks for kicking off a report worth chasing. I've retested while logging and while adding pauses of at least 20 seconds at various points in the workflow. More details in Jira, some of which are possible additional factors which our devices might (or might not) have in common; I'm on T-Mobile US prepaid with device set to 3G mode for mobile data.
[Moto G 4G Android Development] default_user0815:
It's me again. :) I still don't have a single clue how to solve my problem.

I took a look into the building.prop file of my stock ROM and compared it to the lineageOS file (latest build). There are differences in the "Bluetooth" section.

In lineage the building.prop files shows

[...]# Bluetooth
qcom.bluetooth.soc=smd
qcom.bt.le_dev_pwr_class=1
ro.qualcomm.bluetooth.opp=true
ro.qualcomm.bluetooth.hfp=true
ro.qualcomm.bluetooth.hsp=true
ro.qualcomm.bluetooth.pbap=true
ro.qualcomm.bluetooth.ftp=true
ro.qualcomm.bluetooth.nap=true
ro.qualcomm.bluetooth.map=true
ro.bluetooth.sap=true
ro.bluetooth.dun=true
ro.bluetooth.hfp.ver=1.6
ro.qualcomm.bt.hci_transport=smd[...]

whereas the building.prop of the stock ROM looks like this:

[...]# system property for Bluetooth hci transport
#
ro.qualcomm.bt.hci_transport=smd

#
# system property for Bluetooth HFP version
#
ro.bluetooth.hfp.ver=1.6

#
# system property for Bluetooth SAP support
# Motorola disabled SAP
#
ro.qualcomm.bluetooth.sap=false

# Bluetooth LE power class
qcom.bt.le_dev_pwr_class=1[...]

Basically, under lineageOS every setting is "true" whereas the Stock ROM shows less "functions" and SAP support is deactivated.

Could it help if I deactivated a couple of the lineage options in order to solve the problem? How high would be the risk of bricking the phone?
[Moto G 4G Android Development] IronTechmonkey:
Possible overlay or permissions (draw over other apps) issue.

At attempt to allow ADB connection error "Because an app is obscuring a permissions request, Settings cannot verify your response.” (and other overlay or "draw over..." permissions issues?)

- With SU installed, root enabled for apps and ADB, USB Debugging enabled; Connect to USB to computer and run "adb devices".

- Adb prompt appears on droid.

- Check always allow from this computer.

- Tap OK

- Error: "Because an app is obscuring a permissions request, Settings cannot verify your response.”

- Attached image:ADBprompt.png and log PeregrineADB2018-01-27-00-22-05.txt.

- There is no app blocking the prompt, and the check-box registered the selection.

- LMT is the only app on the device which has draw over apps permissions so I disabled LMT and then the error did not occur, but the following testing precludes LMT as sole or even primary cause.

- This has only occurred on the last only in the last 2 week's Peregrine builds but not the last 2 week's Osprey or Athene builds (including Osprey flashed at same time).

- Another symptom also occurring only in the last 2 week’s Peregrine builds (and this time not involving LMT ): when the volume drop-down is expanded during phone call it seems to go behind the home-screen, and when this occurs the only way out of it is to tap the home button.

Attached image: Volume.png and log PeregrineVolume2018-01-25-17-29-28.txt.

- Coinciding with both of the aforementioned symptoms are these sub-symptoms.

— Lags and slow response to list and page scrolling everywhere, as if a multiplier or display size value is off; more scrolling required for little movement and with no acceleration.

— Lags in button presses in loggin app and other apps.

— Lags in hardware button combo press for screenshot which invoked bug report button even though the duration did not seem long enough for that.

— These sub issues cease when the primary problem condition(s) are stopped.

Notes: The logging was done while I was using Nova Launcher but it occurs in Trebuchet as well.

[EDIT] Jira ticket. Here: https://jira.lineageos.org/browse/REGRESSION-1648 (and some modifications to the above report).

[EDIT2] FYI based on notes from the Jira ticket (thanks to G): ADB prompt component of this is probably desired behavior surrounding security of ADB access, but then I wonder about why it is not occurring in other devices and previous builds. It would be interesting to know the experiences of anyone who uses LMT Launcher (PIE only) and connects to computer via ADB.

[EDIT3]ADB prompt not an issue, details in ticket.
[Moto G 4G Android Development] ncc1701a:
Hi, @IronTechmonkey.

I've read the answer from REGRESSION-1648 about ADB connection error.

I did not know, that Android (from Lollipop version or newer) has the safety hole, which can be used by "tapjacking" exploits. Useful info.
[Moto G 4G Android Development] Gegene73:
Same problem, waiting for an answer if you have a solution !

And also bluetooth connection is very slow with this watch.
[Moto G 4G Android Development] IronTechmonkey:
Thanks for sharing that. I tested and don't think it applies to this situation, athough it might peripherally inform the issue. If what I've seen is a part of the tapjacking protection then it is a case of the protection accidentally being invoked when not needed rather than failing when needed. Also, I'm inclined to go with G's description in the jira ticket - something to do with display properties of Peregrine (since same thing did not occur on Osprey or Athene).
[Moto G 4G Android Development] IronTechmonkey:
With so many variables, BT issues can be hard to pin down to ROM or 3rd party factors but that does not mean there is nothing in LOS that could be fixed in this regard. If you want to establish that this is an actual bug and try to get it fixed you could search LOS Jira for similar issues and create a bug report from your device. https://jira.lineageos.org/
[Moto G 4G Android Development] default_user0815:
I know it's a long shot especially with the Movescount app being very unreliable. But knowing that the app & pairing does work with my stock ROM still gives me little hope that it could work under lineageOS, too.

I've kind of "hijacked" :) a related bug report and described the problem there: https://jira.lineageos.org/browse/REGRESSION-782
[Moto G 4G Android Development] marexel:
Hi,

I hope I'm right in this thread. I'm running 14.1-20180105-NIGHTLY-peregrine and when I use for example the "ZDF-Mediathek" App to watch a film via Wifi the connection aborts again and again. The problem is that I don't realize it directly (because I am in full screen mode) until I get a message that my mobile data volume is spent.

When I click on the Wifi button my SSID is found after a few seconds, then it reconnects.

When I use the Wifi-Analyzer I can see that others SSIDs disappear as well so I think it is a peregrine-thing.

Anybody who can report the same problems?

Thanks in advance, kr,

marexel
[Moto G 4G Android Development] 239:
Installed the ZDF app and let it stream for a while, connection was stable all the time. I can't remember any disconnects while streaming with YouTube, Netflix or Spotify with both peregrine devices.

It sounds like a network issue to me. Does it happen on all WiFi networks with other routers?
[Moto G 4G Android Development] IronTechmonkey:
Thanks for the heads up. Those changes seem to be reflected in the build roster, which indicates changes for the LOS 14.1 schedule - Peregrine LOS 14.1 is now on day 6 (Saturday). https://github.com/LineageOS/hudson/blob/master/lineage-build-targets.

Also, Jan 23 build seems OK. Not many changes in past few weeks but there is some interesting new stuff regarding sharing wired and USB connections, and Accept Linux GPT partitions on external SD cards (https://review.lineageos.org/#/c/203877/).
[Moto G 4G Android Development] IronTechmonkey:
Regression in Feb 23 Peregrine BT

Unable to pair with BT keyboard. Fails with time-out at PIN entry regardless of keyboard interaction.

https://jira.lineageos.org/browse/REGRESSION-1725

- BT unable to make initial pairing with keyboard*.

- Keyboard is detected but connection fails at the point of entering PIN.

- There is a prompt for PIN but PIN entry on keyboard is not recognized.

- Connection seems to fail based on (shorter than usual) time-out rather than based on actual PIN entry.

- PIN prompt yields same "bad pin" error even when no input is provided at keyboard.

- The timeout in which PIN fails (regardless of correct, incorrect or no keyboard input) is much shorter than normal.

- Osprey running LOS 14.1 Jan 26 pairs OK and does not time out (tested on all 3 of the keyboard's BT connections).

- Athene running LOS 14.1 Jan 29 pairs OK and does not time out (tested on all 3 of the keyboard's BT connections).

- Peregrine running LOS 14.1 Jan 26 pairs OK on all 3 of keyboard’s connections (tested on all 3 of the keyboard's BT connections).

- All 3 Android devices can pair with each other and with Ubuntu 16.04 computer (good connections but no file transfers tested).

- I;ve used this keyboard successfully on every other LOS14.1 build on any device (many dozens of iterations).

More details in Jira ticket: https://jira.lineageos.org/browse/REGRESSION-1725

[EDIT] This might just be a matter of the timer being too short to enter the PIN in time.

More testing where the issue was reproduced a few dozen times, but one time when I was particularly quick to type the PIN, the PIN was acknowledged and the keyboard was connected. I was unable to enter the PIN quickly enough in any other attempt.

A hypothesis that the timeout is just too short is supported by the facts that.

1) Other devices not requiring PIN have no problem

2) Even with no keyboard input the timeout occurs within just a few seconds.

[EDIT]Looks increasingly likely to be related to time-out. confirmed on Osprey:

- The PIN prompt takes 1 or 2 seconds to appear (which seems normal).

- The PIN prompt disappears after 5 seconds if there is no input (which seems very quick).

- I suspect that not all f the 5 seconds are available for active for PIN entry (in reality more like 3 seconds) but this may be normal and negligible give a more reasonable time-out.

- In Jan 26-29 Peregrine, Osprey and Athene the time out is 30 seconds and yields the same error but allow for proper PIN entry.
[Moto G 4G Android Development] marexel:
unfortunately I don't have another router at hand so I can't check that. But since nobody reports the same problems it seems that it is not a problem of the OS.

However, in some weeks I will try Oreo and hope that the connection is stable.

Thanks, kr,

marexel
[Moto G 4G Android Development] IronTechmonkey:
IMO, that is not a safe assumption. There are many settings in the devices and routers which could account for why one firmware on one device might having problems that others don't . This does not mean it can't be a bug but since others are not reporting the same issue then it would be up to you to create a good bug report for it.
[Moto G 4G Android Development] 239:
Just a reminder that you can disable cellular data access for any streaming app to prevent excessive data usage.
[Moto G 4G Android Development] diziet_sma:
Earlier this evening I rebooted my xt1039 (the reason why has clear left my broian due to what happened next), when it restarted it showed me the white first time screen, asking to import from another device or do a fresh start, of course i want neither.n i checked in recovery and my sdcard still mounts and my stuff is there. is there some file i can edit bin recovery or maybe adb that will turn off this first time stuff?

diziet
[Moto G 4G Android Development] Darkshado:
Flashed yesterday's build, the phone doesn't connect to the cellular network anymore; anyone else have this issue? downgraded, didn't resolve, eventually tried fastboot erase modemst1 and 2 and signal now works.