yashsingh1/xdaforums huggingface dataset:
[Nexus 4 General] maverick_hunter:
I believe CM changed that behavior back in CM 10.1. I specifically remember when it became a cherry pick on Jellybro and was puzzled by the change.
[Nexus 4 General] rskyline:
I see. IMO it looks better on stock like a pop up. But anyway it doesn't matter that much

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 General] ciano865:
I know that it's a REALLY known issue BUT changes in CM nightly from 10.02 (no AOSP drivers, as I can understand) don't fix it, increase them and I step back to 10.01 nightly.

Just my feedback ;)
[Nexus 4 General] maverick_hunter:
I agree, I preferred the stock behavior.
[Nexus 4 General] axsdenied1:
It seems to work if you don't use zoom.
[Nexus 4 General] cgulliver:
Anyone been able to set the color correction to match Hospital or Kelgu? Wish that loadable profiles were supported.
[Nexus 4 General] Packsman:
I would like to be able to use two profiles: one with sound + vibrate option and the other with just sound. I set phone app group in profiles to vibrate on, but when i get a call it shortly vibrates one time and then stops. Did anyone have the same problem and knows how to fix it?
[Nexus 4 General] Zehlek:
Anyone having issues sending SMS with latest 10/05/13? I was able to and now it keeps saying message not sent. I flashed to another rom and it works
[Nexus 4 General] BossNexusS:
Is it just me or when I have active notification on and when I open a notification from there my icons in my status bar disappear and the only way to get them back is to hold the power button until the shutdown menu comes up.. Does anyone know why? Or is it just because it's in early stages?
[Nexus 4 General] CMNein:
No issue here. Are you running stock build without any modifications?
[Nexus 4 General] BossNexusS:
Yeah everything is stock so I'm not sure why..
[Nexus 4 General] FRLinux:
Switched to cyanogenmod 10.2 nightly from stock and looks very good. Nice work team.
[Nexus 4 General] drawde40599:
Ive been sms and mms all weekend works perfectly 5th and 6th builds

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

They r sorta with 3rd party apps use trickster or faux app

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

I upgraded from stock 4.3 but ya works fine with no issues. Not what u wanna hear but Try full wipe reinstall new build
[Nexus 4 General] KevinChaos:
Could it be the modem I'm using? I don't know which modem is included with the builds, but I flashed the one in the cm thread that says "android 4.3 modem" I'm assuming it's the same one though...
[Nexus 4 General] drawde40599:
Sorry i just figured u were on correct one but it should end in 84 http://xdaforums.com/showthread.php?t=2087227 last time I had some kind of issue like that, no matter what I did didn't fix it till i wiped...
[Nexus 4 General] KevinChaos:
Yeah my modem ends in 84. Crap. I don't wanna full wipe :(
[Nexus 4 General] drawde40599:
U could try the normal stuff, shut off pull sim card, turn on let boot shut off, reinstall sim, reboot. Or , remove apn, reboot, reset apn reboot, Usually that stuff for data connection issues but worth a try. U could also delete sms app reboot, pull sms app from build put in system app folder, fix permissions reboot.
[Nexus 4 General] otariq:
Does anyone have good gamma settings? First time I'm using the cm one always used franco before
[Nexus 4 General] Fr33L4nc3r:
Baseband (radio/modem, whatever you call it) is not included in the nightlies, and never will.

As for your issue, I would backup the SMS app/storage with Titanium Backup or any SMS backup app, then clear cache / data of the SMS app and remove / reconfigure the APN.

If it still doesn't work after that, make a nandroid backup, then wipe your device and see if it's better.
[Nexus 4 General] Slurpino:
I found a problem with my all app.. I don't know why they open in tablet mode and fc immediatly. Now I see with 20131001 and cmkernel problem persist, when I use other kernel I haven't problem to open my app.. A fix for kernel pls
[Nexus 4 General] Zehlek:
Anyone not able to change cycle date in data usage?
[Nexus 4 General] Kc_Nirvana:
That option is for limited data plans.

Activate the option and you could change
[Nexus 4 General] rskyline:
Enable data first.

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 General] ssauger:
phone is off

I have every few days the problem that the phone is off but can not understand why. It can then only be started by pressiing the power button for a long time. At the moment I'm on the nightly from 06.10 (no custom kernel or so), but also occurred on earlier nightlies. I received a replacement unit from Google a few weeks ago, so i can not be sure if its a hardware defect. Maybe someone can look into the attached last_kmsg if that is useful, I have directly copied after I started the N4 again. Thanks in advance.
[Nexus 4 General] pmorrsn:
After about 3 weeks troubleshooting support by Google play, they tell my they do not support play movies on custom roms.

Go figure.

You'd think they would cut to the chase on day 1.
[Nexus 4 General] Fr33L4nc3r:
I can't tell since I never "bought/rented" a movie on the Play Store, but it feels like a desperate Google CSR complete B**S*** answer ...
[Nexus 4 General] thracemerin:
Officially Google doesn't support anything you do to your phone once you 'fastboot oem unlock' so the CSRs that pretended they could/would help are the ones who were wrong, not the one who said they don't support software on custom ROMs.
[Nexus 4 General] pmorrsn:
I would agree with you, they just need more training support to get you an answer with less effort and time.

Does anyone have a work around for playing Google movies?
[Nexus 4 General] thracemerin:
True, the failure in training is that they strung you along claiming to be able to help when they should have just told you they couldn't right away.
[Nexus 4 General] drawde40599:
Is there a hack somewhere to fix the video recording ?
[Nexus 4 General] Razer(x):
Cyanogenmod is getting very disappointing, this graphic driver issue is the last one for me. I'll move to another rom
[Nexus 4 General] thracemerin:
You could just make a custom kernel with the CM patches in it (...or I could), or use the revert zip from the dev thread.
[Nexus 4 General] yaatzek:
Well few days ago I was also mad at deadlocks and other stuff so I moved to slim and after that I thought, well long time no stock, so maybe I'll stay on stock till kitkat is out... I couldn't do it :) stock is ok, but it's so naked, besides i think I am addicted to cm. Anyway after i clean flashed stock i returned 3 days ago to cm... And it's ok, no bugs, deadlocks are gone. Don't know maybe it's just luck or something else. For now I'm happy.
[Nexus 4 General] rskyline:
Farewell...
[Nexus 4 General] Fr33L4nc3r:
I do understand your point. I was not implying Google and this particular CSR should help pmorrsn fixing the issue at hand ("support"), but merely that play movie should "work" on CM.
[Nexus 4 General] goTouch:
Why did CM move to CAF? Didn't understand this. It broke almost every good custom kernel.

Is CAF implementation really good? Does someone have any performance comparison?

Enviado de meu Nexus 4 usando Tapatalk 4
[Nexus 4 General] thracemerin:
The drivers provided from Qualcomm (CAF) are newer and more highly optimized for Qualcomm chipsets than those that Qualcomm licenses to AOSP.

To your first point, CM has never recommended using custom kernels nor have they provided support if you do, they have also in the past diverged from the "standard" implementation of certain things resulting in incompatible custom kernels. There is a fix (it's in the dev thread) to allow you to continue to use your chosen custom kernel with the new CM, but it reverts the library optimizations so you lose out on the benefits.
[Nexus 4 General] CMNein:
People with tinfoil hats will theorize it has something to do with "Inc.".
[Nexus 4 General] rskyline:
Anyone knows a solution to this: Everything i flash a new build, it wipes all the system data, so apps like Maps get wiped.
[Nexus 4 General] jawz101:
Which gapps did you use?
[Nexus 4 General] rskyline:
Official ones with emoji and photosphere addon

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 General] jawz101:
Is it just certain apps that get wiped? like just the Google apps?

By official, do you mean the gapps from goo.im?

Are you talking about when you're upgrading cm from nightly to nightly or coming to & from another ROM?

I just wipe cache & dalvik cache if I'm on a same ROM.

If I'm switching ROMs I'll use something like Titanium Backup , then wipe cache & dalvik cache and system & data (but never internal storage), install new ROM and restore apps with the backup app I used.

I also keep backups of several ROMs if I think I'm going to switch back & forth & just keep the backups updated if I'm switching often.

... but back to the original thing. If you're only wiping cache & dalvik cache between nightly builds of any of the distributions you should be fine. If switching distributions, backup & wipe all 4 - not internal storage, though.

The only other thing I was thinking was the gapps thing. For instance, ParanoidAndroid's gapps installs all of them to the system partition because it makes for more room for any other apps you install. I don't like that way but whatever. It just confuses me and I'd rather pick & choose the Google apps I want since I don't use all of them.

I'd try to find out where it's installing Maps when it has worked vs. when it hasn't.
[Nexus 4 General] rskyline:
Do you know which kind of optimizations we'll get with those drivers? And if we will get better results of any kind? Or maybe we'll have tha same behavior as before?

---------- Post added at 03:38 PM ---------- Previous post was at 03:35 PM ----------

Talking specifically about cm. So from cm to cm. Google maps when installed from play store get stored at system/app AFAIK. So it get wiped when flashing a new build. I just flash without any wipe

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 General] jawz101:
Mine is stored in data/app. It's weird. There's no rhyme or reason to where this crap gets stored. I have a copy of gmail in both places.
[Nexus 4 General] rskyline:
I'll try that again. I'll report back what i got.

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 General] thracemerin:
I can't be too specific because I haven't looked into it too much, but Qualcomm drivers that are licensed to AOSP are basically frozen at the point where they decide to release them for Nexus devices (generally whenever a new Android version is pushed) where the ones from CAF continue to evolve, bug fixes and optimizations are made on an almost daily basis, but that doesn't mean that they are noticeable in real world use.
[Nexus 4 General] blomc:
Anyone got problems with msm_hsic_host wakelocks? I have to reboot my phone after every charging to get decent baterry live. This problem started around 25-26 09 nightlies.
[Nexus 4 General] jawz101:
Quoting [MENTION=4303511]thracemerin[/MENTION]

http://xdaforums.com/showpost.php?p=38227972&postcount=8
[Nexus 4 General] thracemerin:
The fixes I was discussing there were for the 4.2.x kernel, most (at least the ones that we're sure helped) were merged by Google for 4.3 so the state of the situation is about as good as it gets.

There is some good discussion including a fairly good explanation written by myself here: http://xdaforums.com/showthread.php?t=2102986&page=85
[Nexus 4 General] blomc:
So as i understand, ther is no problem with rom or kernel. But i don't understand why there is so significant difference with wakelocks and battery usage before rebooting the phone after charging. Before i charge the phone i got around 1-2% battery usage per hour after charging it's around 5%, and after reboot again about 1-2%. No changes in using apps or cell reception, wifi networks, still the same conditions. Any ideas? It's a little bit weird.
[Nexus 4 General] thracemerin:
The battery shows 100% but it's not actually at 100%, to prevent battery damage and maintain battery life the charging chip begins to trickle charge at 92% and when it gets up to 95%+ it begins cycling the charge, as a result the first few % from 100% burn off much more quickly than average, when you reboot it resets the charge chip which gives a more accurate battery percentage in this zone.
[Nexus 4 General] andy o:
FWIW guys, to say something positive, these patches seem to finally have done away with the delayed notifications on WiFi. Not having them for a few days since I had to come back to the CM kernel. Would be nice if others who were still having them after 4.3 confirmed.
[Nexus 4 General] ziddey:
Yes, a recent commit enabled arp offloading. Note that arp offloading requires the new radio, or at least the wifi component of it. .54 and earlier have the bug that mangles the mac address when using arp offloading. It's fixed in .84 (and possibly .83).

I've been running with arp offloading for a few weeks now, and everything seems fine. It was enabled in JWR66N (leak) but disabled for JWR66V (official), with JBQ saying it resulted in suboptimal battery performance. Results seem largely the same for me, although perhaps my usage is atypical (airplane mode + wifi + tcp sip client when at home)
[Nexus 4 General] otariq:
What are delayed notifications on WiFi? What type of notifications are delayed for you guys? Like let's say a notification from Facebook? I don't think I've ever experienced this or if I did I never noticed it. And these deadlocks are killing me constantly getting them today especially when deleting something while typing. I think I've had more running cm kernel than I did when I had Franco. Did a clean wipe last night too.
[Nexus 4 General] andy o:
See here http://xdaforums.com/showthread.php?t=2072930

It's not very noticeable unless you're using VoIP which needs the phone to ring instantly.

I was under the impression that radio didn't affect WiFi?
[Nexus 4 General] thracemerin:
It doesn't
[Nexus 4 General] andy o:
IIRC you were one of us still having problems with delayed notifications even after the various "fixes" came out. You still having trouble? I don't have to change anything now, even the ARP relevant strings on that WiFi config file are set to 0.
[Nexus 4 General] thracemerin:
Mine doesn't work any differently with the flags 1 or 0, it also makes no difference which radio I use, if it works it's almost definitely external network infrastructure that is the cause. I can tell you that with a completely garbaged radio partition I can continue to use my N4 on WiFi without any noticeable difference to anything.
[Nexus 4 General] ziddey:
That's some misinformation you've been repeating over and over. I know you've said you corrupted your radio and yet still had working wifi, but I can tell you for a fact that the wifi component of .84 fixes arp offload mangling (broken in .54 and earlier). Refer to the hybrid modem thread to get some information on the different components of the radio. Mount it and do some swapping if you don't believe

It's generally agreed that .84 has poor 5ghz wifi performance, and that .54 or earlier is best. However, I flat out have not been able to connect to any 5ghz APs so I can't speak personally.

I can confirm for a fact that arp offloading will indeed mangle the mac address on .54 and earlier, and that it's resolved on .84. A workaround for this for anyone who wishes to use an earlier wifi component would be to spoof the mac address to one that mangles to the same address (of the form A:B:B:A:C:C).

This thread discusses arp offloading.

And here is a thread where morrislee makes "hybrid" radios by replacing certain components of different radios (radio partition is FAT after all). And specifically, there is evidence of poor 5ghz performance on .84.
[Nexus 4 General] thracemerin:
Hybrid modem doesn't fix it, my radio partition is full of 1s and 0s at the moment, it doesn't make any difference to WiFi performance or anything else other than my baseband says Unknown. I'm willing to accept that I might be wrong, but none of my testing supports your contention that WiFi is affected in any way by anything in the radio partition.
[Nexus 4 General] rskyline:
The camera flash is definetely broken here. If you dont manually focus it will last about 3 seconds to take the picture and with strange colors/focus. Any workaround?

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 General] ziddey:
I'm not sure what you mean by "fix." You don't have a way of flashing a working radio back on your device? I'm assuming your issue isn't simply related to twrp/selinux?

Again, I cannot for the life of me get my device to connect to ANY 5ghz AP. That said, I haven't tried anything other than CM10.2 nightlies, so that's not saying a whole lot. I don't have first hand proof of the 5ghz slowdown on .84 but there is evidence from enough people that I don't think smoke is being blown up my ass.

As for arp offload mangling, I do have hardcore first-hand results that show that .54 mangles A:B:C: D:E:F to D:C:B:A:F:E, while .84 does not. Testing was done back to back by *only* flashing radios. Test was done on a recent cm10.2 nightly, with arp offloading enabled.

If there's anyone out there on .54 or earlier and on a recent cm nightly (with arp offloading enabled), you can easily test this by trying to ping your phone a minute or so after turning your screen off. The pings will fail. You can then check your arp table to confirm the mac address has been mangled:

arp -a xxx.xxx.xxx.xxx

After flashing .84 (or at least the wifi component), the first ping or two may still timeout (looks like it takes a while / few requests for the phone to arp reply when offloaded), but will then start replying normally. The arp table will of course then also have the correct mac address.
[Nexus 4 General] thracemerin:
I just reflashed the .84 modem, with a full stock build, manually edited the ARP flags to 1, I continue to have the same ARP problem you say is fixed between .54 and .84, I also can see and connect properly to 5ghz with no discernable difference in speed.

I did unpack the radio image and there do appear to be WiFi components in there, but that doesn't explain why I can flash an empty file in that partition and it still works the same.
[Nexus 4 General] ziddey:
your mac address is still confirmed to be mangled with .84 radio?
[Nexus 4 General] andy o:
I can connect fine to my 5GHz Netgear WNDR4000. However when I had DD-WRT installed (basically what I bought it for) both my N4 and N10 used to get disconnected when they weren't very close to the router, but only after a couple of days. It was weird. For a couple of days they would work fine in my bedroom, at exactly the same spots, then nothing, until I got to the hallway and about 2m from the router. I think it was a DD-WRT bug though. Always ran the latest CM nightlies on both.
[Nexus 4 General] thracemerin:
Hmm.....no, it says <incomplete> in arp -a
[Nexus 4 General] ziddey:
That bothers me as well. Incomplete is when it hasn't gotten an arp reply yet despite sending arp requests. It can take a while for it to respond when offloaded to the wifi chip (far longer than it should / does when the screen is on). You'll need to keep the ping running until it does reply (or in the case of the following snippet, it will have responded eventually).

Here's a run where I try to ping my phone but then immediately abort:

ziddey@ijib:~$ arp 172.16.100.199
172.16.100.199 (172.16.100.199) -- no entry
ziddey@ijib:~$ ping 172.16.100.199
PING 172.16.100.199 (172.16.100.199) 56(84) bytes of data.
^C
--- 172.16.100.199 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

ziddey@ijib:~$ arp 172.16.100.199
Address HWtype HWaddress Flags Mask Iface
172.16.100.199 (incomplete) eth0
ziddey@ijib:~$ arp 172.16.100.199
Address HWtype HWaddress Flags Mask Iface
172.16.100.199 ether 10:68:3f:3c:da:b8 C eth0

Obviously still not ideal but it does work now. I'm assuming the issue with earlier "radios" had to do with an endianness confusion (big vs little)

I will now flash the .54 radio to reconfirm my prior results. Update in a few minutes.

Update: confirmed:

ziddey@ijib:~$ arp 172.16.100.199
172.16.100.199 (172.16.100.199) -- no entry
ziddey@ijib:~$ ping 172.16.100.199
PING 172.16.100.199 (172.16.100.199) 56(84) bytes of data.
^C
--- 172.16.100.199 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

ziddey@ijib:~$ arp 172.16.100.199
Address HWtype HWaddress Flags Mask Iface
172.16.100.199 (incomplete) eth0
ziddey@ijib:~$ arp 172.16.100.199
Address HWtype HWaddress Flags Mask Iface
172.16.100.199 ether 3c:3f:68:10:b8:da C eth0
[Nexus 4 General] thracemerin:
Yeah, I dunno what's up.

Anyway, you are correct about the WiFi components in the radio image, I don't know where I heard that it had no effect in the first place, but clearly I was wrong, I should know better than to repeat things I hear without checking them out myself.
[Nexus 4 General] ziddey:
Here's with .54 where arp offload mangles the mac address:

ziddey@ijib:~$ arp 172.16.100.199
172.16.100.199 (172.16.100.199) -- no entry
ziddey@ijib:~$ ping 172.16.100.199
PING 172.16.100.199 (172.16.100.199) 56(84) bytes of data.
^C
--- 172.16.100.199 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

ziddey@ijib:~$ arp 172.16.100.199
Address HWtype HWaddress Flags Mask Iface
172.16.100.199 (incomplete) eth0
ziddey@ijib:~$ arp 172.16.100.199
Address HWtype HWaddress Flags Mask Iface
172.16.100.199 ether 3c:3f:68:10:b8:da C eth0

So at the end of the day, as far as "delayed notifications" is concerned, those who are running older radios *should* see no difference in behavior, since the phone essentially goes dark in either scenario.

However, in the event that the user's router did proxy arp, enabling arp offload + old radio *could* potentially introduce such delayed notifications that didn't exist before.
[Nexus 4 General] thracemerin:
Yeah, I figured out why it was incomplete, my linux machines were VPN'd to work, when I switched them to the correct network it works. Weird, I could have sworn I tested this when 4.3 first came out and it didn't work....:confused:
[Nexus 4 General] ziddey:
If you're referring to stock JWR66V, unless you manually enabled it, it was disabled by default, so the phone would have still gone "dark" after the screen goes off.

Hmm, guess I've derailed this thread a little more :p

I'm glad I'm not crazy. I definitely noticed a change in flash behavior recently. Sure, people say that "you need to know how to take pictures when it's dark" but I was in a situation where I handed my phone off to a stranger to take some pictures, and absolutely nothing came out but a bunch of pictures of legs and shoes. Then got a bunch of insults about my phone. :(
[Nexus 4 General] thracemerin:
I have the flags set to 1 manually, at the risk of derailing the thread more, thanks for setting me straight on this :D
[Nexus 4 General] rskyline:
Came back to stop because of that. I get strange back sound like someone posted here before, like the camera cracking and automatically crashed and rebooted. Too bad really. Tested on Cm cam and Google cam.

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 General] maverick_hunter:
I just tested this out. I took a couple pictures just fine, until I got one with a weird crackle sound then reboot.
[Nexus 4 General] CMNein:
RC did refer to the flash fix commit for CAF as a 'bit hacky' or something along those lines.
[Nexus 4 General] noonecanhide:
Has someone a copy of the last nightly before this big f*ckup called CAF happened (2013-10-01) ? It's not on get.cm anymore...
[Nexus 4 General] tvisforme:
Which build of DD-WRT? I'm running the latest v3 on a 4000 and both the N7 (2012) and N4 connect well. (The N7 on 2.4 Ghz of course.)