Hi!
I have a problem with my phone that it randomly vibrates with no notification what so ever, even after doing a full wipe and flashing new ROM.
Lets start with some info:
GT-i9505
Danvdh Google Play ROM 4.4.4 (Pure nexus version)
GoogyMax3_GE 1.1.6 Kernel
I have Xposed Framwork installed
I have "Show all app that don't respond" in Developer options, still no errors have popped up.
No app which i've seen send vibration without notification when an update occurs.
I've tried to trace the source with logcat but havent really gotten any far.
Using the app aLogcat ROOT i often get the message:
Code:
E/AndroidRuntime(xxxxx): cannot open customer xml file
E/memtrack(same numbers): couldn't load memtrack module (no such file or directory)
E/Android.os.Debug(same numbers): failed to load memtrack module: -2
If i have the logging up and running in the app and then press Home button (Which takes me to Apex Launcher) i often get 2 quick vibrations
If i then start aLogcat ROOT again, i sometimes get another vibration followed by either
Code:
I/DEBUG (26414): Build fingerprint: 'samsung/jgedlteue/jgedlte:4.4.4/KTU84P.S001/140602:user/release-keys
or
Code:
E/LightSensor ( 1010): Light old sensor_state 1, new sensor_state : 1 en : 0
However, it seems most often related to I/DEBUG (26414): Build fingerprint: 'samsung/jgedlteue/jgedlte:4.4.4/KTU84P.S001/140602:user/release-keys
It's kinda getting frustrating and nothing i've Googled have seem to have provided the answer, most answers are something in line of Facebook messenger, repeat notification functions (For example vibration every 5 mins for sms, etc).
It happened more often before i wiped phone, which i then had Danvdh GPE rom, but 4.4.2 version instead, and ktoonez kernel. Apps were mostly same.
Following caused 2 vibrations 2 times:
Code:
I/DEBUG (26830): Build fingerprint: 'samsung/jgedlteue/jgedlte:4.4.4/KTU84P.S001/140602:user/release-keys'
I/DEBUG (26830): Build fingerprint: 'samsung/jgedlteue/jgedlte:4.4.4/KTU84P.S001/140602:user/release-keys'
E/LocSvc_eng( 1010): D/void loc_eng_deferred_action_thread(void*):1627] received msg_id = LOC_ENG_MSG_INJECT_LOCATION context = 0x8012add0
E/LocSvc_adapter( 1010): I/<--- void globalRespCb(locClientHandleType, uint32_t, locClientRespIndUnionType, void*) line 115 QMI_LOC_INJECT_POSITION_REQ_V02
E/LocSvc_api_v02( 1010): D/loc_free_slot:298]: freeing slot 0
E/Watchdog( 1010): [email protected] 194
E/AndroidRuntime(27295): cannot open customer xml file
E/memtrack(27295): Couldn't load memtrack module (No such file or directory)
E/android.os.Debug(27295): failed to load memtrack module: -2
I/DEBUG (26830): Build fingerprint: 'samsung/jgedlteue/jgedlte:4.4.4/KTU84P.S001/140602:user/release-keys'
I/DEBUG (26830): Build fingerprint: 'samsung/jgedlteue/jgedlte:4.4.4/KTU84P.S001/140602:user/release-keys'
E/AndroidRuntime(27396): cannot open customer xml file
E/memtrack(27396): Couldn't load memtrack module (No such file or directory)
E/android.os.Debug(27396): failed to load memtrack module: -2
Does anyone have ANY clue on how to fix this, or what might be causing it.
Anyone have any similar findings?
Thanks in advance
I have same problem!
If I remove Xposed Framework the random vibrations no longer appear, but it is very useful for me!
I opened a thread in Xposed Framework General -> here
Hi, ive got the same problem, random vibration 1 to 3 time, im running on the same
Rom with xposed installed. Anyone know any fix for that? Thank you
Want adopted sd enabled in the latest cm based custom rom for our dear moto e
Here is a temporary workaround
Firstly this was done by making use of a guide found in ashwin007's thread called
[ROM][OFFICIAL][condor] CyanogenMod 13 for Moto E 2014
Page 134 by millerscout.
In that guide youll find 11 steps to follow.
Now you'll just have to make small changes to two of the steps
Step 2. Change to whatever MM CM based rom you want and
Step 10. to the MM CM based rom you have chosen.
Now I usually keep these things to myself but for some time now I've noticed a lot of persons keep asking in the threads if adopted sd card is working. C'mon guys Its annoying. Despite the answers being yes at times its only after I've wiped my phone and install the latest rom I find out that adopted sd card is not working and corrupts my sd card. The guide by millerscout is a simple workaround I found for this small problem and with my added input it could work with other cm based marshmallow roms. Ive never tried it with AOSP or any other marshmallow based roms only CM.
That's it now enjoy the latest mm cm based roms with adopted sd until it as been officially fixed by ashwin007 :highfive:
Disclaimer: The instructions are pretty straightforward. Read and follow the instructions to reap your reward. With that said I will not be responsible for any fumes leaking from your phone
I could testify it
Just done it yesterday, using cm13 20160113 instead of temasek unoficial build
1. Factory reset using twrp
2. Clean flash cm13 20160113 and gapps
3. Wipe cache n dalvik cache, don't know if it is necessary, it just habits
4. Reboot system, finish setup wizard, set up sdcard as internal
5. Reboot to twrp
6. Flash newest cm13 build, i use 20160224 yesterday
7. Wipa cache n dalvik cache
8. Reboot system, sdcard as internal still working fine
I heard that aospb n orionos has sdcard as internal worked too
Thanks to @ehrans and @millerscout for the tricks
didnt worked for me with ressurection
any other way i can use..??really frustrated with the storage running out msg
I've Successfully formatted my sd card as internal but having a serious problem..when i connect my phone to the computer, it doesn't show my sd card for transfering the backup files to my phone.. what to do now ?? Any help Guyss ??
Edit : I've restarted my phone also but still doesn't helped..
Hello everyone. I've been hearing a lot of users reporting issues with adopted SD on condor. It worls fine on otus, so it is evidently a condor specific issue. I don't yet have the device, so I can't test and debug the issue myself at the moment. However, if someone coulld share logs of trying to format the SD card as internal on the latest nightly, that would be helpful. In particular, I want to see the logcat and dmesg output during the SD card formatting process.
A few word of advice on capturing logs: It's usually more helpful to capture a log of just doing the action of interest rather than providing a log from bootup till an hour after reproducing the issue. The way I usually do this on Linux or Mac is to start adb logcat on a shell, let it spew out everything, then clear the terminal, do the action of interest, let it complete, then hit Ctrl-C to stop logcat. Then copy paste the terminal contents into a file. For dmesg, just copy paste the last n secomds showing the relevant operation.
squid2 said:
Hello everyone. I've been hearing a lot of users reporting issues with adopted SD on condor. It worls fine on otus, so it is evidently a condor specific issue. I don't yet have the device, so I can't test and debug the issue myself at the moment. However, if someone coulld share logs of trying to format the SD card as internal on the latest nightly, that would be helpful. In particular, I want to see the logcat and dmesg output during the SD card formatting process.
A few word of advice on capturing logs: It's usually more helpful to capture a log of just doing the action of interest rather than providing a log from bootup till an hour after reproducing the issue. The way I usually do this on Linux or Mac is to start adb logcat on a shell, let it spew out everything, then clear the terminal, do the action of interest, let it complete, then hit Ctrl-C to stop logcat. Then copy paste the terminal contents into a file. For dmesg, just copy paste the last n secomds showing the relevant operation.
Click to expand...
Click to collapse
please find attached dmesg.txt
Ansh2000 said:
please find attached dmesg.txt
Click to expand...
Click to collapse
Thanks for the log. The associated logcat would also be helpful, but from what I see in the dmesg, a couple things jumped out to me.
It looks like the f2fs formatting utility (mkfs.f2fs) crashes, and subsequent attempts crash further:
Code:
[ 2413.240089,0] mmcblk1: p1
[ 2414.518112,1] mmcblk1: p1 p2
[ 2414.969437,1] Core dump to |/system/bin/coredump mkfs.f2fs 8800 1457156718 pipe failed
...
[ 2462.808252,1] mmcblk1: unknown partition table
[ 2464.031938,0] mmcblk1: p1 p2
[ 2464.556586,0] Core dump to |/system/bin/coredump mkfs.f2fs 8996 1457156767 pipe failed
The big question would be why it crashes. The logcat may give more hints as to this. One thing I did notice is that there are an awful lot of untrusted_app selinux denials. One should usually not grant additional permission to untrusted_app. However, I'm curious if SELinux is causing issues for you. One thing worth trying would be to make selinux permissive (run "setenforce 0" as root) before trying to format the card. If that makes formatting work, then we'd know for sure that it's an SELinux related issue. However, this is just a wild guess, and the issue may be something completely unrelated.
squid2 said:
Thanks for the log. The associated logcat would also be helpful, but from what I see in the dmesg, a couple things jumped out to me.
It looks like the f2fs formatting utility (mkfs.f2fs) crashes, and subsequent attempts crash further:
Code:
[ 2413.240089,0] mmcblk1: p1
[ 2414.518112,1] mmcblk1: p1 p2
[ 2414.969437,1] Core dump to |/system/bin/coredump mkfs.f2fs 8800 1457156718 pipe failed
...
[ 2462.808252,1] mmcblk1: unknown partition table
[ 2464.031938,0] mmcblk1: p1 p2
[ 2464.556586,0] Core dump to |/system/bin/coredump mkfs.f2fs 8996 1457156767 pipe failed
The big question would be why it crashes. The logcat may give more hints as to this. One thing I did notice is that there are an awful lot of untrusted_app selinux denials. One should usually not grant additional permission to untrusted_app. However, I'm curious if SELinux is causing issues for you. One thing worth trying would be to make selinux permissive (run "setenforce 0" as root) before trying to format the card. If that makes formatting work, then we'd know for sure that it's an SELinux related issue. However, this is just a wild guess, and the issue may be something completely unrelated.
Click to expand...
Click to collapse
logcat
@squid2 http://forum.cyanogenmod.org/topic/...-sd-as-internal-storage-then-says-sd-corrupt/
does this seems legit? and if it would works (it works acc. to users in cm12.1 forum) how to execute it?
see the post made by socram8888
can anyone confirm at all if running the command "mkfs.f2fs /dev/block/dm-0" in terminal emulator would do the job? without having to format card using january nightly
booo159159 said:
@squid2 http://forum.cyanogenmod.org/topic/...-sd-as-internal-storage-then-says-sd-corrupt/
does this seems legit? and if it would works (it works acc. to users in cm12.1 forum) how to execute it?
see the post made by socram8888
can anyone confirm at all if running the command "mkfs.f2fs /dev/block/dm-0" in terminal emulator would do the job? without having to format card using january nightly
Click to expand...
Click to collapse
The mkfs.f2fs /dev/block/dm-0 is the command that is failing when trying to format through the wizard. Maybe it works properly when invoked manually. It's worth a try. Let me know what happens when you try it. Be sure to run it as root.
@Ansh2000 Thanks for the logcat. The relevant problem that repeats in the logcat is this crash in mkfs.f2fs:
Code:
03-05 12:09:15.017 192 200 D vold : Resolved auto to f2fs
03-05 12:09:15.017 192 200 V vold : /system/bin/mkfs.f2fs
03-05 12:09:15.017 192 200 V vold : /dev/block/dm-0
--------- beginning of crash
03-05 12:09:15.121 6320 6320 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x6 in tid 6320 (mkfs.f2fs)
03-05 12:09:15.122 231 231 I DEBUG : property debug.db.uid not set; NOT waiting for gdb.
03-05 12:09:15.122 231 231 I DEBUG : HINT: adb shell setprop debug.db.uid 100000
03-05 12:09:15.122 231 231 I DEBUG : HINT: adb forward tcp:5039 tcp:5039
03-05 12:09:15.206 231 231 I SELinux : SELinux: Loaded file_contexts contexts from /file_contexts.
03-05 12:09:15.209 706 1108 W NativeCrashListener: Couldn't find ProcessRecord for pid 6320
03-05 12:09:15.210 231 231 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-05 12:09:15.210 231 231 E DEBUG : AM write failed: Broken pipe
03-05 12:09:15.210 231 231 F DEBUG : Build fingerprint: 'motorola/condor_retaildsds/condor_umtsds:5.1/LPC23.13-34.8/12:user/release-keys'
03-05 12:09:15.210 231 231 F DEBUG : Revision: '0'
03-05 12:09:15.210 231 231 F DEBUG : ABI: 'arm'
03-05 12:09:15.210 231 231 F DEBUG : pid: 6320, tid: 6320, name: mkfs.f2fs >>> /system/bin/mkfs.f2fs <<<
03-05 12:09:15.210 231 231 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x6
03-05 12:09:15.221 231 231 F DEBUG : r0 b6d2e1c0 r1 00000006 r2 b7b770c8 r3 b7b770d8
03-05 12:09:15.222 231 231 F DEBUG : r4 b6d2e1c0 r5 b6d2e1c0 r6 b7b770c8 r7 00000000
03-05 12:09:15.222 231 231 F DEBUG : r8 00000036 r9 b6f4fff4 sl b6f001a4 fp 00000006
03-05 12:09:15.222 231 231 F DEBUG : ip 00000000 sp bea446c0 lr 000007c0 pc b6ef3368 cpsr 60070030
03-05 12:09:15.236 231 231 F DEBUG :
03-05 12:09:15.236 231 231 F DEBUG : backtrace:
03-05 12:09:15.237 231 231 F DEBUG : #00 pc 00001368 /system/lib/libf2fs.so (utf8_to_utf16+31)
03-05 12:09:15.237 231 231 F DEBUG : #01 pc 0000f843 /system/lib/libutils.so
03-05 12:09:15.237 231 231 F DEBUG : #02 pc 0000f897 /system/lib/libutils.so (android::String16::String16(char const*)+22)
03-05 12:09:15.237 231 231 F DEBUG : #03 pc 0001fa41 /system/lib/libbinder.so
03-05 12:09:15.341 231 231 F DEBUG :
03-05 12:09:15.341 231 231 F DEBUG : Tombstone written to: /data/tombstones/tombstone_00
03-05 12:09:15.344 192 200 I mkfs.f2fs: mkfs.f2fs terminated by signal 11
03-05 12:09:15.344 706 733 I BootReceiver: Copying /data/tombstones/tombstone_00 to DropBox (SYSTEM_TOMBSTONE)
03-05 12:09:15.344 192 200 E vold : private:179_66 failed to format: No such device or address
You can see that the crash is happening in some string conversion code (invokations via utf8_to_utf16). I'm not yet sure why this crash is happening, but at least we now know what the crash is. One wild and probably incorrect guess is that it has something to do with differences between the condor fstab and otus fstab (such as the dual f2fs and ext4 userdata support, different mount flags).
BTW: Just to be sure, @Ansh2000, your internal storage userdata partition is formatted as f2fs and not ext4?
@squid2 formatted with f2fs.
Thanks @squid2 for taking your time out and looking at this condor specific issue. Thanks a bunch
@squid2 the partition formats successfully but still in the setting, it shows the sd card as corrupted even after a reboot. again trying to format through wizard and still unable to use.
FYI I had permissive selinux, and yes i ran it as root
and I use ext4 only, I never migrated to f2fs
EDIT: i made a mistake, this command would only work through the stock kernel, while i was using custom kernel. And flashing the kernel after making the sd card internal wont work either.
I mean the sd card would format. But only will be usable as internal through stock kernel
So i guess we'll have to wait until @rainforce279 brings some updates
squid2 said:
The mkfs.f2fs /dev/block/dm-0 is the command that is failing when trying to format through the wizard. Maybe it works properly when invoked manually. It's worth a try. Let me know what happens when you try it. Be sure to run it as root.
It is not working says mkfs.f2fs not found.
Click to expand...
Click to collapse
cm13 20160113
from where i can get cm13 20160113 build. bcoz it's not available on official site...
can u plz provide the link...
rajeev20 said:
from where i can get cm13 20160113 build. bcoz it's not available on official site...
can u plz provide the link...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=65406771&postcount=1338
:laugh::laugh:
squid2 said:
Thanks for the log. The associated logcat would also be helpful, but from what I see in the dmesg, a couple things jumped out to me.
It looks like the f2fs formatting utility (mkfs.f2fs) crashes, and subsequent attempts crash further:
Code:
[ 2413.240089,0] mmcblk1: p1
[ 2414.518112,1] mmcblk1: p1 p2
[ 2414.969437,1] Core dump to |/system/bin/coredump mkfs.f2fs 8800 1457156718 pipe failed
...
[ 2462.808252,1] mmcblk1: unknown partition table
[ 2464.031938,0] mmcblk1: p1 p2
[ 2464.556586,0] Core dump to |/system/bin/coredump mkfs.f2fs 8996 1457156767 pipe failed
The big question would be why it crashes. The logcat may give more hints as to this. One thing I did notice is that there are an awful lot of untrusted_app selinux denials. One should usually not grant additional permission to untrusted_app. However, I'm curious if SELinux is causing issues for you. One thing worth trying would be to make selinux permissive (run "setenforce 0" as root) before trying to format the card. If that makes formatting work, then we'd know for sure that it's an SELinux related issue. However, this is just a wild guess, and the issue may be something completely unrelated.
Click to expand...
Click to collapse
even if we somehow get adopted working on the roms which gives corrupted sd card error ....another error arises that is when we update apps that is on sd card the updated app comes on internal and when we try to move that app to sd card again ,phone soft reboots and app still remains on internal.
I'm on bliss 6.0 tried all the methods get error 255 I like m but if can't get SD fixed I'm going back to 5.1.1
Hi guys,
First time posting on XDA so hope I have the right section etc...
I am trying to compile and boot the kernel for the Xiaomi Mi Note 2 and have had some success, but the image created causes the phone to boot into recover. Can I check my build procedure with your please?
The Xiaomi GitHub wiki page has an guide for another phone, which I have followed as far as possible.
Anyway, here are the steps I have taken. Have I missed anything out in terms of configuration?
Step 1: Clone the Xiaomi git repo using:
git clone [email protected]:MiCode/Xiaomi_Kernel_OpenSource.git
Step 2: Checkout the Scorpio branch:
git checkout scorpio-m-oss
Step 3: Get the release tag for the QualComm suported Android Enablement Project: For the Mi Note 2 it I have used LA.UM.5.5.r1-04600-8x96.0.
Step 4: Download the QAEP:
repo init -u git://codeaurora.org/platform/manifest.git -b release -m LA.UM.5.5.r1-04600-8x96.0.xml –-repo-url=git://codeaurora.org/tools/repo.git --repo-branch=caf-stable --depth=1
repo sync -j8
Step 7: Merge Xioami Linux Kernel into QAEP: From the QAEP repo dir...
rm -rf kernel/*
mkdir kernel
cp -rf ~/Mi_Kernel/Xiaomi_Kernel_OpenSource/* kernel/
Step 8: Build Kernel
source build/envsetup.sh
lunch msm8996-userdebug
make bootimage BOARD_USES_LIBC_WRAPPER=true
I found that I had to specify BOARD_USES_LIBC_WRAPPER=true as otherwise there would be a link error in the build as the symbol __propClientDispatchWrite would not be defined. Searching for this symbol I found that it is defined in ./bionic/libc/codeaurora/PropClientDispatchWrite.cpp:48. Looking at the Makefile ./bionic/libc/Android.mk one can see that this file is only compiled if ifeq ($(BOARD_USES_LIBC_WRAPPER),true), hence the need for the extra define in the command line for make.
Step 9: Put kernel image into original
Download the original image and unpack:
adb pull /dev/block/sde36 boot_minote2_original.img
./mkboot boot_minote2_original.img boot_minote2_original
Do that same with mkboot for the image I built and unpack that. Then copy the file kernel from the newly build version into boot_minote2_original and repackage:
./mkboot boot_minote2_original boot_minote2_new.img
Step 9: Attempt to boot new image
adb reboot bootloader
fastboot boot boot_minote2_new.img
And, almost there. The new image boots to a state where I can at least ADB shell into the device. The logcat shows the following significant errors when compared to the logcat of the original xiaomi image:
W SystemServer: ***********************************************
E SystemServer: BOOT FAILURE making display ready
E SystemServer: java.lang.NullPointerException: Attempt to invoke virtual method 'void com.android.server.wm.WindowManagerService.displayReady()' on a null object reference
E SystemServer: at com.android.server.SystemServer.startOtherServices(SystemServer.java:594)
E SystemServer: at com.android.server.SystemServer.run(SystemServer.java:281)
E SystemServer: at com.android.server.SystemServer.main(SystemServer.java:179)
E SystemServer: at java.lang.reflect.Method.invoke(Native Method)
E SystemServer: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:738)
E SystemServer: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:628)
E System : ******************************************
E System : ************ Failure starting system services
E System : java.lang.NullPointerException: Attempt to invoke virtual method 'void com.android.server.wm.WindowManagerService.showBootMessage(java.lang.CharSequence, boolean)' on a null object reference
E System : at com.android.server.am.ActivityManagerService.showBootMessage(ActivityManagerService.java:6474)
E System : at com.android.server.SystemServer.startOtherServices(SystemServer.java:627)
E System : at com.android.server.SystemServer.run(SystemServer.java:281)
E System : at com.android.server.SystemServer.main(SystemServer.java:179)
E System : at java.lang.reflect.Method.invoke(Native Method)
E System : at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:738)
E System : at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:628)
D AndroidRuntime: Shutting down VM
E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main
E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'void com.android.server.wm.WindowManagerService.showBootMessage(java.lang.CharSequence, boolean)' on a null object reference
E AndroidRuntime: at com.android.server.am.ActivityManagerService.showBootMessage(ActivityManagerService.java:6474)
E AndroidRuntime: at com.android.server.SystemServer.startOtherServices(SystemServer.java:627)
E AndroidRuntime: at com.android.server.SystemServer.run(SystemServer.java:281)
E AndroidRuntime: at com.android.server.SystemServer.main(SystemServer.java:179)
E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:738)
E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:628)
So, onwards with my investigations but if any one has tips and clues to share, please lemme know
Trying to ask help from StoneTrapper !! He is the only one developer in this forum until now ...
Hey did you ever figure this out? Struggling with my Blu Life One X2 kernel. Compiling it without the QAEP tree boots, but the display goes all glitchy and just shows black. I can adb and everything else works.
Trying your method of QAEP now. Please let me know if you found anything new!
Hey, sorry I hadn't been keeping an eye on this thread.
I don't really use MIUI so haven't tried to compile the kernel for it. The current kernels that are around for these devices are based on generic similar devices with source code taken and adjusted from MiCode where needed.
Since this kernel base is also marshmallow for the more recent MIUI releases it'll need updating for that too.
For building a MIUI kernel your best bet is to take a look at other devices in the same family that currently have third party MIUI kernels. A good example is the DragonXia Kernel which is MIUI compatible. You'll need to add the missing features required for scorpio and add msm8996pro support but between MiCode and various sources it's do-able.
If you're successful and happy with the result then the author may be happy for you to release with permission.
I have successfully compiled stock kernel from samsung sources for my galaxy S5 G900H on kali linux.
I am trying to compile some modules. For that I have starred these ::
Code:
[*] Enable loadable module support
[CENTER] [*] Forced module loading [/CENTER]
[CENTER] [*] Module unloading [/CENTER]
[CENTER] [*] Forced module unloading [/CENTER]
I have rooted my phone and set selinux permissive mode. But trying to load these modules gives Exec format errors .
Code:
/system/bin/insmod asix.ko
insmod: failed to load asix.ko: Exec format error
In dmesg, it is showing ::
Code:
[ 5378.629376] [c3] TIMA: lkmauth--launch the tl to check kernel module; module len is 279631
[ 5378.630154] [c3] TIMA: lkmauth--cannot open mobicore session from kernel. 15
[ 5378.630296] [c3] TIMA: lkmauth--unable to load kernel module; module len is 279631.
After hours of searching , I found the culprit, it was samsung TIMA. So I just deselected "Enable TIMA" under "System Type" in kernel config. Now the modules load successfully.
I flashed a custom built ROM to a TB-8504F and it didn't go well. I was able to restore the majority of the partitions, but the WIFI doesn't work now. Everything else seems to work.
Is there a particular petition that I need to flash?
Attached are screenshots of the partitions on a stock tablet.
I think these logs are related:
Code:
01-08 17:48:26.818 2890 2890 E Sensors : sns_main.c(447):Timeout waiting for SMGR service. Exit sensors daemon!
01-08 17:48:26.819 2890 2890 W Sensors : sns_main.c(355):sns_main_exit called unlock daemon to exit
01-08 17:48:26.819 2890 2890 E Sensors : sns_main.c(561):Exiting! Err 0
01-08 17:48:26.848 2909 2909 W sensors.qcom: type=1400 audit(0.0:74): avc: denied { read write } for name="diag" dev="tmpfs" ino=717 scontext=u:r:sensors:s0 tcontext=u:object_r:diag_device:s0 tclass=chr_file permissive=0
01-08 17:48:26.858 2909 2909 E Diag_Lib: Diag_LSM_Init: Failed to open handle to diag driver, error = 13
01-08 17:48:26.858 2909 2909 W Sensors : sns_debug_main.c(442):Diag_LSM_Init failed: log packets and messages will not be available
01-08 17:48:26.861 2909 2911 E Sensors : sns_fsa_la.c(84):realpath failed for directory name2
01-08 17:48:26.861 2909 2911 E Sensors : sns_reg_la.c(289):Error creating registry file
01-08 17:48:26.861 2909 2911 W Sensors : sns_reg_mr.c(367):File init failed 5
drizzle123 said:
I flashed a custom built ROM to a TB-8504F and it didn't go well. I was able to restore the majority of the partitions, but the WIFI doesn't work now. Everything else seems to work.
Is there a particular petition that I need to flash?
Attached are screenshots of the partitions on a stock tablet.
I think these logs are related:
Click to expand...
Click to collapse
Use lenovo moto smart assistant to flash the stock firmware
skoar said:
Use lenovo moto smart assistant to flash the stock firmware
Click to expand...
Click to collapse
Will try this when I get to a PC - thank you!