yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] georgedorn:
I can't set the permissions as in Settings > Apps there are no Google apps, there are two strange entries com.android.vening and com.google.android.gms

I did not remove anything

With "add more zips" I mean the option in TWRP to add the Gapps package to the CM13 zip. Both CM13 and Gapps are successfully installed according to TWRP.

In the meantime I tried as another poster suggested Deltradoid Gapps instead of Open Gapps, there is no difference.

First boot takes a while then the new CM13 screen appears showing which apps are prepared and started. After the last you see starting apps...

Then after 2 automatic reboots and initialising CM apps the Welcome wizard appears and instantly you get the Google play services has stopped.
[Samsung Galaxy Nexus] bamtan2:
[MENTION=2633638]Ziyan[/MENTION] I was thinking maybe the ROM maintainers could modify a setting to disable automatic updates in the CM12 updater app. That way innocent people wouldn't get the notification to do a destructive upgrade?
[Samsung Galaxy Nexus] Android-Andi:
[MENTION=333677]georgedorn[/MENTION] what twrp version you are using? Sounds strange. Maybe you need to update twrp?

~ All my work, news etc. on http://andi34.github.io ~
[Samsung Galaxy Nexus] georgedorn:
I'm happy to report that I fixed the issue by flashing the latest unofficial TWRP 3.0.2 from here:

http://xdaforums.com/showpost.php?p=67975081&postcount=2014

Before I used the latest official TWRP 3.0.0

Everything's fine now!
[Samsung Galaxy Nexus] MayuraDeSilva:
ViPER4Android

Any of you guys using ViPER4Android with this ROM?

Works fine when the SELinux mode set to Permissive. But with Enforcing enabled, it doesn't.

Is there any way we can get it to work with Enforcing enabled?

Thanks.
[Samsung Galaxy Nexus] uji_sine:
CM13 snapshot can not show weather in cLock widget, any one have same problem?
[Samsung Galaxy Nexus] KemikalElite:
Make sure you install the Yahoo CM Weather Provider

https://play.google.com/store/apps/details?id=org.cyanogenmod.yahooweatherprovider

You need to install a modified SELinux policy for certain root apps that are normally blocked in enforcing mode.

http://xdaforums.com/showpost.php?p=61242973&postcount=18854

See this post for V4A under enforcing.
[Samsung Galaxy Nexus] Ziyan:
Based on these logs, it seems like the problem is on a lower level (kernel or ducati). Since it seems like you already have your build system set up, please try increasing CONFIG_ION_OMAP_IPU_MEM_IOBUFS_SIZE to something bigger, like 40 and report back if it stabilizes things. While at it, also enable CONFIG_CMA_DEBUG, and upload a dmesg ASAP when camera breaks. Also post the ducati trace1 log, which can be found under /sys/kernel/debug/remoteproc/omap-rproc.1 (trace1 and trace1_last). I'm thinking that the problem arises for people who use lots of apps or something... since I still couldn't reproduce it, camera works fine after 4 days of uptime (used it every day) :(

If notice in the logs that the CMA allocations failed, you should increase the retries (nMaxTries = 25) from 25 to something like 50. It might be possible that killing enough apps to free enough RAM for ducati takes more time if you have lots of apps installed.
[Samsung Galaxy Nexus] MayuraDeSilva:
Thanks for the link [MENTION=3572041]KemikalElite[/MENTION]. I've come across the same link and since it needs SuperSU installed, it doesn't help.

Installing SuperSU still leading to a bootloop and flashing the script without SuperSU is not helping V4A either.

Do you have V4A installed and functioning properly?
[Samsung Galaxy Nexus] uji_sine:
Dear,

Nightly build i used weather provider from Chronus weather, it work fine but on Snapshot not work. Any suggestion.
[Samsung Galaxy Nexus] Regina Rainbow:
Thanks for your reply! It's going to take a while to set up builds with the above changes. I hope, I will manage to do so at the weekend. For analytical reasons I will build two versions of CM13:

1. CM 13 nightly with hal debugging and CMA debugging enabled -> just to get better logs out of the codebase most of us are running right now

2. CM 13 with the above changes to OMAP_IPU_MEM_IOBUFS_SIZE

and

nMaxTries

plus

hal debugging and CMA debugging enabled -> to check if it solves or lessens the problem and to get logs

Update: Builds are finished, flashed the first one a few minutes ago.
[Samsung Galaxy Nexus] iPlasm:
It's a welcome thing for stable SnapShot released for Nexus! that was fast!

Thank you so much!
[Samsung Galaxy Nexus] KemikalElite:
I have SuperSU installed working and its working fine.

For SuperSU installation, make sure your using the flashable zip for v 2.76 from the official thread/website NOT the download from the Play Store.

http://xdaforums.com/showthread.php?t=1538053

http://download.chainfire.eu/supersu-stable

A bootloop during the first reboot is normal (it says so in the recovery when flashed) just pull the battery and boot again.

Without flashing that zip from the V4A thread or setting SELinux to permissive, the only other way to make it work under enforcing as you asked in your last post would be to have V4A updated to support enforcing mode.
[Samsung Galaxy Nexus] Tediiii:
Impressive

My galaxy nexus is getting younger :D:D
[Samsung Galaxy Nexus] MayuraDeSilva:
Thanks for the clarification. Went ahead with SuperSU v2.76 flashable zip and no bootloop encountered this time. Now ViPER4Android is working too. :good:

Thanks again, [MENTION=3572041]KemikalElite[/MENTION] :) Much appreciated!

---------- Post added at 03:06 PM ---------- Previous post was at 03:04 PM ----------

Indeed! ;)

Following the CM13 SNAPSHOT, pleasantly surprised to find official TWRP 3.0.2-0 is listed for our device now: https://dl.twrp.me/maguro/twrp-3.0.2-0-maguro.img.html :victory:

Can't be thankful enough for all the devs who keeping our favorite device alive and up-to-date :good: :)
[Samsung Galaxy Nexus] hgmichna:
SNAPSHOT not visible in updater

I still see only nightlies in the updater. It should only show snapshots if available, or perhaps both, but preferring nightlies is wrong.

I know how to download and install the ZIP manually, but a whole bunch of less technically inclined friends does not. My question is mostly on behalf of them.

What is wrong with the auto-updater? Can it be fixed?

---------- Post added at 12:55 PM ---------- Previous post was at 12:52 PM ----------

Or, better, press and hold the power button for 20 s.
[Samsung Galaxy Nexus] Ziyan:
A new (bugfix) snapshot release will be rolling out in a day or so for all supported devices, fixing this issue. Apparently, it's caused by a missing patch, causing weather to be non-functional.
[Samsung Galaxy Nexus] MayuraDeSilva:
Great! Will that include all the updates up until latest nightlies? :)

SNAPSHOT is already up, but 263.5 MB. Looks like doesn't include the latest NIGHLTY updates.
[Samsung Galaxy Nexus] alex_ee:
Music

It would be nice to switch to the next music track by double-clicking the headphone button as it was in the google music under android 4.3.
[Samsung Galaxy Nexus] KemikalElite:
I tried this and on the Galaxy Nexus it only seems it reboot the phone when CM is fully booted and not frozen.

When I tried holding the power button while it was on the boot animation all it did was freeze the phone :( ...and I had to pull the battery anyway.

Apparently holding the power button to force reboot only works on phones that are designed with that as a hardware feature (mainly phones with non-removable batteries)
[Samsung Galaxy Nexus] MayuraDeSilva:
Interesting! Since [MENTION=2633638]Ziyan[/MENTION] shared about this Kernel feature, I didn't pull mine once. Worked for me in bootloops - froze for a moment but turned off in a second or two. Just had to press and hold until it turns off :)
[Samsung Galaxy Nexus] hgmichna:
Power button reset (20 s)

Ah, I had forgotten! Now it comes back to me that [MENTION=2633638]Ziyan[/MENTION] had put this feature in, so it cannot be a hardware reset and does not work when the kernel is not running. Sorry for forgetting and not mentioning this.

So occasionally we have to pull the battery, but most of the time the 20 s power button push should work.
[Samsung Galaxy Nexus] andifor:
Additional Permissions in CM13

Hi

With CM13, I run into issues with saving additional application permissions. I installed CM13 and open gapps (clean flash, system, and data).

Symptom:

1. Open "Settings"

2. Select "Apps"

3. Select "Configure apps" (the gear-wheel icon on top)

4. Select "App permissions"

5. Select "Additional permissions"

6. Select "Read email attachments"

7. Turn this permission "on" for the built in "Email" client

8. Hit the back button

9. Select "Read email attachments" again

10. => the permission is disabled again

Standard permissions (Calendar, Phone, Location) are no issue.

Did anybody run into the same issue? Does somebody know a solution?

I did collect some logs, I think to be relevant:

08-18 20:28:23.849 D/SubSettings(2073): Launching fragment com.android.settings.applications.InstalledAppDetails

08-18 20:28:23.925 W/ApplicationsState(2073): Cannot find pkg: com.android.terminal on user 0

08-18 20:28:23.944 W/ContextImpl(2073): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:773 android.content.ContextWrapper.sendBroadcast:402 com.android.settings.applications.PermissionsSummaryHelper.sendPermissionRequest:61 com.android.settings.applications.PermissionsSummaryHelper.getPermissionSummary:34 com.android.settings.applications.InstalledAppDetails.refreshUi:556

08-18 20:28:23.952 D/Settings(2073): Have 0 number of activities in preferred list

08-18 20:28:24.121 W/ContextImpl(2073): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:773 android.content.ContextWrapper.sendBroadcast:402 com.android.settings.applications.PermissionsSummaryHelper.sendPermissionRequest:61 com.android.settings.applications.PermissionsSummaryHelper.getPermissionSummary:34 com.android.settings.applications.InstalledAppDetails.refreshUi:556

08-18 20:28:24.123 D/Settings(2073): Have 0 number of activities in preferred list

Thanks!
[Samsung Galaxy Nexus] alex_ee:
I have also

---------- Post added at 01:19 PM ---------- Previous post was at 01:09 PM ----------

Camera and flashlight did not work from time to time after reboot. Sometimes after rebooting the phone flashlight and camera are works (including sometimes occurs with a delay of 1-2 seconds) and sometimes after rebooting the flashlight does not work or camera (or a message appears unable to connect to the camera, or just a bug in the application "camera ")

All errors are sent.

I use cm-13.0-20160819-NIGHTLY-maguro.
[Samsung Galaxy Nexus] vortex-5:
Is anyone experincing with 13 that DHCP seems to frequently fail and most of the time it takes longer to obtain an IP address but a lot of times it will show "Obtaining IP Address" then go back to "saved" and loop a few times?
[Samsung Galaxy Nexus] hgmichna:
Yes, I believe I have noticed this a number of times, but thought it could be a general Android defect that has been there for a long time.
[Samsung Galaxy Nexus] vortex-5:
From what I can tell it was a new bug brought in from 13.0 12.1 did not have this.

It appears if you set region code to United States it helps a bit but I still get it from time to time.
[Samsung Galaxy Nexus] LeoHart:
Same here :( Build 20160813

I noticed the wifi connection since CM13 sometimes frequently drops and reconnects, but today I am unable to connecting with my wifi. After Authentication nothing happens.

The connection-dropping behaviour is more obvious on the GalaxyS2 with CM13.

I can deal with the broken camera or with the connection drops but the failing wifi connection is..... :crying:

Try to flash the latest build...
[Samsung Galaxy Nexus] KemikalElite:
Have you tried Settings > Developer Options > Use Legacy DHCP client ?

Also I believe this is a general CM thing and not the device but it doesn't really make (user-friendly) sense that I need to use developer options to switch between USB MTP and charging.

Why isn't under Settings > Storage as it was before?
[Samsung Galaxy Nexus] vortex-5:
Yes you are correct legacy DHCP seems to work every time I guess there's some a bug in the new client.

As for the MTP thing in Marshmallow you get a notification when you plug in the USB you can then opt to turn on MTP by touching the notification. The developer option probably changes this default to mount as MTP I'm guessing but the normal UI now you should be touching the notification to set the mode.
[Samsung Galaxy Nexus] osm0sis:
In addition to my recent 00-resizesystem.sh addon.d script, I've just whipped up another addon.d script to make the nightly update process even more seamless for those who like SuperSU and other add-ons that would need to be flashed again.

It'll flash anything in /sdcard/FlashAfterUpdate (alphabetically) after the addon.d restore process, and does so in an independent subshell so that it also takes place after boot.img gets flashed. I've got the latest SuperSU zip and my GN Synapse Injector Add-On AK2 zip in /sdcard/FlashAfterUpdate and they both get flashed flawlessly over the new nightly's boot.img, retaining systemless root and Synapse support. :)

/system/addon.d/99-flashafterupdate.sh:

#!/sbin/sh
#
# /system/addon.d/99-flashafterupdate.sh
# For ROMs that don't have "Flash After Update" support built-in.
#
# During an upgrade, this script will flash zips in /sdcard/FlashAfterUpdate
# after all other addon.d backup/restore actions have completed
#
# osm0sis @ xda-developers

. /tmp/backuptool.functions

# define working paths
sdzipdir=/sdcard/FlashAfterUpdate;
tmpzipdir=/tmp/flashafterupd;

case "$1" in
backup)
# Stub
;;
restore)
# Stub
;;
pre-backup)
# Stub
;;
post-backup)
# Stub
;;
pre-restore)
# Stub
;;
post-restore)
# wait out any post-addon.d zip actions (flashing boot.img, etc.)
while sleep 5; do
# read zips from sdcard directory and unpack then run update-binary/script
test ! -d "$sdzipdir" && mkdir "$sdzipdir";
metadir=META-INF/com/google/android;
for i in "$sdzipdir"/*; do
mkdir -p "$tmpzipdir";
unzip "$i" -d "$tmpzipdir" "$metadir/*";
chmod 755 "$tmpzipdir/$metadir/update-binary";
# update-binary <RECOVERY_API_VERSION> <OUTFD> <ZIPFILE>
"$tmpzipdir/$metadir/update-binary" 3 1 "$i";
rm -rf "$tmpzipdir";
done;
exit;
done&
;;
esac;

Attached in my Odds and Ends thread:

https://xdaforums.com/showthread.php?p=40409361#post40409361

v1.0 is located here, with several new features:

https://xdaforums.com/showpost.php?p=72245260&postcount=1223
[Samsung Galaxy Nexus] vaedasti:
Edit: Sorry.
[Samsung Galaxy Nexus] alex_ee:
Camera and flashlight did not work from time to time after reboot

[MENTION=2633638]Ziyan[/MENTION]: Sometimes after rebooting the phone flashlight and camera are works (including sometimes occurs with a delay of 1-2 seconds) and sometimes after rebooting the flashlight does not work or camera (or a message appears unable to connect to the camera, or just a bug in the application "camera ")

All errors are sent.

I use cm-13.0-20160823-NIGHTLY-maguro.

cut log:

dropmefiles[dot]com/FJTCZ
[Samsung Galaxy Nexus] vortex-5:
I have maybe a dumb question but has google officially shutdown the mechanism that allows the Bookmarks Sync Adapter to work? (That's the mechanism that allows android browser to sync with chrome).
[Samsung Galaxy Nexus] hgmichna:
Bookmark sync

I believe that Chrome on the computer only syncs bookmarks with Chrome on the Android phone.

Is this correct? If yes, you may want to install Chrome for Android on your phone.
[Samsung Galaxy Nexus] vortex-5:
A few months ago the BookmarkSyncAdapter.apk allows syncing with AOSP browser but it is no longer operational.
[Samsung Galaxy Nexus] LeoHart:
[MENTION=7046460]Regina Rainbow[/MENTION]

I noticed the camera issue affects the playback function of the YouTube App.

If the camera doesn't work, the YouTube app is unable to play videos. It displays an error.

In order to use the app, the camera must be working.

I'm not sure if the issue be related to the media server, but maybe the short information helps to locate the problem.
[Samsung Galaxy Nexus] bamtan2:
That's weird! The other day for me, on CM12.1, YouTube errored out like that, and I needed to reboot. Maybe I'd I had tried the camera it wouldn't have worked either..
[Samsung Galaxy Nexus] Regina Rainbow:
As far as I can speculate and reproduce, there's two different bugs affecting camera right now:

1. The bug [MENTION=7643454]jango0[/MENTION] described; when this happens, mediaserver is segfaulting while camera app is being started/used. As a result snap (or any other camera app) crashes, since mediaserver is one of the necessary processes. If this bug occurs, the camera app crashes, but mediaserver is restarting in the backround. Result: camera app is working again at the next trial, because all the necessary processes are up again.

2. The bug [MENTION=7143784]LeoHart[/MENTION], me and some others described. When the camera app crashes in this scenario, it will stay broken because it can't reconnect to the camera hardware (or the corresponding software abstraction). This bug seems to be a memory allocation failure which results in ducati throwing errors. (You may imagine ducati as something like the "videocore" or central video driver for our phone.) Maybe when this bug hits, it freezes ducati or processes that rely on ducati partly/completely which could lead to "video based" apps like youtube having problems, since they might rely on ducati for video decoding (acceleration).

But that's just my thoughts. We will have to wait, if [MENTION=2633638]Ziyan[/MENTION] finds something useful in the logfiles we sent him.

On my phone I was able to reproduce this partly just a few minutes ago: after camera bug nr. 2 (=reconnection bug) occurred, video acceleration on my phone was broken. (I don't use the youtube app, so I can't test this specific app.)

Playing a m4v file while bug nr 2 persists: 110-130% CPU usage (according to top)

Playing the same m4v file after a reboot: 2-4% CPU usage (according to top)

-> no video hardware acceleration after camera bug nr. 2, means ducati might be down for one reason or the other - which might prevent youtube app from working properly?
[Samsung Galaxy Nexus] MayuraDeSilva:
FlashAfterUpdate / Flashable Zip

Thanks for coming up with this script, [MENTION=4544860]osm0sis[/MENTION] :) Just wanted to try this one, but didn't work for me though.

Am I missing anything?

1. Created FlashAfterUpdate folder in /sdcard and placed following files:

SuperSU-v2.76.zip

xposed-v85-sdk23-arm.zip

ViPER4AndroidSELinux.zip

eXtremeBeats Aural Maximizer.zip

2. Placed 99-flashafterupdate.sh in /system/addon.d using TWRP File Manager

3. Flashed cm-13.0-20160820-NIGHTLY-maguro.zip (was placed in /sdcard/CyanogenMod)

If I may, I've been placing ViPER4Android folder (with ViPER4Android.apk) in /system/priv-app after each update to have ViPER4Android installed as a system app. Is it possible to make a flashable zip to push 'em instead? A sample zip is much appreciated.

Thanks.
[Samsung Galaxy Nexus] osm0sis:
Did you set 755 executable permissions on the script?

They get flashed alphabetically remember, so extreme beats gets flashed first.

You could definitely make your own zip to do what you're asking, or make viper its own addon.d backup/restore script. It's extremely straightforward stuff.
[Samsung Galaxy Nexus] MayuraDeSilva:
Nope. I didn't do that for 00-resizesystem.sh either. Hence thought just placing the file was enough.

I did it again with 755 permissions, but still didn't work for me. Any ideas?

About the flashable zip, think I was too cautious and wondering if the updater-script should be updated for Galaxy Nexus. Turns out I could use the sample out of the box :)
[Samsung Galaxy Nexus] osm0sis:
Hmm I'm really not sure. It definitely works for me. I'm on the latest nightlies, Open GApps, resizesystem + flashafterupdate addon.d scripts + SuperSU & GN Synapse Injector in FlashAfterUpdate.

Did you Save As to download? People have definitely broken a script or 2 by mistake by copying/pasting over the years.
[Samsung Galaxy Nexus] MayuraDeSilva:
Yeah, used Direct Download link and removed .txt from the saved file. See the attached - attached in a .zip as it doesn't let me upload .sh file.

I'm on 08 / 20 NIGHTLY build with OpenGApps 08 / 06. Have ResizeSystem and FlashAfterUpdate scripts. Have SuperSU + Xposed + ViPER4Android + ViPER4AndroidSELinux + eXtremeBeats in FlashAfterUpdate.

00-resizesystem.sh script works perfectly, but not this one.

Should I mount or unmount anything prior to update?

Let me know if you need anything to investigate the issue.

Thanks.
[Samsung Galaxy Nexus] osm0sis:
Yeah that looks fine too. Hmm. Recovery? I'm using the new official TWRP 3.0.2-0 build.
[Samsung Galaxy Nexus] MayuraDeSilva:
Me too. Official TWRP 3.0.2-0 build.
[Samsung Galaxy Nexus] osm0sis:
Well I'm out of ideas for now. Does it work if you just have the SupeSU zip in there and nothing else? Maybe one of your zips is something it can't handle.
[Samsung Galaxy Nexus] MayuraDeSilva:
FlashAfterUpdate

It's alright, [MENTION=4544860]osm0sis[/MENTION] :) Just wanted to try.

Flashed with only SuperSU zip in it, but no luck either. Screenshots: FlashAfterUpdateSSU.png + UpdateLog.png

Thanks for your help and suggestions.

PS: Attached general images of addon.d + FlashAfterUpdate directories too.
[Samsung Galaxy Nexus] ExecutorElassus:
Question: is anybody else having a recent (ie, about a week old) issue with the phone frequently rebooting itself? My phone reboots with no warning (like, I'm not using it, it's locked, screen is black) a good four or five times a day. It's not that bothersome, but it's annoying if it happens at night and I miss my alarm as a result. Is this a known issue?

I've been sideloading the last recent updates, as the (unofficial) twrp I've been using also tends to reboot when it's trying to unlock encrypted storage.

Thanks for the help.

EE
[Samsung Galaxy Nexus] vortex-5:
I haven't encountered this but I also don't use encrypted storage not sure if it's related.
[Samsung Galaxy Nexus] 9Lukas5:
(I hope this wasn't asked yet, cause I didn't read through the thread^^)

I have freshly installed the latest nightly yesterday and revived my GNex as my current phone has a broken GPS and I'll give it to the repair.

I inserted my simcard now, and after boot I get asked for the pin, it unlocks the card and gives me network. I tested also calls in and out quickly. But then the network goes away and it says only emegency all the time.

Will test if any of my kernel settings are doing something bad here, but am I right that this isn't a common problem?

L

Gesendet von meinem HTC One m7

Edit: I got it fixed by disabling two parts of my done kernel settings
[Samsung Galaxy Nexus] andifor:
If I'm the only one, how can I try to debug this issue? I'd like to be pointed in the right direction...
[Samsung Galaxy Nexus] Regina Rainbow:
This bug might indeed work the other way round, too. Yesterday I wanted to watch a m4v file on my Gnex. It ran extremely choppy, the phone got hot fast, indicating that the CPU does the video decoding, not ducati. Log confirmed this:

08-25 22:35:43.004 D/DOMX ( 556): hardware/ti/omap4/domx/omx_proxy_component/omx_video_dec/src/omx_proxy_videodec.c:226	OMX_ProxyViddecInit()

08-25 22:35:43.004 D/DOMX ( 556): ERROR: failed check:eError == OMX_ErrorNone - returning error: 0x80001001 - Proxy common init returned error

08-25 22:35:43.004 E/OMX ( 556): FAILED to allocate omx component 'OMX.TI.DUCATI1.VIDEO.DECODER' err=Undefined(0x80001001)

I instantly tried to start snap, after I had closed the video app (VLC). Result: snap couldn't connect to camera. Up to the point, when video acceleration failed, everything seemed fine. I had no camera crashes/ reconnection issues until then.
[Samsung Galaxy Nexus] superdragon11:
Hi guys, can I install this version over Cyanogenmod 11 android 4.4.4 KitKat without lose anything?