yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] zzpianoman:
Just thinking out loud here, on a related note:

What if we can get fRom to run in recovery mode and make extracting the calibration file part of the ROM install process? We'd have to somehow get the mtd device populated, bc I'm guessing the camera device isn't defined as part of the recovery drivers list. If we can do this, then extract the calib.bin file to /system/vendor and symlink it to /data/misc/camera as part of the boot process and we can leave all this PIE-disabling stuff behind.
[Samsung Galaxy Nexus] poo706:
I had a thought as well, although yours would be far more elegant if it could be pulled off. Hasn't it been mentioned that the calibration file can be pulled from KK, but that it's not one size fits all? Is every single one of them different? If not, maybe we could gather together a bunch of different calibration files that various people contribute and wrap them up in flashable zips. Then people can install that zip every time, after doing some trial and error to find which one is right.

Hmm, even better... I bet I could easily write a script so that you could install/restore KK, run the script to pull the calibration file & stick it in a flashable zip, restore your LP ROM, flash the zip, profit.

[poo]
[Samsung Galaxy Nexus] pobetiger:
I checked the build.prop on the phone, it is set to 1.

not sure what else to look. I'll have to dig into the code next if it's not already seen before. And yes, I'm using CM-12.0. With the additions from ziyann.

Thanks,

Ben
[Samsung Galaxy Nexus] frizluca:
[MENTION=2633638]Ziyan[/MENTION] i know that it's OT but do u know if exist any cyanogenmod of meizu?
[Samsung Galaxy Nexus] zzpianoman:
As I understand it, each calibration file is unique and is stored in NV flash memory on the camera chip. Although some calib files might be a "close" match, the "best" calibration file is the one that exists on your individual phone. The only issue is extracting that file - which is what the fRom binary does - and apparently, that's ALL it does.....I believe someone tried to dump the calibration file directly by reading it from mtd0, but was unable to do so because a special command is likely needed to get the camera chip to turn on its flash memory. In other words, it is not always "mounted" - which is where fRom comes into play, as it holds the "secrets" to accessing this portion of the camera logic. There's also no way of really knowing if the binary file is a direct read from /dev/mtd0 (i.e. dd=if/of) or if there is some special processing that is done to the data before it is packaged into calib.bin.

I would think that it would be relatively short work for someone to reverse engineer the fRom program and write a simple program that performs the exact same function. Wouldn't it be funny if it was just a glorified version of "dd"? At the moment, I'm happy running my ROM with PIE enforcement disabled so this isn't really a high priority for me right now.

Another solution would be along the lines of what you were thinking - flashing kitkat (or jellybean) and extracting it from there. Perhaps develop a super slimmed down build that only boots far enough to run the calibration, copies the file, then boots back into recovery ready to apply it to Lollipop installation.
[Samsung Galaxy Nexus] poo706:
Everything you mention about the difficulty in extracting the calibration file, is that just LP, or is it difficult on KK as well?

[poo]
[Samsung Galaxy Nexus] zzpianoman:
Well, the difficulty is in figuring out what the fRom binary does because starting with Lollipop, all executables have to be compiled with position independent code (PIE) and fRom was not compiled this way, so under normal circumstances, Lollipop will just refuse to execute it. KitKat had no such restriction so in order to run it on LP, one must disable PIE enforcement (easy, but supposedly a security risk). If you are interested in the patch to disable PIE, you can find it here. Someone had also written a solution that allows only specific non-PIE binaries to run while blocking all others, but I could not seem to get it to work properly.
[Samsung Galaxy Nexus] theBlackEnd:
The most efficient solution is to reverse engineer fRom, IMHO. I don't know if it would be legal, though.

However, we all come from a KK (or LP with non-PIE support enabled) ROM, we could just copy our calibration file to data/media/ that is usually left untouched after a factory reset\full wipe and then copy back it to its location on every data wipe.
[Samsung Galaxy Nexus] zieruchan:
Oops nothing I wrong
[Samsung Galaxy Nexus] zzpianoman:
True, but I think we need a more fool-proof, automated solution.

Few ideas:

Require that all Lollipop ROMS be installed on top of KitKat builds with an intact data partition, at which point the installer script will preserve the calib.bin from /data/misc/camera and copy it to /system/vendor of Lollipop. Init scripts for Lollipop can then symlink from /system/vendor to data/misc/camera on boot so that calib.bin is exactly where the system expects it to be. I think it can be safe to assume that anyone installing Lollipop would be upgrading from a previous version of Android.

So the steps for installing a Lollipop ROM would be:

-flash ROM in recovery

-wipe /data /cache

-install gapps

-reboot

But then how to handle those of us who are already using a Lollipop build without a proper calib.bin? Instruct those people to revert back to KitKat, perform at least one boot so that calib.bin can be copied, then reboot into recovery and install Lollipop as per the instructions above.

Then there is a slightly more horrifying idea that fRom is not just a one-shot deal, and that it actually gets run every time the camera is loaded. I remember reading somewhere in the forums where it was suggested to move fRom from /vendor to /system/bin as it was supposed to speed up switching from front to rear camera. Now the only way that would make any sense (if it actually worked) is if fRom was being called as the camera was loading. I moved fRom to /system/bin in my ROM but haven't done any scientifically valid comparisons to test whether this has made a difference in camera loading time.
[Samsung Galaxy Nexus] Master94ga:
[IMG="Battery"]https://dl.dropboxusercontent.com/u/22722558/Screenshot_2015-01-17-11-15-51.png[/IMG]

The last build is the best :D
[Samsung Galaxy Nexus] Jackson Paulino:
gapps

MY SMARTPHONE AND Galaxy Nexus GT-I9250 Maguro YAKJU JWR66Y, WHEN THE CM12 Ziyan install, DO NOT OPEN THE GOOGLE APPS!

INSTALOS OS GAPPS Manually AI OF THIS ERROR stopped google.process.gapps - How to solve? ja ista lntalei all pa gapps, but not istala !!
[Samsung Galaxy Nexus] fearlessaryan:
Steps for installing a Lollipop ROM would be:

-flash ROM in recovery

-wipe /data /cache

-install gapps

-reboot

Please see the previous comments in the discussion for gapps issues.

---------- Post added at 10:32 PM ---------- Previous post was at 10:16 PM ----------

@Ziyan Not sure how it works for Dreams version 5.3.0.4 : http://xdaforums.com/galaxy-nexus/development/rom-dreams-version-5-1-t2510649 has the fix for the offline Charging. If you can collaborate grabs changes :confused:
[Samsung Galaxy Nexus] nobodyvb:
i clean flshed the rom

but camera dont appear in the app drawer and when i install google camera and want to open that it says Unfortunately, Camera has stoped

what is wrong? please help
[Samsung Galaxy Nexus] fearlessaryan:
Restart ur device. It should go. if it doesn't please use Open Camera
[Samsung Galaxy Nexus] nobodyvb:
restart didnt work and n matter which app i want to use camera doesnt work
[Samsung Galaxy Nexus] fearlessaryan:
Whats ur ROM version. On the latest ROM it works perfectly. Please check!!!!
[Samsung Galaxy Nexus] GamaX320:
before flash rom no need perform wipe data and wipe system operation :confused:

sorry for my poor english :crying:
[Samsung Galaxy Nexus] MrLeeVn:
i want setup supersu for my phone after flash cm12 20150111 . tell me how please?
[Samsung Galaxy Nexus] sodas43:
download supersu zip file, goto recovery, flash it !! :)
[Samsung Galaxy Nexus] fearlessaryan:
u should :)

---------- Post added at 02:34 PM ---------- Previous post was at 02:32 PM ----------

OR

goto Developer option. Root Access -- give it to Apps and ADB only
[Samsung Galaxy Nexus] fink42:
Camera is working on build 20150111, but sometimes this happens, and a reboot is required too get it working again. Anyone else experiencing the same?
[Samsung Galaxy Nexus] fearlessaryan:
Hmmm, Its happening if u open an app for which camera do not work, eg : tourch app in the notifications bar, then restart is required. :). There might be more such apps
[Samsung Galaxy Nexus] Nabbolo:
Yes, as I posted some posts ago, I experience the same.

And no, I don't use any other camera than the stock one, and no, I never try to use flashlight.
[Samsung Galaxy Nexus] Ziyan:
Just a heads up, the flashlight toggle has been fixed, but CM's ffmpeg **** broke the domx, so video playback is now gone, I already have the fix composed in my mind (lol), just need to test it... my finals are here, so I'm pretty busy now, but I'll try to fix and upload a new build in the next few days :)
[Samsung Galaxy Nexus] disclwd65:
so, i am using this rom for about a week now, runs quite smooth but internal root option doesn't seem to work but after flashing supersu 2.40 no problems at all (except the known camera/flashlight issue)

can't wait for next update. this really keeps the nexus alive :D
[Samsung Galaxy Nexus] moovID:
hi.. how about battery life on latest build?
[Samsung Galaxy Nexus] kergefarkas:
It lasted me from 6 AM till 22-23 without a problem. Note that I didn't game on the GNex and don't have Facebook on my phones, so that helps a lot as well. Nowadays I only use it as a phone - like just a phone - with nothing installed, and it lasts about 3-5 days laying on my desk.

But it should get you through the day.
[Samsung Galaxy Nexus] moovID:
thanks. i just installed bbm & whatsapp on my phone.

how about gapps your instaled?
[Samsung Galaxy Nexus] kergefarkas:
I had GMail (for the calendar integration, not sure if Inbox works), Inbox, Maps, Hangouts, G+, Photos, Music, Store, Services, Calendar, Keep, Sheets, Drive and Translate. This is my "basic" Google suite I use on all my primary phones.

I also had Feedly, AppDeals that sync background data, and a couple of other apps, like Remote for MPC, foobar2000 controller or IMDB and some banking apps. I don't use BBM or WhatsApp on either of my phones. Nor Viber.

So you can say I'm mainly a "minimal" user, but I didn't really like the lag, so I rather didn't use anything that caused much and could be avoided with a PC nearby (I know, GN is old and outdated in terms of the OMAP4 and the devs are still making amazing work with CM12, so I'M not bashing their work).
[Samsung Galaxy Nexus] massoudsh:
[MENTION=2633638]Ziyan[/MENTION], plz tell me about fixing offline charging....
[Samsung Galaxy Nexus] freshgiammi:
Can you please stop? It's the only thing you say, and you keep posting this over and over. We're working on that, stop. No further info. It will be fixed when it will be fixed, no etas.
[Samsung Galaxy Nexus] zzpianoman:
I don't even understand the obsession with offline charging. You can charge the phone in recovery and if you don't have enough charge to boot into recovery, then you have even bigger problems, as that is absolutely terrible for the battery. The system shuts itself down when the battery still has about 5 percent charge left.....which is more than enough to boot into recovery where you can then charge either to 100% or just enough to boot back into the system without it shutting down.

</rant>
[Samsung Galaxy Nexus] SergioRius:
Well, in favor of the... obstinate guy, I must say that if I leave TWRP (last version) alone and it shuts screen, I must pull the battery as the phone completely hangs in an unknown state.

Leaving the screen on all night at the bed side is not an option. If I don't want electronic fries and nightmares, of course.

In response for those saying that this version could be a daily option: No.

My hangouts hangs out three or four times before I can read a message and "The user interface app stopped" message is a well known friend of mine now. That with clean 2015011+gapps only. :rolleyes:

Think about Nexus is not only used in USA, so other flavors may have problems. Yes, the menus are in two languages for me, mines and english.

Standing in tune, thou!
[Samsung Galaxy Nexus] ardeus_ua:
[ROM] [5.0] CyanogenMod 12 Beta builds

Disable screen timeout in twrp settings. Had the same
[Samsung Galaxy Nexus] bigflea:
Hello!

First of all: Great Job, Ziyan!! I hoped so much to get Android 5 Lollipop for the Galaxy Nexus! It works nearly perfect!

Even my Sony Smartwatch 1 works perfectly!! WOW!!

Now my question: I wanted to flash CM12-20150111 over CM12-20150110 as an update. It didn't work! Information displays "12-20150110-UNOFFICIAL-maguro" again. Then I tried to flash the ROM over a wiped (System/Data/Cache/Dalvik Cache) system with the same result.

How can I flash cm-12-20150111-UNOFFICIAL? Or did I flash the ROM and the phone shows a wrong version??

I'm looking forward to get a positive answer! And: Thank you again!

Greets, Bigflea
[Samsung Galaxy Nexus] ardeus_ua:
It's the same build, different settings in it. Don't pay attention to it
[Samsung Galaxy Nexus] bigflea:
All right! Thank you!! :)
[Samsung Galaxy Nexus] 0s1ride:
Is there a way for us to tweak this value without recompiling?

I see you edit lowMemoryKillerMinFreeKbytesAbsolute, how does this affect /sys/module/lowmemorykiller/parameters/minfree?

I'm having issues keeping background services in memory (e.g. music).
[Samsung Galaxy Nexus] fearlessaryan:
Is any body facing issues with chrome while browsing ???:confused:
[Samsung Galaxy Nexus] nikodr:
Chrome lags sometimes and there are crashes when phone is out of memory,i noticed that wallpaper might dissappear,there are some problems yet.
[Samsung Galaxy Nexus] foosion:
I mainly see very laggy behavior. It hasn't crashed yet for me on this build, but I don't use it very often. When I exit Chrome, as well as some other apps, it can take a while to redraw the home screen.
[Samsung Galaxy Nexus] BfstMtn:
Chrome's a pig. I'm pretty sure everyone's having problems with it. And memory management seems... less than perfect on all ROMs/builds right now.
[Samsung Galaxy Nexus] kergefarkas:
I always had problems with Chrome on the GNex, no matter the ROM/Android version. I think it is a very well known problem that this phone - for some reason - can't handle Chrome properly. There were even discussion about it on the official Google Channel when Chrome was first released.
[Samsung Galaxy Nexus] BfstMtn:
Turning on zram in the kernel (trickstermod) does seem to help with chrome a bit.
[Samsung Galaxy Nexus] rodriciru:
Not for me.

And i dont have Cm torch app and i cant see in /system or in extracted system.new.dat

Much slowly 20150118 version than 20150111

Great job and be lucky whit finals!!!!
[Samsung Galaxy Nexus] Rindmann:
Which kernel do you use? I can not seem to find the Option in trickster mod..
[Samsung Galaxy Nexus] Ziyan:
New build up, finally found and fixed the goof in domx (it was ONE ******* LINE)... this build contains the torch fix, as well as the theme engine, and some other new cm stuff.

There's no torch app, it's been integrated into the quick settings. If it's broken for you, send a logcat ;)
[Samsung Galaxy Nexus] ALBIEL:
New build torch toggle is working?And stock camera works?
[Samsung Galaxy Nexus] seriousia:
Wow means only video recording bug remains :p:p
[Samsung Galaxy Nexus] Oleg-s:
@ziyan

Offline Charge repaired?
[Samsung Galaxy Nexus] sasuketobi:
from the OP:

Remaining bugs

- charging text stuck on the lockscreen, offmode charging broken

- green lines may appear in the recorded videos
[Samsung Galaxy Nexus] sgspluss:
Please, has [MENTION=2633638]Ziyan[/MENTION] anything written about thats fixed?

If not then there is your answer ;)
[Samsung Galaxy Nexus] Oleg-s:
sorri

Ohh I'm sorry for my English, I use google translator
[Samsung Galaxy Nexus] ALBIEL:
systemuı stopped I clean install
[Samsung Galaxy Nexus] smartAgent47:
Is the rom working smooth in the new build ??
[Samsung Galaxy Nexus] fearlessaryan:
Flash it and see :p. I am downloading.
[Samsung Galaxy Nexus] ALBIEL:
Yes new build and pa gapps status 1 aborted
[Samsung Galaxy Nexus] ardeus_ua:
System ui crashes on 15-01-20 build
[Samsung Galaxy Nexus] root.232:
same
[Samsung Galaxy Nexus] cristobal151:
me too
[Samsung Galaxy Nexus] fink42:
Systemui hasn't crashed for me yet with the new build.. :p

Using Nova Launcher, don't know if that makes a different.
[Samsung Galaxy Nexus] alboz83:
Also i use Nova Launcher, can anyone confirm if with Nova there aren't systemui crash? Otherwise i don't flash the today build
[Samsung Galaxy Nexus] netreign:
system ui has stopped by me.... clean and dirty flash
[Samsung Galaxy Nexus] ardeus_ua:
System ui crashes with nova on dirty install
[Samsung Galaxy Nexus] fearlessaryan:
same SystemUi crashes::confused:
[Samsung Galaxy Nexus] TRemrecan:
system ui crash

system ui stopped?
[Samsung Galaxy Nexus] DomieMic65:
Thank you very much!!!!

If I use an older recovery (I think that now I have 2.7... ) I might have issues???
[Samsung Galaxy Nexus] chinarobin:
it seems doesn't support ext4/sys, and cache,data/f2fs, stuck on cm logo,4 wipes.
[Samsung Galaxy Nexus] Airlibik:
well I never used f2fs and I dunno if this kernel support it anyway there is a modified unofficial version of TWRP for f2fs here

in the first post,maybe it have what you are looking for.
[Samsung Galaxy Nexus] blacktomcat:
i'on 1/12 build and it works quite well. it's as smooth as kitkat and i think that it's ok for a daily usage. the only problem very annoing for me it's the camera and torch issue, but i've to say a big thanks to the dev for this awsome work and it's growing day by day....so...i run to install the new build!
[Samsung Galaxy Nexus] Reptilez_DK:
ROM flashes fine with cwm 6.0.5.1

I don't use f2fs, and of course YMMV. :)
[Samsung Galaxy Nexus] alboz83:
I hope in a F2FS version and in a camera fix (because i have problem also with other camera apps how camera 360 that works one time yes one time no)
[Samsung Galaxy Nexus] frickinjerms:
F2fs is not supported by this kernel, ziyan hasn't added the commits yet.. so you'll bootloop if you aren't on ext4 for all partitions
[Samsung Galaxy Nexus] revanmj:
I constantly see location icon on status bar and in AppOpps it shows that Android System, Google Play Services and depending on a time some Google app (like Inbox) is using location. Event if I disable location from Quick Toggles, the icon in the status bar is still there and AppOps says same thing as before.
[Samsung Galaxy Nexus] kergefarkas:
Is there a way in TWRP to convert back to ext4? I vaguely remember converting to f2fs in twrp, but can't find the options now.

Edit: nevermind, found it.
[Samsung Galaxy Nexus] flip360:
Newest build working good, thanks Ziyan! One weird situation for me though, after i flash the rom i can install apks from sdcard but after a reboot or some time i cant install any apk of off the sdcard, i can only click on cancel button, install doesnt seem to work. Happens to me from the first release from CM and FML also. Any light on the subject? Thanks for the awesome work on Lollipop
[Samsung Galaxy Nexus] blunatic:
Newer Version? Is there a changelog?
[Samsung Galaxy Nexus] Airlibik:
here it is
[Samsung Galaxy Nexus] blacktomcat:
i use FX camera and it works Always...also with flash...try it
[Samsung Galaxy Nexus] an430:
Great to see 5.0 rom in gn, big thanks to Ziyan! Support! Look forward to seeing such great rom growth!

Flash the new bulid, smooth! Only battery usage is more than in 4.4Pa rom!
[Samsung Galaxy Nexus] pvkiniyan95:
just found that stock email app is now functional i.e imap is fixed
[Samsung Galaxy Nexus] tiagofernandex:
Hi there!

I cant get any gapps to work. I install the latest build of the rom, and the gapps that the dev recomends give me the error because of my cmw is the 6.0.4.7, but one user said that the FML works too but not for me, it flasshes normaly, but it keeps getting errors and crashing.

What alternatives i have to get the gapps working?

Thanks!
[Samsung Galaxy Nexus] foosion:
I always see the location icon with 1203. I was not always seeing it with the earlier versions.
[Samsung Galaxy Nexus] w0uter:
Titanium backup ain't restoring here..... evertying else is just working fine for me...

Any solution?
[Samsung Galaxy Nexus] NCguy:
Anyone know if 5.0 has substantially different bluetooth under the covers? I'm in serious need and wondering if it might help solve my disconnect issues.
[Samsung Galaxy Nexus] rajputrajat:
Guyz, is it possible to dirty flash latest version, if coming from latest lollipop fml?
[Samsung Galaxy Nexus] Rindmann:
System UI cas stopped.

Clean install.

With Nova launcher prime.
[Samsung Galaxy Nexus] disclwd65:
jup same here, dirty clean, wipe doesn't matter crashes instantly.

---------- Post added at 03:48 PM ---------- Previous post was at 03:46 PM ----------

with nova, does it still crash or not?
[Samsung Galaxy Nexus] TRemrecan:
how to install rom with nova launcher?
[Samsung Galaxy Nexus] Rindmann:
That all happens with Nova installed.
[Samsung Galaxy Nexus] disclwd65:
honestly i have no idea :silli:

hmmm okee, guess we have to wait for a bugfix
[Samsung Galaxy Nexus] TRemrecan:
thats impossible. crash notification dont close? (sorry my english)
[Samsung Galaxy Nexus] Ziyan:
lol, sorry guys, it worked fine for me :crying: preparing a new build, should be done in 3-4 hours :)
[Samsung Galaxy Nexus] disclwd65:
awesome :good: cant wait
[Samsung Galaxy Nexus] Rindmann:
Thanks man, we all appreciate your great work!
[Samsung Galaxy Nexus] TRemrecan:
ı cant wait. ı eat something and watch breaking bad :) ziyan thank you
[Samsung Galaxy Nexus] foosion:
It's working fine for me.

Thanks again for all your work on this.
[Samsung Galaxy Nexus] Reptilez_DK:
What hardware are you building on ? A clobber build takes ~1,5 hours on my ancient desktop. :eek:
[Samsung Galaxy Nexus] aosp:
[MENTION=2633638]Ziyan[/MENTION]

add overlays to override lowmemorykiller adjustment values

Add overlays config_lowMemoryKillerMinFreeKbytesAbsolute and

config_lowMemoryKillerMinFreeKbytesAdjust to allow a product to

modify the size of the lowmemorykiller minfree buckts. The absolute

overlay sets the size of the largest bucket to the specified value

and scales the smaller buckets proportionally. The adjust overlay

(which can be negative) directly adds to the size of the largest

bucket and to the the smaller buckets proportionally.

https://android.googlesource.com/platform/frameworks/base/+/fcdad6f

set the extra_free_kbytes kernel vm tunable

Set the sys.sysctl.extra_free_kbytes property, which will proxy

through init to the /proc/sys/vm/extra_free_kbytes tunable (on

kernels where it exists). This will ask the kernel to keep

more memory free, causing lowmemorykiller to fire earlier and

allocations to succeed faster.

The size is set to 3 full screen 32bpp buffers. Products can

override the size with an absolute or adjustment value using

overlays config_extraFreeKbytesAbsolute and

config_extraFreeKbytesAdjust.

https://android.googlesource.com/platform/frameworks/base/+/59d80a5
[Samsung Galaxy Nexus] Rindmann:
After flashin 20.01. Rom, I received the System-UI has stopped error. So i went back to recovery, wiped system, cache and dalvik cache and wanted to install the 11.01. Rom.

Now, the phone boots and is stuck with the blue CM logo. Is there anything I can do to fix this issue?
[Samsung Galaxy Nexus] BfstMtn:
Sorry! Should have included that. I'm using [MENTION=4608636]bsmitty83[/MENTION]'s kernel:

http://xdaforums.com/galaxy-nexus/development/lollipop-kernel-fullauto-r1-aosp-cm-t2994371
[Samsung Galaxy Nexus] poo706:
With KK or LP? I used to be able to make KK builds in 1.5 hours, but LP builds take me 8.5 hours.

[poo]
[Samsung Galaxy Nexus] SergioRius:
Wow! How people goes testing a ROM and directly changes launcher.
[Samsung Galaxy Nexus] Reptilez_DK:
That's for Lollipop. :o