Database Info

[Dev][Help] Camera Crash Radio 6.35

Ok so i've pretty much found the problem i just need some help finding the solution.
Ok so using my kernel i booted up on cursor's rom and then booted up on my super D rom and took an adb logcat of both starting up the camera. My kernel isn't the problem as it loaded cursors fine. I copied libhtc_acoustic, libcamera, libqcamera, and libcameraservice from cursors rom.
Ok so here's the difference in ADB logcat. Both roms make it to
Code:
V/QualcommCameraHardware( 41): setParameters: X mCameraState=1
fine but the next line the working one says
Code:
V/CameraThread( 491): START_PREVIEW - Camera setPreviewDisplay()
and the broken one says
Code:
V/camera ( 340): startPreview
i looked back and i found that the working one had a chunk of V/CameraThread's that the broken one didn't.
So basically i just need to figure out what file is missing that executes CameraThread (correct me if i'm wrong)
I've uploaded the logcat's if you're interested
OK so i tested with the libs from RA's rom (a donut rom for radio 6.22) and i the line that was broken in the other code seems to be working now. Could anyone running RA's rom post the logcat of them starting up the camera so i can compare? Uploading logcat now
looks like to me the problem with this one is caused by msm_camera
When it says no such file in /dev/etc. where is that? anyone know how i can take a look at that area of stuff?
Code:
E/QualcommCameraHardware( 56): startCamera X: /dev/msm_camera/control0 open failed: No such file or directory!
E/QualcommCameraHardware( 56): ioctl error. camfd=-1, type=21, length=4, rc=-1, ctrlCmd.status=49168, Bad file number
E/QualcommCameraHardware( 56): ioctl error. camfd=-1, type=15, length=4, rc=-1, ctrlCmd.status=49224, Bad file number
E/QualcommCameraHardware( 56): ioctl error. camfd=-1, type=14, length=4, rc=-1, ctrlCmd.status=49296, Bad file number
...
E/QualcommCameraHardware( 56): ioctl error. camfd=-1, type=21, length=4, rc=-1, ctrlCmd.status=50224, Bad file number
E/QualcommCameraHardware( 56): ioctl error. camfd=-1, type=15, length=4, rc=-1, ctrlCmd.status=50416, Bad file number
E/QualcommCameraHardware( 56): ioctl error. camfd=-1, type=14, length=4, rc=-1, ctrlCmd.status=50352, Bad file number
...
E/QualcommCameraHardware( 56): register_buf: MSM_CAM_IOCTL_(UN)REGISTER_PMEM fd -1 error Bad file number
E/QualcommCameraHardware( 56): register_buf: MSM_CAM_IOCTL_(UN)REGISTER_PMEM fd -1 error Bad file number
E/QualcommCameraHardware( 56): register_buf: MSM_CAM_IOCTL_(UN)REGISTER_PMEM fd -1 error Bad file number
E/QualcommCameraHardware( 56): register_buf: MSM_CAM_IOCTL_(UN)REGISTER_PMEM fd -1 error Bad file number
E/QualcommCameraHardware( 56): ioctl error. camfd=-1, type=1, length=28, rc=-1, ctrlCmd.status=13297, Bad file number
E/QualcommCameraHardware( 56): startPreview X initPreview failed. Not starting preview.
Thanks for your time
Sphaerophoria

Maybe sanpei could help with this. He was able to make the camera work on 6.35 radio.

did some hard searching and still no luck... i'm sure it's not a kernel problem as i tested it with other working kernels out there any chance that it could be some other file located around the system somewhere?

See, I got thinking that maybe there is some file that is specific to 32A roms that seems to make the camera work, since roms built from the AOSP (Sanpei's) or dumped from 32A models (Fender) seem to have no problem.
I'm beginning to think maybe there is more to porting that we originally thought.

skittleguy said:
See, I got thinking that maybe there is some file that is specific to 32A roms that seems to make the camera work, since roms built from the AOSP (Sanpei's) or dumped from 32A models (Fender) seem to have no problem.
I'm beginning to think maybe there is more to porting that we originally thought.
Click to expand...
Click to collapse
Ya i saw that post but didn't know how to contribute sorry ya i tried to replace the camera libs with the one from the fender but it didn't boot... maybe i'll try that again and look at the logcat's properly... i know that's not really what you were telling me to do but it just sparked my mind

same error... that's a shame

[Q] IPSEC on Gen8

Hello,
i'm trying urukdroid 0.5 and i can not use ipsec/l2tp with it
logcat say :
...
E/racoon ( 1972): libipsec failed pfkey open: Operation not permitted
I/racoon ( 1972): initiate new phase 2 negotiation: 192.168.0.200[4500]<=>192.168.0.10[4500]
I/racoon ( 1972): NAT detected -> UDP encapsulation (ENC_MODE 2->4).
I/racoon ( 1972): Adjusting my encmode UDP-Transport->Transport
I/racoon ( 1972): Adjusting peer's encmode UDP-Transport(4)->Transport(2)
E/racoon ( 1972): pfkey UPDATE failed: Function not implemented
E/racoon ( 1972): pfkey ADD failed: Function not implemented
...
is there a way to rebuild the urukdroid kernel with all ipsec function implemented ?

aosp kitkat4.4 nexus 7(deb) not boot

hi all:
i download aosp kitkat4.4 source codes from google website. i compiled the code. i got the ROM.but when i flash the ROM to my device nexus 7(deb). it cannot boot.
from the log. i found that following error log. the sentence "couldn't find an OpenGL ES implementation" maybe cause the fatal question.
any advices is welcomed !
thank
brian
02-10 08:37:07.375: E/QCOMKeyMaster(17633): failed to load qseecom library
02-10 08:37:07.375: E/keystore(17633): could not open keymaster device in keystore (Operation not permitted)
02-10 08:37:07.375: E/keystore(17633): keystore keymaster could not be initialized; exiting
02-10 08:37:07.405: A/libEGL(17630): couldn't find an OpenGL ES implementation
02-10 08:37:07.405: A/libc(17630): Fatal signal 6 (SIGABRT) at 0x000044de (code=-6), thread 17630 (surfaceflinger)
02-10 08:37:07.575: E/msm8960_platform(17632): platform_init: DLOPEN failed for libacdbloader.so
02-10 08:37:07.575: E/msm8960_platform(17632): platform_init: DLOPEN failed for libcsd-client.so
02-10 08:37:07.575: E/MonoPipe(17632): Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional

wifi problem

Hello,
i own a RK3188 device (T-R42 with board version B351 V1.1)
I flashed a custom rom and since then i am no more able to reactivate the wifi
I tried many other custom roms and stock roms, but i have always the same behavior:
When from the settings i try to turn it on, it stays on for a few seconds ( no wireless network is shown ), and then it goes off
This is the logcat that is printed when i try to turn my wifi on:
(using command adb logcat on terminal emulator session)
D/WifiHW ( 368): Read wifi chip type OK ! wifi_chip_type = RK901
D/WifiHW ( 368): wifi_load_driver: DRIVER_MODULE_PATH = /system/lib/modules/rkwifi.ko, DRIVER_MODULE_ARG =
D/BluetoothAdapterService(1097373104)( 811): getState(): mAdapterProperties: [email protected] 4168aef0
D/BluetoothAdapterService(1097373104)( 811): getState(): mAdapterProperties: [email protected] 4168aef0
D/WifiService( 368): setWifiEnabled: true pid=870, uid=1000
D/AudioHardwareALSA( 109): Audio exiting sandby will open audio device
D/AudioHardwareALSA( 109): AudioStreamOutALSA::standby().....
D/WifiHW ( 368): wifi_load_driver: driver load failed
D/WifiHW ( 368): Unable to unload driver module "wlan": No such file or directory
E/WifiStateMachine( 368): Failed to load driver!
E/WifiStateMachine( 368): DriverFailedState
i checked that under system/lib/modules do exist these files:
rkwifi.ko
wlan.ko
both with owner 'root', group 'root' and permissions 644
Can someone give me some hints on what is the possible cause of this error,
and how to discover the right wifi drivers for my device?
Thank you!

Try reflashing the baseband again, I was having the same problem with a kernel, and a custom rom, I flashed the stock baseband and reflash the custom rom and my wifi started working again, or check the kernel that you are using, that could be the problem. Hope this helped out a bit, I know its a real headache when this happens, hope you made a backup too.

Vicolodo said:
Hello,
i own a RK3188 device (T-R42 with board version B351 V1.1)
I flashed a custom rom and since then i am no more able to reactivate the wifi
I tried many other custom roms and stock roms, but i have always the same behavior:
When from the settings i try to turn it on, it stays on for a few seconds ( no wireless network is shown ), and then it goes off
This is the logcat that is printed when i try to turn my wifi on:
(using command adb logcat on terminal emulator session)
D/WifiHW ( 368): Read wifi chip type OK ! wifi_chip_type = RK901
D/WifiHW ( 368): wifi_load_driver: DRIVER_MODULE_PATH = /system/lib/modules/rkwifi.ko, DRIVER_MODULE_ARG =
D/BluetoothAdapterService(1097373104)( 811): getState(): mAdapterProperties: [email protected] 4168aef0
D/BluetoothAdapterService(1097373104)( 811): getState(): mAdapterProperties: [email protected] 4168aef0
D/WifiService( 368): setWifiEnabled: true pid=870, uid=1000
D/AudioHardwareALSA( 109): Audio exiting sandby will open audio device
D/AudioHardwareALSA( 109): AudioStreamOutALSA::standby().....
D/WifiHW ( 368): wifi_load_driver: driver load failed
D/WifiHW ( 368): Unable to unload driver module "wlan": No such file or directory
E/WifiStateMachine( 368): Failed to load driver!
E/WifiStateMachine( 368): DriverFailedState
i checked that under system/lib/modules do exist these files:
rkwifi.ko
wlan.ko
both with owner 'root', group 'root' and permissions 644
Can someone give me some hints on what is the possible cause of this error,
and how to discover the right wifi drivers for my device?
Thank you!
Click to expand...
Click to collapse
Do you have stock firmware/rom of your device? If yes then you need to flash(patch) all the files in lib/modules.
Also in updater-script add this code:
symlink("rkwifi.ko", "/system/lib/modules/wlan.ko");
then flash it via cwm

MgudFrn said:
Do you have stock firmware/rom of your device? If yes then you need to flash(patch) all the files in lib/modules.
Also in updater-script add this code:
symlink("rkwifi.ko", "/system/lib/modules/wlan.ko");
then flash it via cwm
Click to expand...
Click to collapse
Ok thank you,
yes, the seller gave me some links for the stock firmware, but he is not sure on which is the original stock firmware
(for T-R42 there are a lot of different board versions with different chipsets...)
i can extract the components with a tool (perhaps i need only system.img and unpack it)
and build a zip to patch the system/lib/modules
by the way, why i have to add that symlink?
i checked that RK901 information is under the sys folder,
the file system under this folder is built dynamically by the kernel, i am right?
do you think that RK901 is hard-coded into the kernel?
because opening the board i checked that i have a different chipset... wifi is managed by chip AP6210
Thank you!

kidkree1 said:
Try reflashing the baseband again, I was having the same problem with a kernel, and a custom rom, I flashed the stock baseband and reflash the custom rom and my wifi started working again, or check the kernel that you are using, that could be the problem. Hope this helped out a bit, I know its a real headache when this happens, hope you made a backup too.
Click to expand...
Click to collapse
Thank you too
The strange thing i see on the settings is that the wifi mac address is not set (unknown)...perhaps this happens because wifi driver cannot be loaded?
The second strange thing i see is that the file
/sys/class/rkwifi/chip
(this is the file used by the wifi driver loader procedure to know which is the wifi chip of the board)
contains RK901
i read somewhere that this chip is used on rk3066 boards, instead i have a rk3188 board
Besides that, i opened my tv box and i saw that i have the chip AP6210...
By the way, this is the link to an example driver loader procedure
https://github.com/gripped/MK808-he...lob/master/RK30_MT5931_MT6622/wifi/wifi.c.new
I found it googling one of the strings that is reported by the logcat
'D/WifiHW ( 368): wifi_load_driver: DRIVER_MODULE_PATH = /system/lib/modules/rkwifi.ko',
this string is contained in the c source file
so also the driver load procedure seems done for other device (rk3066)...
or perhaps rk3066 and rk3188 share the same procedures... i dont know...

Vicolodo said:
Ok thank you,
yes, the seller gave me some links for the stock firmware, but he is not sure on which is the original stock firmware
(for T-R42 there are a lot of different board versions with different chipsets...)
i can extract the components with a tool (perhaps i need only system.img and unpack it)
and build a zip to patch the system/lib/modules
by the way, why i have to add that symlink?
i checked that RK901 information is under the sys folder,
the file system under this folder is built dynamically by the kernel, i am right?
do you think that RK901 is hard-coded into the kernel?
because opening the board i checked that i have a different chipset... wifi is managed by chip AP6210
Thank you!
Click to expand...
Click to collapse
Previously I faced same problem with my mt6575 chipset and that was resolved by this method. I know mine and yours chipset is totally different but the logcat that I got was same as yours mentioning 'loading drivers failed'. So you can give it a try. but plz do a nandroid backup first.

Driver problem??
Vicolodo said:
Hello,
i own a RK3188 device (T-R42 with board version B351 V1.1)
I flashed a custom rom and since then i am no more able to reactivate the wifi
I tried many other custom roms and stock roms, but i have always the same behavior:
When from the settings i try to turn it on, it stays on for a few seconds ( no wireless network is shown ), and then it goes off
This is the logcat that is printed when i try to turn my wifi on:
(using command adb logcat on terminal emulator session)
D/WifiHW ( 368): Read wifi chip type OK ! wifi_chip_type = RK901
D/WifiHW ( 368): wifi_load_driver: DRIVER_MODULE_PATH = /system/lib/modules/rkwifi.ko, DRIVER_MODULE_ARG =
D/BluetoothAdapterService(1097373104)( 811): getState(): mAdapterProperties: [email protected] 4168aef0
D/BluetoothAdapterService(1097373104)( 811): getState(): mAdapterProperties: [email protected] 4168aef0
D/WifiService( 368): setWifiEnabled: true pid=870, uid=1000
D/AudioHardwareALSA( 109): Audio exiting sandby will open audio device
D/AudioHardwareALSA( 109): AudioStreamOutALSA::standby().....
D/WifiHW ( 368): wifi_load_driver: driver load failed
D/WifiHW ( 368): Unable to unload driver module "wlan": No such file or directory
E/WifiStateMachine( 368): Failed to load driver!
E/WifiStateMachine( 368): DriverFailedState
i checked that under system/lib/modules do exist these files:
rkwifi.ko
wlan.ko
both with owner 'root', group 'root' and permissions 644
Can someone give me some hints on what is the possible cause of this error,
and how to discover the right wifi drivers for my device?
Thank you!
Click to expand...
Click to collapse
The last few line sof your logcat show that there is some driver error...try a full wipe, then (as already suggested) flash a stock ROM for your device.
(<--Remember to Thank me if this helps)

Vicolodo said:
Thank you too
The strange thing i see on the settings is that the wifi mac address is not set (unknown)...perhaps this happens because wifi driver cannot be loaded?
The second strange thing i see is that the file
/sys/class/rkwifi/chip
(this is the file used by the wifi driver loader procedure to know which is the wifi chip of the board)
contains RK901
i read somewhere that this chip is used on rk3066 boards, instead i have a rk3188 board
Besides that, i opened my tv box and i saw that i have the chip AP6210...
By the way, this is the link to an example driver loader procedure
https://github.com/gripped/MK808-he...lob/master/RK30_MT5931_MT6622/wifi/wifi.c.new
I found it googling one of the strings that is reported by the logcat
'D/WifiHW ( 368): wifi_load_driver: DRIVER_MODULE_PATH = /system/lib/modules/rkwifi.ko',
this string is contained in the c source file
so also the driver load procedure seems done for other device (rk3066)...
or perhaps rk3066 and rk3188 share the same procedures... i dont know...
Click to expand...
Click to collapse
Vicolodo,
Were you able to get your wifi working again? I am having a similar issue on RK3066 aftermarket GPS car unit and can really use some advice.
Thanks!
P340

[5.1.x] [SM-T325] CyanogenMod 12.1 UNOFFICIAL Nightlies for the Tab Pro 8.4 LTE

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 12.1 on your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Known Issues
* None
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
Download Links
CyanogenMod: download.crpalmer.org
Google apps addon:
Download: http://d-h.st/users/dhacker29/?fld_id=27426 (use latest lpmr1 gapps)
XDA:DevDB Information
CyanogenMod 12.1 for MondrianLTE (Unofficial), ROM for the Samsung Galaxy Tab Pro 12.2, 10.1, 8.4
Contributors
crpalmer
ROM OS Version: 5.1.x Lollipop
Version Information
Status: No Longer Updated
Created 2015-04-18
Last Updated 2016-02-13

Reserved

Works fine
ROM works fine, made a dirty flash from CM12.
No problems at all.

http://review.cyanogenmod.org/#/c/95004/2
hopefully merged soon (already in cm12 since late march..just noticed recently in cm12 builds in mms.apk...should have known by looking at the history for the cm12 version)
EDIt
One thing though
Email exchange (hotmail etc) app has a repeated error popup during sync..this is from 4/17 build and also today's 4/18...was not the case till 4/16..noticed the apk file size has changed (not sure what..but it starts giving error popups during sync...pretty irritating as have to somehow get it to stop the sync to stop the popup...using the cm12.1 email apk 5.82mb from 4/16 or earlier fixes the issue)
cm12 not having such issues,.at least from 4.16 to 4/18 no email.apk file size changes..no sync issues
Edit attached mixer file to address earpiece echo for other caller not speakerphone echo for other caller.. change zip in extension to xml.. not a zip file..put in system etc folder permissions 644

Does miracast work with this build? I know CM started enabling the feature, but it didn't work when I last tried it with my SM-T315. Thank you for your answer.

Can I just ask a general question to all who have flashed this on the T325, what version specifically of TWRP did you use to flash this? Been having some issues and just want to compare.

RavenY2K3 said:
Can I just ask a general question to all who have flashed this on the T325, what version specifically of TWRP did you use to flash this? Been having some issues and just want to compare.
Click to expand...
Click to collapse
TWRP 2.8.5.0 here. Any later version will work as well.

Hello,
Thank you @crpalmer - great job with this rom!
Any chance I could buy you a beer to express my gratitude? I don't see a donations link in the OP

vrl13 said:
Hello,
Thank you @crpalmer - great job with this rom!
Any chance I could buy you a beer to express my gratitude? I don't see a donations link in the OP
Click to expand...
Click to collapse
Thanks!
There's a donate link in my profile but I prefer not to clutter up useful information with extra donate links...
My PayPal is [email protected].

Beer uploaded: 7UG08116JF1461945
Thanks again!
Sent from my SM-T325 using Tapatalk

Anyone having issues with there WiFi. Sometimes it picks up my wifi other times it doesn't. Sees all the others around the building but not mine.
Sent from my Nexus 6 using XDA Free mobile app

mackenzie121 said:
Anyone having issues with there WiFi. Sometimes it picks up my wifi other times it doesn't. Sees all the others around the building but not mine.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Hello,
I'm having no issue with both 2.4 and 5ghz wifi in my home.
Sounds like a router problem though.. can your other devices pick your wifi without a hitch?
Maybe it would help using a fixed IP, in case you are using DHCP now.
Regards.
Sent from my SM-T325 using Tapatalk

RavenY2K3 said:
Can I just ask a general question to all who have flashed this on the T325, what version specifically of TWRP did you use to flash this? Been having some issues and just want to compare.
Click to expand...
Click to collapse
I used TWRP 2.8.6.0. I already flashed several nightlies on this tablet, no issues.
---------- Post added at 10:41 PM ---------- Previous post was at 10:26 PM ----------
Is the changelog the same of the nightlies for "MONDRIANWIFI"? Thanks

Is it support cifs ?

Device encryption doesn't work. Build 20150507
Log:
Code:
D/Cryptfs ( 247): unmounting /data succeeded
D/QSEECOMAPI: ( 247): QSEECom_get_handle sb_length = 0x2000
D/QSEECOMAPI: ( 247): App is not loaded in QSEE
E/QSEECOMAPI: ( 247): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt
E/QSEECOMAPI: ( 247): Error::Loading image failed with ret = -1
D/QSEECOMAPI: ( 247): QSEECom_get_handle sb_length = 0x2000
D/QSEECOMAPI: ( 247): App is not loaded in QSEE
E/QSEECOMAPI: ( 247): Error::Cannot open the file /firmware/image/keymaste.mdt
E/QSEECOMAPI: ( 247): Error::Loading image failed with ret = -1
E/QCOMKeyMaster( 247): Loading keymaster app failed
E/Cryptfs ( 247): could not open keymaster device in keystore (Operation not permitted)
E/Cryptfs ( 247): Failed to init keymaster
F/libc ( 247): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x3c in tid 316 (vold)
F/libc ( 247): Unable to open connection to debuggerd: Connection refused
W/vold ( 316): type=1400 audit(0.0:190): avc: denied { search } for name="/" dev="mmcblk0p1" ino=1 scontext=u:r:vold:s0 tcontext=u:object_r:firmware_file:s0 tclass=dir
W/vold ( 316): type=1300 audit(0.0:190): arch=40000028 syscall=322 per=800000 success=no exit=-13 a0=ffffff9c a1=b62f84fc a2=20000 a3=0 items=1 ppid=1 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 exe="/system/bin/vold" subj=u:r:vold:s0 key=(null)
W/auditd ( 314): type=1307 audit(0.0:190): cwd="/"
W/auditd ( 314): type=1302 audit(0.0:190): item=0 name="/vendor/firmware/keymaster/keymaster.mdt"
W/auditd ( 314): type=1320 audit(0.0:190):
W/vold ( 316): type=1400 audit(0.0:191): avc: denied { search } for name="/" dev="mmcblk0p1" ino=1 scontext=u:r:vold:s0 tcontext=u:object_r:firmware_file:s0 tclass=dir
W/vold ( 316): type=1300 audit(0.0:191): arch=40000028 syscall=322 per=800000 success=no exit=-13 a0=ffffff9c a1=b62f84fc a2=20000 a3=0 items=1 ppid=1 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 exe="/system/bin/vold" subj=u:r:vold:s0 key=(null)
W/auditd ( 314): type=1307 audit(0.0:191): cwd="/"
W/auditd ( 314): type=1302 audit(0.0:191): item=0 name="/firmware/image/keymaste.mdt"
W/auditd ( 314): type=1320 audit(0.0:191):
W/vold ( 316): type=1701 audit(0.0:192): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=u:r:vold:s0 reason="memory violation" sig=11
I/Vold ( 8391): Vold 2.1 (the revenge) firing up
D/Vold ( 8391): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 8391): Volume usbdisk state changing -1 (Initializing) -> 0 (No-Media)
I/Cryptfs ( 8391): Check if PFE is activated on Boot
E/Cryptfs ( 8391): Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
E/Cryptfs ( 8391): Error getting crypt footer and key
I see, that file /vendor/firmware/keymaster/keymaster.mdt exists:
# ls -la /system/vendor/firmware/keymaster/keymaster.mdt
lrw-r--r-- root root 2015-05-07 07:04 keymaster.mdt -> /firmware/image/keymaste.mdt
# ls -la /firmware/image/keymaste.mdt <
-r--r----- system drmrpc 12892 2014-11-13 05:32 keymaste.mdt
Any ideas how to fix it? Thanks.

crpalmer said:
CyanogenMod
Click to expand...
Click to collapse
f2fs support?
I am waiting for 10 minutes, hanging on the logo

Alexey71 said:
f2fs support?
I am waiting for 10 minutes, hanging on the logo
Click to expand...
Click to collapse
Try again with today's build and let me know.

crpalmer said:
Try again with today's build and let me know.
Click to expand...
Click to collapse
For me :
cm-12.1-20150523-UNOFFICIAL-mondrianlte.zip work fine but
cm-12.1-20150527-UNOFFICIAL-mondrianlte.zip and cm-12.1-20150528-UNOFFICIAL-mondrianlte.zip don't work : hanging on the logo

27-28 build not work (ext4-f2fs)
26 build work ext4

Builds 0527 and 0528 does not boot; instead, causes shutdown of the tab.