yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Roland Stone:
Clean flash of 12/8 Skank nightly gives me NO keyboard, even with separate flash of Gapps. Full wipe data and cache. Tried two different GAPPS same issue. At my wits end. I can't even enter the password for my wifi at the set up stage. Any ideas? Going back to 12/2 for now.

---------- Post added at 07:32 PM ---------- Previous post was at 07:11 PM ----------

So I just did a clean install of 12/2 Euroskank with PA Gapps (same Gapps I used above) and now my keyboard is back. This is after TWO clean attempts to install 12/8 Euroskank with GAPPS that both resulted in no keyboard.

Guess I'll just stick with 12/2 for now. It's been working well for me and I'm not even sure what benefits, if any, might come with the 12/8 nightly. So far recent Euroskanks and the recent Official CM nightlies have been nothing but trouble for me. Couldn't even get the official CM11 nightly to get past the splash screen.
[Samsung Galaxy Nexus] hxdrummerxc:
I just installed this rom last night. I did a full wipe / factory reset, and a new clean install of franco kernel and the pa4.4 gapps.

Everything seemed fine. The rom was snappy. But I have no 4g connection at all. It won't even let me turn it on. Every time I go to the settings 3G is selected. I select 4G, and nothing happens. If I go back into the settings, its back on the 3G option again. No 4G at all.

Also, network performance is terrible right now. It doesn't matter if im on 3G or if im using my home wifi. The play store loads only 50% of the time. It will come up and say times out. I will close it and reopen it and then it will load. Same thing with the browser, loading a website will sit there forever. If I try again sometimes it will finally load. I don't get it. Anyone else having these issues?
[Samsung Galaxy Nexus] Roland Stone:
I drive a BMW and I'm running Euroskank's 12/2 CM 11 nightly for Toro. Using Google Play Music, metadata was finally working properly for me in CM 10.2 but it is borked in CM 11. The first song in a playlist does transmit it's metadata to my BMW display properly. But after that subsequent songs still show the metadata from the first song. Very annoying! I'm seriously contemplating switching back to CM 10.2 until this gets fixed. Very disappointed that KitKat is a step backwards for Bluetooth metadata song info! From what I can glean online, this isn't just a Toro problem, Nexus 5 owner's are having trouble too. I wish someone would look into this since it "almost" works.
[Samsung Galaxy Nexus] RepeatUntilTheEnd:
You should look into it and let us all know when it's fixed. Thanks
[Samsung Galaxy Nexus] spearman792:
I don't know if anyone else noticed this (or if it's just placebo), but I feel like beginning with yesterday's build (12/8) the GPU has been practically entirely fixed. I don't have anymore weird animation stuttering in apps like feedly or G+

Just thought I'd say thanks to the cm devs and fits (even though they probably won't see this)
[Samsung Galaxy Nexus] klobkelosh:
Agreed. The screenshot glitch is fine today as well. Webview working like a champ. Very happy
[Samsung Galaxy Nexus] Roland Stone:
I will look into it as best I can. By the way, I apologize if my message came off wrong. I only included the make of the car because some cars have different Bluetooth profiles than others. I wasn't trying to brag.

By the way I am now running Euroskank's 12/9 nightly with no issues other than Bluetooth metadata.. I use the Photosphere corrected 11/19 PA GAPPS and the Pano Fix zip.
[Samsung Galaxy Nexus] RepeatUntilTheEnd:
No worries. I was just giving you a hard time... Sometimes its easy to get caught up in the frustration of software not working properly and forget that we have next to nothing to do with how well it works. Bug reporting is important, but it needs to be done a certain way and understood that these builds are not stable.

I'm still having issues with LTE. The only other new bug I've found is that the insecure lock screen setting in profiles doesn't work. Other than those two things this is completely stable for my purposes; I'm sure they'll get worked out over time.

Thank you, fits, and all other devs who have gotten us this far! I can't believe I have 4.4.1 on this phone already! Reminds me of when ICS hit the OG Incredible haha
[Samsung Galaxy Nexus] kuronosan:
It won't let me disconnect my nexus from my smart watch's internet, that isn't turned on.
[Samsung Galaxy Nexus] Roland Stone:
I don't know much about this sort of thing, but how difficult would it be to revert CM 11 to the Bluetooth stack in CM 10.2 that had working metadata?
[Samsung Galaxy Nexus] RepeatUntilTheEnd:
Oh, that would be extremely difficult and very time consuming. It would probably take a few weeks or even months, depending on how much time you had to devote to it.

Unless you already knew how to do it. Then it could be quite easy...
[Samsung Galaxy Nexus] Roland Stone:
Well then I guess the question is, does anyone around here (like maybe you for instance) already know how to do it?
[Samsung Galaxy Nexus] fcisco13:
Battery is messed up in 12/11 i believe, and i can't find battery settings.

WHATCHOO TALKING BOUT WILLIS?
[Samsung Galaxy Nexus] RepeatUntilTheEnd:
12/13 has fixed a bunch of stuff for me.

LTE is fixed. Can't toggle on quick settings tile, but manually changing works now.

Battery percentage is fixed; a separate option has been added to show it.

Insecure lock screen profiles has been fixed. Hide error and dots on lock screen pattern has been added, too.
[Samsung Galaxy Nexus] blackhand1001:
Anyone elses home button noticeably laggy compared to cm10.2 and even compared to the back button in cm11. It has a noticeable delay and the animation is laggy. The back button in comparison is instant.
[Samsung Galaxy Nexus] cujo6801:
Yoshi....

To kool...

sent from the DOG pound
[Samsung Galaxy Nexus] klobkelosh:
Word of warning - don't start using that LTE toggle just yet. I accidentally tried it out today and it actually functions now, but once pressed you can't get LTE signal back at all. Rebooted a bunch of times, messed with all the settings, nothing. A clean flash fixed it all up just fine so not a very big deal but annoying when you press it accidentally and want to get online right afterward.
[Samsung Galaxy Nexus] fcisco13:
Trickster mod not restoring my settings, anyone?

WHATCHOO TALKING BOUT WILLIS?
[Samsung Galaxy Nexus] Roland Stone:
Not much activity around these parts lately. I guess no news is good news. I just flashed the 12/24 nightly with no problems. Is anyone still working on a new Kitkat Kernel for the GNex or did interest in that fade once the graphic glitches were fixed with workarounds in the ROM?

Does Cyanogen Mod let you change the carrier name?
[Samsung Galaxy Nexus] dteich02:
Anyone else having problems with the camera on the 1223 build?
[Samsung Galaxy Nexus] fcisco13:
What kind of problems? Fc?? If its fcing dload this one and replace it in system/app change permissions and reboot.

https://www.dropbox.com/s/xtq9eakcrcqqf8v/Camera2.apk

WHATCHOO TALKING BOUT WILLIS?
[Samsung Galaxy Nexus] TuxDroid:
Looks like the fix is on Gerrit now. More info via http://forum.cyanogenmod.com/index.php?/topic/84656-Cm11-121913-Nightly----No-Camera!?#entry433113
[Samsung Galaxy Nexus] KillerVamp09:
Mine crapped at as well on another ROM but the fix seems to be dialing "#"#4636#*#* selecting phone settings and setting the network to gsm/CDMA auto (prl)
[Samsung Galaxy Nexus] Roland Stone:
Is it still necessary to flash the Panorama fix and the special Photosphere GAPPS or have those fixes been integrated into the ROM yet?
[Samsung Galaxy Nexus] jlvlawrence:
Photo sphere has never been included in CM.
[Samsung Galaxy Nexus] Roland Stone:
Why not? Is it in other Jellybean Roms? Every time I flash a new CM nightly I have to go back to the modified GAPPS from November just to get Photosphere. So if it is possible to have both Jellybean and Photosphere (and Panorama with the Pano_Fix.zip) why not integrate them into the ROM?
[Samsung Galaxy Nexus] dereaper:
because not everyone wants photosphere, just install the photosphere add on from banks gapps page
[Samsung Galaxy Nexus] fcisco13:
I believe these are Kik Kat.

WHATCHOO TALKING BOUT WILLIS?
[Samsung Galaxy Nexus] Roland Stone:
Yes, my mistake I meant KitKat, not JB.
[Samsung Galaxy Nexus] fcisco13:
Can't you just back it up with Titanium and restore it once you flash new rom? Would this be easier?

WHATCHOO TALKING BOUT WILLIS?
[Samsung Galaxy Nexus] Roland Stone:
My concern was in flashing an old set of GAPPS just to get Photosphere. I see now that there is a Photosphere "add-on" that's supposed to work with the GNex. I'll give it a try next time I flash a nightly. And then I'll continue to flash Pano_Fix.zip to get panorama. I don't think its too much to expect that both Photosphere and Panorama work with my KitKat Gnex.

And for the record, Bluetooth metadata is still borked too. It might "appear" to work on first glance, but in subsequent songs the metadata stays stuck on the first song.

Seriously, if I knew for a fact that Photosphere, Panorama and Bluetooth Metadata all worked flawlessly on a Kitkat Moto X, I might be tempted to buy one of those off-contract. Still a trade-off though. I'd keep unlimited data but lose tethering. :<
[Samsung Galaxy Nexus] JkdJedi:
HOLY BAT THREADS!!!!! Fitz HAs Done it Again!!!! Thanks Dude!!!!
[Samsung Galaxy Nexus] MBQ_:
Why so ecstatic?
[Samsung Galaxy Nexus] Sheetzie03:
This

?Turnt Up-KK Metal with THE best Audio Improvement Patch out there↔@Misledz Xlouder?
[Samsung Galaxy Nexus] Calamityx1:
Hey guys, I was wondering if this ROM has navigation button customization. I saw that AOKP has KitKat available for the G-nexus, but when I tried it out, I barely saw and customization options. At all.
[Samsung Galaxy Nexus] klobkelosh:
Anyone running fitsnugly's build on toro - how is your data connection? I tried yesterday's nightly, but phone wouldn't hold 4g for more than a few seconds - same as official cm for me. Wish I knew what commit caused the issue...we might ask fits to revert it.
[Samsung Galaxy Nexus] Whompy:
There was talk of bionic commits from the 18th causing all sorts of grief with toro, but I haven't had a chance to investigate. I saw it in the nightly thread.
[Samsung Galaxy Nexus] klobkelosh:
Thanks whompy!

I'm happy to report, after extensive testing, that reverting to the version of bionic (libc.so) from the 1/17/13 nightly does seem to fix the network connection. I've tested the fix on clean builds of fitsnugly's latest and the official cm nightly from yesterday and LTE works properly. I'm now testing upgrading my working 1/17 nandroid with cyandelta - fingers crossed.

Please help me test. Flashable zip for the bionic rollback patch is at toro-downgrade-bionic-to-1.17.13.zip - 332.05 KB
[Samsung Galaxy Nexus] drumst1x:
I'll cross-post this in both threads, but i've been running fitsnuggly's CM builds lately, and i've had the same issues everyone else has been having with sleep of death and rare 4g and crappy 3g.... I'm currently on the 2014-01-20 (Jan 20th) nightly and I just flashed this rollback. IMMEDIATELY upon rebooting i went right into 4G and have had great service since (only about 10 mins, but coming from what i had, it's impressive). Great job, and thanks so much for providing this. Even tho it's only a "hack" the results are great for me. Hopefully CM team can figure out what really went wrong and truly fix it, then we can stop with the rollback hack.

Since you seem to understand what went wrong and what needed to be done to rollback, can you explain what libc.so is, and why it's related to Bionic? Is that referring ot the Droid Bionic phone, or some piece of CM known as "bionic"? Curious to know more details, even though i'm already back up 'n running.

Thanks so much.
[Samsung Galaxy Nexus] klobkelosh:
Glad it's working for you. Bionic discussed here has nothing to do with that embarrassing device also named bionic. It's a core android component. Read more than your want to know at http://en.m.wikipedia.org/wiki/Bionic_(software)
[Samsung Galaxy Nexus] Roland Stone:
This will be my last post ever complaining about the flawed implementation of Bluetooth metadata on the GNex. Why? Because I have a new Moto X with Kitkat and metadata song info works perfectly, updating properly to my car as songs change while I stream from Google Play or Poweramp. As I've posted before, on the GNex w/Kitkat it would only show the first song's info and then get stuck there through subsequent songs.(It did used to work right with later versions of Jellybean, but Kitkat broke it.)

Anyway its been a long fun ride with the GNex, but I'm out of here! The Moto X is a nice step forward. Nothing to miss about the GNex yet excvept maybe the weight of my humongous "No Lemon" 5400 battery! At least I always knew when it was in my pocket!
[Samsung Galaxy Nexus] klobkelosh:
Congrats, and bon voyage!
[Samsung Galaxy Nexus] jlvlawrence:
I also recently upgraded from a gnex to a moto x. Its so nice not having to monitor my battery constantly! I bought the moto maker version, so no ROM flashing for me. There are definitely a few things I miss from CM, but overall, I'm pretty happy. Enjoy yours!
[Samsung Galaxy Nexus] Roland Stone:
Well you can still root your Motox even if its not the Developer Edition. But its a process not for the faint of heart! I won't go into the details here of why you might want to try.

I'm not missing my GNex. It doesn't have quite the sentimental value of my OG Droid. Not sure what I'll do with it. Maybe send it to Belize. That's where my old Kyocera 7135 went.
[Samsung Galaxy Nexus] klobkelosh:
Jealous of all the motox talk...

Team vanir found the source of the bionic problem. http://vaniraosp.goo.im/#/c/9911/

[MENTION=2419035]fitsnugly[/MENTION] would you be able to cherry pick the revert?
[Samsung Galaxy Nexus] klobkelosh:
I also submitted to Bekit, the cm maintainer for toro. Response - "Thanks! I'll take a look at it and either do a similar revert, or get the code fixed up."

Update : looks like it should be in the next build
[Samsung Galaxy Nexus] drumst1x:
This is great news! Thanks Klob for following up with this issue. That flash revert fix you provided has been working great for me.

Now I just have to wait for others to flash it and say it's all good :)
[Samsung Galaxy Nexus] blackhand1001:
I left my Galaxy Nexus for a Dev edition moto X as well. Definitely the only real option for verizon users to get a real replacement for the galaxy nexus. The phone is awesome. Amazing battery life and reception. The screen is so much better as well.

I also have a commit that I submitted that would be nice to cherrypick to test and hopefully post a code review. It brings back the titlebar autohiding to the aosp browser which has been broken in 4.4 because of the switch to chromium webview. I rewrote some of the code to make it compatible.

http://review.cyanogenmod.org/#/c/59839/
[Samsung Galaxy Nexus] MBQ_:
heads up guys:

02/21 build results in constant hot reboots and com.android.Phone force closes
[Samsung Galaxy Nexus] klobkelosh:
Not here. 2/21 running without a hitch. No force close, no not reboots.
[Samsung Galaxy Nexus] Shadow Death:
I wanted a Moto X but the phone is just too small for me. I have baseball mitts for hands so I don't get the luxury of using a smaller phone. To me the Moto X just feels a bit on the small side. Especially compared to the Gnex. :/
[Samsung Galaxy Nexus] Sheetzie03:
I lold at 'baseball mits' haha

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] blackhand1001:
Well in defense of the Moto X the screen is actually bigger than the galaxy nexus's.
[Samsung Galaxy Nexus] somato:
Yep, same thing here... It started when I hung up after the first outgoing call. Time to restore the nandroid. :(
[Samsung Galaxy Nexus] klobkelosh:
Looks like massive changes to telephony in the latest build. I tried dirty flashing but note getting the constant phone has stopped dialog. Managed to clear phone app data but now acore is stopping. Might want to clean flash this one.
[Samsung Galaxy Nexus] MBQ_:
Clean flash of official 0303 cm results in the constant fc
[Samsung Galaxy Nexus] klobkelosh:
Mbq, you flashing dirty v kernel on this? I was too. Garak and Aosp confirm this is a kernel-cm incompatibility. Dirty v needs a ramdisk edit to work with cm.
[Samsung Galaxy Nexus] MBQ_:
Didn't realize that. Thanks for that gem of info. :)
[Samsung Galaxy Nexus] drumst1x:
Seems pretty quiet in here.... anyone still flashing these? I've currently got the February 6, 2014 build on my phone. Running overall pretty well. I get a process stopped in com.android.(something, I forget) on every boot before my lockscreen enables (once I click "ok" it goes right to the lockscreen). No real issues other than that, but i realized how long it's been since I've flashed and haven't seen too much activity here and don't like to flash without hearing what others have seen as far as performance/broken features.

Thx Fits for continuously building :)
[Samsung Galaxy Nexus] klobkelosh:
Crickets....

I had to jump off the cm train when they merged the multi-sIm stuff earlier this month, but looking to come back over when the apn/mms/data issues are ironed out. I've been following a few threads but not entirely sure if everything is working yet.
[Samsung Galaxy Nexus] Shadow Death:
I didn't even know this thing still had active development.
[Samsung Galaxy Nexus] klobkelosh:
I see there's only 4 or 5 folks actively downloading nightly builds. Anyone using this anymore? If so, do you still have your device connected to Verizon's network? And, if so, how have the most recent nightly builds worked?
[Samsung Galaxy Nexus] jlvlawrence:
I'm on the m4 build but I'll nandroid and flash this later today.
[Samsung Galaxy Nexus] MBQ_:
It's actually kind of a shame.
[Samsung Galaxy Nexus] klobkelosh:
I couldn't agree more Kyle. This is my favorite ROM, when the boys at cyanogen aren't f'n it up.
[Samsung Galaxy Nexus] MBQ_:
you forgot an 'r' at the end of my name. ;)
[Samsung Galaxy Nexus] klobkelosh:
Lol, sorry, I actually typed it right but autocorrect did it's thing... so, you know earn the right to call me Dang.
[Samsung Galaxy Nexus] DR3W5K1:
I used to love this rom! Have either of you checked to see what it's all about now?
[Samsung Galaxy Nexus] klobkelosh:
I dropped a few weeks ago when the data and phone stopped working. Haven't had time to clean flash on a gamble since
[Samsung Galaxy Nexus] DR3W5K1:
I'll flash tonight at work then. Will report back good or bad.
[Samsung Galaxy Nexus] MBQ_:
Still fantastic as usual, I can tell ya that much ;)

Hahaha I was just messing with you dude. It's an unusual name anyhow.

I see you're in Phoenix. Nice! I'm in Tempe. :)
[Samsung Galaxy Nexus] klobkelosh:
Yep, downtown. I work in mesa, so I prolly pass you every day. But we've had this convo on g+ already...

---------- Post added at 09:10 PM ---------- Previous post was at 09:10 PM ----------

Right on, thanks man
[Samsung Galaxy Nexus] DR3W5K1:
Flashed 3-29 with dirty v no data on boot.......

Toggled data no dice switched to 3g bingo back to 4g bingo phone call bingo. No force closes or anything.....

Soooo good to go!

BTW felt REALLY REALLY smooth
[Samsung Galaxy Nexus] Shadow Death:
The biggest problem is that there are a lot of devs and builds but not as many Gnex users as there once was. That's why Roms aren't getting the download count they used to.

I'm not discounting the Dev of this rom but I honestly have no idea what it offers over the CM nightlys mostly because reading a long Dev post for change logs on this phone is a PITA. I'm currently waiting for my video card to get back so I can use my desktop again. [emoji52]
[Samsung Galaxy Nexus] DR3W5K1:
Cherry picks. Not sure which ones currently though. Also if I remember correctly sometimes this rom is fine even if the official is ****ed.
[Samsung Galaxy Nexus] Shadow Death:
Its been a while since I've downloaded one of these builds.

Edit: I'll have to give it another shot when I get home... Also I keep hitting the send button by accident in the quick reply so I have all these edited posts.
[Samsung Galaxy Nexus] klobkelosh:
^ this. Often.
[Samsung Galaxy Nexus] klobkelosh:
Fyi, today's nightly still borked. Connects to 4g fine (no lte icon anymore), but will not recover connectivity after switching to 3g. Toggling airplane mode does not recover data either. Pity, I was hoping to jump back on cm, but back to my omni nandroid...I'll try again another day.

Edit, it eventually recovered to 3g, but no 4g after handoff.
[Samsung Galaxy Nexus] Shadow Death:
I'm on 3/31/14 and seem to be having no issues at all. I even had 4G on the whole time and didn't know it. It's at 80% after 4 hours and 40 min.. I wish I could say that I've used it but it's mostly been idling since I got my desktop back up and going. :)
[Samsung Galaxy Nexus] klobkelosh:
Hmmm...odd. I clean flashed 3/31 too. Try toggling 4g on and off. Does it come back? Don't actually do that if you care about keeping the rom tho - in the not too distant past toggling out of 4g meant it never came back.
[Samsung Galaxy Nexus] JoeSyr:
Were you using the LTE toggle in quicksettings at all during that? The behavior you're describing sounds a lot like what the LTE toggle on the official nightlies (which should be identical in this build) does to my phone. Of course, it could be two unrelated problems, or just one deeper issue causing both.
[Samsung Galaxy Nexus] klobkelosh:
Nope. I'm scared to death of that LTE toggle! Like I wrote above, rom connected to 4g just fine on a clean install. I toggled it into 3g via settings menu, then toggled back but no 4g returned.
[Samsung Galaxy Nexus] Shadow Death:
I spoke too soon.. I tried to post a picture via the tapatalk app but it's just too crappy. It wouldn't even upload pictures. Even with 4G connected there isn't any data. Actually I can't seem to get data over radios at all. :/
[Samsung Galaxy Nexus] drumst1x:
Unfortunately it sounds like this rom is still not as stable as I'd need it to be :( Wish these data handoff issues would get fixed already, damn you CM!!!! haha

If they get S-off for the HTC One M8, I'll probably be jumping ship to that. If not, i'll be holding onto my GalNex for a while longer, maybe taking a look at the GS5 or the new Sony Experia phone on it's way (if it makes it to Verizon).

Regardless, definitely glad to see that there are still some people deving for this phone. Here's to hoping we get a nice stable release one of these days....

Thanks Fits for continuing to update the ROM.
[Samsung Galaxy Nexus] Shadow Death:
I'm going to my gnex as a backup but come July I want the One Max.

Keep in mind though its not just us. CM on the One M7 has the same problem.
[Samsung Galaxy Nexus] drumst1x:
Is the One M8 Max a definite thing? I thought it was just speculation at this point and HTC hasn't announced/talked about it? I could wait 3 more months on my Galaxy Nexus for the M8 Max if it is bootloader-unlockable also.... I do have to say, i HATE that the One doesn't have a removable battery... :( No matter how well the phone manages battery use, it's still a battery, and those things have a shelf-life.... A shame to have to completely ditch a phone because a battery no longer holds a charge. Especially with the reports of how difficult it is to open the phone and change anything out ... What an "Apple" thing to do :( Blech.

Didn't know that the M7 on Cm was also having the same handoff/data issues. I guess it's a CM thing, but I guess we already knew that. Options i guess are rollback to CM10.2, deal with the issues, or jump to another KK rom.... blech, i'm happy with CM if these issues were fixed :(
[Samsung Galaxy Nexus] MBQ_:
-_-
[Samsung Galaxy Nexus] drumst1x:
April Fools? :) Site is live for me now.
[Samsung Galaxy Nexus] MBQ_:
Bümp

.. And lol at those who knew how to pronounce it and released 'wow I sound stupid'

:D
[Motorola Atrix HD] teeth_03:
I thought it had it and that it was compatible with the 100 dock? The specs listed up top on xda say otherwise...