yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] KrisM22:
Bye.
[Moto G 2015 Original Android Development] IronTechmonkey:
Also, [MENTION=4177913]marvasten[/MENTION], if you have questions about flashing or bug reporting don't hesitate to ask.
[Moto G 2015 Original Android Development] Subinsmani:
I dont know what m doing,,,,

Now i installed stock rom,,,,:D

my mind gone crazy,,,, :laugh:
[Moto G 2015 Original Android Development] IronTechmonkey:
LOL. A new medical condition, "ROM Shock". "4 out of 5 doctors agree, excessive ROM flashing can jumble the mind".

Sorry for OT. Back to breaking software.
[Moto G 2015 Original Android Development] Subinsmani:
He he seriously bro, on stock rom with same twrp saftynet pass,,,,

But after flash latest lineage os it break saftynet,,,,

Dnt know what is going on,,,,

On February i use payment app it working it only stop working if we root, that is why i didn't root rom since i instlled lineage rom...

But now it show ur device is rooted and all then that app close,,,, for payment i have installed stock rom,,,, :(
[Moto G 2015 Original Android Development] IronTechmonkey:
Sigh in re "bro", but I say this with a smile: Would you directly address unfamiliar members of your parents' or grandparent's generation as bro? :)

As to Safetynet, I don't do anything that requires the device to seem un-rooted and defer to other advice in the thread, but thanks to your's and other reports here I'm learning and researching it.

[EDIT]

Having done some research and read through some posts: I may not be understanding your circumstances but, if the ROM without SU seems to be unrooted for some time after flash, and then later appears to be rooted, it stands to reason that some change has been made to the system. I don't know all of the things that could do that but...

You may be right about the security patch, which sounds like the best guess so far, but to make it a reality instead of a guess and to perhaps request a fix, you could try logging it if you've not already done so. If you have done so I'd be interested in seeing the log.

If that security patch is not the cause then I would wonder about these following things however based on your previous notes it sounds like they are not factors.

- Xposed

- Custom kernel

- Some other item flashed from TWRP.

-Some other action taken in TWRP.

- Other things.

Also one point of process. A few pages ago you mentioned your clean flash process, which looks good but does not specifically mention a Full Wipe (Factory Reset). Even though wiping all of the individual parts with the check boxes should work as well you might consider doing a factory reset the next time if you have not done so before.
[Moto G 2015 Original Android Development] Subinsmani:
ya i have full done full clean exclude external memory...

and installed only rom no gapps no mods no custom kernal...

i have also research about this and i have found that this may come due to kernal also...

https://www.reddit.com/r/Nexus5/comments/5r3hp8/how_to_get_safetynet_with_root_working_in/

dnt know what to do now..
[Moto G 2015 Original Android Development] zuke66:
First time installing lineage os (14.1 20170323 nightly osprey) and I lost my root for apps. In my development options - root access I only have disabled and ADB only. Just wondering what I have to do to get root back for my apps.
[Moto G 2015 Original Android Development] Subinsmani:
just install su add on on linageos download page under extras tab...
[Moto G 2015 Original Android Development] reeeju:
Flashed latest build

ROM IS BUTTERY SMOOTH

VOLTE WORKS WELL

I USED OPEN GAPPS 7.1 MICRO PACKAGE

MORE REVIEW COMING SOON

---------- Post added at 04:53 AM ---------- Previous post was at 04:41 AM ----------

IS THERE ANY WAY TO GET BACK THAT VOLTE OR HD SIGN IN STATUS BAR BESIDE LTE SIGN? [MENTION=4480917]Alberto97[/MENTION]
[Moto G 2015 Original Android Development] IronTechmonkey:
Thanks for that link. That's interesting and a bit funny in regards to kernel since the custom kernel may be a workaround as opposed to being the cause (as I had thought possible) . You might consider testing that kernel but ...then you would be outside of the box in re troubleshooting the raw LOS ROM and reporting here, and you would have to revert to a nandroid backup to go back to previous kernel cleanly.

That being said, there may be a better way that actually could help fix this issue or better establish it's cause. I did some searching at jira and there may be something for you to work with there. There are 2 tickets which seem to be just for this issue. Unfortunately these tickets were filed as regressions which can only be filed for something that broke between 2 consecutive nightly/weekly builds. For a bug that has been around for a while a "bug" report must be filed. Typically those bug reports are only received for snapshots but LOS jira has been receiving them for weekly builds over the weekend in what they call bugbash.

I suggest that you review these 2 rejected tickets, and with the information from your own experience and the tickets file a bug report (as opposed to a regression) during the weekend bug bash. In the report you can paste links to the 2 rejected tickets to tie it all together. Jira will require logs and good details, and there is no guarantee they will accept it, but I think this could be a viable path to a fix. Here are the 2 ticket to which I've referred:

https://jira.lineageos.org/browse/REGRESSION-7

https://jira.lineageos.org/browse/REGRESSION-145
[Moto G 2015 Original Android Development] zuke66:
Thanks
[Moto G 2015 Original Android Development] IronTechmonkey:
March 23 build? Not much point since the next Osprey build will be released tomorrow (unless you've managed to get some pre-release copy of it which case, please do share). There is typically little productive value to bug reporting an old build unless checking to see if a detected bug is a regression or not. Knowing if the new build has fixed previous bugs or introduced new bugs is however of value. Things to look out for in that regard:

- Panorama picture camera crash.

- com.android.phone FC when leaving voicemail sound settings.

- Increasing system fonts size pushes countdown timer backspace button off screen

It's unlikely that those will be fixed in tomorrow's build but still worth checking. Also those are only the ones I've been testing and there are certainly more outside of my range of use and testing, such as the Android Pay issue described a few posts ago.

Also, please pardon my editorial help preventing those all caps (which are indeed considered shouting in forums like this) from running through the thread. ;)
[Moto G 2015 Original Android Development] reeeju:
1.panorama working well

2. No fc

3. Happens when trying to increase font size
[Moto G 2015 Original Android Development] IronTechmonkey:
Thanks for testing.

1) Some people have not experienced the pano picture crash bug but some people can reproduced it reliably immediately after clean flash on this device and another (Peregrine). This may mean it is related to some setting which, if changed later prevents the crash. This one has been reported here: https://jira.lineageos.org/browse/BUGBASH-326

2) I neglected to mention that phone FC only occurs with visual voice mail disabled (apologies). This one reported here: https://jira.lineageos.org/browse/BUGBASH-315.

3) Not that I like any bugs but ones with the layout that have obvious visual clues are easier to test:). This one is reported here: https://jira.lineageos.org/browse/BUGBASH-300

In general there could be circumstantial differences such as different settings combinations that we each use which may cause a bug to appear for one person and not for another. Thanks again for giving them a test, particularly the pano picture issue which is not occurring universally. Since that one was reported from a different device (but also reproduced on our Osprey) I'm curious to see if the fix works on both devices but unlikely to be in tomorrow's build.
[Moto G 2015 Original Android Development] reeeju:
Okay....

Is it possible to change the position of clear all button in recents panel...cos when try to clear all I have to scroll down all the opened apps then only I cud reach the clear all tag....
[Moto G 2015 Original Android Development] IronTechmonkey:
You're not alone there. I dont like that at all and many people dont. IMO this is made difficult by google because we are supposedly not to clear recents often (better performance if apps left cached). There is an element of truth to that, but not for all usage cases. You could try the app Recently (https://play.google.com/store/apps/details?id=eu.chainfire.recently) but at that point we're getting off topic for the ROM.
[Moto G 2015 Original Android Development] Sal12538:
Just flashed CM14, gotta say its smooth. Only facing one problem, can't access my SD card using the CM file manager. It just says that "Root privelages needed" but I have already given it root access.
[Moto G 2015 Original Android Development] panagiotis15:
There are many file managers at the market.I deleted the cm file manager at all!
[Moto G 2015 Original Android Development] GustavoWiesner:
Video recording does not work with Google Camera.
[Moto G 2015 Original Android Development] hareshsangar:
Set recording to 720p

Yes works for me...
[Moto G 2015 Original Android Development] GustavoWiesner:
720p works.
[Moto G 2015 Original Android Development] kanishkdudeja:
Is this rom the same as the one of this thread?

http://xdaforums.com/2015-moto-g/development/rom-cyanogenmod-14-moto-g-2015-t3458315
[Moto G 2015 Original Android Development] S¡lver:
That's an old version. This is an updated version but by a different developer.
[Moto G 2015 Original Android Development] green2005:
How to apply hexaolibre theme ? Plz, the apk is in system
[Moto G 2015 Original Android Development] Mimisf:
You can't right now. Theme manager needs to be built for cm14 and it most likely will at the end of the development.
[Moto G 2015 Original Android Development] gp_sousa:
ROM Updates

When there are new updates for this ROM, the same will have to be done manually? This ROM does not have a section for updates in the settings.

Despite that, the Developer Options section, there is an option of "automatic updates of the system."
[Moto G 2015 Original Android Development] Mimisf:
The same process manually again. There is no ota for now.
[Moto G 2015 Original Android Development] Sunhoo:
Manual install means formatting and installing again, right? You can't install the new release over your existing installation?
[Moto G 2015 Original Android Development] Mimisf:
NOOO!! Don't delete your data lol

Just wipe system,cache and dalvik cache and reinstall the ROM zip (any any other zips you may have installed.) No data will be lost this way.

---------- Post added at 02:21 PM ---------- Previous post was at 02:20 PM ----------

See above I forgot to quote you ^_^
[Moto G 2015 Original Android Development] robot_head:
Has anyone noticed when restoring a backup of this ROM a lot of the settings are not saved. And text messages do not appear it shows up as blank like none were ever sent or received. I don't really care I love this ROM just in case someone else has the same problem
[Moto G 2015 Original Android Development] GustavoWiesner:
New fault: After flashing SuperSU, the phone does not detect any SIM. I am currently trying to fix flashing the 'NON-HLOS.bin' file. Model: XT1543.

---------- Post added at 11:10 ---------- Previous post was at 11:05 ----------

Updated: Lost one of the two IMEI :crying:
[Moto G 2015 Original Android Development] robot_head:
Supersu does that for dual Sim for some reason, just use cm root

Same issue

http://xdaforums.com/showthread.php?p=68803603
[Moto G 2015 Original Android Development] GustavoWiesner:
Remove SuperSU and the problem was solved, thanks :good:
[Moto G 2015 Original Android Development] panagiotis15:
Something is going wrong with your backup I made a backup yesterday and i restored this backup today.Everything works ok...everything.I think its impossible a backup behave like you are saying....
[Moto G 2015 Original Android Development] S¡lver:
Do you know that the backup just saves everything at that point of time. So if you get messages or change settings after taking a backup, restoring it won't keep them. Also, did you take a Backup of data too? And if you did, did you restore it too? Because if you hadn't, everything will be at default settings.
[Moto G 2015 Original Android Development] robot_head:
I've been making backups for millions of years on several different devices only this ROM does it if I go back down to CM 13 then flash this backup the problem appears
[Moto G 2015 Original Android Development] reeeju:
Thanx for ur suggestion...I know that app...

I used it in my titan regarding euphoria ROM doesn't have clear all at their initial builds but the dev implement it later
[Moto G 2015 Original Android Development] reeeju:
In case of my two previous roms(aosp caf 20170324 and aosp extended v3.3 20170309) GPU temp was above 65°c always.....and phn was feeling literally hot when I hold it without my motomo back cover; sometimes GPU temp goes beyond 70°c also...that's why I m searching for a cool:laugh: ROM...

I think I found the right one

Thanx Alberto97 for such a nice ROM...keep it up man....
[Moto G 2015 Original Android Development] Komapatient:
Since nobody is answering me in the Q&A I will ask my question here:
[Moto G 2015 Original Android Development] reeeju:
Today morning I flashed this ROM latest build..live display in automatic mode...when I went out under bright sun and take out my phn from pocket it automatically gave me maximum brightness and when I entered room and take out the phn brightness is reduced

Final word..live display works for me...

Probable solution for u - reflash the ROM ;ie clean flash with open gapps and don't use any theme engine
[Moto G 2015 Original Android Development] xfahim:
Looks like a new build is available. Going to clean flash because my current one (3/16) is giving me pretty bad battery life and BT issues. Lets see if it's solved or not.
[Moto G 2015 Original Android Development] dougue2:
Moto G Model XT1543 - Osprey

Hello I need help using the official Lineage OS rom I down and I make the installation via TWR normally more when I reboot it gets garaged with the initiation of the LineageOs rom and does not leave this one because I can not do the installation? I'm using the rom Resurrection Remix it and good I know that LineageOs is better because it follows the bse of Cyanogemod. I hope you can help me. Personal sorry for my English because I'm using google tratudo to talk (I'm brasieliro)
[Moto G 2015 Original Android Development] ApocalypsjeNL:
Hello,

Is there some kind of night mode in Lineage OS?

Regards,

ApocalypsjeNL
[Moto G 2015 Original Android Development] IronTechmonkey:
Battery saver on? https://jira.lineageos.org/browse/BUGBASH-45

If not...

Assuming truly clean flash and no hacks or mods of ANY kind have been applied.

Live Display worked for me in tests of March 16 and March 23 builds where it was enabled by default (not yet up to March 30). Immediately after flash It seemed to misinterpret the time of day, and in my case it actually invoked night color during daylight hours until the ROM had a chance to connect to whatever services feed it the location and time. I know it is less dependent on a GPS location fix than it once was, but I still dont know exactly what makes it work. That being said, the next time you clean flash you might try the following.

- Connect to a wifi network

- Connect to your cellular network (should occur natural with working SIM and Service Provider)

- Connect to Mobile data network. For good measure make sure data save is disabled.

- Get a GPS fix

- Don't reboot wile testing (in the older incarnation of LiveDisplay we had to get a new GPS fix after every reboot. This should not be required but cant hurt).

If the issue continues in clean flash, you might help fix it by logging the issue and participating in this jira ticket: https://jira.lineageos.org/browse/BUGBASH-226

You could also find other reports of this by searching web for - LOS 14.1 LiveDisplay not working.
[Moto G 2015 Original Android Development] adityak1303:
Have you done a clean flash? (Wipe dalvik cache/system/data/cache/internal storage). If not, try it.

Also make sure you are using the latest gapps package. Try pico or nano package.

---------- Post added at 03:07 AM ---------- Previous post was at 03:07 AM ----------

Yes. It has live display for night mode. You can configure it according to your needs.
[Moto G 2015 Original Android Development] Sachin ET:
Big Thanks to the developers........looks like the media scan issue is now fixed.
[Moto G 2015 Original Android Development] Ashwin Asher:
Really bro.. Did you tested multiple times with different apps like WhatsApp.. Facebook? :fingers-crossed:
[Moto G 2015 Original Android Development] Sachin ET:
I don't use Facebook bro......but WhatsApp is working fine.......and I've also tried some image editing softwares like snapseed picsart etc.......i hope everything else will be working fine tooo.......just have a try bro.
[Moto G 2015 Original Android Development] Ashwin Asher:
Edited images in picsart are all showing fine ah bro?
[Moto G 2015 Original Android Development] Sachin ET:
yes.....now they are showing......earlier they didn't show up even after a manual media scan.
[Moto G 2015 Original Android Development] Ashwin Asher:
Very much thanks bro..!! Am out of data.. I'll by tomorrow..! ??
[Moto G 2015 Original Android Development] reeeju:
Will try new build now..downloading

??amazingly my broadband giving me now unbelievable speed in uc browser
[Moto G 2015 Original Android Development] althafvly:
[MENTION=4480917]Alberto97[/MENTION] Can u add this hd notification disabler in next build.. Coz redmi note 3 and oter devices added it on official cm

In ims.apk

1. res>values>bools.xml

Change value of config_update_service_status to True

2. res>values>strings.xml

Delete value of device_is_hd_capable

3. res>values-mcc** > bools.xml

Change all values of config_update_service_status to False
[Moto G 2015 Original Android Development] IronTechmonkey:
I dont need this and would not even know if that is a viable fix (although I dont doubt that it is viable) but thanks for providing an answer with the question :)

I wonder if this could be filed at jira during weekend bugbash. https://jira.lineageos.org. I would try to do so but dont think I could effectively.
[Moto G 2015 Original Android Development] Subinsmani:
one off topic,[emoji16] [emoji16]

on jira.lineageos.org, when i create new issue it only show regression... no other option, so how to report bugbash. [emoji12] [emoji12]
[Moto G 2015 Original Android Development] reeeju:
Flashed 30th march build..all good...

This is becoming my daily driver ROM in osprey....

The phn is dazzling now:laugh:
[Moto G 2015 Original Android Development] IronTechmonkey:
It could be logically argued that asking a quick question about jira is right on topic. :)

On the weekend, starting Friday night (in my GMT-4 time zone) there is another option under category "Project". One time it might have appeared later, some time on Saturday. IDK if there is any automatic email notification when it opens but keep an eye out for that just in case.
[Moto G 2015 Original Android Development] reeeju:
this rom saves mah day

Really guys I have tried almost all ROMs available in osprey XDA forum and kernels also....and tuned to different levels but lineage 7.1 with its stock kernel gifts me best juice till now....ss attached below...I will attach another ss of battery usage after some hours of usage....

My LTE on all the time
[Moto G 2015 Original Android Development] Komapatient:
Only automatic power saver if less than 15% battery. -> So never reached that limit.

Performance profile is balanced and extreme power saver is off.

Clean flashed the first official nightly build and then always dirty flashed with cache/Dalvik deleted.

No Mods/hacks installed.[/QUOTE]

I cannot recall if it ever worked on any build. But at least on 16th and 23rd I had those problems.

I am very reluctant to do a clean flash, after my phone is set and I don't want spend hours to configure it again.

But thanks for your help and suggestions.
[Moto G 2015 Original Android Development] reeeju:
After 3hours of usage....

Seeing 7.1 in my phn one of my friend was telling me to root his merlin ....

But he can't found a USB cable in his room????
[Moto G 2015 Original Android Development] ApocalypsjeNL:
Is battery life better on newer builds? At build from 16-3-2017 they are really bad for me.
[Moto G 2015 Original Android Development] IronTechmonkey:
OK, that seems to eliminate one possible factor/cause.

Previous clean flash does eliminate doubts introduced by later dirty flash.

We are certainly not always in a position to clean flash however, remembering that the goal (here at least) is bug testing the ROM more than getting a single device to work, the clean flash is not necessarily the "fix" but, a clean flash followed by good testing removes doubts and provides better opportunities to detect the cause. Sometimes that fix could even be directly related to making dirty flashing work but... clean flash is the base from which bug reporting should start, followed by methodical and incremental testing as you install apps and make settings changes. Capturing logs is an important part of this as well.
[Moto G 2015 Original Android Development] Komapatient:
I am aware of that and done that for several devices here on the board. I know that this is the development thread, but nobody answered me in Q&A. :(

I will do a clean flash when I do find the time. Until then I will live with this single bug.
[Moto G 2015 Original Android Development] IronTechmonkey:
BTW, thanks for asking at Q&A, and just to be clear, I was advocating the process but not complaining about you posting in dev thread (although I've done that before in general, perhaps too much), and not saying you had to clean flash right now this very second. You now have a chance to watch for other factors as you use the device, and if you notice anything (or if you dont), even after dirty flash a log has the potential to find the problem and is relatively easy to get.

Even though I've not had the same problem on Osprey I have noticed oddities relating to system time in LiveDisplay on Osprey which dont occur on Peregrine, and think there may be something to this so I'll be looking out for chances to test it... if I can find a way to reproduce it. Sometimes a simple settings change elsewhere can be the difference between being able to reproduce an issue or not. A current bug where phone FCs when leaving voice mail sound settings is a good example of this; it only occurs when visual voice mail is disabled so some people never experience it while others do.

[EDIT] What version of TWRP do you use, and is the time and time-zone set properly in TWRP?

The I reason I ask: The "oddity" mentioned above is that during my after flash first-run configuration in March 16 and March 23 Osprey builds, LiveDisplay was invoked at the wrong time of day until the device was connected to cellular network and or mobile data or wifi. Where I wonder if this relates to TWRP is...In TWRP some times of year the time is off by an hour (possibly related to daylight savings). Just one more time related possible factor.
[Moto G 2015 Original Android Development] Komapatient:
TWRP 3.1.0-1 is set correctly to my time zone (UTC+1) with daylight savings on. So correct time and date is set.
[Moto G 2015 Original Android Development] IronTechmonkey:
That might remove another possible factor. Thanks.
[Moto G 2015 Original Android Development] damianiq:
Hello guys,

I don't know if I'm the only one experiencing this but, when I receive a voice call I only hear the sound of it ringing. The phone app doesn't come on top on display. I have to open the phone app and tap "Return to voice call in progress" to be able to pick up the incoming call. I'm running the 3.30.2017 build and my phone is an X1542.

Anyone else having this issue?

Cheers