yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] VegetaSSJ5:
Hi all!

My nexus 4 runs cm 12.1 (last snapshot). I would update to the first cm13 snapshot, but I would avoid the automatic update (Settings - > Info -> ...) and do it manually. I have some quesitons:

- can I use the last version of Philz recovery (clean to instal new rom + flash)?

- where can I find the gapps for the new version?
[Nexus 4 Android Development] miguelbelo:
I always use this ones http://opengapps.org
[Nexus 4 Android Development] thrustman:
Impossible to log in Snpachat
[Nexus 4 Android Development] jer_ying_fd:
Is there no ambient display? I thought there was in CM12.1 :\
[Nexus 4 Android Development] dixon85:
Does this issue persist in CM13 snapshot? I'm thinking about installing CM13 snapshot and this would be a deal breaker for me as well.
[Nexus 4 Android Development] 0Kajuna0:
It does
[Nexus 4 Android Development] sergio_f:
i never install snapshots, if it have problems you have to wait until next sanposhot
[Nexus 4 Android Development] hnl_dk:
It is not a general problem. Only some people (maybe based on location) have problems with assisted GPS. Here in Denmark I see no problem.
[Nexus 4 Android Development] 0Kajuna0:
Hm... I'm not sure what the cause of the bug is and why only some users see it. I've experienced it both in Spain and Italy.

I'm not optimistic, as they have labeled it as Fixed in Jira while some of us are still having it on more recent Nightlies https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/NIGHTLIES-2628
[Nexus 4 Android Development] jcsogo:
I don't see any problem in Spain with my device and any of the nighties
[Nexus 4 Android Development] hnl_dk:
I do not think that your problem is due to that problem. It sounds more like there is a problem with the AGPS data, where the location is fund with help of the cell tower and/or locations of wifi access points.
[Nexus 4 Android Development] 0Kajuna0:
Then the problem does not look to be location-related.

I could be wrong, but wouldn't then the location be faulty when using "Power Saving" mode (Wifi+ Bluetooth + mobile networks) and correct when using "Device only" (GPS)? The problem is the exact opposite, as many people have reported: Location is correct when "Power Saving", really buggy (switches constantly between the correct position and a random one, even hundreds of kms away) on "High accuracy" and missing completely (not always, but very often) on "Device only".
[Nexus 4 Android Development] hnl_dk:
High accuracy is exactly when using assisted GPS (GPS, Wi-Fi, cellular networks and other possible sensors).

When you say that it is often missing completely when on "Device only" (only using GPS), are you indoors or at a location where it is surrounded by high buildings?

I am always using high accuracy and have never noticed any trouble. No matter if it is indoor or outdoors.
[Nexus 4 Android Development] 0Kajuna0:
High accuracy is buggy both indoors and outdoors, but definitely worse indoors. When testing with GPS status apps, very often the phone sees satellites but does not fix to them. High Accuracy and Device Only give trouble, Battery Saving mode is fine. That's why I think the GPS side is failing, not the "A" of AGPS if that makes sense, might also just be the way they interact.

Edit: TO answer your question more clearly, I will test again with Device Only outside, but I think it struggles a lot to get a fix. I'm not sure how long that should take, as like most people I've become accustomed to using High Accuracy and not having to wait for proper GPS signal. Thanks for your point of view.
[Nexus 4 Android Development] hnl_dk:
Battery Saving mode is when it is not using GPS... will try to test a few things, in little more than a week. If it is working good, can I let you test it, to see if it fixes your problems.
[Nexus 4 Android Development] 0Kajuna0:
Sounds great, thanks! :)
[Nexus 4 Android Development] hnl_dk:
Having two exams in next week, why I am not able to look at it before.
[Nexus 4 Android Development] 0rAX0:
Anyone has issues with LiveDisplay? it stopped working three days ago. No automatic as well as forcing night mode.

Also, sometimes when I set the alarm (or even when I leave it alone) it dies at night until I hold the power button and do it again to boot it. I read somewhere that it's a known issue but I haven't found a fix (a kernel change perhaps, and would that affect OTA?)

Thanks! ;)
[Nexus 4 Android Development] hnl_dk:
For me, the alarm was fixed with the release from 20160323.

Have not noticed any issue with LiveDisplay, but I can try to check later.

Can confirm that LiveDisplay is not working with 20160325.

Just found: https://jira.cyanogenmod.org/browse/NIGHTLIES-2656
[Nexus 4 Android Development] 0Kajuna0:
So I did some more outdoors testing. Device Only mode works reasonably well when completely outdoors. Once Device Only mode has fixed to satellites, High Accuracy works well too, but if GPS signal is just a little weaker (for example, inside a bus), High Accuracy goes crazy and gives me an error margin radius (the blue area in Google Maps) of about 12km, then the blue circle goes small and big randomly all the time.

Please let me know if I can help resolve the issue by providing logcats or whatever you deem necessary.
[Nexus 4 Android Development] hnl_dk:
Will return to you in a week (have written a calendar notification for Saturday).
[Nexus 4 Android Development] sijben:
Break out mako from devices that are still alive?

What does that mean?

"Break out mako from devices that are still alive"

in

CyanogenMod/android_device_lge_mako

and

CyanogenMod/android_kernel_google_msm

found here:

http://review.cyanogenmod.org/#/q/mako
[Nexus 4 Android Development] hnl_dk:
The device maintainer from Flo keeps breaking Mako... as an example: https://jira.cyanogenmod.org/browse/NIGHTLIES-2656
[Nexus 4 Android Development] Azerty16:
I've got a bug with Cyanogenmod 13 Snapshot, the alarm doesn't ring, or doesn't ring every time, sometime it works and sometime it doesn't, and when i check the alarm settings after it should have ring there is a number instead of the ringtones names. This is a very annoying bug
[Nexus 4 Android Development] brudjuz:
CM13 20160323 Nightly stable

I must report that I was installed CM13 20160323 Nightly with fresh install procedure and that version is working better than latest official. I am surprised with battery life, that is increased obviously. I recommend this version to everyone. My Nexus 4 is finally working like it should on Android Marshmallow 6.0.1. No bugs so far... :good:
[Nexus 4 Android Development] matteus198701:
Stock kernel or not?

Nexus 4
[Nexus 4 Android Development] hnl_dk:
There are some important changes in todays nightly... will report when I have done some testing (after it is done building).
[Nexus 4 Android Development] brudjuz:
CM13 20160323 Nightly stable

Stock kernel.
[Nexus 4 Android Development] AhmedAbdulhafiz:
please help after flashing the rom the phone boot up in twrp and wont to boot system !!!!!help
[Nexus 4 Android Development] 0Kajuna0:
My alarm was ringing when it should, but then it would not allow me to stop it. Then it crashed (App Not Responding). I installed Google's version of the app and all is working well now: https://play.google.com/store/apps/details?id=com.google.android.deskclock
[Nexus 4 Android Development] colin p:
I've been using Timely since I got my Nexus 4 and 7 (got them both the same weekend) and I've never had any alarm issues. But then again, Timely was bought out by Google around that time also.
[Nexus 4 Android Development] 0Kajuna0:
Hi.

What's the proper way to roll back to a previous nightly without losing any data? Alternatively, is there an option to turn the April Fools stuff off?

Thanks
[Nexus 4 Android Development] Bastlwastl2010:
Normaly dirty flash the previous nightly works, or wait for tomorrow nightly
[Nexus 4 Android Development] 0Kajuna0:
Thanks, that did it.

Is it just me or the April Fools joke was incredibly childish?
[Nexus 4 Android Development] 0rAX0:
I have noticed an interesting pattern here. The phone hangs on the nights of any day I perform an OTA update (using CM Downloader, not the built-in updater). Of course this goes without saying that I still have the problem with yesterday's update. :(
[Nexus 4 Android Development] MrKaupo:
I have 2303-nightly and got huge baterry drain because cpu always is 1.5 ghz as soon as i turn on display. It goes 384mhz or sleep with display off.
[Nexus 4 Android Development] Dazeon:
I'm running the latest snapshot release (16th March) which I clean installed having performed a full wipe from the latest TWRP, including wiping the system partition.

I am suffering from severe battery drain when the screen is on and in use. It dropped from 100% to around 89% in minutes having taken it off charge.

i can literally watch the percentage dropping whilst using the phone.

I have all the location and scanning stuff turned off, including NFC. Automatic screen brightness is off and the screen dimmed as far as it will possibly go.

I do run Bluetooth for Android Wear, but that never caused an issue under the official Lollipop build.

I have had a look with GSam and I can't see anything that looks suspicious (although I am no expert).
[Nexus 4 Android Development] infra_red_dude:
I have 0328 nightly and I can confirm fast battery drain issue. Nothing suspicious to me. I have BT on all the while for Android wear too.
[Nexus 4 Android Development] hnl_dk:
It was the worst April fools change ever :(
[Nexus 4 Android Development] hnl_dk:
Please try to check this to see if GPS is working better with this one:

http://www.amigaos.dk/cm-test/cm-13.0-20160403-UNOFFICIAL-mako.zip

Let me know so I am able to commit the changes, if it is an improvement.
[Nexus 4 Android Development] MrKaupo:
I think its cpu usage. doing nothing just screen on it is 1.5ghz.. Its too much.
[Nexus 4 Android Development] 0Kajuna0:
Thank you hnl_dk. I will try it later today and let you know.
[Nexus 4 Android Development] n0b0dy666:
Yes, please do something about GPS issues, I'm having trouble since first CM13 nightly (locking to a location which is way off from the correct one) :mad:
[Nexus 4 Android Development] hnl_dk:
Then please try the ROM I posted (that you just quoted).

Besides the change in GPS, it is the same as the nightly from yesterday.

I am personally not having any trouble with GPS here in Denmark, so I am not able to check if it is working better. Just that it is at least working as good.
[Nexus 4 Android Development] n0b0dy666:
I'll try it later and let you know ;)
[Nexus 4 Android Development] n0b0dy666:
Unfortunatelly, patch didn't fix my issue :( It still locks (well, most of the time) to the same wrong location when set to high accuracy. But no problem, keep doing what you doing, I'll be glad to test out your builds.
[Nexus 4 Android Development] hnl_dk:
Is this inside or outside?

Please try to check using something like GPS test, to see if it is actually using the GPS satellites.

Just to make sure, that it is not a cell tower problem (aGPS).
[Nexus 4 Android Development] 0Kajuna0:
I did some tests and Location behaviour in High Accuracy mode is good outside, when the GPS fixes to satellites. Unfortunately, once you go just slightly inside, the location goes crazy, changes from your actual location to random places 100 kms away, the blue area goes huge (maybe a couple of km), then small, then huge, small, huge, and so on... some times it behaves almost acceptably, some other times it is unusable. I'm checking with my colleague, who has stock android, and in the same room he has got a good constant location (just 50 metres off).

I flashed your zip over the previous one, after clearing dalvik and cache. Is that good enough or should I do a 100% clean install?

Thanks.
[Nexus 4 Android Development] hnl_dk:
Impressive. Where I live, if I am inside, the blue area is also changing, but that is going from 10 meters till 100 meters... that depends on the number of satellites the GPS is reading and how strong the signal is.

As I have changed the XTRA servers, you should maybe try to clear the GPS data.

Try to download something like: https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2

Open it up and go to the settings... Calibrate "Compass"... And then choose "Manage A-GPS state", when a window opens up, choose "Clear".

When that is done, try to reboot the phone... then it should have forgotten the previous GPS satellites, that it could have been locked at.
[Nexus 4 Android Development] 0Kajuna0:
I have cleared A-GPS data as you suggested. Went out, good location, went back inside... 3km blue area unfortunately. It has not switched yet to a completely wrong location though. While being inside but really close to a window, it is not fixing to any satellites. Not sure if this is normal.

Thanks
[Nexus 4 Android Development] hnl_dk:
I am looking forward to hear, if you get bad locations again.

The large blue area can also come if you have high houses around you. The radio signals get reflected on buildings, making it impossible to get an accurate fix.
[Nexus 4 Android Development] raz123:
Has anyone found a way to make LTE stick on reboot?
[Nexus 4 Android Development] 0Kajuna0:
Unfortunately bad locations are back. Now I'm sailing in the middle of the sea.
[Nexus 4 Android Development] hnl_dk:
Sorry to hear.

Just for the "fun" of it, could you please when you get the time, try to change your timezone from +2 till +1. It could be that the database of GPS satellites does not get that even though you are at the same longitude as Great Britain, you use the same timezone as Denmark.

It is a long shot, but it could be why you are suddenly "enjoying" the sea.
[Nexus 4 Android Development] 0Kajuna0:
I tried that + cleared AGPS data, and the location went jumping between Madrid and Barcelona (600km) and the blue area was the size of Algeria. Rebooted the phone and now has been looking fine for some minutes. Will go back to my actual time, I need alarms to ring at the right time :). Happy to try more things if you want.
[Nexus 4 Android Development] infra_red_dude:
This EnableNexus4LTE zip when flashed after flashing 33/107 hybrid modem let's LTE stick on reboot in my case on 3/28 nightly:

https://www.androidfilehost.com/?fid=23578570567720962
[Nexus 4 Android Development] raz123:
Thanks for posting. Didn't work on my end, as prefered network keeps resetting to WCDMA.

I'm on CrDroid's 2016-04-04's CM build. Looks like I'll have to abandon that ship.
[Nexus 4 Android Development] karan.sorathia:
is CM 13 aosp rom ??
[Nexus 4 Android Development] scambelo:
It is based on AOSP but is not a pure AOSP ROM. CyanogenMOD project enhances the AOSP codebase with several features and options not found in the official stock Android ROMS.
[Nexus 4 Android Development] 666biker:
Hello,

i am on latest nightly an using SuperSU beta 2.68 and I cant find option there (in SuperSU) that will works also after flashing new nightly. Do I need to install another SuperSU version? i am using it for toggle data application and tasker plugin. Thanks for help
[Nexus 4 Android Development] Bastlwastl2010:
I never understand why people use SU with CM.

CM have build in Superuser.
[Nexus 4 Android Development] 666biker:
as i mentioned, toggle data app. need supersu, via cm build-in root it is not working for me. I am using that toggling via Tasker
[Nexus 4 Android Development] hnl_dk:
If toggle data needs supersu, then send a bug report to the developer.

Overwriting the builtin su functionality can result in trouble, as it is used by the framework.

Have you tried in the quick tiles to click on the mobile network icon followed by turning Mobiledata off?

Is this not what toggle data does?

I know there may be one or two extra steps, when needing to go through the quick tiles, but it is working perfectly.
[Nexus 4 Android Development] 666biker:
I will check it, primary I am using toggle data application because it has extension for Tasker. So I am using this plugin for Tasker to automate toggle data when opening/closing web applications.
[Nexus 4 Android Development] redj12:
Hi guys. With the latest builds I have to unlock my phone (pin code) to turn off the alarm or answer when someone call me. I enabled something or it's just a bug ?
[Nexus 4 Android Development] 666biker:
during call I also noticed this "unlock" needed "feature" in previous nighties., I think, it is a bug.
[Nexus 4 Android Development] :
a new version of cm-13.0-20160415-NIGHTLY-mako has issues, the phone stops on the "Finish Boot"
[Nexus 4 Android Development] 666biker:
someone who tried latest build? 17042016? working?
[Nexus 4 Android Development] blassphemy:
I'm testing it right now. Seems to be fine so far. The lockscreen bug mentioned before should also be fixed.
[Nexus 4 Android Development] hnl_dk:
Working fine. LiveDisplay is now also working again.
[Nexus 4 Android Development] 666biker:
how automatic live display working? it is almost night and still day mode is active.

EDIT: working
[Nexus 4 Android Development] Nilsb7:
Partially, apparantly. It's now using the GPU which is not ideal (at all..) and it seems to stop working after a while.

more info here:

https://jira.cyanogenmod.org/browse/NIGHTLIES-2656
[Nexus 4 Android Development] Crysis2:
didn't got the point!

"I'd wipe and flash 11-5 again" what do you mean?

and every time i connect N4 to computer the Ui crash message pop up!
[Nexus 4 Android Development] stephanmc:
You don't have to. Actually, flashing gapps *after* firstly running the ROM without gapps lead to these force closes, due to Marshmallow permissions not set properly

Edit: I thought you "will" flash again, while you said you already did it. (aaargh I should improve my English :) )
[Nexus 4 Android Development] stephanmc:
Flash gapps in the same time than the ROM, else you'll have these force closes. So now you have to :

- wipe data + caches + system

- flash rom 11-5 zip

- flash gapps (just after the rom, without rebooting)

- flash other zips if you want (SuperSu)

- reboot
[Nexus 4 Android Development] bnitty:
lol meaning...... I'd wipe cache and system, flash the 11-5 ROM release, then gapps, and SU... but the dev said you don't have to. only telling what I did that worked for me... hopefully that made sense... ?☕
[Nexus 4 Android Development] stephanmc:
If you have a 64b PC you can use Virtualbox to emulate a 64b Linux, then build on it.
[Nexus 4 Android Development] Crysis2:
i flashed the same way you mentioned here!

and every time i connect the cable to phone (charger or computer) the force close shows up!

but i'll re flash it!

with the same order!

ouh! you mean release date!

sorry! :angel:
[Nexus 4 Android Development] J0SH1X:
my pc is 64 bit but

sadly my internet connection is only able to dowload max.200 kb/s so 39 gig would take 390000*5 s
[Nexus 4 Android Development] J0SH1X:
[MENTION=5395025]stephanmc[/MENTION] could you upload your android/system/vendor/lge/mako/mako-lge-blobs.mk ? as you now i wanna build for me but i use a vserver so i had to extract the propitarty files on my pc and got no make-lge-blobs.mk
[Nexus 4 Android Development] Packsman:
[MENTION=5395025]stephanmc[/MENTION] sorry for the OT, do we need just these two cherry picks http://review.cyanogenmod.org/#/c/112391/ , http://review.cyanogenmod.org/#/c/111336/ to make a functional build from source or some other hacking necessary?
[Nexus 4 Android Development] eneEYpsiloM:
can i install on my Samsung GT-I9305? I already have Lollipop 5.1.1. Thanxs.
[Nexus 4 Android Development] bnitty:
the 11-5 build has been so smooth for me. very impressed ?
[Nexus 4 Android Development] monish1995:
wheeeereeee ? am waiting !!! :D
[Nexus 4 Android Development] ChucCTaylor:
So far it's been smooth for me. One thing though I can't get to work is Google Now on Tap. I have it active but I get a app crash of Google app. Anyone else having that issue? Maybe it's just a glitch on my end.
[Nexus 4 Android Development] bnitty:
I did have this issue a few days ago, but since then app updated I can use it by tapping my widget without any issues...
[Nexus 4 Android Development] stephanmc:
Build 11-11 is out !

I also fixed "no voice audio while calling", reported since 11-07 build (which was removed because of that issue).

Let me know if it works for you.
[Nexus 4 Android Development] stephanmc:
No worries. I didn't see that the same things I made locally were also existing as a commit. Yes disabling these will fix some parts of the build. But you may need some others modifications to fix the build. Let me know if it's your case.
[Nexus 4 Android Development] stephanmc:
No, this is only for Nexus 4. Installing on an other device could brick your phone ^^
[Nexus 4 Android Development] stephanmc:
Thanks for the feedback, really appreciate

Lol I removed it because it had an issue with voice call since recents cm commits : we did hear just nothing after clicking call button.

But build 11-11 is out and includes my fixes on that. Let me know if everything works for you.
[Nexus 4 Android Development] Crysis2:
hi!

i still have issue with System UI!(made a full wipe of phone!Data + System + cache + Dalvik cache + Internal Storage!)

than add rom and gapp and SU zip files by

adb push X.zip /sdcard/x.zip

and than installed them as you said!(1- flash rom 11-5 zip 2- flash gapps (just after the rom, without rebooting) 3- flash other zips if you want (SuperSu) 4- reboot)(attach 1.png)(even wiped chach after flashing ROM but the same!)

and found one funny bug in landscape mode!(2.png & 3png)

Trusted Face keep crashing!(4.png)

and every time i want to open Mobile networks again it keep crashing!(5.png)

add some screenshots!

ready to do whatever you offer!

sorry for my bad english!
[Nexus 4 Android Development] stephanmc:
What ROM release did you flashed ? What gapps ?

And yes, for now "Mobile Networks" setting is not yet fixed (it's a known issue)
[Nexus 4 Android Development] VegetaSSJ5:
Not yet someone with a confirm that the snapshot of april works fine?
[Nexus 4 Android Development] matteus198701:
I have latest snapshot and no problems yet

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Android Development] Thrikiller18:
Are there battery modes lol?
[Nexus 4 Android Development] matteus198701:
No

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Android Development] mparmpas122321:
Flashed latest snapshot. No problems so far. The kernel has different settings i think. Minimum Frequency 1026 MHz. I will test the next 24 Hours and edit.
[Nexus 4 Android Development] Dazeon:
I was running the March Snapshot (clean flash) and suffering from severe battery drain. I upgraded to the April Snapshot using the built-in updater and I am still experiencing the issue. My device has also started to run very hot for no reason. I'd blame it's age but unless it's a huge coincidence, it never occurred on stock. There's something bizarre going on with Wakelocks and CPU frequency I believe. I have some screenshots from GSam when I figure out how to attach them with Tapatalk.
[Nexus 4 Android Development] mparmpas122321:
Hello there. Have you flashed any custom kernel or made any customizations to the CM one? I had normal battery life (better than Stock Lollipop) with both March & April Snapshots with no customizations, just Greenify.
[Nexus 4 Android Development] justmix4:
Someone who tried nightly build 20042016? Working, no boot loops etc?

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Android Development] lonsimbt:
I don't have any problems with this nightly up to now.