yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] sickopsycho:
I'm not sure if I'd go with a custom rom period if you dont want to be the "tech guy". Granted I dont know how savvy your wife is or what she may or may not be willing to put up with- but my girl has an iphone thats not even jailbroke and shes calling me every few days asking "why won't it do this" or "how can i get it to do that"... lol. This rom doesnt have any major issues- but there are some little "glitches" or annoyances that might affect performance. Just be forwarned. Only thing I get restored from google is contacts and calender. I dont even get my apps restored, although certainly i can go in and see what they were- restore them manually. I BELIEVE that titanium can be used to restore wifi passwords... dont think that one would mess with anything if coming from 4.3. Please correct me if I'm wrong...

I can't get google NOW to reply to "ok, jarvis" for me =( It will respond to ok, computer 9 times out of 10 but not jarvis once. Has anyone tried ok, google... "beam me up scotty"? Give it a whirl. =)
[Samsung Galaxy Nexus] Enter The Nexus:
Very good, Google, thanks for telling us about that easter egg!

I've tried...

OK Dildo

Ok Doo-Doo

Ok Doodle

Anything that sounds like "ooh-ohh" works, really.
[Samsung Galaxy Nexus] kb8no:
I got my wife on this ROM. I dirty flashed the most recent one over the last one no problems with all the apps and WiFi and so forth. No crashes. No tears. No whining. No nothing. She's happy.

Just do a tibu backup, full wipe, tibu restore. Just get over it and type in WiFi PW again and redo her ringtones. You can dirty flash the next release. You won't regret it.
[Samsung Galaxy Nexus] rice923:
This post is probably funnier than it was meant to be hahaha

Anyhow, has anyone had a reboot when launching yelp and summoning the keyboard to search?
[Samsung Galaxy Nexus] Fluey18:
I used a lot of stuff off this list and it worked for me. Surprisingly they haven't suggested the "OK, Dildo" command.

Edit: Guess it didn't like my picture.... http://goo.gl/NBy2Ci
[Samsung Galaxy Nexus] MBQ_:
Sexual.
[Samsung Galaxy Nexus] sickopsycho:
So regarding the "Bluetooth" audio bug that glitches music when locking and unlocking the screen... Its not a Bluetooth bug I don't think. I get the same error over headphones... Also with audio playing over speaker in phone. It sounds a little different but its there. Haven't tried muting lock/unlock sound... How does one do that? I suppose I could dig around and find out myself and give it a whirl, report back results.

Regarding Google now easter eggs... Am I the only one that thought, when they heard your phone will respond to "ok Jarvis", it was an ingress reference? I was like... Oh hell yeah what if I say ok ADA? Lol... Oh well... =)

Sent via Galaxy Nexus Life completely Forked.
[Samsung Galaxy Nexus] MWisBest:
Sorry I haven't been on much lately! Been a little busy with things.

Friday I took my grandma to the hospital because she was having chest pains. The fact that she even told me she was having pain in the first place was amazing, as she very rarely shares things like that with people, mostly because she doesn't want to go to the hospital, so the fact that I was able to convince her to go in too was awesome. I was there for a few hours with her, they ran a bunch of tests and stuff and came to the conclusion that she just pulled a muscle in her chest somehow, but they did notice some level of something in her blood was a bit off and they adjusted one of her medications as a result, so it certainly wasn't a waste of time or anything. I'm just glad she's OK.

This weekend my laptop were taken apart more than they were put together, this being the reason why:

http://imgur.com/a/uOOai

http://imgur.com/a/T1R38

and people think computer programmers are only good with software problems, hehe. Everything worked after putting the computers back together the first time, so I didn't have to take them apart twice and I didn't lose any screws or other parts, haha.

I also worked on a bunch of homework this weekend, and got to watch the Packers finally win a game...

I read through the thread to see what new things had come up, I'm not going to quote anything specific but I'll try to respond to some of the things that were reported.

I'm aware of the audio glitch that seems to be related to locking and unlocking the phone. It isn't just for Bluetooth either, it is for headphones as well. I'll be looking into this for sure, as it's something I ran into a number of times myself as well. If you guys having this issue could let me know what media player you use as well, that would be great, thank you.

[MENTION=3527370]taz1458[/MENTION], thank you for the extra info about the issue you are having with the texting thing. I'm especially glad you found a build that didn't have an issue with it, as it gives me a "regression range" to look at for what started this problem.

I'll see what I can do about getting a new build up soon, this weekend certainly put a delay in what I was planning on adding so I might have to scrap it for a bit. :c
[Samsung Galaxy Nexus] David 617:
Nice pics. I had to do the same last summer with my Sager. Some moron wanted $500 to do it for me. So I did it myself. Also stuck a square of copper between the heatsink and CPU to get even more heat dissipation.
[Samsung Galaxy Nexus] taz1458:
No problem. I think it has to do with that pop-up. Something between the 11/25-12/2 builds.
[Samsung Galaxy Nexus] MWisBest:
Lmao, before I can get a 4.4.1 build up Google is already coming out with a 4.4.2!
[Samsung Galaxy Nexus] skylordusa1:
hahahahhah Google is on the ball lately with moto ahhahaha. Well I guess its good you didnt waste much time on 4.4.1 hahahah.
[Samsung Galaxy Nexus] MWisBest:
I'm thinking of putting the big thing I've been doing on hold and getting a new build out. There might be an issue with stability since it isn't finished but I could at least try working around it for a new build. The thing I'm working on was something that I had completely finished before I initially released FML back in late August, and it took me a couple weeks to do back then but I thought I'd be able to get it done quicker this time since I could reuse a lot of the code I changed back with 4.3.x.

I was hoping to maybe surprise people with what I'm doing, but I think if I was a user of a ROM and the dev decided to be secretive with things I'd get annoyed, haha. If you want to know...

Linaro/Optimizing. I don't just simply use the Linaro toolchain, I make changes to the Android code itself to further optimize it like Linaro does. Simply using their toolchain doesn't provide much in terms of optimizing things and making them faster.
[Samsung Galaxy Nexus] ricola1989:
You, sir are a gentleman and a scholar.
[Samsung Galaxy Nexus] Rushead:
"Best rom ever"

Sent from a flashead cracker.
[Samsung Galaxy Nexus] taz1458:
Just a quick question, anybody know of any gapps where the panorama works?
[Samsung Galaxy Nexus] sickopsycho:
The panarama "works"- you just cant see the picture while you're taking it. The picture renders fine when youre done though. As an alternative use photosphere but just take a row of pictures instead of a full sphere...

Hell yeah on Linaro- I'd be really curious to see how much of an improvement would be offered... =) =) =)
[Samsung Galaxy Nexus] klobkelosh:
Or just flash this after gapps: http://d-h.st/GB2
[Samsung Galaxy Nexus] smokeydriver:
I am running recovery 2.6.3.1 TWRP. It fails. This is my first time trying out this ROM. Yes, I am doing a clean flash....manually. I don't have ADB on this computer so flashing 2.6.3.2 won't work (unless someone has an .apk of version 2.6.3.2 for me to try out). Any other suggestions/hints/something stupid I might have missed?

Thanks!!!
[Samsung Galaxy Nexus] nalanotae:
Could be a bad download might want to try redownloading

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] ricola1989:
Download flashify from the market. You can flash boot images, and zips with it. Also, have you wiped system when trying to flash from a pre-4.4 ROM?
[Samsung Galaxy Nexus] smokeydriver:
I always wipe system when flashing. I used flashify and it updated my recovery. It installed just fine after that. I have been searching this thread, and I believe I can't change these options, but if possible, can someone please give me clear directions on how to do so?

1- Center clock on statusbar

2- Change navigation button colors (I know I can do this with apps, but doing it with a simply option in the menu is so much easier/quicker).

3- Can I make the app drawer be a continuous vertical style instead of horizontal page style?

3 A- If this is not possible, can I make the launcher I typically use (Apex) have this launcher's search bar....basically, I want to have the always listening 'OK Google' option.

Again, yes I've searched this thread and I do not believe I can do options 1, 2, or 3. I'm not sure if 3A is possible. Thanks!
[Samsung Galaxy Nexus] grandzu:
The the buttons for the menu the navigation bar goes to the launcher menu and the menu gear on that screen goes to Google now settings.

Any way to have one of these menu icons go to the phone settings menu?
[Samsung Galaxy Nexus] MWisBest:
Well I wasn't able to just "turn off" what I've been working on in order to put out an updated build. I've really been working hard on being able to get a new build done, this is probably the longest it's ever taken me to get a new build up and going and I'm probably even more frustrated than you guys are.

Since this has taken me so long, if you're getting impatient I'd suggest giving another ROM here a try while I get this stuff with FML sorted out. There's a few CM-based ROMs and they're all very nice as far as I can tell. I really don't care how many users my ROM has or things like that, all I want is for people to enjoy their phone, regardless of whose ROM they use. That seems to be a lost (or never found) art among many devs in my opinion...
[Samsung Galaxy Nexus] metalspring:
Btw just to save you a little time if you didnt know yet, only use linaro 4.7 toolchain

any and all 4.8 toolchains will cause a bootloop if you switch to ART runtime (aosp and the linaro team are working on it though)

I myself tested linaro 4.8, sabermod 4.8, aosp 4.8 codefirex 4.8 (used in vanir) and none worked with ART
[Samsung Galaxy Nexus] Enter The Nexus:
>Xposed

>GravityBox

?
[Samsung Galaxy Nexus] MWisBest:
I'm aware that GCC 4.8 breaks ART, however I think I know a way around that. Thank you for the heads-up though.
[Samsung Galaxy Nexus] grandzu:
Xposed doesn't work with ART though, right? When I used it, I couldn't switch from davlik.
[Samsung Galaxy Nexus] MWisBest:
Quick update on how development is going:

I finally have everything building correctly. All that's left is making sure ART doesn't crap out because I'm using GCC 4.8, the chances of this being done tonight aren't great but there will definitely be a new build tomorrow for sure. Even better news is that in some ways I'm ahead of Linaro, and as always everything I've done is right on my GitHub for anybody else to use. :highfive:
[Samsung Galaxy Nexus] metalspring:
Have you thought of trying these aosp commits? They are by one of the linaro team (note who submitted them lol) and they are trying to get 4.8 toolchains working with ART (apparently something with 4.8 and the clang cause the issue with ART)

https://android-review.googlesource.com/#/q/status:open+branch:master+topic:clang,n,z
[Samsung Galaxy Nexus] MWisBest:
I haven't looked into those, thank you. I am using Clang with ART and switched to using AOSP's master branch for ART as well, so those might be helpful if I run into some issues with testing.
[Samsung Galaxy Nexus] smokeydriver:
I'm a bit confused...what would these two apps help me out with?
[Samsung Galaxy Nexus] Enter The Nexus:
Do you really need ART? If so then that's something you have to sacrifice...

---------- Post added at 08:16 AM ---------- Previous post was at 08:12 AM ----------

Xposed let's you modify your framework like CM does on any ROM. It's basically having the ability to add things to your ROM. GravityBox is a module apart of XPosed that lets you customize your ROM. It gives you the ability to add quick setting tiles to your ROM as you please. Go ahead and watch videos on XDA TV by Kevin and TK and read up about it on XDA. It's amazing. Hope i gave you a basic understanding on these two things. btw they're not apps on the Play Store.
[Samsung Galaxy Nexus] MWisBest:
NEW BUILD UP! Please make sure to read the changelog before flashing, there is some important info in there that will help avoid some issues.
[Samsung Galaxy Nexus] eriscentro:
I just clean flashed to the newest build. I'm using bank's gapps (for 4.4.2), as well as mpokang's super ram kernel. Messaging FC's for me on both dalvik and ART, can't even open it

EDIT: messages don't work in hangouts either

2nd Edit: Also tried a reflash with stock kernel and PA gapps for 4.4.2, and same problem
[Samsung Galaxy Nexus] ohurvitz:
Messaging works fine for me. Did you clear /system when updating?
[Samsung Galaxy Nexus] eriscentro:
Yup, wiped system, dalvik, data and regular cache. Are you on today's build?
[Samsung Galaxy Nexus] ohurvitz:
Yes. Though I am using latest ASKP kernel.
[Samsung Galaxy Nexus] MWisBest:
I haven't been able to reproduce any issues with SMS, regardless of whether or not I use Hangouts or Messaging.

For those of you having issues with this:

1. Did you make sure you were on Dalvik before you flashed the new build if you were using ART?

2. Did you wipe /system, /cache, and dalvik-cache before flashing?

3. Have you tried using the recommended GApps (Paranoid Android's)? They have a specific zip for 4.4.2, please give that a try.

4. Have you given the phone some time to stabilize? Sometimes things can be a little weird after a new flash, especially if you're using ART. I actually had the phone completely freeze on me while the screen was off which required a battery pull when I was testing, but I've been going rock-solid for a good 5 or 6 hours since then.

5. If you have done all of these things, can you get me a logcat?

Thank you!
[Samsung Galaxy Nexus] eriscentro:
Before ART I hadn't wiped the dalvik cache, although I had the same issue with dalvik. Before flashing, I wiped /system, /cache, dalvik-cache, and /data. I tried it with the PA gapps (the ones that just came out today) as well as with the BaNkS package. I gave it several minutes (on one flash up to 30), and I just went back to 4.4.1. I can reflash and do a logcat, although not at the moment. I also tried with the stock kernel, as well as mopkang's super ram kernel.
[Samsung Galaxy Nexus] skylordusa1:
I am having trouble with sms to. Gchat in hangouts seems to be working fine but as soon as I try to send an sms to someone hangouts force closes.

I was on dalvik before I flashed.

I wiped everything before flashing.

I used the gapps from PA that they put out today for 4.4.2

I gave my phone some time to stabilize and also tried to reboot. I also cleared data again for the hangouts app and disabled and reenabled it.

still a no go.

Whats the best phone app to get a logcat I should be able to get one now.

---------- Post added at 10:34 PM ---------- Previous post was at 10:23 PM ----------

I think I was able to grab it. Seems pretty long. Where you want me to put it?

I had the log level set to error. Not sure if thats what Im suppose to set it to.

EDIT: I through it up for you. http://pastebin.com/buXR9zHr

---------- Post added at 10:48 PM ---------- Previous post was at 10:34 PM ----------

Also seeing some of these.

2-13 22:33:33.036 E/RichInputConnection(668): Unable to connect to the editor to retrieve text... will retry later

12-13 22:33:33.145 E/RichInputConnection(668): Unable to connect to the editor to retrieve text... will retry later

12-13 22:33:33.177 E/RichInputConnection(668): Unable to connect to the editor to retrieve text... will retry later
[Samsung Galaxy Nexus] MWisBest:
It seems the common thing with this issue is having wiped /data before flashing... it looks like it's having trouble recreating the SMS database (I believe this is at /data/data/com.android.providers.telephony/databases/mmssms.db).

In the mean time, while I look into what is causing this and figure out how to fix it:

1. If you have a full Titanium Backup of your phone (or similar), try to restore the data for the following backups (these are the Titanium Backup names for them...), one at a time, until SMS works again:

- Phone/Messaging Storage (SMS/MMS/APN)

NOTE: This would be probably be your best shot at getting it fixed.

- Messages (SMS & MMS)

NOTE: This would be an XML backup and have yellow text, it might be a Titanium Backup Pro feature.

- Hangouts

- Messaging (SMS/MMS PREFS)

2. If you have a backup of your phone from before flashing the new build (via custom recovery), I suggest restoring it, making a backup with Titanium Backup, re-flash the new build, and do the steps in #1.

3. If you would prefer not to go through the hassle of the things listed above, either go back to the last build that worked or try out some other ROMs.

I'm really sorry for the inconvenience caused by this! I'm working as hard as I can to get it fixed. :(
[Samsung Galaxy Nexus] rice923:
Running current build, all stock settings. Textbook clean install. Switched to ART. Only problem I've encountered is TiBu FC'ing. Anyone else?
[Samsung Galaxy Nexus] MWisBest:
Titanium Backup is working just fine here, are you sure you have the latest version of it? Also, did you wipe /data and if so is SMS working? It seems people that have wiped /data are having issues with SMS.

UPDATE:

I didn't realize that Paranoid Android put up a 2013/12/14 GApps. I've been using the 2013/12/13 GApps, which I downloaded earlier today. At this point, I think I'm going to start putting together my own GApps package as I'm getting incredibly frustrated with issues that pertain to GApps. There's just a lack of a standard go-to GApps package with Android 4.4 like there has always been via goo.im/gapps for previous versions of Android. I know they don't release a new GApps right after a new Android release, they need some time, but I think it's been over a month now and I'm thinking the goo.im/gapps thing is dead.

For those of you that have had any issues with the 2013/12/13 FML build, please try using these GApps after a /system, /cache, and dalvik-cache wipe (followed by re-flashing the new FML of course): pa_gapps-modular-mini-4.4.2-20131213-signed.zip (120.73 MB)
[Samsung Galaxy Nexus] skylordusa1:
Thanks for the quick response MW. Looks like the first step you mentioned about restoring data for Phone/Messaging storage did the trick. I'm able to send and receive text messages now using hangouts.

Should I go ahead and restore data for the other backups you mentioned or I should be fine now that its working?

I will stay on this new FML build with the new PA gapps for a bit and see how it goes.

Let me know if you need to me to check/try anything else.
[Samsung Galaxy Nexus] sickopsycho:
what is the latest askp kernel? All I can find in the xda thread for toro is for 4.2.2...
[Samsung Galaxy Nexus] rice923:
I ended up reverting back to dalvik. No more FCs for TiBu. Still running stock settings for everything
[Samsung Galaxy Nexus] ohurvitz:
Grande

From http://xdaforums.com/showthread.php?t=2479983

[KERNEL] A.S.K.P | Codename: Grande | 3.0.101 | [12-12-2013]
[Samsung Galaxy Nexus] agreenbhm:
MW, your latest build is the bomb. I'm running the 1213 build with Tiny 5.4 kernel, using ART. Job well done!
[Samsung Galaxy Nexus] taz1458:
I initially had the messaging issues. Just restored data on the 1st option you gave and it fixed. Also no issues sending to the Pens thing at 32623. Awesome!
[Samsung Galaxy Nexus] beatlesfan01:
Had the messaging issue, restored your first option, and phone kept force closing to the point where I had to pull the battery and boot into recovery. I restored a previous FML for now.
[Samsung Galaxy Nexus] taz1458:
Hangouts works, but getting fc on handcent

EDIT: I tried all of the steps, messaging and hangouts work, but Handcent force closes.I'll post a logcat in a bit.

EDIT 2: link

http://pastebin.com/ZHdR8DNm
[Samsung Galaxy Nexus] kb8no:
J

Just this alone fixed SMS in 5 minutes including reboot time of 12/13 build. I am not touching ART so only Dalvik experience.
[Samsung Galaxy Nexus] beatlesfan01:
That's the step I did which caused "phone" to continuously force close. Also on Dalvik, not on ART. Everything was fine until I rebooted the phone, that's when it started force closing.
[Samsung Galaxy Nexus] kb8no:
Hummm.... Not here. My wife only yelled at me once about SMS. No more yelling since the fix. In fact, this is the first time she has yelled at me since the reboots quit. Lol. I just called myself from her GNex to test and it worked fine, no FC. All this gapps jockeying is very confusing to me.
[Samsung Galaxy Nexus] MWisBest:
If your backup wasn't from the 2013/12/05 FML build, then it would cause that to happen. If you aren't on the 2013/12/05 build, flash it over your existing build (without wiping /data) and make a backup with TiBu, then flash the 2013/12/13 build and restore that backup. Actually, you should be able to flash the 2013/12/13 build over a 2013/12/05 build without wiping /data and there shouldn't be any messaging issues (as long as you have an SMS message stored already).
[Samsung Galaxy Nexus] taz1458:
Did I post the pastebin right for my logcat of handcent fc'ing?
[Samsung Galaxy Nexus] MWisBest:
Ah, I didn't see that you had edited your post. I will definitely look at it, looks like you posted it just fine, thank you for providing the logcat. It looks like you posted a bigger logcat than other ones I usually get, which I actually prefer as it lets me look at other things that might be happening without you or me realizing either.

Just a little FYI to everybody, ART might have some small issues due to the changes I had to make with it recently. This morning I had to do a battery pull, but I'm 100% sure the issue is different than the one that was experienced earlier in my KitKat ROMs and I don't have the issue with Dalvik. It's hard to pin this down though, as the phone completely locks up and unless I'm getting a logcat as it happens I can't get anything at all. If it was more frequent then I'd be able to get it for sure, but I just can't have my phone dumping a logcat for 12 hours until something happens. :(
[Samsung Galaxy Nexus] taz1458:
Just an fyi, I'm running dalvik still. Have not moved to art.
[Samsung Galaxy Nexus] MWisBest:
Yeah I could see that in your logcat. Is the performance with Dalvik improved compared to previous 4.4 builds, or are you not quite sure of it? Benchmarks have seemed better for me, but benchmarks don't really reflect real-world usage in my opinion.

Regarding Handcent, are you on the latest version of it? I see they updated it just recently, so I just want to make sure.
[Samsung Galaxy Nexus] taz1458:
As for dalvik, I don't really know. It doesn't seem any different then Art to me to be honest. I'm running the bigram kernel so that may be why.

As for handcent, yes it is fully updated. I tried wiping data and cache and uninstalling and reinstalling and it didn't help either.
[Samsung Galaxy Nexus] NuclearBier:
This was my first 4.4 ROM install and I installed the latest nightly which from reading through the threads has broken SMS/MMS. I have already set everything else up in this ROM and really don't want to start over. So I think this will be my plan of attack. NANDROID my current setup > Install a slightly older nightly that has working SMS/MMS > Make a TiBu of basically everything > Wipe phone and restore NANDROID bu > restore Phone/Messaging Storage (SMS/MMS/APN) via TiBu.

I have everything I need except for a known working SMS/MMS nightly. Could someone please provide a link to the latest nightly that has working SMS/MMS?

If someone knows an easier route to fix this please let me know. Thanks!