yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] Maxicus1:
I like the dark theme too. Was great.

The volume up and down buttons are still not able to switch tracks from the music player while sceen is off.

Auto rotate works for me.

Dirty Flashed 20160407 Nightly (Wipe Cache/dalvik).

LockScreen bug is gone fore me.

And a question: Is WiFi Direct working ? I get a connection to my Samsung TV but it stays at the loading screen. S2 says already connected.

Feels a little bit smoother overall.
[Galaxy S II Android Development] Andrea900:
Google Now on Tap is finally working for me! :victory:
[Galaxy S II Android Development] karrlito:
Stock camera is only good for video because any other app for recording that i tried is crashing. Auto focus for picture taking stopped working after they put patch for camera on the first releases (forgot which exactly) and after that no auto focus for me. Tested on 2 phones. To focus i need to touch screen every time... Also the stock camera app makes my camera buzzing (sometimes i feel my phone vibrating from the camera...) so i switched to procapture that have all of the gone scene modes and no buzzing sound.

And for the video files now with the new releases of CM MX player HW accel is working. No black screen only. But HW+ is not working.

[MENTION=5798657]Skyline[/MENTION] Forgot to say that. The front camera is not working with stock app from some time for me too. From what i remember on 02 and 07 build.
[Galaxy S II Android Development] Skyline:
Getting camera error[Can't connect to camera] when trying to take pic from front cam. Same on 30th March and 7th April build.

Anyone else??
[Galaxy S II Android Development] laptopu:
Dirty flash from 30/3 to 7/4 with Google camera app and DSLR paid app, can switch between cameras fine on both. Try wiping cache?

Also someone mentioned rotation issues, I am not having this problem again try wiping cache/dalvic.

I did have lots of stock email app problems since about 29/3, set to push receive, it often never retrieved emails or would give one blank email for every received email, I wiped storage and reset the accounts but still problems. Anyone else? For now I am using gmail app for a non gmail IMAP account but there is no push receive on this.
[Galaxy S II Android Development] 74mk:
I make the same mistake
[Galaxy S II Android Development] Spyr0s:
Anyone knows why /data partition gets full after a month or so? I have duplicate or triplcate entries of apps like

com.google.android.gms-2 (127,8MB)

com.google.android.gms-3 (127,8MB)

com.facebook.orca-1 (101.6MB)

com.facebook.orca-2 (100.9MB)

com.google.android.youtube-1 (57.2MB)

com.google.android.youtube-2 (57.2MB)

com.google.android.youtube-3 (57.2MB)

...629.7MB for three apps? Plus the space in system partition for gms and YouTube that were installed with gapps?
[Galaxy S II Android Development] daniu:
Hi

No idea why they are double in /data but they end up additionally in /data because the system app cannot be updated easily so playstore installs an additional updated copy in /data. The version in /system is useless from this point on as long as you don't want to reset the app to the original state.

In former times titanium backup and/or link2sd could integrate the update into the system but for quite some time the successrate of this operation is close to zero. I suggest installing an updated version of gapps in recovery. You can try to integrate the apps with one of the apps as long as it is not playstore. If the operation fails normally the app is completely gone which is quite a problem if it is playstore and you did not expect it ...

There is also a manual way to do that with a root explorer (es file explorer or total commander) however that includes renaming some apk files and moving them to various places - I never succeeded - probably beyond me ...

Regards

Sent from my x-phone using brain 2.0
[Galaxy S II Android Development] Kevin3014:
The lock screen bug still exists, but it's not serious.

When in the lock screen, if you touch the top-left or top-right portion of the screen, the lock screen buttons would appear on the top of the screen, if you swipe down from top-right the camera app will open up.

More preciously, you need to touch on the Mobile Networks sign/WiFi sign shown on the top-right screen to see the buttons.

I'm on 20160407 build.
[Galaxy S II Android Development] LudovikXVI:
i have the same problem, I can not resolve it on every CM firmware. On stock 4.2 no problem, works fine. Please help. 10x
[Galaxy S II Android Development] Draky50110:
Have sometimes this problem, not every day or everay nightly.

Soft reboot fixes the problem...
[Galaxy S II Android Development] jainalo:
I have the same problem with front cam. Also I have the locksreen bug.

I'm on 20160407 build.

Enviado desde mi GT-I9100 mediante Tapatalk
[Galaxy S II Android Development] p3dboard:
There's a library of Nexus drivers,including widevine/google DRM files for the various Nexus devices here -https://developers.google.com/android/nexus/drivers#fugummb29u

I tried Qualcomm versions for android 6, but they don't seem to be compatible with our Samsung Exynos processor. I haven't tried the Nexus Player as I think they use Intel processors I believe, so I think we need Arm CPU versions.
[Galaxy S II Android Development] Skyline:
I know that other camera apps works without problems but I am talking about stock camera app and btw I always perform clean wipe for each nighly that i am flashing.

[MENTION=6159291]Lysergic Acid[/MENTION]

Attaching logs if you think it's important take a look.

Thanks
[Galaxy S II Android Development] Spyr0s:
Yes i know that system apps will add an apk in data partition when being updated but thats not the case. I have two "Messenger" apps, three "youtube" apps and two "google services" in data partition without reason...

What i did to solve this.

1. Unistalled Facebook Messenger

com.facebook.orca-1 (101.6MB)

com.facebook.orca-2 (100.9MB)

GONE from /data

2. Unistalled Youtube updates from Settings-->Applications

com.google.android.youtube-3 (57.2MB)

GONE

com.google.android.youtube-1 (57.2MB)

com.google.android.youtube-2 (57.2MB)

REMAINED

3. Uninstalled Goole Play Services updates

com.google.android.gms-3 (127,8MB)

GONE

com.google.android.gms-2 (127,8MB)

REMAINED

4. Reboot

5. Deleted

com.google.android.youtube-1 (57.2MB)

com.google.android.youtube-2 (57.2MB)

com.google.android.gms-2 (127,8MB)

folders in /data partition with a file explorer

REBOOT, TRIM ETC

GOT 1 GB BACK

but clearly there is a problem somewhere, because i don't have the same problem in my nexus 7 2013 with CM13. I think that i9100 runs out of memory while installing apps, installer crashes and retries but without cleaning the garbage.
[Galaxy S II Android Development] pappy_034:
I think that is in this build 04/07 battery life a bit worse, and I tried to use 3G(Cellular data) but it didn't want to connect to it (no H+ or E sign in status bar). Does anyone experiencing this problems?

And what screen on time would you get with normal use ?
[Galaxy S II Android Development] Sub_Zero2:
While googling, I found a neat little app to test drm drivers/plugins; DRM Info, by android fung. You can find it on google play. Could be useful when trying out libs ?
[Galaxy S II Android Development] ahmadabumaizer:
Could anyone please upload the trebuchet apk for me and save my phone
[Galaxy S II Android Development] pravingasva:
I am facing phone heating issue, however less battery life! But I can connect to the networks properly.

I didn't searched much, but this might help: http://xdaforums.com/moto-g-2014/themes-apps/android-m-launcher-cyanogenmod-trebuchet-t3123514
[Galaxy S II Android Development] ssandyji:
Hear it is
[Galaxy S II Android Development] pappy_034:
What are your impressions about 20160409 build ? How can I enable Now on tap?

I saw that is lockscreen bug fully fixed it works perfectly without problems!
[Galaxy S II Android Development] DTSParsley:
i have problem with the gapps

no free space
[Galaxy S II Android Development] Draky50110:
Read first post.

Entirely.
[Galaxy S II Android Development] Drx86:
Have you read first post?

http://xdaforums.com/galaxy-s2/development-derivatives/guide-want-to-update-to-cm13-read-t3313978

______________________________________

Does anyone know what's up with Cyandelta today? It seems unable to find today's build. :confused:
[Galaxy S II Android Development] Andrea900:
Tried 9th April build, cannot access camera/scan qr codes yet.

---------- Post added at 05:38 PM ---------- Previous post was at 05:36 PM ----------

From Settings->Google-> Now
[Galaxy S II Android Development] Kevin3014:
For me, only the front camera shows 'Can't connect to camera'. Rear camera works.
[Galaxy S II Android Development] pappy_034:
When I went to google now settings and opened section "now on tap" I couldn't do anything with the switch it's grey.

[MENTION=7013647]Kevin3014[/MENTION] Both of cameras are working fine for me.
[Galaxy S II Android Development] Andrea900:
Update your gapps. It was enough for my device! :)
[Galaxy S II Android Development] Alucard:
Hey [MENTION=6159291]Lysergic Acid[/MENTION] can you please support if you have the time the device Lenovo Tab 2 A8-50LC?
[Galaxy S II Android Development] pappy_034:
All of my google apps that I have are updated via Play Store and all are latest so I don't know where is problem.
[Galaxy S II Android Development] Sub_Zero2:
I did some digging: downloaded the whole api 23 android 6.0.1 on a linux computer and mounted the arm system image in the linux fs. I figured that nothing is actually missing on our cm13 version, until i checked the file sizes:

/system/bin/drmserver is either unreadable or has size 0 - in the api it has size 57.6kb, but even with root capabilities it is size 0 or not readable. Not that it means anything, it could be normal. But the L1 libraries are there, in /system/vendor(lib/ and /system/lib/ so it seems there are only compatibily issues, as stated before
[Galaxy S II Android Development] Lysergic Acid:
I can only support devices that I own, sorry
[Galaxy S II Android Development] Alucard:
Oh its ok
[Galaxy S II Android Development] Dii8670:
Battery very drain wen on celullar data and wen on chargering batery drayn wen on celullar data way haw can fix that
[Galaxy S II Android Development] SAMDestroy:
im using isorec twrp 3.0 and i do ask me if i need to be aware of something related to this:

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

can someone please explain it.
[Galaxy S II Android Development] Naudiz:
I just tried latest Nightly and I am experiencing massive problems with notifications. Whenever the phone is sleeping, I don't get any notifications at all.

I have searched through this thread and found some hints that point to the "battery-optimizing" setting. However, fiddling with these settings doesn't seem to fix the problem reliably. Sometimes it works, sometimes it doesn't. Overall the notification handling seems a lot more unstable than in CM12.1.

Also messing with the battery settings can't be the "real" solution. Any "normal" Android 6.0 device has working notifications with optimized battery too, so in theory it should be possible...
[Galaxy S II Android Development] SAMDestroy:
did you exclude google service framework from optimizing?
[Galaxy S II Android Development] Naudiz:
Yes, I tried and I will still do more extensive testing...

However, for reference I took a look into my Nexus 7. It uses optimizing on Google Service Framework and it's no problem there. Maybe doze doesn't work correctly on i9100?

EDIT:

It's no use :(

Google Service Framework optimized or not... It doesn't make any difference. Notifications are not working at all, unless I open the respective app. I guess it's back to CM12 for me. That was my fourth attempt to update to CM13, always struggling with different issues. Maybe CM12 is the end of the road for my old S2...

EDIT2: oh well, just after I wrote these lines, now suddenly notifications work again. I guess I will keep testing. :D

Right now, all I can say is that notification handling feels a little bit more sluggish than on CM12.
[Galaxy S II Android Development] Saber:
Already has been explained in the TWRP thread:

In other words, we are likely to receive official TWRP very soon :)

gsstudios
[Galaxy S II Android Development] Kevin3014:
Both the cameras are working on my device as well, just that I can't capture pics from the front camera using the stock camera app.
[Galaxy S II Android Development] Fasullo:
to be included in next nightly:

audiofx: Add support for line-out path (android_packages_apps_AudioFX)

May be we'll be able to listen again to music through our hifi when docked???

Pleasepleasepleaseplease!!!
[Galaxy S II Android Development] Sub_Zero2:
Thanks for the info ☺
[Galaxy S II Android Development] pappy_034:
In your opinion, what is the best kernel to use with CM 13 and to get better battery life (I mean better SoT).
[Galaxy S II Android Development] Naudiz:
After testing further my issues of not receiving notifications, here are my results:

Disabling battery-optimization for Google Service Framework makes it possible to receive notifications again, but unfortunately not to a stable and satisfactory level.

The notifications do indeed come in, but sometimes with delays between 30 - 60 minutes, which is of course unacceptable for instant-messaging applications. I tried different things like unistall and reinstall Whatsapp, hoping that the app would maybe re-register at google GCM, but with no success. Also the problem is not app dependent, it is a global problem that affects Whatsapp, Signal, Threema, Gmail and all similar apps. Enabling or disabling the battery-optimization for these apps directly, doesn't seem to have any effect.

I can only assume that there is still some serious bug with the way how Marshmallow's doze feature is handled on the i9100.

Owning a Nexus 7 tablet, I can compare how it works on a vanilla-Android device. Usually it is not necessary to disable battery-optimizing for any app. Notifications should work out of the box.

I hope that this is on the "know issues" list of the devs and can be fixed before a stable release.

For the time being I'm (once again) back to CM12.1 lol
[Galaxy S II Android Development] SAMDestroy:
hmm i have no delay with notifications in standby and for whatsapp i changed the push time with this:

https://play.google.com/store/apps/details?id=com.andqlimax.pushfixer&hl=en
[Galaxy S II Android Development] cdzo72:
Good morning to everyone...

OK guys I'm pulling my hair out. From the get go I have not had root. I enabled it in the developer settings but any app that asks for root permissions give me a popup saying that my device does not have root.

I came from running NeatROM Samsung based. I repartitioned and all went well, had no issues with installing gApps so I assume the repartition went off without a hitch.

When booting from recovery I did notice that I did not get the message asking if I wanted to repair root access, it just booted straight up.

Knowing that superSU doesn't work with CM13 and our i9100, I really don't know what else to do...

Any help is greatly appreciated!
[Galaxy S II Android Development] gpvecchi:
As I'm on IsoRec, when I slash a newer build, do I have to check the "update recovery" in developer options?

I'd like to update the kernel, but keep the recovery...
[Galaxy S II Android Development] the.gangster:
[MENTION=4909585]gpvecchi[/MENTION]

So far, this setting never had any effect on our device. The IsoRec-Recovery in the recovery partition is not overwritten when a kernel gets flashed.

As long as your new kernel still has IsoRec-support, you will still be able to launch your current IsoRec-Recovery. If it doesn't have IsoRec-support, you will notice it as then the recovery that is bundled with that kernel will launch if you boot into recovery. In that case, once you reflash an IsoRec-supporting kernel, your last (your current) IsoRec-Recovery will be back.

[MENTION=5456499]Naudiz[/MENTION]
[MENTION=6770733]SAMDestroy[/MENTION]

Notification was fixed for me since this commit got merged back on march 28.

So I assume no more exclusion from optimizing is neccessary.

[MENTION=3826867]cdzo72[/MENTION]

normally flashing a 2nd time fixes those problems.

Fixing root in recovery (upon the request that you missed) is not working for Marshmallow.

Recently there were builds where root didn't work. But if I remember right, that was on march 23rd and 24th nightlies.
[Galaxy S II Android Development] Naudiz:
That's super-strange, since I did all my testing with 20160409. It was so bad for me that I'm now back to CM12.

I rely too heavily on notifications, not just for leisure, but also for work, so this was a game-breaker for me.
[Galaxy S II Android Development] oscarlamyf:
I apply icon pack in cm theme but this does not change the icons in now launcher. It does change the icon in recent app card stack. However, after reboot, icons in recent become default again.
[Galaxy S II Android Development] Sub_Zero2:
For me i get root access after updating to the next nightly. After every time i do a clean install ☺
[Galaxy S II Android Development] pravingasva:
Has someone lost AudioFX on 20160409 Nightly?? Its not in the app drawer. :(
[Galaxy S II Android Development] the.gangster:
[MENTION=4659967]pravingasva[/MENTION]

yes, I assume everyone (not just us two) has lost it.

That's why in next build it will be back after this commit.
[Galaxy S II Android Development] Kevin3014:
So that's what was missing! Lol. I did find something rather unusual in my app drawer, but since I don't use AudioFX, I didn't notice it.
[Galaxy S II Android Development] fireburner-de:
I am on 20160331 and I am not sure, that I always get notification instantly. I need to investigate further. But I can tell, that Signal and Telegram give me instant notification.

Not sure about the other push apps.
[Galaxy S II Android Development] Andrea900:
IMHO the camera freeze at startup is much more serious. In my case, the camera module is completely useless, with every camera app I've used.

Furthermore, I'm not seeing any fix about this bug in cmlog, yet.

Any workaround is very appreciated.
[Galaxy S II Android Development] chrisXL:
The only app I don't receive notifications is XDA. LOL. But I think it's a app issue. The rear camera is ok, the front camera crash while taking a picture.

Edit: ... and lockscreen overlay issue while in charge (0409 build)
[Galaxy S II Android Development] Catscratch:
For me both cameras are working without problems. I'm on 0331 and using better camera app.
[Galaxy S II Android Development] Fasullo:
I'm using 07/04 build. Default camera app crashes when taking pictures with front camera.

With Camera Zoom Fx everything is OK...
[Galaxy S II Android Development] Andrea900:
What the heck! With "A better camera" i can select the front camera and everything is ok (exposure, hdr...). Rear camera is dead like before.
[Galaxy S II Android Development] pappy_034:
Based on your opinions and reports I can suppose that is currently the most stable build 0331 snapshot?
[Galaxy S II Android Development] Catscratch:
Yes. At least in my opinion.
[Galaxy S II Android Development] Sub_Zero2:
For those of you with camera issues, there are a couple of camera fixes scheduled for the next nightly according to the changelogs
[Galaxy S II Android Development] Draky50110:
My 2 cents test : using the 20160409, rear cam is ok taking picture but front cam craches. Back to rear cam takes picture so only taking pictures of me (AKA selfie :p) is a problem. Not a real one but I'm downloading today's nightly, will post my test, so you'll be afraid of my selfie :p
[Galaxy S II Android Development] wave41:
Front camera not working. cm-13.0-20160412-NIGHTLY-i9100.zip
[Galaxy S II Android Development] Draky50110:
Same here...
[Galaxy S II Android Development] SAMDestroy:
i can confirm front camera is not working cm-13.0-20160412-NIGHTLY-i9100.zip
[Galaxy S II Android Development] rogers11:
Both cameras work for me with Open Camera on 12/4.
[Galaxy S II Android Development] ajislav:
Users with working front camera, can you please post the build you are using, so that the regression can be traced?
[Galaxy S II Android Development] Draky50110:
Not working with 20160407.
[Galaxy S II Android Development] Drx86:
I remember that front camera used to work with build 0310. The next build I flashed was 0331, and front camera did not work with that build (and still doesn't).

However the problem is just with stock camera app, Google Camera and other camera apps work fine.
[Galaxy S II Android Development] cdzo72:
[MENTION=3826867]cdzo72[/MENTION]

normally flashing a 2nd time fixes those problems.

Fixing root in recovery (upon the request that you missed) is not working for Marshmallow.

Recently there were builds where root didn't work. But if I remember right, that was on march 23rd and 24th nightlies.[/QUOTE]

I flashed another ROM... an AOKP ROM and it gave me back root... then flashed the CM13 again and I have root.

But there are other issues that have to do with access to the SD cards... the music app is unable to see the music on my storage and the gallery will not show my pics. 3rd party apps for both work just fine.
[Galaxy S II Android Development] wdevil12:
When [MENTION=6159291]Lysergic Acid[/MENTION] isn't here, everything gets really messed up..
[Galaxy S II Android Development] Sub_Zero2:
Hello all!! I've done some digging again, and this time we might actually be closer to a solution!

I did some decompressing of nightlies: cm-12.1 latest snapshot, cm-13 next-latest nightly for i9300, and cm-13 next-latest nightly for i9100. I found that 1 drm file is missing from the i9100 build compared to the i9300 build, this file: /system/vendor/lib/mediadrm/libwvdrmengine.so ...

Not that exactly that matters, if the next thing i discovered in the i9300 thread when asking around, matters. Someone gave me a link to commits supposedly fixing the exact same problem on galaxy tab 3 (also exynos 4?, ofcourse!) : http://review.cyanogenmod.org/#/c/137230/ .... Seems this is the real problem we're facing? If so, then the dev could probably fix it! This is quoted from the commit description:
[Galaxy S II Android Development] piddy2:
error when typing number in phone/call a number

Hi

First thanks for all the hard work on this rom. I have experienced an error on this release 12/4 and 09/4. When I change the DPI settings for the screen from default (240) to 180 and after the restart when I try type a number to call a person the phone shuts down the call. It makes a 2 sec "error" sound if that makes sense and then goes back to the home screen. When I change DPI back to 240 and after the phone restarts the call function is working again. no problems.

I hope this can be fixed because it's a real deal breaker for me not being able to "see so much on the screen".

Thanks again for all the help.
[Galaxy S II Android Development] itsmyname:
Why is my battery draining so fast? 3% every minute of screen on time
[Galaxy S II Android Development] daniu:
Do the following:

*Turn your phone to airplane mode (not sure that is really necessary but ot won't harm)

*shut the phone down

*remove the battery for 10min

*put it back in, boot and turn off airplane mode

If that does not help: install betterbatterystats and find the reason

Sent from my x-phone using brain 2.0
[Galaxy S II Android Development] Boolian:
Just checked since it's being reported.

Stock camera (front) not working on 20160329

Shows image but "Can't connect to camera" error on press.

Open Camera works OK.
[Galaxy S II Android Development] henrryxda:
Front camera not working. cm-13.0-20160413-NIGHTLY-i9100.zip
[Galaxy S II Android Development] pappy_034:
In your opinion what is the best build that gives best battery life because it sucks on this newer builds?
[Galaxy S II Android Development] Draky50110:
I don't have any problem with last nightly.
[Galaxy S II Android Development] Sub_Zero2:
[MENTION=6159291]Lysergic Acid[/MENTION] : I hope you can fix this for us ☺it seems it would fix the netflix issue and issues with other videos using those color schemes