yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] kb8no:
Put it in airplane mode and turn on wifi. If it is in airplane mode you dont need to worry about shutting off data. I just spent 2 days in Canada and this is what I did and it worked fine. You can always hijack open wifi.

Your experience in Israel was a fluke and you were lucky you did not come home with a huge bill. Whatever loophole you were in is closed now. LTE is a form of gsm. I expect you were maybe riding unauthorized LTE but there is also some spotty CDMA around some places.

I am very sure your S4 is a "global" phone with gsm like my S3. My S3 conveniently comes from Verizon with an unlocked SIM. If the SIM is unlocked in your S4, when you get there you can buy a prepaid card for reasonable price. Europe is getting better but they still hit you hard for roaming. So if you get a sim from Italy they charge you lots to roam in Spain and Israel.

I'm spending a week in the Netherlands and a week in Belarus in July. I will buy a NL sim in the Schipol airport to use for a week. Then going to shop in BY and buy a different sim to use for a week.

You can now leave your phone on airplane mode in the plane. Here's something fun. Download Google maps of your flight path and get fresh satellite fix just before you get on. GPS works on the plane and you can follow the flight. Airplane mode draws almost no battery, just the screen. Get gps test app to follow satellite lock cuz it can take a while to get a fix at speed.

Google voice and Skype work.
[Samsung Galaxy Nexus] MWisBest:
Sorry for the delay in getting a new build up! I was going to get one up last night but for some reason I started getting random inexplicable errors while building, so far the only possible cause I can think of is that my HDD is corrupting. I've always had bad luck with stock HDDs included in computers I buy... I do have a few spares but they aren't nearly as fast as this one nor do they have even half the amount of storage.

Tonight is my high school graduation ceremony so I probably won't have a new build up today either unfortunately.
[Samsung Galaxy Nexus] smokeydriver:
Congrats on Graduating!!!
[Samsung Galaxy Nexus] bsmitty83:
Awesome dude congratulations

Hack The Tuna
[Samsung Galaxy Nexus] rice923:
Congrats MW! Glad to see you moving on and, hopefully, enjoying the journey.
[Samsung Galaxy Nexus] Cloudy_cloud:
Uber (the app)

Does the app Uber (taxi service) not work for anyone else on this ROM? This is kind of a deal breaker for me living in a city by myself. Any help in getting it compatible is appreciate. Thanks.
[Samsung Galaxy Nexus] rice923:
Works for me. Stock settings and gapps modular mini
[Samsung Galaxy Nexus] MWisBest:
I got stuff building again, as usual just a few last bugs to work out but the wait is shaping up to be worth it!

This was my (and most other people's) reaction after high school graduation tonight...just a perfect GIF:

..get it? Because that place was generally considered hell and just made us feel dead with those damn all-nighters before finals..? :p

1. Make sure you use Dalvik instead of ART. It's completely back-asswards right now with Dalvik and ART on this ROM... don't get me wrong it's not that ART is slower on FML compared to other ROMs, it's that Dalvik is just off the charts right now!! (Not to mention it's compatible with all apps, has a much faster initial boot-up time, and takes up much less space)

2. Uninstall the app, reboot, and install it again. Usually I have something like this happen to me once every other month (and not just with FML, with anything Android as a whole), and the uninstall --> reboot --> install trick will usually fix it.

EDIT: Oh um, by the way, I got another Android device to tinker with, and it has an OMAP4460 SoC just like the Galaxy Nexus. :D
[Samsung Galaxy Nexus] Shadow Death:
I remember the day that I graduated a friend and I stayed up all night that day before. Then we had to be there st 11am. Probably about as bad as being hung over before a wedding. Then later that night the high school hosted a all night fun park for graduates that donated towards the event. Had a blast.. More so than my friends that had after graduation parties.

The only issue that I've had with this rom is that it will ride all day sipping battery with data off but turn 3G on and hold on tight she's a battery killer.
[Samsung Galaxy Nexus] MWisBest:
New build up.
[Samsung Galaxy Nexus] metalspring:
Future optimization?

https://github.com/AOSPAL/android_build/commits/kitkat/core/binary.mk
[Samsung Galaxy Nexus] MWisBest:
I experimented with graphite stuff a few months ago and I wasn't able to notice much in terms of improvements, I decided to set it aside to hunt for some bigger stuff instead, which spawned things like these:

https://github.com/MWisBest/android_build/commit/95bb49b613424b70af3e820748724fb92ef35b5e

https://github.com/MWisBest/android_build/commit/d2c13f1c35cfa9c114a69c74cfb1c2631643eebc

https://github.com/MWisBest/android_build/commit/614d0a0f7a808bd735e285a133911be8124172f1

With that stuff, everything is flying, and Dalvik is the most effected by them from what I can tell.
[Samsung Galaxy Nexus] Philosophre:
omg.. i just finished setting it to the way i liked it.

flashing merry-go-round... i love it!
[Samsung Galaxy Nexus] dagwood00:
I installed this rom last night. It looks and runs great so far. The only exception is the keyboard, which FC's every minute or so. I found a lot of people mentioning the same issue in the thread from months ago, so it does not appear to be unique to me. I installed the Swipe-Dragon keyboard and the problem is solved. Thanks for all the hard work.

-Edit, I see you released a new version a few hours after my install. My comment is related to the previous version. I will update to the new one and test it out as well. Thanks
[Samsung Galaxy Nexus] MWisBest:
Sometimes when you get an app that FCs like that you might have to reboot, there's a bug I'm trying to track down where some apps won't be DexOpted (put in the dalvik-cache ya know) on the first boot-up. It's either that or the GApps package you're using is overwriting the file: "/system/lib/libjni_unbundled_latinimegoogle.so". That file provides support for gesture typing in the stock keyboard, among other things, and if a GApps package overwrites this with the wrong version the AOSP keyboard will have issues. I suppose it's about freakin' time I make that FML GApps package I promised like over a month ago! :eek:
[Samsung Galaxy Nexus] dagwood00:
I suspect it is an overwrite issue. I used the GApps suggested in the post. I tried to fix it by rebooting and then by re-installing the google keyboard from Play (used voice to type it in). It just kept reverting to "install" and never "installed". I used some of my stash of amazon coins from bonus promotions to buy swipe, glad I could finally put them to use. Other than being a different color, it appears to work just as well as the android stock keyboard. Handy to have just in case anyway.
[Samsung Galaxy Nexus] ashclepdia:
I like swype a lot better than stock anyways.

particularly it's suggestions bar, how you can scroll it from right to left to see more words, vs that annoying 3dot popup box on google&aosp and many other keyboards.
[Samsung Galaxy Nexus] rice923:
Is anyone else getting a "server error" notification when trying to view the OP via tapatalk? All other pages work for me except the OP
[Samsung Galaxy Nexus] MWisBest:
You should try the Google Keyboard add-on package from the GApps suggested, it'll just swap out the AOSP Keyboard with Google Keyboard which is probably better anyway.

That's not the first time this has been reported, first time was in the maguro thread. It's probably the length of it, and I'm not going to be shortening it, I'd suggest telling the Tapatalk people about it or something. :/
[Samsung Galaxy Nexus] rice923:
Ehh no biggie. I'll DL via browser
[Samsung Galaxy Nexus] demlv:
Same error for me too.
[Samsung Galaxy Nexus] Shadow Death:
Same here with XDA's app
[Samsung Galaxy Nexus] MWisBest:
FML on my Kindle Fire HD 7"!! :D:D

What's awesome about this is that the KF HD 7" is an OMAP4460 SoC just like the Galaxy Nexus, and I've already found numerous things done for the Galaxy Nexus that'd be of use for the KF HD 7" and vice-versa.

There's a few things I need to do before officially releasing FML on it, but it's looking good so far.

HUGE thank you to [MENTION=4243514]Hashcode[/MENTION] for all the work he's done for the Kindle Fires, there's absolutely no way I or probably anybody else would have custom stuff running on this tablet without him.
[Samsung Galaxy Nexus] pattyboi:):
you should try those commits from mpokang for the ram speed increase on a kernel for the fire and see if it helps it performance considering its the same system :p
[Samsung Galaxy Nexus] kb8no:
Same problem here on Tapatalk. I have been getting intermittent and annoying server errors on XDA via Tapatalk for a long time. Usually but not only it is responding with a quote like this. Work around is to close message with a save, exit XDA, restart XDA, start new message with saved message, then it takes.

I've suspected it was an XDA problem and server error with XDA's own app here would support that theory.
[Samsung Galaxy Nexus] MWisBest:
I'm pretty sure XDA's app is just a custom Tapatalk app.
[Samsung Galaxy Nexus] HaRdC0r3:
Hey [MENTION=328694]mwise[/MENTION]Best when do you think you may have time to get a full F2FS ROM out?
[Samsung Galaxy Nexus] Shadow Death:
It is... I believe it's a few versions behind Tapatalk. Some of the issues also play into the plugin. Instead of the app making a mobile version of the site it uses a plugin built into the site for browsing. It converts the site into a format that Tapatalk/xda can read. That's where a lot of problems come in. If the plugin's license is expired, it gives errors.... etc... They basically took the wheel and made a more complicated version of it.
[Samsung Galaxy Nexus] Rushead:
OK, let's pretend you're not asking for an ETA, cuz we all know that's a serious no no. Let's try rephrasing your query, shall we?

"Hey [MENTION=3390093]MWisBest[/MENTION], have you seen the activity regarding f2fs & all the work the dirty team has put into it? Do you plan on taking FML in that direction?"

This way you avoid even coming close to sounding pushy. Sorry if this is a bit patronizing...

Sent from a flashead cracker.
[Samsung Galaxy Nexus] MWisBest:
Thanks [MENTION=4648519]Rushead[/MENTION]. [MENTION=2424014]HaRdC0r3[/MENTION], you did ask nicer than most people would have though, you at least asked it more like "when I think I might have the time to work on f2fs" and didn't ask it like "wen wil u ad f2fs suport", so I am going to answer the question anyway:

Right now I'm kinda waiting for some things to be finalized so-to-speak. I am actively following the F2FS work, and it is just that: active. I want to wait until there's some more finalization on some of it. FML will have F2FS, and I'm guessing it'll be within the next week depending on how long I keep tinkering with this tablet... few things I'll share on that in a bit.

Ah yes, I forgot about that part.
[Samsung Galaxy Nexus] Shadow Death:
AOSP has the TWRP 2.7.0.0 recovery IMG that supports F2FS/ext4 hosted in a few threads if people want to check it out.
[Samsung Galaxy Nexus] metalspring:
Best to wait awhile anyway, 4.4.3 source is out with tons of bug fixes, and a few other little things
[Samsung Galaxy Nexus] MWisBest:
FML.
[Samsung Galaxy Nexus] metalspring:
I think omni will take awhile to merge it in though, I know vanir is having fun with it though :P
[Samsung Galaxy Nexus] MWisBest:
Stahp! You're only making it worse :crying:
[Samsung Galaxy Nexus] Shadow Death:
I've been having a very strange issue with the latest build. Its not really a problem just an inconvenience. If I reboot the phone via the power menu it will bootloop at the Google screen continuously until I pull the battery and power it back on.
[Samsung Galaxy Nexus] MWisBest:
What the hell... can you by chance grab me a copy of the /proc/last_kmsg file when that happens next?
[Samsung Galaxy Nexus] dbt816:
Are you running one of the DirtyV kernels? This is a known issue and I believe it has something to do with the ramdisk...I'd have to look back through that thread to be sure. You can hit the lock button and both volume buttons simultaneously to bring up the boot menu instead of pulling the battery. At least it's a little less on an inconvenience that way :)
[Samsung Galaxy Nexus] Shadow Death:
Yeah, ill try and remember next time I get a chance.

I can do it on command anyway.

It is DirtyV-rsr 5/3 but this is the first time I've had this issue.
[Samsung Galaxy Nexus] dbt816:
Yeah, same here...it happens intermittently and has for quite a few previous releases, even on other ROMs
[Samsung Galaxy Nexus] dlabadie:
I've been having the same problem. Running DirtyV-R 5/3 with Nephilim's settings.
[Samsung Galaxy Nexus] MWisBest:
BTW guys, I had reported my topic (under "Other - Non-Urgent") asking if they could look into the Tapatalk issues, and I was informed that the server admin is working to correct it. Let me know if it starts working for you any time soon.
[Samsung Galaxy Nexus] MWisBest:
New build up, Android 4.4.3!

If they don't do a 4.4.4 I'm going to be pissed, because:

1. It's 3 4's, duh!

2. KitKat bars are usually in 4 long pieces.

Currently working on the maguro build, but I might fall asleep before I can upload it. :(

EDIT: By the way, that 2.7.1.0 TWRP version number is not a typo. :)
[Samsung Galaxy Nexus] Reinvented:
On behalf of all of us,

thank you
[Samsung Galaxy Nexus] DR3W5K1:
Just so everyone knows this issue can be fixed by clean flashing the ROM. It happens because of MILD data corruption caused by having fsync off at some point in your phones lifetime (can be caused by other things as well... Either way a clean flash will fix it).
[Samsung Galaxy Nexus] rice923:
Does anyone have a recommendation for a smooth browser on FML? Chrome is quite disappointing for me right now, but I'm not sure if it's simply because of the hardware.
[Samsung Galaxy Nexus] Rushead:
I haven't used my computer to download a rom in what seems like years (stupid tapatalk app).

So what do we need to do to get [MENTION=3390093]MWisBest[/MENTION] developer status? And let's do that thing, whatever it is.
[Samsung Galaxy Nexus] rice923:
You can go to the OP and open in the browser. Just click the three dots on the upper right and use web view. DL as usual.

Is there a perk for developer status?
[Samsung Galaxy Nexus] kb8no:
Open the OP in"Web View" in Chrome. NICE TRICK! Thanks.
[Samsung Galaxy Nexus] MWisBest:
NOTE: I have discovered that there is a bug where the recents sections of the Dialer app crashes instantly, I will get a new build out today to fix this!
[Samsung Galaxy Nexus] dbt816:
I did a clean flash to the latest build this morning. I noticed that the Messaging app is sending "[Automated Message] I'll get back to you when I can" whenever I received a new message. I don't see anywhere in the app settings for automatic replies. ???

EDIT: Weeeeeel, it has been one of those days. I somehow managed to hit "Start Now" in the settings for Quiet Hours when I was checking everything after the upgrade...sheesh :)
[Samsung Galaxy Nexus] Shadow Death:
Op magically works in a different build.
[Samsung Galaxy Nexus] MWisBest:
Um. New build is up to fix the Dialer crash bug, but I'm using the DevDB Variable feature for the OP and somehow all of the variables have just been replaced by "[#VarNameHere]" instead, so the OP is kinda broken right now...
[Samsung Galaxy Nexus] Shadow Death:
I think that the standard 4.4.2 apps should work with this.. but don't quote me on that.

I had some glitching with the first 4.4.3 build earlier. I didn't actually know the first release today was 4.4.3 until I checked the version # right before flashing the second release. I also flashed 4.4.2 Gapps in the first 4.4.3 build today. So that probably explains the issue there. This thing is running super smooth with the second release and proper PA mini 4.4.3 Gapps.
[Samsung Galaxy Nexus] Droideez:
Working good with new build and pa 4.4.3 apps ... looking for lock screen notification I can't find it under security.
[Samsung Galaxy Nexus] MWisBest:
Lock screen notifications are not included with OmniROM, and hence not included with FML. I rarely include things that haven't passed through OmniROM's Gerrit Code Review (https://gerrit.omnirom.org), and lockscreen notifications is one of those things.

I don't even know what lockscreen notifications is, nor do I see a point to that: does nobody use ActiveDisplay?!
[Samsung Galaxy Nexus] oman0123:
Lockscreen notification >>>>>>>> active display

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] Shadow Death:
lol yes... the thing though.. I don't care for either anymore. Lockscreen notification was nice... but it cluttered the side of my phone when I was at work. I learned to love the notifications menu again.
[Samsung Galaxy Nexus] Zer0_Cool:
have you used the new version of active display?
[Samsung Galaxy Nexus] oman0123:
.... Define new lol

Honestly.... No.... It's been awhile. Whenever I tried it the screen would constantly turn on in my pocket and invite itself to feast on the battery.

Not sure if they are somewhat the same but Peek was actually really nice for the short time I was on PA.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] bothgoodandbad:
active display>

I like active display, if peek was able to be used as lock screen and when ever picked up with out "being in pocket" it would still activate(or at least an option) then i would use something with peek or enable peek.. other wise it's active display for me.. last resort in some roms = acdisplay 2.3.1
[Samsung Galaxy Nexus] Zer0_Cool:
the new one is essentially peek. I didn't notice until a week or two ago that the original was deprecated. I've been using it as my primary lockscreen as well, it's an option in the settings.

https://play.google.com/store/apps/details?id=com.achep.acdisplay
[Samsung Galaxy Nexus] oman0123:
Hmmmm When I get home I'll definitely give it a try. Been a couple months since I really gave Omni a try other than testing mms (which was always rock solid)

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2

---------- Post added at 02:45 PM ---------- Previous post was at 02:36 PM ----------

Is there an f2fs version or will I have to make one?

Sorry for asking. I glanced quickly at the op but I'm out with the lady and am getting yelled at for having my phone out lol

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] Shadow Death:
To my knowledge there is not an f2fs version.
[Samsung Galaxy Nexus] Rushead:
FTFY

Sent from a flashead cracker.
[Samsung Galaxy Nexus] dbt816:
FWIW, my Antutu benchmark scores have *consistently* been 800-1000 points higher with the 4.4.3 build. I can think of only one other time my device has broken the 13,000 mark, and not with the kernel tweaks I use normally, but now it's a solid 13,600 to 13,800 :good:
[Samsung Galaxy Nexus] oman0123:
Anybody interested in the newest FML with f2fs?

I have a build that I just threw together using the guide in the slim thread. I can post it if MW says its ok

:)
[Samsung Galaxy Nexus] ashclepdia:
mwisbest is usually very nice about people posting in his thread

that being said, I could see where since it's not an OFFICIAL build by HIM, and people might ask for support in THIS thread for it, maybe not so much. you COULD always privately share your builds through PM if you want, with disclaimer to NOT ask for support for any issues in it that might occur in this official builds thread ;)
[Samsung Galaxy Nexus] Shadow Death:
I found one issue with the recent build for me. People fc the second it opens.
[Samsung Galaxy Nexus] kinfolk248:
is 443 any better than 442? did They actually fix the bugs?
[Samsung Galaxy Nexus] Shadow Death:
I don't k ow about the bugs but battery life is definitely better.
[Samsung Galaxy Nexus] Zer0_Cool:
agreed, battery life has been better for me on this build. I did a clean install. The last build I was running the latest dirtyv with Nephilim's settings, and battery life was less than par. This build, I left the stock kernel. I have one problem though, I expected video camera issues with the superram kernel (even though I set it to 720p), but with the stock kernel for the latest build I'm still experience video camera lockup. Is anyone else experiencing similar issues?
[Samsung Galaxy Nexus] domenci:
Haven't tried video but I did notice lens blur crashes while trying to render.
[Samsung Galaxy Nexus] Rushead:
I've had camera fc problems at times when taking stills. Wipe data & reboot to fix it. But it's pretty random. I've gone weeks with no issues.

Sent from a flashead cracker.
[Samsung Galaxy Nexus] MWisBest:
Hey guys, I went on a vacation for the weekend and got home not long ago. I'll catch-up on the FML threads sometime tomorrow, I'm exhausted so I'm gonna try and get some sleep first!
[Samsung Galaxy Nexus] Shadow Death:
Man, it is really hard to get off this last build. Its rock solid.

Edit: I'm about to take my PTO, 60 hours worth, and try to find another job.... Err.. Career
[Samsung Galaxy Nexus] cujo6801:
Good luck bro.....

You got this...

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Shadow Death:
I feel a little out of place when even the techs dont know jack about linux. Their network is windows based.
[Samsung Galaxy Nexus] MWisBest:
@ all the F2FS stuff:

1. I'm not comfortable with people posting a modified FML build with F2FS support. I've been approached with that a few times, my response has always been that they should link people to how to do it themselves instead. From a security standpoint it's a big issue for me, the only builds of FML I want in my threads are my own.

2. The next FML build (probably tomorrow) will at the very least support F2FS to the point where all you need to do is flash an F2FS-enabled kernel, format, and away you go.

The best I've ever done (with the FML kernel at least) was about 13,200, but it usually stays between 13,000 and 13,200 then. That of course is with turning on the performance CPU governor and 1500MHz OC frequency. My tablet on the other hand can consistently get above 14,000, and I still don't understand how the difference is that big.

Is this with the 06/05/2014 v2 build? Sounds like the same bug that Dialer had with the first 06/05/2014 build and I can't reproduce it.

Here you can find what changed between 4.4.2 and 4.4.3: https://funkyandroid.com/aosp-KOT49H-KTU84L.html

There's some bugs fixed and whatnot, the huge annoying walls of text are from the chromium crap though.

I forgot about the camera thing, I do need to fix that up a bit in the stock kernel, thanks for the reminder!

Lens blur? What the hell is that and where do you find it. :eek:
[Samsung Galaxy Nexus] bsmitty83:
Lens blur is in the Google camera , its actually a pretty cool effect , you take a pic , then slowly pull the camera away and it takes a blurry photo and combines the 2 and blurs the background out . I dig it

Fwiw , I can consistently hit 13500-14k in antutu with my kernel running throttle off , 1.6 GHz , 512gpu , interactive gov , zen io . I think the biggest difference maker is the throttle off . with it on my kernel benches @ 12-12500 . best I've ever hit was 14,800 . but that crap is meh to me lol . [emoji6]

Hack The Tuna
[Samsung Galaxy Nexus] Shadow Death:
Yes but for whatever reason I don't seem to have the issue anymore. If it does happen it does it when I make calls using the dialer or a contact. It doesn't stop the call from happening it's just weird.

Edit: I'll try and get a logcat next time it happens.
[Samsung Galaxy Nexus] kinfolk248:
Will most def be trying this rom when the next build drops, I see where there are one or two bugs and maybe some new stuff coming so I'll wait...
[Samsung Galaxy Nexus] otter34:
Loving it. When I get a notification a dark screen comes on. How can I stop the screen from coming on? I'm concerned about battery life. Does this have to do with pocket mode? I sure love that. Lastly can I move the omni switch somehow?