yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] IronTechmonkey:
OT:

I doubt that you would appreciate it if people here called you "child". "Bro" is similarly disrespectful, and you are being told that it is a childish and unappreciated form of address too familiar for some people in forums like this. If you want to address people (at least me) that way then go join a social chatroom somewhere. No need to respond to this post.

OT over.
[Moto G 2015 Original Android Development] KrisM22:
test failed - too short :D okay, nuf!
[Moto G 2015 Original Android Development] Arshadhack:
Ooo ok sir:o
[Moto G 2015 Original Android Development] IronTechmonkey:
Physical keyboard settings not persisting, and LiveDisplay issues when GPS is used: Not device specific, reported from Peregrine, also reproduced in Osprey. Details and links to Jira tickets in this post in Peregrine thread:https://xdaforums.com/showpost.php?p=72885562&postcount=921, but if you reproduce them on Osprey then post here in the Osprey thread. Comments and votes from either device could be added to the Jira tickets.

[EDIT] Clarification in re Physical Keyboard: This would apply to most external (AKA - physical) keyboards which, when used on Android devices, preclude the need for the on-screen keyboard and therefore are more dependent on auto-correct. This is what the options in Settings > Languages & input > Physical keyboard are supposed to handle but do not. To witness it you can test it as described in the jira ticket: with "USB keyboard attached via OTG, or with BT keyboard attached." Even without any external keyboard attached the issue is clear by doing what is described in the ticket in re logging the issue:

- With no physical keyboard attached.

- Open Physical keyboard settings through main settings panel.

- Enable the settings in question.

- Back button to Languages & input.

- Open Physical keyboard settings again = the settings are no longer selected.
[Moto G 2015 Original Android Development] KrisM22:
I have an OTG adapter but I'd have to go buy another keyboard. - no spares around.
[Moto G 2015 Original Android Development] IronTechmonkey:
The issue can be replicated as described without any external keyboard. Even if it cannot be verified with a keyboard the settings can be observed reverting back to disabled.
[Moto G 2015 Original Android Development] KrisM22:
Hopefully I'll get a chance to test it tomorrow - today was a total loss. sister: router: wifi: phone.

Is it fair to expect it to save settings if there is no actual keyboard?
[Moto G 2015 Original Android Development] IronTechmonkey:
Considering the way this setting is presented and the way similar settings are presented I would expect yes. The fact that it behaves the same way with a keyboard attached is just the clincher.

[EDIT] Another possibility is that autocorrect for physical keyboard is a depreciated feature to be removed from the ROM, in which case we would be dependent on apps supporting the red underline spell check but it seems that there are fewer and fewer apps which support that. The native Messaging app supports it as does the XDA Labs app but surprisingly many text editors and word processors do not.
[Moto G 2015 Original Android Development] KrisM22:
Posted to jira bug 761: "I concur - Osprey 2GB, Microsoft 600 keyboard, Inland OTG dongle. You can set them but if you leave and come back to Settings/Languages and input/Physical keyboard, they are again off. "Show virtual keyboard" is the only one that remains on."
[Moto G 2015 Original Android Development] mrViZhy:
Wi-Fi calling

Hello All,

Thank you for this best rom for my device! :good:

It is possible to have Wi-Fi calling/VoWiFi on our devices?

As i know, on T-mobile branded devices this option is aviable.
[Moto G 2015 Original Android Development] KrisM22:
It depends on whether your carrier offers it.
[Moto G 2015 Original Android Development] mrViZhy:
My carrier offering VoWiFi, but i cant find how to enable it on my Osprey.
[Moto G 2015 Original Android Development] KrisM22:
I find this for the oneplus3

But I do not know if it works on the Osprey - my carrier (ATTUS) doesn't have it afaik. so I can't test it.
[Moto G 2015 Original Android Development] mrViZhy:
My carrier - T-Mobile. They support VoLTE and VoWiFi.

Osprey's Snapdragon 410 is supporting VoWiFi.

Information from official qualcomm site:

Next-generation Calling Services:

Voice over Wi-Fi (VoWiFi) with LTE call continuity

HD Voice over 3G and VoLTE

Osprey's processor supporting also handover beetwen Wi-Fi and LTE.

:rolleyes: But in LeneageOS no options to enable this functionality. In internet no information about it.

I tried to enable it using manual from XDA, but this solution does not work.

:laugh: Yesterday i didn't know nothing about VoWiFi, but in my new home is very low T-Mobile signal strength ...
[Moto G 2015 Original Android Development] KrisM22:
country? carrier?
[Moto G 2015 Original Android Development] mrViZhy:
Country: Poland; Carrier: T-Mobile; Information from T-Mobile about VoLTE and VoWiFi (in polish lang)
[Moto G 2015 Original Android Development] Subinsmani:
Ya wifi calling is there but it culd not wrking.. may my carrier is not supporting till now thatswhy..
[Moto G 2015 Original Android Development] mrViZhy:
When you close this layer and open WiFi calling will be disabled. I think it cant be enabled, because LineageOS kernel does not has VoWiFi libs or some driver.

Anyway ROM is very good (i'm on today build).
[Moto G 2015 Original Android Development] KrisM22:
What you could do is start a thread in the Q&A section for Osprey and see if anyone there knows of a rom that will do what you want...
[Moto G 2015 Original Android Development] mrViZhy:
VoWiFi/Wi-Fi Calling for Osprey thread is created there. Thank You!
[Moto G 2015 Original Android Development] Sachin ET:
Can anyone tell me how i can change the SELinux mode to permissive in this ROM?
[Moto G 2015 Original Android Development] IronTechmonkey:
An answer in Q&A thread: https://xdaforums.com/showpost.php?p=72955358&postcount=107.
[Moto G 2015 Original Android Development] IronTechmonkey:
July 6 build review of reported bugs (and not bugs).

Clean flash, July 6 LOS Osprey, with July 6 Open Gapps Pico and LOS SU

-------

Minfree (LMK) and Kernel stuff:

I've been logging issues Peregrine because I still have to change the LMK settings on Osprey to prevent apps from being killed, and I'm using squid2 kernel to stop reboot freeze, and those things don’t make for clean ROM testing. That being said, we've go a lot of kernel related commits from Alberto97 coming up in the next build which I'm eager to test: https://www.cmxlog.com/14.1/osprey

-------

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

A particularly easy bug to reproduce, but getting few votes. It would be great if anybody else would vote on this one. It can be easily and safely reproduced by setting system font size to Largest and witnessing the disappearance of the back button in the countdown timer in portrait orientation.

-------

LiveDisplay does not apply the blue screen at night when set to automatic; https://jira.lineageos.org/browse/BUGBASH-226: This is fixed. Also, in regards to night mode being invoked an hour later after using GPS....that may be an intended behavior and I apparently had this backwards in re the remaining partial dependency on location fix.

After a reboot LiveDisplay uses whatever information is available which in my case had the transition occur an hour early (which I thought was the correct time for the transition), and then after a GPS fix it adjusts to make the transition at the proper time (which I thought was the wrong time for the transition). The GPS adjusted time for the transition may be correct one, but I suppose time zones and daylight savings might be a factor. I'm remembering an article or old CM12.1 commit which describes this but cannot find it and would be interested in any available explanation of the mechanism,as well as at which time the transition to night mode is complete for devices at the same latitude as New York City. In any event, LiveDisplay seems to be functioning reliably and serves its purpose when the transition is made at either time.

-------

Physical keyboard: Auto-replace, Auto-capitalization, Auto-punctuate settings do not persist:

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

Apparently the auto-correct settings for physical keyboard which seem to be reverting are actually just indicators of whether they are being used by the input method (the AOSP on screen keyboard). Unfortunately the native AOSP Keyboard does not support auto-correct when physical keyboard is attached. It is possible that third-party keyboards would support it but I'm not certain of that. The explanations of this is in the Jira ticket.
[Moto G 2015 Original Android Development] xfahim:
June 29th Build. I've been noticing a battery bug with the Pebble app where it will use a lot of battery even when the screen is off. This is the first time I've seen this type of battery drain from the Pebble app. It's always at 1% usage.

I'm going to update to the latest build this weekend but before that is there any way I can find exactly what is causing the app to act this way? I've added battery status of two separate day to back it up.
[Moto G 2015 Original Android Development] KrisM22:
You would need to ask that at pebble forums. I see you are not the only one with that problem.

https://forums.pebble.com/t/pebble-android-app-huge-battery-drain/30172
[Moto G 2015 Original Android Development] jay.bhadra1995:
I have noticed that after installing this ROM, during call, people seem to complain about hearing their own voice when they speak. Anyone else facing the same issue?
[Moto G 2015 Original Android Development] IronTechmonkey:
Minor regression in clock + button.

Notification of set alarm pushes the pink add button (+) higher on display where it persists across all clock panels until clock is closed by back button and opened again. A few screenshots below. More details and screen shots in Jira ticket: https://jira.lineageos.org/browse/REGRESSION-821. Should be easy to reproduce if anyone would like to vote for it.
[Moto G 2015 Original Android Development] KrisM22:
Whenever I get that artifact myself it is because I am talking to someone where they are on a landline.. It can occur cell to cell if the connection is made over the "long lines", ie a physical connection. I would suggest you try previous LinOS roms and non-LinOS roms before filing a bug.
[Moto G 2015 Original Android Development] jay.bhadra1995:
No. Mine isn't the case of landline or cell to cell long lines either. It is normal calling within the same area or city itself over cell to cell which is giving me this issue. I have 2 questions:

1. Can it be a hardware issue?

2. How do I roll back to previous LinOS rom without losing any of data/not doing a clean wipe?
[Moto G 2015 Original Android Development] KrisM22:
imho not likely to be anything other than a switching artifact. EDIT: I suppose a bogus BT headset could cause it... EDIT2: I can induce it when testing a rom I dial myself via skype and the mike is close to speakers, but that's just local feedback.

In TWRP, nandroid(backup) what you have and then clean wipe and test at will. When going back to where you are now, clean wipe and restore. Make sure you never wipe 'internal storage" or "sdcard" or you will lose your TWRP backups.
[Moto G 2015 Original Android Development] IronTechmonkey:
I'm not experiencing this issue in recent LOS builds on Osprey or Peregrine.

To [MENTION=2945516]KrisM22[/MENTION]'s points: The only time I've seen something similar (several months ago) was when calling from my cell phone to a particular local range of landline numbers but not when those landlines called me and not when I called out of the local area from the cell phone. Those issues, which have since been resolved, were almost certainly with my mobile phone service provider and or the regional landline provider.

Before going through too much trouble testing ROMs you might want to contact your service providers to report this, without expecting them to have an immediate fixed but at least to put it on their radar.
[Moto G 2015 Original Android Development] jay.bhadra1995:
Seems like I will have to give it a try with an older version or the stock rom again. I don't have a BT headset at all. I had my microphone changed recently since it wasn't working but don't see how that can affect the speaker at the ear level, microphone being at the bottom speaker that way.

And thanks for the procedure. I will definitely follow that.

Also, which is the recent most stable LinOS version?
[Moto G 2015 Original Android Development] KrisM22:
Yes, it is possible, though unlikely that either the mike or the earpiece in the phone could cause it. Like if you had dunked your phone and then it happened I would have you replace both.
[Moto G 2015 Original Android Development] rahul9999:
Latest nightly build is 06.07.2017 - lineage-14.1-20170706-nightly-osprey-signed.zip

If you wanna flash then wait till tomorrow evening as new build will be release by tomorrow evening :o
[Moto G 2015 Original Android Development] IronTechmonkey:
I apologize for bumping but it seems justifiable in this case: The last page has been off topic troubleshooting of a flashing, hardware or telecom issue (IMO [MENTION=2945516]KrisM22[/MENTION] is spot-on about it being a switching artifact, in other words a telecom issue) which is not related to the ROM. I would not have said anything if a page of off topic were not dumped right on top of a report of an actual regression in the ROM (which may have to do with a new feature added to the Alarm clock).

Getting back on topic...

Notification of set alarm pushes the pink add button (+) higher on display where it persists across all clock panels until clock is closed by back button and opened again. A few screenshots here: https://xdaforums.com/showpost.php?p=72988966&postcount=5035. More details and screen shots in Jira ticket: https://jira.lineageos.org/browse/REGRESSION-821. Should be easy to reproduce if anyone would like to vote for it.
[Moto G 2015 Original Android Development] balaji.vr06:
Great ROM! Thanks dev! :D

I'm getting 6hrs sot with continuous usage, and my kernel settings are balanced settings....
[Moto G 2015 Original Android Development] KrisM22:
I'm not sure this is the place for this ( meaning here or jira), but I set 2 alarms and I see no shift in where the red + is. But I notice you are using a larger font.

same reason for why I don't change fonts or use theme engines. - things just don't work.
[Moto G 2015 Original Android Development] IronTechmonkey:
Reproduced on 2 devices in July 6 build (clean flashed) and also occurs at default font size (as described in Jira ticket). Your pictures do not show the toast notification of set alarm or an alarm in set condition as described and shown in screenshots in the Jira ticket.
[Moto G 2015 Original Android Development] IronTechmonkey:
In regards to this apparent bug (Jira ticket: https://xdaforums.com/showpost.php?p=72988966&postcount=5035): Since some doubt has been cast on it, below are the full notes and screenshots from the ticket . If anyone who has not already reported on this can reproduce it as described in the ticket and screenshots please vote on it. If you are unable to reproduce what is described in the ticket and screenshots please do share the details of the differences you noticed. Thanks.

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

Jira ticket: https://xdaforums.com/showpost.php?p=72988966&postcount=5035:

Notification of set alarm pushes the pink add button higher on display where it persists in all clock panels until clock closed by back button and opened again.

- When an alarm is enabled the pink + button is moved higher on the display to accommodate the notification “Alarm set for <X time from now>”. AddButtonMovedAlarm.png

- The button persists at that location on all clock panels (until clock is closed and opened again). AddButtonMovePersistsAlarm.png, AddButtonMovePersistsClock.png, AddButtonMovePersistsStopwatch.png.

- Going directly to Home screen then back to clock does not put button back in normal location.

- Exiting clock via back button then opening again does put button back at expected location. AddButtonNormal.png

To reproduce: enable an alarm.

Attached log, <at jira ticket>, spans enabling an alarm then swiping across panels to confirm results (screenshots taken later while not logging). It would not be surprising if this were related to this “switch to profile” commit https://review.lineageos.org/#/c/179147/ which first appeared in the same build as the aforementioned issue with button. Note: In the attached screenshots the system font size is set to largest but the same thing occurs when they are set to normal (to a lesser degree but still not quite right).
[Moto G 2015 Original Android Development] guest_2011:
xt1540 6/22 build still get BT disconnect when wifi is out of range. I usually notice when i walk with my BT headphones but this time i paired with a car. Then got BT disconnected message. Same problem. Not sure if any july builds still have this bug or it's been fixed in recent builds. I don't want to update yet. Everything else seems ok and battery life is good.
[Moto G 2015 Original Android Development] KrisM22:
You know, you could save where you're at simply by backing up in TWRP and then creating a new build with only what you need to test BT... Then you would restore back when you're done - don't forget to wipe dalvik/art,data,system,cache before each step.
[Moto G 2015 Original Android Development] rahul9999:
Just for the information Squid have updated his TWRP to latest version twrp-osprey-3.1.1-r1 , Also he is going to update his Kernel soon,

Below are some words from Squid -

I've rebased my TWRP fork on the latest upstream release. It brings miscellaneous bug fixes from upstream.

I've also updated the kernel with recent security and bug fix patches - I'm in the process of bringing my "Squid Kernel" project back up to date. A new Squid Kernel release will probably come some time next week.

Those who want to try latest TWRP then you can get download link over here - twrp-osprey-3.1.1-r1.img
[Moto G 2015 Original Android Development] Az Biker:
Let's remember to keep the posts/comments On -Topic, and respectful.

Just like dealing with members who violate the rules in the threads, anyone experiencing issues via PM, can simply report the PM and allow Moderation Staff to address it. The rules apply for PMs as well.

Bottom line; Android Development threads are for development related comments/questions/troubleshooting/etc, period.

Off-topic opinions, debating, conversation, etc need to be conducted via PM, social media, G+, etc... NOT in the thread please.

Your cooperation is appreciated.
[Moto G 2015 Original Android Development] niftynick:
They do, I've tried them out and went back to Lineage 13 because all LOS14+ based osprey builds (RR, AICP...) also exhibit the 444 bug.

https://jira.lineageos.org/browse/BUGBASH-444
[Moto G 2015 Original Android Development] KrisM22:
Unfortunately that doesn't help us solve it... :(
[Moto G 2015 Original Android Development] niftynick:
Well, there's nothing else I can do to help, apart from testing each version and providing occasional logs, which I have already done. It is very easy for me to reproduce the bug, especially since it manifests itself on a clean install, I don't even have to bother with setting up gapps or a google account.

I find it just weird that such an annoying bug (especially the reboots it triggers if music streaming is interrupted by a phone call, which I believe is related to BT) has managed to persist in every build since CM14.
[Moto G 2015 Original Android Development] KrisM22:
Thanks - I just went back and read your comment on 444 - I noticed you were listening to music - I don't recall whether I was or not - were you using a particular player? I am flashing 7-13 and will stop there(rom+gapps only) and nandroid that and play with it and see if I can reproduce it. Thanks.

EDIT: I assume you rooted it to get logs? What root did you use?

EDIT2: nope, unable to replicate. I could sit there going in and out of wifi but no drop of BT. Once early on it dropped and I had to re-pair to get it back. This is a new router, the old one would drop wired connection occasionally (like a few times a day). Both tp-link 841. I can't help if I can't dependably get the result. Wish I could help.
[Moto G 2015 Original Android Development] rahul9999:
Thanks for the feedback :)
[Moto G 2015 Original Android Development] niftynick:
The music was playing from the stock music player and I did not use root (matlog permissions were granted via adb). I've uploaded two more logs, one showing BT disconnects on two different routers/SSIDs, and one showing a full system reboot after I attempt to end an incoming call via the "end call" button on the BT headset. Both include detailed instructions how to reproduce the bugs which work each and every time for me.
[Moto G 2015 Original Android Development] florincristea:
Phone model is lineage_osprey....?
[Moto G 2015 Original Android Development] rahul9999:
Yes it's being changed since latest nightly build :)
[Moto G 2015 Original Android Development] KrisM22:
Many thanks for the details on 444. I am guessing that the guest connection is on the same physical router? Also I noticed that no gapps this time... Okay, I will nandroid back to my rom w/gapps and see...
[Moto G 2015 Original Android Development] niftynick:
No, the Guest SSID is a Huawei B315s-22, an LTE wireless router, whereas Magrathea is on a TP-Link TL-WDR4310 for my VDSL landline, completely separate devices with different IP ranges/public IP's/locations in the house.

Like I said, I did a factory reset, clean-installed the build, installed matlog from an APK, enabled ADB debugging, granted log access rights to matlog and that's about it.
[Moto G 2015 Original Android Development] KrisM22:
Wonderful - thanks! working...

EDIT1: Can't get matlog to work - it pops up with a failed message after start recording. Just stuck on "recording" (did the long adb command). - Later! EDIT: it was the widget - if I do it manually it works.
[Moto G 2015 Original Android Development] KrisM22:
Bad news:

1) music on, BT on, walked out of wifi range, back a few steps and in settings/wifi clicked on canoe to connect, which it did, Repeat at least 3 times - no BT drop. log1a and b (split because too large for xda.)

2) music on, BT on, called myself via skype, answered with click on BT headset, talked to myself briefly, hang up with click on BT headset, music returned. Repeat. No BT problems or cutouts. No rom lockups. Everything seemed perfect. log2.

New new build with 7-13 LinOS and 7-13 nano gapps. only Matlog added. No root. I will nandroid it.

EDIT: I will look at your logs this evening. Later.
[Moto G 2015 Original Android Development] niftynick:
Well, damn. I can easily reproduce the bug on any nightly and any 14-based build and I'm clearly not the only one because this bug has been cropping up from time to time over the last few months, it's only quite specific so a large majority of users don't notice. Is it possible that the bug occurs on my specific radio firmware, since my osprey is the XT1541? In any case, do check out my logs and get back to me if there's anything else I can contribute.
[Moto G 2015 Original Android Development] KrisM22:
Preliminary: It happens if you are

precisely

in the location where settings/wifi can see the router, but NOT be able to connect to it

if forced

. For me this is a very narrow space. I would ask: why are you trying to force it, rather than waiting until rom connects automatically? Okay, back to logs...

2 things stand out to me in your logs (reduced to errors only). You get a lot of a2dp errors, so I am guessing that the headset you are using doesn't have a2dp capability. OR...

Also I see a lot of "proximity covered/un- " That shouldn't affect anything, but...