yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] IronTechmonkey:
In addition to these previously reported bugs (https://xdaforums.com/showpost.php?p=72480331&postcount=4763), here are a few notes about other possible bugs for which official reports have not been submitted, as well as permissions for the new browser.

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

Quick Tiles:

When dragging Quick Tiles (QT) up into the active group, especially when dragging from the bottom of the inactive group, the upward scroll is slow and the QT is sometimes released. There is still a sweet spot where the scroll is reasonably fast and the drag/lock on the QT persists but it seems harder to hit than before. This might be just a matter of user adjusting to changes but...

... Also, there is an odd thing where sometimes the border between the blue/green tint which defines the inactive QTs section and the dark gray tint which defines the active QTs section moves up and down along with the dragging of a QT. Attached screenshots show this shading border in 2 stages as it follows a QT that is being dragged up. This does not occur when the QT is dragged up in one motion but it can be induced by dragging the QT up into the active section then down then up again. There may be a relationship between this moving shading and the subdivision (faint line) in the middle of the inactive QT section but ATM Iâ€™m seeing this as an inconsistency in the animations and shading more than a feature. If itâ€™s a feature IDK itâ€™s purpose. Also, the presence of 3rd party app QTs may be a factor.

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

Camera:

Mentioned before but just keeping it on the list, many Scene-Modes missing from the Scene Mode section invoked by the icon at the upper right of the camera tool bar. If I cared about them being missing I might report this but there are more important things to test.

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

Permissions:

- The new Browser has fewer permissions than the previous one. Nothing for camera or microphone, and also the location permission is now disabled by default and no longer warns about basic device functions being disabled if it is toggled on/off.

- On devices that have a many apps restored or reinstalled after flash (particularly older apps) a review of all app permissions may find some interesting and totally unnecessary permissions, which we can control. Anyone interested in this can explorer the categories in Settings > Apps > gear button > App permissions.
[Moto G 2015 Original Android Development] KrisM22:
a) here's a couple from mine - didn't notice anything though slid it up and down many times...

b) camera: yeah, no-one seems to have said anything about it. Maybe if they want those toys they're already using some other camera app - there are tons out there...

c) interesting. I looked in there - I use about 30 apps installed via TBPro, but saw nothing that seemed untoward in there... What kinds of things are you noticing?
[Moto G 2015 Original Android Development] IronTechmonkey:
Poweramp (music player) being given access to Phone for no apparent reason (assigning ring tone?) and Weekender app (NYC MTA status) being given un-needed location access are 2 that stand out, and there are others that I'm not recalling ATM.

In terms of process (as opposed to security) it has been helpful to review all app permissions by category for a few reasons:

- To manually grant permissions for apps that will need them, which avoids the sometimes disruptive requests for permissions on the fly.

- A few apps, such as the Google search app, which have not always properly requested permissions when restored via TiBU

- Just good to know what permissions are being requested by which apps.
[Moto G 2015 Original Android Development] KrisM22:
It is true that some apps have pretty outlandish permission requests.
[Moto G 2015 Original Android Development] IronTechmonkey:
D'oh! I forgot to include something in previous bug reporting (although I did mention it in passing some weeks ago): Device freeze upon restart, seemingly at or immediately after the point when External SD card is being un-mounted. This does not occur when squid2's Osprey kernel is installed (but please note that other reporting has been done from stock LOS Osprey Kernel) and the minfree settings do not seem to be a factor as this occurs with default or modified minfree settings. Although I've reproduced this in clean flash before installing apps I've not had a chance to reproduce it in that state while logging across the reboot, and also testing with different external SD card (as opposed to the 64GB, half full card I normally use).
[Moto G 2015 Original Android Development] KrisM22:
At what point are you talking about? I have noticed a freeze sometimes when I use (advanced restart) power button / restart / recovery - it will start, then lock. It means I have to hard boot to recovery (powerbutton&voldn). This seems to happen after I have changed something - darned if I can remember what - takes a few reboots to "clear" itself , then it's fine. I ignore it because I assume all things involving software and hardware have temporary quirks.
[Moto G 2015 Original Android Development] IronTechmonkey:
"....seemingly at or immediately after the point when External SD card is being un-mounted", at which point a brief flash of an SD card status bar icon is the last visual indicator (other than the animated blue spinner) before the power down part of a restart, and at which point the device will freeze with the spinner (now stationary) still on screen over the home-screen, and with the device not responsive to ADB via USB (requiring power/vol button restart). Occurs frequently at this point of any type of restart but not every time, and rarely in an immediately subsequent reboot (when I suspect the post boot scanning is still active).

I'm tempted to think these are related issues but cant make a good case for that. If they are related, a reason that I may see it more often is that; after flashing and configuring both Osprey and Peregrine I sometimes have "reboot races" which, not as frivolous as the name might imply, are to compare the duration of and processor activity during the post boot media scans. Osprey wins those "races" through the reboot itself but takes longer through the media scan because it has larger SD containing more multimedia.... unless it stalls at the starting gate. Never occurs with squid2 kernel installed, with enough passes having been done to be fairly certain of that.
[Moto G 2015 Original Android Development] Komapatient:
I followed the build guide for nicki on the LinOS wiki.

All repos were synced and that one patch was applied through repopick which adds/deletes/modifies the files in question.

But now the status is merged, so it will be in the next official builds.
[Moto G 2015 Original Android Development] JithuKSelwyn:
Is this ROM support VoLTE on both sim cards..
[Moto G 2015 Original Android Development] Ouiloui:
I've been playing with the LMK values in Kernel Adiutor, by curiosity (after the discussion initiated by IronTechMonkey). I just wanted to report a couple of things.

I've tried the medium profile values, but they don't seem to correspond to the values reported in a previous post.

I have instead: 57 - 76 - 95 - 114 - 133 - 172

Anyway, after a couple of days, I can see some mild improvement on the battery life, and no significant change on the phone overall, except one (quite annoying, I must say!): the alarm does not work at the preset time (it only works when I open my phone). I will do some more testing, but I just wanted to report that if those who have tried experienced the same problem with the alarm clock.
[Moto G 2015 Original Android Development] KrisM22:
It appears that google play store took magisk manager off.
[Moto G 2015 Original Android Development] GoelPlz:
Anyone else having this bug in the nav bar?
[Moto G 2015 Original Android Development] batboy29011:
YES!

---------- Post added at 05:40 PM ---------- Previous post was at 05:38 PM ----------

First question. How did you get night mode to work ?
[Moto G 2015 Original Android Development] eemgee:
Settings>display>livedisplay.

I can't change the color temperature.
[Moto G 2015 Original Android Development] ranaxda200:
At first enable system ui tuner >Download night mode enabler from play store and enable it. Then>colour and appearance >night mode >enable adjust tint and turn on automatically. Profit
[Moto G 2015 Original Android Development] kaustubh_lipare:
Waiting for Volte support in custom roms.. Switching to Stock again :(
[Moto G 2015 Original Android Development] WaxysDargle:
VOLTE is not coming to custom ROMs anytime soon, if ever. please stay with stock and stop plaguing the forums with irrational wants. comments like "Switching to Stock again" apply no value to the project and will only discourage the developer from wanting to help the rest of us.
[Moto G 2015 Original Android Development] kaustubh_lipare:
[MENTION=4746211]WaxysDargle[/MENTION]

Sir, Sorry for the post but my intention was neither to discourage anybody nor its an irrational want. I am always here to help our fellow developers for testing new features brought by them..... :):):)

.. I know developers has to do a lot of hard work for bringing such features in custom ROM to us. After lot of search and disappointment on support for VOLTE in custom rom i posted the same. Hope developers can understand it.
[Moto G 2015 Original Android Development] valkaizer2594:
cool u will be the guy from meme " still waiting for ... "
[Moto G 2015 Original Android Development] ranaxda200:
Sure you'll be be getting the VoLTE support in the next build. Thanks for pointing out the 'feature' to the developers.
[Moto G 2015 Original Android Development] tzzeri:
The other person can't here me with WhatsApp calls. Anyone else having this issue?
[Moto G 2015 Original Android Development] WaxysDargle:
if you want VOLTE in a custom ROM you could do some research and help the developer understand how it might work.

it is very irresponsible for you to be rooting and flashing ROMs without having read countless pages of information already available to you. you should keep stock and restrain from doing anything root-related until you have read most of the threads in this forum. the information is already there. before you ask any more questions please check to see if anyone else has already asked it. 99% of the time your answer is already out there.

no hard feelings, but there is an etiquette to posting on these forums, with good reason. let's work to keep them concise and efficient.
[Moto G 2015 Original Android Development] kaustubh_lipare:
Once again Sorry Sir... But you misunderstood something over here...Again I am trying to clarify as my intention was different for posting. I am not asking for ETA. Might be problem with my english. Not able to interpret properly. Let's keep this out of forums as told by u.. .. i Will personal message u later...Thanks for the help...
[Moto G 2015 Original Android Development] kailasraj97:
after installing arise sound system...cannot play music...

any help?
[Moto G 2015 Original Android Development] ranaxda200:
What arise version? Did you flash ROM before installing arise?
[Moto G 2015 Original Android Development] kailasraj97:
ARISE+Sound+Systems+Deuteronomy+1.6+++Extras

yes..clean flash+gapps+arise
[Moto G 2015 Original Android Development] ranaxda200:
Can you please pm me. I'll be there to guide you if any problem arises.
[Moto G 2015 Original Android Development] sensi277:
Does this ROM support Moto Display/Actions (or Ambient Display/Double-tap Power for camera)?
[Moto G 2015 Original Android Development] Majid2000:
Doesn't support Moto display. But it has ambient and double tap power for camera features
[Moto G 2015 Original Android Development] sensi277:
How does Active Display compare to Moto Display?

Edit: Also, how is the general stability on this ROM? If it's not 99% stable (it needs to not crash like once a week) then I'll just use CM13.
[Moto G 2015 Original Android Development] Majid2000:
U can only see notifications in ambient display but can't open them .. When u tap the ambient screen, the phone turns on.
[Moto G 2015 Original Android Development] Bastlwastl2010:
This is no wonder,.....

Is is a software to skip googles security...

The same with all the selinux things 2 years ago
[Moto G 2015 Original Android Development] IronTechmonkey:
Interesting, those values are much higher then even the Kernel Adiutor very aggressive profile (on both of the devices that I'm testing). A few questions:

- What Osprey model # is this on, and is it is it 2GB or 1 GB?

- Is Adaptive Low Memory Killer enabled or disabled?

- Have you enabled "On oot" in the Kernel Adiutor Low Memory Killer configuration panel?

- Can you confirm clean flash, and particularly that this is on the otherwise unmodified default LOS Osprey kernel?

- Which LOS weekly build is this on?
[Moto G 2015 Original Android Development] rahul9999:
New nightly is up for osprey - https://lineageos.mirror.karneval.cz/full/osprey/20170601/lineage-14.1-20170601-nightly-osprey-signed.zip

Official changelog - https://www.cmxlog.com/14.1/osprey/#
[Moto G 2015 Original Android Development] KrisM22:
There's a lot of stuff showing up on jira but I'm not having any probs with 6-1 - knock on particle board...
[Moto G 2015 Original Android Development] Ouiloui:
Sorry, I should have mentioned that in the first place. This is an osprey 2GB (I forgot how to obtain the model number, sorry), Adaptive MLK was enabled (I've disabled it today to see if there is any difference), I have enable "on boot". No clean flash, but this is the classical LOS kernel, build version of May 25, which I am about to abandon for today's build.
[Moto G 2015 Original Android Development] IronTechmonkey:
That is indeed a significant detail because the 2GB devices seem to not be affected by the app killing, which stands to reason. No worries about model # as it is the amount of RAM that matters most in this regard. You may determine model # from a sticker on the back of the device under the removable cover and or by going to the "Bar Codes" option in bootloader.
[Moto G 2015 Original Android Development] KrisM22:
Did you ever solve these 2?
[Moto G 2015 Original Android Development] Ray Krebs:
Hmm, i installed the latest nightly, but now HEVC 720p videos shows only a black screen and the sound is running. With the nightly bevor i had no problems.
[Moto G 2015 Original Android Development] rahul9999:
No such issue with me.. can you tell me what you have done while flashing ? have you dirty flashed or clean flashed ?
[Moto G 2015 Original Android Development] Ray Krebs:
This time and the time before i did a dirty flash.
[Moto G 2015 Original Android Development] rahul9999:
ok.. i recommend you to clean flash latest build with latest opengapps & check once..
[Moto G 2015 Original Android Development] KrisM22:
clean flash means wipe advanced: (dalvik/ART, data, system, cache) Do not wipe internal storage or sdcard.
[Moto G 2015 Original Android Development] Sachin ET:
Nop........still continuing with the problem........today i went to an authorised Motorola service centre, and they told me i need to replace the touch+display module........but i can't believe them they neither did a detailed examination nor asked me a detailed explanation about the problem (Don't even gave me time to speak in detail)........i can't consider it as display or touch problem........ my observations points me to battery damage........but i don't know how battery failure may lead to" Ghost Touch" during calls........am totally confused........anyway am not gonna replace the display.........i am surprised that no one reported a similar problem, sounds like I'm the only Moto G3 user with this wierd problem.

glad to know that you didn't forget it

Thankyou
[Moto G 2015 Original Android Development] Ray Krebs:
Yes, i know, i always flash then the latest gapps.
[Moto G 2015 Original Android Development] KrisM22:
:)

So might that more likely mean a hardware problem?

Yeah I can see why they might say led/digitizer for the ghosting - they would use the shotgun approach - replace phone and see if it fixes it.

Hope you figure it out.

EDIT: so I suppose you could get a led/digitizer and a battery on ebay and replace them both...
[Moto G 2015 Original Android Development] Axaion:
So, after not having been able to get MMS to work .. for.. months i guess ill ask here, anyone else having this issue?

Whats working: anything but MMS, Data works, 4G LTE works, SMS works, Phone works.

Carrier: 3.dk

I used their settings, and it does connect to LTE, but regardless MMS just fails to send or recieve, which is.. super annoying really

Its the 2GB model, and ive done several clean installs too

heres a logcat filtered to "mms"

pastebin messes with formatting, and xda says message too long, so sorry for having to download the .txt

https://www.dropbox.com/s/nkqo2ivfbg61760/2017-06-02-20-55-13.txt?dl=0

Fixed; had to delete all apn's, remake them, then delete them again, and then make the one for my carrier.

Weird.
[Moto G 2015 Original Android Development] Ray Krebs:
Hi, so i did now a clean install with the latest nightly and the latest gapps, but the problem with HEVC 720p videos still exists. I get only a black screen with sound. h264 videos works well. 1GB Device
[Moto G 2015 Original Android Development] KrisM22:
give me a link to the video and I'll try it later.
[Moto G 2015 Original Android Development] Ray Krebs:
Okay, but i must search again for the link.
[Moto G 2015 Original Android Development] KrisM22:
Any one will do. Or is it jus one that fails?

What app do you view it with?
[Moto G 2015 Original Android Development] Ray Krebs:
No, all the videos which i downloaded for testing will not played well. And of course they are only 720p. If i did't found the link again, i will put the files in my OneDrive Box and post this link.
[Moto G 2015 Original Android Development] rafaelbarreto22:
I can't play videos in 1080p in .mkv format but in .mp4 format if I can play them without any problem

01/06 version and clean flash
[Moto G 2015 Original Android Development] KrisM22:
osprey is 720
[Moto G 2015 Original Android Development] rafaelbarreto22:
If I know but videos are reproduced in 1080p but only in .mp4 but in .mkv it does not play
[Moto G 2015 Original Android Development] KrisM22:
a) use a different player?

b) did it work in stock?

c) did it work in a previous LinOS release?
[Moto G 2015 Original Android Development] rafaelbarreto22:
a) Yes, vlc media player and in stock player neither play

b) Yes, but only in vlc

c) It is the first time that I try to reproduce this type of video in LinOS
[Moto G 2015 Original Android Development] KrisM22:
vlc player has problems with Nougat. Use another player.
[Moto G 2015 Original Android Development] Ray Krebs:
Hi, so i am back. Here is the link to the demo videos.

http://www.libde265.org/downloads-videos/

- Tears of Steel -> 1720px × 720px "tos-1720x720-cfg01.mkv"

- Spreed – The Meeting -> 640px × 360px "SpreedMovie-640x360.mkv"

- Big Buck Bunny -> 1280px × 720px "bbb-1280x720-cfg02.mkv"

All of these videos works well [MENTION=2344764]nightly[/MENTION] 20170525
[Moto G 2015 Original Android Development] Jithin91:
June 1st build eating so much battery. Usually i charge my battery to 100% and goto sleep. In morning the charge would be 96% or 95%. For last two days it went down to 75 to 70%.

also phone freezes at times.
[Moto G 2015 Original Android Development] KrisM22:
no joy on 6-1. tried 5 different players and 2 videos. most tried to play them but tons of digital video breakup. If you have a LinOS release that it works on wait until Monday and file a regression on jira.

EDIT: I tried this on 5-25 and I see no difference. This phone/rom simply is no where near fast enough.

EDIT2 on June 4: This is a player problem - MXPlayer works just fine. Thanks [MENTION=3784616]shadowchaos[/MENTION] .
[Moto G 2015 Original Android Development] shadowchaos:
I'm 1GB model on Tesla-osprey-7.1.1 using MXPlayer 1.8.21 which again originally supports AC3/DTS due to patent expired .

I'm done a more test :

Note that all videos can be turn on HW+ in MXPlayer ,so the G3 plays much more power.

tos-1720x720-cfg01.mkv 1049Kbps 24 fps well played

tos-4096x1720-tiles.mkv 2658Kbps 24 fps out of synchronizing ,not watchable

spreed-1080p.mkv 898Kbps 30 fps well played

bbb-1280x720-cfg02.mkv 1666Kbps 60 fps well played

bbb-1280x720-cfg06.mkv 1349Kbps 60 fps well played

bbb-1920x1080-cfg02.mkv 2549Kbps 60 fps out of synchronizing ,not watchable

bbb-1920x1080-cfg06.mkv 2012Kbps 60 fps out of synchronizing ,not watchable

elephants-dream-1080-cfg02.mkv 1767Kbps 24 fps loses audio when its bite rate boosts to 11000Kbps ~ 14500Kbps at time 2:11 - 2:17 watchable i'd say

sintel-1080-cfg02.mkv 1368Kbps 24 fps well played

All videos are encoded by HEVC(H.265) .

It seems no problem playing 720p as the hardware spec to HW of HEVC up to 720p ,and for those 1080p most likely playing well if fps at 24 or 30 ,but not for 60 fps.

And if the video is encoded with H.264 ,I think there should be no problem at all up to 1080p as the hardware spec supported.(but no chance for 4k/2160p )

And one more thing ,these videos are talking about is all with bit depth of 8 bit ,if the bit depth is 10 bit ,it can be only decoding with software regardless it encoded with h264 or h265 .

I didn't test this situation much .All I can recall is John.Wick.2014.720p.10bit.HDR.BluRay.x265.HEVC that can be played well with option "speed up tricks" on .(didn't find video quality reduced)
[Moto G 2015 Original Android Development] KrisM22:
Thanks! Yep, you're right! 6-1 LinOS rom, 1.8.21 MXPlayer.
[Moto G 2015 Original Android Development] IronTechmonkey:
That is not a universal issue (I've been running the June 1 build for 2 days with no such problems) and you would have to investigate further to establish that it is an issue with the ROM. I'm not saying it cannot be, but evidence establishing cause and effect would be required to make the case. Such things can occur due to problematic apps or issues between Gapps and ROM (particularly with location services and GPS). To determine the cause of the battery drain try installing Better Battery Stats; https://xdaforums.com/showthread.php?t=1179809 and look for processes that are consuming battery and wakelocks. Note the description in that thread about how to do a good test over a sustained period of time.
[Moto G 2015 Original Android Development] KrisM22:
Mine's been going down to 70 in less than an hour, but I've been playing PokeGo while riding the bus. :D