yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] chakme:
Hi again...

I've just flashed latest ROM "cm-12.1-20160105-UNOFFICIAL-maguro-BFQ-ZCACHE-LZ4-ZRAM.zip" and everything is running smooth... And [MENTION=4545566]bamtan2[/MENTION] no worry, since I've flashed Cyanogen for the fist time in my GNexus, I knew that it was not official... I just wanted to know how to set ZRAM with those parameters..

But since two weeks ago, I'm facing a issue with my device and I thought it could be fixed with a dirt instalation, but not happened. The device is not been recognized by Windows 10. That happened suddenly, I do not know when it happened. When I connect my device into USB port, It returns me the message bellow:

"Windows has stopped this device because it encountered problems. (code 43).' and "Unknown USB device (Failure on Device Descriptor Request)" (this last one I don't know exactly in English, because my Windows is in PT-BR and I just translated it. But it's about "some USB device descriptor"..

I already made a reset in my device, wiped system, cache, data, internal data, and even so, nothing happend... Can it be hardware, software? I Already deleted all USB device controller at Device Manager... Used USBDeview to uninstall all of it too... Really don't know what to do more !!

Any thoughts ??
[Samsung Galaxy Nexus] hgmichna:
Windows or Samsung install wrong drivers

That is a Windows defect that I know from own experience. Windows likes to install the wrong driver, as if it wanted to sabotage Android. It installs an ADB driver, even though ADB is not activated.

In addition, Windows stores the driver in \Windows\inf as oemxx.inf and oemxx.pnf, where xx is a number. The .inf files are text files, so you can try to uninstall the driver first and perhaps replace it with a Google Android driver and then find and erase its .inf and .pnf files to make it disappear for good.

The next time Windows tries to auto-download a driver to install it, abort that process immediately, before Windows gets to downloading the same wrong driver again.

If you install original Samsung drivers, I think a very similar thing happens particularly with the Galaxy Nexus. Samsung installs some MTP driver that also does not work on the Galaxy Nexus, but that I believe to work on other Samsung phones.

This is off-topic here. Unfortunately I have never found a good explanation of the defect or a better workaround than the crude one I just described, so I cannot point you anywhere. Good luck.
[Samsung Galaxy Nexus] bamtan2:
I googled for windows drivers for android devices and found this: [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 http://xdaforums.com/showthread.php?t=2588979
[Samsung Galaxy Nexus] chakme:
Sorry for the off-topic !!

It installed the drivers, but didn't solve the problem with recognition... it keeps returning the "Device Descriptor Request Failed" message ....

If I understood what you meant, I did the uninstall of the drivers, deleted those .inf and .pnf of Android driver (path \Windows\inf) and even so, Windows didn't recognized my Gnexus.

Thank you all guys, for the help, but I'll keep my research to try to solve that... Once again, sorry for the OFF-TOPIC..
[Samsung Galaxy Nexus] hgmichna:
Windows driver problem

You still have to find, download, and install the right driver.

I think the Google driver is your best bet, but am not perfectly sure.
[Samsung Galaxy Nexus] bamtan2:
When I have USB problems, I try using a different USB port / controller / cable. Some ports are connected to a worse controller, or a broken controller.
[Samsung Galaxy Nexus] aosp:
egl: Remove old tuna BGRA vs RGBA workaround.

Some time before kitkat, a workaround was put in place to keep tuna

working with obsolete PowerVR GPU drivers. The tuna product was dropped

in AOSP for kitkat, but the workaround remained.

There are still a number of devices shipping with OMAP4 processors, and

this workaround continues to be applied on those products even when it

is not required. The effect is that virtual display CTS will fail on

those devices.

https://android.googlesource.com/pl...ve/+/733a80754786d39cdc0fee09509b194472c320bc
[Samsung Galaxy Nexus] torchwood0829:
Hi, i've been using CM11 on my Nexus for quite some time. Decided to flash this ROM after reading about how stable it has been for some people.

I was able to successfully flash the cm-12.1-20160102-UNOFFICIAL-maguro.zip version with my old CWM 6.0.4.7 recovery. Wasn't too sure what the newer ZRAM and BFQ versions meant so I went with the older version to be sure.

I had troubles flashing GAPPS with CWM so I switched to the latest TWRP and was finally able to flash GAPPS using the smallest pico version from Open Gapps. I've been using it for a couple days with all my apps with no problem. Today it started constantly rebooting itself. Sometimes it turns itself off too. I also cant turn it on right away. I have to wait a few minutes before the power button responds. I'm not sure how to proceed. Factory reset? Flash the newer version of the ROM?

Can anybody please give me some advice with what i'm experiencing? Thanks.

EDIT: Can't turn it on now. :( Power button does not respond at all. It's plugged in to it's charger too.

EDIT 2: I got to turn it on. Stays on the home screen for a minute and reboots itself.
[Samsung Galaxy Nexus] norton75:
Happened to me with nearly full SD

How much free space do you have?

You need at least 30% free
[Samsung Galaxy Nexus] torchwood0829:
I tried to get into Settings>Storage before it restarted again but I couldn't reach it on time.

I tried Safe Mode. Made it in. 13.33 total space. 9.65 free space. More than enough I think.

Strange enough, the phone hasn't restarted itself now that im in Safe Mode.

Could a rouge/buggy app cause the phone to boot loop? I did install 1 new app this morning before it started boot looping. Will check if i can remove it from Safe Mode.

EDIT: I was able to remove the suspected app. Im in normal mode now for the last 5 minutes. No restarts so far.

In case anyone is wondering what the app was, it was this:

https://play.google.com/store/apps/details?id=com.rstudioz.habits&hl=en

EDIT 2: 1 and half hours later, still no restarts. It could have been that app after all.
[Samsung Galaxy Nexus] playitlouder:
Grab the Andy Log App and post logs when it happens again.

Stuff like this are usually pretty hard to reproduce..
[Samsung Galaxy Nexus] torchwood0829:
Turns out. My problem still exists. Phone started boot looping and hanging up again last night. Safe mode runs fine. Will try to flash the newer ZRAM version of this ROM to see if it's any better. Will monitor with Andy Log too.
[Samsung Galaxy Nexus] aosp:
https://01.org/android-ia/user-guides/android-memory-tuning-android-5.0-and-5.1
[Samsung Galaxy Nexus] hgmichna:
Highly recommended reading for ROM developers.

They recommend 400 MB zRAM with swappiness 100 for 1 GB devices. Perhaps a slightly smaller size may be apt for the Galaxy Nexus.
[Samsung Galaxy Nexus] Ziyan:
Attached an updated audio hal - overwrite the one in /system/lib/hw with this one, and tell me if it changed anything regarding the issue :)

EDIT: I had to zip it, as XDA doesn't allow uploading .so files.
[Samsung Galaxy Nexus] playitlouder:
[MENTION=4545566]bamtan2[/MENTION] any updates on the GPU blobs?
[Samsung Galaxy Nexus] bamtan2:
In system: audio.primary.default.so (5.27 KB)

In your zip: audio.primary.tuna.so (26.16 KB)

I should I rename one to the other? I will need to do this in TWRP because I don't know any other way ;)
[Samsung Galaxy Nexus] Ziyan:
It should be there already, you just need to replace it:

View attachment 3611360

If you have access to a PC, simply push it using adb:

adb root
adb remount
adb push audio.primary.tuna.so /system/lib/hw
adb reboot
[Samsung Galaxy Nexus] bamtan2:
So if it wasn't there, we're already making good progress ;)

Regardless of my degree of human error, I have good news: I was not able to reproduce the bug and make the video desync significantly! I mashed the screen and made the video skip, but when it smoothed out, the audio looked in sync. Maybe a little off, but certainly not as bad as I expected. These are my first impressions. I thought we did such a bad job of reporting this bug in a timely fashion, that you'd never be able to fix it. Ziyan saves the day! :)
[Samsung Galaxy Nexus] thagringo:
Thanks, youtube vídeos are un sync now !

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] bamtan2:
Update: I've watched several videos to confirm my observation. I do believe there is still desynchronization. But it is much less than before! :) If I had to guess, it might be around the order of ~100ms off. It doesn't seem to get worse.

On ZRAM: With 300MB limit, I rarely see the system use over 200MB. I have only one screenshot with over 200MB used. So I think the debate about exactly how much ZRAM is chosen is likely moot ;) if any limit around 200MB ultimately acts the same.

I noted that Synapse would break ZRAM if I tried to change settings with it on this ROM. It would set ZRAM to 0. I also couldn't change the number of threads. And I found the RGB colors interacted wierdly with the CM color system. So maybe Synapse is not the right tool for CM :)

At this point I think 200-300MB ZRAM and BFQ are ready for default use. I cannot say yet if they are related to the crashing and data loss I experienced with Chrome. But the settings are STABLE enough for anyone to test, even if there are still bugs to be found. I think anyone would be impressed to see Galaxy Nexus run a new android so well!
[Samsung Galaxy Nexus] bandelenth:
I tried this audio fix and it seems to me, that is has gotten a lot better. The desync is not fully gone for me, but it is a lot less.
[Samsung Galaxy Nexus] hgmichna:
Lip sync

Is the desync variable or constant? If it is constant, maybe all that's needed is tweaking some sound delay parameter.

(I know something about home cinemas and AV receivers, but nearly nothing about the innards of Android.)
[Samsung Galaxy Nexus] bandelenth:
It's kind of hard to tell, because I have not found a perfect testing material yet, but I would say that it seems somewhat constant. But I can't really tell for sure right now. However it would be really nice, if it is so easy to correct.
[Samsung Galaxy Nexus] Nabbolo:
Thank you! It seems that this solved the problems for the other guys.

I replaced the file in system/lib/hw using the CyanogenMod file manager, and now I completely lost my audio. I tried rebooting, I tried fixing permissions, but it's no longer working. Any idea before I wipe everything? :)
[Samsung Galaxy Nexus] :
We are official ;)

https://download.cyanogenmod.org/get/jenkins/144834/cm-12.1-20160117-NIGHTLY-maguro.zip

:)
[Samsung Galaxy Nexus] Ziyan:
After countless unofficial builds and hours spent with this, I am happy to announce that maguro is now considered stable enough to get official CM12.1 nightlies :) moving on to CM13 after I find some time, which will hopefully become a nightly soon as well, since the hard part of the work is now done ;) updated the OP accordingly (the builds in the downloads section will stay up for a couple days, just in case there's a problem we need to compare with an older build).
[Samsung Galaxy Nexus] :
Thanks for your great support in our maguro device!!!
[Samsung Galaxy Nexus] Nautilus74:
audio.primary.tuna.so must be added in the official build ? :)

.... Yes...
[Samsung Galaxy Nexus] Nabbolo:
One more reason to wipe and flash from scratch after my audio problem :D great job and thank you!
[Samsung Galaxy Nexus] michael_ch:
Fantastic work! Many thanks for your efforts...
[Samsung Galaxy Nexus] Fenvarien:
Awesome news! Thanks for all your great work and support. :good:
[Samsung Galaxy Nexus] garrymar:
Great news! Thank you for the hard work! Many thanks to all maguro developers! I'm glad to use the glorious phone supported by glorious developers!
[Samsung Galaxy Nexus] hgmichna:
Auto-install through TWRP

Great! Thanks. Just installed it on a Galaxy Nexus that had never seen CyanogenMod before, and it works perfectly well.

However, on another phone I got the new 2016-01-17 version offered by the updater. I let it run its course and got this from TWRP 2.8.7.0, after the updater automatically rebooted into TWRP:

----- TWRP log file -----

Updating partition details:

...done

Full SELinux support is present.

Processing AOSP recovery commands...

Installing mapped zip file '/cache/recovery/block.map'

Installing '@/cache/recovery/block.map'...

Checking for MD5 file...

Skippping MD5 check: no MD5 file found

E:Zip file is corrupt!

E:Error installing zip file '@/cache/recovery/block.map

Done processing script file

----- TWRP log file ends -----

Still in TWRP I then tapped Install and selected the update file from the /sdcard/cmupdater/ folder.

Any idea what that was about? What is block.map? Did TWRP catch a wrong update script file? I am used to TWRP doing these automatic update jobs without a hitch.

Probably no big deal and easy to fix. Just a bit irritating. Thought I should ask, just in case it is something in this particular ROM version.

p.s. Tried the same on yet another Galaxy Nexus and observed the exact same error. It is possible that I had treated both phones similarly before and that that triggered the error on both. But at least the second test proves that the ZIP file was not just incomplete or otherwise defective, because it was a separate download.
[Samsung Galaxy Nexus] thagringo:
i agree having an official CM build is nice but honestly i dont give a sh!t : CM hasnt done anything for us recently, if we are here today its because of all of you guys in this development section that have been taking care of keeping this device alive with builds, kernels, customization and tuning. There are many newer devices here at xda that are dead already and their users can only dream of the free support we got here from all of you.

i really really REALLY look forward to your coming work and support !!

TIA !
[Samsung Galaxy Nexus] massima:
Thank you so much for your efforts to support our ancient maguro. I hope to try your improvements on your next ZMoD release but with MM:D.
[Samsung Galaxy Nexus] jassim007:
Dedication and Hard work brings success. :good:
[Samsung Galaxy Nexus] mukesh:
Congratulations and thanks

Congratulations and thanks for the untiring efforts in the face of all odds to keep the GNexus afloat.
[Samsung Galaxy Nexus] Nautilus74:
Usb-otg don't works on new 2016-01-17 official version....
[Samsung Galaxy Nexus] mlsoftlaberge:
You are a hero, ziyan
[Samsung Galaxy Nexus] giudech:
:good: :highfive: ZIYAN = TOP PLAYER :highfive: :good:

THANK YOU FOR YOUR IMPRESSIVE WORK
[Samsung Galaxy Nexus] ed10vi:
Great news. Thank you so much!

Does the CM Recovery support f2fs?
[Samsung Galaxy Nexus] 0s1ride:
Official nightly (20160117) doesn't have the lowram flags set.

Thanks again for your work!
[Samsung Galaxy Nexus] vortex-5:
So the two bugs that I have noticed:

1. Trebuchet has a strange folder bug where if you have things in a group every time you open it it goes further up.

2. There's still the popping problem it seems to happen when media programs close it creates an audiable pop on the galaxy nexus speaker. Doesn't occur with (4.4.4) I think it's stated once before in this thread but just wanted to point out it's still occuring.

Otherwise it seems to work great very nice and smooth.
[Samsung Galaxy Nexus] bamtan2:
we should take screenshots of the workaround and make a guide on the first page :) it's buried deep within the settings. touch sounds....
[Samsung Galaxy Nexus] vortex-5:
There is still popping even with touch sounds disabled. The popping is a very different noise from the touch sound it's a sharp pop as if the speaker bottomed out and hit something.

Usually the sound co-incides with the phone closing a program or the phone doing a garbage collect operation.

Turning off touch sounds only reduces the frequency but the pop is still present.
[Samsung Galaxy Nexus] Pandi111:
Thank you for your good work and for keeping my phone alive!!!
[Samsung Galaxy Nexus] Childe89:
Great news :) Camera is still buggy though, after video recording camera tends to crash and not be able to run again until restart. :)
[Samsung Galaxy Nexus] gorgooger:
The upgrade from cm11 is a little bit fuzzy, I had to install new gaps and to uninstall/reinstall every google app which is using the google play services ...

And balanced is not really an option, you definitely want to use performance usage.

but after that , everything is fine, so far :- )
[Samsung Galaxy Nexus] Tromzy:
Seriously ??!
[Samsung Galaxy Nexus] hgmichna:
I guess it does not need it any more because of the zRAM memory extension.
[Samsung Galaxy Nexus] freshgiammi:
We knew that! Hehe, but good job finding it out. ATM, recreating a fRom binary is hard (ducati connections), so we would probably be better off with PIE disabled, since it breaks a lot of things on a lot of devices.
[Samsung Galaxy Nexus] zzpianoman:
I wonder if there is a practical way to only allow execution of a specific non-PIE binary while blocking all others?
[Samsung Galaxy Nexus] freshgiammi:
Not to my knowledge. Since fRom is a closed binary (unlike pvrsrvinit, which gets now built with PIE allowed), recreating a opensource version is our only option, afaik. But with no docs and stuff, you can guess how difficult it could be. non-PIE set globally is better, IMHO.
[Samsung Galaxy Nexus] zzpianoman:
I agree considering we have done just fine without it for this long. What else does PIE break that you know of off hand?
[Samsung Galaxy Nexus] freshgiammi:
As far as we know, nothing else since pvrsrvinit has been fixed. On the other hand, users can't run fstrim from LagFix because of the binary. I don't know if it's something app related since I didn't look at the issue, but should be since the command line goes just fine.
[Samsung Galaxy Nexus] rodriciru:
Hi guys.I use this ROM as my daliy ROM and its great.Apart from camera and some other things!

But i think i found a bug. Im not developer, so maybe its not.

if you drain your batery and the phone shuts off, if you try to power on whit an usb pluged in it wont start in normal mode, only in recovery an then you car reboot into normal. And de battery animation for chargin its stoped, so i think i doesent charge

Its only for me??

Thanks developers, this ROM saved me for buying an other phone!!
[Samsung Galaxy Nexus] Reptilez_DK:
Offline charging does not work. It is a known issue. :)
[Samsung Galaxy Nexus] mickeyasamoah:
Is that what its called?? Also I use to think that charging animation was in another partition, but from the looks of things, it seems its in the system partition.
[Samsung Galaxy Nexus] Reptilez_DK:
Firstly: I'm not a developer ! This is pure speculation. Since charging while the phone is off, does not work, it will not have enough power to turn on, into system. It will then reboot, because error, and as a failsafe, boot into recovery, where it will indeed charge, and user will be able to boot into system.

Again, this is pure speculation !

Also, I'm not even able to power my phone on, when a cable is plugged in. I need to remove the battery, reinsert it, and power on, when it is unplugged.

I don't know anything about the animations, at all.

Edit: Anyone feel free to correct me, if I am mistaken. :)
[Samsung Galaxy Nexus] Ziyan:
At every power on, the kernel queries the boot mode from the bootloader. In case you connected the charger while the phone was off, the kernel will read 'charging mode' as the current mode, so it won't load the full OS, just the charging part of it (healthd and the charger executable [the latter is merged into healthd since Lollipop], both of which sits in the ramdisk). There are no separate charging images now, there's only one, healthd creates the rest dynamically from it.

At least that's what I understood after studying the process :rolleyes:

Currently, the charging mode simply hangs - this is where my UART cable should help :)
[Samsung Galaxy Nexus] Reptilez_DK:
That makes sense. Thank you.

So the UART cable can log errors, while the phone is turning on/hangs in charging mode ?

Sorry for asking. :) And please do ignore me, if you're too busy fixing things. :P

I sent you a PM a week or so ago, please do ignore that. Not that I succeeded, but I'll just wait until everything related is merged upstream. :)
[Samsung Galaxy Nexus] Ziyan:
I'm not ignoring anyone, more possibly I just miss stuff, for example I hate XDA's PM system - if you want to talk with me, feel free to msg me on hangouts (this applies to everyone) :)
[Samsung Galaxy Nexus] zzpianoman:
I'm attempting to fix the video recording issue where it appears as if the recorded frame is improperly aligned within the viewing field. Once I disabled the PIE check, thereby allowing the fRom binary to run correctly to calibrate the camera hardware, the recorded video has improved somewhat but is still misaligned.

The video actually looks like the entire frame has been shifted over to one side, leaving a thin vertical (or horizontal, depending on orientation) line running down the edge of the captured video frame. This thin strip appears to actually contain scrambled video from what should actually be on the opposite edge. In other words, the video is shifted over to the right and wraps around from the opposite side.

I'm wondering if this an encoding issue, or if it has something to do with the way the software is reading the video dimensions from the camera. I've already applied the various Samsung-related camera fixes to the VideoModule code in Camera2, but that does not seem to fix this issue.

Any ideas?
[Samsung Galaxy Nexus] freshgiammi:
OMX is good imho. Both DDK 1.8 and 1.9 have that issue, and 1.9 is okay on KK. Perhaps something in framework_av? IDK yet, finished my

exams today so i'll have a bit more free time to check.
[Samsung Galaxy Nexus] zzpianoman:
Ah, so the camcorder works on KitKat with the new GPU drivers? Yeah I've been working long hours trying to fix this one issue. I'm using the 1.8 drivers because I want to have a working camera (for barcode scanner apps) and after disabling PIE enforcement I can now record 1080p video with only a small green bar along on edge - It's usable if I crop that out in post-editing. Another bug with the camcorder seems to be that it likes to continually try to auto-focus during the recording. I think it might have something to do with this in VideoModule.java:

private void updateFocusParameters() {
// Set continuous autofocus. During recording, we use "continuous-video"
// auto focus mode to ensure smooth focusing. Whereas during preview (i.e.
// before recording starts) we use "continuous-picture" auto focus mode
// for faster but slightly jittery focusing.
Set<CameraCapabilities.FocusMode> supportedFocus = mCameraCapabilities
.getSupportedFocusModes();
if (mMediaRecorderRecording) {
if (mCameraCapabilities.supports(CameraCapabilities.FocusMode.CONTINUOUS_VIDEO)) {
mCameraSettings.setFocusMode(CameraCapabilities.FocusMode.CONTINUOUS_VIDEO);
mFocusManager.overrideFocusMode(CameraCapabilities.FocusMode.CONTINUOUS_VIDEO);
} else {
mFocusManager.overrideFocusMode(null);
}
} else {
// FIXME(b/16984793): This is broken. For some reasons, CONTINUOUS_PICTURE is not on
// when preview starts.
mFocusManager.overrideFocusMode(null);
if (mCameraCapabilities.supports(CameraCapabilities.FocusMode.CONTINUOUS_PICTURE)) {
mCameraSettings.setFocusMode(
mFocusManager.getFocusMode(mCameraSettings.getCurrentFocusMode()));
if (mFocusAreaSupported) {
mCameraSettings.setFocusAreas(mFocusManager.getFocusAreas());
}
}
}
updateAutoFocusMoveCallback();
}

I think what is happening here is that during video recording, it changes the autofocus mode from continuous picture to continuous video, but maybe our cameras do not support this particular mode?