yashsingh1/xdaforums huggingface dataset:
[G 2014 Original Android Development] Transdimensionalotaku:
I also have a small bug to report, but I'm encountering it only with a specific app. Still, it didn't happen while I was on MinimalOS. Don't know if it's a CM issue, but here goes:

While playing music using Phonograph, if I turn off the screen, then turn it back on, a filter is applied to the music and it sounds kinda muffled and the volume is lowered. If I do the same while headphones are plugged in, the volume is raised , but I notice no muffling. It's really annoying. If I have an equaliser active (from AudioFX) while doing this, nothing happens, either on speakers or headphones.

Disabling or removing AudioFX entirely had no effect on this, it's the same as having no equaliser active.

Is it something system wide? Is it just an error in the app?

EDIT : It happens on Timber Music Player as well, and it's easily reproducible using the steps above. So it could be system wide. On VLC it doesn't happen for some reason, although VLC has its own issues with equalisers.

Logcat while doing the procedure above ^ : http://pastebin.com/wnBUGyYp

---------- Post added at 03:21 PM ---------- Previous post was at 03:19 PM ----------

I thought we were talking about the touch delay though?

What does DTW have to do with this, since it isn't even in CM for this device?
[G 2014 Original Android Development] josfr4ncisco:
He actually copied the instructions for getting the screen model from a kernel thread (dtw works on one of those screens), lol
[G 2014 Original Android Development] Transdimensionalotaku:
Oh lol

Well at least now we can get screen models
[G 2014 Original Android Development] josfr4ncisco:
Let's gather some information and see what kind of screens (if they're the fault of this) are causing the touch issue.

I have the mdss_dsi_mot_inx_720p_video_v0 one and it has touch issues.
[G 2014 Original Android Development] andreas0013:
Hello guys, I just installed the latest nightly and gapps but my play store is not working. It says "unfortunately, Google play store has stopped".
[G 2014 Original Android Development] tom002:
Did you do a fresh installation (Factory Reset) and install GApps directly afterwards without rebooting into the new system first?
[G 2014 Original Android Development] josfr4ncisco:
Are you using OpenGapps by any chance?
[G 2014 Original Android Development] mario156090:
The ROM not enter to deep sleep

Enviado desde mi SM-T230NT mediante Tapatalk
[G 2014 Original Android Development] Mestreian:
I installed the latest version of ROM and nano opengapps and playstore does not open

Error

java.lang.RuntimeException: Unable to create application com.google.android.finsky.FinskyApp: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.app.AppOpsManager.checkPackage(int, java.lang.String)' on a null object reference

at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4754)

at android.app.ActivityThread.-wrap1(ActivityThread.java)

at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1424)

at android.os.Handler.dispatchMessage(Handler.java:102)

at android.os.Looper.loop(Looper.java:148)

at android.app.ActivityThread.main(ActivityThread.java:5461)

at java.lang.reflect.Method.invoke(Native Method)

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)

at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)

Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.app.AppOpsManager.checkPackage(int, java.lang.String)' on a null object reference

at android.os.Parcel.readException(Parcel.java:1626)

at android.os.Parcel.readException(Parcel.java:1573)

at android.content.pm.IPackageInstaller$Stub$Proxy.getMySessions(IPackageInstaller.java:385)

at android.content.pm.PackageInstaller.getMySessions(PackageInstaller.java:415)

at com.google.android.finsky.installer.v.<init>(SourceFile:77)

at com.google.android.finsky.FinskyApp.onCreate(SourceFile:18023)

at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1014)

at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4751)

... 8 more
[G 2014 Original Android Development] apx@dwx:
this is a thread about cm13 for moto g 2014, not gapps.

so you should ask your question about gapps-errors here:

pa-gapps-continuation

thank you ;)
[G 2014 Original Android Development] godoy.rafa:
Erased
[G 2014 Original Android Development] nuno cravo:
Yes wrong quote i eas supposed to start another thread sorry.

Now for your issue

For lag, go on configs

Language and entrance >mouse trackpad

Them pull the bar all to your right

Other thing

Go to

Configs>developer options>Windows scale animator> set to 0 OK

Then below > scale transition> set to zero

Then below >animator scale duration> set to zero and OK

Then test and post the results

Cheers
[G 2014 Original Android Development] H@wK11:
SD card option again gone from camera.
[G 2014 Original Android Development] daywalk3r666:
the option is still present.
[G 2014 Original Android Development] rghvdberg:
Clock crash when language set to Dutch (Nederlands)

What is your--

Phone model :XT1068

CM version: 13.0-20160324-NIGHTLY-titan

CM Download url: get.cm

Gapps version: open_gapps-arm-6.0-nano-20160324

Did you--

wipe: yes

restore with titanium backup: no

reboot after having the issue: yes

Are you using--

a task killer: no

a non-stock kernel: no

CMSettings/Performance settings (other than stock): no

Dual SIM: yes

other modifications: adaway, supersu (to get rid of # symbol :silly:)

Reproduce crash : tap cLock wigdet, tap 3 dot menu, tap settings -> crash

set language to English (US) , no crash
[G 2014 Original Android Development] Bobtehblob:
I too am having the play store constantly crash on boot. This after a clean flash on the 26th nightly with latest gapps.
[G 2014 Original Android Development] LuK1337:
Have you tried wiping Clock's data?
[G 2014 Original Android Development] Danilo-Sanchez:
I have a problem writing on sdcard folders on some apps. Will this enable me to write on sdcard on these apps?

http://review.cyanogenmod.org/#/c/138053/
[G 2014 Original Android Development] rghvdberg:
Wiped data, rebooted, still crashes.

Wiped data, no reboot. Settings crash again.

Verstuurd vanaf mijn Moto G 2014 met Tapatalk
[G 2014 Original Android Development] LuK1337:
I'll try wiping my other phones later. I'm not going to do it on my dd.
[G 2014 Original Android Development] rghvdberg:
Sorry I wasn't clear enough. I wiped clock data. Not a full wipe/factory reset.

Verstuurd vanaf mijn Moto G 2014 met Tapatalk

---------- Post added at 01:16 PM ---------- Previous post was at 01:09 PM ----------

btw: found out weather wasn't updating.

noticed this :

https://play.google.com/store/apps/details?id=com.dvtonder.chronus

Using OpenWeatherMap as source seems to fix this.
[G 2014 Original Android Development] Transdimensionalotaku:
Mouse trackpad thing did nothing. Disabled animations (although I don't want to have to do this, I like how they look), and still, nothing. Touch delay is still there.
[G 2014 Original Android Development] josfr4ncisco:
Actually noticed we both are facing touch lag and we got the same screen, lol
[G 2014 Original Android Development] Danilo-Sanchez:
I got the same result, but I think that touch response is fine now.
[G 2014 Original Android Development] Jeannuel:
Hi, right now Im using the 2016/03/22 nightly. I have zero problems with this build, I use it as my daily driver. Theres something new worthy to update the nightly to the last one? (im seeing that the last build is from 03/26)

thanks and sorry if im bothering.
[G 2014 Original Android Development] Danilo-Sanchez:
You can see the changes here: http://www.cmxlog.com/13/titan/
[G 2014 Original Android Development] sagar846:
This might be OT but has the play store/services fc problem been fixed in today's build or is it a problem with the gapps itself? I flashed 26/03 build with the 19/03 gapps and problem still persisted.
[G 2014 Original Android Development] rghvdberg:
I flashed 24/03 build cm with 24/03 build open gapps nano and have no issues with play store etc. So I guess it's better to use the latest gapps.
[G 2014 Original Android Development] Danilo-Sanchez:
I'm sure your issue is related to gapps. Try to download gapps from another day.
[G 2014 Original Android Development] josfr4ncisco:
I reverted to CM12.1, but yeah, going to test it later to see if it's improved.
[G 2014 Original Android Development] Danilo-Sanchez:
The only issue that I have is that some apps don't save data to sdcard, but this isn't related to CM13 but Android 6 in general.
[G 2014 Original Android Development] josfr4ncisco:
Can you test the touch on some intensive games like Dumb Ways to Die or Vainglory in the meantime?
[G 2014 Original Android Development] Danilo-Sanchez:
Yes. Let's talk on PM.
[G 2014 Original Android Development] Kurt Krummbein:
... fixed in build from 2016-03-25 ...

Kurt
[G 2014 Original Android Development] rghvdberg:
Gonna update tomorrow. Thanks

Verstuurd vanaf mijn Moto G 2014 met Tapatalk
[G 2014 Original Android Development] rgnicholas:
It seems the last couple of CM builds (and others built on them) are giving Play services force closes constantly. Clean flashed with latest OpenGapps... and Banks dynamic. Is this the experience of others? Or maybe this is a hiccup with later Gapps packages? Just curious. I really want to test the latest build under better circumstances. I am NOT complaining, I know the devs are working hard at perfecting CM, but I hoped to find a work around. TIA
[G 2014 Original Android Development] luca020400:
Flash old build or tomorrow build
[G 2014 Original Android Development] mmerlone:
Personal observation and idea

So, I have been following this "touch lag" conversation with close interest. Since I applied a glass protective film on my xt1069 touch became very crap. But I was curious if that was all and the easiest test was to remove SD Card (class whatever). Did it, rebooted to be sure and bingo! Removing SD Card DID make a BIG difference on touch sensitivity. You don't need a heavy app to test, I use SlimSocial for Facebook navigation and page scrolling is enough to be sure.

Those are subjective observations though. So I felt the urge to download some kind of "touch sensitivity test and benchmark app" so we could give some real objective data to help devs, but... would such an app be even possible in any way?

:laugh::fingers-crossed::confused:
[G 2014 Original Android Development] rgnicholas:
Thank you... I'll wait for another build. Appreciate your work!
[G 2014 Original Android Development] ihmerick:
Waiting for a fix of google service crash issues
[G 2014 Original Android Development] shouryashri14:
I have tried many gapps but nothing works , especially the open gapps for which the link is provided. I keep having this error unfortunately Google play services has stopped. Need help
[G 2014 Original Android Development] rghvdberg:
Come on man, read 5 posts back in this thread .

Verstuurd vanaf mijn Moto G 2014 met Tapatalk
[G 2014 Original Android Development] lokopol:
any user can confirm if Xposed works with the latest version. 2016-03-28 ??

Thank you.
[G 2014 Original Android Development] RukusX7:
Can anyone confirm if this rom will run on my toaster? thx.
[G 2014 Original Android Development] sharique88:
This ROM is now quite stable for me. I'm updating every week with the official CM OTA, and i am not facing any issue. Just 1 bug is there that i cannot select sim as ask every time in messaging app.
[G 2014 Original Android Development] sagar846:
Yeah dude.

I was able to run this on my oven.

Just grab a remove the screen from an old tablet. Paste that son of a b**ch to the side.

Attach a motherboard lying around somewhere. Some RAM too (check the saucer shelf you might find some ). A Li-on battery. A GPU and some cpu's (check your cereal box for this, I got a few as a surprise toy).

And then just add the rest of the crap needed and connect that Hodge podge to the power supply and you're good to go.

Heck I installed Windows 7 on mine and it's working perfectly.

I would attach a photo but judging by the fact of the complete bulls**t I've said, I won't.

P.s. You said ON your toaster. I took it literally.

#OvenAndroid/Windows #MeTryingtoBeFunny #ThisIsSoOffTopic #IEditedThisPost5timesAlreadyRIPTypingSkills

#IDidNotThinkThisThrough #IDC #TooManyWordsInAHashTag #IShouldStopNow

#OkThisIsTheLastOne #AnotherOne #DjKhaled
[G 2014 Original Android Development] marcelo1998:
Cm13 ou RR12.1?
[G 2014 Original Android Development] benjausen:
Hi people. XT1072 Thea user here. I am impatient for the snapshot (please don't say anything) so I am thinking about trying a nightly. The problem is that I don't know if it's safe to move on yet. I know Titan & Thea are mantained by the same guy and both get the same nightlies, but should I jump to CM13 or stay safe and wait for the snapshot? Please answer me politely. I refer as stable to a build that works for daily use or with minor issues.

Currently running CM12.1, 20151117/YOG7DAO1K5 snapshot with zero issues since the first install. My device is already customized and full of info and games.
[G 2014 Original Android Development] RukusX7:
Unless you feel you're missing something, the snapshot is the best.

---------- Post added at 10:30 PM ---------- Previous post was at 10:26 PM ----------

This is the cm13 thread..... sooo... cm13.
[G 2014 Original Android Development] CreasingMass Dev:
Stay on cm12.1
[G 2014 Original Android Development] ayush_nagpal:
instructions

can I get instructions on what to wipe in recovery before installing the build and gapps:rolleyes:
[G 2014 Original Android Development] sagar846:
You can just flash cm13 and latest gapps on whatever ROM you're on now.

But it's better to do a full clean wipe. (wipe system, data, dalvik cache and cache). Then flash build and gapps. Then for future builds, inbuilt cmupdater does the job for you.
[G 2014 Original Android Development] doppelhelix:
Big thanks to the devs for fixing the deep sleep issue!

Nice work guys :good:
[G 2014 Original Android Development] virenlr:
After properly setting up the build environment , installing all the required files, syncing the repository and extracting the proprietary blobs, i started the compilation process. After about 4 hours, I got a build error as shown in the screenshot. Can someone please tell me where I am going wrong?

Thanks in advance for your time :)
[G 2014 Original Android Development] sharique88:
It's pretty stable... I'm using for the last 50 days. Use the pico gapps package.
[G 2014 Original Android Development] Rajat22:
Google play service fc fixed or not ??
[G 2014 Original Android Development] sagar846:
Yeah. It's been fixed.
[G 2014 Original Android Development] Dr Matt:
Hi ppl, I have a XT1068 runing SlimLP on 5.1.1 with bootloader v48.82

can I just flash CM13 by TWRP? Or do I have to do some other step first?
[G 2014 Original Android Development] Rajat22:
yes you can. but im waiting its final build .and is its recent botton works perfectly ?? any one please reply
[G 2014 Original Android Development] benjausen:
I think I will stay in CM12.1 for now. I want to move but these bug stories still scare me away. Alright, I will wait for the snapshot and then update. Still better than stock LP.
[G 2014 Original Android Development] smitharro:
Bug stories? Most people complaining here caused the problems themselves because of faulty apps or settings, like xposed, or non-stock kernels. I'm using CM13 since the very beginning of it. Still before it became official. Every now and then a small bug comes by (yes, these are nightlies!), but in general it's solved quickly! Nothing to be afraid of or let you scare of!

Written with my XT1068 using Tapatalk on CM13
[G 2014 Original Android Development] skaveelicious:
Only issue if at all are touch issues which me,luk,luca and many others don't have. Also some games do have general issues regarding input on Android 6.

If you don't have to many apps you could do a backup with twrp and copy it to your pc just to be safe, then flash 13.0.

Lastly, a big mistake that some guys in her do is flash every single nightly. You only flash a nightly if it adds something new/something you want or fixes a bug. You can either track changes using cyanogenmod gerrit or http://www.cmxlog.com/13/titan/ and decide whether it is worth updating or not.

At the current state a "bugless" nightly is equal or better than a snapshot.
[G 2014 Original Android Development] chadha:
What touch issues are you guys facing? I want to know if I also might be having one but yet not recognized.
[G 2014 Original Android Development] Danilo-Sanchez:
The touch commands doesn't respond when you swipe or touch softly like it was in CM12.1.

Sometimes you need to swipe twice to make it work.
[G 2014 Original Android Development] josfr4ncisco:
Here's how I describe the touch problem: soft gestures don't work as they used to on CM12.1.

Swipes: When unlocking the device, for example, a single soft swipe on CM12.1 would be enough. On CM13, either you have to swipe softly a couple of times or do a firm swipe. On some games, like Dumb Ways to Die and Table Touch Tennis, this is annoying because you have to be quick.

Taps: Again, soft taps don't work as they should. That applies to everywhere on the phone, because you have to tap firmly/strongly to make it work. On some games (like Vainglory), this is hard, because it's a MOBA and you gotta be fast, and the sensivity sometimes makes you die or lose a prey.

That's all I can try saying now, I guess. If there's a more dev-focused way to report it, let me know, I will report back.
[G 2014 Original Android Development] luca020400:
Thanks for the good explanation

Soft touch work perfectly on my thea and titan, I don't really know what's the problem
[G 2014 Original Android Development] josfr4ncisco:
We got three different screens for our devices. An user here said that one or two models might be causing the issue. Could you grab your phone's screen model for a comparison?

Also, tested stock MM yesterday and sensitivy is all good, so I'm also lost here.
[G 2014 Original Android Development] luca020400:
Display has nothing to do with that, touchscreen is the same between all the moto g 2014

Anyway I have both inx and jdi
[G 2014 Original Android Development] josfr4ncisco:
Since some users experience it and some don't, is there a proper way to report it? Because that's all the users affected by the issue can do now.
[G 2014 Original Android Development] chadha:
Which build are you on bro? I'm presently on the 2016-03-24, and not facing any touch issues. But lately the battery life is wearing off which I think happens with every Rom on every phone. I will flash the new one in this week, whatever is the latest the day I want o flash.
[G 2014 Original Android Development] josfr4ncisco:
Have been running a couple of the latest nightlies, but I've reporting this since late February/early March.
[G 2014 Original Android Development] chadha:
Bro try other roms just to check if t is Rom or something else.
[G 2014 Original Android Development] josfr4ncisco:
Sure, will download other MM roms and see if they also got issues.
[G 2014 Original Android Development] BealeStBluesBoy:
Hi, which is your base firmware?
[G 2014 Original Android Development] josfr4ncisco:
Base firmware? Running CM12.1 atm
[G 2014 Original Android Development] BealeStBluesBoy:
I mean the moto firmware you were using before installing cm
[G 2014 Original Android Development] josfr4ncisco:
Stock 5.0.2 -> CM12.1 -> CM13 -> Stock 6.0 -> CM12.1
[G 2014 Original Android Development] Danilo-Sanchez:
I have the same issue and tried everything: from stock 5.0.2 to CM13, from CM12.1 to CM13 and from stock 6.0 to CM13.
[G 2014 Original Android Development] BealeStBluesBoy:
Have you flashed proper 6.0 firmware? Today I've flashed XT1068_TITAN_RETLA_DS_6.0_MPB24.65-34_cid12_CFC.xml which is my variant firmware, coming from the generic RETAILDSDS and tested touch with Dumb Ways to Die, for me it did the trick, I notice a better responsiveness
[G 2014 Original Android Development] josfr4ncisco:
I've flashed XT1068_TITAN_RETBR_DS_6.0_MPB24.65-34_cid12_CFC.xml just to test and moved straight away to CM12.1. Since I'm at college right now, might give CM13 a try with 6.0 base firmware later
[G 2014 Original Android Development] Danilo-Sanchez:
The last one that I've flashed was TITAN_RETBR_DS_6.0_MPB24.65-34_cid12_CFC and I didn't have any issue with Dumb Ways to Die, but I have this problem with Table Touch Tennis.
[G 2014 Original Android Development] Somebod y:
Might be related to the app?
[G 2014 Original Android Development] Danilo-Sanchez:
No, it isn't related to the app, because in stock 6.0 it works well.
[G 2014 Original Android Development] Somebod y:
Never had the touch issue, so I wanted to try the app, but don't want to buy it just for a try.

If it works on stock, the problem could be related to different hardware or to software, that is not changed by flashing CM, but I am no dev....

By the way: Thanks to our devs, the rom is really great (and no problem with xposed :D)
[G 2014 Original Android Development] Danilo-Sanchez:
As related by [MENTION=5577087]josfr4ncisco[/MENTION], he is facing this issue with Dumb Ways to Die, which is free. You can try it (although I didn't face the issue with this game).

You can also try to unlock your phone swiping softly to see if it works.
[G 2014 Original Android Development] sharique88:
Even in using with xposed (with cm ota survival), never faced any issue..
[G 2014 Original Android Development] nxr_:
The only weird touch thing I've notice is in the recent apps menu. If you don't swipe perfectly down it starts to move the app horizontally as to remove it.

The rest, battery included, are great. Proximity decetor is off and just in case I restore de hosts file before flashing anything.
[G 2014 Original Android Development] nikunj.baheti@gmail.com:
Hey [MENTION=5778309]luca020400[/MENTION] [MENTION=5075128]LuK1337[/MENTION] can USB OTG support be added natively to the rom? like in stock kk and mm?
[G 2014 Original Android Development] LuK1337:
Umm...what?
[G 2014 Original Android Development] rghvdberg:
Just say yes [emoji83]

Verstuurd vanaf mijn Moto G 2014 met Tapatalk
[G 2014 Original Android Development] LuK1337:
I'd rather want to know what he meant by using word 'native' in this case.
[G 2014 Original Android Development] alexromhor:
Two Questions:

I can install xposed? Can anyone pass link/tutorial?

If there are more updates, I can install the lastest or I need to do 1, and then next, and then the other?

Thanks
[G 2014 Original Android Development] SuperSimian:
In the order you asked:

Yes, you can. No. You only need latest build.
[G 2014 Original Android Development] smitharro:
Yes, you can install xposed. But after you installed it, you can no longer complain about bugs anymore. Xposed is totally unsupported and is known to cause many 'bugs'.

Written with my XT1068 using Tapatalk on CM13
[G 2014 Original Android Development] Vidhanth:
Downloaded latest nightly, completely forgot its April 1st lol
[G 2014 Original Android Development] Somebod y:
Xposed itself is working very well on CM13 and causes no bugs for me, may be depending on the modules .
[G 2014 Original Android Development] alexromhor:
Can you give me a link or something? First time with xposed :c
[G 2014 Original Android Development] Somebod y:
Here you can download the framework (xposed-v80-sdk23-arm.zip) and the apk (XposedInstaller_3.0_alpha4.apk). For diskussion look here, because this is CM13 thread
[G 2014 Original Android Development] virenlr:
Heads up for everyone- If you have a lot of time on your hands, make sure you don't miss the latest build. If you do install the latest build, make sure to check out the epic new theme we now have xD
[G 2014 Original Android Development] Danilo-Sanchez:
Please post a picture of this theme, because I don't want to have the word "MOD" in every single word lol