yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Nabbolo:
What about the new kernel Ziyan was developing? If I'm not wrong it was going to be compatible both for Kitkat and for Lollipop, and included far better graphics and audio drivers from Texas Instruments than the drivers we are using now. Is it still in developement? Any news? :)
[Samsung Galaxy Nexus] Culex316:
Yes it's in development but let's be patient, shall we? :)
[Samsung Galaxy Nexus] Nabbolo:
I was just asking for an update since some time has passed from the last one

Didnt ask for ETA, didn't put pressure :)

Anyway good to hear it is still an alive project.
[Samsung Galaxy Nexus] RoadToNever:
You can browse his github: https://github.com/Ziyann?tab=activity
[Samsung Galaxy Nexus] :
no use , he pushes directly to cm
[Samsung Galaxy Nexus] Ziyan:
Yeah, it's almost completed, every ROM that uses the new graphics drivers (currently only FML) uses that kernel. CM12 will too :)

I didn't push any code related to CM12 yet. However, the kernel is here: https://github.com/Ziyann/omap/tree/stable-newpvr

About CM12, it may get delayed a day or two more, as I had to do several clean builds (which take long time) until I got an issue sorted out :( I started clean from aosp 4.3's device tree, so I had to upgrade it from jb to lollipop (this makes the commit history a lot cleaner)... while it's nearly done now, I don't push anything yet, until it's booting on my phone :good: hopefully tomorrow or Friday...
[Samsung Galaxy Nexus] massoudsh:
Thank you very much Ziyan...i can't wait for official nightly CM12[emoji7]
[Samsung Galaxy Nexus] Nabbolo:
Great! Many thanks :)
[Samsung Galaxy Nexus] a3361035:
New Privilege Escalation found in Android <5.0 (CVE-2014-7911):

http://seclists.org/fulldisclosure/2014/Nov/51

Will be fixed in the next CM11 nightly (20141119):

http://review.cyanogenmod.org/#/c/77991/

Some other security holes fixed, too:

http://review.cyanogenmod.org/#/q/status:merged+branch:cm-11.0+topic:security,n,z
[Samsung Galaxy Nexus] :
If you want me to help you just tell me, I have high download/upload speeds (180 mbps) and a clean build only takes 1.25 hour,

I can do those things for you if you like, we have testers enough
[Samsung Galaxy Nexus] sgspluss:
After lollipop i've test atm CM11 M12 with ART, its an improvement compared to dalvik the whole device feels faster... Apart of the h264 bug dont find any other thing yet. ;)

Gesendet von meinem Galaxy Nexus
[Samsung Galaxy Nexus] Nabbolo:
One more question, IDK if it was already asked: does this new kernel support tap-to-unlock feature? As far as I know Lollipop does support it natively, but only on devices that have an hardware support for that (for battery purposes ofc). Will it be possible to extend the support to every device with the tap-to-unlock module? I used it one year ago and I'm missing it now that I use stock CM kernel :'( It is so handy!!!
[Samsung Galaxy Nexus] KreNtal:
Try Touch control even if isn't supported anymore. I Don't think maguro's cpu is a good cpu for this kind of things, I tested touch control and it causes to many reboots on my phone.

R. Darko
[Samsung Galaxy Nexus] freshgiammi:
^exactly.

However, there's a feature i've been working on, which basically keeps the screen off but the digitizer on, so that you can have DT2W, but i'm still missing panel hooks so just the core functionality has been implemented. It's still not working, it means.

I'll finish it when i have time, AKA when Lollipop is bug free.

To everyone, feel free to get the source: https://github.com/freshgiammi/omap/commit/29aa91652a69748bb698998c197f7f824d41cd0b
[Samsung Galaxy Nexus] Reptilez_DK:
[MENTION=4986658]freshgiammi[/MENTION] You rock ! :) Awesome work. Really appreciate it.
[Samsung Galaxy Nexus] rseiler:
I'm curious, is encryption going to be required in CM12 as it apparently is with the standard version of Lollipop?
[Samsung Galaxy Nexus] Conte Mascetti:
[MENTION=2633638]Ziyan[/MENTION] I just updated my N7 2012 to lollipop. Music controls in lockscreen are terribly awful!!

Please CM team do something magic for that!

Really awful screenshot:

From GNexus
[Samsung Galaxy Nexus] foosion:
Not only are music controls ugly, they eliminated lockscreen widgets, so you can't start music from the lockscreen (unless you recently stopped it).
[Samsung Galaxy Nexus] a3361035:
Lollipop does not force encryption for old devices, it's only for the new Nexus 6 and 9. [1]

So CM12 will prolly neither.

[1] https://android.com/versions/lollipop-5-0/

At least custom shortcuts are under discussion:

https://plus.google.com/+CyanogenMod/posts/ETx6FjBiGpu

Anyway this has nothing to do with the device tree, so it's hardly the responsibility of the device maintainer. Such feature requests should go to Jira (when Jira is ready for CM12).
[Samsung Galaxy Nexus] Elibl:
Thx for the input likely the same i googled afterwards. I do know what trim does. It was just a quick reply with no real thought on it [emoji13]

FYI it was my phone dying what just happened shortly afterwards. Now with new mainboard my phone flies again [emoji4]
[Samsung Galaxy Nexus] Ziyan:
A small status update on CM12: RIL isn't working yet, I need to find and submit the commit(s) to make it working to gerrit. The rest looks fine (except camera, as I use the updated gpu drivers, but we'll try to fix it before the nightlies begin).
[Samsung Galaxy Nexus] KreNtal:
Can't wait :D

R. Darko
[Samsung Galaxy Nexus] ashish811:
great
[Samsung Galaxy Nexus] m.is.for.michael:
I'm assuming you guys are talking with [MENTION=3390093]MWisBest[/MENTION] about how he fixed the ril in FML...
[Samsung Galaxy Nexus] flip360:
Any news on cm12? No ETA just a question
[Samsung Galaxy Nexus] sgspluss:
Let me answer your question with two quotes:

1.

...and...

2.

Now you will know it ;)
[Samsung Galaxy Nexus] flip360:
Thanks, already knew that.
[Samsung Galaxy Nexus] Ziyan:
I'm still in the process of figuring out what's wrong with RIL. CM may have messed up something, as it should work now...
[Samsung Galaxy Nexus] Airlibik:
I found this in FML section it seems they get it working like this but maybe you already know about it
[Samsung Galaxy Nexus] freshgiammi:
This does nothing actually haha, the fix is in hardware_ril.. but CM borked things.

Ziyan is working with us, we got a group hangout so everything that happens on FML or CM, we know it.
[Samsung Galaxy Nexus] Airlibik:
Ok nice to hear this.

keep up the good work ^^
[Samsung Galaxy Nexus] Ziyan:
Finally, RIL is fixed.
[Samsung Galaxy Nexus] Suxsem:
Great! GSM and WCDMA?
[Samsung Galaxy Nexus] sgspluss:
What for wonderfull news! :good:

Thank you [MENTION=2633638]Ziyan[/MENTION] for all those hard work for us from you :highfive:
[Samsung Galaxy Nexus] rajputrajat:
Hi ziyan,

Is it fixed by using old ril daemon or you fixed the damn thing directly?

Thanks
[Samsung Galaxy Nexus] ashish811:
just waiting for the build to be uploaded :D
[Samsung Galaxy Nexus] AllAboutTech:
it is already uploading?! :eek: awesome!
[Samsung Galaxy Nexus] Ziyan:
Fixed it by cherry-picking 4 commits that our ril requires to work.
[Samsung Galaxy Nexus] KreNtal:
Where can I find it?

R. Darko
[Samsung Galaxy Nexus] Nabbolo:
Great, I'm looking forward to the first nighlies :) if the only big problem left is just the camera (that I don't use so much) it would be awesome!
[Samsung Galaxy Nexus] martialaw:
Hi Guys!

I have been on CM10.2 for the last months because a few months ago CM11 was laggy on my phone.

Now I got the thing repaired (had kernel panics) and now again want to give CM11 a chance.

I read the last 20 pages, but got confused over CM12, seems to me this thread mostly contains CM12-related posts now.

So please excuse me for asking, I honestly tried my best to get the info myself.

What is the current state of CM11?

What's the most stable version atm (M12 or nightly?) and exactly what errors/bug are still in there?

I would stay at CM10.2 if CM11 is not completely smooth and bugfree.

Thank you!
[Samsung Galaxy Nexus] Darklife1337:
my advice: m10+franco kernel, m11 was slow for me ;)
[Samsung Galaxy Nexus] martialaw:
Was that issue identified and fixed with M12? Or is M10 still better despite being 2 months old?

By the way, this seems to be a mixed thread for CM11 and CM12. Is there still work being done on CM11?

Gonna wait for some more input, thanks Darklife
[Samsung Galaxy Nexus] sgspluss:
[MENTION=4751306]martialaw[/MENTION] this is exalcly what i mean in other thread, why do you not take the time so read a bit?

I mean if you take the time you'll find following two answer for you question, let me quote them for you.

1.

2.

So as you can read from they two quotes, the last reminig bug are h264 (which are since M11 if i am not wrong builded in), but apart of them M12 is bugfree and with ART an very quick, responsiv and fast rom. I use it with franko kernel btw ;)

About CM12, this will gonna take more time to fix few things befor it will be published.

FML (AOSP 5.0) are already published but it contains bugs, few of them will be fixed in coming update, the other in updates after coming update.

So Android 5.0 will takes a bit more time, but atm for beta its working pretty nice!

Conclusion:

If you need an rom for daily useage which are stable use CM11 M builds, here you can take the dission between new M12 or old M10 (both working really nice).

If you wanna test new things you can use FML (android 5.0) as i saied it working nice but it contains bugs, stable to use but maybe not for daily driver atm.
[Samsung Galaxy Nexus] Suxsem:
Can you please link me those 4 commits?
[Samsung Galaxy Nexus] martialaw:
Thanks for the conclusion. I've read the last 20 pages here but somehow overlooked your M12 post inbetween the whole CM12 discussion.

For someone who is up-to-date with a given topic it's easy to tell what's going on. I have to check the forums more often I guess!

I can live with a little bit of minor lag, the version I tested in summer had crazy lags.

There seems to be a manual fix for the video issue (http://xdaforums.com/galaxy-nexus/general/how-to-to-solve-hw-video-playback-t2559138) in case I need that.
[Samsung Galaxy Nexus] sgspluss:
Well M12 is stable enougth for daily use, i use it on my own atm (since it was released) and working pretty nice so far with ART ;)

Ok you have to reboot your phone few more times as you stay on dalvik but i can deal with them (personally i reboot my phone every 2 - 3 days after charging)

This fix what you posted it not needed, if i am understand the "h264 bug" correctly you can use the needed libs from older M build like M10 or M9 where it working.

Just replace it in M12 zip and the "bug" will gone, but hard to say which libs have exacly need to replace so you replace the whole lib folder (much easier).

But dont know if anything will be broken after proceed this step, cause i dont changed anything i can deal with the "bug"...
[Samsung Galaxy Nexus] martialaw:
I usually don't reboot my phone in weeks, so I will activate ART. Or are there any reasons to stay on dalvik? (Besides a few apps not working)

That h264 bug - if I understand correctly - is irrelevant if I do not want to record on h264 codec. Regular video recording still works, right?

Both topics there is not a lot of articles about. So thanks again for your help!

edit: Wait, do you have to reboot a lot on dalvik or on ART? Just to be sure about your semantics...
[Samsung Galaxy Nexus] sgspluss:
To be clear first the situation of ART and reboots, dalvik works still fine but on my experiance it was a bit laggy in few situations. If you using ART your phone will benefit from it but you have to restart it more times as on dalvik, otherwise (again on my experiance) it will be slower day by day.

Now about "h264 bug", h264 codec are standard if you look into the camera (video) settings, i think if you change it to one of both other h263 or MPEG4 it will be fine but never test it cause doesnt use my phone as videorecorder...
[Samsung Galaxy Nexus] martialaw:
I think I'll check out M12 on Dalvik, and if that's not smooth enough it's 10.2 for me again. Nothing wrong with JB after all.
[Samsung Galaxy Nexus] sgspluss:
Haha yes right, but after going back to JB if KK on dalvik not working so nice think about to try ART.

ART is also in Lolipop standard but sadly in KK not so optmized, anyway tried it out by yourself and get you own experiances :good:
[Samsung Galaxy Nexus] a3361035:
On gerrit there are only two:

http://review.cyanogenmod.org/#/q/reviewer:jaraidaniel%40gmail.com+status:open+branch:cm-12.0,n,z

At this time these are:

http://review.cyanogenmod.org/#/c/78128/

http://review.cyanogenmod.org/#/c/79279/

Stop recommending pre-release ART. Google and CM did add a big warning to it for a reason. It breaks more than just having to restart.

Please write a real bug-report on Jira for that:

http://wiki.cyanogenmod.org/w/Doc:_The_JIRA_project_management_system

CM 10.2 isn't maintained since February 2014. So it has major security holes.

Basically everything mentioned after that date on:

https://plus.google.com/communities/118124907618051049043
[Samsung Galaxy Nexus] Ziyan:
That's correct, as it turns out, those two are all that's required to fix the RIL. The other two is only used to retain compatibility with the qcom multisim stuff (which broke lots of rils). They will be added to the rild commit your link shows.

In the meantime, I'm updating the kernel with some minor stuff to go with lollipop. Those interested can watch the progress here: https://github.com/Ziyann/omap/commits/stable-newpvr

Thanks to [MENTION=2838735]aosp[/MENTION] for pointing out mmc commits, we have mmc health info now! :p Here's mine:
[Samsung Galaxy Nexus] Tromzy:
I have a question regarding the upcoming CM12 Roms : are they going to be fully compatible with F2FS ? My phone has /data, /system and /cache in F2FS. I read something about CM12 not compatible with /system in F2FS or something like that ?
[Samsung Galaxy Nexus] aliesz:
I think that ROMs based on lollipop, don't need to be converted f2fs.
[Samsung Galaxy Nexus] sgspluss:
Well dont find any other problem yet since i used ART :eek:

I know its just experimental in KitKat but it works, maybe you can tell me what are the other problems with it (means what it breaks)...
[Samsung Galaxy Nexus] martialaw:
The need for reboots shows me that it's not ready to roll out, however if it helps people why not try it. It's the development section, almost everything here is experimental.

By the way, CM11 M12 on franco and dalvic runs flawless for me. Way better than it ran a few milestones ago. As expected :good:
[Samsung Galaxy Nexus] a3361035:
F2FS on /system is pretty pointless, because it's mounted read-only and most F2FS benefits lie in random write.

Even FML dropped it, because all in all you just lose ~100MB due to F2FS overprovisioning:

https://github.com/MWisBest/android...mmit/3d42e5a7873dc387f347667cf71c1cc5d885fa18

Read further in the next answer.

Yes, that commit in AOSP should keep the current filesystems during flashing:

https://android.googlesource.com/platform/build/+/5bfed5a

(assuming recovery is F2FS-ready)

Actual filesystem support is provided by the kernel, so just make sure it supports F2FS and its filesystems table (fstab) matches yours.

But getting a compatible custom kernel for CM12 might be problematic as it expects Ziyan's new kernel with updated GPU driver. Currently no custom kernel offers that. (maybe FML's kernel)

For vold support there's :

http://review.cyanogenmod.org/#/c/77724/

(tho kind of pointless with no fstrim and fsck)

But beware F2FS is still very much in an experimental state (especially that strange backport for tuna which uses old mainline instead of Motorola/AOSP's F2FS).

Even the Nexus 9 recommends a wipe on errors due to no working fsck:

https://android.googlesource.com/device/htc/flounder/+/66b9aa7

https://source.android.com/devices/tech/dalvik/art.html#Known_Issues

http://developer.android.com/guide/practices/verifying-apps-art.html

All those fixes in platform/art for Lollipop:

http://aosp.changelog.to/aosp-KITKAT-LRX21L.html
[Samsung Galaxy Nexus] sgspluss:
WOW thank you [MENTION=5856785]a3361035[/MENTION] for this very helpfully links :good:

I know ART was experimental but contains (on my mind) such big problems, surprice me and also didn't know that.
[Samsung Galaxy Nexus] xaifer:
Nightly 20141127

I'm not able to download the last nightly... http://get.cm/get/lzS

I see this:

Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/tornado-2.4-py2.7.egg/tornado/web.py", line 1037, in _execute
self.prepare()
File "/usr/local/lib/python2.7/dist-packages/tornado-2.4-py2.7.egg/tornado/web.py", line 1487, in prepare
raise HTTPError(self._status_code)
HTTPError: HTTP 404: Not Found
[Samsung Galaxy Nexus] Ziyan:
I didn't cherry-pick the F2FS support yet into the kernel, but if it's the only thing required, I'm willing to do it.

By the way, I made pretty good progress with CM12 - overall, I'm quite happy with the bringup so far. There are still some minor things waiting to be fixed, like the charging indicator on the lockscreen and the offmode charging mode seems bugged, but I use it as a daily driver without any problems (I don't care about these minor issues). Oh, and the stock camera app is still behaving oddly, we need to get that fixed too.

I have decided to drop 32 MB of reserved tiler memory. This adds 32 MB of usable RAM back to the system, without compromising 1080p functions at all (we could drop more than 40 MB and still have 1080p working, so 32 should be totally good). [MENTION=3390093]MWisBest[/MENTION] also found out that HDMI mirroring is broken (probably because HWC 1.0), so disabling that added back another 16 MB of RAM.

So overall, we have over 750 MB of usable RAM now, with everything working, and there's still room left in the tiler memory for custom kernels (bigram).
[Samsung Galaxy Nexus] Airlibik:
Will you upload the rom when all this issue will be fixed or it will be uploaded a nightly that will be fixed time to time?
[Samsung Galaxy Nexus] Ziyan:
Since I received several requests to publish test builds, here you go. My builds are available here (updated constantly). Only use the gapps from that page, with the provided gapps-config.txt (place it next to the zip file for flashing). This is because I have dexpreopt enabled (since I flash several test builds a day), which increases the system partition size, so only a minimal sized gapps will fit.

Generally, this is similar to FML. The current bugs are:

- charging text stuck on the lockscreen, offmode charging broken (I'm pretty sure we need to move the charging logic from the kernel to healthd, beginning the work soon...)

- stock camera app broken (if you do 'setprop camera2.portability.force_api 1' you can get preview working on it, like on kk, but it's easier to just use a 3rd-party camera app)

- video playback broken (something's missing from CM12, I'll find it)

- screen off animation sometimes buggy (this may be an issue with CM itself)

There may be other minor ones, nothing major for me... but remember, these are test builds meant to be only tested by me and a small group, so if something's broken, please don't spam the thread full of it (feel free to hit me on hangouts if you really want, I like it more than using PM's).

As you may see on my github, I'm beginning to have more free time, I'm working on this stuff daily, so this is really in-progress yet ;)
[Samsung Galaxy Nexus] Wingerio:
Thanks!!!

Is it compatible with F2FS?
[Samsung Galaxy Nexus] foosion:
Please consider starting a separate thread for these builds. If nothing else, it may decrease off topic posts in this thread and would provide a place for testers to answer other testers questions without bothering you.
[Samsung Galaxy Nexus] a3361035:
No, look at the kernel source and its supported fs (filesystems):

https://github.com/Ziyann/omap/tree/stable-newpvr/fs
[Samsung Galaxy Nexus] xergio24:
+1
[Samsung Galaxy Nexus] aliesz:
Has anyone tried the CM12 test builds?
[Samsung Galaxy Nexus] piterdemon:
I have tried. Videos on youtube, facebook etc work but that there is same bugs like on FML

================================

Just press thanks button if I helped :)
[Samsung Galaxy Nexus] Airlibik:
I've tried to install it this morning but I was not able to install gapps thet op posted so I tried install fml gapps and it work but I'm not able to get google account. if I try to add it in the account section I don't find add a google account I found only email account.

I've installed it by cwm now I'm tring to reinstall it usin twrp maybe it will work this way.
[Samsung Galaxy Nexus] Khizar:
Enable NU player in dev options. That'll fix the videos.

Sent From My A0001 With AK Awesomeness!!
[Samsung Galaxy Nexus] aliesz:
I don't think the google account be related to your recovery type, because I have installed fml ROM and gapps by TWRP 2.8.1.0 and the same issue is occurred:good:.
[Samsung Galaxy Nexus] piterdemon:
I know

================================

Just press thanks button if I helped :)
[Samsung Galaxy Nexus] Airlibik:
I flashed that gapps but I got error and I'm not able to install them.

there is a different procedure that I've not understand to install them?
[Samsung Galaxy Nexus] TheMan0790:
Did you make sure to have the .txt file in the same folder as the gapps when you flashed the gapps? Was system unmounted as well? Running very well for me right now.
[Samsung Galaxy Nexus] martialaw:
Maybe you could open a thread for CM12 and keep this one a CM11 thread? Lots of people (like me) want to go with KitKat and are a little confused about this thread talking about BOTH versions... Thank you!
[Samsung Galaxy Nexus] Airlibik:
I have to flash rom->gapps->txt or i just need to have txt in the same folder of gapps?
[Samsung Galaxy Nexus] xaifer:
With CM12 phone ask me for PUK Code and not PIN code XD
[Samsung Galaxy Nexus] TheMan0790:
.txt file merely needs to be in the same folder as where your gapps are located when you flash the gapps.
[Samsung Galaxy Nexus] Ziyan:
I opened a thread for CM12 in order to keep this one clean. Feel free to talk about CM12 as much as you want in this one: http://xdaforums.com/galaxy-nexus/development/cyanogenmod-12-beta-builds-t2958865 and let's keep this one for CM11 :)
[Samsung Galaxy Nexus] maxiv:
Great ROM, I've been using it for months....

well, now I've decided to pass the phone on to my girlfriend. So I went to settings -> backup & Restore and did a factory reset. Ever since my phone has been stuck in a boot loop. I booted into recovery and wiped cache and data but still, nothing - still stuck in a boot loop.

Can anyone tell me how to get the phone to boot up again? Unfortunately, I made an absolute rookie mistake and didn't do a nandroid backup...
[Samsung Galaxy Nexus] Ziyan:
Reinstall your rom from recovery (push the zip with adb if you need to).
[Samsung Galaxy Nexus] maxiv:
thanks for the tip! I got adb to run in recovery and pushed the rom.zip to sdcard...but when i hit "Choose zip from /sdcard" in the recovery to install a zip, it a "Can't open directiry. No Files found."
[Samsung Galaxy Nexus] Conte Mascetti:
I think the only option is to try, lastly how about buying a otg cable? It helps to avoid so many headaches, trust me.

From GNexus
[Samsung Galaxy Nexus] Ziyan:
I would suggest you to install TWRP instead of CWM, which is way easier to use... idk what's that sdcard error you're getting (maybe CWM doesn't mount it automatically and you need to do so manually?).

One more case I might think of is that factory reset somehow corrupted your partition, so formatting it may also help :confused:
[Samsung Galaxy Nexus] maxiv:
what exactlyy should i format?

ADB push seems to work fine. i pushed to several folders...sdcard, sdcard\0\, storage\sdcard, etc....but when i go to "install zip from \sdcard", \0\, \OBB and \clockworkmod show up. But whatever i tap on, i always get "No files found"....so where are the files being pushed to !?

the cmd tells me how loong it took to push the file with a certain filesize, so i'm assuming the adb push worked successfully?!