yashsingh1/xdaforums huggingface dataset:
[Moto G 4G Android Development] mrLoma:
just installed this on my xt1039, my first time installing a rom.

I had to install the new "google Camera" , which works fine(better than the camera in the rom which crashed when selecting that power button option, sometimes got stuck when switching to the gallery and didn't work for recording)

I had the same issue with the torch, but the soft reboot works.

I did have a strange issue, after soft rebooting my battery had 13% my automatic battery saving switches on 5% and the battery saving kept going on and off.

I had to disable the 5% auto switch thing and soft reboot. And the battery saving mode was back on even though I disabled the auto battery saving mode.

After an other soft reboot it started to work as intended again. 12% battery - limit on 5% and battery save mode off.

I haven't had any major problems with this rom and it seems smoother than the official 5.1 I had before seems to use less resources AND it has a ton cool new features.

Thanks for all the great work.
[Moto G 4G Android Development] mrLoma:
I just tried to change my user's picture, I can load a picture and select a crop rectangle, but when I press save, it doesn't do anything.

I also can't find the smart lock menu.

Not complaining, just reporting ;)

update: This was an issue with the original google camera's gallery app, with the newer google camera app's gallery I installed, this worked fine.
[Moto G 4G Android Development] satanas17:
Hi,

This is for Peregrine, not for Falcon, so, if u try it, don't blame devs for bricking issues... ;)
[Moto G 4G Android Development] csako:
Hello,

Which gapps should I use? I've tried "arm-7.0-aroma" but google play services crashes every time and I can't add my account :/

build: cm-14.0-20161011-UNOFFICIAL-peregrine.zip
[Moto G 4G Android Development] mrLoma:
I used "open_gapps-arm-7.0-micro-20161008", that worked for me.

I had to download the other google apps I wanted.
[Moto G 4G Android Development] Danielnc43:
Window permissions bug

When some application need permission appears to me this window and stays there. The only solution is close the aplication.

Any idea or solution??

ROM: cm-14.0-20161011-UNOFFICIAL-peregrine

GAPS: open_gapps-arm-7.0-pico-20161012

(Sorry for bad English)

[IMG="Bug"]https://k60.kn3.net/3/9/7/3/A/D/3AE.png[/IMG]
[Moto G 4G Android Development] csako:
Thanks, it worked :)
[Moto G 4G Android Development] Dark98:
Download these gapps, it's a permission error or something downloadmirror.co/Uni/banks_dynamic_gapps-7.x.x-20160915.zip

In recovery format only your system partition and reflash the ROM and gapps
[Moto G 4G Android Development] obrunowalker:
What are the applications that come in this GAPPS package ?
[Moto G 4G Android Development] Clusterix:
I get error 7 when i try to flash. System Version should be right.

I flashed RR 6.0.1 and after that i clean flashed this cm 14 and it worked, thx to the dev, but i wonder why it didn't work with stock 5.1 rooted unlocked.

Nevermind, now anything is fine :)
[Moto G 4G Android Development] sebaalbo98:
SuperSU causes bootloop
[Moto G 4G Android Development] Wyneg:
What version?

I use 2.78 SR1 (systemless) without problems...
[Moto G 4G Android Development] sebaalbo98:
He had installed the version of SuperSU of play store and gave me bootloop
[Moto G 4G Android Development] sevenrock:
Same here, to circumvent the problem I grant the permissions manually via the app info settings.
[Moto G 4G Android Development] Wyneg:
Then, System version, try Beta systemless (flash via recovery) ;)
[Moto G 4G Android Development] pjconoso:
Anyone else getting signal issues? Signal bar shows something but the status reports No service.
[Moto G 4G Android Development] damian3581:
It does not work linksd
[Moto G 4G Android Development] csako:
It's fixed.

Build: "cm-14.0-20161016-UNOFFICIAL-peregrine" and "open_gapps-arm-7.0-micro-20161015"
[Moto G 4G Android Development] mrLoma:
I wondered about this as well, I'd like to know when it's worth trying to update my version again.

The changelog in the OP looks like it's from the main branch of CM14, also has no dates, so it's hard to know what version has what changes.

Just a simple , we update the main cm to that date and fixed these things in our local branch.

For me right now, there is little incentive to update to a newer build as long as most things run smooth.

A bit of information might convince people like me to test the latest builds.
[Moto G 4G Android Development] IronTechmonkey:
Presently flashing and configuring March 30 build.

FYI It seems as if the option to set LOS update checks to manual has been removed, moved, or broken. There are several new commits in this build relating to updater (https://www.cmxlog.com/14.1/peregrine/) but I see nothing obviously related to removal or relocation. If it's broken then this is a regression as this issue did not occur in previous build (although in previous build it said there was an update and offered the same build as was just installed). The circle-with-center-dot icon in the upper left corner of the panel pulses when tapped but there is no apparent effect of tapping it. Still testing but will swing back to this (depending on what else is found).

[EDIT] Checking some previously reported issues before fuller tests:

Persists:

- Phone FC when leaving voice-mail sound settings with Visual Voice-mail disabled: Added note at https://jira.lineageos.org/browse/BUGBASH-315.

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

- Panoramic camera FC: Added note at https://jira.lineageos.org/browse/BUGBASH-326.

Fixed (could use additional confirmation):

- Alarm ringtone permissions being requested properly.

- Can truly disallow location permission for contacts although it popped up twice within one session, but then the setting persisted as it should.

- Google app setting - OK Google detection, has new option to toggle mic permissions so you can can use voice typing, etc. ROM? Google? IDK, but good because that permission was not being requested automatically when app restored from TiBU and other times.
[Moto G 4G Android Development] IronTechmonkey:
Missing update scheduler option.

If missing update schedule option is not a (disappointing) intentional change then it is a regression so: https://jira.lineageos.org/browse/REGRESSION-288

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

In clean flash of March 30 Peregrine Open gapps pico, Native SU package with no apps except mattlog: In Settings - About Phone - LineageOS updates: The option to set update schedule (manual, daily, weekly, etc) is missing.

The the update schedule option is present in March 23 Peregrine.

March30 build.

March 23 build.

The images were captured in portrait mode with font size = largest but the issue was confirmed and logged under normal font sized in both portrait and landscape so - not like something was hiding off-screen. If anyone can confirm this please feel free to vote on the ticket.

[EDIT] No need to vote. Here is the commit: https://review.lineageos.org/#/c/167444/
[Moto G 4G Android Development] odinsbaneful:
SIM card not detected and Mobile Networks causes com.android.phone to stop.

Hello I have an XT1039 and I have installed the nightly lineage os from March 30 with gapps. My sim card is not getting detected.

I tried with two different sim cards, both of which worked before I installed the new rom. I was using CM11 before.

If I go to the settings menu and select Mobile Networks, I get the error com.android.phone has stopped, and click to open again.

I tried installing three different ways, even doing a full wipe, nothing gets the phone to recognize the sim card.

Everything else looks great though, and I really would like to use this version.

Thank You

*Edit

I have tried with CM13 + GAPPs and I still cannot read my sim cards. But the mobile networks doesn't crash. I am currently downloading one of the older stock versions to try it out.

The complete process:

First I upgraded from CWM to TWRP 3.1.0

I installed the latest bootloader, 41.1A

Then I did a complete wipe and put the roms on the sd card (not wiped).

Then I used TWRP to install lineage-14.1-20170330-nightly-peregrine-signed.zip and open_gapps-arm-7.1-pico-20170331.zip

I don't know what step would cause my sim card to not be found, or what I could try at this point short of trying some older roms.
[Moto G 4G Android Development] mrLoma:
I read about this once. It's possible to wipe your imei settings. Sort of the identity of your phone.

That can cause your SIM to stop working.

I never had it myself so I'm not sure, but check this link.

https://xdaforums.com/showthread.php?t=2208207&page=2

The easiest solution would be recovering the nandroid backup you hopefully made. That should put back the partition that holds your imei.

That only works if you made a nandroid backup before you started wiping things off course.

Start with checking your imei settings>about phone>status

Here you can check your imei, also check if you have wifi Mac address.

Your imei is printed on the battery of your phone, in case you need to type it in.
[Moto G 4G Android Development] odinsbaneful:
Great, thanks for the heads up. My phone does not have an imei number, so I think that is the problem.

When I first rooted this phone I backed up as much as I could with ADB, hopefully I got what I needed.

The MAC address is present, so I think I just need to get my IMEI number.
[Moto G 4G Android Development] zeroxcub:
I just wanna tell my story hope it'll be a help to you.

I was on RR 5.8.2, two days ago I got "No signal" basically the sim card is not recognized and impossible to connect to any network (tried 2 working sim from different network operator), then I strolled (really long stroll :P) around the forum to find some info, so to resume my finding if you "fastboot erase all" then it's the end, it may be also a faulty motherboard or just bad luck due to too much tinkering with kernel and roms (don't know how this can happen I always clean flash all my rom :angel:).

So I get the sim card out, clean flashed Stock Optimized LP + radio firmware after reboot radio is working like a charm again and it still working now.

Hope that'll help you out, cheers
[Moto G 4G Android Development] odinsbaneful:
Okay, this worked for me too, eventually.

Before I started I backed up a version of lineage os where everything was working except the imei/sim card.

I tried it once using the 1.1 optimized version, and things got worse. Much worse. First it didn't work so I rebooted and tried again. Then it worked but when I booted into android there were serious problems. When I rebooted again, the wifi didn't work and imei were broken. I restored to my lineage os version, and then I preceded to wipe everything. TWRM wipe/advanced, every box checked except for the usb one. (I didn't want to wipe my sd card, but I did). From there I installed the [stock motorola](https://xdaforums.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816) but this time used the 1.0b EU version. I didn't have many hopes at this point, but when it booted up, I checked the IMEI number and it was there.

Initial state:

IMEI was Unknown

fastboot getvar imei returned a blank.

wiped *everything*

installed stock rom.

rebooted, and the IMEI number was there.

Then I just used TWRP to install the zips for gapps and LineageOS everything went perfect. I made a backup with TWRP so I hope things are good in the future.

I have no clue how my IMEI got corrupt, and none of the expose apps that change imei worked for my situation.
[Moto G 4G Android Development] zeroxcub:
Me neither, good that things go well for you
[Moto G 4G Android Development] IronTechmonkey:
LOS Peregrine April 06 with Open Gapps April 05 and LOS SU...

- Hoping jellyfish is temporary.

- Br0Zip is absolutely hilarious.

- Panoramic camera crash is mostly fixed. There may still be issues when the camera is turned around in a tighter circle. Still testing.

- Other previously reported bugs with jira tickets are still open or in progress.

- [MENTION=7785396]mrLoma[/MENTION], for what this is worth, in regards to gyro sensor: https://jira.lineageos.org/browse/BUGBASH-348.
[Moto G 4G Android Development] jrc2:
[MENTION=5119654]IronTechmonkey[/MENTION],

Which of the latest builds do you think is the best to use as a daily driver?

Also, congrats on being promoted to RC :good:! From what I can see, it's very well deserved. :D
[Moto G 4G Android Development] IronTechmonkey:
Thanks

I've been flashing clean each week and would say keep going with the newest, although different usage cases could yield different results. There is a very funny easter egg in this build.
[Moto G 4G Android Development] cuttero:
..will there be another release-build on CM/LOS 13?

To me the last release-build on CM13 was a little quicker than the LOS14.1 weeklies.. (at the moment). I think, it's because of the RAM-management.. LOS14.1 takes a little more RAM i think.. ;)!
[Moto G 4G Android Development] mrLoma:
Thanks, I haven't had total gyro failure since I did a clean flash last week. Tested yesterday's version. It still had some issues,

For example if you use skymap it needs to be recalibrated every time you start the app. This wasn't the case with cm and stock.

The gyro range and resolution still shows the wrong values (wrong scale), I wonder if that is the case in stock aswel.

I tried the panoramic picture, this still crashed for me. But in the processing phase, it used to do it in the capture phase.
[Moto G 4G Android Development] IronTechmonkey:
As to gyro sensor its still working for me except for the Here maps calibration. Not that I doubt your report, I just cannot reproduce.

As to camera - yep, better but not fixed. In some cases I can complete a picture although it may go to 270 degrees of rotation, and in other cases it may FC during taking of picture as it had before. Also, I'm Noticing a corelation between the FC (and amount of rotation required) and the length off the radius around which the camera is arced. EG at full arm's length it is less likely to FC or require 270 degrees than at half arms length. It is reasonable that there be some lower limit on the radius but in that case the camera should report error rather than FC. Also other cameras (versions of Moto camera) dont experience the same problem. I'm going to continue configuring and adding apps to the April 6 build then, in a day or 2, do a clean flash to re-log the pano camera issue and re-open the pano camera jira ticket.

[EDIT - I've added notes to the jira ticket in hopes of keeping it alive until some clean flash testing and logging can be done.]

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

---------- Post added at 07:33 PM ---------- Previous post was at 07:26 PM ----------

I'm finding LOS 14.1 smoother than CM12.1 or CM13 but different usage cases may yield different results. As to the overall course of development, it is a forward moving thing and once switched to the next CM/LOS version there are no more official releases for the previous version. You might be able to find a custom project somewhere from a developer that is keeping a Marshmallow ROM alive for your device or.... you could install LOS 14.1 and report bugs.
[Moto G 4G Android Development] IronTechmonkey:
Follow up on open reports at jira

It has been confirmed with a note in each ticket that these issues persist in April 06 Peregrine build:

https://jira.lineageos.org/browse/REGRESSION-288 (Missing option to set update schedule (manual, daily, weekly, etc))

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

https://jira.lineageos.org/browse/BUGBASH-315 (com.android.phone FC when leaving voicemail sound settings).
[Moto G 4G Android Development] IronTechmonkey:
April 13 2017 Build

This week’s bug round up (bug rodeo?), busier that last week's.

lineage-14.1-20170413-nightly-osprey-signed, with open_gapps-arm-7.1-pico-20170413 and LOS SU package.

https://jira.lineageos.org/browse/REGRESSION-288; (Missing option to set update schedule (manual, daily, weekly, etc)): Has been fixed.

https://jira.lineageos.org/browse/BUGBASH-315; (com.android.phone FC when leaving voicemail sound settings): Should be fixed in next build by this commit https://review.lineageos.org/#/c/168816/.

https://jira.lineageos.org/browse/BUGBASH-300; (Increasing system fonts size pushes countdown timer backspace button off screen): Initially reported from Osprey but I’ve been confirming it in Peregrine. This is actually the one bug which overlaps my daily usage but is understandably low priority, and easily worked around by using landscape mode to reach the back button.

https://jira.lineageos.org/browse/BUGBASH-315; (Notification panel does not properly close after opening Quick Settings Cast tile) This one I saw drift by in the Jira activity stream and was able to reproduce. I would not even consider it a bug, but themers and others might, and it is an example of how “deep in the weeds” we can go.

https://jira.lineageos.org/browse/BUGBASH-326 (Camera (and more) FC when attempting to take panoramic picture): Speaking of getting into the weeds, the copious details of this issue are in the Jira ticket. In short, the camera scan is much better but it has been but it may be possible to reproduce FCs during the rendering. I’ve tested and re-logged in ROM with my apps installed but may need to confirm in a clean flash. Hint, hint, - if anyone if flashing the April 13 Peregrine has not installed all their apps yet;).

As to the gyro sensors, they seemed OK in very quick tests which would not have reproduced the issue as described anyhow but, cycling season is here and I’ll keep an eye on the sensors while tracking rides. :)
[Moto G 4G Android Development] rabbitvcactus:
EDIT: Ignore this, I posted too fast before realising I made a silly mistake. Will post what I did and how to solve in the morning!

EDIT 2: Ok, so my mistake was caused by going directly from 4.4 Kitkat to this ROM.

Because of this, the radio firmware was out of date, and caused the phone not to detect the SIM card.

The solution was to flash the official Lollipop ROM, then wipe and install this. I'm sure there is a better way, but this is what worked!

Hope this helps somebody, and thanks to the devs for this great ROM!
[Moto G 4G Android Development] IronTechmonkey:
Silly mistakes are sometimes the best kind of problem to have, certainly easier to deal with than many bugs. :) Thanks for the heads up about the change in status, and most definitely share how it goes.
[Moto G 4G Android Development] sevenrock:
This patch might improve RAM usage: https://review.lineageos.org/#/c/168882

Speaking of the camera, in earlier cm versions I was able to take photo sphere images using the Google camera. With Android 7.x this got broken due to camera api2 and so on. Is there a way with LineageOS 14.1 to get photo sphere images again?
[Moto G 4G Android Development] IronTechmonkey:
Been checking out that commit, hoping it does help our capable but low RAM Peregrines. No clue about photo sphere.
[Moto G 4G Android Development] 239:
Works fine for me. There is an issue with the gyroscope in the past weeks though which probably caused inaccuracy for some apps.

However something was fixed with the latest build and compass works again but the gyroscope still seems broken. The range and resolution don't match with the values.
[Moto G 4G Android Development] IronTechmonkey:
There was this commit https://review.lineageos.org/#/c/168147 in re orientation sensor but I dont know if that would affect our Peregrine devices since it states "In KitKat and on most Samsung devices"

As to those sensor readings, have you watched those values while actually rotating the device? Those readings may be normal when device is stationary. Gyro measures rotational speed while the orientation sensor measures orientation (and they both work along side compass and GPS in map apps). I've seen the same in Sensors MultiTool even when the sensors work fine in Google Maps and Here WeGo. Although the Here WeGo calibration routine fails, both Google Maps and Here WeGo use compass, orientation, gyro, and gps OK.

You can find more notes about the sensors from developers and testers by searching this thread and the Jira ticketing system https://jira.lineageos.org/secure/Dashboard.jspa for "sensor", "gyro", "orientation", "compass". Also, I would recommend instead of Sensors Multitool using Aida64 which shows all of the sensors on one page (and Aida64 is one of the best system information apps I've ever seen on PCs or Androids).
[Moto G 4G Android Development] 239:
The screenshot was actually made after rotating the device and you have to look closely to notice the tiny bumps. That's why the scale doesn't fit.

You are right but in this case it's much easier to see that something is wrong when looking at the graph. Otherwise I wouldn't even have noticed the issue.

Thanks for the link, I'll look into the thread later.
[Moto G 4G Android Development] mrLoma:
Though I agree that Aida is a good tool, it does not show the resolution and Max range.

Some apps use this for noise reduction afaik.

According to the gyro s datasheet the range can be 2000 but that should be degrees per second, not rads.

"Three selectable full scales (250/500/2000

dps)"

Don't see the resolution in that doc but I'm sure it's closer to 1 degree per second than 1 rad.

Some apps use the gyro and the range and resolution to reduce noise in the readings.

I think skymap does cause last 4 or 5 builds I have to recalibrate my "compass" every time I open the app. I also have to do a violent 8 shape to get it calibrated. It used to be easy to do.

Are these values in some kind of settings file, so we can do some tests with it or are they pulled from the sensor?
[Moto G 4G Android Development] IronTechmonkey:
Ahhh, I may never have scrolled down to the graph (hanging head in shame). Thanks for the clarification.

---------- Post added at 08:47 PM ---------- Previous post was at 08:02 PM ----------

Point taken. You and [MENTION=6076637]239[/MENTION] have convinced me to keep Sensors Multitool around.

I defer to you in regards to those technical details, but what you describe about the calibration seems exactly like what occurs in the HereWeGo calibration routine even though the app uses the sensor OK (and Google calibration is OK). As to the violent motion, yes and sometimes I've even indulged the calibration with a simple long fast downward chop. Not sure where the values might be stored but that's a good idea.
[Moto G 4G Android Development] sevenrock:
The patch should have had no effect because the dlmalloc code was removed from bionic.

Right now I am compiling with this patch to add back dlmalloc.