[Q&A] CyanogenMod 12 - Lollipop - Pre-Nightly Shakeout

Sleeepy2

Senior Member
Dec 9, 2009
1,028
197
0
Toronto
Nice. Thanks for all your work and effort.
@pershoot I just got a chance to try my USB. There is no notification to unmount the usb however going to Settings > Storage it does allow you to unmount correctly. Once it is unmounted I get a notification to remount.
I do have a list of 9 different USB storage devices in the Settings > Storage, my actual USB is listed as the 3rd one. Not a big deal as it works correctly just something to take a look at if you get a chance.

I also had an issue with my bluetooth headset, everything sounded like the chipmunks :) I did unpair and re-pair however I still had the issue. I didn't get a chance to reboot and test again and I don't have it with me at work, I will try it again when I get a chance.

Thanks again
 
Last edited:

K94U

Senior Member
Mar 1, 2015
67
14
0
Stock 442 miracast connection log

I haven't looked at your log as of yet. but please only post the one from the device that is known working against stock.

Please also post a log from stock of it working.

Thx.
Here is the log file for the working miracast connection to the LG TV using stock 11.4.1.29 442 This file goes with the other log file I posted for the LG TV for CM12 on page 2. I was able to connect to the TV without problems twice in a row. This log file has one full connection and disconnect. Thanks!
 

Attachments

Last edited:

pershoot

Inactive Recognized Developer
Dec 1, 2008
7,969
4,339
243
Nice. Thanks for all your work and effort.
@pershoot
I do have a list of 9 different USB storage devices in the Settings > Storage, my actual USB is listed as the 3rd one. Not a big deal as it works correctly just something to take a look at if you get a chance.
That is done on purpose for the interim. In stock, they wrote a custom vold to manage the various interfaces and provide one access place for it.
 

pershoot

Inactive Recognized Developer
Dec 1, 2008
7,969
4,339
243
Here is the log file for the working miracast connection to the LG TV using stock 11.4.1.29 442 This file goes with the other log file I posted for the LG TV for CM12 on page 2. I was able to connect to the TV without problems twice in a row. This log file has one full connection and disconnect. Thanks!
can you please run a quick test on cm12 by binding static IPs to tv|dongle/tab, re-try and post logs?

does miracast work on CM11?

Thanks.
 

K94U

Senior Member
Mar 1, 2015
67
14
0
results....

can you please run a quick test on cm12 by binding static IPs to tv|dongle/tab, re-try and post logs?

does miracast work on CM11?

Thanks.
So, miracast acts the same way on cm 11 as cm 12!I have tried binding and unbinding... And there's no positive outcome.! As I read over the log file although I see some issues. can you debug this little issue for all of us?

03-26 01:57:14.350 1367 1433 I WifiDisplayController: Connected to Wifi display: Roku Streaming Stick - 407

03-26 01:57:14.350 1367 1433 I WifiDisplayController: Stopping Wifi display scan.

03-26 01:57:14.354 1367 1433 I WifiDisplayController: Listening for RTSP connection on 172.29.243.227:7236 from Wifi display: Roku Streaming Stick - 407

03-26 01:57:14.356 1367 1433 I ExtendedRemoteDisplayHelper: ExtendedRemoteDisplay Not available.

03-26 01:57:14.356 1367 1433 I ExtendedRemoteDisplayHelper: ExtendedRemoteDisplay isAvailable() : Not Available.

03-26 01:57:14.717 1367 1392 W ActivityManager: getRecentTasks: caller 10081 does not hold GET_TASKS; limiting output

03-26 01:57:16.717 1367 1393 W ActivityManager: getRecentTasks: caller 10081 does not hold GET_TASKS; limiting output

03-26 01:57:18.717 1367 2566 W ActivityManager: getRecentTasks: caller 10081 does not hold GET_TASKS; limiting output

03-26 01:57:20.717 1367 2395 W ActivityManager: getRecentTasks: caller 10081 does not hold GET_TASKS; limiting output

03-26 01:57:21.134 549 11885 I NetworkSession: incoming connection from 172.29.243.225:47792 (socket 20)

03-26 01:57:21.135 549 11885 I NetworkSession: added clientSession 2

03-26 01:57:21.136 549 11886 I WifiDisplaySource: We now have a client (2) connected.

03-26 01:57:21.208 549 11886 I WifiDisplaySource: Picked video resolution 1280 x 720 p30

03-26 01:57:21.208 549 11886 I WifiDisplaySource: Picked AVC profile 1, level 1

03-26 01:57:21.209 549 11886 I WifiDisplaySource: Using AAC audio.

03-26 01:57:21.216 549 11886 E HDCP : Unable to locate libstagefright_hdcp.so

03-26 01:57:21.216 549 11886 E WifiDisplaySource: Failed to set HDCP observer.

03-26 01:57:21.216 549 11886 E WifiDisplaySource: Unable to instantiate HDCP component. Not using HDCP after all.

03-26 01:57:21.256 549 11886 I Converter: using audio bitrate of 128000 bps, video bitrate of 5000000 bps

03-26 01:57:21.257 549 11950 E OMXNodeInstance: OMX_SetParameter() failed for StoreMetaDataInBuffers: 0x80001005

03-26 01:57:21.257 549 11950 E ACodec : [OMX.Nvidia.h264.encoder] storeMetaDataInBuffers (output) failed w/ err -2147483648

03-26 01:57:21.257 549 11950 W ACodec : do not know color format 0x7f000789 = 2130708361

03-26 01:57:21.257 549 11950 E OMXNodeInstance: setParameter(100663302) ERROR: 0x80001006

03-26 01:57:21.257 549 11950 E ACodec : Setting intra macroblock refresh mode (-2147483648) failed: 0x0

03-26 01:57:21.257 549 11950 I ACodec : [OMX.Nvidia.h264.encoder] setupVideoEncoder failed

03-26 01:57:21.257 549 11950 E ACodec : [OMX.Nvidia.h264.encoder] configureCodec returning error -2147483648

03-26 01:57:21.257 549 11950 E ACodec : signalError(omxError 0x80001001, internalError -2147483648)

03-26 01:57:21.259 549 11949 E MediaCodec: Codec reported err 0x80001001, actionCode 0, while in state 3

03-26 01:57:21.259 549 11886 E MediaCodec: configure failed with err 0x80001001, resetting...

03-26 01:57:21.267 549 11886 I Converter: We going to manually prepend SPS and PPS to IDR frames.

03-26 01:57:21.268 549 11950 E OMXNodeInstance: OMX_SetParameter() failed for StoreMetaDataInBuffers: 0x80001005

03-26 01:57:21.268 549 11950 E ACodec : [OMX.Nvidia.h264.encoder] storeMetaDataInBuffers (output) failed w/ err -2147483648

03-26 01:57:21.268 549 11950 W ACodec : do not know color format 0x7f000789 = 2130708361

03-26 01:57:21.268 549 11950 E OMXNodeInstance: setParameter(100663302) ERROR: 0x80001006

03-26 01:57:21.268 549 11950 E ACodec : Setting intra macroblock refresh mode (-2147483648) failed: 0x0

03-26 01:57:21.268 549 11950 I ACodec : [OMX.Nvidia.h264.encoder] setupVideoEncoder failed

03-26 01:57:21.268 549 11950 E ACodec : [OMX.Nvidia.h264.encoder] configureCodec returning error -2147483648

03-26 01:57:21.268 549 11950 E ACodec : signalError(omxError 0x80001001, internalError -2147483648)

03-26 01:57:21.269 549 11949 E MediaCodec: Codec reported err 0x80001001, actionCode 0, while in state 3

03-26 01:57:21.270 549 11886 E MediaCodec: configure failed with err 0x80001001, resetting...

03-26 01:57:21.281 549 11886 E PlaybackSession: video converter returned err -2147479551

03-26 01:57:21.282 1367 1433 I WifiDisplayController: Lost RTSP connection with Wifi display due to error 1: Roku Streaming Stick - 407

03-26 01:57:21.282 1367 1433 I WifiDisplayController: Wifi display connection failed!

03-26 01:57:21.741 549 11885 E NetworkSession: readMore on socket 20 failed w/ error -104 (Connection reset by peer)

03-26 01:57:21.743 549 11886 E WifiDisplaySource: An error occurred in session 2 (-104, 'Recv failed./Connection reset by peer').

03-26 01:57:21.746 1367 1433 I WifiDisplayController: Lost RTSP connection with Wifi display due to error 1: Roku Streaming Stick - 407

03-26 01:57:21.746 1367 1433 I WifiDisplayController: Wifi display connection failed!

And then...?

---------- Post added at 05:15 AM ---------- Previous post was at 04:26 AM ----------

in cm12, I get this reoccurring fault in the log file. any help to rectify the situation?
ActivityManager: getRecentTasks: caller 10081 does not hold GET_TASKS; limiting output
 
Last edited:

pencilmonkey

Member
Oct 11, 2010
7
0
0
Quick question on a battery issue

I'm using the Lollipop rom and loving it, one of the best I've had. One thing I've seen on my system that's come on very suddenly is that even when I leave the TF701T on charge it never goes above a 6% charge....is there anything I can do short of replacing the battery? I'm wondering if the battery stats are off or if this is something fixable without cracking the shell.
Any help anybody could provide would be greatly appreciated.

Quick edit here - after some testing, it also doesn't seem to be going below 6% when off the charger...I'm sure the battery is draining at that point, it's just that nothing is reporting the change.
 
Last edited:

K94U

Senior Member
Mar 1, 2015
67
14
0
Hola...

It sounds like you did a dirty flash, lol! :D Do a fresh backup from recovery from whatever platform you're on, then go into recovery and do a complete format, except for your SD card unless you want to wipe it also, and then go into advanced and do a dalvik wipe. then install your new ROM! Or you can go back to stock... :cool:

If this does not help, then it sounds like you have an internal issue... :(
 
Last edited:

pencilmonkey

Member
Oct 11, 2010
7
0
0
It sounds like you did a dirty flash, lol! :D Do a fresh backup from recovery from whatever platform you're on, then go into recovery and do a complete format, except for your SD card unless you want to wipe it also, and then go into advanced and do a dalvik wipe. then install your new ROM! Or you can go back to stock... :cool:

If this does not help, then it sounds like you have an internal issue... :(
I think it's an internal issue, at this point.
Wasn't a dirty flash, I had been running Pershoot's rom for months with no problems, even occasionally doing a clean wipe and reinstall from time to time....it's just really, really odd. The battery doesn't ever charge above 6% but then again doesn't ever fall under 6% when off charge...so I really think whatever reports battery charge is borked.
Ah well, not a dealbreaker for me right now, as I still use the tablet a great deal and don't want to replace it just yet.
 

erzherzog

Senior Member
Mar 6, 2015
86
27
38
CM recovery

The CM recovery.img coming with 12-20150408-UNOFFICIAL-tf701t doesn't see the tablets external Micro-SD-Card. Therefore I think, it's better to keep CWM-Recovery 6.0.5.1 installed.