yashsingh1/xdaforums huggingface dataset:
[Moto G 4G Android Development] minimale_ldz:
I had the same problem some time ago and couldn't unlock the phone until I flashed retail stock firmware over carrier firmware, so check what firmware you've got because that's where your problem could be.
[Moto G 4G Android Development] IronTechmonkey:
Upon reading your answer, which does make sense for provider-unlocking a phone, it becomes apparent that poster of question was not clear about whether they are unlocking the phone or the SIM although I suspect they are trying to unlock the SIM card: "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"
[Moto G 4G Android Development] minimale_ldz:
I meant SIM unlocking of course, IDK why I wrote "phone unlocking" . Sorry for confusion.
[Moto G 4G Android Development] IronTechmonkey:
A question about notifications in regards to new "feature" of Nougat; Bundled notifications. Bundled notifications are: When the same app delivers multiple notifications they are condensed into one expandable notification. In regards to the swipe down notification this is OK but in cases where the notification includes an icon to be displayed at upper left of status bar, as soon as a 3rd (or 4th) icon is added, the icons merge into the main app icon which defeats the purpose of having them in the status bar in the first place.

This is a particular problem for Tasker which maintains its own permanent notification and icon for the main Tasker app, but can also create notifications with icons as part of various tasks and phone states. I use Tasker to set various states of the phone and notify of those states with permanently visible icons in the status bar like so:

Useful (for my purposes) in CM12.1/L5.1.1 without bundled notifications:

Useless (for my purposes) in LOS14.1/N7.1 with bundled notifications:

.

I've found an article (http://blog.danlew.net/2017/02/07/correctly-handling-bundled-android-notifications/, Section: Cancellation Side Effects) which describes "disassociate the remaining (primary) notification from the group" to allow a primary notification to be canceled without canceling the rest and I wonder if that functionality could somehow be used to prevent the bundling in the first place at least for a given app. Along those lines I should contact Taker Dev but wanted to see if anything could be done in the OS first.

I shake my fist at a Google colored sky: They are notifications that were put there to serve a purpose by being visible, aka acting like notifications, not for Google to play hide and seek with important status indicators.
[Moto G 4G Android Development] georgios.evangelidis:
BLE not supporting more than one connections

First of all I have to thank all the developers for the great work! I tried LineageOS back in January, but bluetooth would not work with two devices (watch and heart rate monitor). Has anybody tested recent builds? The same was true with the latest CM14.1. Currently, I am back to CM13.0 where bluetooth works OK.

Thanks in advance!
[Moto G 4G Android Development] IronTechmonkey:
Please remember, this not a review board. It is a development thread where the purpose is to contribute to development rather than just wait for what works. Assuming that you've searched the thread and found no confirmation that it was fixed (if it was actually broken), each usage case may be different and may be affected by different factors, so you should test it yourself, and file a bug report if it does not work. At that point I'd be glad to jump in and help test and verify the report.
[Moto G 4G Android Development] IronTechmonkey:
FC and SIM restart issue in Phone settings. This is on retail XT1045 (single SIM) on T-Mobile, lineage-14.1-20170309-nightly-peregrine-signed, open_gapps-arm-7.1-pico-20170309, native SU.

Open Phone app - Settings - Calls - Voicemail - Sound - OK or Cancel = FC "com.android.phone keeps stopping".

Device briefly sees no SIM (as observed in status bar) then SIM reappears in status bar then 2 or so seconds later prompt to "Select SIM card" is presented.

I'm revisiting last weekly to see if this is an existing issue or new regression. If regression, will post log. [EDIT] Not a regression. Same thing occurs in last weekly.
[Moto G 4G Android Development] jdegreef:
Confirmed on xt1039 with last week nightly, I've not yet updated to the latest one. Sim card is briefly disabled then re-enabled but I don't get the sim card prompt.
[Moto G 4G Android Development] mrLoma:
Do your gyroscopes still work?

Mine seem to have stopped working. Sky map says the accuracy of the sensors are bad. And I can't fix it with the recalibration method.

Sensor multitool app does not show data for the gyroscopes.

Does any one else have this?
[Moto G 4G Android Development] 239:
Same here (20170309-nightly), according to Sensors Multitool everything works fine except the gyroscope.
[Moto G 4G Android Development] sevenrock:
According to https://play.google.com/store/apps/details?id=asd.vector.sensor the gyroscope works on a self-compiled ROM dating 2017-03-11.
[Moto G 4G Android Development] mrLoma:
They seem to work again on today's build.
[Moto G 4G Android Development] Lobo_Azul:
Compass inaccurate

Hello. New here.

Using Lineage OS in my XT 1045, I've noticed the compass is completely inaccurate. It's not stuck, but it rotates constantly like if magnetic north were constantly changing (lol)

This is happening with current build and at least two builds before, I've tested.

Since I only have one XT 1045, I can't test in another hardware. Is this happening to anyone else or it's only me?

I'll try later flashing other roms or/and the stock rom to see if it also fails with those.
[Moto G 4G Android Development] IronTechmonkey:
Please be advised that we are expected to read original posts and search for answers (actual XDA rule). That being said, yes it's happening to others. You can see exactly what others have reported by reviewing the recent pages of the thread and searching for "gyro" or "sensor" or "compass" . Also, I think this might be a legacy related to quirky hardware, older sensor type, or competition for exclusive hardware access. I saw something similar occur in Peregrine CM12.1 in a parallel test with a different device (CM12.1 Osprey). I'm actually in the middle of writing some notes which meld that experience with these new reports and will post it later.
[Moto G 4G Android Development] IronTechmonkey:
An FYI about a non-device specific UI issue that affects Peregrine. As system font size is increased the backspace button in the countdown in portrait mode is pushed off screen. Details in the Osprey thread here https://xdaforums.com/showpost.php?p=71493020&postcount=3568, but it's the same in Peregrine.
[Moto G 4G Android Development] IronTechmonkey:
Gyros accelerometers sensor calibration isssue.

When gyro sensor issues started appearing in this thread (or at least when I noticed them) I gave this a test in the March 09 build where the sensor did not disappear but it did have trouble staying calibrated. Now, in the March 16 build the calibration routine seems even worse, but the maps seem to orient and move OK.

- Peregrine LOS14.1/N7.1 March 16 build.

- Using GPSfix to get fix then switching to Here WeGo to test orienting the map.

- Calibration is requested every few seconds but the compass and gyro seem to be orienting the map properly even if that prompt is ignored.

- The calibration gesture prompt can be obliged momentarily with a quick single direction wave (such as a long down chop) which AFAIK should not result in successful calibration. Ironically, this may mean that calibration routine it's self needs to be calibrated.

- GPS Status and Toolbox (different app apart from GPS fix) shows smooth accurate motion for compass and gyro (level).

- Sensors seem OK in apps Aida64 and Sensor Multi tool.

- For what it's worth: Before these map apps can start using the gyro sensor they neeed their GPS fix so, could GPS be a factor?

- For what it's worth: In re disappearing sensor there is always the potential for problems caused by competition for hardware device - as is sometimes the case with cameras and microphones.

Among some commits relating to a new custom tiles feature there is one that incidentally mentions that the compass QT is not working (and should not be included in custom QT until fixed) https://review.lineageos.org/#/c/165827. I don't know what bearing that has on the actual calibration issues but it might be worth noting.

Searches for similar issues at jira find nothing exactly the same however there was one particularly interesting comment in an accelerometer issue for anther device (shamu): "make sure you're also on the latest bootloader, modem/baseband/radio, and vendor.img for your device ". It just so happens that we've updated our bootloaders to get here so there is another possible factor.

Most definitely worth logging and reporting at jira (weekends when they'll receive non regression reports) but this may require a log taken from boot and going through a few bad calibration attempts. Will try to test and get log next from next build. The more the merrier.
[Moto G 4G Android Development] mrLoma:
I just tested gyro and accelerators again. Nothing worked in multitool.

After a reboot it worked again. ?
[Moto G 4G Android Development] IronTechmonkey:
As I said "Most definitely worth logging and reporting at jira (weekends when they'll receive non regression reports) but this may require a log taken from boot and going through a few bad calibration attempts". That does not mean it has to wait for the weekend.

Also, since stating that something is (still) not working does not equal a bug report, here's a reminder of what comprises a bug report (dont take this personally it is a general reminder):

- Testing is done in a clean flash of most recent nightly/weekly with no mods or hacks and is done under LOS native SU package (if any SU package).

- Provide Details of the device (model #?* Single dual SIM? Anything that distinguishes your device from others running the same ROM).

- Name the specific nightly/weekly being tested (and Gapps package too).

- Provide a description of the exact steps taken to reproduce the error (so others who would try to reproduce or fix the issue might be able to test it).

- Share a logcat taken while the issue was being reproduced as described in previous step.

Clean flash:

- No hacks or mods of any kind. No custom kernel, no Xposed, even no SuperSU. Seriously none whatsoever.

- Confirm that you are using the proper recovery, ROM, Gapps, and SU packages.

- Wipe Dalvik and System caches (optional)

- Full wipe, aka Factory reset

- Install ROM, Gapps, SU package during same TWRP session.

- Wipe Dalvik and System caches

- Reboot to system.

- Let the phone settle for 5 or 10 minutes to indulge first-boot-post-flash scans.

- Reboot, and give phone 2 or 3 minutes to perform normal boot media scan.

- Test the issue before you install any app that are not necessary for the test.

* The device model # may be a significant bit of information for a hardware issue like this and should be including any any report

The above is all standard operating procedure for bug reporting. Don't leave it up to others if you want this fixed. ;).
[Moto G 4G Android Development] mrLoma:
Thanks for the complete, clear list and explanation.

As a Dev I know how important a good bug report and a repro can be, but I don't have time right now, I'll see if I can make a report this weekend.

Since it's not something noticeable right away, I thought it was a good idea to at least let people know.

I'm not on a clean install and this is my daily driver phone.

So it's full of data/apps I need and use.

It's a xt1039, 1 sim. Latest build. After reboot everything works fine, don't know what triggers the issue yet.

After reboot multitool shows values, when the issue happens all the values are "-".
[Moto G 4G Android Development] IronTechmonkey:
I can dig it. There is that good testing window after a flash but then at some point we've got to put our stuff on the device.

Still, it's a good idea to include with even passing mentions of a problem, whether or not it was in clean or dirty flash. This is not to frown on dirty flashing (which I confess to doing in a different context) Just that it is a significant factor even when assessing a quick heads up. I (or anyone else) could have sailed into a hours of testing based on what you said, which is often wasted time and effort when done in clean flash and being compared to dirty. We should be able to assume clean unless dirty is specified. As a dev you probably don't appreciate chasing false leads and can appreciate this.

When you do have a chance to test, if you find some combination of things that seem to cause the sensor to disappear I can try to reproduce it with an eye toward combinations of apps and difference by device model #s. I'll also try to log the calibration issue (which I can easily reproduce) in the next build.
[Moto G 4G Android Development] mrLoma:
I think I could've found the issue or at least part of it.

The gyro it's range and resolution are pretty strange when or at least the values I see in multitool.

It goes from 1 rad/s to 2000rad/s which are the correct values in degrees. In rad/s it's basically useless.
[Moto G 4G Android Development] IronTechmonkey:
Good catch, consistent with and more diagnostically valuable than the gut feeling I had that the scale of the calibration routine is off (at least in one axis). It's better to have some actual data instead of gut feelings. Thanks! I'll take a look at those #s first thing after next flash and then keep checking as different things are tested.

[EDIT] [MENTION=7785396]mrLoma[/MENTION] and anyone else with the sensor problems. If this commit makes it into the upcoming build we may have a fix or at least something new to test. https://review.lineageos.org/#/c/166616.
[Moto G 4G Android Development] diziet_sma:
Bluetooth audio skipping

Hi all,

I've done some googling and also searched this site but I've found nothing conclusive to help me. I have a XT1039, currently running the latest lineage nightly. For quite a few nightlies now, incl. the latter few cyanogenmods I have experienced bluetooth audio skipping forward (not muting) just a second or less when playing. The odd thing is that this only seems to happen with the specific combination of my phone and the one bluetooth device in my car (an fm transmitter that takes my bluetooth audio and re-transmits to my old head unit). Using my daughter's ipad and her b/fs phone results in no skipping, and using my phone with other devices (incl. modern bluetooth head units in other cars) also result in no skipping.

I am thus at a loss as to where the problem lies and I'm reaching out to find out if anyone else has experienced this (a search of xda does show up some instances of this on other phones, but no conclusive solution), or if anyone has a suggestion - other than 'buy a new device' :)

At some point in the past either kitkat to lollipop or lollipop to marshmallow, I had to install newer radio/modem files using adb, am I supposed to have done this with nougat?

diziet
[Moto G 4G Android Development] IronTechmonkey:
Gyro sensor still NG, new issue with panoramic pictures.

FYI Even though the commit I referred to a few posts ago was included in the March 23 build, the issue of gyro sensor repeat request for calibration persists in March 23 build. I'll see if I can log and report this at jira this weekend.

[EDIT] I'm now wondering if this gyro sensor thing is a problem with apps not properly communicating with the ROM and hardware under Nougat as opposed to a purely ROM issue. I was also testing in Osprey where the same thing was happening with Here WeGo, so I tested in Google Maps on both devices and in Google Maps the sensor is fine and never requests calibration. I suppose it could still be a ROM issue but the list of things that are ok with the sensor is growing, at least for me. It would be a bummer if google maps was the only one that did not have this problem

Also, we seem to have a new issue with panoramic pictures. It is the same issue described in the Osprey thread (I've been testing Osprey and Peregrine March 23): https://xdaforums.com/showpost.php?p=71561814&postcount=3623.

I've reproduced the pano pic issue in Peregrine but, if anyone is presently on Peregrine's March 16 build it would be very helpful to know if panoramic picture works in that build. If it does then this is a regression and need not wait until the weekend to be reported at jira.

Can anyone else confirm this as an issue in March 23 and or March 16 build? It's an easy one to test, just try to take a panoramic picture :)

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

There have been some reports of BT audio skipping in this thread and elsewhere but I've seen no workable bug report or confirmation that this occurs in a clean flash of the ROM with no modifications applied. You should not have to install newer radios for what seems to be just an under-reported ROM or device issue; but who knows, maybe this is a bug related to just that. What is needed is for someone who experiences the issue to log from a clean flash then share that log with the details that would typically be included in a bug report. I would try to reproduce this but my usage scenario and gear preclude doing so.
[Moto G 4G Android Development] mrLoma:
Hey diziet ,

I had some bt issues in the past. Last time I used it with last weeks build we were in the car for an hour using bt listening to offline Spotify without skipping. I told my gf hey this looks fixed then the next song started skipping ?.

It is a lot better for me than a few builds ago.

OK a few things can cause this.

Interference-> try disabling all things you don't need ; disable WiFi, location, data..., Try placing your phone on another place in your car.

If this solves it, check which one is the culprit.

I noticed that location uses bt even when it's switched off to improve your positioning, which makes zero sense to me. Disable that one too for good measure. Under location ... Scanning etc.

It could also be an incompatibility issue between the two different bt versions or the implementation of the bt FM transmitter. Not much you can do about that.

Could also be an app resource issue, make sure you have enough free memory, close all background apps and clear all other recent apps.
[Moto G 4G Android Development] mrLoma:
I can shake the idea that it had to do with the resolution and Max range values. If apps use those to calculate things. This will not be very accurate.

I used 2 different sensor apps to see if it's not a multi tool bug.

If these values are used it's going to be hard to get any valid values, hence the calibration will think you're not moving your phone a lot and fail calibration. Just my two cents.

The values that show up in the test tools are correct though, so if the app doesn't take the range in account it'll all go fine.
[Moto G 4G Android Development] IronTechmonkey:
Forehead slap: magnetometer, accelerometer, and orientation sensors, not gyro (somewhere along the way I got this twisted).

It is a combination of magnetometer and orientation sensor or accelerometer that is orienting and leveling the map. The gyro sensor measures rate of rotation (which is not really required to orient map). I suspect that your orientation sensor and accelerometer values line up better with what you expect for rotating the device to orient a map, and that if you wave the phone in an arc (while somehow managing to see the screen) you’ll see appropriate gyro values

For good measure I restored Peregrine CM12.1 and saw the same sensor readings, and the same version of HereMaps calibrated fine. I feel the same as you that there is something wrong with the scale or the math of the calibration routine in LOS N but it’s still not clear where responsibility for the fix lies. The sensors work fine in the app just not for the calibration routine in HereMaps.

BTW, the app Aida64 can give you a view of all sensors on one page so you can compare several while testing the same motions/actions.
[Moto G 4G Android Development] pigeons9:
Issues w/ Root Apps

I'm unable to visit root folders in a file manager. I'm using Ghost Commander & tried a couple others with no luck. I think this began when they removed CM file manager from the build, as I remember being able to access root folders before then. I flashed the root img, and the ADB & Apps root options appear under Dev Settings. I am able to get into the phone with adb. Anyone else experience this? Do I need to install superuser as well?
[Moto G 4G Android Development] IronTechmonkey:
You might have to install the SU package (which should be done in same session as ROM and Gapps flash). I've seen various opinions about the state of root the device is in under LOS 14.1 without the SU package, and here is my take on it:

At one time before the advent of the native CM and LOS SU package, and in an earlier generation of hardware, it was common to root the stock rom on the device and then install SuperSU for management of permissions. If I remember correctly you could root and SU without unlocking boot-loader and return to stock image for OTAs. If you did unlock the boot-loader and install a recovery you could then SuperSU to root and manage SU on a stock ROM (but no easy return for OTAs). At that time CM11 would appear to be rooted (perhaps granting the r/w access you seek) but SU permissions would still be managed by SuperSU installed from PlayStore or flashed.

Now that the LOS SU package works effectively (which was not always the case before it was separated) maybe it was removed for just this reason: To be able to present a truly stock ROM experience without root or SU. Let's call that conjecture, but I can vouch for the fact that with the SU package and a good file manager (or 2, rarely does 1 work for everything) you can get r/w access to most locations.
[Moto G 4G Android Development] diziet_sma:
my phone is my only one, in daily use, i do a backup before updating but dirty flash then, would a log from a dirty flash be of no use at all?

diziet

---------- Post added at 10:45 PM ---------- Previous post was at 10:40 PM ----------

i already had the scanning turned off and never have location or wifi on unless i'm using them, thanks for your reply though :)

diziet
[Moto G 4G Android Development] IronTechmonkey:
A log from a dirty flash might reveal something and is certainly easier that re-flashing. Give it a try.

Also, just to to clarify: There might actually be cases where the fact that something failed through dirty flash might considered a bug, however even the testing for such an issue would start with or at least include a comparison to a clean flash. Clean flashing helps separate actual rom issues from app issues.

An important thing is to mention which method was used so developers and testers dont wasted time.
[Moto G 4G Android Development] IronTechmonkey:
com.android.phone FC

FYI In re com.android.phone FC when leaving voicemail sound settings: https://jira.lineageos.org/browse/BUGBASH-315.

Please feel free to vote for the ticket if you can reliably reproduce this issue like so...

- Open phone app

- Settings

- Calls

- Voicemail

- Sound

- Cancel (or select a sound then, OK)

- Error "com.android.phone has stopped" or 'com.android.phone keeps stopping".

- "Select SIM card" prompt appears as SIM is re-detected.

[EDIT] While testing the above I accidentally discovered one-handed mode (swipe left or right across nav bar). Although one handed mode on the small peregrine screen is somewhat amusing I'd prefer to disable it. Does anyone know of a way to disable one-handed mode?
[Moto G 4G Android Development] pigeons9:
Thanks for the explanation. I do have the su package installed. I currently don't run any apps needing root & I'm able to adb into my phone and run su in a terminal, so it's not a big deal, was just curious what the issue may be. I also read it may be an incompatibility with apps as Android/LOS evolves?