yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] MWisBest:
Here's an update on progress towards the next build:

I have been hacking up the RILs for all three Galaxy Nexus variants. It's quite a task, and I'm crazy for trying it (there's no source code for this crap!), but it helps with future maintainability of these devices.

With the changes I've made to the toro (Verizon GNex) RIL, I have fixed a long-standing issue that has really been pissing me off. You remember the issues with the Mobile Network Settings that appeared in KitKat (and continued over into Lollipop)? Where picking "LTE" didn't stick? That had required a patch to Android to fix it, and I was ****ing sick of that, as it was yet another fork to maintain. To put it simply, the toro RIL wanted Android to tell it "use band configuration GLOBAL" to turn on LTE, when really it should be told "use band configuration LTE_CDMA_AND_EVDO", so without patching Android the two argued over the issue and "came to an agreement to just use 3G only". Now instead I got the RIL patched (with a total of 7 bytes changed out of over 700,000 bytes) and there's no longer any arguing.

For the maguro (GSM GNex) RIL, I'm trying to fix an issue that appeared in Lollipop, where long SMS messages do not send. The issue is that Android started to use the "SEND_SMS_EXPECT_MORE" request, which is identical to the standard "SEND_SMS" request except it lets the RIL know that more SMS messages will be sent shortly. This gives the RIL the option to keep some sort of link open so that it can be more efficient. The problem is that because it was never used before, this is what Samsung implemented for it in the RIL: Pastie - requestSendSmsExpectMore(). It doesn't take a programmer to see that's not going to be sending any text messages any time soon! To fix it I'm attempting to redirect it to the standard SEND_SMS function. I've had a couple brave users test it and the results look promising.

Here's what I have left to do for the new build:

Get synced up with AOSP. I am way behind and need to get updated to fix some bugs as well as a few security issues that popped up since the last FML build.

Pull in some changes to the kernel. There's some security fixes needed here too, plus improvements to other things done by other developers here.

Get SELinux working properly. Again, another security thing, but this is something I really should've done before, not just something that came up all of a sudden over the past few months.

Clean up my 'unified build' stuff (one ROM that works on all Galaxy Nexus variants). There's a couple issues with it currently:

It requires a small but ugly change to the build system. No ROM that supports devices other than the Galaxy Nexus would consider merging it.

It only does the changes necessary for the device (setting up maguro-only stuff on a maguro, or setting up toro-only stuff on a toro) on the ROM's first boot, and does not do them when the ROM is flashed. This method does need to be in place so that it works when a system image is flashed from fastboot rather than a ROM zip being flashed in recovery, but making the device-specific changes when the ROM is flashed is more reliable.
[Samsung Galaxy Nexus] musical_chairs:
Awesome work! Your patched toro RIL is working well on my CM-12.1 test builds so far, great work at making this phone easier to maintain.

I've got SELinux set to enforcing and working well on toro and toroplus, my info is posted here and here.
[Samsung Galaxy Nexus] MWisBest:
My dad surprised me with a Nexus 6 today! :)

Don't worry though, I'm not leaving my Galaxy Nexus behind anytime soon. I may not be able to do much with the RIL anymore however.

New build is getting closer to being ready. I'm set up with the latest AOSP 5.1.1 tag now, and I have cleaned up 1 of the 2 messy things I did for the unified ROM building.

What's left:

1. Fix the other part of the unification mess.

2. Kernel updates and bug fixes.

3. Get SELinux working properly.

Hopefully can have that ready this weekend.
[Samsung Galaxy Nexus] MWisBest:
Sorry on the wait guys. As you may have already realized I am awful with time estimates. Lot of stuff going on in life, college getting back into full swing, etc. :/

I did take a slight detour to get FML running on my Nexus 6...

Highest I was getting stock was 48,500. It is nice to have a clearer view to see that the optimization stuff I do really does make a difference, it was getting quite difficult to see on the GNex lately!
[Samsung Galaxy Nexus] jguerdat:
Any updates? I'd love to have a new build. Thanks for all your hard work!
[Samsung Galaxy Nexus] Razvan:
Thread cleaned.

Please show some respect to dev and other users.

Its very rude to post in a demanding way, nobody owes you anything

Razvan

Forum Moderator
[Samsung Galaxy Nexus] traco1:
wow & thats the name of that tune eh?
[Samsung Galaxy Nexus] MWisBest:
Right now I'm super busy with school still, so currently my plan is to just work with [MENTION=2633638]Ziyan[/MENTION] on getting things stable for M.

Basically I'm hoping he can be the one releasing test builds but we can put our heads together to fix the issues that crop up.

He's made far more progress than I've had the time for, so I think this is the best use of my time towards getting Marshmallow running well on the Galaxy Nexus. You may not see my name in the news for this update like the last few though! :P
[Samsung Galaxy Nexus] jguerdat:
Do we still monitor this thread for progress?
[Samsung Galaxy Nexus] :
Thread cleaned.

Warning:

Keep all disagreements and arguing to PM and not in open forum. Any further abuse of the rules will result in more serious action being taken.

Regards,

The_Merovingian

Forum Moderator
[Samsung Galaxy Nexus] traco1:
Thank You maybe this is the end of this
[Samsung Galaxy Nexus] bsmitty83:
That goes for all 6 of us that still own a Verizon galaxy nexus and are active in this community ......lmao

Just having a laugh my good Mod . no offense.
[Samsung Galaxy Nexus] Ozzie12:
Yeah...picked mine up again after sitting a while.

I still like it just fine.

I'd rather have a little control and privacy.

Taking the battery out to kill it is good too.
[Samsung Galaxy Nexus] MWisBest:
Wow, I just realized this thread has 349 pages. The GSM Galaxy Nexus thread has 311. I can't believe how crazy this stuff has gotten over the past 2 years. When I first started making this ROM, I thought it would maybe get used by a few people at most. I know I haven't been as active with releasing new FML builds, not even close in fact, but over time things have changed.

FML first started out as just trying to squeeze some extra speed out of Android with our aging device, but over time I found that the largest improvements came from big picture things that can improve every ROM in this community rather than just FML. Instead of sitting in my own little corner doing things for just me, I started a huge collaboration with other developers in this community. FML turned into my "crazy idea tester", and because of that FML has never been in a state where I felt I could release a build for you guys to use, but instead has come up with stuff that the entire community benefits from rather than just myself. Soon I hope to get back to where FML started and do releases often, but as I said before this is a time where I want to do everything I can to help everybody as a whole.

I want to thank everybody here for their support, I love this community and want to see us all succeed!
[Samsung Galaxy Nexus] otter34:
Thanks for all your work
[Samsung Galaxy Nexus] rice923:
Just saw this thread randomly on my notifications. It's been a long time since I've been here but I'm shocked to see this thread going strong.

MW, keep up the good work. Good luck in school and I hope all your car problems of yesteryear are no longer so.
[Samsung Galaxy Nexus] MWisBest:
PLEASE FOLLOW THE FML THREAD IN THE REGULAR "Galaxy Nexus Android Development" SECTION INSTEAD NOW.

Here's a direct link to it: http://xdaforums.com/devdb/project/?id=4352

With Android 6.0 and up, expect every ROM for the Verizon Galaxy Nexus to be in that forum section now. Just make sure the ROM developer (beit me or somebody else) mentions that it is a unified build. It took a lot of hard work, but I finally got it stable and working well. As soon as you flash the ROM, it will make the necessary adjustments for whatever version of the Galaxy Nexus you're using now.

Thanks man. School is going better, and my car is fantastic; took a lot of work to get it there but yeah lol.
[Samsung Galaxy Nexus] Joeisgood99:
Thanks for your work [MENTION=3390093]MWisBest[/MENTION] !!!

Anyone know how to fix this error.

host C: libaapt_32 <= frameworks/base/tools/aapt/qsort_r_compat.c
frameworks/base/tools/aapt/StringPool.cpp: In member function 'android::status_t StringPool::writeStringBlock(const android::sp<AaptFile>&)':
frameworks/base/tools/aapt/StringPool.cpp:474:45: error: invalid conversion from 'char16_t*' to 'uint16_t* {aka short unsigned int*}' [-fpermissive]
frameworks/base/tools/aapt/StringPool.cpp:36:6: error: initializing argument 1 of 'void strcpy16_htod(uint16_t*, char16_t const*)' [-fpermissive]

Is this the sort of incompatibility used as an example in post #3?

I was inspired by MWisBest OP (great read btw) to start optimising my CM12.1 build for my HTC m7

I started cherry picking

"#Make GNU++11 the default standard version type "

commits from MWiseBest Git repo.

like

+COMMON_GLOBAL_CPPFLAGS:= $(COMMON_GLOBAL_CFLAGS) -Wsign-promo -std=gnu++11

etc.

I have sifted through to find all the C++11 fixes that apply to my phone and patched them in to my build in an attempt to get this working but no joy.

Id eventually like to get LTO and strict aliasing to work. as well

I get the same error with MWisBest Linaro-4.9 tool chain and uber-TC-4.9 & 4.8

Do i need to disable something locally? Any help, advice or articles for reading/learning would be appreciated. Also if anyone has done this a few times and have made these changes in one big commit please point me to it so I can have a look.

I understand this thread is not for my phone or even how to compile FML but I’m assuming someone (if not at least the OP) has compiled with these flags successfully and give me a pointer or two.

Thanks.
[Samsung Galaxy Nexus] MBQ_:
Have you tried clearing data? And, are you on the latest version of titanium backup? It was updated here earlier today (Arizona, USA), and I know it sometimes differs.

Also, if all the stuff above doesnt work, if you have the time, can you please pull a log with the FC? I'd like to *try* and take a look at it to see if it'd be an easy fix, and to take some stress off of MW's back. :)
[Samsung Galaxy Nexus] rester555:
Sorry MBQ, I already reverted to last build. :( I will try to pull a log and yes, I have the latest titanium backup and did a fresh install. I will revert to this build and try to get a log. What do you recommend to log?

EDIT: This is also with ART runtime enabled, also after installing the ROM and gapps, when it boots up for the first time, I have to do a battery pull and then after it boots up a second time, it makes it through initial setup.

Running on CWM 6.0.4.3 with latest bootloader as well.
[Samsung Galaxy Nexus] MBQ_:
ohhhhh, okay.

As I know you know, ART isnt necessarily 'stable' yet for our Nexus', so im sure that's to blame for your Titanium backup mishaps
[Samsung Galaxy Nexus] rester555:
I figured as much, thanks. I am going to keep it running on davlik then. When ART is enabled the device flys, but yes many things not working for me at least.
[Samsung Galaxy Nexus] MWisBest:
Wasn't able to figure out what's wrong with this data setting overlay crap yet. Nothing new has really happened in CM lately anyway so there's not a reason to put out a new build if nothing has changed. Been a little busier with things lately too. >.<
[Samsung Galaxy Nexus] metalspring:
There is a fix you can cherry pick

I've been using it and it works just fine

http://review.cyanogenmod.org/#/c/53131/

and heres another quick one thats supposed to fix ART breaking superuser

http://review.cyanogenmod.org/#/c/53956/

You might have to wait though... cyanogenmods gerrit seems to be down at the moment :(

Btw, as far as adding features go, there are also working open gerrit commits that add quick setting tiles, quick pulldown, long press back to kill app and some other useful features

All the ones I've tested so far work pretty well
[Samsung Galaxy Nexus] DevVorteX:
You guys should just team up to make the ultimate ubber unofficial cm 11 rom for the toro (uuucm11_toro) pronounced "ohhhhh CM11 toro" :D
[Samsung Galaxy Nexus] PalmerCurling:
CM's online stuff (gerrit etc) is down for a few hours for server maintenance, per their G+ account.
[Samsung Galaxy Nexus] MWisBest:
I already have Superuser working with ART, but thank you, and I will check out that first fix you linked once gerrit comes back up. I also have one of the Superuser security issues that was mentioned in the news lately fixed as well.

EDIT: Looks like their gerrit is back up, and that fix is indeed the final piece of the puzzle. Thank you very much for the heads-up, not sure I would've noticed it otherwise! I will get a new build out soon with this pulled in there.
[Samsung Galaxy Nexus] Enter The Nexus:
Webview is fixed? When is the new build coming?
[Samsung Galaxy Nexus] David 617:
nvm. delete
[Samsung Galaxy Nexus] MWisBest:
Sorry! Got busy with some homework stuff, big test tomorrow. The webview fix isn't merged yet, but I'll cherry-pick it in or something. I was actually hoping to have more time to be able to play around with adding some features to the kernel, but this is definitely more important. :good:
[Samsung Galaxy Nexus] Enter The Nexus:
Thanks man I can't wait.
[Samsung Galaxy Nexus] MWisBest:
I'm syncing up my code and then I'll run a fresh build. I'm not sure if I'll be awake when it finishes, I might just try to get in a power nap or something; if all else fails, I'll upload it in 9 hours or so when I wake up from sleeping. I hate to keep you guys waiting! :(
[Samsung Galaxy Nexus] oman0123:
Go get some shut eye. Nobody will notice a couple hours difference.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] Rushead:
...except us crack flashers... :banghead: :banghead: :banghead:

Sent from a frequent flasher.
[Samsung Galaxy Nexus] oman0123:
Touche' lmao. I use to be like that with Droidtheory's Rom. Can't forget anything back on the og droid.

Man I remember rooting my phone manually. Reading hours upon hours. It took me so long to do lol Now we have one clicks and all in one toolkits.

Listen to me sounding like an old man.

/nostalgia kick

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] David 617:
Wow. Talk about a trip down memory lane...

I remember DT's Roms for the Thunderbolt and the the GNex. Those were the days... Sigh. Lol
[Samsung Galaxy Nexus] MWisBest:
I did get some sleep. I'm uploading and flashing the new build as I type this, if it boots I'm gonna post it right away.

EDIT: NEW BUILD UPLOADED. BYE BYE BLACK BOXES!
[Samsung Galaxy Nexus] taz1458:
For whatever reason when I try to flash, it's saying I'm on a maguro device. Any ideas why?
[Samsung Galaxy Nexus] thetakerfan:
I just flashed new build and didn't have any issues, was a dirty flash though. Confirmed no black boxes in Google Rewards which was the most annoying app I had with the boxes (even though I've only gotten one survey so far), so glad its fixed.
[Samsung Galaxy Nexus] Zer0_Cool:
Doing a clean install right now, will report back shortly :cyclops:
[Samsung Galaxy Nexus] MWisBest:
This would happen if you flashed a recovery that was built for maguro (GSM Galaxy Nexus) and not toro (Verizon Galaxy Nexus).

If TWRP is your preferred recovery, this is the latest version for toro: http://techerrata.com/file/twrp2/toro/openrecovery-twrp-2.6.3.1-toro.img

If CWM (touch) is your preferred recovery, this is the latest version for toro: download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.3-toro.img

You can also find the CWM download in the Downloads section in this thread.
[Samsung Galaxy Nexus] taz1458:
Figured it was something stupid. Does anyone have a zip of the cwm recovery? Think I'm missing it.
[Samsung Galaxy Nexus] thetakerfan:
I Dled the IMG file and used flashify from the play store to flash it that way, easier than setting up ADB on the machine I was using at the time.
[Samsung Galaxy Nexus] airmaxx23:
Just an FYI for other people. I had an older version of TWRP installed and was getting a status 7 error when flashing the ROM, once I updated TWRP everything installed fine.
[Samsung Galaxy Nexus] ironfisted:
Does this ROM have the quick settings toggles?
[Samsung Galaxy Nexus] chris157:
What is everyone using for photoshpere on this ROM? I tried using the gapps add-on but it says nexus 4 and 5 only.
[Samsung Galaxy Nexus] jlvlawrence:
Just install ROM manager and let it install it for you. Or you can also get the .IMG file from the clockworkmod website and use flashify to install it.

Sent from my Nexus 10
[Samsung Galaxy Nexus] airmaxx23:
I'm trying to install this from a USB-OTG flash drive but I keep getting "can't open zip file" any suggestions?
[Samsung Galaxy Nexus] Enter The Nexus:
This is running great. Thanks [MENTION=3390093]MWisBest[/MENTION] !!!!

---------- Post added at 04:45 PM ---------- Previous post was at 04:45 PM ----------

Yes and they're editable.
[Samsung Galaxy Nexus] taz1458:
FYI, I used flashify to get the updated and right recovery. Flashed this, the recommended gapps, and mpokang kernel. So far 0 issues other then the rotate stuff which I don't even really notice. Super fast. Loving it so far!
[Samsung Galaxy Nexus] stangdriverdoug:
I just wanted to chime in here. I just flashed this last night and everything is running well. No reboots or lock ups. I'm coming from a 4.2 rom and this seems a little smoother. Anyone know where I can try a custom 4.4 kernel for a little over clock?
[Samsung Galaxy Nexus] bluerez79:
Tiny kernel 5.3.1 is what I am using. Works very well
[Samsung Galaxy Nexus] Sonicmax2k2:
The 11/21 version is working very well for me! The GEL is a bit laggy so I went back to Nova, but everything is very stable and I haven't rebooted at all since installing it. I'm only seeing the black boxes during the screen rotation animation, but otherwise the visuals are just fine! ART was great, but I switched back to Dalvik because a few apps (mostly TitaniumBackup) weren't playing nicely with it. Overall a great build and an impressive improvement in a short period of time!
[Samsung Galaxy Nexus] Zer0_Cool:
Everything is working so far. Only problems I had were when I switched to ART, google keep and the camera got borked. Cleared the data and force stopped keep, then it worked after a reboot when it rebuilt it's cache or whatever ART does on first boot. The camera still would not detect, so I switched back to Dalvik.
[Samsung Galaxy Nexus] MWisBest:
Thanks for the feedback guys! I'm glad everything seems to be running great in the new build. I'm going to try getting a new build out tonight with overclocking and undervolting stuff added. I don't want to add too much at once, and now seems like an OK time to do stuff like this as CM looks a little quiet right now.

Here's the problem... I got Need for Speed: Rivals last night (for those who didn't know, my name stands for "Most Wanted is best", referring to Need for Speed: Most Wanted (the 2005 version, not the new 2012 one)), so that's one distraction. Aaaand, to top it off, I got a beta invite to The Elder Scrolls Online which starts tonight at 5PM. If a new build isn't out soon, blame Ghost Games and Criterion Games (developers of NFS Rivals) and ZeniMax (developers of The Elder Scrolls Online)!
[Samsung Galaxy Nexus] DevVorteX:
cough...cough...NERD.....oh wait, we all kind or are :) #jealous
[Samsung Galaxy Nexus] Enter The Nexus:
Thought is was Modern Warfare Is Best when I first saw it. I was like "this guy is awesome." Did you buy a PS4 or XBox One? Or is it for PS3/Xbox 360?
[Samsung Galaxy Nexus] Sonicmax2k2:
Take a break and enjoy your accomplishment with some video games. You deserve it! :)
[Samsung Galaxy Nexus] swarlesbarkely:
Oh I don't know much about building ROMs or anything like that I was just giving feedback. I'm more of a test dummy than anything
[Samsung Galaxy Nexus] MWisBest:
Without "test dummies" giving feedback a developer would have a hard time fixing bugs and would be discouraged by the lack of interest in what they're making, so you're more important than you think! I really do appreciate everything people say. You won't believe the amount of times somebody has said something that ends up making me think of something differently and results in a fast fix to something I might have been struggling with or just simply overthinking.

Just a little update on what I'm working on: I'm really working hard on getting mobile data fixed up! From what I can tell the VZW Galaxy Nexus radios/RIL are... "strange." It looks like they don't do what Android is expecting of them in some ways, so I'm trying to fix some of these "quirks." I've never really tried to debug the RIL, however I'm making progress with it and learning as I go.
[Samsung Galaxy Nexus] MWisBest:
Alright, threw up a new build that appears to have fixed the mobile data issues from the first build of today. Will still be working on improving mobile data, it's definitely far from perfect!
[Samsung Galaxy Nexus] db306:
Gonna give her a go now!!
[Samsung Galaxy Nexus] swarlesbarkely:
I gotta say I love your dedication
[Samsung Galaxy Nexus] MWisBest:
Thanks, I like to try my best at whatever I do. :)

I don't think I'll be able to get up a 09/03/2013 build, today I started school again and I still have to work yet tonight. It looks like I'll be working Tuesday, Friday, and Saturday nights for at least the next couple months, and I'll have school Monday through Friday, however I don't have many classes for at least this semester.

I did encounter an issue with mobile data at school today, the one that I had mentioned required a reboot to fix and then might not even fix itself again... Toggling Airplane Mode didn't fix it, however leaving Airplane Mode on for a few minutes and then turning it off restored data connection. There's a decent 4G LTE connection at school so I'll be able to test 4G LTE more now as well!

As for what I plan on doing with the ROM for a potential 09/04/2013 build, I'm going to keep working on mobile data but I'm thinking I might experiment with some potential open-source versions of some of the proprietary things (sensors in particular). It looks like there was some work done with other OMAP4 devices on making open-source versions of them, and the reviews were good on them as well. I'm not really sure if it can be done (or if I can do it, at least), but I'm a huge fan of open-source things. Everything I've done with the FML ROM is right on GitHub and anybody can just go and build it no different than any other CM-based (or AOSP-based?) ROM. Actually it's probably simpler than CM, as the proprietary libs are just fetched automatically, rather than having to make a local_manifest.xml containing them.

Sorry... I tend to ramble on and on sometimes. >.<
[Samsung Galaxy Nexus] swarlesbarkely:
Don't know if this is normal but with expanded desktop on there's still a barely visible navigation bar. Amoled screens don't burn in do they?
[Samsung Galaxy Nexus] nitsua98:
Yes they do, mine has a slight burn in as well