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
anyone know how to fix the notification pull down lag? its present in all roms. just wondering if someone found a way around.
Explain the problem you have please. I either don't understand or I don't have the lag.
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.
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
I have a question for you guys:
Would you rather see more frequent FML builds but with less changes in each build, or continue with what I've been doing lately and release builds less frequently with a huge amount of changes in each build?
Part of what has caused me to slow down with releasing builds is that I'm just getting extremely ambitious with things. For example, here's a preview of the changes for the next build, in order of when they were um, started.
- Complete overhaul of the kernel, rebasing it on top of Ziyan's heavily updated kernel. He managed to pull in upwards of 1,000 commits from the omapzoom kernel (sort of the 'official' OMAP (the CPU the Galaxy Nexus uses) kernel, which while the Galaxy Nexus was based on this kernel, it got neglected and wasn't kept up to date). I've also used this as an opportunity to clean up many things with the previous kernel and do them 'properly' this time around.
- Laid down some initial code for "OMAP Audio Control". This isn't going to be much for a while, as I'm not really familiar with Digital Signal Processing (DSP), at least on such a low level! But like just about everything I do with FML, it's an opportunity for me to learn new things.
- Switched the compiler for the ROM to Linaro's GCC 4.9, and the compiler for the kernel to 'standard' GCC 4.9. This should result in an all-around improvement of speed, however it also could introduce some bugs. The kernel seems fine, but the ROM-side of things was pretty disastrous:
--- First, it wouldn't boot at all. After a while I was able to figure out what the problem was and implement a workaround for it.
--- Second, it resulted in a huge problem with my /data partition, after tracking down and fixing what was causing this I had to reformat /data.
--- Third, fourth, fifth, sixth, and seventh, there were just random inexplicable crashes, that I somehow managed to fix. Seriously!
--- Eighth: I haven't gotten to eighth yet actually but I'm sure I will eventually!
- Small change to the build.prop that will improve (reduce) memory usage.
- Updated libpng from 1.2.46 (released in 2011, however 1.2 as a whole was originally released in 2001) to 1.6.10 (released just a few months ago, with 1.6 as a whole being released in 2013), and also enabled NEON for it. This may or may not affect speed or stability... I'm not going to say that it will as there's not really a way for me to measure it and if I try to 'guess' based on how it 'feels' my mind will probably play tricks on me and just make it a placebo effect, but I certainly like higher version numbers!
- Switched from libjpeg to libjpeg-turbo. Like the libpng change, libjpeg-turbo has NEON support, and as a result is claimed to be 2 to 4 times faster than the regular libjpeg.
- Enabled LTO (Link-Time Optimization) for all the things it previously had to be manually disabled for: parts of bionic and parts of ART. This is partly due to fixes and improvements to LTO by GCC 4.9.
I hope the links were helpful! I know this stuff can be hard to understand sometimes.
Yeah I still haven't quite worked out all the USB OTG issues, hopefully they'll be fixed for the next build.
I see somebody else answered #2, as for the search bar being blank I'm not really sure what's up with that. I'll ask the OmniROM guys, I'm guessing it could maybe be a legal issue with using Google's images.
Would you rather see more frequent FML builds but with less changes in each build, or continue with what I've been doing lately and release builds less frequently with a huge amount of changes in each build?
Part of what has caused me to slow down with releasing builds is that I'm just getting extremely ambitious with things. For example, here's a preview of the changes for the next build, in order of when they were um, started.
- Complete overhaul of the kernel, rebasing it on top of Ziyan's heavily updated kernel. He managed to pull in upwards of 1,000 commits from the omapzoom kernel (sort of the 'official' OMAP (the CPU the Galaxy Nexus uses) kernel, which while the Galaxy Nexus was based on this kernel, it got neglected and wasn't kept up to date). I've also used this as an opportunity to clean up many things with the previous kernel and do them 'properly' this time around.
- Laid down some initial code for "OMAP Audio Control". This isn't going to be much for a while, as I'm not really familiar with Digital Signal Processing (DSP), at least on such a low level! But like just about everything I do with FML, it's an opportunity for me to learn new things.
- Switched the compiler for the ROM to Linaro's GCC 4.9, and the compiler for the kernel to 'standard' GCC 4.9. This should result in an all-around improvement of speed, however it also could introduce some bugs. The kernel seems fine, but the ROM-side of things was pretty disastrous:
--- First, it wouldn't boot at all. After a while I was able to figure out what the problem was and implement a workaround for it.
--- Second, it resulted in a huge problem with my /data partition, after tracking down and fixing what was causing this I had to reformat /data.
--- Third, fourth, fifth, sixth, and seventh, there were just random inexplicable crashes, that I somehow managed to fix. Seriously!
--- Eighth: I haven't gotten to eighth yet actually but I'm sure I will eventually!
- Small change to the build.prop that will improve (reduce) memory usage.
- Updated libpng from 1.2.46 (released in 2011, however 1.2 as a whole was originally released in 2001) to 1.6.10 (released just a few months ago, with 1.6 as a whole being released in 2013), and also enabled NEON for it. This may or may not affect speed or stability... I'm not going to say that it will as there's not really a way for me to measure it and if I try to 'guess' based on how it 'feels' my mind will probably play tricks on me and just make it a placebo effect, but I certainly like higher version numbers!
- Switched from libjpeg to libjpeg-turbo. Like the libpng change, libjpeg-turbo has NEON support, and as a result is claimed to be 2 to 4 times faster than the regular libjpeg.
- Enabled LTO (Link-Time Optimization) for all the things it previously had to be manually disabled for: parts of bionic and parts of ART. This is partly due to fixes and improvements to LTO by GCC 4.9.
I hope the links were helpful! I know this stuff can be hard to understand sometimes.
Yeah I still haven't quite worked out all the USB OTG issues, hopefully they'll be fixed for the next build.
I see somebody else answered #2, as for the search bar being blank I'm not really sure what's up with that. I'll ask the OmniROM guys, I'm guessing it could maybe be a legal issue with using Google's images.
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.
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 @Christopher83 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!
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.
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.
I would prefer a "complete" build, so go on this way dude!
BTW, will an update be dirty-flashable or require a wipe?
Less frequent fits the bill with your current setup, especially when you're testing new stuff that might break the build. 
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 @r3pwn'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?
Thanks as always. :victory:
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 @r3pwn'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?
Thanks as always. :victory:
On another note, I've been testing Chromecast mirroring with the GNex using @r3pwn'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?
Yeah, this will be fine!
---------- Post added at 11:09 AM ---------- Previous post was at 11:07 AM ----------
+1
@MWisBest 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
....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 themselvesSimilar threads
Top Liked Posts
-
There are no posts matching your filters.
-
227[#Intro]
Oh, and now there's these Lollipops I'm handing out. They are free as always, and they are very very delicious.
[#Why]
[#Info]
I need people testing and finding bugs if anything is going to be fixed. I might not have the Bluetooth devices you have, I might not use the camera as much as you, I might not use mobile data as much as you; you get the idea.
NOTE: FML is built and tested on the Verizon Galaxy Nexus variant, also known as toro. The GSM Galaxy Nexus variant (the one pertaining to the forum section you're currently in), also known as maguro, is extremely similar in hardware to the Verizon Galaxy Nexus, however I'm not able to test these builds personally. There aren't any code changes between builds for toro and maguro so that I know there shouldn't be any huge issues, but things specific to maguro I'll need feedback on to make sure they're working OK.
[#HowTo]
Latest BuildKitKat/ROM Stable: omni-4.4.4-20140705-maguro-FML.zip (159.07 MB)
KitKat/TWRP Stable: fml-twrp-2.7.1.0-20140705-maguro.img (8.58 MB)
KitKat/ROM Beta: omni-4.4.4-20141015-maguro-FML.zip (160.13 MB)
KitKat/ROM Beta Hotfix: boot.img (4.83MB)
Hotfix Info: The latest beta had a bug on maguro causing the radio to be a jerk and not work. Flashing this boot.img will resolve that issue. If you'd rather not flash it with fastboot like is normally done for .img files, you can use the Flashify app for it, or you can open up the ROM zip and replace the boot.img in there with the hotfix.
Lollipop/ROM Beta: FML-AOSP-5.0-20150108-maguro.zip (194.45 MB)
LOLLIPOP INFO:
USE THESE GAPPS: FML-GApps-5.0.x-20150101-tuna.zip (167.81 MB)
They are based on PA's GApps, huge thank you to them!
Known Issues:
- Camera can be a little touchy, but it generally works.
- Long SMS messages fail to send, fix is on-the-way though.
Lollipop Changelogs can be found in the post below!
(KitKat) BETA INFO:
Beta builds are using updated GPU drivers (and an updated kernel to go with them) courtesy of @Ziyan, as well as being up to date with the latest stuff from OmniROM. NOTE: YOU CANNOT FLASH A DIFFERENT KERNEL WITH THESE BUILDS.
Currently broken with the new GPU drivers:
-Hardware Video DecodingFIXED 2014/10/06
-Hardware Video Encoding(?)FIXED 2014/10/08
-Camera(PARTIALLY) FIXED 2014/10/08
- The stock camera app (as well as Google Camera) has this weird quirk of crashing when pressing the shutter button to take a picture, however many different camera apps on the Play Store (in particular Camera ZOOM FX) work flawlessly. Video recording is generally OK, however I've been getting some reports of the audio and video being a little out of sync, so your mileage may vary...
See the Changelog post below for..... well..... changelogs.
[#GApps]
Known Issues- The screenrecord command does not work directly, however it does work via the Power menu.
- There can be a slight (noticeable, but not huge) delay when pressing the Recents or Home button.
[#Thanks]
[#Donations]
XDA:DevDB Information
FML: Fork My Life, ROM for the Samsung Galaxy Nexus
Contributors
MWisBest
Source Code: https://github.com/MWisBest/
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Beta
Stable Release Date: 2014-07-05
Beta Release Date: 2015-01-08
Created 2014-05-27
Last Updated 2015-01-0896I'm feeling terrible. I don't have the energy to update the thread, but the new build is uploaded here:
FML-AOSP-5.0-20141207-maguro.zip (199.24MB)
I see some people have already downloaded it...
A new GApps package isn't quite ready yet. I believe PA has a Lollipop GApps package up that may work as-is and would be better than the one I'm currently linking to, so give that a try if you're impatient.
I also have a new TWRP build on the way as well.
Short changelog on the new build:
- Superuser is now built-in, no need to flash SuperSU. It's in the Settings app. You may have to enable the "Development Settings" menu to see it...
- Video playback should be fixed. YouTube in particular seems OK. If you have some weird format you're playing back locally I cannot make any guarantees though.
- The camera situation has improved and also regressed. The stock camera is back to the point of where it was with the KitKat Beta builds:
---- Preview works. Saving photos does not work. Video recording works.
--- However:
---- The camera calibration is a little messed up. Long story, but it'll be fixed soon. So your white balance may look kinda funky, among other things.
- Audio quality is improved, and 192kHz FLAC files will now play:
---- This is possible thanks to a new audio resampler, which doesn't impose the same sample rate restrictions of the stock Android ones.
---- It also has far better quality than the stock Android resamplers.
- Kernel changes:
---- Reclaimed 38MB of RAM from the carveout stuff.
---- Removed HDMI's framebuffer, saving another ~16MB of RAM. With Lollipop, MHL/HDMI out isn't working with our old hwc, so might as well save some RAM in the mean time.
---- Added overclocking support, as well as adjusted the stock frequencies a little.84I see there have been some bugs discovered with the recent build, so I'm planning on doing a new build fixing what I can and then updating the OP with that build instead. I also have something special planned for the next build as well... for those of you who follow my GitHub, please don't spoil it! It might not be ready in time, but it's coming along quicker than I thought...
I'd like to thank those of who you have been patient waiting for the new build and not asking when it'll be out etc. I do know it's frustrating for you guys when I give a timeframe on when a new build will be ready and I don't deliver though, however lately the pestering for when a new build will be out has gotten out of hand. I'm usually pretty good with handling things like that which would cause most other devs to basically yell and scream at their users... for example, when people report bugs I'm not one to say "logcat or it didn't happen". At least 90% of the bugs reported are something I can reproduce myself! Why the hell should I need the user to get the logcat when I can get one myself? But anyway, I hope those of you who have been pestering for ETAs can be a little more patient from now on.
I'd also like to thank those of you who have donated to me lately. I usually try to send out thank yous to them when I update the FML thread, but I'm sad to admit that lately I've fallen behind with that. My problem is that I like each thank you to be different and not just a copy and paste generic BS sorta thing, but I'm running out of things to say because there have been so many donations since the GPU driver updating and Lollipop release. Before I update the FML thread next, I will be sure that everybody has been thanked personally.
The donation money has been so helpful lately with me being sick too; I've been able to get food and drinks that are easier for me to digest and keep down.
