yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] the Doctor:
I did that. It was the last thing I did the first time I tried getting a logcat for 11/30 because I know the drill. I just redid everything with the same result. On boot, I get "XXXXXXXXXXXXX device" in 11/27. After wiping and flashing 11/30, I get "XXXXXXXXXXXXX unauthorized". What now? :confused:

--------------

Edit:

Doubting myself, I restored back to 11/27 again, removed all authorizations, re-authorized my laptop, re-wiped, re-flashed 11/30 and adb devices still returned unauthorized.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
Interesting. That probably means that userdata is not getting mounted (which is not what I expected). I'll have to look at it some more and get another test build up, probably tomorrow.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
Oh, and thanks a lot for testing (and the other people also testing it for me)!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] the Doctor:
NP. I'll try the next one as soon as it's available and I'm conscious (I'm 12 hours of of EST).
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Alexey71:
Yep. Build 11.30 bootloop and adb not work
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] arrrghhh:
How 'bout building with -eng [MENTION=3857343]crpalmer[/MENTION]?

Also, do you no longer have the 320? :p

I'm going to try building with the new SELinux stuff, I haven't tried with it enforcing yet myself...
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
I think that they are being built as -eng, but I guess I never double checked.

I still have the mondrianwifi. I"m flashing each of these builds before posting them and they are all fine on my device. Trying to figure out something that affects some devices (apparently a lot of ours) which seems to be msm8974 bootloader related (same thing on hlte and klte). It's very painful when you can't reproduce the problem....
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
And, here's another build to try. Please let me know whether or not it boots for you (if it boots, do please let me know):

http://download.crpalmer.org/downloads/cm-12-20141130-UNOFFICIAL-mondrianwifi-revert.zip
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] arrrghhh:
Ah no worries. I apologize, I've just been running my own builds. Let me try yours, although I doubt there's a difference.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Alexey71:
Works.

Micro SD exFat 64gb does not mount:(
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] arrrghhh:
I don't use exFAT myself, but as you know you should post logs with issue reports ;)
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Alexey71:
you use fat32 64gb?)
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
exfat support probably hasn't been added back yet. I haven't checked recently but early on it was definitely missing from vold/fuse drivers.

Can you check something for me now that it's booting? Can you run:

adb shell su -c "umount /efs"

adb shell su -c "e2fsck /dev/block/platform/msm_sdcc.1/by-name/efs"

adb reboot

and then send me the output? (the reboot is the easiest way to make sure /efs gets remounted correctly)
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Alexey71:
I will not lose the data on the card?

C:\android-sdk-windows\platform-tools>adb shell su -c "umount /efs"
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

C:\android-sdk-windows\platform-tools>adb shell su -c "e2fsck /dev/block/platform/msm_sdcc.1/by-name/efs"
e2fsck 1.42.9 (28-Dec-2013)
/dev/block/platform/msm_sdcc.1/by-name/efs: clean, 79/896 files, 1156/3584 blocks

C:\android-sdk-windows\platform-tools>adb reboot

C:\android-sdk-windows\platform-tools>

C:\android-sdk-windows\platform-tools>adb shell
shell@mondrianwifi:/ $ su
su
root@mondrianwifi:/ # mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=921936k,nr_inodes=81577,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=921936k,nr_inodes=81577,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=921936k,nr_inodes=81577,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=921936k,nr_inodes=81577,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0

/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/apnhlos /firmware vfat ro,relatime,uid=1000,gid=1026,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=rem
ount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware-modem vfat ro,relatime,uid=1000,gid=1026,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors
=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/fuse /mnt/shell/container fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=1000,default_permissions,allow_other 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
root@mondrianwifi:/ #

View attachment 3041378

Not mount my card
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] arrrghhh:
Ya, I don't have any individual files over 4gb and I prefer the compatibility of FAT32 personally.

e2fsck should not cause any data loss. Besides, that partition doesn't have anything to do with your SD card.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
Sorry for the confusion. The two things were unrelated I think the exfat requires changes across all devices before it will work and therefore I haven't been looking at it. There is still a ton of cm improvements that need to be ported to cm-12.0 and I think that is one of them.

The e2fsck was to test a theory I had about why your device wouldn't boot and mine would. Thanks to the output, I know that my theory was incorrect. Thanks for checking for me!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] lexusisf:
Whats the best way to root this device with cm 12? I want to get mother of all ad blocker and have root access to es file manager.

Thanks in advance
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] arrrghhh:
SU should now be built-in... Otherwise you can get Chainfire's SuperSU from the Play Store I spose?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] brakke97:
Everything runs pretty well. The only thing I don't like that much is the 400 dpi instead of the 320 dpi. Anyways, great job!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] arrrghhh:
[MENTION=3857343]crpalmer[/MENTION] - I can confirm the bootloop actually with SELinux enforcing.

http://hastebin.com/axorenaver.avrasm

Building with those other patches now. I didn't want to jump in on that gerrit madness...
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] tmacgarris6727:
any video of the tab running this rom
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] arrrghhh:
I'm sorry what does this have to do with development?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] tmacgarris6727:
wanted to see how it runs on the pro and to see if any one took any videos of it is that a crime ?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] scottharris4:
ANy idea when the DRM will be fixed? Not being able to use Netflix and the like is a pretty big deal
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] milkk:
You're asking that in the wrong thread this is for development only ask that in Q&A or General.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] wmc90:
Wifi appears broken in the latest build (1130-revert) - what logs do you need pulled or can you reproduce this one?

EDIT: Hmm looks like the updater script is failing

~~

mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Device or resource busy

script succeeded: result was [0.200000]

~~

If I flash it again the mount fail goes away but the script succeeded message remains; it appears random apps in /app/data also don't work.

If I dirty flash back to 27 (after wiping /system) it's all back to normal. - nope, tried with CWM and no change

Using TWRP... which is probably the issue?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Airtioteclint:
Wifi is working for me. I came from another aosp rom.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] amityg:
I have working WiFi!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] arrrghhh:
[MENTION=3857343]crpalmer[/MENTION], I seem to be having issues with selinux even after your patches...

I made it permissive, here is the audit log:

http://hastebin.com/zironimuqu.rb

cat /proc/kmsg |grep -i 'denied':

<4>[ 10.660973] type=1400 audit(1412309395.830:15): avc: denied { getattr } for pid=244 comm="installd" path="/data/media/0" dev="mmcblk0p26" ino=260621 scontext=u:r:installd:s0 tcontext=u:object_r:media_data_file:s0 tclass=dir
<4>[ 19.476516] type=1400 audit(1356998975.919:121): avc: denied { getattr } for pid=268 comm="sdcard" path="/data/media" dev="mmcblk0p26" ino=260609 scontext=u:r:sdcardd:s0 tcontext=u:object_r:media_data_file:s0 tclass=dir
<4>[ 19.630456] type=1400 audit(1356998976.069:141): avc: denied { read } for pid=268 comm="sdcard" name="albumthumbs" dev="mmcblk0p26" ino=260942 scontext=u:r:sdcardd:s0 tcontext=u:object_r:media_data_file:s0 tclass=dir
<4>[ 19.630670] type=1400 audit(1356998976.069:141): avc: denied { open } for pid=268 comm="sdcard" name="albumthumbs" dev="mmcblk0p26" ino=260942 scontext=u:r:sdcardd:s0 tcontext=u:object_r:media_data_file:s0 tclass=dir
<4>[ 20.315676] type=1400 audit(1356998976.749:165): avc: denied { getattr } for pid=268 comm="sdcard" path="/data/media/0" dev="mmcblk0p26" ino=260621 scontext=u:r:sdcardd:s0 tcontext=u:object_r:media_data_file:s0 tclass=dir
<4>[ 22.491396] type=1400 audit(1356998978.929:166): avc: denied { getattr } for pid=268 comm="sdcard" path="/data/media/0/Android/data/com.andrew.apollo/cache/ImageCache/journal" dev="mmcblk0p26" ino=261012 scontext=u:r:sdcardd:s0 tcontext=u:object_r:media_data_file:s0 tclass=file
<4>[ 22.492213] type=1400 audit(1356998978.929:167): avc: denied { read } for pid=269 comm="sdcard" name="journal" dev="mmcblk0p26" ino=261012 scontext=u:r:sdcardd:s0 tcontext=u:object_r:media_data_file:s0 tclass=file
<4>[ 22.492498] type=1400 audit(1356998978.929:167): avc: denied { open } for pid=269 comm="sdcard" name="journal" dev="mmcblk0p26" ino=261012 scontext=u:r:sdcardd:s0 tcontext=u:object_r:media_data_file:s0 tclass=file
<4>[ 22.493328] type=1400 audit(1356998978.929:168): avc: denied { read } for pid=268 comm="sdcard" name="ImageCache" dev="mmcblk0p26" ino=261011 scontext=u:r:sdcardd:s0 tcontext=u:object_r:media_data_file:s0 tclass=dir
<4>[ 22.493502] type=1400 audit(1356998978.929:168): avc: denied { open } for pid=268 comm="sdcard" name="ImageCache" dev="mmcblk0p26" ino=261011 scontext=u:r:sdcardd:s0 tcontext=u:object_r:media_data_file:s0 tclass=dir
<4>[ 22.494270] type=1400 audit(1356998978.929:169): avc: denied { append } for pid=269 comm="sdcard" name="journal" dev="mmcblk0p26" ino=261012 scontext=u:r:sdcardd:s0 tcontext=u:object_r:media_data_file:s0 tclass=file
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] the Doctor:
Please read the OP. I think you missed something.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] scottharris4:
Yeah, no I didn't. The OP says
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] lexusisf:
In 2 weeks
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] the Doctor:
And this:
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
I've updated the title and the OP because I've added nightly builds to my auto-build server for this. You can always find the latest successful build at:

http://download.crpalmer.org/nightlies/mondrianwifi

This means that you need to look if you want a newer build, I won't be announcing them here...
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Alexey71:
thx crpalmer

Oh, waiting for the support exfat. And put the firmware)
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] the Doctor:
No go on cm-12-20141201-UNOFFICIAL-mondrianwifi.zip. Not only does it fail to boot, but unlike yesterday I can't even get my computer to recognize it.

Please don't put pressure on the devs. He knows you want exfat support and doesn't need any [not so] subtle reminders.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] hotshot2:
i just installed and works fine the first try just did a clean install and then installed gapps everything is working Thanks a Mill and keep up the good work
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Alexey71:
Works for me. Need wipe system-data-cache-dalvik
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
Did you find it yourself or download it after I posted? Earlier today there was a NAD build with the same name. The right build should be 225MB.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] arrrghhh:
Any ideas on my SELinux issues [MENTION=3857343]crpalmer[/MENTION]?

I wasn't able to boot unless I made SELinux permissive.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] the Doctor:
I downloaded from your link. I don't know what happened but I did get it to boot finally after a second try. It's late here and I'm tired, so I'll blame operator error.

Here's a logcat of the clean install w/ no gapps just did in case you're interested.

G'nite all!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
Was that on your build or my build (ideally today's nightly)? If it was your build, mind trying mine to see if you have the same problem?

I glanced at the log last night and nothing looked like it would make it not boot. But I only had time to glance so I may have missed something more serious...
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] arrrghhh:
No worries I'll give it another shot.

Those logs were from my build - I just made SELinux permissive so it would boot & I could get an audit log of what was being denied.

I did try your builds - the ones before SELinux enforcing were fine, after they would not boot. Same with my personal builds, unless I make it permissive. I have not tried your most recent nightly, will try this afternoon.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
If it doesn't boot, can you PM the output of ls -lR /data/. I definitely don't get those denials but I also don't think I have any music on my device so I'd like to see if I can reproduce the denials myself.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] brakke97:
I think this patch will help with exFAT. http://review.cyanogenmod.org/#/c/79877/
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] arrrghhh:
Still doesn't boot. I guess you want me to reboot into recovery & grab that? You're building userdebug (makes sense) because the device is offline:

adb devices
List of devices attached
10f7eaa60376db8e	offline
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] user91:
Hey guys! I do realise that this is an alpha build, but then I believe this to be a device-specific bug as I don't have such problem on my Nexus 4 running CM 12 builds.

Sliding the brightness slider completely to the left makes the screen go completely dark (i.e. black, as if it was turned off) in dark environment with adaptive brightness on. The reason why I know the screen is still on is that by blindly tapping for the brightness slider and sliding it right, the screen becomes visible again.

If there's anything I can help with to resolve the issue, please let me know.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Itzamistry:
Ik this is an alpha and am not sure if it is a known bug but the camera doesn't work at all. Ik the video recording doesn't work but you can't take pictures either? Thanks
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] wind0zer:
I installed each of these as a fresh rom

build of 27th - boots

build of 30th - stuck at boot animation

build of 1st - boots
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] daniel3ric:
Bonjour,

Same problem here. I have to put the device under bright light for the screen to turn on again. Nightly 01/12.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
Looks like a bunch of files are probably mislabeled, probably from running permissive and/or with older file_contexts. Can you try doing a factory reset? I would hope that will boot and then if it does run

restorecon -rvFD /data

which should hopefully be able to relabel the files on your sdcard. The sdcardd audit log denials look like they are all from mislabeled files. The mpdecison ones in your log were actually good ones (there's a file it creates once, which I guess I already had and therefore never saw the denial) so I'll fix that.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] arrrghhh:
I've done plenty of factory resets... In fact I do advanced wipes every time I flash, and I wipe every partition available except internal SD and external SD. So it wipes /data without removing /data/media...

Do you want me to blow away the internal SD and try booting?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] meko007:
Camera doesn't work in the latest nightly build 12\2 it says"unfortunately camera has stopped"
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
If you don't mind, that's probably the best option.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] arrrghhh:
Well damn, I only had one single music file on my internal SD... not much else other than some old empty folders.

But that seemed to do it. Odd. I am now running your latest CM12 build with SELinux enforcing, thanks.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
The state that you were in was odd. You had files that were labelled with a context that isn't actually defined by the file_contexts (aka, you couldn't have that label starting from the current rules). I think that includes /data/ which was what was causing the boot to fail. Hopefully that's just a result of running with older policies and permissive (which can jack up your contexts, apparently, or so sayeth arcee at one point).
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] brakke97:
The exFAT patch is now officialy merged. http://review.cyanogenmod.org/#/c/79877/
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Alexey71:
Cool. I hope in the new build add patch)
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] arrrghhh:
The 12/3 build (assuming it builds/uploads successfully) will have it.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Alexey71:
Build 12/03 - exFAT 64gb works. Tnx:good:

lol android 5.0.1?:D
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] iamnotkurtcobain:
Thanks
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] arrrghhh:
I didn't even look at the patch that closely, it was actually merged Dec 1...

Oh well, glad it's working for you!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] brakke97:
Christopher, why have you changed the DPI to 400? It looks to big and is for seniors :D. Would you mind to change it back to 320 DPI? It would enhance our user experience a lot.

Thanks in advance.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] arrrghhh:
From the commit:

mondrianwifi: Set lcd_density=400
This resolves various rendering issues.

I'm assuming it resolves rendering issues.

Edit - you can always adjust the build.prop setting yourself... although if 320 causes rendering issues, I wouldn't advise it.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] brakke97:
Will it be permanent?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] amityg:
You will adjust as you age!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] brakke97:
Hahahaha that's true.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] coolqf:
The tab pro is scheduled to receive lollipop by February, which leads me to assume that by March/April we should have an extremely stable lollipop release.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] KarlDag:
Currently installing today's build on my tablet, was running M11 before... Right now it's still installing my apps but it is HOT, really really hot... Never got this hot on stock ROM or CM11. Almost worried.... Otherwise seems to be working great.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Itzamistry:
Is the camera fixed yet?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] amityg:
Mine is not but I'm very patient
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
Today's nightly should have a fixed camera and DRM. Sadly, I fixed those a few days ago but my auto-build server wasn't setup correctly and wasn't using the right repo to be able to get those fixes. I believe that should be fixed now. Let me know if I still screwed it up and either camera or DRM isn't working.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] dr4stic:
That it did. Thank you :)

---------- Post added at 05:16 AM ---------- Previous post was at 04:50 AM ----------

crpalmer, question: On CM11 the home button used to wake the screen. The gpio-keys layout from your device repo has WAKE's on all the buttons, but for CM12 you removed the WAKE's from all the buttons.

I was wondering if you were thinking of bringing the functionality back? As an insomniac, I can understand the endless battle against the WAKE's , but I found the WAKE, at least on the home button, to be tremendously useful. It's an easier target to find in the dark, and it also helps to have a second way to re-animate the screen during various holding positions.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
I just posted a newer gapps package. I haven't tested it nearly as much as the original, but I do know that it fixes calendar sync and I would recommend using it:

http://download.crpalmer.org/downloads/gapps/unofficial/gapps-lp-20141122-signed.zip

The safest way to update a gapps package (especially when they aren't official!) is to wipe system, flash the ROM, flash the gapps.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] kingofcomedy:
Netflix is working now, thanks.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Veter0k:
crpalmer, can you build cm-12 for 325?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
Home button wake is general CM functionality. I think I saw that it was currently under review for CM 12. It should come back soon and is unrelated to the keylayouts where the WAKE flag was deprecated in android 5.0.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
Not right now. I will likely do it eventually but given that I don't own the device, it is low on my list of priorities. I haven't even touched sm-t525 yet and I own that tablet...
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] angry english:
Thanks for this, when i seen CM12 was available on the 8.4 i literally packed up my Nexus 9, sold it on Swappa and bought one of these for $199, no brainer.

So again thanks for your great work
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] KarlDag:
Using on-screen buttons I can't use the home button to power on the screen, which worked on CM11.

Works great otherwise.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] the Doctor:
Did you happen to read the OP or even the last few posts on this page?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] KarlDag:
I did when I left home, which was before 8am, which means all this hadn't been posted. Sorry I offended you.