yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] christianpeso:
This came across my Google+ feed yesterday. Looks like CM should patch it by this weekend for CM11.

https://plus.google.com/+CyanogenMod/posts/7iuX21Tz7n8
[Samsung Galaxy Nexus] Ziyan:
Hey guys, check out the poll at the top of the thread. Since lots of people still use KK, and CM11 is pretty fine generally, I'm thinking about updating it to use the new kernel and GPU drivers, which should give it a noticeable speed boost (and a bit more RAM). For all I know, all of our bugs on newer ROMs (video recording related) are caused by Lollipop itself, not directly by the drivers. In fact, the new drivers would even fix video recording snapshots on KK, and add support for extremely smooth 1080p/30fps video recording. Not to mention the battery savings from the updated GPU drivers (way more efficient GPU governor, voltage and thermal handling). What do you guys think?
[Samsung Galaxy Nexus] christianpeso:
That would be fantastic! Would you be able to build that for Toro as that is what I am on? Kit Kat seems to run better for me versus Lollipop.
[Samsung Galaxy Nexus] sergialess:
YES!, please, do it!! :)

I suggested doing it for Omni FML (KK), but I guess It would be cool for CM11, too.

Thanks!.
[Samsung Galaxy Nexus] steevo1:
Yes Ziyan, that would be fantastic!
[Samsung Galaxy Nexus] ramsheart:
yes, please... it would be great for us
[Samsung Galaxy Nexus] g3nesisEXIA:
I think at this point it wouldn't hurt, KitKat is still great and runs better than any LP ROM Ive tried. Maybe add whatever makes zMoD sound good in the headphones as well :p.
[Samsung Galaxy Nexus] benoit.btd:
+1 for Ziyan idea ! ;)
[Samsung Galaxy Nexus] Ziyan:
Just uploaded a test build using the new drivers. It's safe to dirty flash this over official builds (and vice versa), so report back how it works (I didn't really have time to test it carefully) :)
[Samsung Galaxy Nexus] g3nesisEXIA:
So....(1 hour in)

Interface/most apps way smoother (Practically LP level at this point), Games run better

Camera works, Video works (Has small purple line at the right)

Idk if this was the case before but audio quality is BANGING on High-Performance mode, no stutter after closing screen 90% of the time

Watching videos on apps (Youtube etc.) way smoother compared to SNAPSHOT build but still has some dropped frames(?)

This is amazing pls help
[Samsung Galaxy Nexus] sergialess:
Promising! thanks for the feedback. It's a pity that video recording shows just one (?) purple line. I'm pretty sure Ziyan will figure out how to adjust it. Regards.

Edit: I have two questions for [MENTION=2633638]Ziyan[/MENTION] on the DDK 1.9:

- Can I change the kernel (custom kernel like DirtyV or Fancy), or I must keep the one that the rom brings?

- Would it be possible to port easily the DDK 1.9 stuff (copy some files?) to other roms, or I'd need to do a full build?.

Thanks.
[Samsung Galaxy Nexus] Astug:
Cheers! Does this test build include the aformentioned new kernel /w more RAM?
[Samsung Galaxy Nexus] sergialess:
Why this rom feels so heavy?.
[Samsung Galaxy Nexus] uji_sine:
Please confirm video record.

Any one please help to confirm problem video record, have a small purple line same LP.
[Samsung Galaxy Nexus] sergialess:
Not exactly the same. While in LP, there is a purple bar (several lines), in this KK there are few lines (maybe only one!!). It is almost imperceptible.
[Samsung Galaxy Nexus] ovejota:
Dirty flashed over CM10 Milestone. Seems smoother, but I'm getting HEAVY battery loss , apparently coming from Android System. What could it be [MENTION=2633638]Ziyan[/MENTION] ?

Screenshot: http://i.imgur.com/DrYjiaa.png
[Samsung Galaxy Nexus] djkk16:
the test build doesnt seem to have support for f2fs right ?
[Samsung Galaxy Nexus] Tetsujin101:
The 1.9 testbuild is with stock kernel clocks as smooth and snappy as a overclocked kernel to 512/1500. awesome job. Will test batterylife and things like bluetooth and camera later.

Thanks for the awesome build!
[Samsung Galaxy Nexus] Ziyan:
Just uploaded an updated version of the test build to the downloads section.

Changelog:

- F2FS support for /data - note that /cache is not used in any recent Android version, making /cache F2FS unnecessary and unsupported

(note to self: to compile CM11 with F2FS support, I need to cherry-pick this commit and add the /data F2FS entry to the fstab)

- 44.1 kHz UI sounds, enabling the use of the fast path (this is broken since KitKat, as nobody noticed that Google silently changed the default UI sounds to 48 kHz ones in KK, resulting in using the regular audio path instead of the low latency one) - I merged this one to the CM repo as well, so the next official build will include this fix as well

- SELinux set to enforcing mode (added a couple missing rules) - report back if it causes any issue

After the small purple line in video recording is fixed, all of this (the new kernel, etc) will be merged to the CM repos, making the last official builds for maguro even more awesome :)
[Samsung Galaxy Nexus] WraithTDK:
AT&T data issue

I just installed 3.0.101-cyanogenmod-ga1e8481, and I can't seem to get a data connection on AT&T anymore. My signal is strong, I can make & recieve calls, and I can use data over wifi, but nothing over cell. On suggestion on the CM forums, I installed the updated baseband, 19250UGLL1, but no joy. Help :confused:
[Samsung Galaxy Nexus] Ziyan:
Did it work on previous builds (nightly)? If yes, I think I know what causes the issue.
[Samsung Galaxy Nexus] mlsoftlaberge:
This is fast and stable for me.

everything i tested works.

Good Job!!
[Samsung Galaxy Nexus] Namautoenx:
Very smooth and fast,thank you Zian
[Samsung Galaxy Nexus] stevo32:
Do these new builds include stagefright fixes? Thanks!
[Samsung Galaxy Nexus] WraithTDK:
I've identified the problem. Well, someone on Reddit identified the problem, more accurately:

[IMG="that aint good..."]http://dl-1.va.us.xda-developers.com/3/4/2/5/6/6/8/Screenshot_2015-08-02-01-13-48.png?key=xe5KP3rzhuw2iIc2b0Rmxw&ts=1438492650[/IMG]

How do I remedy this?
[Samsung Galaxy Nexus] g3nesisEXIA:
Seems like you need to put in At&t's APN settings. Googling it should do.

Also still fast, still has purple line to the right side of the screen.

This is great.
[Samsung Galaxy Nexus] wh0c4re5:
Am I blind? :( Where I can find it?
[Samsung Galaxy Nexus] ALBIEL:
http://xdaforums.com/devdb/project/?id=11013#downloads here :)
[Samsung Galaxy Nexus] Punkiderma:
I'm also very curious about these two questions!

By the way, I'll try it as soon as I get home, thanks a lot [MENTION=2633638]Ziyan[/MENTION] !

I used 5.1 for sometime, and it was great, but after coming back to KK I have to say is definitely smoother on this device. This work you're doing with the DDK is just great!
[Samsung Galaxy Nexus] sergialess:
Good work [MENTION=2633638]Ziyan[/MENTION]!!. You're delivering the smoothest experience in Gnex :)
[Samsung Galaxy Nexus] Ziyan:
Yeah, we all thought that the purple lines were caused by Lollipop - now that we know that the issue is in the domx/camera sources, we at least have a clue where to start debugging.

About your two questions:

- you can use any kernel that's based on my sources (has DDK 1.9 support), by replacing the ramdisk of course. If the specified kernel is meant for Lollipop, you won't have the android logger available (no logcat), as Lollipop deprecated the in-kernel logger and replaced it by an in-ROM logger - this shouldn't cause any issues if you aren't reading logcat

- about porting DDK 1.9 to other ROMs, I'm not sure... it might be possible to do so by carefully replacing all the related files and the kernel, but I never tried it.
[Samsung Galaxy Nexus] Punkiderma:
And what of the kernel is in anykernel format? For example, I can flash smitty's lollipop kernel?

About hte second thing, sure would be nice, since CM misses a lot of useful features that roms like Carbon or Liquidsmooth have :(
[Samsung Galaxy Nexus] uji_sine:
Developper know root cause purple line in video record, I'm glad to here it.
[Samsung Galaxy Nexus] musical_chairs:
Don't forget that after the stride was fixed, but before focus mode and snapshots were fixed, the purple line was actually completely gone. Also, remember that before the stride fix, the green lines were not in the preview, only in the recorded video, but since the focus mode / snapshot fix, the purple line is in the preview as well as the recorded video. Is there something amiss with the focus mode fix that actually created the purple line?

I can't post links to the commits where these changes were made, as they're all squashed into one. But I'm thinking the builds around the time of 2015-05-21 were the ones that had clean videos.
[Samsung Galaxy Nexus] sergialess:
I'm afraid we must experiment by ourselves with all these questions...

The idea is to know which files (including the kernel, of course) are responsible for the DDK 1.9 stuff. We could just compare latest DDK 1.8 CM11 build with test DDK 1.9 and look for differences, but perhaps this is useless.

This afternoon I'm going to do some tests on this idea.
[Samsung Galaxy Nexus] Punkiderma:
I would like to help, but I really don't know where to start.

Please, if there's anything I can do, tell me! Would be great to have a "ddk 1.9 universal package "
[Samsung Galaxy Nexus] sergialess:
Yeah, even knowing that the kernel is mandatory, but it would be nice if [MENTION=2633638]Ziyan[/MENTION] could throw some light at this point.

I understand it is not an obvious subject... but it would be cool anyway :)

Edit

Relevant diferences between:

cm-11-20150712-NIGHTLY-maguro.zip

and

cm-11-20150801-UNOFFICIAL-1.9-maguro.zip

boot.img (kernel)

file_contexts

META-INF\com\google\android\updater-script

system\build.prop

system\vendor\firmware\ducati-m3.bin

Folders with different files (names):

system\bin

system\vendor\lib => very significant folder with a lot of differences in filenames (libraries).

system\lib => some files related to sgx, ducatti and pvr

I'm going to contrast that info also with the Omni FML DDK 1.8 vs Omni FML DDK 1.9 to see if we could port this stuff.
[Samsung Galaxy Nexus] mlsoftlaberge:
The clicking sound of 12.1

I am sorry to report that since after 2015-07-12 , the cm-12.1 bug of the clicking sound is now in the cm-11 build.

In fact the small and mostly inaudible click happens most of the time when we start an application, or ask for a heavy task to be performed.

It seems that it comes from the drivers changes, like the line in the videos.

Maybe it will put someone on the track of finding the real cause.
[Samsung Galaxy Nexus] sergialess:
Trying to backport the SGX DDK 1.9 stuff from the test build to another roms, and... no luck. In the worst case, the system doesn't boot, and in the best case, the bootanimation never ends, so... this is not as easy as doing some file copying/updating.

My attempt is cheap and hackish and it was predestined to failure. Even trying to update the Omni FML already with DDK 1.9, it has failed. I must be doing something horrible xDDDD.
[Samsung Galaxy Nexus] Punkiderma:
:(

I went back to liquidsmooth, Cyanogen has no sense for me. Apart from features, even with the old DDK liquidsmooth (or also Carbon) is much faster, especially using the latest franco's kernel tweaked by [MENTION=4544860]osm0sis[/MENTION]!
[Samsung Galaxy Nexus] sergialess:
Yeah, let's try that combo again! (Carbon + tweaked Franco). I'm bored :P
[Samsung Galaxy Nexus] Ziyan:
Did you try getting logs when the bootanimation never ends? Which blobs did you replace?

One thing I forgot to mention - you need to add sime lines to the ramdisk:

diff --git a/rootdir/init.tuna.rc b/rootdir/init.tuna.rc
index 406c740..9940ea5 100755
--- a/rootdir/init.tuna.rc
+++ b/rootdir/init.tuna.rc
@@ -89,6 +89,10 @@ on fs
chmod 0660 /dev/i2c-2
chown media media /dev/i2c-2

+ # pvr module
+ insmod /system/lib/modules/pvrsrvkm_sgx540_120.ko
+ start pvrsrvinit
+
# change permissions for Tiler driver
chmod 0777 /dev/tiler
chmod 0777 /dev/dmm

Otherwise, you'll either face a black screen or stay on the Google logo.

You should also add 'debug.vfr.enable=0' to build.prop for smooth video recording.
[Samsung Galaxy Nexus] sergialess:
I'm not an expert nor an Android developer. I've just tried to copy some files which I've thought they were relevant, such ducatti and pvr sgx libraries (and of course boot.img). Also moved/updated some cfg files like powervr.ini, file_contents, build.prop, updater_script, but still no luck. Nah! thanks anyway Ziyan!! xD.
[Samsung Galaxy Nexus] Ziyan:
Is it only happening in the DDK 1.9 builds? Are you fully sure that you didn't hear them on any other builds?

By the way, the click comes when the speaker turns on/off. It's not related to anything else - if you enable touch sounds, you can observe it nearly every time after the touch sound is heard. I'm gonna debug it...
[Samsung Galaxy Nexus] thuanle:
First, TiBu said that it couldn't get root. Then, I flashed SuperSU, and everything is ok now.
[Samsung Galaxy Nexus] TunedFish:
I don't understand this problem but it seems to be affecting many users. For me, I downloaded from the play store with the paid key and it didn't restore, so I changed location and it worked. No need for extra su stuff.
[Samsung Galaxy Nexus] boogaley:
Google+ Locations

Quick question. Does the Google+ Location app correctly show you a map? And the location of your friends? (Is Google+ a sys app in this CM 10.2?) Other earlier 10.1 CM-based ROMs had this issue and needed to convert the Google+ app to a system app. Thanks!
[Samsung Galaxy Nexus] RevengeFNF:
Do we need the last bootloader for this to work? Or 4.2 bootloader works fine?

Enviado do meu Galaxy Nexus utilizando Tapatalk 4
[Samsung Galaxy Nexus] TunedFish:
You don't need a new boot loader. I was fine with the old one. I flashed the new one and now I'm having problems with oc frequencies sticking with scripts but im not sure if the new boot loader caused them or if it's the 4.3.

---------- Post added at 03:33 AM ---------- Previous post was at 03:27 AM ----------

Bump.

I don't have friends:) I'm going to flash the official nightly, coming from the unofficial with PA gapps. The more we flash/experiment the more we know: ) keep looking or flash back to the old ROM. We all have different results.
[Samsung Galaxy Nexus] korro:
Can I dirty flash on CM 10.1?
[Samsung Galaxy Nexus] TunedFish:
I've heard you can. I've only had problems when I switch gapps providers. In this case, your going to need new gapps, so make a nandroid and flash. If you get fc's , restore and try again.
[Samsung Galaxy Nexus] :
Quick question: I am on 4.1.2. Can I just jump to CM10.2 directly without any issues?

Of course, after a factory reset
[Samsung Galaxy Nexus] SergioA:
I've just done it, only cleared cache and Dalvik, so far no problems!

If anyone is having trouble with apps not getting root access (I had problems with Titanium Backup), try to go in developer options, root access, and change from applications only to applications + ADB. No need to install SuperSU

Inviato dal mio Galaxy Nexus usando Tapatalk 4
[Samsung Galaxy Nexus] koelspy:
It depends on the gapps you flash. If you flash this gapps then Google+ app will be a system app:
[Samsung Galaxy Nexus] dirtyreturn:
I have flashed the PA 4.3 gapps. Thread said it wasn't specific to the rom. So they work.
[Samsung Galaxy Nexus] yojlik:
I notice in the notes for the GApps package that the Google Gallery/Camera is no longer included. I'd prefer the stock app to CM's implementation. Is there a GApps package with Photosphere/Picasa sync included?
[Samsung Galaxy Nexus] dirtyreturn:
Not included in PA's 4.3 Gapps.
[Samsung Galaxy Nexus] ReMuSeR:
Any smooth kernel to use with 10.2
[Samsung Galaxy Nexus] enryfox:
Google stock gallery and camera are included in "official" GApps package. Indeed a nice addition as focal is still not ready for prime time on the gnex.

bye
[Samsung Galaxy Nexus] ke_be:
I need to update bootloader and radio before flash 10.2? Now I use cm 10.1.2
[Samsung Galaxy Nexus] galapagos:
no
[Samsung Galaxy Nexus] abalam:
Franco r390: http://xdaforums.com/showthread.php?t=1367341
[Samsung Galaxy Nexus] Darkat70:
I'm getting, YouTube, Google music & google keep error won't load. Also trying to download from the playstore give error messages. Maps won't update.
[Samsung Galaxy Nexus] Carlos_Manuel:
Caused by the gapps that ypu are using. Use another gapps.
[Samsung Galaxy Nexus] Atento:
I did this test with wifi and everything worked fine. No problems with reconnection.
[Samsung Galaxy Nexus] hhwong:
I did a dirty flash from 10.1 nightly, play store cannot connect, chrome works however so connection is just messed up with play store.

I did a clean flash, wiped everything including data, same issue.

Anyone know how to fix it?
[Samsung Galaxy Nexus] Rufufu:
As it has been said several times before, you must have forgot to flash 4.3 gapps...
[Samsung Galaxy Nexus] hhwong:
I did.....I am a noob but i am not retarded ~_~.....
[Samsung Galaxy Nexus] jorgen2009:
Has anyone tested the new CyanogenMod Account? I just made a build with the necessary code to use it. It finds my device like a charm, but I was a bit reluctant to test the wipe functionality :)

To test it do the following:

Install my test build and reboot (see below)

The phone will ask you to login with your CyanogenMod account. Of course, since it's the first time, you have to create this account and verify it by clicking the verification link in the responsemail from CyanogenMod.

You can now login at the CyanogenMod site using your newly created credentials.You can locate and wipe any registered device from there.

If there is a demand for further testing I can update this post with updated builds (or perhaps make a new thread).

And now the good bits::

ROM https://docs.google.com/file/d/0BwNDN4ITQ7pha3ZJWmEwUlFPLVk/edit?usp=sharing

MD5: E12C113E589CC0C9C5B2C81BAD2B425D
[Samsung Galaxy Nexus] Rufufu:
Sorry if I offend you.

Have you tried to remove your google account and then add it again?
[Samsung Galaxy Nexus] hhwong:
dont worry, none taken.

also i did, tried to force stop google service and enabling it too, cleared cache wipe dalvik everything i tried,

heck i did a clean flash too with the 4.3 gapps, still doesnt work so i just roll it back to 10.1 nightly :(
[Samsung Galaxy Nexus] mrasquinho:
Can someone compile mms.apk with this change for testing, please?

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

I'm on vacations and I don't have access to my building environment.

Thanks in advance
[Samsung Galaxy Nexus] Justinhopaolo:
Low batt warning prompting every time I press okay.
[Samsung Galaxy Nexus] deutschmark:
wi fi bug is present on every 4.3 based rom i've tried.. checking/unchecking optimization didn't work for me but i'll try again. this is weird since on earlier versions it worked with and without optimization (actually i prefer to disable this 'feature'). as far as I understood it happens because the device doesn't scan for networks in the background... PS. turning wifi off and on in the quick settings pulldown menu has the same effect as entering the wifi settings since it triggers the phone to scan for networks.
[Samsung Galaxy Nexus] hanschke:
what is the difference between official nightly? have you picked things to get this feature?
[Samsung Galaxy Nexus] _Drifter_:
To restore with Titanium Backup, it still needs to move the backup to another place? Is this fix yet?
[Samsung Galaxy Nexus] kroogar:
I'm using BrowserTexting and I can't send messages longer than 160 characters from the Chrome plugin. It's been like that with every 10.2. It worked just fine on a JWR66V based 4.3 rom. Sending long messages from the phone app works as expected.
[Samsung Galaxy Nexus] jorgen2009:
The only changes I made are the ones necessary to build the CyanogenMod Account app. The rest is stock CM10.2, just as I like it
[Samsung Galaxy Nexus] Schiehallion:
Yes I had to change location yesterday nightly
[Samsung Galaxy Nexus] Carlos_Manuel:
Then don't dirty flash CM10.2 ...
[Samsung Galaxy Nexus] hanschke:
CyanogenMod Account APK - push it into system\app folder and reboot if you dont want to flash the whole build :laugh:
[Samsung Galaxy Nexus] abalam:
I owe him the builden for you. Later this day I sent you the link. This build has the last repo sync.
[Samsung Galaxy Nexus] mrasquinho:
Thanks pal!

However, it seems that it's working, as it has been merged already...

Thanks once again and best regards!
[Samsung Galaxy Nexus] abalam:
Okay I'll let it be.
[Samsung Galaxy Nexus] mlsoftlaberge:
I am absotely sure about the clicks, cause i pass 1 hour every time i install a new rom, to review all the settings. (yes i go to every options of settings and set them on my settings)

up to the 2015-07-12, I never heard any clicks on cm-11, but I had it on almost every cm-12.1 or other 5.1.1 tests i do (except the one of zzpianoman)

I am not a rom developper (just an ancien computer scientist on retreat) but I test one to 3 roms a day on my Nexus.

in the hundred of different versions of differents roms that I tested in the last 6 months, I always returned to my cm-11 base for a daily driver. This is THE ROM I run for my life to be in. So I know my rom... oups Your ROM.

So i can tell you that it is not coming from the touch sound, since i dont activate it.

I do remark that most of the time it comes when I ask a lot of work to my phone, and then I ask for one more. then click.

I hope my observations can help you pinpoint the cause.

Thanks [MENTION=2633638]Ziyan[/MENTION] for making my phone, one I can be proud of.
[Samsung Galaxy Nexus] ovejota:
What Gapps package are you guys using?

I'm getting the play services battery drain and i hate it!!
[Samsung Galaxy Nexus] skyleth:
I was using the one in here http://wiki.cyanogenmod.org/w/Google_Apps until I brick my testing gnex restoring a backup with a "supposedly" f2fs compatible kernel into a f2fs data partition. Now it does not boot and I can't fix it until I manage to solder the volume button flex to the mainboard
[Samsung Galaxy Nexus] friendlybiker:
Thanks so much, just came back 5.1.1, so much better!
[Samsung Galaxy Nexus] friendlybiker:
Battery life is so much better than lollipop.
[Samsung Galaxy Nexus] leto78:
The nightly is already from 2015-07-12, i.e. almost a month old.

Did Ziyan stop releasing nighties?
[Samsung Galaxy Nexus] Ziyan:
No, that's only because there were no changes since then, so weeklies didn't get built.
[Samsung Galaxy Nexus] sergialess:
It all depends if you have to fight against Google Play Services. Luckily, this rom manages them very well and allows you to deny some privacy events, like "wake up", "keep awake" and "autostart".
[Samsung Galaxy Nexus] stevo32:
Ah, but there have been! Stagefright fixes:

https://github.com/CyanogenMod/android_frameworks_av/commits/cm-11.0

Could we please get updated nightlies with these fixes? I'd greatly apprecaite it.
[Samsung Galaxy Nexus] steevo1:
Thank you Ziyan for the latest build.
[Samsung Galaxy Nexus] michierusama:
I went to download the latest nightly, can I install it over the test build that you posted before with the modified drivers?
[Samsung Galaxy Nexus] w.sherman:
Initial Stagefright fixes were no good

After stevo32 pointed out some security fixes on Aug 12, Ziyan made a new build which was submitted to the nightly builds on 2015-08-13 @ 05:22:09. Thanks Ziyan for being quick to provide a build with the latest security fixes.

Unfortunately the initial stagefright patch did not fix the problem properly and the vulnerability had to be fixed a second time:

http :// www .cyanogenmod.org/blog/more-stagefright

http :// blog .exodusintel.com/2015/08/13/stagefright-mission-accomplished/​

Since the second fix/commit came in on the 13th, I suspect it didn't make it into the new nightly.:

https :// github.com/CyanogenMod/android_frameworks_av/commits/cm-11.0

https :// github.com/CyanogenMod/android_frameworks_av/commit/a5dd546165cf89e946dc8e463ab632c5370bdedc​

How can one confirm exactly which commits are in the nightly build "cm-11-20150813-NIGHTLY-maguro.zip"?

(sorry,the spam prevention does not permit me to post real links, you will have to manually copy/paste and delete the spaces)