yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] SuperGoober:
Thanks , I tried 2.65 and it worked . Still no 3g . I flashed the apn with no results so then I wiped , flashed the rom , apn and gapps but still no change . Build prop editor shows ro.carrier as unknown but I can make a call and send and recieve text on sprint . I'll keep trying some things with the 3g and let you know . It's sort of like it just doesn't connect with the apn that it's a sprint phone .

edit: A little more info on the sprint data issue . I've looked all through the build prop file and there aren't any entries at all pertaining to data or telephony , none . I've flashed several good apns and none work or change anything . The single entry related to carrier is ro.carrier unknown which is fairly common . Also no entries related to RIL , CDMA , Radio , Data , Telephony or Operator . None of those words are found anywhere in build prop . At this point I'm not sure there's an apn in the world to fix it . Could be related to the eri.xml not being built . Whatever builds or generates those keys isn't succeeding for some reason . Other than this problem phone is rooted fine and runs pretty dang good . Occasional FC like on carrier settings . Shows good promise overall . On the camera mine has no line or green tint whatsoever . Takes great pictures . Hope this will help some .
[Samsung Galaxy Nexus] Gargoyles:
Sorry for noon question, how to enable vibrate on answer? I can't find that setting. Thanks
[Samsung Galaxy Nexus] CYoung234:
This is in Settings - Sound, and is a check box "Vibrate when ringing".
[Samsung Galaxy Nexus] saprer:
yes stock recovery too. Doesnt the recovery come with the rom?

i think i got it:

there was something called SIMUILATING options that was enabled.

i disabled it and now it works

any thx for everything :D
[Samsung Galaxy Nexus] DR3W5K1:
?¿?:confused:
[Samsung Galaxy Nexus] saprer:
lol i dont know this device much.

im flashing so many devices for friends etc and its very complicated to know which was how.

my main phone was S3 and i did knew nearly everything about it but the switch made me a little bit confused :silly:
[Samsung Galaxy Nexus] Gargoyles:
Thank for answer man, but i want to know how enable vibrate, when i make a call and the other person answer, my phone should vibrate. Thanks
[Samsung Galaxy Nexus] MWisBest:
No beta builds for maguro yet, sorry guys. The issue is that, with development being so... active, I can't afford to sit around for an hour and wait for another build. I'm looking into possibly getting my other laptop set up to at the very least "pitch in" with building or something. The good news though is that whatever build you guys get will be more polished and refined...

I've never heard of such a thing, I don't even think it's possible to tell if the other person picks up at all in the first place.
[Samsung Galaxy Nexus] chongns:
Hi, this might be helping.

to enable on-call-state-changed vibration
[Samsung Galaxy Nexus] caluz78:
usually located in the phone app settings..
[Samsung Galaxy Nexus] Gargoyles:
True, but probably omni roms not have that setting.
[Samsung Galaxy Nexus] Ci@cKi:
Actually i think the dialer is gapps related, isn't it?
[Samsung Galaxy Nexus] CYoung234:
Okay, I understand. I googled this, and it looks like more people want to know how to turn it off than how to turn it on! So, I had never even heard of the feature, and I am pretty positive it is not in FML. But, sorry for the mis-information. When you said vibrate on answer, I assumed it was the same as vibrate on ring.
[Samsung Galaxy Nexus] Gargoyles:
No problem man! Anyway, i appreciate your help. Thanks!;)
[Samsung Galaxy Nexus] MWisBest:
Development update:

"OMAP Audio Control" is coming along OK. The equalizer stuff is way more complex than I had originally thought though! The equalizer probably won't be ready for a while, but I'm working on getting some other stuff in there as well anyway. I'm planning on adding a menu to DSP Manager for this, as well as eventually a standalone app that could be used on any ROM for those that e.x. stick with AOSP but use custom kernels (which I hope will pick up on OMAP Audio Control when it is further developed at least). I'm thinking that I'll have a new FML release within the next few days.

Other news:

I now have a weird obsession with the Nexus Q... it uses, guess what, an OMAP4460 SoC. How awesome would it be for me to have THREE OMAP4460 devices. :laugh: Hopefully someday I can pick one up for cheap on eBay or something.
[Samsung Galaxy Nexus] qtoo941:
Just a question: does current ROM got vibration on quick-tiles? If not, could you add this feature in next build? Please <3

Thumbs up for Linaro 4.9 !
[Samsung Galaxy Nexus] MWisBest:
No it is not in the ROM, I can't make any promises on it getting into the next build other than that I'll try!

Well that leads me into this...

I'm currently being hit by this bug regarding GCC 4.9: https://bugs.launchpad.net/gcc-linaro/+bug/1332989

While I'd certainly like to get that fixed, I think it might be out of my hands, so I'm not going to make just that one bug (so far...) stop me from updating to GCC 4.9.
[Samsung Galaxy Nexus] qtoo941:
You betta ask [MENTION=4825437]Christopher83[/MENTION] for any bug from Linaro 4.9.
[Samsung Galaxy Nexus] santi1993:
Great news fr GCC, anyone could post batt life / perf of the last version?

Sent with love [MENTION=887416]tap[/MENTION]a
[Samsung Galaxy Nexus] Jar3112:
Hi everybody. Just installed this rom on f2fs filesystem, seems fine but I can't connect my flash drive via OTG. Is this a common problem, can it be solved?

I'm using rom's own kernel and twrp f2fs recovery (the one from the dirty v thread)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] musical_chairs:
Ah, sorry, I should have picked up earlier that you are hunting in build.prop. On these unified builds, the general stuff is in build.prop and device-specific stuff is in /system/vendor/device/build.prop. Running 'adb shell getprop' should show that it is all there.
[Samsung Galaxy Nexus] SuperGoober:
Geeeeeeez , timing can be a ***** sometimes . I restored an L nandroid and data was no longer working . I've cleaned , flashed every which-a-way and finally called sprint because my wife's s3 had also lost 3g . Turns out sprint had done some upgrades on their network and neither phone had taken it because of the custom rom's , so i'm told . Anyway I had to re-provision via the dialer codes to get 3g and then reflashed MM and 3g worked like a champ right out of the box . The problem was on my end . Honestly I've never seen 3g pop up as fast as it does with MM . Best it's ever worked for me . That being said I apologize for the mistake . I'm not use to unified builds and when I found no reference to anything related to telephony I just assumed the worse .

Toroplus report

Flash and boot from a clean install goes off without a hitch Flashing the rom takes several minutes, longer than what we're use to so don't get impatient , it will complete . First boot is faster than normal . I've clean flashed several times and it actually boots up afterward in about 3 or 4 minutes . Painless procedure .

Google play services will be having lots of fc's . Just keep going until your at the home screen then go to settings/apps and give google play services permissions to everything and the fc's will stop .

SuperSU 2.65 works fine for root although it doesn't survive the next wipe . Just reflash .

Calls , texts and MMS do work for me .

Yes , MMS sends and receives perfectly right out of the box . I haven't touched or seen the apn I'm using . I'm on whatever apn is included , not 3rd party and no setting changes . I'm actually on Ting , and mvno and normally we do have to set MMSC but that's not the case here .

Phone is very stable . Carrier settings FC's so I can't check out that menu .

Wifi works .

Back Camera works with no lines anwhere and no green tint whatsoever . Front camera can't connect , video camera doesn't work .

Things like theme missing from settings but I imagine hasn't been implemented yet . Only option for reboot is power off , no advanced reboot available under developer options but probably not implmented yet either .

Maybe if your having MMS issues on toro or other variants you can look at why it works so good on toroplus hehe .

Same for our camera as compared to why green tint or lines are in other variants .

It has bugs as expected for an early work in progress but my expectations are definitely exceeded .

Definitely good enough for a tester's daily driver .

Thanks so much for your efforts . Again I'm sorry for the false alarm on the data issue .

3g data working
[Samsung Galaxy Nexus] musical_chairs:
It threw me for a bit as well, I thought at first that the device specific stuff was getting left out of build.prop - but a quick look at MW's scripts showed that they were doing exactly what they are supposed to do.

Well it's nice when things work when you expect them not to. I wouldn't mind seeing a 'logcat -b radio' taken while sending an mms.

My camera is working fine too, no green tint here on toro. Probably an issue with some older hardware on earlier maguros.

Anyway, thanks for the detailed report. Glad to hear data works on toroplus!
[Samsung Galaxy Nexus] bamtan2:
[MENTION=3390093]MWisBest[/MENTION] :good::good::good:
[Samsung Galaxy Nexus] MonstaDriva:
Links

I'm wanting to try Unified MM . Latest link on the main page is for a beta L . What is the latest build and link for MM ? Thanx
[Samsung Galaxy Nexus] jguerdat:
Check the Downloads link at the top of these pages.
[Samsung Galaxy Nexus] musical_chairs:
[MENTION=3390093]MWisBest[/MENTION] May I ask a technical question?

I'm trying to backport your libsecril-compat fix to Lollipop, specifically, the fix for toroplus's RIL missing the symbol it needs to take a screenshot. (So I don't need to fork frameworks/native.) I've got libsecril-compat building, and I have tried various versions of your modified libsec-ril_LTE.so's, but so far I can't get things to work. It throws this error:

D/RILD ( 135): **RIL Daemon Started**
D/RILD ( 135): **RILd param count=1**
E/RILD ( 135): dlopen failed: dlopen failed: cannot locate symbol "release_wake_lock" referenced by "libsec-ril_lte.so"...

I must be missing something - apparently now the only symbol the RIL can find is the screenshot one...
[Samsung Galaxy Nexus] ramosroger:
Any chance of a new LP or mm build soon?
[Samsung Galaxy Nexus] luckana:
i switched to this rom, seems much smoother than others, but overall i have 2 questions - 1. Why is the google search bar on the homescreen blank (is it a bug ? ) and 2. How can i add custom lockscreen widgets and expand them
[Samsung Galaxy Nexus] hp13:
go to settings > security > and enable lock screen widgets.
[Samsung Galaxy Nexus] daniil1410:
Explain the problem you have please. I either don't understand or I don't have the lag.
[Samsung Galaxy Nexus] hp13:
when you're on home screen, and pull the notification bar its laggy. its not fluid as its on 4.3 .

do you understand? i tried on few other roms but similar result.
[Samsung Galaxy Nexus] jesan9:
i think i know what is he talking about... i noted this bug since 4.4.2.

when you are not in launcher (in settings, Whatsapps, etc) and you have 5 icons in the status bar(like clock ,battery, signal, wifi/3g and alarm or vibrate or bluetooth) there is a little pull down lag... but with 4 o 6 icons there is no such lag... is weird xD
[Samsung Galaxy Nexus] daniil1410:
More frequent builds are better in my opinion, but only if they don't slow you down much overall. And of course if you don't want to waste time uploading more frequently it's totally up to you.
[Samsung Galaxy Nexus] qtoo941:
I would like to be absolutely honest with you - in my opinion rare but major updates are preferable. This nightly/weekly updates are totally useless - but this is just my opinion. I also think that it is a must to be used latest Linaro Toolchain 4.9 by [MENTION=4825437]Christopher83[/MENTION] and you can also make a chat with him for any question in connection with his Linaro 4.9 toolchain because he and his ADC-Team are really nice and helpful devs! Lag on home/recents, drawer and notification (swipe/pull down/remove) should be totally executed. Also i think that you gotta keep focusing on EXT4 and Dalvik instead of F2FS or ART. Because both ART and F2FS are just experimental things for KitKat. We better stick with good old dalvik which is really stable. About this DSP thing which you wrote - you can put this for last thing in your project. But rare and major builds are preferable - even once a month!
[Samsung Galaxy Nexus] CYoung234:
My opinion is that less frequent builds are likely going to be better for you, as you like to actually test your work first. More frequent builds will result in more testing, which I believe will slow you down somewhat. Some of the items you mention above are very exciting in terms of their possibilities to extend the lifespan of this phone.
[Samsung Galaxy Nexus] cabalio83:
I totally agree... I don't mind sticking for a while to a well performing ROM... Take your time.

It looks to me the way you are doing right now brings us a superb rom :good:
[Samsung Galaxy Nexus] daniil1410:
I have a feature request. It's nothing of great importance, but if you have time and desire, why not. Could you implement the new cm11 theme engine. I moved to this ROM from PA and this is the only feature I miss. Otherwise FML is way more speedy and lag free.
[Samsung Galaxy Nexus] x3m.zone:
100% +1
[Samsung Galaxy Nexus] Jar3112:
I would prefer a "complete" build, so go on this way dude!

BTW, will an update be dirty-flashable or require a wipe?
[Samsung Galaxy Nexus] nickdc986:
I like major updates better too.
[Samsung Galaxy Nexus] sivaseraphim:
Less frequent fits the bill with your current setup, especially when you're testing new stuff that might break the build. :D More frequent probably if you want the community to also get their hands dirty on testing and helping you fix stuff. A fresh pair of eyes could go a long way...sometimes :silly:

On another note, I've been testing Chromecast mirroring with the GNex using [MENTION=4732871]r3pwn[/MENTION]'s MirrorEnabler. Looks like for it to work on the GNex, Custom ROM maintainers must add audio.r_submix.default to the product_packages in the device.mk file.

Would it be possible to add this patch on your next build? Pretty please? :o

Thanks as always. :victory:
[Samsung Galaxy Nexus] SoftWord:
Is need trim command I'm f2fs version?

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] mieru:
Yeah, this will be fine!

---------- Post added at 11:09 AM ---------- Previous post was at 11:07 AM ----------

+1
[Samsung Galaxy Nexus] pvkiniyan95:
[MENTION=3390093]MWisBest[/MENTION] tbh rather than saying nightlies lets go for the test versions which u feel want to be tested.....rare stable updates are the best for people who love the rom and test versions for people who love bleeding edge.....i m up for tests as long as it is f2fs :)....that audio thing, i would love if it works great coz i m a audiophile too, recently all i do with my gnex is songs, songs, songs....may be phone calls email browsing too....for the sweet love of GOD please stick with DALVIK coz ART burns the hell out of our device also strictly no theme engine till OMNI does it themselves
[Samsung Galaxy Nexus] sergialess:
After a journey thru several roms, I've decided to come back to FML. Converted to F2FS, up and running.

It is the smoothest of all. Please keep up the good work! :good:.
[Samsung Galaxy Nexus] MWisBest:
Thank you for all the feedback!

I am not going to be adding the theme engine any time soon. The theme engine has too may problems. I've seen how it gobs up RAM, it is not going to play nice with devices that only have 1GB of less of RAM like the Galaxy Nexus. The next FML build is looking fantastic in terms of RAM usage though, better than I've seen before, if I can keep that up I will consider having a closer look at the theme engine, and maybe I can improve it...

Thank you for the feedback!

This next update is going to come with the recommendation for a data wipe. There were some problems I was running into that seemed to resolve themselves with a data wipe, however this was quite a few test builds ago and I may have fixed whatever was causing it since then. There shouldn't be any harm in testing just a dirty flash first at least.

Thanks for the feedback!

I would LOVE to have Chromecast mirroring working, and I will DEFINITELY look into that fix! I do have a Chromecast so I do have the ability to test it!

I discovered that F2FS isn't really "trimable". It turns out F2FS sorta builds that in, removing the need for fstrim.

Thank you for the feedback! :D
[Samsung Galaxy Nexus] mieru:
MWisBest you rock! Thank you man! :good::good::good:
[Samsung Galaxy Nexus] ilgimmy:
Hi I have a question.

When I enable "high accuracy" or "battery saving" location mode, I have tons of RILJ partial wakelock, and my phone never goes to deep sleep.

If I put location mode to "Device only", everything is fine.

I'm on 4.4.4-20140705-maguro-FML, with standard kernel 3.0.101-fml-gce4a987 and baseband I9250XXLJ1.

Everything installed after a full wipe of every partition, using F2FS on all partitions.

Do you have any suggestion?

PS thanks for the best ROM ever!
[Samsung Galaxy Nexus] MWisBest:
Release Candidate build: omni-4.4.4-20140726-maguro-FML.zip (159.83 MB)

I reverted the LTO stuff to libc/libdl (bionic) and ART, as it just wasn't stable enough. As a compromise I added some tested, proven optimizations to bionic, courtesy of the awesome people from Linaro.

Chromecast streaming/mirroring is working, as well as other WFDs (WiFi Displays) I think. Screen recording should work 100%, beit command line or the app/shortcut, and it should use the device audio rather than microphone audio now as well.

If the Chromecast stream/mirror thing works OK (don't expect 100% performance, this is nearly a 3 year old device, it can be decent however if the Chromecast or the Galaxy Nexus drop just a single packet it can cause a large stutter and, RARELY, disconnect the entire thing), I plan on getting it merged directly into OmniROM then.

The kernel is still kinda barebones, that'll be the last thing I mess with before getting an official update to FML up. I have so many ideas bouncing around in my head, eventually I just have to stop or I'd never get new builds out at all! :confused:

In the past week alone I've done at least 3 builds a day!

I've actually seen the location icon on the status bar randomly/inexplicably before, this is the best lead I've got on that issue then and I appreciate the report! I'll be looking into this as time permits, right now it's 2:30AM here and I need some sleep... I don't think I ever sleep. :(
[Samsung Galaxy Nexus] qtoo941:
Maybe I am still sleepy and didn't understand enough so i better ask you instead of just wonder and waste my time. What are expected bugs in this build? Also still no chance to add vibration feedback on quick tiles?
[Samsung Galaxy Nexus] Gingerbread1611:
[MENTION=3390093]MWisBest[/MENTION] awesome thanks!

btw: could you next time please also upload it to another hoster. (Or could someone mirror it?) Im downloading with 40 kb/s with a 16k connection. :/
[Samsung Galaxy Nexus] daniil1410:
Clean installed this. There is something wrong with the pictures in the Play Store. Everything was ok with the last build.
[Samsung Galaxy Nexus] MWisBest:
Yes I noticed the speed issues with Dev-Host. Usually with official builds I upload them to XDA as well, but with beta builds I don't want them just sitting there in the Downloads section here as people might download it without understanding it's a beta build etc. I will look for another place to use instead of Dev-Host.

This is a bug when compiling with GCC 4.9 unfortunately. The speed improvements with GCC 4.9 outweigh the image glitches in the Play Store for me. However that doesn't mean I'm just going to ignore this bug either, I am trying to fix it!

This is a list of the changes for this build, in addition to the few things I mentioned in the post with the build download link: http://xdaforums.com/showpost.php?p=54327632&postcount=327

The only expected bug is the Play Store images issue mentioned above.

I completely spaced out adding vibration feedback on quick tiles, I am moving it to the top of my list to get done before I do anything else. I promised to add this a long time ago, and I apologize for the delay. :(
[Samsung Galaxy Nexus] daniil1410:
If they only happen in the play store it's fine for me. I will try to use the new build.
[Samsung Galaxy Nexus] sergialess:
Great present for my birthday this RC. Waiting for final release.

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] Gingerbread1611:
Is this RC F2FS compatible? It won't boot for me.
[Samsung Galaxy Nexus] daniil1410:
It boots fine for me with f2fs on every possible partition.
[Samsung Galaxy Nexus] Litening0815:
Thx for this great ROM.

For me the fastest 4.4.4 ROM.

But:D

The last release stop booting at Google logo (clean or dirty install).

It looks like a kernel problem. With fancy r53 it boot up.

Sry for my English.

Cu Litening
[Samsung Galaxy Nexus] Gingerbread1611:
Yup, works fine with fancy kernel.

/edit: Does someone also have problems with PA Gapps? Most of the Gapps are force closing, im now going to try banks gapps.

/edit2: Random reboot and freezes with Fancy and SmittyV Kernel. :(
[Samsung Galaxy Nexus] Jar3112:
I experienced some freezes with previous version (not the latest, still have to try it) while listening to music via bluetooth. Stuttering and eventually SOD, more precisely. Stock kernel and smittyV so I suppose it's a rom issue..

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] pvkiniyan95:
http://www.phoronix.com/scan.php?page=news_item&px=MTc1MDQ

Linus Torvalds on gcc 4.9 : Utter crap....

[MENTION=3390093]MWisBest[/MENTION] i think right now its safe to stay with 4.8 or if u want an adventure go for it
[Samsung Galaxy Nexus] Litening0815:
I have no reboot and no freezes with r53 and pa micro gapps

Gruß Litening
[Samsung Galaxy Nexus] Gingerbread1611:
This is really weird, if i flash PA (Micro) or Banks (Standard) Gapps i get "Force-Close loops" Play Services and Google Search are always force closing.

And without Gapps the screens turns after some seconds black and i can't wake up my device, i have to take out the battery to get it working again.

Would logs maybe help?
[Samsung Galaxy Nexus] MWisBest:
EVERYBODY WHO IS HAVING ISSUES BOOTING THE RECENT TEST BUILD:

Please tell me what the /sys/board_properties/revision file says (on a working build or kernel)!

Well, in GCC's defense Linus is always finding something to complain about, and the bug he's talking about in particular has existed since GCC 4.5, and not only does it seem to be limited to x86 CPUs but also limited to using -Os and not -O2, neither of those apply here. ;)

Really though, eventually just about everything is going to be compiled with Clang instead of GCC since GCC is FUBAR.
[Samsung Galaxy Nexus] sergialess:
Not boot issues here, but two hard locks (need to pull battery).

Maguro 8th Sample (0x09)
[Samsung Galaxy Nexus] MWisBest:
Everybody who is trying the recent test build:

Try using the stock FML kernel with it (meaning don't flash a different kernel) first.

If it boots, tell me what the /sys/board_properties/revision file contains and that it boots OK.

If it doesn't boot, either flash a different kernel or go back to the 07/05 FML build and then tell me what the contents of the /sys/board_properties/revision, as well as that the test build doesn't boot with the FML kernel.

I really need all the help I can get!
[Samsung Galaxy Nexus] iviarck:
I flashed the test build on the day of release. It didn't boot, sticking on the Google logo.

I reverted to 07/05 FML and the revision file contains:

Maguro 8th Sample (0x09)

Good luck! (love the ROM)
[Samsung Galaxy Nexus] Litening0815:
+1
[Samsung Galaxy Nexus] daniil1410:
The release candidate boots and works amazing for me.

Maguro 8th Sample (0x09)
[Samsung Galaxy Nexus] Litening0815:
You are on F2FS or EXT4 ?

I'm on EXT4.