yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] MWisBest:
I've got a new (to me) Galaxy Nexus on the way! Snagged one off of eBay for $60 that was just factory refurbished / replaced under extended warranty, the thing looks MINT!

I decided to go another way, as you can see. You were asking for more than the one I got on eBay.

Thank you very much! :)

Thank you!! :D I certainly am.

Thanks to the deal I was able to get on the Galaxy Nexus, I'm also getting...

An official car dock (the non-pogo pin one) and an audio cable with in line microphone and media controls. This will allow me to safely use my phone in the car. I can't stand Bluetooth headsets, so to be safe I never talk on the phone when I'm driving as I'd have to have it up next to my ear with my shoulder etc. etc. its just really unsafe, and I also love playing music in my car with my phone, so rather than having to fumble around to find wherever my phone has slid off to and press the volume buttons for next/prev track (or now reach up to the dock and press the volume buttons on there!) I can just do it with the controls on the cable, which also happens to be where the microphone is of course. The cable plugs into the phone at a right angle as well which is nice, and goes into the aux jack I soldered into my car stereo straightly (no angle), exactly what I need!

I'm also getting a new case and a new screen protector. My old case was the XDA one from Cruzerlite, however over the past... 20 months, the entire front of it has worn off and changed color from the original dark gray to what is now white. My dad keeps making fun of it! Also, my existing screen protector is still in good shape, but I highly doubt I can transfer it over to the new screen without wrecking it...

THANKS AGAIN GUYS!
[Samsung Galaxy Nexus] rice923:
Actually, thank you MW! After what you've contribute into this phone's dev scene, you've kept this phone running strong for many of us. Many of our phones might have been long gone if it wasn't for your work.

Now... Get back to work ASAP!
[Samsung Galaxy Nexus] MWisBest:
Hey look at this thing!

Yep, somehow the post office got everything here 4 days ahead of schedule (except the new case and screen protector, which is coming via UPS)! Already found multiple uses for the car dock while not in the car. First, (pictured), on the dev laptop, so I don't have to use two hands to test stuff on the phone etc., and its right there in my view always too. Second, on the back of my tablet LOL.

One little issue: Since I didn't think this stuff was going to be here for a while, I figured I'd take the time to do a fresh install of Linux and just generally get things cleaned up on this laptop. So it'll be another day before I'm at 100% here!
[Samsung Galaxy Nexus] MWisBest:
Development update:

I've been asked multiple times about adding "mpokang's" "RAM" commits (quotes because they weren't his... he just didn't preserve authorship (let alone follow GPL in the first place), and because they weren't technically RAM things), aka double linefill, and each time I've explained that they aren't safe. This has been met with a lot of skepticism, as it seemed to work just fine and have no issues for people.

After hearing they were going to be added back into DirtyV, one of the most widely used Galaxy Nexus kernels, I set out to get some definitive proof to back up what I and Texas Instruments have said. I didn't care how long it took me, best case scenario I could be wrong and could add the changes to FML, otherwise I was right and now I now have it.

This mailing list post states that without disabling double linefill, errors will be observed running memtester: http://lists.infradead.org/pipermail/linux-arm-kernel/2013-September/197964.html

Sure enough, after getting memtester up and running on Android I was able to get the results described in the mailing list post, but ONLY with a double linefill enabled kernel. Surprise surprise.

So they won't be added to FML any time soon, and I suggest you tell any kernel devs you know that are using these to at least contact me and discuss it.
[Samsung Galaxy Nexus] MWisBest:
Awesome, the Play Store icons aren't corrupted in the test build I just did.

Today I'm planning on trying to get the kernel booting issue fixed. First off I'll upload a test build of FML that uses the original kernel, then I'll be uploading some boot.img's for people to test until they find one that breaks. Then I should be able to narrow down whatever is causing the issues and hopefully fix them.
[Samsung Galaxy Nexus] Meticode:
Thanks for the updates. I've stayed with your ROM the longest since the last year. I've had it running for almost 2 months now. I don't plan on flashing until the next final version is released. Good work! :good:
[Samsung Galaxy Nexus] MWisBest:
New test build available! Made some changes that should hopefully fix booting of the new kernel. If you still are having issues booting it, please try doing a totally clean flash (factory reset)! This was something I had to do so maybe others have to as well.

Also included is memtest and memtester:

memtest is a program for testing memory bandwidth

memtester is a program for testing memory corruption

Due to Dev-Host being slow, I'm going to try uploading to Google Drive instead. Let me know if it is any better!

omni-4.4.4-20140824-toro-FML.zip (159.41 MB)
[Samsung Galaxy Nexus] mastertech007:
Factory wipe. Format system and cache to f2fs. Install test new build and PA Gapps modular micro 20140818.

Stock camera FCs, after reboot, camera works for awhile then camera won't open.
[Samsung Galaxy Nexus] MWisBest:
Thank you for the feedback! Could you by chance snag a logcat of when the camera stops working? I'm having a tough time reproducing this on my end :(
[Samsung Galaxy Nexus] p34rp34r:
unfortunately, this might be just you :( haven't seen this behavior at all, with either stock or google camera, even after trying out various photo modes.

Edit: guess it's not just you, lol. mah bad.

I didn't read (oops) and dirty flashed this over 7/5 and everything is fine.
[Samsung Galaxy Nexus] mastertech007:
Hope I did this right....

Around 08-26 06:30:25.552

https://drive.google.com/file/d/0By2h7ZB48inALUVtbWdzc2YwMzg/edit?usp=sharing
[Samsung Galaxy Nexus] rice923:
I'm having this problem on 6-05 build, both stock and Google camera. It's caused me to reboot after every few pics on my vacation...[emoji29]

Stock kernel, everything wiped except data. Dalvik runtime
[Samsung Galaxy Nexus] mastertech007:
Exact same here
[Samsung Galaxy Nexus] MWisBest:
Not quite, you've gotta give me access to the file via Google Drive! Check your email, I requested access so it should just let you press a button to approve it or something. However, this is actually pretty cool: I've seen apps spit out things like phone numbers into logcats before, so sharing them with just the developer is a good idea!
[Samsung Galaxy Nexus] mastertech007:
granted
[Samsung Galaxy Nexus] MWisBest:
Made some headway with the new kernel today... in case you didn't notice, microphone button(s) aren't working in the new kernel. Something that I would've never noticed had it not been for the awesome cable I got thanks to your guys' donations :eek:, I use it pretty much every other day! So I got that fixed, not sure if I broke anything else in the process though...

So now I'm going to get some of the usual features added to the kernel, make an attempt at fixing the camera issues, and eventually toss out a new test build. :good:
[Samsung Galaxy Nexus] rice923:
Glad to see our donations aren't going towards drugs... Right?!
[Samsung Galaxy Nexus] cujo6801:
I hate to break the news to you but Android is a drug...

I've been addicted for years...

Sent from the "DOG" pound
[Samsung Galaxy Nexus] MWisBest:
Lol, I've never touched drugs and I don't plan on it. I'm also pretty much the only person around here who hasn't gotten an underage drinking citation (Wisconsin tends to be a pretty heavy drinking state...), I'm not touching that stuff either. Also, no tobacco in any way shape or form.
[Samsung Galaxy Nexus] Meticode:
La Crosse, WI here! We're famous for people getting drunk and drowning in the river.
[Samsung Galaxy Nexus] Shadow Death:
You should try visiting Texas sometime lol
[Samsung Galaxy Nexus] MWisBest:
Sorry guys, no new build today.
[Samsung Galaxy Nexus] AquilaDroid:
Aw shucks, guess that was just a dream. We'll keep watching and waiting, hope you have a good day!

From my Nexus 5
[Samsung Galaxy Nexus] mastertech007:
NNNNNOOOOOOOOOO !!!!!!!!!!!!

Sent from my GNex running Omni FML on Tapatalk.
[Samsung Galaxy Nexus] MWisBest:
NOOOOOOOOOOOOOOO
[Samsung Galaxy Nexus] Rushead:
The ultimate Lucas travesty.

I grew up with a healthy fear of Darth Vader only to become a man and realize he's just a little whiney *****. Saddest day of my life.
[Samsung Galaxy Nexus] quickdraw86:
Hmm... I always thought that the emperor was the more terrifying of the two, because, as scary as Vader was to me as a kid, he was a slave himself, who lived in fear of the emperor...
[Samsung Galaxy Nexus] mastertech007:
Cricket noise:

Sent from my GNex running Omni FML on Tapatalk.
[Samsung Galaxy Nexus] p34rp34r:
i know...getting flash withdrawls. no rush though [MENTION=3390093]MWisBest[/MENTION]! much rather have a polished, feature-packed product than random update with almost nothing to enjoy.
[Samsung Galaxy Nexus] Rushead:
[MENTION=341447]MW[/MENTION] is probably all hopped up on Coke (a-Cola) enjoying his new toys.
[Samsung Galaxy Nexus] MongolPup:
When cujo6801 said Android was a drug he was spot on. I check this thread way more than I should because wanting a fix...errr looking for a new build to flash!
[Samsung Galaxy Nexus] mastertech007:
I check this 6 - 10 times a day. Now I know how a junky feels.

Sent from my GNex running Omni FML on Tapatalk.
[Samsung Galaxy Nexus] MWisBest:
Actually lately it's been Pepsi Throwback (the made-with-real-sugar stuff), was able to get 4 12-packs of it for $6. Like I said before, I can really stretch money far!

But otherwise, yeah, the new toys have been a lot of fun. The car mount is absolutely amazing. I found some new bands that I like (which is rare for me, my taste in music is picky to say the least), Dead by April & Glamour of the Kill, so I've been rockin' out in the car with it. :D

Note: Why the hell do some of the bands I like have the weirdest names? Bullet For My Valentine, plus the two I just mentioned, I'm almost uncomfortable saying their names... but their music is good! :eek:

College is kicking in to full swing now. Gas is going to cost me $30/week, and it's going to cost me a zillion hours of time, so my time for FML has really taken a huge hit. I'm thinking I'll need to switch to a different system of FML releases, where I have a Beta build and a Stable build. The hold-up for me releasing a new build lately has been that it doesn't feel complete and stable like previous releases, and it's been two months since the last official build which is just ridiculous and is pissing me off. Another contributing factor to the delay is that I'm writing a lot of my own code for this build, especially with the kernel. The majority of the things I've done with FML code-wise previously have just been fixing bugs and things like that, and not writing a kernel driver from basically nothing like I am now. Right now I'm working on "Charger Control". This is intended to be a replacement for the current "fast charge" stuff. The idea is to allow for 'slow charging' via wall chargers in addition to the usual option of allowing 'fast charging' via regular USB ports. The life of the battery can be improved by charging it at a lower current, so this way people who don't need to charge their battery super fast (like me usually) can have their battery not 'degrade' so much.
[Samsung Galaxy Nexus] MongolPup:
MW I hope I've just taken a bad luck phone hardware failure bullet for you. Was answering a text and all of the sudden it dropped signal and never got it back. Unknown baseband, unknown IMEI, intermittent bootlooping. My SIM worked in another phone and flashing factory firmware, reflashing the radios etc didn't help as it always failed.

Had a friend with a GNex with a cracked screen that was unusable so I swapped the internals and I'm up and running again.

You're welcome, develop away ;)
[Samsung Galaxy Nexus] MWisBest:
Been working on a new build, unfortunately the one I did last night had some pretty bad issues. Monday (today) is my busiest day at college so there probably won't be anything new today. :/

On the bright side, I finally got around to making an FML GApps package. It's pretty hackish and not release-ready yet but it should be good-to-go for when I get the next FML build out.

Cool news is that TWRP now supports MTP and has been bumped to version 2.8.0.0, and when I fixed ADB in TWRP it made the USB connection say it has MTP support as well so it'll be good-to-go right away with a new TWRP build I'll release soon!

Yikes! I guess mid-to-late 2014 has been a bad time for the Galaxy Nexus!

By the way, if his GNex is a 16GB and yours is a 32GB you might be able to use the 32GB eMMC. It's on the SIM tray, separate from the motherboard. Or if they're the same size you could at least get all your data off the old eMMC.
[Samsung Galaxy Nexus] quickdraw86:
Smitty's unofficial TWRP?
[Samsung Galaxy Nexus] bsmitty83:
"My" twrp is simply built from Omni's source so I'd say they are the same but its not mine [emoji39]
[Samsung Galaxy Nexus] quickdraw86:
Hmm. Thanks for the info, was just unsure in which thread to find TWRP 2.8.00.
[Samsung Galaxy Nexus] MWisBest:
The FML TWRP builds are built with the same optimizations that the FML ROM uses, which I'm not really certain if it makes things like flashing and wiping faster, however it improves the speed of decryption tenfold. I'm not exaggerating, it's that big of a difference.

It'll also use an updated libpng with the next builds of it, and I'm working on something that'll allow themes to cut down their size, which I hope can be merged into the official TWRP code at some point.

Other than that they're pretty much the same.
[Samsung Galaxy Nexus] MongolPup:
The donor was a 16/I have a 32 and I did swap them...I don't think I could survive with "only" 16 gigs, which definitely says more about me than the phone!
[Samsung Galaxy Nexus] MWisBest:
Still working on a new build, but college has eaten into the time I have available for FML. I was hoping to have a new build out a few days ago but I'm having an issue with something I'm trying to add to the kernel. Hopefully I'll have it sorted out within the next couple of days!
[Samsung Galaxy Nexus] AquilaDroid:
Hang in there, remember that college comes first. We'll enjoy the update when it's ready!

From my (Toro) G-Nex
[Samsung Galaxy Nexus] rice923:
If you don't release a build in the next 48 hours... I will find you... And I will steal your soda
[Samsung Galaxy Nexus] JoeSyr:
While you're working on the kernel, this commit seems to have just worked its way into CM and most actively developed kernels. Do you think you would be able to add it to official OmniRom too?

If I understand it correctly it sounds like the bluetooth chip is always on at boot even if BT is disabled, and will stay powered unless BT has been toggled on/off since last boot.
[Samsung Galaxy Nexus] Rushead:
Don't steal it, just replace his coke with crack. [emoji12]
[Samsung Galaxy Nexus] MWisBest:
DON'T YOU DARE TOUCH MY SODA! I WILL STAB YOU!

http://i.imgur.com/LxM1u5j.gif (<-- not embedded due to language, view at your own risk...)

Yep I'll be getting that in there, I've already got it into the FML kernel. I've been hoping to replace the OmniROM kernel with the FML kernel once I get it stabilized actually.

Get out. GET OUT!!!!
[Samsung Galaxy Nexus] MWisBest:
Still super busy with school guys, but a new build is on the way soon! Going to try something new... it's gonna have some issues at first but I think I can take a stab at getting it fixed. There's a bunch of other people working on it as well, so if I can't figure it out one of them surely can.
[Samsung Galaxy Nexus] vrahn:
I need a flash fix!!! I havent switched roms in some time
[Samsung Galaxy Nexus] MWisBest:
So... this is what I've been working on.

Note the GPU Version section.

Pretty much all the progress made on this is because of [MENTION=2633638]Ziyan[/MENTION], so big shout-out to him.

Right now we're still in the same boat of the cameras not working with the new GPU drivers, as well as hardware video decoding and encoding not working, but I'm trying to make some headway with it. I went from Camera FCing upon opening to just the "Cannot connect to camera" message so far at least.
[Samsung Galaxy Nexus] MWisBest:
Anybody interested in test builds of this? I know there are some shutterbugs out there and YouTube fanatics etc... for what it's worth, I wouldn't really need bug reports and logcats on it unless it isn't related to the camera and video encoding/decoding. A restriction on these builds would be that other kernels couldn't be flashed, however I have at least added overclocking support back (with the following frequencies: 350MHz, 525MHz, 768MHz, 998MHz, 1200MHz, 1350MHz, 1500MHz, 1632MHz, 1747MHz. It seemed like a fairly optimal curve to me, but it is certainly changeable based on your guys' feedback).
[Samsung Galaxy Nexus] p34rp34r:
I'll take a crack at this... i have flash withdrawal, so I'll take anything!
[Samsung Galaxy Nexus] Rushead:
I'd like to see something in the 200s range also. It may be placebo, but I usually run my mins below 350.
[Samsung Galaxy Nexus] MWisBest:
I hope to have something up today! :)

Before I add something lower, I'm going to ask you to check what voltage 350MHz gets calibrated at with SmartReflex on the new build (whenever that gets released). The way I usually check that is the Info page in TricksterMod; wait for the frequency to drop to 350MHz, and see what it says at the bottom for MPU. If it's 840mV, that's the minimum allowed voltage, so a lower frequency won't do you any favors. Otherwise, I think I'd maybe consider dropping the 350MHz frequency to 330MHz or something. Adding another step to the frequencies to try and save a few mV of power isn't worth it in terms of performance to have an extra minute worth of battery life, but if somebody has a chip that runs 350MHz at 890mV or 900mV or something then a lower frequency would be worth it with the inclusion of a minimum screen-on frequency. I could also check to see if there's any issues with allowing for a lower voltage than 840mV as well...
[Samsung Galaxy Nexus] MongolPup:
Looking at those OC frequencies, have any of you (personally) daily driven this phone above 1500MHz?
[Samsung Galaxy Nexus] Zer0_Cool:
Yep, 1520
[Samsung Galaxy Nexus] MWisBest:
Dammit. Ran into a problem with the build I tried last night... today I'm loaded up with homework, so I don't know if I'll get a build out today either.
[Samsung Galaxy Nexus] p34rp34r:
I hate to add to your work, but do you have any ideas about this messed up video (attached image)? It's basically unwatchable, since I feel like I'm going to have a seizure watching this. I have no idea what info is relevant, so I attached logcat and dmesg as well.
[Samsung Galaxy Nexus] MWisBest:
Which build is this on, what kernel are you using (I presume the FML kernel?), and can you try a different kernel? Trying to narrow down where the issue is...
[Samsung Galaxy Nexus] p34rp34r:
Whoops, forgot to include that info. I think this is a 4.4 issue on the Gnex, since it's happened on multiple combinations of ROMs and kernels. Just tried the latest DirtyV (9/28 by [MENTION=4544860]osm0sis[/MENTION]) and it does the same thing. I was just wondering if you had any ideas about it or if you think the 1.9 ddk will help.

ROM: 8/24 Omni-FML

Kernel: FML and DirtyV 9/28
[Samsung Galaxy Nexus] DR3W5K1:
Im not running your rom but fwiw.. My voltage goes down to 820 when my phone his my lowest frequency of 190MHz.
[Samsung Galaxy Nexus] mastertech007:
I would try flashing back to stock and check. Could be hardware issue. Especially since it is happening with multiple ROMs. Just my 0.02
[Samsung Galaxy Nexus] ashclepdia:
fwiw [MENTION=3390093]MWisBest[/MENTION] , regarding lower voltage&freq, when I used to run kernels that allowed me to lower the smartreflex calibration min, and used either 190 or 230 mhz as min freq, I could stably run both of those at voltage of 770. I used to set it to 775 though just to be "safe".

and I was also able to run 350mhz min freq at a stable voltage of 780.

but I know NOT all chips are equal and some others experience may vary. just wanted to chime in.

man I miss having a working device :(
[Samsung Galaxy Nexus] terminal13:
[MENTION=3390093]MWisBest[/MENTION] thanks for keeping the gnex going. Just picked up a g3, on to the next...
[Samsung Galaxy Nexus] raing:
Have fun doing nothing to it with the locked bootloader. I would buy a g3 if the bootloader wasn't locked down :( Waiting for the nexus 6 instead.

Also, MWisBest, thanks for all your hard work to keep the old trusty galaxy nexus current! Still running your 7/5 build and eagerly awaiting the next build!
[Samsung Galaxy Nexus] terminal13:
Yeah it is pretty lame. But the device itself makes up for it until that magical far off day:D:D:D. At least I have root access for now.... I was going to get a one plus or a nexus but Verizon (the biggest double edge sword in existence) is the service I really wanted, because in south Carolina, every other carrier sux it. So I jumped and now I wait. :(
[Samsung Galaxy Nexus] MWisBest:
WOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOT.

I got hardware video decoding working with the new GPU drivers!!!!!!!!!!!!!!!!! I've been obsessed with this for weeks and working non-stop on it. Any time not spent on school, has more or less gone to working on this.

Camera is still borked, and I presume hardware video encoding as well (how can I test that without the camera..?), but it's certainly close!

Here is the test build I've been promising... maguro will come probably tomorrow.

omni-4.4.4-20141006v2-toro-FML.zip

EDIT: Main post has been updated and will now display beta builds such as these in addition to the stable build.

Note that you cannot flash a different kernel with this build. Reach out to your favorite kernel developer and let them know they should consider rebasing their kernel on top of the stable branch here: https://github.com/Ziyann/omap In doing so, they'll be just a few commits away from the updated GPU drivers (meaning retaining current compatibility with ROMs using the old GPU drivers), so when the camera is fixed with them (hopefully by L) they just need to do a couple cherry picks and we can get everybody using these new drivers ASAP.
[Samsung Galaxy Nexus] Shilalygawd:
Can't wait to check it out after work!

Would any of you happen to know of any Call Recording apps that would work on our GNex in 4.4.4? All I know of is CM11's and I really don't want to get off OmniFML lol.
[Samsung Galaxy Nexus] p34rp34r:
It's horrible [MENTION=3390093]MWisBest[/MENTION]! Games are too fast and smooth so they've become too hard! It was so much easier when they were a little slower and choppier! j/k

Seriously, once the ROM had a little time to settle, it's been running great! I can't recall off the top of my head, but I think the new GPU drivers are helping, since the DNA portion of the Quadrant test is hovering around 50 fps, which I think is better than before? AnTuTu changed their benchmark since last I tried, so I can't compare those. GPUBenchmark3D scores worse by ~1000 points, but that last time I ran this, I was still using mpokang kernel and we all know what weirdness that kernel had, so who knows.
[Samsung Galaxy Nexus] smokeydriver:
Running the beta build with the suggested GApps kept faulting. It installed just fine, but once I got near the end of the setup stuff, it kept faulting. I think it was a muiu fault or something like that. Sorry I didn't pay better attention. I tried it with other GApps, and it's starting up just fine. Not sure what else will come up as I am just getting my downloads going.