yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] :
Security Update

In http://charlesingo.mine.nu/ftp/nvertigo/ you find a new build (20150307) and a md5 file. This contains a fix for FREAK security hole. Though it contains all upstream commits till today 13:00 h UTC, I recommend this one only if you use the aosp browser - for users of chrome or firefox it is not mandatory, 'cause these browsers are safe.

No announcement and chanlog - to tired and lazy.

Happy flashing!
[Galaxy Tab S Android Development] touchee:
Checked and I had 8 hard links. Did a dd install of twrp-2.4.8.0 and it seemed to go ok, but didn't work upon reboot. Now can't get beyond the downloader screen, so no recovery or rom. Tried heimdall to flash a recovery but problems (think possibly heimdall not working, though it's the latest version). Will try to find a windows machine and get a v3.10 odin to try and get twrp on there. Does that sound like a possible way forward? What a saga, lol.
[Galaxy Tab S Android Development] mx900:
You were right. It was SELinux.

In order to make Xposed work, I installed SELinux Mode Changer and changed the mode to Permissive. Xposed was working fine.

Came here, saw your reply mentioning to change the mode to permissive. As it was already on permissive, I tested copying file and it worked! I have attached the dmesg.log. Thank you again!
[Galaxy Tab S Android Development] :
From the download mode screen press home, vol down and power. As soon as screen went black (really immediatly!), change from vol down to vol up. Then you are back to recovery.

Only flash rom, pa gapps pico and SuperSu. Something seems to mess up your installation.
[Galaxy Tab S Android Development] :
Thank you. But would you be so kind to follow EXACTLY my instructions? The first line of your log says:

[L0: toolbox: 15152] audit: rate limit exceeded

But audit log is exactly what I need to see. Therefor it is mandatory to do the reboot and start as less processes as possible to get the fu***** audit logging.
[Galaxy Tab S Android Development] touchee:
Had already tried that but I think I'd messed up recovery partition on the tablet previously in the dd step! Finally got odin and drivers on a Windows machine and flashed twrp-2.8.4.0 ok. Reflashed rom and gapps and everything working first time. So some issue with philz recovery apparently. Wierd though as I then checked the WiFi folder and the same 8 links were there as were there with philz.
[Galaxy Tab S Android Development] :
Hmm, very unlikley, if the symlinks were present philz is NOT the problem - therefor I instructed you only to change recovery, if they were NOT present. You wrote, that wifi was working after flashing with twrp, but on reboot something was broken. So I take a bet, that the breakage occured between first boot of rom and next boot. Ask yourself, what that could be: installs, restoring of apps and/or data, flashing something... Thats the reason, why I tell people to repprt an issue they should do a "clean flash" (as described in posting #2), and only flash pa gapps pico and SuperSU.
[Galaxy Tab S Android Development] reubenskelly1992:
Anyone else notice lag after latest build. 7/3 one
[Galaxy Tab S Android Development] Zootopia:
Nope.

Running stable and snappy as before, if not better.

Perfection over perfection, cortesy of NVertigo. ?
[Galaxy Tab S Android Development] reubenskelly1992:
Hmmm weird. Laggy for me dirty flash. Will I investigate what's causing it my side
[Galaxy Tab S Android Development] zombolt:
Yeah it's been lagging and freezing a lot all of a sudden. Might wipe and refresh and see if that fixes it
[Galaxy Tab S Android Development] :
I neither recommend a clean flash nor a dirty flash. As stated many times: if coming from a dirty flash and having issues, always do a clean flash, install/flash only gapps (ps pico) and SuperSU and provide logs (see also posting #3).

On lagging you can additionally look for a bad behaving, resource consuming app: if lagging occurs you can search with i.e. timeline if an app is using lots of cpu time.

If device freezes reboot directliy to rom (do not boot to recovery) and copy /proc/last_kmsg to a directory of your choice and provide that log.

Before reporting an issue read and follow posting #3. Without logs and a description on how to reproduce an issue, any debugging attempt is senseless. This is especially true on issues, that are expirienced only with single installations.

cm12 is still heavy WIP. Including frameworks and settings. Depending on the combination of your settings a dirty flash my work or not.

A side note on xposed: I don't want to discourage anybody to use xposed. But keep in mind, xppsed replaces framworks, art-compiler (jave runtime environment) and some system libraries. After installing xposed (which is considered alpha by the author) you DO NOT HAVE nvertigo/cm12 any longer, but something different. Any issues evolving with xposed installed should be reported and discussed in xposed thread.

It is important when reporting an rom issue to do a clean install with only gapps and SuperSU installed, to be sure to not suffer from any side effects.

Also quite some apps are not adapted for L and/or cm12: this can also give some strange side effects.

BTW: it would be very useful, if clean flash resolves some wired phenomens, to report that to help other users with similar expiriences.
[Galaxy Tab S Android Development] nikolasmar:
hi, will this work on T700?

Thanks
[Galaxy Tab S Android Development] :
No. But [MENTION=2346758]eousphoros[/MENTION] is making cm12 for klimtwifi.
[Galaxy Tab S Android Development] reubenskelly1992:
Mines fine now after doing a clean flash:)
[Galaxy Tab S Android Development] heatfire:
This rom is so stable its crazy.

i flashed it with the CM12 gapps i found on cyanogenmods page, works nicely.
[Galaxy Tab S Android Development] :
Thanx for reminding me of cm12 gapps. Of course they work. The reason why I recommend pa pico is this:

Providing a custom rom - particulary a source open, aosp based one - is about the freedom of choice for the users. The pa pico is very minimal and basic, so the user has the choice to install from playstore what he wants and what he does not want. I don't recommend pa pico 'cause it's "better" in any technical way. It's all about the freedom of choice.

OT: regarding this freedom of choice, I like having as much as possible source build roms around. It makes me feel sad, that no one jumps in for bliss. If anybody here wants to continue the work of [MENTION=2779578]jewnersey[/MENTION] and has basic knowledge on building aosp/cm from source, I would be glad to support him as much as my time allows.

For political correctness and gender mainstreaming:

sed 's#he#she/he#g'
[Galaxy Tab S Android Development] :
New Build in OP

Build 20150310

fix vulnerability to FREAK attack in Browser.apk. Until cm (there are curtently two diffrent suggestions in gerrit to fix this) commits a fix, every rom builder can do this before brunching:

pushd external/chromium_org/third_party/openssl
git fetch http://review.cyanogenmod.org/CyanogenMod/android_external_chromium_org_third_party_openssl refs/changes/39/90739/1 && git cherry-pick FETCH_HEAD
popd

kernel: gone back a few steps (for details see git). After patching kernel to 3.4.106 and applying some additional commits, I hoped increasing speed and decreseaing battary usage, I realized in many loading cycles, that one or some of the additional commits slightly decrease battery life (the opposide of my intention) - so I removed them again. Sadly I have not the time to examine, which commit really did the bad. I will push the questionable commits in branch "questionable". Everybody can test which commit is the culprit patch. My gut feeling suggests the "squash 'enhanced power efficiency' patch" commit. I would be very thankful for help on testing, 'cause it's very time consuming. You need AT LEAST two complete recharging cycles to make an educated decission. Thanx in advance.

UMS mode: fix write acces to device.

ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150310-UNOFFICIAL-nvertigo-chagallwifi.zip

MD5: 77cc7bc67818f1251dcf295482fddd65

Happy flashing!
[Galaxy Tab S Android Development] Hannibal226:
Mirrors coming tomorrow...
[Galaxy Tab S Android Development] :
Do NOT feel any timely preasure - I'm thankful for your regular mirroring, it does not depend on time!

OT: I love the second last line of your sig.
[Galaxy Tab S Android Development] Bushcrafter:
[MENTION=4405529]nvertigo67[/MENTION]. I seem to be having a problem with setting up my email account with the new build. I'm using the my email app

From the play store. I have two emails, both with gmail accounts. I can sign into one account but as soon as I try too sign in on my other account the tab auto shuts down. This never happened with the last build. I'm attaching a logcat and I'm hoping you can tell me if it is the new build or not.:D

Thanks in advance!:good:
[Galaxy Tab S Android Development] maxal:
Have you tried using the new inbox app for Gmail, works ok for me.
[Galaxy Tab S Android Development] :
I need logging from the autoshutdown... ;) Not that diffecult as it seems: start logcat without -d option and redirect. In a terminal:

su
logcat >/path/to/logfile.txt

Tuen go and crash you tab... ;)

If you have done so, sorry. I can look at the log tomorrow.
[Galaxy Tab S Android Development] :
My tab wasn't going to deep sleep after latest flash. Reason was a wakelock from CMUpdater.

To solve this, go to Settings->tablet->Updates, set to manual (if you have done so, set it to daily, leave settings [back,back,back,back], go there again and set it to manual again. Then initiate a manual search and leqve Settings again.
[Galaxy Tab S Android Development] Bushcrafter:
Okay I will redo it and re crash my tab:D

When ever you get a chance to look at it would be great.:good: I have a backup of my last build to use in the mean time.;)

---------- Post added at 02:23 PM ---------- Previous post was at 02:22 PM ----------

Thanks for the heads up.:good:
[Galaxy Tab S Android Development] Bushcrafter:
[MENTION=4405529]nvertigo67[/MENTION]. Okay I tryed it again and I'm not sure if I did it right or not. Here is another zip of my logcat.:)

A 54 old NOOBIE at his finest!
[Galaxy Tab S Android Development] Bushcrafter:
No I have not but I will give it a try.:)
[Galaxy Tab S Android Development] :
I can't see a bad crash, segafault or intended shutdown. So I have no clue whats going on. :( The last actions before the log stops regards to a theme and mali.

What you should try: clean flash and only flash/install gapps amd SuperSU. Get your email app from playstore and try it without any other app - and without any theme - installed....
[Galaxy Tab S Android Development] :
Thank you.

Added to OP.
[Galaxy Tab S Android Development] Hannibal226:
U don't need to change OP always again.

Maybe u name the mirros itself in OP as they r general,

so no updates necessary.

CHEERS!
[Galaxy Tab S Android Development] :
Was working for me yesterday on a selinux test build. Are you using branch cm-12.0?
[Galaxy Tab S Android Development] lionheartk:
Oh, I installed the latest 1.23 busybox. That may have caused the problem. WIll look into it to see what happened and will report back :)

---------- Post added at 09:58 AM ---------- Previous post was at 09:56 AM ----------

For vendor and device yes, for the kernel Im using cm12-sh.

Here's what happens:

zero@ubuntu:~/android/system/repackrom-master$ ./repack.sh rom23.zip

Archive: rom23.zip

signed by SignApk

inflating: META-INF/com/google/android/updater-script

patching file META-INF/com/google/android/updater-script

Hunk #1 FAILED at 138.

1 out of 1 hunk FAILED -- saving rejects to file META-INF/com/google/android/updater-script.rej

adding: META-INF/com/google/android/updater-script (deflated 66%)

zero@ubuntu:~/android/system/repackrom-master$

Just compiled this rom today, using vendor and device cm12 and kernel cm12-sh repo synched couple hours ago.
[Galaxy Tab S Android Development] :
I'm talking about repackrom...

For device and kernel I try to keep cm-12.0mand cm-12.0-sh clean for you and develop on 12-work branches.
[Galaxy Tab S Android Development] :
gps is definetly an selinux issue.

Workauround without reboot: in a root shell type

setenforce 0

BTW: Can anyone confirm camera is working?
[Galaxy Tab S Android Development] :
AGain: use cm-12.0 branch of repackrom, please. Just ochecked and it IS working. Belive my: use cm-12.0 branch and you get the working patch file...
[Galaxy Tab S Android Development] maxal:
Hi, yes camera is working.:good:
[Galaxy Tab S Android Development] lionheartk:
uh right sorry was using master branch it seems. Sorry!!!!!!! I'm a idiot...

Yep camera is working perfectly!
[Galaxy Tab S Android Development] :
Go to your local clone of my devive git. git fetch the whole repo - not only cm-12.0. Type

git log|grep -i derp|wc -l

and you get a rough estimate how often I was an idiot only on developing chagallwifi. ;)

BTW: if your build systemui crashes, dom't spend 5 h on hunting down like me (add one to above number... ;) ), seems to be introduced upstream with the lockscreen shortcut commits.

[MENTION=535343]all[/MENTION]: I'm still struggling to allow gpsd to handle its own lockfile... the L way of selinux sucks... :( The path for the named pipes were wrong. Fixed that, added .gpsd.lock: errors for pipes has gone; errors for lock file persists... Look in branch 12-work if you are familar with selinux.
[Galaxy Tab S Android Development] lionheartk:
Haha yeah I already did, just to check cyanogen commits a few minutes ago and see that they fixed it already. Was a derp on the system ui status bar MSIM.

Building another...
[Galaxy Tab S Android Development] :
I'm sick of the selinux stuff. I will try to make a permissive build in the 12-work branches...
[Galaxy Tab S Android Development] barth2:
Camera is working fine on my T800. Both front and rear. No FC.

Notably, video is working WITHOUT disabling HW overlay. No video artifacts when changing orientation. These were problems in earlier cm12 builds.

As noted in OP, install flashable zip of SuperSU to get titanium backup working properly. [emoji106]

Themes, yay!!

Only issue I have not seen reported is none of my audio equalizer apps are working. AudioFX works but only for the built in Music app, not for general apps, eg Pandora or Pocket Casts. Kind of a bummer for me because I hate how tinny the speakers sound without bass boosting.

Otherwise, This is a terrific and stable ROM. Thank you!!!

[emoji106] [emoji106] [emoji106]
[Galaxy Tab S Android Development] lionheartk:
I think everyone here would be ok with a permissive build?
[Galaxy Tab S Android Development] :
Systemui crash is fixed upstream (http://review.cyanogenmod.org/#/c/86603/).

I managed to make a permissive build. Which fixed gps as well as init.d as expected. This is no solition. This is even not a workaround - this is just crap. But: it works for now. I don't now how many security holes I opened with this (feels like opening Pandorra's box. So be carefull what apps you install with a permissive build.

I worked on selinux now for over 26 hours with little sleep, so I would like to come back to your offer, [MENTION=1409248]lionheartk[/MENTION], to make a build and an upload. For device and kernel use branches 12-work, for vendor cm-12.0. Take a look at this patch:

diff --git a/vendor/cm/config/common.mk b/vendor/cm/config/common.mk
index 96f459f..16935bc 100644
--- a/vendor/cm/config/common.mk
+++ b/vendor/cm/config/common.mk
@@ -258,7 +258,7 @@ ifdef CM_BUILDTYPE
else
# If CM_BUILDTYPE is not defined, set to UNOFFICIAL
CM_BUILDTYPE := UNOFFICIAL
- CM_EXTRAVERSION :=
+ CM_EXTRAVERSION := -nvertigo
endif

ifeq ($(CM_BUILDTYPE), UNOFFICIAL)

I would suggest you put "-lionheartk" there, so we can easily tell the different builds. Thanx in advance.

Priorities for the next week(s):

Fix selinux finally

Fix netflix

Fix move to sdcard (says: not enough space, though there is)

1000 issues I have forgotten + 1001 issues you tell me... ;)

[MENTION=535343]all[/MENTION] the themers, that want the newest theme engine: please make a dark theme. I personally dislike the new everything white look.

Good night all together & have a nice flashing/testing weekend. Don't forget your beloved... ;)

Nvertigo
[Galaxy Tab S Android Development] Jacob_Bentzen:
Hope it will come to the SM-T805 :)
[Galaxy Tab S Android Development] barth2:
[MENTION=4405529]nvertigo67[/MENTION]

Have a look at the mega CM12 theme thread

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

There are several dark themes. Though they're all a little buggy and inconsistent at the moment.
[Galaxy Tab S Android Development] jewnersey:
just to clarify. the camera and video fixes were on CM side? so simply resyncing and rebuilding should eliminate those issues? I don't see any specific work on these in your repos so I am guessing it's that simple.
[Galaxy Tab S Android Development] :
As gar as I can tell camera was always working on my trys to build cm12. I have tried to find and look atyour device and vendor gits, but didn't found them. If you look at my devive git, you see that I worked my way up from a working cm11 version and merged most of the commots from picasso wifi (had to resolve some comflicts due to the differences in cm11 base). Only change to vendor was taking the hexedited lib_GLES_maili, keeping all camera related blobs to our original t800 sammy blobs (including the renamed camera[.vendor].exynos5420.so to have the from cm source builded camera.exynos5420.so with the changes in device git from crpalmer not overwritten). So I don't think there was an upstream fix since Monday at least.

I would really like to have a look at your vendor- and device-git regarding sepolicy (I haze it in L!) and ppwered off charging.

Good luck.
[Galaxy Tab S Android Development] :
I wil NOT build for chagalllte. I only build for devices I have my hands on. Sorry.
[Galaxy Tab S Android Development] :
Works for cm11 - but I have read on other threads, that this doeas not work on cm12. But I have not tested myself, so I would suggest: nandroid, try, report back.
[Galaxy Tab S Android Development] :
Yes, I know the directory structure of your mirros, and I had thought of your sugestion before. But I'm afraid of the possible resulting confusion, if I put up a new build and your mirror is not current. So I decided to put the mirror link in the build announcment, when I het your confirmation, trying to keep it as simple and confusionless as possible for the users.

(I bet at least half of the users wouldn't check the filename...)

But thank you for trying to reduce the time I spent on this!
[Galaxy Tab S Android Development] Bushcrafter:
Thanks a lot nvertigo,I will give that a try.:good:

Update: I removed both themes that I had installed and rebooted. Then I tryed my email again and it works perfectly. Thanks again nvertigo for the tip about the themes. You the best!
[Galaxy Tab S Android Development] :
...gimme logfiles - I eat them for breakfirst... :lol: glad to help.

Back to business. Notice to devs and homebuilders:

Fixes for FREAK vulnarability are commited to upstream. The cherry-pick I posted is not needed any longer.
[Galaxy Tab S Android Development] FearlessSpiff:
I cannot confirm that atm but will do more testing on this subject. For me it works flawlessly.

I flashed the ROM yesterday and I'm veeeerrryyy happy with it. Thanks [MENTION=3456089]nvertigo[/MENTION] for this.

Edit: Wow, even the Samsung Keyboard works. I'm able to select the right Keyboard Layout! :D Only Task Switcher doesn't do anything. But else even Brigthness, Loudness, Media keys are working. Great stuff!
[Galaxy Tab S Android Development] FearlessSpiff:
Is it normal that the capacitive buttons are lit as soon as I touch the screen? I didn't notice in the day, but now at night it is hurting my eyes. ;)

Edit: Found it under Settings -> Button -> Backlight

-> Perfect! I also enabled the onscreen navigation buttons as described in the workaround in the OP. And disabled the capacitive buttons as described there too. Only the Home button TODO. ;) But this one is ok to have. I don't hit it accidentaly also as the other two.

All in all the perfect "Nexus" experience now! :D
[Galaxy Tab S Android Development] :
I think a disabled home button is not possible: it's a gpio key (with different driver then the capacitive buttons). Disabling gpio keys would mean to disable power, vol-, vol+ and home, which would render the device quite useless... ;)

On cm capacitive keys are lit if screen is touched. I use capacitive keys with backlight disabled.
[Galaxy Tab S Android Development] lionheartk:
Hi Everyone! I'm back, and with the infamous Sex Build!

cm-12-20150313-UNOFFICIAL-lionheartk-chagallwifi.zip 238.2 MB

cm-12-20150313-UNOFFICIAL-lionheartk-chagallwifi.zip.md5sum 142 B

All commits from both Nvertigo and CM12 team since last Nvertigo release are included.

Dirty flashed and working!

Have fun!
[Galaxy Tab S Android Development] reubenskelly1992:
Welcome back!! Hero:)
[Galaxy Tab S Android Development] Bushcrafter:
Good too see you back!:good:
[Galaxy Tab S Android Development] FormeriPhoney:
Although it's 100% stable I'm so damn bored with the stock based roms I think I'm gonna give this a run.
[Galaxy Tab S Android Development] reubenskelly1992:
I would. And the theme engine is very good. A lot of themes
[Galaxy Tab S Android Development] barth2:
Welcome back. Seems like it's been ages since we had Sex :)
[Galaxy Tab S Android Development] FormeriPhoney:
I guess there are a lot more compatible themes as of late. I have only used the RRO layer themes which I absolutely love.

Which ones are you guys using? I like a dark themed to take advantage of the amoled.
[Galaxy Tab S Android Development] reubenskelly1992:
Deepdarknrss is great. Flux. There's loads mate take a browse on play store
[Galaxy Tab S Android Development] FormeriPhoney:
That's great man. Thanks.

Is anyone running the new xposed module? Only thing I'd really be interested in is YouTube AdAway. Those drive me up a wall.
[Galaxy Tab S Android Development] reubenskelly1992:
Yeah I ran it. No problems what so ever. Alpha 2 great:)
[Galaxy Tab S Android Development] :
Just rememner before repprting issues after installing xposed to do an clean flash WITHOUT installing xposed and reproduce the problem.

For themes: we had latlely an issue, that an email app was crashing the rom, when themes was used.

If you are looking for 100% stable - as you wrote - reconsider, if using a beta status rom with xposed (alpha status) and themes is really your way...
[Galaxy Tab S Android Development] FormeriPhoney:
Yes.. I know. I always run the rom for a few days as is to find seek out any issues.

If a theme or xposed caused issues I'd uninstall it. I'd rather have a stable build than a few modules
[Galaxy Tab S Android Development] FormeriPhoney:
Been a few hours and the sex build is pure.... Well sex.

Trying out Euphoria dark theme. No issues so far.
[Galaxy Tab S Android Development] DUHAsianSKILLZ:
Been a while since you had lollipop :) Yeah everything works including and battery is amazing! On standby it never dies (like really!)
[Galaxy Tab S Android Development] FormeriPhoney:
Yup.. Haven't used LP since bliss pop.

Only annoyance I've found is my videos played choppy until I switch from h/W to s/W decoding. Didn't have that issue on Iron rom (using MXplayer & vlc)