yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] GaneshAgasthya:
Guys does this custom ROM working good with Moto g3 dual SIM devices now ??? And is it stable
[Moto G 2015 Original Android Development] Subinsmani:
nope... stay on stock...
[Moto G 2015 Original Android Development] guest_2011:
I tried to open a ticket on Jira but it got rejected.
[Moto G 2015 Original Android Development] KrisM22:
why? same thing? don't need to open 2. Just add comment to mine. attach logs if you have any.

mine is at: https://jira.lineageos.org/projects...rby=created+DESC,+priority+DESC,+updated+DESC
[Moto G 2015 Original Android Development] IronTechmonkey:
Did they say why rejected? Did you act on what they suggested? What ticket #. If a ticket is rejected because it was filed as a regression instead of a bug then just re-file it as a bug. The weekly bug tracker is presently available in the "Project" category as "Weekly/nightly bug reporting (BUGBASH)"

In any event, at this point, if you are experiencing the same BT issue then it might be best to contribute to [MENTION=2945516]KrisM22[/MENTION]'s ticket for this issue so all the feedback from Osprey is in one ticket.

[EDIT] I type slow and have been ninja-ed by previous post. :)

[EDIT2] The line out was a (perhaps clumsy) way to defer, and intended to be bit humorous, but at your request lined back in. As you say, different words...
[Moto G 2015 Original Android Development] KrisM22:
:D

---------- Post added at 08:58 PM ---------- Previous post was at 08:51 PM ----------

you didn't have to do that! undo lineout please. All in good fun and different words might make sense and this is important.
[Moto G 2015 Original Android Development] guest_2011:
It was a few weeks back i don't remember rejection details. If i remember correctly i think because when i first switched to Lineage, one of the first builds, but not the very first one, there were no issues in the previous build (or maybe nobody reported). That's what i think the rejecting party meant. If i had experienced the same issue in the past and it was persistent or something then i could file. I'm overwhelmed with other things but i'll try to run Matlog and replicate. All i have to do is go out and let WiFi disconnect and connect to hotspots as i move. I'm listening to audio via BT connected to wifi. Flawless. As soon as wifi signal weakens and phone tries to connect to something else bt will start acting up.
[Moto G 2015 Original Android Development] KrisM22:
If you don't have time to get a log, just post a comment on mine saying how/procedure you get the error (like what you just said). If, later, you can get a log, that would be great, but live your life FIRST! :) I do!
[Moto G 2015 Original Android Development] guest_2011:
Is there a link for your comment? That Jira site gives me cancer ))))
[Moto G 2015 Original Android Development] KrisM22:
this should take you to bug 444

https://jira.lineageos.org/projects...rby=created+DESC,+priority+DESC,+updated+DESC

If you're not logged in, log in (top right), and then comment button at the bottom and type away. Thanks!

Access jira a few times and you'll be an old hand!
[Moto G 2015 Original Android Development] guest_2011:
Added a comment under log5. Thanks.
[Moto G 2015 Original Android Development] KrisM22:
Thanks! Only thing I would suggest is to go to your logon top right, choose profile, click on the pencil and change your name from user user to guest_2011.
[Moto G 2015 Original Android Development] guest_2011:
ha that's what i have for user name. thought it would show up. and my previous jira ticket was for GPS, not BT. told you the site gives me cancer.
[Moto G 2015 Original Android Development] KrisM22:
goes in "Full Name" most of us seem to use xda logon name.

Yeah, it can be scary at first but after you access it a few times it won't be scarry.

Thanks again!

---------- Post added at 10:32 PM ---------- Previous post was at 10:28 PM ----------

:D
[Moto G 2015 Original Android Development] Az Biker:
* * * Thread Cleaned * * *

A few quick reminders: asking for donations either in the thread, or via PM is STRICTLY prohibited and will get you banned, and comparing outside roms in another dev's thread is plain disrespectful.

IF this thread continues to be problematic (I've already cleaned it a few times), it may be closed to allow folks time to re-read the rules, and to remind themselves that this is a DEVELOPMENT thread.

Remember, report the trolls, don't engage them, and move on. Let the Moderation staff address the issue.

Let's keep the comments on development and within the rules.

Thanks for your cooperation.

Hopefully you folks got this ridiculousness out of your system and are ready to focus on the development of this Rom.

As previously mentioned in this thread, if a user is causing trouble or disrupting the thread, simply report them and leave it alone.

All the back and forth wiped out an entire page of this thread.
[Moto G 2015 Original Android Development] cutesammy1:
Hey, I just downloaded the latest nightly 20th March but I am unable to update it automatically. My phone goes in recovery but it doesn't update as it used to happen. I use TWRP and it stays on the home page. Earlier after applying update, the phone goes into recovery and start updating. Anyone facing same problem??
[Moto G 2015 Original Android Development] KrisM22:
Only thing I've heard recently was in post#4118 see if that helps...
[Moto G 2015 Original Android Development] cutesammy1:
Thanks for the help Kris but I am not getting any error. Actually after restarting, the update process doesn't start and It shows the main screen of TWRP.
[Moto G 2015 Original Android Development] umeshxda:
Update twrp recovery
[Moto G 2015 Original Android Development] cutesammy1:
I haven't rooted my phone yet. I thought it might break the OTA automatic and update system. Can I just update TWRP from their playstore app?
[Moto G 2015 Original Android Development] KrisM22:
I would be inclined to grab squid's latest, then use the playstore TWRP app to flash it.

root shouldn't affect update.
[Moto G 2015 Original Android Development] cutesammy1:
Sorry I don't know about squid superuser? Is this a new file?
[Moto G 2015 Original Android Development] KrisM22:
Squid's twrp

If you want root, grab the one from first post this thread or I use su 2.79
[Moto G 2015 Original Android Development] cutesammy1:
Thanks man for such a fast reply ? could you provide a file to root my phone? I will root it using current TWRP then update squid twrp using the app from playstore
[Moto G 2015 Original Android Development] KrisM22:
I don't have link to 2.79 - later - so use one in link in 1st post this thread
[Moto G 2015 Original Android Development] cutesammy1:
It worked bro!!! I downloaded supersu from the first page and rooted my phone. Afterwards, I downloaded TWRP app from playstore and updated recovery. The update went smoothly :)
[Moto G 2015 Original Android Development] KrisM22:
Excellent! but I was typing up the info so here it is...

flashing to root in TWRP:

from the 1st post - addonsu-arm-signed.zip

https://download.lineageos.org/extras

grab the top one. You have to turn on root in Developer Options.

SuperSU 2.79 zip - SuperSU-v2.79-201612051815.zip

http://www.supersu.com/download

go down a few inches to "zip" and grab it.

This is system wide and you do not have to turn it on in Dev Options though there is an option there for using adb.

I used to use the first one but now use the second one.

With the second one, I wipe, flash rom, flash gapps, flash supersu, boot, and a few seconds into it if you're watching VERY closely you will see it skip a beat and reboot. This is normal. Then wait 3 min for initial settings.

This

OLD

link explains why the first one

USED

to be necessary. Now either is fine though SuperSU is the way we did it in the past and is more broad in scope.

http://www.theandroidsoul.com/root-lineage-os-su-addon-zip-download/

[MENTION=7725765]adityak1303[/MENTION] turned me on to SuperSU 2.79 and may know more about the differences.

---------- Post added at 05:10 PM ---------- Previous post was at 04:53 PM ----------

second topic - I will do update this time just to experience it, but after you download the update and click install and it bounces you to TWRP, do you have to do anything, or is it automatic? Is it clean or dirty install?

never mind, I backed up and restored back a week and did one - it is a dirty flash - tell update to download, then click Install - it preps for update and then boots to an install screen in TWRP and automatically installs it, then reboots - takes about 3 min, All apps are intact.

---------- Post added at 05:23 PM ---------- Previous post was at 05:10 PM ----------

Thanks for this!
[Moto G 2015 Original Android Development] shravan27:
Hey man do u know how to disable the notification of “Your device is HD capable ”??
[Moto G 2015 Original Android Development] jackk11111:
From a few versions I can not copy internal memory files to SD. Me by 0 byte
[Moto G 2015 Original Android Development] Mama Luigi:
[MENTION=2945516]KrisM22[/MENTION] I managed to get a log this morning. I uploaded it to Jira ticket #444 with the following text:
[Moto G 2015 Original Android Development] KrisM22:
Thanks! Yeah, I looked at the log and again right after SOC reset. So that's 3 or 4 of the same type so that should help Alberto get a fix on one of the things that's doing it! Thanks!

---------- Post added at 11:02 AM ---------- Previous post was at 11:01 AM ----------

I generally use USB cable to PC to copy files to/from internal and SD.

What are you using?

---------- Post added at 11:04 AM ---------- Previous post was at 11:02 AM ----------

I believe it is impossible but folks here from India using Jio could tell you better. It is an indication that its VoLTE is active.
[Moto G 2015 Original Android Development] jackk11111:
External memory inside the external memory does not make sense to use the USB cable. I do it by phone. but it does not work

Inviato dal mio MotoG3 utilizzando Tapatalk
[Moto G 2015 Original Android Development] KrisM22:
What app are you using? What error message do you get?
[Moto G 2015 Original Android Development] jackk11111:
With all file managers. I have no errors but after the copy are 0 bytes then damaged

Inviato dal mio MotoG3 utilizzando Tapatalk
[Moto G 2015 Original Android Development] guest_2011:
I think i'm going back to stock. This bug seems more recent. Whenever i record video the thumbnail appears blank in the gallery. When i try to move video to pc i get an error in pc "the library, drive, or media pool is empty". I can play video in phone. I can see video files in phone storage folder. I can copy picture files to pc but not video.
[Moto G 2015 Original Android Development] KrisM22:
I just took a 5 sec video with stock camera, viewed it in stock gallery and copied it to PC and viewed it there. Maybe if it was a big video and you have a 1GB phone... Dunno. All I can say is "whatever". Thanks for trying!!! I understand you are time limited.
[Moto G 2015 Original Android Development] guest_2011:
2gb phone. 19mb video. i needed to do time lapse. used snap cam app.
[Moto G 2015 Original Android Development] KrisM22:
I still have no sense of what you are doing other than in very general terms. "It's broken" doesn't help.

---------- Post added at 12:11 PM ---------- Previous post was at 12:08 PM ----------

I looked in playstore and I find "snap camera hdr trial", and "snap camera hdr $1.99" . Is it one of those?
[Moto G 2015 Original Android Development] jackk11111:
Sorry my bad english. The copy it's ok without errors but if the file is example 4mb insteas the copy is 0mb, then damaged
[Moto G 2015 Original Android Development] KrisM22:
English is fine - just not enough specifics! :)

specifically what app are you using?

---------- Post added at 01:39 PM ---------- Previous post was at 01:32 PM ----------

If I use stock "files"

choose MotoG3

long press on the file I want to copy.

tap 3 dots upper right.

choose copy to...

choose sdcard1

tap copy bottom right

test result:

tap 3 bars top left

tap sdcard1

it's there and correct.
[Moto G 2015 Original Android Development] jackk11111:
That's exactly what I do. But the copy is 0 bytes !!!! For example if it is an image, copy does not open because it is empty. Apk the same.
[Moto G 2015 Original Android Development] KrisM22:
strano

strange

works fine for me

what is name of rom module?

what is name of gapps module?

Is is rooted? How?

grazie

thanks
[Moto G 2015 Original Android Development] jackk11111:
For now I found a solution. I must unmount SD and remount. But this system does not last long.

Inviato dal mio MotoG3 utilizzando Tapatalk
[Moto G 2015 Original Android Development] KrisM22:
grazi!!!!!!!!

so SD card is dismounting.

I would suggest: connect via USB and copy everything on SD card to PC.

Then, in phone, format the SD card as external.

Then copy the stuff back from the PC to the SD card.

This should fix it.

EDIT: if that doesn't help, remove and re-insert SD card.

EDIT2: if that doesn't help, get a new SD card (not sandisk) and format it in phone and copy stuff from PC to it.

EDIT if that doesn't help, let me know...
[Moto G 2015 Original Android Development] jackk11111:
Thank you very much for the availability ;)

Inviato dal mio MotoG3 utilizzando Tapatalk
[Moto G 2015 Original Android Development] KrisM22:
[MENTION=2810725]Mama Luigi[/MENTION] thanks for second log, and comment!!! again, after SOC status reset. I like consistency!!! This looks like a VERY useful log!!!!!!!

---------- Post added at 02:40 PM ---------- Previous post was at 02:36 PM ----------

You're very welcome - hopefully we can get this fixed!
[Moto G 2015 Original Android Development] mmk88:
Low LTE signal on XT1540

I am getting noticeably weaker signal on T-Mobile LTE on Lineage OS. I could get full bars under stock rom but no bar at all under Lineage, but the signal strengths are the same, around -105 dBm. The cellular data is working fine and I could make and receive calls, so I am guessing it just an icon bug. The model is XT1540, I am using the latest build 14.1-20170420. Does anyone else have this issue?
[Moto G 2015 Original Android Development] KrisM22:
Same APN settings?
[Moto G 2015 Original Android Development] mmk88:
Yes, I am using the default APN settings that comes with the Lineage OS. Looks like they are the same as T-Mobile suggests here: https://support.t-mobile.com/docs/DOC-28006
[Moto G 2015 Original Android Development] IronTechmonkey:
Osprey XT1540 (1GB), clean flash of April 20th Osprey build with April 20 OpenGapps Pico and LOS SU. Exploring 2 potential issues and trying to turn observations into a viable bug report, particularly in re RAM and camera on 1GB device.

1) RAM and general performance on 1GB device.

2) Device freeze when restarting.

3) (Incidental) Google Play services FC, other stuff.

1) Performance, particularly RAM, when camera or other apps are used (on 1GB Osprey models?).

After flashing ROM, Gapps, LOS SU and letting the device settle down, with no other apps installed, merely opening the camera causes a few dozen apps/services to be killed. Apps being killed may be relatively normal but this is extreme. Once any (even reasonable) load of user apps is installed then, any time the camera is opened (even without taking a picture) more things are killed including apps service that need to run continuously (eg VPN client, among others). Similar things occur when some other apps are run. For comparison I tested this once with SuperSU and once with squid2's Osprey kernel (or course reverting back to clean ROM after those tests) which had no impact either way. I've got a log of the first test in clean ROM before apps were installed and am trying to add enough good information to make a viable Jira ticket for this.

2) Device freezes upon restart, seemingly at the point where the SD card is being unmounted, although this might relate to the device having no SIM card. This occurs a significant percentage of the time (perhaps >50%) when the device is restarted however I have been unable to log it yet.

3) Incidental to previous testing: at one point there was a Google Services FC which might be related to other reports of Google Play services FCs. For what this is worth Google did recently update their Play Store app and interface, and it is not uncommon for there to be Play services crashes, especially if you are installing apps at the time like I was. Just worth keeping an eye on.

[MENTION=6073162]Komapatient[/MENTION]: FYI: In re Live display: On Peregrine, after running the April 20 build for a few days, the night color did not invoke yesterday until I toggled Airplane mode on/off after which the night color was invoked. Osprey has been fine through the same period in re Live Display in April 20 build, and I don’t know what precipitated the need to toggle AP mode on Peregrine.

Also, thanks [MENTION=2945516]KrisM22[/MENTION] and [MENTION=2810725]Mama Luigi[/MENTION] for kicking off and filling in that BT ticket (I saw the new notes during some Jira activity stream watching:)).
[Moto G 2015 Original Android Development] KrisM22:
I ask because I don't know - "merely opening the camera causes a few dozen apps/services to be killed" how do you see this? Thanks

---------- Post added at 04:46 PM ---------- Previous post was at 04:26 PM ----------

I compared between stock and 4-20

Readings seemed slightly weaker (higher minus numbers) and the amount of the triangle that was white seemed slightly reduced on LinOS.

I believe it is the same radio software in each case.

Don't know how you'd file a bug on this - you'd need radio logs from both and I have no idea whether the devs would accept it. You could always try...

Edit at that very low signal strength (-105) there may be anomalies in the display. I would expect it to show nothing.
[Moto G 2015 Original Android Development] IronTechmonkey:
From lines in the logs that go something like this: "ActivityManager(XXX): Killing YYYY:PACKAGE_NAME_OF_THE_APP/ZZZZ", which I was reminded about and quote from this comment https://jira.lineageos.org/browse/B...issuetabpanels:comment-tabpanel#comment-13171.

The app killing is a natural thing which may occur more than we realize, and most apps/services bounce back however, same test in Peregrine had only 1 item killed (easily recoverable Google service) which is a stark contrast. The fact that this also occurs when other apps are run on Osprey but not Peregrine has taken me away from considering it a camera specific issue (even though the camera may be heavy lifting for 1GB), and other things take me away from thinking it is purely a RAM issue although the RAM is a ceiling.

IMO Osprey hardware is poorly matched to and wants more than 1GB RAM, but same Osprey on CM12.1 and Peregrine (also with 1GB) on LOS14.1 have no such problems (nor does the Moto camera on same devices) so I have hope for general performance improvement if not specifically the camera.
[Moto G 2015 Original Android Development] KrisM22:
thanks.

The Moto G 4G has a 5MP camera, while the Moto G3(2015) has 13MP plus auto HDR. The second will need 3 times the space, per snapped image piece, Mult by number of images in a panorama. Mult by 70% for Peregrine and 50% for Osprey. I suppose one could say they shouldn't have sold the 1GB version (I had one for a week before I realized), but I suspect a ton of Osprey 1GB owners are oblivious.

In mine it says 160x120 for 200 frames. Nothing was killed.
[Moto G 2015 Original Android Development] IronTechmonkey:
I'm familiar with those specifications (which were incorporated into my assessment) and the point of what I was reporting is that in spite of only having 1GB and in spite of the LOS camera requirements for Osprey's hardware vs Peregrine's hardware:

- Other apps (besides native LOS camera) which would have similar demands on both devices kill apps rather massively in LOS 14.1 Osprey but not in LOS 14.1 Peregrine.

- LOS 14.1 Osprey 1GB has this problem while CM12.1 does not, nor do other 1GB devices (Peregrine on CM12.1 or LOS14.1 & Otus on CM12.1).

- Other cameras do not have the same problem in LOS 14.1 Osprey.

Ergo, not just a camera issue and not just a RAM limitation, and I'd be interested in reports from 1GB Osprey devices which have experienced similar performance issues apart from the native LOS camera.
[Moto G 2015 Original Android Development] KrisM22:
I grabbed moto camera 6.0.43.10 and did a panorama - yes larger pic, but only 110degrees vs 270 for the stock camera.
[Moto G 2015 Original Android Development] guest_2011:
yes. it started when i updated lineage. past 2 builds. tried downgrading snap cam. same thing. i can't copy/move video files to usb or pc from internal or sd storage. also two video files created with same name. one normal size, another one is 0. no problems in other phones running stock mm.
[Moto G 2015 Original Android Development] KrisM22:
I'm obviously not hearing correctly - I grabbed the trial one, put phone in airplane mode as it requested, took a short video, played the video in gallery via fx player, plugged usb and copied it to PC and played it there. No problems. What am I doing wrong?
[Moto G 2015 Original Android Development] guest_2011:
i don't know. what lineage build are you on?
[Moto G 2015 Original Android Development] KrisM22:
4-20, gapps nano arm 4-20

edit I was using internal mem - were you using sd card? Maybe time to copy contents off sd card and re-format it?
[Moto G 2015 Original Android Development] guest_2011:
i just reformatted sd card. no difference. same happens when try to copy video from internal.
[Moto G 2015 Original Android Development] IronTechmonkey:
Yep, and along those lines Moto camera panorama only goes to 180, so we've got a Ferrari (Osprey) with little room in the trunk (1GB ram) and a gigantic suitcase (LOS Camera)... but it is my belief that there is some available underutilized space somewhere in this Ferrari's chassis that might allow us to, dare I say, store more junk in the trunk. :)

That being said. I'm really trying to get this issue away from the camera and toward general performance, which my last round of tests seems to indicate.
[Moto G 2015 Original Android Development] KrisM22:
So what's the difference between us? Some setting in camera?

---------- Post added at 06:43 PM ---------- Previous post was at 06:39 PM ----------

The only thing I changed in settings was photo picture size to 9.5M. Nothing else. Maybe clear apps/data?
[Moto G 2015 Original Android Development] guest_2011:
same settings as usual for me. same as i use every day that worked in lineage until the last 2 updates. definitely since the last one.
[Moto G 2015 Original Android Development] KrisM22:
maybe clear apps/data?
[Moto G 2015 Original Android Development] guest_2011:
cleared, reinstalled, downgraded. same thing.
[Moto G 2015 Original Android Development] KrisM22:
Start a log, take a short 5 sec video, stop log, check to make sure that video has problems, check to make sure your email isn't in the log, attach log here. I'll see if I see anything.
[Moto G 2015 Original Android Development] guest_2011:
i'll try. thanks.
[Moto G 2015 Original Android Development] IronTechmonkey:
Live Display not invoking night mode when set to Auto.

The (non device specific) issue of Live Display not invoking night mode when set to Auto has occurred again on my Peregrine tonight. For those experiencing this issue and curious about the details they are in this XDA post: https://xdaforums.com/showpost.php?p=72016970&postcount=827 and in this Jira: ticket: https://jira.lineageos.org/browse/BUGBASH-226.The precursor to which I refer in the XDA post was seen in both Osprey and Peregrine.
[Moto G 2015 Original Android Development] guest_2011:
was able to "fix" it. storage access suddenly became a problem for video. photos and other files no problem. as of last or previous lineage update. may not even be related to lineage, i have no idea. just unusual for the app to work and the suddenly can't move video. coincidentally only thing that changed is lineage itself.
[Moto G 2015 Original Android Development] KrisM22:
So it works now?