L.S.,
As the title of the thread explains my camera seems to fail for no reason. When the camera app is initialized I get the error 'Camera failed'. This error is application independent, as I tried different camera apps.
When I launch the factory test app (*#0*#), i cannot launch the 'Megacam', but the front-camera is working. When I start the camera firmware app (*#7412365#), the program force closes. I am still running on stock rom (I9100XENLP5), already performed factory reset but no improvement.
I've attached a log file, main error code seems to be: E/SecCameraHardware( 1832): FimcV4l2 init: error -1, VIDIOC_S_INPUT. After which the camera instance is destroyed.
Help is appreciated.
NotwNL said:
I've attached a log file, main error code seems to be: E/SecCameraHardware( 1832): FimcV4l2 init: error -1, VIDIOC_S_INPUT. After which the camera instance is destroyed.
Help is appreciated.
Click to expand...
Click to collapse
I am by no means an expert, but this suggests a hardware problem.
Hi,
I developed a native process that uses ScreenshotClient to capture the device screen ( rooted devices only )
I have a loop where ScreenshotClient does update() every cycle. everything works well until 4.3.
when I run it on 4.3 the first call to update succeeds, but in the second call the call result is -2 , and I get these erros in logcat:
E/BufferQueue( 8166): [ScreenshotClient] connect: already connected (cur=1,req=1)
E/libEGL ( 2463): EGLNativeWindowType 0x4116d5f8 already connected to another API
E/libEGL ( 2463): eglCreateWindowSurface:376 error 300b (EGL_BAD_NATIVE_WINDOW)
E/SurfaceFlinger( 2463): captureScreenImplLocked: eglCreateWindowSurface() failed 0x300b
Any idea what changed in 4.3 that causes this, or what these errors mean.
Hi, since I closed my DEV threads there is no place for discussing development related things.
I've opened this thread so we can discuss any development related stuff (kernel etc).
Please keep the thread clean. I will report any non-low-level development posts.
ION kernel status
Kernel boots, lcd backlight is on but no image is shown.
I only get a display full of noise for half a second, after the following error occurs:
Code:
[ 8.994812] ------------[ cut here ]------------
[ 8.995025] WARNING: at /home/mike/android/cm10.1/kernel/semc/msm7x30/kernel/mutex.c:198 __mutex_lock_slowpath+0x70/0x27c()
[ 8.995483] Modules linked in:
[ 8.995758] [<c001428c>] (unwind_backtrace+0x0/0x11c) from [<c008a6f0>] (warn_slowpath_common+0x4c/0x64)
[ 8.996154] [<c008a6f0>] (warn_slowpath_common+0x4c/0x64) from [<c008a720>] (warn_slowpath_null+0x18/0x1c)
[ 8.996582] [<c008a720>] (warn_slowpath_null+0x18/0x1c) from [<c061b524>] (__mutex_lock_slowpath+0x70/0x27c)
[ 8.998138] [<c061b524>] (__mutex_lock_slowpath+0x70/0x27c) from [<c061b73c>] (mutex_lock+0xc/0x24)
[ 9.007171] [<c061b73c>] (mutex_lock+0xc/0x24) from [<c02988dc>] (mddi_host_timer_service+0x374/0x430)
[ 9.016448] [<c02988dc>] (mddi_host_timer_service+0x374/0x430) from [<c00949dc>] (run_timer_softirq+0x18c/0x260)
[ 9.026519] [<c00949dc>] (run_timer_softirq+0x18c/0x260) from [<c008fa1c>] (__do_softirq+0x74/0x120)
[ 9.035705] [<c008fa1c>] (__do_softirq+0x74/0x120) from [<c008fe8c>] (irq_exit+0x44/0xa8)
[ 9.043884] [<c008fe8c>] (irq_exit+0x44/0xa8) from [<c000f08c>] (handle_IRQ+0x68/0x8c)
[ 9.051788] [<c000f08c>] (handle_IRQ+0x68/0x8c) from [<c00084e4>] (vic_handle_irq+0x28/0x30)
[ 9.060119] [<c00084e4>] (vic_handle_irq+0x28/0x30) from [<c000dd80>] (__irq_svc+0x40/0x70)
[ 9.068511] Exception stack(0xc0879f58 to 0xc0879fa0)
[ 9.073547] 9f40: ffffffff 000000b0
[ 9.081634] 9f60: 00000001 00000000 c0878000 c0889470 c0908048 c0889464 00204059 511f00f2
[ 9.089874] 9f80: 00000000 00000000 00000000 c0879fa0 c007dbd8 c000f1a0 400b0013 ffffffff
[ 9.098052] [<c000dd80>] (__irq_svc+0x40/0x70) from [<c000f1a0>] (default_idle+0x24/0x2c)
[ 9.106201] [<c000f1a0>] (default_idle+0x24/0x2c) from [<c000f458>] (cpu_idle+0x5c/0xac)
[ 9.114196] [<c000f458>] (cpu_idle+0x5c/0xac) from [<c060af7c>] (rest_init+0x84/0x9c)
[ 9.122100] [<c060af7c>] (rest_init+0x84/0x9c) from [<c0840a54>] (start_kernel+0x368/0x3c4)
[ 9.130432] ---[ end trace 826fbc4fa566ec66 ]---
EDIT: Full log with mddi & msm_fb debugging enabled here: http://pastebin.com/Tj1izvyt
I don't see anything useful
I'm not familiar with these kernel building i know u people @android1234567 @DevConnection_Team @Christopher83 @johnnyslt @arco68 can help us building ION kernel for xperia 2011 devices ... sorry if I'm interrupting u .. thank you
mike maybe we need some specific changes in qcom_display_caf try to use arco'w variant
Does kernel panic if you exclude display driver?
Gesendet von meinem Xperia Neo V mit Tapatalk 2
deccen90 said:
I'm not familiar with these kernel building i know u people @android1234567 @DevConnection_Team @Christopher83 @johnnyslt @arco68 can help us building ION kernel for xperia 2011 devices ... sorry if I'm interrupting u .. thank you
Click to expand...
Click to collapse
Where is the stable pmem kernel source? and in what branch @mikeioannina tried to enable ION?
johnnyslt said:
Where is the stable pmem kernel source? and in what branch @mikeioannina tried to enable ION?
Click to expand...
Click to collapse
current pmem kernel: https://github.com/LegacyXperia/msm7x30-3.4.x-nAa/commits/cm-10.1
new ion kernel: https://github.com/mikeNG/android_kernel_semc_msm7x30/commits/cm-10.1-mutex-error
You can check the second post for more info.
mikeioannina said:
current pmem kernel: https://github.com/LegacyXperia/msm7x30-3.4.x-nAa/commits/cm-10.1
new ion kernel: https://github.com/mikeNG/android_kernel_semc_msm7x30/commits/cm-10.1-mutex-error
You can check the second post for more info.
Click to expand...
Click to collapse
I'm seeing that pmem_adsp doesn't get allocated and it should:
Code:
[ 3.558837] pmem: pmem_setup: unable to register pmem driver(pmem_adsp) - zero size passed in!
What adreno libs are you using?
Also are you using patched gralloc with PMEM_ADSP support?
hi @mikeioannina
I would like to help fix the fm radio in cm11. I am not a dev and I only have some basic C programming and github skills. If you think it is worth the time ( mine and yours), could you describe how to build the fm app for cm11 and where to look for bugs?
johnny.tifosi said:
hi @mikeioannina
I would like to help fix the fm radio in cm11. I am not a dev and I only have some basic C programming and github skills. If you think it is worth the time ( mine and yours), could you describe how to build the fm app for cm11 and where to look for bugs?
Click to expand...
Click to collapse
I believe that the FM app is broken because there is no wrapper for the SEMC FM libs...
johnny.tifosi said:
hi @mikeioannina
I would like to help fix the fm radio in cm11. I am not a dev and I only have some basic C programming and github skills. If you think it is worth the time ( mine and yours), could you describe how to build the fm app for cm11 and where to look for bugs?
Click to expand...
Click to collapse
kemoba said:
I believe that the FM app is broken because there is no wrapper for the SEMC FM libs...
Click to expand...
Click to collapse
You can pick this change: http://legacyxperia.us.to:8080/131 in order to build the TI FM stuff. It's only for cm10.1 currently but in my opinion it's the best version to work on FM, since we have the most complete code for msm7x30 & TI wl12xx in that version.
I'm afraid you won't manage to do anything since you need some knowledge of how android audio stuff works (I also haven't worked on audio stuff very much in the past and don't have much knowledge)
Anyway, the code is there for anyone who wants to try
mikeioannina said:
Kernel boots, lcd backlight is on but no image is shown.
I only get a display full of noise for half a second, after the following error occurs:
Code:
[ 8.994812] ------------[ cut here ]------------
[ 8.995025] WARNING: at /home/mike/android/cm10.1/kernel/semc/msm7x30/kernel/mutex.c:198 __mutex_lock_slowpath+0x70/0x27c()
[ 8.995483] Modules linked in:
[ 8.995758] [<c001428c>] (unwind_backtrace+0x0/0x11c) from [<c008a6f0>] (warn_slowpath_common+0x4c/0x64)
[ 8.996154] [<c008a6f0>] (warn_slowpath_common+0x4c/0x64) from [<c008a720>] (warn_slowpath_null+0x18/0x1c)
[ 8.996582] [<c008a720>] (warn_slowpath_null+0x18/0x1c) from [<c061b524>] (__mutex_lock_slowpath+0x70/0x27c)
[ 8.998138] [<c061b524>] (__mutex_lock_slowpath+0x70/0x27c) from [<c061b73c>] (mutex_lock+0xc/0x24)
[ 9.007171] [<c061b73c>] (mutex_lock+0xc/0x24) from [<c02988dc>] (mddi_host_timer_service+0x374/0x430)
[ 9.016448] [<c02988dc>] (mddi_host_timer_service+0x374/0x430) from [<c00949dc>] (run_timer_softirq+0x18c/0x260)
[ 9.026519] [<c00949dc>] (run_timer_softirq+0x18c/0x260) from [<c008fa1c>] (__do_softirq+0x74/0x120)
[ 9.035705] [<c008fa1c>] (__do_softirq+0x74/0x120) from [<c008fe8c>] (irq_exit+0x44/0xa8)
[ 9.043884] [<c008fe8c>] (irq_exit+0x44/0xa8) from [<c000f08c>] (handle_IRQ+0x68/0x8c)
[ 9.051788] [<c000f08c>] (handle_IRQ+0x68/0x8c) from [<c00084e4>] (vic_handle_irq+0x28/0x30)
[ 9.060119] [<c00084e4>] (vic_handle_irq+0x28/0x30) from [<c000dd80>] (__irq_svc+0x40/0x70)
[ 9.068511] Exception stack(0xc0879f58 to 0xc0879fa0)
[ 9.073547] 9f40: ffffffff 000000b0
[ 9.081634] 9f60: 00000001 00000000 c0878000 c0889470 c0908048 c0889464 00204059 511f00f2
[ 9.089874] 9f80: 00000000 00000000 00000000 c0879fa0 c007dbd8 c000f1a0 400b0013 ffffffff
[ 9.098052] [<c000dd80>] (__irq_svc+0x40/0x70) from [<c000f1a0>] (default_idle+0x24/0x2c)
[ 9.106201] [<c000f1a0>] (default_idle+0x24/0x2c) from [<c000f458>] (cpu_idle+0x5c/0xac)
[ 9.114196] [<c000f458>] (cpu_idle+0x5c/0xac) from [<c060af7c>] (rest_init+0x84/0x9c)
[ 9.122100] [<c060af7c>] (rest_init+0x84/0x9c) from [<c0840a54>] (start_kernel+0x368/0x3c4)
[ 9.130432] ---[ end trace 826fbc4fa566ec66 ]---
EDIT: Full log with mddi & msm_fb debugging enabled here: http://pastebin.com/Tj1izvyt
I don't see anything useful
Click to expand...
Click to collapse
Hello,
I'm porting 3.x kernel on an other xperia device (x10) and facing the same issue ... Did you managed to solve it ?
I'm using ion memory management and as johnnyslt wrote I got this line in log too :
PHP:
pmem: pmem_setup: unable to register pmem driver(pmem_adsp) - zero size passed in!
I'll look with for this (that musn't be a big deal to allocate pmem_adsp with fitting lines in board ... let's see if this is what is causing the trouble.
If you didn't find the solution yet, I'll let you know if I find
Regards
Tof37 said:
Hello,
I'm porting 3.x kernel on an other xperia device (x10) and facing the same issue ... Did you managed to solve it ?
I'm using ion memory management and as johnnyslt wrote I got this line in log too :
PHP:
pmem: pmem_setup: unable to register pmem driver(pmem_adsp) - zero size passed in!
I'll look with for this (that musn't be a big deal to allocate pmem_adsp with fitting lines in board ... let's see if this is what is causing the trouble.
If you didn't find the solution yet, I'll let you know if I find
Regards
Click to expand...
Click to collapse
No, still having the problem. I have limited time these days so no much progress...
If you manage anything let me know
@mikeioannina
Hope it'll help ... you should have a look to your drivers/video/msm/logo.c and msm_fb.c and .h files
In the last 2 files the lines which are dealing with fb_msm_logo ...
I ported 3.4 video drivers in the 3.0.8 kernel I use and add the same issue.
I add this problem too with 3.0.8 drivers and solving the problem of fb_msm_logo did it.
If you disable fb_msm_logo in your config file but still have the issue this means you're mising lines specific for your device.
If 3.0.X kernel is already working on your device, try to make a diff with video drivers.
I'll take a look at your repo when I'll have a little time
Regards
Tof37 said:
@mikeioannina
Hope it'll help ... you should have a look to your drivers/video/msm/logo.c and msm_fb.c and .h files
In the last 2 files the lines which are dealing with fb_msm_logo ...
I ported 3.4 video drivers in the 3.0.8 kernel I use and add the same issue.
I add this problem too with 3.0.8 drivers and solving the problem of fb_msm_logo did it.
If you disable fb_msm_logo in your config file but still have the issue this means you're mising lines specific for your device.
If 3.0.X kernel is already working on your device, try to make a diff with video drivers.
I'll take a look at your repo when I'll have a little time
Regards
Click to expand...
Click to collapse
Thanks for the hints,
hmm... I think I have tried without bootlogo with no luck, I will try again to be sure.
3.0.8 works fine on our devices, 3.4 works too but with 3.0.8 video drivers. When I try pure 3.4 it doesn't boot with the above error.
EDIT:
I tried disabling bootlogo with no change, still no display.
Making a diff of 3.0.8/3.4 drivers/video/msm is almost impossible since there are too many changes involved, I already tried it with no luck, spent hours and it didn't even compile.
I'm really sad with this situation, I'm working for 3 months on this kernel with the exact same issue. where the hell is the problem?
mikeioannina said:
Thanks for the hints,
hmm... I think I have tried without bootlogo with no luck, I will try again to be sure.
3.0.8 works fine on our devices, 3.4 works too but with 3.0.8 video drivers. When I try pure 3.4 it doesn't boot with the above error.
EDIT:
I tried disabling bootlogo with no change, still no display.
Making a diff of 3.0.8/3.4 drivers/video/msm is almost impossible since there are too many changes involved, I already tried it with no luck, spent hours and it didn't even compile.
I'm really sad with this situation, I'm working for 3 months on this kernel with the exact same issue. where the hell is the problem?
Click to expand...
Click to collapse
I see so I'm facing exactly the same problem ...
do you have this problem with your kernel with pmem ?
I didn't try with mine (only tried with the one where ion is enabled)
Even in the ion enabled version, pmem_adsp is allocated but still have the problem.
ps : It's been nearly 1 year I started to port 3.0.8 kernel on x10 ... I got nearly 6 months (including 2 months to not work on it) to try to solve display problem
@mikeioannina
You should try this ...
in drivers/video/msm/mddi.c
in void pmdh_clk_enable() you've got
PHP:
if (mddi_host_timer.function)
mddi_host_timer_service(0);
In my .32 video drivers this if is in static int mddi_resume ...
Try to get the the above function like this :
PHP:
static int mddi_resume(struct platform_device *pdev)
{
mddi_host_type host_idx = MDDI_HOST_PRIM;
if (!mddi_is_in_suspend)
return 0;
mddi_is_in_suspend = 0;
if (mddi_power_locked)
return 0;
pmdh_clk_enable();
mddi_host_reg_out(PAD_CTL, mddi_pad_ctrl);
[B]if (mddi_host_timer.function)
mddi_host_timer_service(0);[/B]
return 0;
}
The mddi_host_timer_service error in log dissapeared ... seems there are some problems is it stays in pmdh_clk_enable...
Tof37 said:
@mikeioannina
You should try this ...
in drivers/video/msm/mddi.c
in void pmdh_clk_enable() you've got
PHP:
if (mddi_host_timer.function)
mddi_host_timer_service(0);
In my .32 video drivers this if is in static int mddi_resume ...
Try to get the the above function like this :
PHP:
static int mddi_resume(struct platform_device *pdev)
{
mddi_host_type host_idx = MDDI_HOST_PRIM;
if (!mddi_is_in_suspend)
return 0;
mddi_is_in_suspend = 0;
if (mddi_power_locked)
return 0;
pmdh_clk_enable();
mddi_host_reg_out(PAD_CTL, mddi_pad_ctrl);
[B]if (mddi_host_timer.function)
mddi_host_timer_service(0);[/B]
return 0;
}
The mddi_host_timer_service error in log dissapeared ... seems there are some problems is it stays in pmdh_clk_enable...
Click to expand...
Click to collapse
that did nothing, still getting the same error...
mikeioannina said:
that did nothing, still getting the same error...
Click to expand...
Click to collapse
Have to solve a |kgsl_mh_intrcallback| axi read error interrupt: error in my kernel and will take a more attentive look to 3.4 video drivers .
Stay tuned
btw if you ever have a solution for my problem
Thanks
mikeioannina said:
Code:
[ 8.994812]
[ 8.995025] WARNING: at /home/mike/android/cm10.1/kernel/semc/msm7x30/kernel/mutex.c:198 __mutex_lock_slowpath+0x70/0x27c()
Click to expand...
Click to collapse
I'm going to just throw this out, is it possible that you are building a kernel for CM10.1 and booting it on CM11 ?
I started getting random reboots a few weeks ago. I cant tie it to any app in particular and my phone doesnt seem to be getting hot. I thought maybe unlocking the bootloader and flashing a custom rom might help so i flashed CM13 and it seemed to get more frequent and it would almost go into a bootloop that i could only stop by going into recovery and rebooting that way. I eventually flashed stock lollipop back onto it and it slowed down to every once in a while and didnt do the bootloop thing anymore. I did a logcat through ADB but i dont know how to interperet it. Could anyone help?
Code:
[ 03-21 20:30:54.246 1429: 1429 D/KeyguardViewMediator ]
handleMessage dt = 0
[ 03-21 20:30:54.249 16086:16086 I/View ]
ssignParent(ViewParent parent) parent is: com.android.mail.ui.SwipeableListView{262fdc16 VFED.VCL .F....ID 0,0-720,1022 #7f0f0194 app:id/conversation_list_view}
[ 03-21 20:30:54.270 1964: 1982 I/HwSystemManager ]
HoldService:callUid: 10009 notificationType: false
[ 03-21 20:30:54.270 1964: 1982 I/HwSystemManager ]
HoldService:pkgName[0]: com.google.android.backuptransport identity: 42988327681828
[ 03-21 20:30:54.276 876: 891 V/SMCSAMSHelper ]
SMCSAMSHelper.addSTPEvent: cost 0 ms end.
[ 03-21 20:30:54.276 876: 891 V/SMCSAMSHelper ]
SMCSAMSHelper.smartTrimAddProcessRelation: cost 0 ms end.
[ 03-21 20:30:54.280 16164:16315 I/PG Utils ]
acquire_provider pkg:[com.android.providers.contacts] pid:[] send to pg
[ 03-21 20:30:54.296 1964: 2071 I/HwSystemManager ]
HoldService:callUid: 10009 notificationType: false
[ 03-21 20:30:54.297 1964: 2071 I/HwSystemManager ]
HoldService:pkgName[0]: com.google.android.backuptransport identity: 42988327681828
[ 03-21 20:30:54.298 876: 1508 V/SMCSAMSHelper ]
SMCSAMSHelper.addSTPEvent: cost 0 ms end.
[ 03-21 20:30:54.298 876: 1508 V/SMCSAMSHelper ]
SMCSAMSHelper.smartTrimAddProcessRelation: cost 0 ms end.
[ 03-21 20:30:54.301 16164:16315 I/PG Utils ]
acquire_provider pkg:[com.android.providers.contacts] pid:[] send to pg
That was the last of what it picked up before it rebooted. Any ideas?
I too am getting a sudden burst of rebooting after rooting my phone while on B322. I am working on removing apps one at a time though I do not think this to be the issue.
Hi there,
It's my first post here, I landed here a lot of times and always found answers to my questions, many thanks to this community. I hope my frenchglish remains understandable.
The problem is that my poco F1 crashes randomly. I get a black, sometimes blue screen and then the device reboots to the OS normally, without any loop.
It can happen after 10 seconds or 1 hour and I cannot detect what is causing these crashes. Maybe something related to wifi.
How can I investigate to find a clue ?
About the device :
- I bought it used, already unlocked
- I tried with /e/, CalyxOS (2.7.0 and 2.9.0), and with miui (flashed with MiFlash)
- I tried several firmware versions
- I don't see anything relevant in logcat last messages, a lot of errors but different at each crash
There are these errors that are happening a lot of time, but I don't know if it's the cause because they seem to happen constantly :
- CANNOT LINK EXECUTABLE "/vendor/bin/wifidisplayhalservice": library "libwfdaac_vendor.so" not found: needed by /vendor/lib/libwfdmmsrc_proprietary.so in namespace (default) (300 lines over 20mn)
- W libperfmgr: Failed to write to node: /proc/sys/kernel/sched_boost with value: 0, fd: -1 (500 lines over 20mn)
In dmesg, I have tons of these :
[ 176.525217] [schedu][3448610271][14:31:06.270389] wlan: [2652:E:WMI] Service id 258 but WMI ext2 service bitmap is NULL
[ 177.161869] init: starting service 'wifidisplayhalservice'...
[ 177.179652] init: Service 'wifidisplayhalservice' (pid 4373) exited with status 1
[ 177.179670] init: Sending signal 9 to service 'wifidisplayhalservice' (pid 4373) process group...
[ 177.179785] libprocessgroup: Successfully killed process cgroup uid 1000 pid 4373 in 0ms
[ 179.562273] [schedu][3506921340][14:31:09.307424] wlan: [2652:E:WMI] Service id 258 but WMI ext2 service bitmap is NULL
[ 179.562296] [schedu][3506922166][14:31:09.307467] wlan: [2652:E:WMI] Service id 258 but WMI ext2 service bitmap is NULL
[ 179.562314] [schedu][3506922495][14:31:09.307484] wlan: [2652:E:WMI] Service id 258 but WMI ext2 service bitmap is NULL
If anyone has an idea to solve these crashes, some ways to reproduce the crash, test hardware, how to get relevant logs...
Any help appreciated.
Same problem dude ?? Did u get the solution
heyhoy said:
Hi there,
It's my first post here, I landed here a lot of times and always found answers to my questions, many thanks to this community. I hope my frenchglish remains understandable.
The problem is that my poco F1 crashes randomly. I get a black, sometimes blue screen and then the device reboots to the OS normally, without any loop.
It can happen after 10 seconds or 1 hour and I cannot detect what is causing these crashes. Maybe something related to wifi.
How can I investigate to find a clue ?
About the device :
- I bought it used, already unlocked
- I tried with /e/, CalyxOS (2.7.0 and 2.9.0), and with miui (flashed with MiFlash)
- I tried several firmware versions
- I don't see anything relevant in logcat last messages, a lot of errors but different at each crash
There are these errors that are happening a lot of time, but I don't know if it's the cause because they seem to happen constantly :
- CANNOT LINK EXECUTABLE "/vendor/bin/wifidisplayhalservice": library "libwfdaac_vendor.so" not found: needed by /vendor/lib/libwfdmmsrc_proprietary.so in namespace (default) (300 lines over 20mn)
- W libperfmgr: Failed to write to node: /proc/sys/kernel/sched_boost with value: 0, fd: -1 (500 lines over 20mn)
In dmesg, I have tons of these :
[ 176.525217] [schedu][3448610271][14:31:06.270389] wlan: [2652:E:WMI] Service id 258 but WMI ext2 service bitmap is NULL
[ 177.161869] init: starting service 'wifidisplayhalservice'...
[ 177.179652] init: Service 'wifidisplayhalservice' (pid 4373) exited with status 1
[ 177.179670] init: Sending signal 9 to service 'wifidisplayhalservice' (pid 4373) process group...
[ 177.179785] libprocessgroup: Successfully killed process cgroup uid 1000 pid 4373 in 0ms
[ 179.562273] [schedu][3506921340][14:31:09.307424] wlan: [2652:E:WMI] Service id 258 but WMI ext2 service bitmap is NULL
[ 179.562296] [schedu][3506922166][14:31:09.307467] wlan: [2652:E:WMI] Service id 258 but WMI ext2 service bitmap is NULL
[ 179.562314] [schedu][3506922495][14:31:09.307484] wlan: [2652:E:WMI] Service id 258 but WMI ext2 service bitmap is NULL
If anyone has an idea to solve these crashes, some ways to reproduce the crash, test hardware, how to get relevant logs...
Any help appreciated.
Click to expand...
Click to collapse
maxpayne_69 said:
Same problem dude ?? Did u get the solution
Click to expand...
Click to collapse
Have you tried flashing persist partition? (you can find it at XIaomi Tools at in my collection)
Also did you tried to flash stock firmware according my guide? You can find all the guid in my POCO F1 Ultimate Collection & Guides.
maxpayne_69 said:
Same problem dude ?? Did u get the solution
Click to expand...
Click to collapse
Hi,
Nope. I changed the battery, it didn't solve anything but I read in several posts that it fixed the problem.
I also removed the mobo, put it in the oven. It was supposed to check if some soldering would be defective. It didn't solve anything.
I finally cancelled, I may try again later. I think it's a hardware issue.
Retrial said:
Have you tried flashing persist partition? (you can find it at XIaomi Tools at in my collection)
Also did you tried to flash stock firmware according my guide? You can find all the guid in my POCO F1 Ultimate Collection & Guides.
Click to expand...
Click to collapse
I'm not sure about persist partition. I flashed several times, with several firmwares and several roms. Is it part of these processes ?
I follow guides step by step without a good knowing of android, so I may have done a persist partition flash.
Thanks for this awesome collection anyway, the most things I did came from it.