yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] wyur:
Don't get me wrong, I was able to successfully compile the 'whole' ROM, which is, by the way, what I am using right now.

Forgetting for a moment about the first issue/error I was having which maybe was caused by some extra dependecies left in my config or whatever else, when I add some driver USB related, say for example my cheap DM9601 USB-Ethernet converter or some wireless USB drivers (neither of those by default included), I get issue number 2.

My steps which may help explaining:

cd ~/android/system/
~/bin/repo init -u https: //github.com/CyanogenMod/android.git -b cm-12.1
~/bin/repo sync -c -f

I add <project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" /> to .repo/local_manifests/roomservice.xml to download proprietary files.

~/bin/repo sync
bash
source build/envsetup.sh
breakfast maguro

I go to /kernel/samsung/tuna and copy in it /arch/arm/configs/cyanogenmod_tuna_defconfig as .config. Then run make menuconfig e from the menu I add the USB drivers I want. Once I finsihed I copy back .config to /arch/arm/configs/ as cyanogenmod_tuna_defconfig (after made a backup).

cd ~/android/system
make clean
cd kernel/samsung/tuna
make mrproper
cd ~/android/system
brunch maguro
[Samsung Galaxy Nexus] erOzeOz:
Anyone knows what is the changelog of build 20160308 ?

It is currently empty on cmxlog
[Samsung Galaxy Nexus] AgusL:
You can see the changelog in cm updater inside about phone.
[Samsung Galaxy Nexus] skyleth:
Guys I really appreciate the effort of updating twrp and supporting f2fs, but there is a specific thread for it here, maybe it's better if we keep this one only for cm12.1
[Samsung Galaxy Nexus] phaleg:
Probably he is not running it yet

BTW, if you are running it already, could you share your impressions?
[Samsung Galaxy Nexus] erOzeOz:
Thanks guys, didn't know it was built in the ROM.

I won't flash it as it seems the only changes since build 20160302 (on which I am) concern update/merge of android-5.1.1_r35 tags.
[Samsung Galaxy Nexus] Ziyan:
I'll try...

Yes.

About the PUK issue, that's really interesting... I have PIN code disabled (I don't think it has any use on a smartphone), so I didn't encounter the issue :confused: I'll try to take a look at it... I don't know what could cause such an issue yet.
[Samsung Galaxy Nexus] Culex316:
Just tried out the latest beta build and I am simply amazed. It already shows A LOT of potential for an alpha release and I'll wait patiently until it is fully stable.

Excellent work man.
[Samsung Galaxy Nexus] Wingerio:
PUK issue solved on 20141201 :)
[Samsung Galaxy Nexus] steevo1:
Thank you!

Thank you so much for pointing this out. I am very grateful for the excellent work here! It is greatly appreciated!
[Samsung Galaxy Nexus] pajd100:
can't get gapps to work

Hi there, first of all thanks a lot for this ROM it is fantastic.

One problem, I get an error when trying to flash the gapps. I have put the config text file in the same folder as the zip file, is there something special I should be doing when flashing them?

Phil.
[Samsung Galaxy Nexus] GorfDroid:
And some folks have the nerve to demand an eta! :mad:

Very disgraceful behaviour.

Thank you to all involved with this project. It can't be easy. :good:
[Samsung Galaxy Nexus] AgentSmith:
Sometimes people get too excited about CM12 making them a little too impatient. I understand that. Don't think you can find any really demanding users here at the moment. And as long as we ignore or politely explain no online wars will start. [emoji4]

Back on topic, I haven't tried the test builds yet. For now I'll keep monitoring this thread and wait with flashing until the few remaining major problems are solved.

And sorry for repeating myself but I really like to know of anyone has tried minimal gapps yet. The one included by Ziyan is still rather big. I always prefer a minimalistic system partition. I download all Google user apps that I need from the play store.
[Samsung Galaxy Nexus] running__man:
Have the same issue.

.txt file is in the same folder where the gapps file is.

ROM flashed normally but when flashing gapps I got error (Status 6). :(
[Samsung Galaxy Nexus] saffa_kzn:
Used the GAPPS from FML, they flashed without any problem....
[Samsung Galaxy Nexus] Airlibik:
Is titanium backup working for you?I'm not able to restore any app
[Samsung Galaxy Nexus] XneofuX:
Status 6

It's a buggy version of CWM. You have 6.0.4.7, with that you can't flash custom Gapps packages (like pico). Just update to a newer or older version (actually any other version will work).

forum.xda-developers<.com>/galaxy-nexus/development/recovery-clockworkmod-recovery-6-0-4-7-t1757146
[Samsung Galaxy Nexus] Tromzy:
I'd like to know that too, if someone tried. :)

Right now I have /data and /cache in F2FS, and /system on Ext4 on CM11 nightly (since CM formats /system in Ext4 even if it was formatted in F2FS) ; If I do a Nandroid backup and try Ziyan's CM12 nightlies, will my /data and /cache remain formatted in F2FS ? And Will I be able to restore my Nandroid backup as it was ? ( F2FS for /cache and /data)
[Samsung Galaxy Nexus] running__man:
This helped! Thanks a lot.
[Samsung Galaxy Nexus] dezful:
I just installed using minimal Gapps and it works flawlessly!

edit1: however, installing google search always ends up on error -505
[Samsung Galaxy Nexus] running__man:
I've restored my apps' data.

Didn't try to restore entire app.
[Samsung Galaxy Nexus] Tromzy:
So maybe the safest is to redownload all apps from the Store and then, restore their data only.

Thanks for the info about the Minimal Gapps !
[Samsung Galaxy Nexus] Airlibik:
I was able to reinstall all my app from zip,from app it stuck in loop.
[Samsung Galaxy Nexus] blacktomcat:
i've never ask a ETA, i've only suggest an idea of partnership because i didn't know that there where only 3 devs working together on it. i respect all the work done and i've never do any pressure to the devs
[Samsung Galaxy Nexus] :
Someone calls doesn't work? I can't call anyone .. error "called unused".

And don't work mobile data.
[Samsung Galaxy Nexus] Airlibik:
I found a little bug on the clock app,as you can see from the screenshot,I selected monday,wednsday and friday and it show it when the windows in expanded but when the windows is collapsed it shows the wrong day,in this case tuesday,thursday and saturday.

Is someone else expecting this?
[Samsung Galaxy Nexus] daasguy:
playstore not working its closing down. tried full wipe and tried with pico gapps as given in first post.
[Samsung Galaxy Nexus] XneofuX:
When your battery is so empty, that you can't turn the phone on anymore ... you actually got a problem :D Yes the symbol appears, but you can't turn the phone on from there and it doesn't charge.

Another point:

I ran into the bug with the mobile network. Things that I saw:

Before it stopped working, the phone app crashed (clicked in "cellular network settings" on "carrier settings").

Then, it still connected to the carrier, but nothing worked (no sms, calls, USSD codes or mobile data).

It connected to the main carrier ("E-Plus" (Germany) for me). That's at least the right Network.

Problem is, that i use a subcarrier called "MedionMobile" which uses the E-Plus network, but the phone actually doesn't get the information from that.

Fixed with crashing phone app some times again with clicking on "carrier settings" and played a little bit with the settings (in the end when it worked, nothing was changed).

Well ... My mother said, that she tried to call me and the mailbox instantly answered. After i fixed it i got no notification, that i missed a call (normally i get a SMS from my carrier).

Hope the information will help to fix the problem ...
[Samsung Galaxy Nexus] Carlos_Manuel:
I wouldn't say that is a bug, because it's not. The new cahnegs on lollipop requires one file for healthd to fix offline charging on tuna. That should also fix charging text from a lock screen.
[Samsung Galaxy Nexus] nikodr:
Ι haven't flashed any lollipop ROM because of this bug. Nowadays most of you amazing developers have managed to bring us a daily driver for our phone.But that bug is nasty.The only solution would be to have an external battery charger,one that you simply take the battery off the phone and connect it there.It helps to charge the battery,i had one or two of such accessories,highly recommended if you have lollipop roms installed.
[Samsung Galaxy Nexus] freshgiammi:
And what's this commit you talking about? ;)
[Samsung Galaxy Nexus] Carlos_Manuel:
I don't know if I'm right with this, but at least I think it's this:

https://android.googlesource.com/de.../android-5.0.2_r1/health/healthd-flounder.cpp which should be modified for MAX17040.
[Samsung Galaxy Nexus] tayyeb:
Found
[Samsung Galaxy Nexus] NicEKidS:
have no google play!!!

please help.

I want to install gapps. but can not.

give me link please. thank you.
[Samsung Galaxy Nexus] Carlos_Manuel:
Ok.

Minnow's kernel has some interesting changes fr off mode like this one:

https://android.googlesource.com/kernel/omap/+/4ef0c4d2561955eeafc1585627736c561ea65bb7
[Samsung Galaxy Nexus] zzpianoman:
I went ahead and compiled the legacy camera app from Cyanogenmod and the same issues exist with the recording of video from the camcorder - albeit some things have improved, such as the autofocus not being so jittery. I'm going to go ahead and conclude that the issue with the improperly sized video is not related to the Camera app itself and is probably somewhere in framework_av.

I/OMXCodec(20207): [OMX.TI.DUCATI1.VIDEO.DECODER] video dimensions are 1408 x 816
I/OMXCodec(20207): [OMX.TI.DUCATI1.VIDEO.DECODER] Crop rect is 1280 x 720 @ (0, 0)
I/OMXCodec(20207): [OMX.TI.DUCATI1.VIDEO.DECODER] allocating 7 buffers of size 1723392 on output port
I/OMXCodec(20207): [OMX.TI.DUCATI1.VIDEO.DECODER] allocated buffer 0x424110b0 on output port
I/OMXCodec(20207): [OMX.TI.DUCATI1.VIDEO.DECODER] allocated buffer 0x42215240 on output port
I/OMXCodec(20207): [OMX.TI.DUCATI1.VIDEO.DECODER] allocated buffer 0x423d10b0 on output port
I/OMXCodec(20207): [OMX.TI.DUCATI1.VIDEO.DECODER] allocated buffer 0x41b660b0 on output port
I/OMXCodec(20207): [OMX.TI.DUCATI1.VIDEO.DECODER] allocated buffer 0x41b66100 on output port
I/OMXCodec(20207): [OMX.TI.DUCATI1.VIDEO.DECODER] allocated buffer 0x41b66150 on output port
I/OMXCodec(20207): [OMX.TI.DUCATI1.VIDEO.DECODER] allocated buffer 0x41b661a0 on output port
I/OMXCodec(20207): [OMX.TI.DUCATI1.VIDEO.DECODER] video dimensions are 1408 x 816
I/OMXCodec(20207): [OMX.TI.DUCATI1.VIDEO.DECODER] Crop rect is 1280 x 720 @ (32, 24)

According to the logs, it looks like the decoder is getting the wrong video dimensions. In KitKat, the video dimensions are equal to the crop dimensions and here you can see that the video dimensions are noticeably larger than the crop dimensions.
[Samsung Galaxy Nexus] GeniusCode:
Hi, I decided to try the new cm12 whereas I found myself so well with the CM11.

it is great to see a rom so young that responds perfectly smoothly

I want to test it thoroughly to see where it can go up to perfection

In the meantime I would like to know what are the nightlies available in the menu "CyanogenMod updates"?

I have not found references online on their existence.

Can I install them regularly? Or this unofficial version is not compatible?

Thanks again for this spectacular rom! :D
[Samsung Galaxy Nexus] ashish811:
those are CM11 nightlies.

CM team is still to announce about their CM12 plans
[Samsung Galaxy Nexus] phuyung:
When fix stock camera? please.
[Samsung Galaxy Nexus] GeniusCode:
LOL

I've seen it 5 minutes ago, too late to edit my post :p

Hope the CM team start it asap

In the meanwhile we enjoy this Unofficial-Beautifull rom :D
[Samsung Galaxy Nexus] foosion:
I tried to go back to the 1201 version from the 1220 version. Despite multiple attempts, including wiping cache and system, it hung on the CM boot animation. I then tried the 1216 version and that booted with no problems.

The only thing I can think of is that I recently upgraded my TWRP version to 2.8.1.0 and am now running trickster mod.

Any idea why 1201 wouldn't work?
[Samsung Galaxy Nexus] blackout23:
Camera seems to be buggy all around in Lollipop. Two of my friends told me yesterday that the camera app hangs when they try to take a photo and both got the stock OTA update to Android 5 on their Nexus 4 and 5.
[Samsung Galaxy Nexus] foosion:
The camera app works fine on my N5 running 5.0.1
[Samsung Galaxy Nexus] aliesz:
I like this ROM more than other lollipops for gnex, because of its smoothness and stability,

The camera issue is not important for me and if big sms problem be solved I will use this Rom as my daily driver.
[Samsung Galaxy Nexus] phaleg:
So, in order to read it, it means you flashed it?

Can anyone tell me if managing text messages from default message app works please?
[Samsung Galaxy Nexus] erOzeOz:
No. You can see the changelog without downloading / flashing the ROM.

I don't know if it works, but I recommend you Signal to replace the default message app!
[Samsung Galaxy Nexus] phaleg:
Ok, I see

I cannot report it, because I am not with this rom yet,

I was asking to know that detail before flashing it

If you are with an older cm12.1 you can check there as well, it should be an older feature, but I would like to be sure it works since my wife cares a lot of old messages XD
[Samsung Galaxy Nexus] wyur:
[MENTION=2633638]Ziyan[/MENTION]

OK so I've tried compiling with the clean defconfig and it builds just fine. When I add any USB driver through make menuconfig I get the two errors I wrote about in my first post. I had previously thought the first error happened regardless but I think because I was reverting the changes I previously made with make menuconfig instead of using (copying back) the clean defconfig.
[Samsung Galaxy Nexus] erOzeOz:
I just tested, the messaging app (built-in sms / text message app) works fine.
[Samsung Galaxy Nexus] phaleg:
My question was if that app can manage (backup and restore) messages...

I am now on SlimLP for maguro and it can manage texts, before moving to Ziyan I would like to be sure it had that feature
[Samsung Galaxy Nexus] hgmichna:
SMS Backup & Restore

You could use the app "SMS Backup & Restore", if Titanium Backup does not cut it.

However, this has nothing to do with CyanogenMod and is off-topic here.
[Samsung Galaxy Nexus] Ziyan:
There's no need to copy any defconfig to .config, as it could cause problems. The correct steps are:

0. cd into the kernel directory

1. make cyanogenmod_tuna_defconfig (this will generate the correct .config)

2. make menuconfig

3. build the kernel using make, or just copy back this .config to cyanogenmod_tuna_defconfig, then run 'make mrproper' to clean up the kernel source dir and build it using the android built system.

Yeah, I'll try to investigate it later.

So, is camera as stable for everyone as it was before the first RAM optimization patch? Can we move on and try out the next one, which will give another ~80mb back?
[Samsung Galaxy Nexus] phaleg:
What about trying to understand the question, before blaming users to be off-topic?

These cyanogenmod nightlies for maguro, come with a default message app.

All what I am asking is to know if these default message app can backup and restore text messages

I know that there are additional apps that could do it, but this is not my question

so if you don't want to spend 30 sec of your precious life to check it and answer

try hard to avoid judging to be off-topic because I was not

(it's a question about this Ziyan's ROM)
[Samsung Galaxy Nexus] defy_owner:
You have my GO to proceed! :)
[Samsung Galaxy Nexus] mukesh:
sms backup

Yes, the default sms app backs up the messages. Confirmed. Created a back up today.
[Samsung Galaxy Nexus] hgmichna:
Backup function in messaging app

Sorry. I wasn't aware that the messaging app has a backup function. I had never seen that.

I looked now, and indeed it does have the function Settings, "Import/export messages" with the three subfunctions "Import from storage", "Delete existing backup", and "Export to storage". I just tried an export, and it creates a ZIP file in the internal memory in the folder BackupSms.
[Samsung Galaxy Nexus] bamtan2:
I'm running the very first CM 12.1 official you released. I stay a step back because I believe in longer term testing than just nightlies, especially because I'm not part of development and I don't know what is happening behind the scenes. Because you're making this comment now, and my testing thus far has gone perfectly well, I will upgrade to the current nightly BEFORE you make the next big change, and I will run this pre-change build for some time and let you know if I find a new camera or video playback problem. Thanks for your work!
[Samsung Galaxy Nexus] phaleg:
Awesome ^_^
[Samsung Galaxy Nexus] ancelin:
Hi,

No more camera issue for me, awsome work!!! I think it is the best rom for our gnex now!

I have had sometime stranges issues (very rare) :

- With shortcuts (light, wifi, gps, profils...) --> Sometime I have a shortcut which disapear or change place, and come back without doing nothing

(if i really need a shortcut back, I just open shortcuts setup without any modification and it come back)

- It happened to me 2 or 3 times that the alarm clock do not worked (and no notification). I have 2 alarms for the morning and the issue happened with the 2nd one which has a profil selection. (I did not notice this with last buil but because it arrived to me a very few time i just wanted to say it)
[Samsung Galaxy Nexus] Fenvarien:
Yes, ROM and camera behavior is perfectly stable here. :)
[Samsung Galaxy Nexus] Master94ga:
I hope to see this changes on Zmod soon! :fingers-crossed:
[Samsung Galaxy Nexus] playitlouder:
Seems all right here.

Can you promote the current nightly to be a milestone / monthly or something, so that they won't get deleted from the cm servers?

That would allow you to tinker with bleeding edge stuff and the ones that don't want to participate can use the stable version.
[Samsung Galaxy Nexus] phaleg:
Which nightly do you mean?

March 9th?
[Samsung Galaxy Nexus] playitlouder:
I cannot check right now, but the nightly I flashed this week works pretty well. Camera etc. I think I installed 03/02 because 03/08 was not available, yet(gnex is handed down in the family, but this thread is fairly interesting).

But I am pretty sure you can go with the latest nightly and it will work just fine.

Use open gapps and try to minimize unnecessary background apps. I use greenify and the phone runs fairly smooth throughout.
[Samsung Galaxy Nexus] AgentSmith:
Me too but I think [MENTION=2633638]Ziyan[/MENTION] will optimize a few more things with this ROM before he spends his precious time on one more Zmod update. :)

From Google:

Most likely wishful thinking but could this be of value to our aging GN?
[Samsung Galaxy Nexus] wyur:
make cyanogenmod_tuna_defconfig fails

make ARCH=arm cyanogenmod_tuna_defconfig succedes, however was what I used when making my very first compiling attempt and needless to say it didn't(/doesn't, I tried again) change anything, to me at least. After the 'tweaks' I substituted cyanogenmod_tuna_defconfig in configs/ with the new .config.

Still get those two errors everytime I select some USB drivers through make menuconfig.

I still think it's not a problem on my end.
[Samsung Galaxy Nexus] bamtan2:
Previously running the Feb 7 build, I just updated to the March 9 build. The Feb 7 CM updater crashed the system GUI and I had to hold the power button to restart. My second update attempt worked successfully.

[MENTION=2633638]Ziyan[/MENTION] The first and only problem/bug I notice with this new March 9 build is that all the notifications say "Contents hidden".
[Samsung Galaxy Nexus] hgmichna:
That is a setting: Settings, Notifications, When device is locked, Show all notification content OR Hide sensitive notification content OR Don't show notifications at all.

Yours is apparently set to hide sensitive notification content, which makes sense when other people can pick up your phone, but you don't want them to read your notifications. I have set mine that way.

But if either your notifications do not need hiding or if nobody can look at your phone, then you can set it so show all notification content when it is locked.
[Samsung Galaxy Nexus] bamtan2:
Thank you for this information! My report is for unlocked notifications. So when the phone is unlocked, all normal notifications say "Contents hidden". So apparently this function in CM has broken. I can confirm that the setting you mentioned WILL make the normal unlocked notification contents show up. Unfortunately I don't know how to report this directly to CM, but I'm sure somebody who does has already noticed the problem and is taking care of it for the future. This is why regular people aren't supposed to use nightlies -- we clog up message boards reporting known issues! ;)
[Samsung Galaxy Nexus] bamtan2:
Here's an interesting case for testing video playback: 360 degree cat video on YouTube! For me, there is a blinking green defect in part of the sphere, behind the camera's starting position. https://www.youtube.com/watch?v=KTyCAfaU1wQ
[Samsung Galaxy Nexus] handofdark:
camera is working fine here :)
[Samsung Galaxy Nexus] vortex-5:
Here's a bug that is somewhat related to the sound pop bug.

If you have screen touch sounds enabled and you're also playing audio then the tap sounds sound like they are of lower / incorrect bit rate playback they sound distinctly more tinny than if the same sounds were played back without the media playback going on in the background.

Possibly the popping issue was related to bit rate mismatch?
[Samsung Galaxy Nexus] Ziyan:
The next nightly (should be up in a few hours at most) will include another memory optimization patch, freeing up about 80 MB of RAM. As usual, report back if it causes any problems :)
[Samsung Galaxy Nexus] playitlouder:
I remember that [MENTION=3390093]MWisBest[/MENTION] changed the Audio Bitrate in his 5.0 rom, and wrote a audio resampler.

http://xdaforums.com/galaxy-nexus/d...05-2014-v2-t2764064/post57321755#post57321755

I guess we are using this thing, too.
[Samsung Galaxy Nexus] vortex-5:
Also earlier in 4.4 CM11 there was a point where all the stock sounds were replaced when they changed the bitrates for something.
[Samsung Galaxy Nexus] bamtan2:
I updated to the March 10 build and this bug is fixed. As expected, CM upstream broke something and then fixed it. :)
[Samsung Galaxy Nexus] Zenroid:
Just updated to mar 11 release and seems it is fast and with 870mb RAM, too good to be true
[Samsung Galaxy Nexus] MAD_psycho_Zz:
just installed cm12.1 latest 11 march build after a full wipe, data,cache,dalvick,system, and i tried 10 times with 10 different gapps packages included open gapps nano which are listed as working in this thread, every time i got gapps fc. trying to install a previous build then update lo latest cm build

edit: even in 10 mar build with a clean install gapps fc

i'm using twrp 3.0.0
[Samsung Galaxy Nexus] vivekjoshi2195:
galaxy nexus maguro

So i have cyanogenmod 11 on my galaxy nexus..working fine.

I flashed cm 12.1 everything was good just one problem.. Now when i am installing apps from my storage it is taking too long. Currently i have cm 12.1 of 9 march !

Help please.
[Samsung Galaxy Nexus] skyleth:
It's the normal behavior for 5.1.1

Enviado desde mi GT-I9300 mediante Tapatalk
[Samsung Galaxy Nexus] Fenvarien:
I installed the Mar 11 release and it's working stable and very smooth. The additional RAM really helps a lot!

Regarding gapps I'm using the quite old but reliable 2016-01-06 opengapps nano package.
[Samsung Galaxy Nexus] johnSpar:
MMS is working fine :) ...and it probably was working OK since day one! :o I was doing the tests against a number provided by the carrier to get automatically an MMS to auroconfigure the MMS settings but due to an unknown reason I do not receive their replies (maybe it could be related to OS detection, official Android vs Cyanongenmod).

So to all people out there with problems with MMS, putting the MMS settings into the data APN should to the trick :good:
[Samsung Galaxy Nexus] MAD_psycho_Zz:
where can i find taht gapps package?