yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] MWisBest:
I'm not exactly sure what direction the OmniROM builds will take. F2FS support might make its way into there, but I can tell you though that the majority of the optimization stuff will only be in FML, that's because the optimization stuff doesn't come without risks: it really requires careful monitoring and testing, and every device will react to it differently, so it's hard to have something like that in a project that supports so many different devices like OmniROM does!

Yes, and I'm glad everything is workin' out for ya! :)

Not sure why you'd want to go back but there shouldn't be any problems switching back and forth between the two with the newest FML build. Simply format to EXT4 in the FML TWRP recovery build like described.

I will have a look at this tomorrow and see if I can figure out what's going on.

Actually I may have overlooked that, thanks for the reminder!

Correct, theme manager stuff isn't included with FML and probably will never be.

"Settings --> Bars --> Long press back to kill app" : is that checked off, and have you tried it with non-system apps?

???
[Samsung Galaxy Nexus] MWisBest:
You're not the first person to describe this problem... I'll see if I can find the cause of it.
[Samsung Galaxy Nexus] CYoung234:
Thanks for looking into this. Made for a long day today formatting, adb push / pull, etc....
[Samsung Galaxy Nexus] SoftWord:
Hi, this Rom is great but my phone is very hot in stand by too! I'v changed between dirtyv and Franco kernel but no way....any idea?

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] NARDO86:
The same for me.. When i'm connected via mobile (expecially if there is poor signal) it seems to heat even more
[Samsung Galaxy Nexus] aniketkuber:
Same here .. Default kernel .. Phone gets hot doing usual stuff..
[Samsung Galaxy Nexus] SoftWord:
I'v changed two kernels but same issues

It's a Rom bug for sure :(

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] saprer:
mines get also hot by usual stuff
[Samsung Galaxy Nexus] pvkiniyan95:
honestly guys, this has been the coolest rom & kernel combo i ever used in last 3 months, no overheating issues in my side but i am not able flash DirtyV which strucks at google logo
[Samsung Galaxy Nexus] CYoung234:
Well, I ended up redoing my phone completely, because after I converted the file systems back to ext4, I began losing whole sdcard directories. Strange problem. I had to take the phone back to stock via fast boot. I have everything setup again running ext4, and it seems to be running great. If you can tell me what the problem was before, and how to prevent it, I may take another stab at f2fs.
[Samsung Galaxy Nexus] AbhishekS:
Luckily I have no such issues on F2FS. Touch wood!
[Samsung Galaxy Nexus] NARDO86:
I don't know what to say, also for me it was cool until about 3 weeks ago.

I usually use stock kernel ad settings, now (after experiencing heating) i tried to reformat everything, use dirty kernel and also covert to e2fs.

Just now i played a game, tiny dice dungeo, for abount 10 minutes and CPU temperature raised to 84°C (183°F).

My ambient temperature is about 27°C (80°F) current kernel is DirtyV-UR 6.28.14, governor interactivex and max freq 1200, voltage untouched.

I experience heating also when mobile signal is slow a during file transfert over mobile connection, sometimes i found it (in stand-by) a little hotter than normal but never so hot. Luckily if i stop activities it return fast to normal temperature so for not it's not a major problem for me
[Samsung Galaxy Nexus] saprer:
Got some problems over here:

My nexus makes random reboots. i didnt faced it till today and today ive had this 3 times already.

using stock rom + kernel and f2fs.

is it a f2fs issue? i dont know much about this phone. i bought it new ( its used) but hadnt any problems while running DirtyV+ AOKP on EXT4.

there i had some problems that my device would take very long to wake up sometimes.
[Samsung Galaxy Nexus] CYoung234:
You should submit a logcat for this problem. You can google for how to do this, but an easy way is via adb. I believe the command adb logcat > file name.txt is the basic idea.
[Samsung Galaxy Nexus] werty100:
Also videos play very slow in mx maybe not all related stuff camera and video deconding enconding
[Samsung Galaxy Nexus] Punkiderma:
sorry, a little OT!

[MENTION=3390093]MWisBest[/MENTION] this is obviously not a feature request, just curiosity :)

do you think our Galaxy Nexus could make use of the new camera2 APIs, in order to support apps alike these ones:

http://www.xda-developers.com/top-4-camera-apps-for-lollipops-new-api/

? Is something that needs to be implemented just at software level, or it also needs a camera hardware supporting them?

Thanks!
[Samsung Galaxy Nexus] rajputrajat:
MWisbest has already been frustated to get camera2 api working on our phone and stated it while back that it is not going to work. As those libs are closed source.
[Samsung Galaxy Nexus] lollipop:
gravity box hits lollipop , i test it(on slimlp) and it work very well with a lot of features.

so [MENTION=3390093]MWisBest[/MENTION],i hope that xposed will work on the next build .fml+gravitybox=best thing so far !!!! :victory:
[Samsung Galaxy Nexus] werty100:
I am making some modifications to device tree adding ksm new LKM values and some Graphics related stuff for improving all until this weekend I cant compile it and test with new kernel stuff and new source and news improvement also looking for a fix for charging off mode but is so much for my some ideas but no clear:eek::eek::eek:

I will try to work thsi rom becouse at the moemnt this one is the best for my lp working also camara is not working well in further updates i will try new stuff
[Samsung Galaxy Nexus] werty100:
I have make a pull request to dev and if this sunday nothing changes i will try to compile my own
[Samsung Galaxy Nexus] werty100:
See my advances and improvements in my github:

https://github.com/werty100?tab=repositories
[Samsung Galaxy Nexus] werty100:
Fetching projects: 99% (411/415) Fetching project android_external_dnsmasq

I am here i dont know why is at 99% a lot of time :confused::confused::(:(:(

Remove sdk and downlaod manually fixed it
[Samsung Galaxy Nexus] Pseudonico:
email problem

this ROM in great!

I've Lollipop and the only problem that I found is using stock email app.

The app hungs in authentication process

Bye
[Samsung Galaxy Nexus] Pseudonico:
I've found another bug with GSM signal, sometimes go down and you have to reboot phone (where is reboot option?)

Bye
[Samsung Galaxy Nexus] sodas43:
reboot option will come with xposed which is in alpha stage(though working greatly according to the users ;) ). We can hope that in the next build MwisBest will integrate it in this rom !! :confused: :o
[Samsung Galaxy Nexus] Loureiro:
Contratz for the "Recognized Developer" title.

I've built from your android_manifest. I've changed the boot alert dialog for dark material design. Do you prefer the Holo theme?
[Samsung Galaxy Nexus] osm0sis:
Nice! I've been hoping someone would redo it in material dark. Open a pull request to [MENTION=3390093]MWisBest[/MENTION] to make it easier for him. :good: :)
[Samsung Galaxy Nexus] Loureiro:
I'm still getting used to git and github and stuff. I did a pull request right now :)

commit: https://github.com/LoureiroPT/andro...mmit/0610c1909f1048670476657438c86e2ddb4a3fe1
[Samsung Galaxy Nexus] werty100:
Also i make some commits forma better perfomance
[Samsung Galaxy Nexus] RoadToNever:
If it's not too much work I would love to see screen color controls in the included kernel next build.
[Samsung Galaxy Nexus] werty100:
Why repo sync makes this and stop here:

Fetching projects: 98% (483/492) Fetching project CyanogenMod/android_packages_apps_ThemeChooser

Fetching project CyanogenMod/android_external_ant-wireless_ant_native

Fetching project CyanogenMod/android_packages_providers_ApplicationsProvider

Fetching project CyanogenMod/android_development
[Samsung Galaxy Nexus] Carlos_Manuel:
Use this command:

repo --trace sync -c -d -j8

There's probably a typo somewhere in default.xml or then some of the repositories aren't available
[Samsung Galaxy Nexus] smartAgent47:
repo sync problem

Hello everybody,

Please help me with a problem ....

I wanted to sync cyanogenmod and started syncing .... i did with repo sync -j2 because of my slow internet .... it was working and suddenly stopped .... i did Ctrl+Z and stopped and again did repo sync -j2. Now it gave me an error that it could not fetch some repositories and it stopped saying exiting due to error fetch... I again did repo sync again the same error .... actually 65% was done but on 32% it was showing this error fetch ....

I am in a problem please help me ...
[Samsung Galaxy Nexus] werty100:
: parsing /home/werty100/cm12/.repo/projects/development.git/config

: export GIT_DIR=/home/werty100/cm12/.repo/projects/development.git

: git fetch github --tags +refs/heads/cm-12.0:refs/remotes/github/cm-12.0 2>|

: load refs /home/werty100/cm12/.repo/projects/packages/apps/BasicSmsReceiver.git

: load refs /home/werty100/cm12/.repo/projects/external/speex.git

: load refs /home/werty100/cm12/.repo/projects/packages/apps/ThemeChooser.git

: load refs /home/werty100/cm12/.repo/projects/external/ant-wireless/ant_native.git

: load refs /home/werty100/cm12/.repo/projects/packages/providers/ApplicationsProvider.git

: load refs /home/werty100/cm12/.repo/projects/build.git

: load refs /home/werty100/cm12/.repo/projects/development.git

I am going to delete development package and try to dowload another time

Development is the one causing problems i have remove it from repo and disk

and now build pufff
[Samsung Galaxy Nexus] frimpasi:
Android 5.1 is in the air!!!! :highfive::victory:

Maybe in a few weeks FML 5.1?? Only [MENTION=3390093]MWisBest[/MENTION] knows that :D
[Samsung Galaxy Nexus] MWisBest:
I'm thinking a few days. Maybe even a few hours.
[Samsung Galaxy Nexus] lorenx:
hi all and sorry for the question but i was not able to find the answer on my own...

is this the only rom using the new v1.9 gpu drivers, regardless of the 4.4.x/5.x version?

one last thing. besides the well-known stock camera issue, i'm still having problems with youtube, not loading video often: http://pastebin.com/60FBJrSn

i'm using pa pico gapps (20150215).

thanks. ;)
[Samsung Galaxy Nexus] sgspluss:
Actually all lollipop roms use new ddk driver, just dreams use the old one.

Gesendet von meinem Galaxy Nexus
[Samsung Galaxy Nexus] lorenx:
Thanks, but this (the beta one) is the only 4.4.x rom, right?
[Samsung Galaxy Nexus] sgspluss:
Both are same (as far as i know) but in lollipop they are more up to date.
[Samsung Galaxy Nexus] lorenx:
Sorry, which ones do you mean with "both"?
[Samsung Galaxy Nexus] sgspluss:
ddk 1.9 in kitkat and lollipop, they (as far as i know) are the same, but on lollipop more up to date.
[Samsung Galaxy Nexus] alboz83:
Woooow thanks for you great work :) I hope that in the next version Camera and Videocamera will be fixed at 100%
[Samsung Galaxy Nexus] Fenix46:
Great job ... you are a great, yet the sources are not public in an official and you have already prepared a build for GNEX ... you really are a great... I hope to release soon this version so you can try it :good:
[Samsung Galaxy Nexus] RW-1:
Well, cmon, we're not having to wait on sources, being that the GNex is the bastard child of android hehehe ... it's no wonder we have awesome dev's ready to release a port ... :)
[Samsung Galaxy Nexus] Like_Gg:
I'll come back to the gnexus after 1 year, i will flash this rom but i dont know which kernel use. Any suggestions? Thanks
[Samsung Galaxy Nexus] lorenx:
ok, wait. this is what i understood, long story. feel free to correct me, please. :)

official texas instruments drivers have been version 1.8 for long. all galaxy nexus roms were based on that version.

then texas instruments released version 1.9, to lengthen their soc life.

now, it would be plain if any kitkat and lollipop roms (since google stopped with jellybean its support due to this) were based on 1.9 but, in my humble experience, it's not like this. maybe most lollipop roms are, but i have some doubts about kitkat roms. it seems that, kitkat talking, only fml merged the new 1.9 version... :rolleyes:

Google who? :D
[Samsung Galaxy Nexus] Ziyan:
TI released 1.8 for ICS. Then, for Jelly Bean, they released 1.9, but lazy Google didn't care about updating it for us :mad:

See: http://www.omappedia.com/wiki/Release_Notes#BlazeTablet_Release_Notes
[Samsung Galaxy Nexus] lorenx:
thanks ziyan, i guess this is the reason why most kitkat roms still use version 1.8. maybe kitkat can (kinda?) run with the old drivers anyway. :)

can you confirm that with lollipop all roms need integrete version 1.9 cause it's unusable with 1.8?

however, i'm still trying to understand if fml (beta) is the only 4.4.4 rom using 1.9 or not... :p
[Samsung Galaxy Nexus] Ziyan:
I guess Lollipop would run with the old drivers, but with worse performance and heating (as it uses heavier effects, and 1.9 brought us way better thermal/power management).

FML isn't the only one running 1.9 on KK, I released an Omni build with the new drivers back in July, but very few people noticed it :cowboy:
[Samsung Galaxy Nexus] lorenx:
oh, right... but if i'm not wrong beta fml 4.4.4 is based on your omni build, at least the filename suggests this :)
[Samsung Galaxy Nexus] zzpianoman:
I built CM12 for toro with 1.8 and it is very stable.
[Samsung Galaxy Nexus] lorenx:
sorry for the noob question but we don't all devs switch to 1.9? :)
[Samsung Galaxy Nexus] zzpianoman:
Well, I originally built with 1.8 because at that time the camera wasn't quite working on 1.9. Camera is now fixed, but I'm choosing to stick with 1.8 for the time being.
[Samsung Galaxy Nexus] MWisBest:
I'll attempt to get 5.1 builds up tonight. I'm curious about whether or not the RIL works on maguro, toro is giving me some trouble.

What Doesn't Work:

- RIL, at least on toro(plus).

What Should Work:

- Everything Else

Even the camera is working well! Flashed directly over 5.0 without any problem either.
[Samsung Galaxy Nexus] zzpianoman:
Did 5.1 fix the video recording issue?
[Samsung Galaxy Nexus] revanmj:
I guess that RIL issues might be caused by changes required by multiSIM support.

EDIT: Seems that this guy got a working RIL on 5.1 (DDK version doesn't make any difference in case of RIL, right?) - http://xdaforums.com/showthread.php?t=2510649
[Samsung Galaxy Nexus] n1kolaa:
Dont link his rom here.

PS: He dont know what he doing :)
[Samsung Galaxy Nexus] sgspluss:
Interessting, are you really serious?!

He does his work as all other devs here...

Respect their work, sure you can have your personally mind but you should not say something like this!
[Samsung Galaxy Nexus] n1kolaa:
Carlos is like Chuk Norris. He is wolf with work alone.He leave our hangout in june. :)
[Samsung Galaxy Nexus] Carlos_Manuel:
The RIL changes on my ROM sources (LP5.0 and 5.1) are same as in freshgiammi's aources, as I cherry-picked those from his repositories. At first I was using RIL changes from AOSPA and CM but some of the commits broke proximity so I had to clean up everything and to use freshgiammi's commits, because Ziyan said that freshgiammi has working RIL on his AOSP ROM.

Also I've included a few extra RIL commits to my sources, but those won't fix anything for tuna. RIL works fine on maguro, but it's probably broken on toro...

Hi Nikolaa! I do know very well what am I doing. (Even though I'm not good in Java and C but I'm learning it all the time more and more).

I don't have anything against you, but what you said, made me actually sad. but everyone can have their own opinion so whatever.. :)

Yes, I did leave the omap4xxx hangouts chat. That was a long time ago and I was pretty much an a-hole there back in those days... I do regret that I left that group chat. Btw. I like Chuck Norris.

I like doing stuff by myself and in my way. That's the one methid to learn more by yourself... I made my ROM a long time ago and I will keep it alive as long as I use my Nexus. (I won't change my phone any time soon, because this is simply the best phone ever)

I appreciate everything that Ziyann, mwisbest and freshgiammi has done with keeping Nexus alive and getting new graphics drivers for it.

Ziyann has helped me a lot and I'm really thankful. Without his help my ROM wouldn't be running Lollipop so well.

This is a little bit OT, sorry OP.
[Samsung Galaxy Nexus] Djalaal:
[MENTION=3390093]MWisBest[/MENTION] It would be awesome if you could make Xposed work on FML. However, I think that'd require a vast amount of effort/time. Since many of us just use it to get back the features that KK builds used to have (at least, I THINK that's the case), I think the time/effort is better spent bringing those features back to your FML "natively". Just my two cents.

Unless making xposed work is really not that hard...
[Samsung Galaxy Nexus] NightShadow02:
Hi there, just flashed your ROM today and I'm experiencing trouble viewing giffy files on Reddit News and also previously downloaded giffy .mp4 files on my phone. Would you happen to know what is causing this? Thanks for your time!
[Samsung Galaxy Nexus] alboz83:
Wait wait wait for 5.1, I've read in MWisBest Google Plus page that in about 10 hours the rom for maguro is ready, and he wrote this about 10 hours ago.
[Samsung Galaxy Nexus] MWisBest:
Aaand here we are.

ROM: FML-AOSP-5.1-20150311-maguro.zip (196.39 MB)

GApps: FML-PA-GApps-Micro-5.1-20150310-UNOFFICIAL.zip (149.31 MB)

What Doesn't Work (Yet):

- Flashlight Tile

What Does Work:

- Everything Else(?)

It's pretty solid and stable so far for me, but I'd prefer if it gets tested out by some other people before I 'promote it' to the main post.

BTW, Superuser isn't baked in just yet, so you'll have to flash SuperSU or something for it.

Also, I'm going to be dropping support for 4.4 and 5.0 now. Due to 5.0's suckiness, I had planned on going back to 4.4 to do a build with all the latest stuff that's been done for the Galaxy Nexus, but 5.1 is good enough to not make doing that worth it anymore.
[Samsung Galaxy Nexus] davinaizer:
Yeah....!!!!!

Thank you very much..

Let´s flash it!
[Samsung Galaxy Nexus] Tolazace:
For asking people:

Video playback - works

Green Line still here

Offmode charging still broken

Rom is very smooth. Great job. Maybe soon can you fix this bugs ;)
[Samsung Galaxy Nexus] alboz83:
Noooo green line still here :(((
[Samsung Galaxy Nexus] eternal70:
For 5.1 users, can you flash bsmitty83 kernel ?
[Samsung Galaxy Nexus] Tolazace:
Must flash SuperSu becouse root don't build-in.

After flash Full Auto r10 phone stop on bootanimation but vibration suggest phone starts and work (navbar vibrations and long press Power button). I try to remove bootanimation in TWRP, maybe help

[MENTION=309187]edit[/MENTION]

Yeah after delete bootanimation.zip phone boot and work great with R10
[Samsung Galaxy Nexus] MWisBest:
If you're referring to the green line at the bottom of video recordings, that can be reduced quite a bit by using the "Open Camera" camera app. It's a slim purple line instead at least.

Flash R11, not R10, and it should work.
[Samsung Galaxy Nexus] Tolazace:
I know that but stock app have green lines. I see R11 only for CM based Roms. For FML newest is R10 in download tab.
[Samsung Galaxy Nexus] frimpasi:
Clean or dirty flash??
[Samsung Galaxy Nexus] alboz83:
Ok thanks, anyway I hope that green line disappear soon. Now I test this new 5.1 rom, I want to left Kitkat forever
[Samsung Galaxy Nexus] eternal70:
Thanks ! With R11 now everything is faster. Btw, just asking. Will you add some little customizations like omnirom in KK for FML in the future ?
[Samsung Galaxy Nexus] alboz83:
Wooow really fast compared to 5.0.2.

I would to replace Mms with Messenger, i know hot to put in system/priv-app, but it's possible to odex it?
[Samsung Galaxy Nexus] osm0sis:
It's all unified with R11 and newest FML.
[Samsung Galaxy Nexus] thomstrack:
I can use F2FS on /cache and /data with latest build? :)
[Samsung Galaxy Nexus] davinaizer:
yes
[Samsung Galaxy Nexus] nachiket_xda:
Can I use pa pico gapps? What is difference in mw's unofficial gapps?
[Samsung Galaxy Nexus] ashish__s:
Hi, I've been using SlimLP until I saw MWI's update. I kinda of liked SlimLP for its density (? i don't know the term! sorry!) Is it possible for me to adjust that with this rom? If so, any directions/guide would be greatly appreciated! Thank you! :)

edit: i think i found the answer. it's called editing the build prop to change the resolution/dpi? any recommended apps to edit the build prop?
[Samsung Galaxy Nexus] smartAgent47:
build.prop editor ... download from play store
[Samsung Galaxy Nexus] ashish__s:
i tried it. i didn't do anything which leads me to believe i lost root :/ i'm not entirely sure how to re-acquire root (it's been a looooooong time since i rooted my phone)
[Samsung Galaxy Nexus] smartAgent47:
flash supersu latest zip through recovery ...
[Samsung Galaxy Nexus] rambhanushali20:
Trusted Faces dont work .
[Samsung Galaxy Nexus] revanmj:
They never did on 5.x (on Maguro) as far as I remember.
[Samsung Galaxy Nexus] rambhanushali20:
It works in Dreams 5.1
[Samsung Galaxy Nexus] eternal70:
[MENTION=3390093]MWisBest[/MENTION] can you add busybox binaries in the next build ? I already tried installing and use flashable zip but it still says that busybox can't be installed. So I can't use trickster mod
[Samsung Galaxy Nexus] revanmj:
For me busybox recommended by Trickster worked like a charm.

Damn this ROM is flying by comparison 5.0.
[Samsung Galaxy Nexus] MWisBest:
Yep, already planned on having the next 5.1 build include both busybox and Superuser.
[Samsung Galaxy Nexus] r.albu:
Trying this right now (big thank you to MWisBest!).

I'd like to know if it's ok to edit buil.prop. to change density. I was on SlimKAT (unofficial) and now I find normal icons (and everything) too big... Is this safe? Or interferes with other things I should care of before changing anything? If it's safe and the only thing I've to do is to change that value, what values are safe?

Many thanks.
[Samsung Galaxy Nexus] Carlos_Manuel:
Firstival:

I did use fRom on lollipop but I've replaced it with Ziyann's dumpdcc as it is better, opensourced and does thesame as from.

I have replaced closesourced pvrstctvl a long time ago with the opensourced one

I've enabled Selinux and PIE.

But the reason why I use old ddk is because it works well on lp and with newer ddk offline charger is broken. Btw alo before wrting about how I do stuff, be sure you have up to date info..

Btw I'm 17 and I'm still learning, I'm not good in programing (yet) im learning it by myaelf and in the vocational shool as this is waht I want to do in future...

I cannot write more because battery tok low on my phone.
[Samsung Galaxy Nexus] MWisBest:
Sorry I was a day behind on you re-enabling PIE enforcement, that's good to hear! :good: I don't check GitHubs daily (I don't think anybody really does?) so I hadn't seen that yet.

You are using dumpdcc nowadays too I see, that's nice, however you're not actually building it from source code. If you were building it from source code (hence the point of having source code man!), I would've seen it, so still something to improve upon there.

However, I'm not really out of date on "how you do stuff". The attitude towards change is still there. I'll give you a chance to prove me wrong though: I'll get a fix done this week for offline charging. If that's truly your only problem with DDK 1.9, you'll switch over.

That's great! I do think you could excel with programming someday, and we all started somewhere! If I may, one tip I have for you is to be more willing to collaborate and work with a team, and be more open to other points of view. I used to be very closed-minded and unwilling to work with anybody else, but it's something I've improved upon greatly and it has helped me learn more in the process.
[Samsung Galaxy Nexus] sudeepbaral:
Setup wizard crashes

Guys i clean flashed the Rom and Gapps but everytime the Setup wizard crashes and i cannot get past the setup wizard. Any suggestions??