yashsingh1/xdaforums huggingface dataset:
[Moto G 4G Android Development] IronTechmonkey:
BT Keyboard PIN timeout is too short.

Any additional tests with BT keyboards that require PIN entry would help resolve this issue:

Not enough time to enter PIN for BT keyboard. I've reproduced this on 3 LOS Android devices including Peregrine in all builds in the last 4 weeks but maintainer at Jira does not have BT keyboard to test with so if anyone else does:

- Unpair keyboard

- Initiate pairing from Android

- When the PIN prompt appears on Android display don’t enter pin but rather wait.

- If the PIN prompt disappears in less than 20 seconds or so, maybe even as fast as 5-10 seconds, there is the bug (the time-out should be 35 seconds).

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

[EDIT] After a few slow weeks for commits, a new batch containing several commits for BT related things was released today to be included in next build. Although none of those commits seem obviously related to the BT keyboard PIN timeout I'm waiting until next week's build to test again. https://www.cmxlog.com/14.1/peregrine
[Moto G 4G Android Development] sdembiske:
Great job. Thank you all for the work put into this to bring it to the Moto G LTE - runs very smoothly, no problems - very impressive. It's given new life to the old phone with up-to-date security. Love the Lineage Updater.
[Moto G 4G Android Development] IronTechmonkey:
Nice to see an apology about this year's LOS April Fools joke, particularly regarding the fact that the joke included a persistent notification which confused people, and that LOS specifically apologized to the maintainers who were not involved in that decision but had to hear complaints about it in forums such as XDA and elsewhere.

https://lineageos.org/An-April-Apology/

IMHO, no such jokes have any place in development or any product testing (whether community or industry based) for the same reasons cited in the apology - the undermining of trust, and this one was worse than usual. Have a joke in a marketing or administrative department but don't prank the testers.

(P.S Please pardon my quasi spamming this note across a few threads for devices on which I test LOS)

[EDIT] Peregrine (and other devices which receive build updates on the same day) has received an build update today, off schedule. Since the dates on the build roster have not changed I would guess that is because the last build for these devices (April 7) still contained the April Fools joke (removed on April 8), and that this was done to get all devices past that without having to wait another full week after April 8th.
[Moto G 4G Android Development] sevenrock:
Missing security patches for the kernel

Hi,

having a look at https://cve.lineageos.org/android_kernel_motorola_msm8226 I noticed

that our kernel did not receive newer security updates anymore.

Today I added a cm-14.1 branch to my personal kernel repo

https://github.com/sevenrock/android_kernel_motorola_msm8226

Contrary to the github note that this repo as a whole was forked from

motog2014devteam/android_kernel_motorola_msm8226 this does NOT apply to the

cm-14.1 branch, the github fork was done for the lineage-15.1 branch only.

The cm-14.1 branch is based on the official LineageOS kernel source:

[remote "upstream_lineageos"]
url = https://github.com/LineageOS/android_kernel_motorola_msm8226.git
fetch = +refs/heads/*:refs/remotes/upstream_lineageos/*

$ LC_ALL=C git status
On branch cm-14.1
Your branch is ahead of 'upstream_lineageos/cm-14.1' by 45 commits.

These 45 commits were mostly backported from

https://review.lineageos.org/#/q/project:LineageOS/android_kernel_samsung_manta

which also contains linux kernel version 3.4.113, just like ours.

Here is the list of CVE's fixed in my repo:

This effort should be considered as a starting point to commit all missing

security-related patches to our kernel. I committed all patches from the

Samsung manta repo which could either be applied without any changes

or with a miminal rebase effort. I am sure that I did not catch all missing

security patches.

Since I have no interest in being an official maintainer of the kernel repo

(I have no time to provide constant support) my intention is to bring this

patch series into the public to be picked up by someone interested with

write access to the official LineageOS repo and the CVE tracker ;)

A few minutes ago I flashed a self-compiled ROM and until now I did not

notice any problems, WiFi/Audio/USB still work.

EDIT 18/04/15:

Pushed another six patches from the manta kernel, including a fix for

CVE-2017-13080.
[Moto G 4G Android Development] IronTechmonkey:
Goodness gracious, this is the biggest single batch of kernel specific commits I've seen: https://www.cmxlog.com/14.1/peregrine

Thanks for putting that stuff out there (and of course thanks to the ever watching Gabriele at LOS and Jira). I'm flashing the April 21 build, not sure if there would be any outward (user noticeable) changes in behaviour but will look out anything different.
[Moto G 4G Android Development] sevenrock:
I rebased my repo today, Gabriele did not commit all the patches I found.

You can check this app for a hint about your current patch status:

https://play.google.com/store/apps/details?id=de.srlabs.snoopsnitch

EDIT 18/04/22: Rebased again.
[Moto G 4G Android Development] schrickz:
settings > buttons
[Moto G 4G Android Development] Nexive:
You mean "Show arrow keys while typing"?

Because when I switch the toggle, the arrows dissappears but after a reboot, the arrows comes back

Edit: Now it works, updated to 23/10 and I enabled the toggle

Sent from my MeMO Pad 7
[Moto G 4G Android Development] ravenmag:
Great job, man... :)

I've got a question. Is it possible to add Private Mode Service as in Samsungs' fw? Or maybe somebody knows how to install Private Mode Service from Samsung to Moto G?

Wysłane z mojego XT1039 przy użyciu Tapatalka
[Moto G 4G Android Development] Lurker-Observer:
I'm aware that these bugs have been noticed, but anyway want to report them.

- Lockscreen: If you swipe down to show the notification shade the clock will shrink a little.

- Lockscreen: Sometimes it is kinda hard to swipe up, the clock will get back to its place without showing the pattern/PIN thing, same with the notification shade, when I swipe down it's hard to stay there.

- Lockscreen: When I long press volume keys to seek music tracks the ROM thinks that I'm raising or lowering the volume then it seeks the track. Example: I'm listening to music then I long press the Up volume, the volume rises a little then seeks the track, same with the Down Volume Key. (obviously I'm doing this with the screen off)

- Overview: If you have more than 2 Apps then you tap "Clear All" and immediately press the Power Button once the phone will not lock itself.

- Encryption: After I turn on the phone, put my encryption pattern, the phone will automatically unlocks itself after that, is this normal? I remember that after I unencrypt the phone it always ask me for the pattern again.

- Battery icon - notification shade: the battery icon is smaller that the other icons, the numbers are see-through, when you are using a white background or using an app that is white you can't see the number on the battery icon. (I'm not talking about the status bar)

- Round battery icon - status bar: the icon is too far away from the other ones and it is not the same size, it looks weird.

- Alarm clock: I'm not sure if this is fixed yet, but when you have an alarm (example: 06:30) then you restart your phone after the alarm (example at noon) the alarm will sound without a reason.

- This feature... I know that this ROM is continuously improving, but there is a feature that I love using and it is not implemented yet: Control Ringtone Volume "Volume keys control media volume" even if I turn it on it doesn't work.

- This happen yesterday I don't know if it was Viper4Android fault: I was using PowerAmp and setting up V4A, after some time I lock the phone, then wake it up, the visualization thing was stuck, when I tried to unlock the phone using my pattern it was just freeze up, I restart then everything was alright (I don't have a logcat, don't know how to make it)

... and that's all!

I was so retarded, actually you can install the ROM, flash yours zips, GApps whatever then wipe to Factory Reset using TWRP without doing it the way I said then encrypt.

Thank you, you're doing God's work :P

----

BTW, I know that the ETA questions are stupid and I don't wanna sound like I'm making one, but, what's going to happen with Android 7.1 on our devices? its source is going to merge with CM14?

(Sorry about typos and that stuff)
[Moto G 4G Android Development] Alessandrotischer:
With latest build, long pressing home button opens recent apps. I can't find out how to get Google now (or Google assistant) working...
[Moto G 4G Android Development] M1chiel:
Thanks for this rom! I got two errors in TWRP while installing ('E:unknown command [log]'; which were apparently not important) and the phone refused Open Gapps Mini (FCs at startup), but the Micro version went well. Everything seems to run smoothly except the flashlight (as indicated on the OP) and the CM File manager (it cannot access my SD card, while Mixplorer can).
[Moto G 4G Android Development] ravenmag:
What is that launcher and how to get this G on the upper left corner?

Sent from a fridge. Moto G is broken.
[Moto G 4G Android Development] schrickz:
that's pixel launcher.

check here for full pixel experience

http://xdaforums.com/android/apps-games/google-pixel-experience-launcher-dialer-t3478907/page10
[Moto G 4G Android Development] Alessandrotischer:
Does anybody know how to solve this?
[Moto G 4G Android Development] Lurker-Observer:
Android 7.1 is awesome, I don't know if it's part of the new features, but screen responsiveness and overall stability is terrific.

And, there's a little thing when you press down or up volume button then press the arrow to show the other volume controls, there's no "Notifications" title, I don't know if that's a bug or not.

Keep the good work (btw I can't install Pixel Launcher with latest Open Gapps)
[Moto G 4G Android Development] sebaalbo98:
Today's version of cm 14.1 by [MENTION=5075128]LuK1337[/MENTION] https://www.androidfilehost.com/?fid=457095661767105732
[Moto G 4G Android Development] schrickz:
Running 14.1 now, smooth and fast
[Moto G 4G Android Development] tonibm19:
Cm14.1

[MENTION=3166483]schrickz[/MENTION]

Is it stable?

Does it break something from cm14? Im using cm14 as a daily diver and I'd like to know if cm14.1 can do that too.

Dirty flash or clean install?
[Moto G 4G Android Development] schrickz:
I did a clean install, everything is working, video recording etc.

The bugs I found so far is long press on the home button shows recent apps and cm file manager still can't access sdcard.
[Moto G 4G Android Development] Alessandrotischer:
Same here... Does the torch shortcut work for you?
[Moto G 4G Android Development] M1chiel:
It does for me after soft rebooting once.
[Moto G 4G Android Development] schrickz:
I'm missing the music app.
[Moto G 4G Android Development] tonibm19:
Cyanogenmod 14.1 working fine here.

Also using pixel launcher.

Great work devs!
[Moto G 4G Android Development] taconi dantas:
CM 14.1 is excellent, developers are to be congratulated
[Moto G 4G Android Development] kamesh_kraken:
Same here (recent apps bug). But I'm on falcon.
[Moto G 4G Android Development] IronTechmonkey:
FYI: Some new commits which seem to be about a network indicator in status bar:

https://review.lineageos.org/#/c/LineageOS/android_frameworks_base/+/215656/

https://review.lineageos.org/#/c/LineageOS/android_frameworks_base/+/215657/

https://review.lineageos.org/#/c/LineageOS/android_packages_apps_CMParts/+/215655/

I'm running the May 26 build which AFAIK should contain everything you put through. I can't say that I notice a difference in performance but I'm glad to have them, especially the security related ones, and Peregrine is still the steadiest of my Moto birds (Peregrine, Osprey Athene). Thanks for spending some time on the old bird.

[EDIT] Athene gets its build earlier in the week so here's a preview of the network indicator.

Settings Status Bar > Network Traffic monitor >

Should be in June 02 Peregrine build.
[Moto G 4G Android Development] Pupet_Master:
This phone is still my secondary phone... and soon will be my Sister Phone (as i'm getting another new one).

I'm at AEX but very unhappy with that ROM, is Lineage N still the best ROM for the phone?
[Moto G 4G Android Development] Libor1:
I can't compare, never had other than LOS 14.1 on my Peregrine, but it's running pretty good and stable, so give it a try .
[Moto G 4G Android Development] Pupet_Master:
Thanks, i will
[Moto G 4G Android Development] Tsuragi:
i buy the moto g xt1040 recently and it turns off, sometimes without warning it only turns off and when turning it on it maintains the battery level, what could it be? just buy it update to 5.1 and install lineage os 14.1. Is the hardware defective? or is it the software? or the battery?
[Moto G 4G Android Development] IronTechmonkey:
Shutting down completely and staying powered off (as opposed to spontaneously rebooting) is not a good sign and could be an indication of a hardware issue with battery, charger or USB port on device.

As to the LOS14.1firmware, this is almost certainly not a bug. I have 2 Peregrine xt1045 devices running LOS 14.1, one of which is a daily device and the other of which is a dedicated security camera; Neither device has ever experienced a spontaneous reboot or unplanned shutdown. Additionally Peregrine has been well tended by developers in LOS 14.1. In spite of having less RAM and slower processor than newer Moto G4s that I've used (Osprey/xt1540 and Athene/xt1625) Peregrine has been more reliable on the same firmware. Also, AFAIK there have been no similar report of such problems specific to LOS 14.1 on Peregrine.

Since this thread topic is LOS 14.1 you should do some separate research about the issue. I've just done a quick bit of searching and found that some people have had this issue but not specific to LOS 14.1 I suspect that many of the people who have reported this have been sold an older device (even if purchased "new" it will have been sitting around for a year or 2 at least) which perhaps have bad batteries or may have issues with the charger.
[Moto G 4G Android Development] Tsuragi:
That gives me confidence, it must be the battery's fault, thank you very much
[Moto G 4G Android Development] sevenrock:
Added some new commits:

https://github.com/sevenrock/android_kernel_motorola_msm8226/commits/cm-14.1

Patches include fixes for CVE-2017-15846, CVE-2017-15857 & CVE-2017-17806
[Moto G 4G Android Development] demoncamber:
Hey dudes, anyone else getting this type of error? How should I go about fixing this?

"Detected problems with app native libraries

libffmpeg.so text relocations

libpack.so invalid DT_needed entry "./obj/local/armeabi/libffmpeg.so

libpack.so text relocations"
[Moto G 4G Android Development] sdembiske:
Surprised that the July 21 update does not include the July 5th latest Google security patch. Is it not applicable or simply has not been incorporated as yet?

Appreciate the work and love the rom.

Thanks,

S.
[Moto G 4G Android Development] sevenrock:
The patch series is still under review: https://review.lineageos.org/#/q/topic:n_asb_07-2018

Afaics it works fine on my private build.

---------- Post added at 11:49 PM ---------- Previous post was at 11:46 PM ----------

Added some new commits for android_kernel_motorola_msm8226:

https://github.com/sevenrock/android_kernel_motorola_msm8226/commits/cm-14.1

Patches include fixes for CVE-2018-5896, CVE-2018-5844, CVE-2018-3584, CVE-2017-14879 & CVE-2018-5344

A run-time test in the last couple of hours showed no obvious bugs.
[Moto G 4G Android Development] BeachBreeze:
Hi, I'm on ResurrectionRemix 5.8.0 (Android 7.1.1) with TWRP 3.2.3.0. I want to try this Lineage and I tried other TWRP version, but when I flashing it reminds me Error 7. Anyone with the same problem? Thanks
[Moto G 4G Android Development] _that:
Your question is useless. Try to install again, then without rebooting, run "adb pull /tmp/recovery.log", then post the log.
[Moto G 4G Android Development] _that:
Have you read the above message? (It also appears on the screen, not only in the log.) What exactly is unclear?
[Moto G 4G Android Development] BeachBreeze:
Ops, you're right! I made confusion between wipe data and wipe cache, so I thought I did wipe data instead I had done only wipe cache. I'm not very experienced :(

Thanks for help, I'll try again the next few days :good:
[Moto G 4G Android Development] key-ancel:
I have discovered a "spin screen" bug, when I am watching a video in horizontal, then I return it to vertical and from blocking the rotation, but I have to press it twice. It is the univco bug that I have found, otherwise the rom is perfect <3
[Moto G 4G Android Development] insidethishouse:
Beforehand, forgive me if this post breaks any rule. I just want to ask if we will ever get LOS 15.1 for this device? Thank you.
[Moto G 4G Android Development] IronTechmonkey:
As you seemed to have suspected we typically don't ask those things (or for ETAs). It comes down to which developer has the device to work with and the inclination and time and to maintain it for the new LOS version. Sometimes that's a smooth transition with same dev and other times it is not or never occurs.

One good thing about Peregrine is that it is very well maintained in LOS14.1 (better than many more popular devices). If we are lucky that will flow into LOS 15.x but even if 15.x is delayed or never happens for Peregrine, LOS 14.1 is a good fall-back.
[Moto G 4G Android Development] BeachBreeze:
I tried the Rom and works fine for me! Thanks :good:
[Moto G 4G Android Development] IronTechmonkey:
FYI regarding a BT keyboard issue which was reported to LOS Jira from Peregrine but affects many devices.

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

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

My most recent note into the ticket:

Some time in the past several weeks this may have been fixed (whether intentionally so or incidental to something else).

While flashing the 9/1 build on Peregrine and Osprey and the 8/29 build on Athene, none of the 3 devices had the same issue. That being said, I'd like to wait until next flash of at least one of the devices before declaring fixed.

[EDIT] From jira ticket:

"Issue did not occur in clean flash of Sept 26 2018 Athene build. As in all of the tests since first noticed fixed, the time-out for PIN entry seems to be as long as expected (30-35 seconds) rather than only 3 seconds as it had been. Whatever the cause, this has been fixed for about 2 months without re-regressing so there's no need to keep the ticket opened. Thanks."
[Moto G 4G Android Development] macmobile:
What about mobile payment with this Rom? Possible? My app claims it wouldn't be secure.
[Moto G 4G Android Development] Brotherofsun:
Hello

Why there is no "recent changes" to lineage-14.1-20181110-nightly-peregrine-signed.zip ? ;)
[Moto G 4G Android Development] IronTechmonkey:
In short - there's just not much going on. In more detail, this has to do with the general and device-specific progression of development.

In general: The LOS 14.1 ROM is fairly mature so there are not as many updates as in the past. For instance, except for one big batch of non-specific commits last week we've not had updates for many weeks. This is the case for many devices, including my Peregrine, Osprey and Athene.

Additionally, device-specific development may move on to newer versions as well. In the case of Peregrine, even though it is an older device we are fortunate that it still gets some device specific development attention, and there have been nice user contributions (which you can read about in the thread).
[Moto G 4G Android Development] Brotherofsun:
That means there are not any changes in 14.1-20181110 build? ;)
[Moto G 4G Android Development] mauriciognr:
Hello boys, here's a video of antutu benchmark running on a XT1040 with this rom

Video: https://www.youtube.com/watch?v=mDa3wetLRLQ

[YOUTUBE]mDa3wetLRLQ[/YOUTUBE]
[Moto G 4G Android Development] pigeons9:
Unless another developer picks it up looks like official support has ended with the Feb 7 2019 release (https://wiki.lineageos.org/devices/peregrine)

Any ideas & suggestions? I don't demand too much. Relying on F-Droid made my dinky jellybean phone usable a couple extra years. It was stagefright vulnerable but I hardly consumed or received enough videos on my phone to have it be an issue.
[Moto G 4G Android Development] IronTechmonkey:
I'm hesitant to share links directly to other ROMs without knowing for sure that our maintainer will not be taking Peregrine to LOS 15 or LOS 16 but you can find some attempts at LOS 15 and 16 as well as other ROMs one level up the forum tree in " Moto G 4G Android Development" https://xdaforums.com/moto-g/4g-development. Considering what I see there so far I'd rather continue using LSO 14.1 and find a way to update the security patches if possible.
[Moto G 4G Android Development] sdembiske:
In anticipation of this eventuality, a couple of months ago, I installed Linux Mint in a dual-boot situation and set-up everything to build Android. The first build of this rom took a fairly long time but now I can do a new build in just over 7 hours (with 4GB ram on a legacy Intel Pentium D 930 CPU desktop computer - if you have a newer CPU and more installed ram, you can run a build very very quickly). I ran the latest build day-before-yesterday, checked the security patch date and found it was already updated to March 5, so clean flashed it yesterday (in TWRP, wipe Cache, Dalvik cache, system and format data (make sure you back up your data etc., beforehand as you will lose all your data when you format it) and restored all the user apps, etc. No problem at all.

[MENTION=5119654]IronTechmonkey[/MENTION]

To learn to update the security patch before starting the latest build, you can refer to the following by thealaskalinuxuser: How to manually update your custom rom source code with security updates - it's not that difficult a process but you do have to build it.

The point is, if you really want to keep this rom up-to-date for your personal use, it's not that difficult if you have enough disk space (recommend 250GB) and are willing to learn the process.

Note

: Setting up the dual-boot process is well worth the effort - with Linux Mint - Xfce, it is hugely faster than doing it in VirtualBox.
[Moto G 4G Android Development] macmobile:
Hi guys!

I need your help. The Moto G of a friend of mine started to bootloop today (stuck at the lineage os logo). It's not possible to turn the device off again.

I managed to reinstall TWRP via Fastboot in order to copy important data (documents, pictures etc). Is there a way to get this rom running again without losing any data? Unfortunately no backups were made and I don't know how to get her SMS saved...?

Many thanks in advance
[Moto G 4G Android Development] J_M_V_S:
You can try just dirty flashing the ROM again. No user data should be touched. Make a complete backup first, just in case
[Moto G 4G Android Development] macmobile:
Thank you for helping me out! After flashing this rom twice it seems to work again. No bootloop anymore. Btw: why isn't the rom any longer available for download on the lineage OS website? How do I get the updates they've delivered until February?