yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] p34rp34r:
Yeah, I should've been a bit clearer. I wrote up the instructions using adb push, but when I actually did it, I was using adb sideload. :p (As an aside, I made the same exact distinction with [MENTION=5476864]michierusama[/MENTION] a page or two back lol)

Also, while browsing the Nexus 7 threads on f2fs, I discovered this https://play.google.com/store/apps/details?id=com.runnerway.converttof2fs. Maybe we can get our GNex supported and then we can use any ROM we want? :D? Edit: Oh, wait, this costs money. I has no moneys. :(
[Samsung Galaxy Nexus] Hetalk:
Just a minor thing if not already mentioned. People who are not able to do a successful adb push. Try doing it after mounting system partition in TWRP.
[Samsung Galaxy Nexus] Driver007:
There was problems whit adb push for me also, in some aspects seems to be faster than Ext4 especially in booting, I did some benchmarking, results shows that sometimes it's almost the same thing, didn't like the rom so I switched back to Ext4 and waiting till other roms and kernels implement this. Thanks devs for this work!
[Samsung Galaxy Nexus] ILA:
Tried that and it didn't work... I've even reformated everything to ext4 to wipe the ROM - still no adb... Reflashed the f2fs enabled recovery - still no adb... Flashed the stock 2.6.3.2 TWRP and now I have adb again...

---------- Post added at 11:32 AM ---------- Previous post was at 11:29 AM ----------

I did flash the ROM and I've managed to push it to /sdcard/ , obviously, but when I flashed the ROM, the ROM.zip was gone and so was adb recognision...
[Samsung Galaxy Nexus] clnzx2:
Windows 7 pro

---------- Post added at 11:00 AM ---------- Previous post was at 10:59 AM ----------

Restarting recovery fixes this
[Samsung Galaxy Nexus] Nephilim:
Cool man, whenever you get a chance I'd be uber grateful!!!

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

Try using Wheatley or Hyper with my normal settings until Smitty releases his new build, they've been confirmed to fix the issue for now. ;)
[Samsung Galaxy Nexus] mrgnex:
My phone has never been this fast. And it never had this amazing battery life. Thanks [MENTION=1533050]bsmitty[/MENTION] your kernel is awesome keep rocking! With the settings from [MENTION=2853378]Nephilim[/MENTION] my phone flies! [MENTION=3685904]ak[/MENTION] has awaken and returned. This is gonna be epic. Prepare yourself guys ?
[Samsung Galaxy Nexus] bsmitty83:
Still get sods on conservative and interactive with early suspend . gonna try some things but
[Samsung Galaxy Nexus] 47th_Ronin:
Has anyone happened to look at the 3.4 "bootable" kernel thread lately?

Maybe something interesting....
[Samsung Galaxy Nexus] Nephilim:
That's the fun of kernel development, you will always have something to tweak and we will always have new kernels to play with! :D :good:
[Samsung Galaxy Nexus] Shambola:
I'm becoming a compulsive "page reloader" on this thread, lol!
[Samsung Galaxy Nexus] Nephilim:
Welcome to the club man. ;)
[Samsung Galaxy Nexus] djtutis:
Don't worry smitty... Sure we'll find a solution! Besides your Linaro kernel is f*cking amazing... No SODs and everything is smooth and blazing fast like a f1 car! Only with Sabermod I have a bit lag at lockscreen and I can't draw a pattern...
[Samsung Galaxy Nexus] metalspring:
Interactive even without that commit isn't working right

I'm also getting the issue where the phone is extremely slow to wake up when you press the power button on interactive on the latest build
[Samsung Galaxy Nexus] Nephilim:
This issue seems to be hit or miss, with my custom settings I literally have no lag waking on interactive.

Side question, even after reverting that commit, the new Liquid Smooth still SOD's within 30 seconds of screen-off while on ART. It's quite strange because I used the exact same settings as 1/18 build on the new Official built by Sean Hoyt today. I don't understand what is causing it or what could be different.
[Samsung Galaxy Nexus] metalspring:
It could be something in some other part of the source as well, a lot of things are very closely related

---------- Post added at 04:28 PM ---------- Previous post was at 03:50 PM ----------

Also one thing I noticed that isn't a huge deal but could be tweaked is the 512 GPU speed probably needs slightly higher voltages at least on the smart reflex version to work for everyone

It stutters and lags with tears across the screen when scrolling and also sometimes freezes and reboots for me at the stock voltage but worked just fine on mpokangs kernel

I don't mess with voltages myself much so it's tough for me to say just how much it would need raised, anyone else having this issue and have any input?
[Samsung Galaxy Nexus] rtfpessoa:
I experienced that same issue too. I'm currently only using 384MHz to make it work better.
[Samsung Galaxy Nexus] poo706:
I also went back down to 384. I'd get the occasional minor graphical glitch while normally using my phone, but one of my games went haywire with the GPU at 512.

[poo]
[Samsung Galaxy Nexus] Vekhez:
Omfg. Skipped this thread for ~2 days while moving and it went from page 69 to 96....
[Samsung Galaxy Nexus] bsmitty83:
In trickstermod bump core voltage 1 up from 1127 to 1150 and should help

Also using these voltages . there from ak's kernel :thumbup:
[Samsung Galaxy Nexus] rtfpessoa:
Your are awesome. Just tested those freqs with some heavy stres and all seem to be working fine.

Thanks a lot :D
[Samsung Galaxy Nexus] metalspring:
will try that now, also I tried getting a dmesg of the issue with waking up the device when using interactive governor

I hope this has some clues as to what might be happening

http://pastebin.com/BZi69aAM

Btw without knowing kernel coding, 2 things i see that might be effecting wake up are-

<6>[ 6071.257934] wakeup wake lock: gpio_input

or

<3>[ 6073.327667] omapdss DISPC error: SYNC_LOST, disabling LCD

<3>[ 6073.327697] omapdss DISPC error: First SYNC_LOST.. ignoring
[Samsung Galaxy Nexus] Nephilim:
My Core is already hat 1150 without changing it.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] TheMan0790:
Excuse my ignorance, but which builds in OP are 4.7.4 toolchain builds? I find the 4.8 builds do not like my phone too much...

Break me off a piece of that Kit-Kat ROM!
[Samsung Galaxy Nexus] pianistaPL:
4.7.4 - Linaro

4.8 - Sabermod

So you have to download Linaro version.
[Samsung Galaxy Nexus] p34rp34r:
Check to see if Windows lost your device driver by checking the Device Manager. I know that sometimes Windows will forget the phone and I'll manually install the ADB driver again (you'll know it did if your phone shows up with a little yellow triangle). Also try "Scan for hardware changes" in Device Manager. That seems to reinitialize the connection when it drops for me.
[Samsung Galaxy Nexus] pvkiniyan95:
These are my f2fs results

http://pastebin.com/k6YqSm8c

http://pastebin.com/MPgtbBkt

Dmeg/kmsg

And antutu score
[Samsung Galaxy Nexus] pvkiniyan95:
Quite bad on antutu, I don't use it but thought why not and disappointed

---------- Post added at 02:09 PM ---------- Previous post was at 02:07 PM ----------

Do u guys need anything else [MENTION=2838735]aosp[/MENTION] [MENTION=4608636]bsmitty83[/MENTION]

BTW why went back to linaro 4.7.4 from 4.9.1
[Samsung Galaxy Nexus] gautam_nexus:
antutu scores dont help. refer to this

by [MENTION=2838735]aosp[/MENTION]
[Samsung Galaxy Nexus] pvkiniyan95:
Of course antutu wasn't there in that list, didn't he asked not to send benchmarks taken with those apps or did I misunderstood??

Alright [MENTION=2838735]aosp[/MENTION] a comma between CPU and use in that post will avoid misunderstanding....

I read " please don't send benchmarks that stress CPU use, like the one listed below" rather than

"That stress CPU, use like the one listed below"

My bad...
[Samsung Galaxy Nexus] gautam_nexus:
He asked not to use antutu and other cpu bench marking tool instead use the one listed by him. ;)
[Samsung Galaxy Nexus] chongns:
People please don't send me benchmark results from apps that stress the cpu , use flash memory focused benchmark apps like the one's listed below when you post comparision benchmarks thanks :p
[Samsung Galaxy Nexus] pvkiniyan95:
My bad...edited my previous post

Update : benchmarked with A1sdcard benchmark app

out of few i/o schedulers with diff rab like zen,bfq,cfq,fiops,tripndroid,

zen with 512 rab topped all with read 31.7MB/s write 20.91MB/s
[Samsung Galaxy Nexus] Atento:
This post is just to thank you guys [MENTION=2838735]aosp[/MENTION] and [MENTION=4608636]bsmitty83[/MENTION] and others involved in f2fs project. Thank you for bringing this amazing file system to our gnex!
[Samsung Galaxy Nexus] sagara.sandaru:
Ok then for comparison. I got 20.72MB/s Read and 2.22MB/s write. (Zen with 512 rab)

EDIT: GOT THESE RESULTS ON EXT4!
[Samsung Galaxy Nexus] chongns:
Your write speed is ad-normal, normaly is about 20+MB, read is about 29+MB.
[Samsung Galaxy Nexus] pvkiniyan95:
For proof
[Samsung Galaxy Nexus] sagara.sandaru:
Really??? I tried again and this is what I got
[Samsung Galaxy Nexus] metalspring:
That's about what I got too on the f2fs build
[Samsung Galaxy Nexus] pvkiniyan95:
Try changing the schedulers, rab and see where u get the sweet spot
[Samsung Galaxy Nexus] oman0123:
Alrighty....I love f2fs....thats a given.

But im still having this #!&$@ mms issue. Im gonna ask a question that Im sure I already know the answer to and hope that Im wrong.

If I hop back on my ext4 Slim build, am I gonna have to re-format everything again? I know I can just tick it back to ext4 in recovery

:crying::crying::crying::crying: I want working mms AND f2fs :crying::crying::crying::crying:
[Samsung Galaxy Nexus] dezful:
Here's what i got (yellow highlighted). Default kernel settings and f2fs.

Edit: it's interesting to see someone with Galaxy nexus in the middle has different size of internal memory :)

sent from Siemens C55
[Samsung Galaxy Nexus] sagara.sandaru:
Tried different schedulers and got about the same results.. As I mentioned before these results from ext4 ok? Not f2fs
[Samsung Galaxy Nexus] metalspring:
I got about the same on fiops, sioplus, and noop, each one only varied by maybe 1 or 2 MB/s read and write speeds so idk.

That said I did, however get absolutely insane scores with androbench, my gnex basically blew away the m8 scores on it lol (which comparing the specs is very impressive)
[Samsung Galaxy Nexus] bsmitty83:
Can you run 2 benches. One with fsync , one without ? I think I remember someone said fsync can skew the results .

Hack The Tuna
[Samsung Galaxy Nexus] metalspring:
Yeah I didn't think fsync would make a big difference but it does. Fsync on/off makes a massive difference

With fsync-

Without fsync-
[Samsung Galaxy Nexus] bsmitty83:
[emoji6] I love the nexus as much as the next guy (well many not as much as some of the pervs in this thread lol ), but there's no way it'll blow away your m8 .

Hack The Tuna
[Samsung Galaxy Nexus] michierusama:
I feel my phone is blazing fast. I think is so high. Omg. Does it have anything to do with the new format?
[Samsung Galaxy Nexus] metalspring:
Yeah, it's kinda odd just how much of a difference fsync makes on that particular test lol

Although even with fsync on, the gnex does surprisingly well against the m8 in some areas. This is what I get on the m8 on sense anyway, aosp might be higher though
[Samsung Galaxy Nexus] bsmitty83:
Maybe lol , f2fs should be an improvement in overall feel of the phone , every device thread that switched people all say the same so I see no reason why it would be different for us

Yea I was so puzzled by that back on 4.2 , I though it was from running lagfix lol
[Samsung Galaxy Nexus] michierusama:
I think the ROM has something to do too. vanir is blazing fast. :)
[Samsung Galaxy Nexus] metalspring:
Apparently fsync skews a few other tests [MENTION=2838735]aosp[/MENTION] mentioned too, like both of the sqlite benchmarks. The A1 SD bench app seems to be completely unaffected though
[Samsung Galaxy Nexus] michierusama:
OK now something is bugging me. After the format is changed on the recovery to f2fs. Everytime I format or wipe it still will be fs2fs rite?
[Samsung Galaxy Nexus] seriousia:
Change the file size in setting to 32MB

Then you'll get accurate results

Fsync off

Ext4
[Samsung Galaxy Nexus] bsmitty83:
Yes as long as you don't toggle the ext4 switch , if you just use the regular wipe menu it won't change format on you

Hack The Tuna
[Samsung Galaxy Nexus] michierusama:
I'm loving the great job you and AOSP and all others have done.

Also I hope Vanir starts using this on the ROM because SmittyV plus this ROM is flying. For real. I can feel the difference. It's big.

I mean nightlies and so on. Because we are using this ROM for testing right now and it's all good so far..
[Samsung Galaxy Nexus] osm0sis:
Yup lagfix/trimming will also boost the scores back to normal max. Some of those with lower scores could probably fix theirs that way, and should consider using suspend_trim. ;)

Nice.

Just for reference for everyone benchmarking: Smitty/Dirty doesn't use a classical fsync toggle. Enabling dynamic fsync makes fsync "off" when the screen is on. Disabling it makes fsync "on" all the time. :)
[Samsung Galaxy Nexus] oman0123:
Why do I feel like im the only one with an mms issue? Its the only thing that is making me consider switching back.

edit: I do know its not anything related to f2fs or anything like that. Just makes me want to pull my hair out.
[Samsung Galaxy Nexus] Atento:
Do you plan to open a new thread dedicated to f2fs (recovery, rom and kernel)? I think it would organize all the information available here...
[Samsung Galaxy Nexus] michierusama:
Yep. Coming soon.
[Samsung Galaxy Nexus] metalspring:
Doesn't formatting the whole partitions kinda make fstrim pointless? I mean I get it for if you haven't formatted in awhile but you need to format to use f2fs
[Samsung Galaxy Nexus] osm0sis:
Good point. Hmm. Did the people with abnormally low scores move any data back to their device? The data->cache->data trick someone suggested would definitely leave some things to be trimmed behind on cache.
[Samsung Galaxy Nexus] pvkiniyan95:
its me that suggested data to cache to data trick but i dont get low scores in a1 sd card bench mark and i didnt use lagfix...just fyi

update : lagfix fstrim says TRIM not supported in the f2fs partitions
[Samsung Galaxy Nexus] michierusama:
In the SD I cannot delete the Readytoflash! Folder or the ROM inside lol.
[Samsung Galaxy Nexus] bsmitty83:
F2fs uses discard mount option , no trim required .

I build a new recovery a little while ago , different source , the same as the first screenie I put up a while back when we first got recovery working . f2fs works ,adb works , but I need to fix USB otg not mounting on this one . so pretty soon if its all good I'll put it up .

Hack The Tuna
[Samsung Galaxy Nexus] michierusama:
What do you think about DirtyRom? Just thinking...
[Samsung Galaxy Nexus] bsmitty83:
2 out of 3 is enough for me lol , it takes hours for my machine to build a ROM . not saying it'll never happen , but I wouldnt expect one .

..... oh yea my wife would kill me if I added another reason to be at my laptop lol

Hack The Tuna
[Samsung Galaxy Nexus] michierusama:
Bhahaha that pic. XD well I was dreaming a little.
[Samsung Galaxy Nexus] bsmitty83:
Also too , I'm kinda slow sometimes and anyways f2fs should be OK with suspend trim , if it was in the ramdisk lol , I gotta make a boot.IMG zip that's f2fs compatible cause right now its vanirs stock rammy , so suspend trim wouldn't have worked anyhow . I got to check if we're using discard mount option , but even if we were you could still run trim , it just wouldn't be necessary , sorry for that misinfo

Hack The Tuna
[Samsung Galaxy Nexus] chongns:
my result from omnimetal + nephilim setting and F2FS result
[Samsung Galaxy Nexus] BestBrd:
How can i update the rom?And next dirty_v releases will be compatible only with f2fs?
[Samsung Galaxy Nexus] pvkiniyan95:
quick update...my gnex gets better and better after a day of installation....got to say, i hated a few options in vanir which always takes me to ls or omnimetal but this time its better specially the recents lag is pretty much gone after 20hrs of uptime which was a huge surprise however no improvement on the battery side and idle drain is comparably bad to dirtyV (very slightly)...i couldn't test data transfer speed btw how is it guys...
[Samsung Galaxy Nexus] pvkiniyan95:
Yes yes yes, no more playstore lags too
[Samsung Galaxy Nexus] michierusama:
What settings are you using? I can confirm the phone feels a lot better. VanirRom is really good.
[Samsung Galaxy Nexus] aosp:
https://github.com/mpokwsths/mpokang_kernel/commits/final

[MENTION=4328678]metalspring[/MENTION] [MENTION=4608636]bsmitty83[/MENTION] ?
[Samsung Galaxy Nexus] bsmitty83:
Well good for him , now all is well in tuna land . [emoji106] . source code for all .

Hack The Tuna
[Samsung Galaxy Nexus] metalspring:
And perhaps these are the 50% faster ram commits?

https://github.com/mpokwsths/mpokang_kernel/commit/7ba14df4dc6aa867a89fcfefdb887fa0ff1dedc5

https://github.com/mpokwsths/mpokang_kernel/commit/dc82e96cdb0ac6af7f868b9e4fc8a43008c81c08

https://github.com/mpokwsths/mpokang_kernel/commit/ede644fde05ce2dcbf2da79feacf7d869b716447
[Samsung Galaxy Nexus] bsmitty83:
Perhaps [emoji39]

Hack The Tuna
[Samsung Galaxy Nexus] AbhishekS:
Wow! Great to see him posting his sources all of a sudden. Wonderful. :)
[Samsung Galaxy Nexus] Fatsodonkey:
Sorry for asking this here but if i use the f2fs twrp thingy does it change the f2fs to every rom? And is it a permanent change? Also does it need support from roms? Just want to try any speed improvements but dont want to mess my only phone.
[Samsung Galaxy Nexus] ILA:
Curently there is only one ROM that supports f2fs and that is the one included in the *.zip. So yeah, the ROM has to support it as well. If you format the three partitions to f2fs, ofc you can reformat them back to ext4 and than it's business as usual. Keep in mind that you will lose everything on your /sdcard/ when you do the switch... :)

Also brush up on fastboot and adb if you plan on doing this ;)
[Samsung Galaxy Nexus] Reinvented:
Things just got even more interesting.
[Samsung Galaxy Nexus] osm0sis:
:laugh: Better late than never. ;)
[Samsung Galaxy Nexus] michierusama:
But ... No memory its kinda better.
[Samsung Galaxy Nexus] osm0sis:
And 50% faster no memory? :p
[Samsung Galaxy Nexus] michierusama:
I mean. Videoplayback would be unnafected and thats the reason I like it. But well 50% faster its good if some users dont mind losing some "features" right?
[Samsung Galaxy Nexus] osm0sis:
Haha you missed my meaning. ;)

If those are the legit commits, then it's 50% faster no matter how much memory there is. :D
[Samsung Galaxy Nexus] michierusama:
Oops. Lol. Sometimes I get a lil slow lmao.
[Samsung Galaxy Nexus] ILA:
That would be living the dream right there :cool:

Optimize the hell out of tuna and make it open source! Love this thread! :D
[Samsung Galaxy Nexus] metalspring:
Well I have a couple kernels for everyone to test :P

If you are on the f2fs vanir rom use this one-

DirtyV-R-5.3.14-f2fs.zip

If you are on any other rom use this one-

DirtyV-R-5.3.14-test.zip
[Samsung Galaxy Nexus] michierusama:
SmittyV lover here lol.
[Samsung Galaxy Nexus] pianistaPL:
What changes are in second version? :)

Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
[Samsung Galaxy Nexus] michierusama:
I think the differences are the f2fs support and the other ext4.
[Samsung Galaxy Nexus] aosp:
That is 50% correct *f2fs ?
[Samsung Galaxy Nexus] michierusama:
I was 50% wrong
[Samsung Galaxy Nexus] cmoG530:
Didn't boot for me. Vanir ROM.
[Samsung Galaxy Nexus] HaRdC0r3:
[MENTION=4328678]metalspring[/MENTION] ....everything is working for me....Toro F2FS Vanir....anything I should look for specifically?
[Samsung Galaxy Nexus] metalspring:
The f2fs version of vanir or regular version of vanir?

---------- Post added at 09:45 PM ---------- Previous post was at 09:43 PM ----------

Voodoo ;)

(hint look at what was discussed a little earlier in the thread)
[Samsung Galaxy Nexus] cmoG530:
Oops, should've clarified. The regular version.
[Samsung Galaxy Nexus] ASHURiCAN:
What's new on the regular version?
[Samsung Galaxy Nexus] cujo6801:
Same here for me

Sent from the "DOG" pound

---------- Post added at 05:50 PM ---------- Previous post was at 05:49 PM ----------

Did not boot

Sent from the "DOG" pound
[Samsung Galaxy Nexus] apollo07:
On both kernels, its the mpokang's faster memory thingy, he released the source of it, so all the law-abiding development community can sleep well. xD (Please Read the edit thingy)
[Samsung Galaxy Nexus] michierusama:
Please dont say that. Its was not hate. Stop right there before something starts here lol. It was clearly a violation of some rules... Not hate I think.
[Samsung Galaxy Nexus] osm0sis:
FTFY ;)
[Samsung Galaxy Nexus] Punkiderma:
just to know, following this guide on our phone

http://xdaforums.com/showthread.php?t=2694201

using boot.img from commotio f2fs and putting it inside slimkat rom, would work? Or, if it wouldn't, it would brick the phone or just need to reflash everything?

Thanks!
[Samsung Galaxy Nexus] Reinvented:
Indubitably.
[Samsung Galaxy Nexus] bsmitty83:
You would need to change the updater-script too , the ROM needs to mount and unmount the partitions f2fs , not ext4 .

Also.I don't see how there is a way to brick your phone with any of this . I haven't been able to brick mine and I'm sure I'm much more abusive than anyone on my nexus .

Hack The Tuna
[Samsung Galaxy Nexus] osm0sis:
Galaxy Nexus is really unbrickable thanks to the OMAPFlash utility. Possibly the only Nexus device that truly is. :)

(Something similar was developed third-party for the Nexus 7 2012, but the user needs to make backups first whereas OMAPFlash is from TI and just works out of the box. :good:)
[Samsung Galaxy Nexus] aosp:
https://github.com/figue/f2fs-scripts

https://github.com/1337/all-f2fs

https://github.com/ft11/android-f2fsall

https://github.com/figue/hellsdoctor-f2fs-zip
[Samsung Galaxy Nexus] infectedorganism:
Can any ROM be converted to work with f2fs, or is version dependant (4.4.2)? I'm interested in trying it on a 4.2.2 ROM.
[Samsung Galaxy Nexus] osm0sis:
Pretty. ;) What's the bullet point? Unified ramdisk?

Edit: Hmm no, ROM conversion I see... Interesting. I can't imagine these being difficult for someone to adapt for tuna.
[Samsung Galaxy Nexus] aosp:
Maybe ?
[Samsung Galaxy Nexus] osm0sis:
No idea yet about any of that stuff, but is the fstab the only thing different?

A nice trick would be to include two fstabs (or generate on the fly), but I'm not sure how to call a script that early in the boot to do so seamlessly.

MTK and AML do some weird sh*t like that on their boards to detect display types; I'll have some time to look into it later this week, after I finally get my goddamn lower leg cast off. :victory: :good:
[Samsung Galaxy Nexus] metalspring:
Btw, one more test kernel for anyone using the f2fs rom, check read/write speeds versus included dirtyv kernel and overall performance over time :P

DirtyV-R-5.3.14-f2fs-test.zip
[Samsung Galaxy Nexus] rajputrajat:
Definitely seems snappier..

Going to try your newer version
[Samsung Galaxy Nexus] cujo6801:
Which one?

Sent from the "DOG" pound
[Samsung Galaxy Nexus] ashclepdia:
yea unless the emmc completely fries, it's pretty much impossible to kill this thing
[Samsung Galaxy Nexus] aosp:
https://github.com/Quarx2k/android_...bae5633c65268a0d8e5c3b2f/ramdisk/f2fscheck.sh
[Samsung Galaxy Nexus] rajputrajat:
Flashed... Will report soon :p
[Samsung Galaxy Nexus] michierusama:
The included kernel is SmittyV I think.
[Samsung Galaxy Nexus] osm0sis:
Holy ****! More importantly:

https://github.com/Quarx2k/android_...5268a0d8e5c3b2f/ramdisk/init.mapphone_umts.rc

There's an exec command I've never seen documented (probably what MTK/AML does too). Apparently it's not enabled in the init binary on all devices but it's definitely worth a try for us. :D