Please analyze this logcat - Android Q&A, Help & Troubleshooting

My games keeps closing on me (Candy Crush and Candy Crush Soda Saga in particular). I've attached a logcat, I just want to know pleae if it is my phones fault or the apps. Hope you can help thank you.
------------------------------------------------------------------------------------------
11-12 17:54:14.668 E/InputDispatcher(233): channel '40802590 com.king.candycrushsodasaga/com.king.candycrushsodasaga.StritzActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x8
11-12 17:54:14.668 E/InputDispatcher(233): channel '40802590 com.king.candycrushsodasaga/com.king.candycrushsodasaga.StritzActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
11-12 17:54:14.718 I/ActivityManager(233): Process com.king.candycrushsodasaga (pid 30275) has died.
11-12 17:54:14.808 I/WindowManager(233): WIN DEATH: Window{40802590 com.king.candycrushsodasaga/com.king.candycrushsodasaga.StritzActivity paused=false}
-----------------------------------------------------------------------------------------------

Related

HBO GO app released - not working on CM7?

Seems to force close when trying to log in. Is anyone else having better luck?
Sent from my NookColor using XDA Premium App
djhotpocket said:
Seems to force close when trying to log in. Is anyone else having better luck?
Sent from my NookColor using XDA Premium App
Click to expand...
Click to collapse
Yeah, saw this posted on Engadget and so I downloaded it. Had to sign up on the web, as trying to create a new account in the app itself gave me FCs. When I click on Menu > Signin, then it FCs right away.
I see where the permissions requires phone access and right now, through the use of the Bloat Freezer app, my Dialer is "frozen" and therefore not accessible by any apps.
Do you have your Dialer intact? If so, then I won't bother going down that troubleshooting path.
Works perfect on my Droid X...watching Terminator Salvation right now.
djhotpocket said:
Seems to force close when trying to log in. Is anyone else having better luck?
Sent from my NookColor using XDA Premium App
Click to expand...
Click to collapse
Mine is doing the same thing. It force closes when I click on either sign up or sign in. It is a shame because I would consider keeping HBO after my free trial is up if this worked.
I can't even find the .apk on my NC....I don't see it in /Data/App or /System/App.
I ran "Fix Permissions" within ROM Manager and that didn't help, as still getting FCs when trying to login.
Looks darn good on my DX, so hoping we can get it running on the NC.
Same here. FC's on either sign in or sign up. CM7 Nightly 41 IIRC.
This is what I am getting from my NC (CM7.02 & 4/24 OC Kernel)
Unfortunately, makes no sense to me as to what could be the problem...or, more importantly, the fix.
Anyone?
Code:
C:\>adb logcat
W/KeyCharacterMap( 4914): No keyboard for id 0
W/KeyCharacterMap( 4914): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
I/ActivityManager( 1001): Starting: Intent { cmp=com.HBO/.TelevisionProvider } from pid 4914
D/AndroidRuntime( 4914): Shutting down VM
W/dalvikvm( 4914): threadid=1: thread exiting with uncaught exception (group=0x40015560)
E/AndroidRuntime( 4914): FATAL EXCEPTION: main
E/AndroidRuntime( 4914): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.HBO/com.HBO.TelevisionProvider}: java.lang.NullPointerException
E/AndroidRuntime( 4914): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1768)
E/AndroidRuntime( 4914): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1784)
E/AndroidRuntime( 4914): at android.app.ActivityThread.access$1500(ActivityThread.java:123)
E/AndroidRuntime( 4914): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:939)
E/AndroidRuntime( 4914): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 4914): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 4914): at android.app.ActivityThread.main(ActivityThread.java:3835)
E/AndroidRuntime( 4914): at java.lang.reflect.Method.invokeNative(NativeMethod)
E/AndroidRuntime( 4914): at java.lang.reflect.Method.invoke(Method.java:507)
E/AndroidRuntime( 4914): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
E/AndroidRuntime( 4914): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
E/AndroidRuntime( 4914): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 4914): Caused by: java.lang.NullPointerException
E/AndroidRuntime( 4914): at com.HBO.Utils.LoginUtils.getDeviceID(LoginUtils.java:517)
E/AndroidRuntime( 4914): at com.HBO.TelevisionProvider.onCreate(TelevisionProvider.java:114)
E/AndroidRuntime( 4914): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
E/AndroidRuntime( 4914): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1722)
E/AndroidRuntime( 4914): ... 11 more
W/ActivityManager( 1001): Force finishing activity com.HBO/.TelevisionProvider
W/ActivityManager( 1001): Force finishing activity com.HBO/.Home
W/ActivityManager( 1001): Activity pause timeout for HistoryRecord{40a31b90 com.HBO/.TelevisionProvider}
I/Process ( 4914): Sending signal. PID: 4914 SIG: 9
E/InputDispatcher( 1001): channel '40941f18 com.HBO/com.HBO.HBO (server)' ~ Consumer closed input channel or an error occurred. events=0x8
E/InputDispatcher( 1001): channel '40941f18 com.HBO/com.HBO.HBO (server)' ~ Channel is unrecoverably broken and will be disposed!
I/WindowManager( 1001): WINDOW DIED Window{40941f18 com.HBO/com.HBO.HBO paused=false}
E/InputDispatcher( 1001): channel '409addd8 com.HBO/com.HBO.Home (server)' ~ Consumer closed input channel or an error occurred. events=0x8
E/InputDispatcher( 1001): channel '409addd8 com.HBO/com.HBO.Home (server)' ~ Channel is unrecoverably broken and will be disposed!
I/WindowManager( 1001): WINDOW DIED Window{409addd8 com.HBO/com.HBO.Home paused=true}
I/ActivityManager( 1001): Process com.HBO (pid 4914) has died.
I/WindowManager( 1001): WIN DEATH: Window{409addd8 com.HBO/com.HBO.Home paused=true}
W/InputManagerService( 1001): Got RemoteException sending setActive(false) notification to pid 4914 uid 10139
HBO Go does work through the browser. I too am getting the fc through the app. But at least the browser is an option till the app is figured out.
360Razir said:
I can't even find the .apk on my NC....I don't see it in /Data/App or /System/App.
I ran "Fix Permissions" within ROM Manager and that didn't help, as still getting FCs when trying to login.
Looks darn good on my DX, so hoping we can get it running on the NC.
Click to expand...
Click to collapse
How did you get it on the Droid X, it wont show up in market for me on mind. I am running Gingerbread rom.
Modra76 said:
HBO Go does work through the browser. I too am getting the fc through the app. But at least the browser is an option till the app is figured out.
Click to expand...
Click to collapse
What browser? Opera doesn't seem to be letting me sign in. I sign in, but when it takes me back to the page, nothing seems to have registered..
Divine_Madcat said:
What browser? Opera doesn't seem to be letting me sign in. I sign in, but when it takes me back to the page, nothing seems to have registered..
Click to expand...
Click to collapse
I'm using Dolphin HD with the desktop toggle plugin (allows you to view full websites instead of mobile version). It seems to work ok. A little choppy. But I'm putting that to a poor 3G signal to my phone with tethering on to allow my nook to get wifi. It's been working great on my EVO when the 3G is working.
****** FOR THOSE HAVING ISSUES WITH THE APP****************
You need the Skype fix posted here:
http://forum.xda-developers.com/showthread.php?t=1004102&highlight=Swype
HBO Go is look for an IMEI, which our Nooks do not natively support (to the person who posted the logcat, thank you; that was able to tell me where the error was). Using the patched Framework.jar, i can now log in...
Thanks to the creator of the patched framework!
Edit: Dangit Madcat! Beat me to it! I was busy taking screenshots and stuff!
360Razir said:
This is what I am getting from my NC (CM7.02 & 4/24 OC Kernel)
Unfortunately, makes no sense to me as to what could be the problem...or, more importantly, the fix.
Anyone?
Click to expand...
Click to collapse
The issue with this seems to be the app calling for a valid IMEI#. Where-as CM7 reports it as "null". And when it attempts to send out a signal to their server. It errors out and FC's. See below in red where the function happens:
Code:
E/AndroidRuntime( 2078): Caused by: java.lang.NullPointerException[COLOR="DarkRed"][B]
E/AndroidRuntime( 2078): at com.HBO.Utils.LoginUtils.getDeviceID(LoginUtils.java:517)[/B][/COLOR]
E/AndroidRuntime( 2078): at com.HBO.TelevisionProvider.onCreate(TelevisionProvider.java:114)
E/AndroidRuntime( 2078): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
E/AndroidRuntime( 2078): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1722)
E/AndroidRuntime( 2078): ... 11 more
W/ActivityManager( 1041): Force finishing activity com.HBO/.TelevisionProvider
D/dalvikvm( 2078): GC_CONCURRENT freed 150K, 51% free 2779K/5575K, external 625K/1061K, paused 3ms+4ms
I/dalvikvm( 2078): Uncaught exception thrown by finalizer (will be discarded):
I/dalvikvm( 2078): Ljava/lang/NullPointerException;:
I/dalvikvm( 2078): at com.omniture.AppMeasurementBaseSE13.finalize(AppMeasurementBaseSE13.java:43)
I/dalvikvm( 2078): at dalvik.system.NativeStart.run(Native Method)
I/dalvikvm( 2078): Uncaught exception thrown by finalizer (will be discarded):
I/dalvikvm( 2078): Ljava/lang/NullPointerException;:
I/dalvikvm( 2078): at com.omniture.AppMeasurementBaseSE13.finalize(AppMeasurementBaseSE13.java:43)
I/dalvikvm( 2078): at dalvik.system.NativeStart.run(Native Method)
W/KeyCharacterMap( 1041): Can't open keycharmap file
W/KeyCharacterMap( 1041): Error loading keycharmap file '/system/usr/keychars/cyttsp-i2c.kcm.bin'. hw.keyboards.65537.devname='cyttsp-i2c'
W/KeyCharacterMap( 1041): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
W/ActivityManager( 1041): Activity pause timeout for HistoryRecord{407cb330 com.HBO/.TelevisionProvider}
I/dalvikvm( 1041): Jit: resizing JitTable from 4096 to 8192[B][COLOR="DarkRed"]
I/Process ( 2078): Sending signal. PID: 2078 SIG: 9
I/WindowManager( 1041): WIN DEATH: Window{406c6d30 com.HBO/com.HBO.HBO paused=false}[/COLOR][/B]
I/ActivityManager( 1041): Process com.HBO (pid 2078) has died.
I/WindowManager( 1041): WIN DEATH: Window{407c5168 com.HBO/com.HBO.WelcomePage paused=false}
W/InputManagerService( 1041): Got RemoteException sending setActive(false) notification to pid 2078 uid 10049
Only way around this is a framework hack where you insert your own IMEI#. I attempted it with the regular CM7 framework and received the same error. Then I replaced the CM7 framework with my hacked framework. Rebooted and I'm able to sign in. See pic below.
This issue has been brought up many times before, but hasn't been resolved as of yet.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Divine_Madcat said:
****** FOR THOSE HAVING ISSUES WITH THE APP****************
You need the Skype fix posted here:
http://forum.xda-developers.com/showthread.php?t=1004102&highlight=Swype
HBO Go is look for an IMEI, which our Nooks do not natively support (to the person who posted the logcat, thank you; that was able to tell me where the error was). Using the patched Framework.jar, i can now log in...
Thanks to the creator of the patched framework!
Click to expand...
Click to collapse
Did you have to do all the steps outlined in that post or just download and install the patched framework.jar that is attached?
Divine_Madcat said:
****** FOR THOSE HAVING ISSUES WITH THE APP****************
You need the Skype fix posted here:
http://forum.xda-developers.com/showthread.php?t=1004102&highlight=Swype
HBO Go is look for an IMEI, which our Nooks do not natively support (to the person who posted the logcat, thank you; that was able to tell me where the error was). Using the patched Framework.jar, i can now log in...
Thanks to the creator of the patched framework!
Click to expand...
Click to collapse
Good, I wasn't sure what the logcats were driving at, so thanks for deciphering it.
I am on 7.02, so I am not sure if that Framework.jar works for 7.02, as it was last updated 4/23 and 7.02 dropped on 4/25?
Does it change anything else that I should be concerned about (I am using the Sense Settings Mod and also the Mau5 Tablet Theme...d'ld from Market).
janko10 said:
Did you have to do all the steps outlined in that post or just download and install the patched framework.jar that is attached?
Click to expand...
Click to collapse
I just used the patch framework jar.
However, i dont know how out of date it is.. we may want to make a new one that is truly from 7.0.2...
Divine_Madcat said:
I just used the patch framework jar.
However, i dont know how out of date it is.. we may want to make a new one that is truly from 7.0.2...
Click to expand...
Click to collapse
Nevermind...reading thru the Framework thread you posted, Post #29 has the 7.02 file we need....thanks to mthe0ry and knaries2000 for their work on this! Thanks Madcat for bringing this to our attention and getting it to work.
EDIT: added file
Divine_Madcat said:
I just used the patch framework jar.
However, i dont know how out of date it is.. we may want to make a new one that is truly from 7.0.2...
Click to expand...
Click to collapse
Hey Madcat,
Would you by any chance know if the servers would store the IMEI with login info. And if that would cause any issues with future logins if X number of people are reporting the same IMEI#?
My thought is it would be better if everyone created their own unique number. Just a thought.
thanks,
Racks
Divine_Madcat said:
****** FOR THOSE HAVING ISSUES WITH THE APP****************
You need the Skype fix posted here:
http://forum.xda-developers.com/showthread.php?t=1004102&highlight=Swype
HBO Go is look for an IMEI, which our Nooks do not natively support (to the person who posted the logcat, thank you; that was able to tell me where the error was). Using the patched Framework.jar, i can now log in...
Thanks to the creator of the patched framework!
Click to expand...
Click to collapse
Thanks Madcat for the find. It allows me to sign in now. Now I just need to get somewhere that has decent 3g service so I can tether or get home to the wifi.
racks11479 said:
Hey Madcat,
Would you by any chance know if the servers would store the IMEI with login info. And if that would cause any issues with future logins if X number of people are reporting the same IMEI#?
My thought is it would be better if everyone created their own unique number. Just a thought.
thanks,
Racks
Click to expand...
Click to collapse
That is a good question. Sadly, no, i have no clue at all.... :-s
racks11479 said:
Hey Madcat,
Would you by any chance know if the servers would store the IMEI with login info. And if that would cause any issues with future logins if X number of people are reporting the same IMEI#?
My thought is it would be better if everyone created their own unique number. Just a thought.
thanks,
Racks
Click to expand...
Click to collapse
Good idea, but would that involve using smali and baksmali to assemble/disassemble?

[Q] Uploading to Google My Tracks

Hi,
I was just wondering if anyone with the SGS II has managed to upload their tracks to Google maps? Every time I try it just waits at the authenticating to Google Maps screen without ever uploading anything. If I try on my old SGS it still works fine so it looks like it's just the SGS II that has the problem.
I did read elsewhere that it could be to do with the phone not having the default language set to english, but I have checked the phone and the default language is set to english, so I'm stumped. Any suggestions?
Same problem here
tracks been posted in GPS thread so guess its at your end .
jje
JJEgan said:
tracks been posted in GPS thread so guess its at your end .
jje
Click to expand...
Click to collapse
I think they are being imported rather than uploaded using the sgs2 as that's the only way I can do it, although I could be wrong (and usually am)
Would be good to hear if anyone had successfully uploaded via the phone.
Same issue here.
Tested and tracks stick at 0 in the uploading window . However my SGS 1 did that at times as well ..
jje
Same problem here too. Had to import tracks manually.
Same problem for me. There seems to be a problem with certain apps accessing my google account for authentication.
If I plug my phone into the PC and watch the console in eclipse I can see in the system logs there is some kind of authentication exception that isn't being handled properly when you try to upload a track.
This affects My Tracks, Andlytics and probably anything else that uses your google account in the same way.
Same problem here, seems to be a bug, the SGS still uploads.
Yep, same problem here.
This is the logcat when I press the "Send now" button:
Code:
I/InputReader( 2680): dispatchTouch::touch event's action is 0
I/InputDispatcher( 2680): Delivering touch to current input target: action: 0, channel '40ab6058 com.google.android.maps.mytracks/com.google.android.apps.mytracks.MyTracks (server)'
I/InputReader( 2680): dispatchTouch::touch event's action is 1
I/InputDispatcher( 2680): Delivering touch to current input target: action: 1, channel '40ab6058 com.google.android.maps.mytracks/com.google.android.apps.mytracks.MyTracks (server)'
D/MyTracks(15555): Logging in to local...
E/JavaBinder( 2680): *** Uncaught remote exception! (Exceptions are not yet supported across processes.)
E/JavaBinder( 2680): java.lang.StringIndexOutOfBoundsException
E/JavaBinder( 2680): at java.lang.String.substring(String.java:1651)
E/JavaBinder( 2680): at android.accounts.AccountManagerService.createNoCredentialsPermissionNotification(AccountManagerService.java:944)
E/JavaBinder( 2680): at android.accounts.AccountManagerService.doNotification(AccountManagerService.java:1803)
E/JavaBinder( 2680): at android.accounts.AccountManagerService.access$300(AccountManagerService.java:79)
E/JavaBinder( 2680): at android.accounts.AccountManagerService$2.onResult(AccountManagerService.java:917)
E/JavaBinder( 2680): at android.accounts.AccountManagerService$2.onResult(AccountManagerService.java:899)
E/JavaBinder( 2680): at android.accounts.IAccountAuthenticatorResponse$Stub.onTransact(IAccountAuthenticatorResponse.java:59)
E/JavaBinder( 2680): at android.os.Binder.execTransact(Binder.java:320)
E/JavaBinder( 2680): at com.android.server.SystemServer.init1(Native Method)
E/JavaBinder( 2680): at com.android.server.SystemServer.main(SystemServer.java:807)
E/JavaBinder( 2680): at java.lang.reflect.Method.invokeNative(Native Method)
E/JavaBinder( 2680): at java.lang.reflect.Method.invoke(Method.java:507)
E/JavaBinder( 2680): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:847)
E/JavaBinder( 2680): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:605)
E/JavaBinder( 2680): at dalvik.system.NativeStart.main(Native Method)
It's an unhandled exception in some non-MyTracks code.
Does this work for anyone yet?
Er NO thats why we is still posting it dont work .
jje
To view your tracks you can export them as KMLs, then upload the KML to somewhere online (I use Dropbox), copy the URL for where they are, then go to maps in your browser and paste the URL into the search bar. You can then see your tracks in Google Maps. Clunky, but at least can be done. I'm quite pleased with how the tracks are for me.
KML import to Google Earth works, too. Its a shame they cannot fix the upload, it's the same from WinPc.
ALexander
Reply from Samsung to my enquiry on the problem
06.05.2011 16:35:37
Customer reference number:
Email response ID:
Dear xxxx,
Thank you for contacting Samsung and I have pleasure in providing the
following assistance:
Regarding to your query, kindly be informed that you need to refresh the
software of the phone and that is by removing the SIM card and the
battery out of the phone and wait for 30 seconds and put them back in.
If this did not work, you would try to reset the software and that is by
going to applications>settings>privacy>factory data reset and if it
enquires you for a password it would be 0000.
Before doing reset to the software, please make sure that you will back
up the whole data on the phone as the reset will erase the whole data on
the phone.
If this did not work out , you need to visit our authorized service
center.Please click on the link below to guide you to the nearest
Service Centre that you can go to with the Proof of Purchase, by just
submitting your Post Code, and choosing Mobile Phones from the drop down
box:
http://www.samsung.com/uk/support/location/supportServiceLocation.do?pag
e=SERVICE.LOCATION
If the authorized service center is far away from you , you need to give
us a call in order to send your phone to book for you a service request
to get it repaired .
Please note that when you contact us:
http://www.samsung.com/uk/info/contactus.html
Samsung mobile: 0845 MSAMSUNG (67267864)
Monday - Saturday: 9am - 6pm
Sunday: CLOSED
You will need to provide our representatives with specific details on
the phone like: The Model number of the phone, as well as the Serial
number. This can be found, underneath the Bar Code when you remove the
battery off the back of the phone, and it begins with an “R”. This will
help us determine the warranty term on the phone.
If you require any further assistance, please contact Samsung again and
we will be more than happy to help.
Kind regards,
Heba Khaled
Online Support Team
Samsung Customer Support Centre
Copy and paste response from Samsung, what a crock of sh...
Same problem here. Any ideas of a fix??
Same problem here. Using the GPX or KML file won´t generate the nice resumee-gfx i guess, right?
Discussion on My Tracks development forum:
http://code.google.com/p/mytracks/issues/detail?id=255&q=samsung galaxy s 2&colspec=ID Type Component Status Priority Targeting Work Stars Owner Summary
Anybody else try setting the language to US English?

mediahub for galaxy player 5.0?

The only reason i bought the galaxy player was to be able to use the mediahub app to watch all the media that I own. Knowing that only Samsung android devices are capable to use the mediahub app I assumed that the galaxy player would have it. After all it is a galaxy product "high end".
Can someone please help me find a working apk for mediahub?
Thank you!
I read before purchasing that it is capable with an upgrade at a later time via OTA... but out of the box, no...Media Hub is not there.
I could be wrong, but very doubtful its available otherwise.
Good luck!
CJ
Sent from my MZ609 using Tapatalk
waldoelx7241 said:
The only reason i bought the galaxy player was to be able to use the mediahub app to watch all the media that I own. Knowing that only Samsung android devices are capable to use the mediahub app I assumed that the galaxy player would have it. After all it is a galaxy product "high end".
Can someone please help me find a working apk for mediahub?
Thank you!
Click to expand...
Click to collapse
Attached is the media hub app that I pulled from my Epic 4G phone.
Enjoy!!!
Jesse- is this confirmed working in The Galaxy Players?
Thanks for the apk, much appreciated!
cramjammer said:
Jesse- is this confirmed working in The Galaxy Players?
Thanks for the apk, much appreciated!
Click to expand...
Click to collapse
It installed ok, but I got "Unknown error" when tried to run it.
Jim
Yeah, kinda what i was afraid of...I'm gonna give it a try now. See if i can play around with it.
Thanks Jim.
CJ
Sent from my YP-G70 using xda premium
cramjammer said:
Yeah, kinda what i was afraid of...I'm gonna give it a try now. See if i can play around with it.
Thanks Jim.
CJ
Sent from my YP-G70 using xda premium
Click to expand...
Click to collapse
Hi,
You're welcome.
I didn't see anything in dmesg, but I didn't check that other log thing (I forget what it's called).
If you do get it working, please post back !
Jim
Jim-
Sorry for taking so long to respond...Kids, wife, life-in-general...gets in the way of my Android obsession!
First let me say I know enough to be dangerous, i.e.- ADB, Odin, rooting, flashing, etc. But as for development, reading and writing code, I'm not the guy. I've self-taught and used steps of others to educate myself. I just got done unlocking my Galaxy Nexus and rooting it. Great phone btw.
So, with that being said I haven't got too far with this. I used the apk from Jesse and it installed, but like you i got the same error msg. I went into Root Explorer and changed the permissions with still no luck. I used the Media Hub from my Vzw Galaxy Tab 10.1 too, (I figured why not...?) no luck either.
i'm not opposed to trying different ideas using my Galaxy Player for the greater good.
sorry, I know this didn't help much but I didn't want to leave you hangin.
CJ
cramjammer said:
Jim-
Sorry for taking so long to respond...Kids, wife, life-in-general...gets in the way of my Android obsession!
First let me say I know enough to be dangerous, i.e.- ADB, Odin, rooting, flashing, etc. But as for development, reading and writing code, I'm not the guy. I've self-taught and used steps of others to educate myself. I just got done unlocking my Galaxy Nexus and rooting it. Great phone btw.
So, with that being said I haven't got too far with this. I used the apk from Jesse and it installed, but like you i got the same error msg. I went into Root Explorer and changed the permissions with still no luck. I used the Media Hub from my Vzw Galaxy Tab 10.1 too, (I figured why not...?) no luck either.
i'm not opposed to trying different ideas using my Galaxy Player for the greater good.
sorry, I know this didn't help much but I didn't want to leave you hangin.
CJ
Click to expand...
Click to collapse
Hi,
Did you get the same error I got when you tried media hub from your Galaxy Tab ("unknown error")?
If so, it's hard to tell what's going on.
I know that awhile ago, I tried bringing over some APKs from my SGP5 to my Gtablet (the opposite of this thread), and some worked ok, and some failed for various reasons, including one (Artillery Defense) that gave a more specific license error. I think another one (Heavy Gunner 3D) just dies.
The log thing I mentioned is logcat. There're some apps on market that allow you to see logcat, which is I think more of a app-type logging (vs. dmesg, which is more system logging). Maybe try install one of these apps (aLogcat, I think is one of them), then try launching media hub, then look at the logcat, to see if there's anything apparent there.
Other than that, "unknown error" isn't very helpful, so not sure what to do if logcat doesn't show anything helpful.
Jim
Jim...I'll give this a run tonight or at work tomorrow morninh and see what the logcat shows. Maybe we can work through this one with a bit of luck.
Sent from my MZ609 using Tapatalk
ya i tried a few different apk's and all had the same error message. also my 5.0 kept messing up so I swapped it for a 4.0, I like it better actually.
Hi,
I finally had time to test and run logcat. This is the snippet from when I clicked Retry, then got the popup again:
Code:
I/PowerManagerService( 120): Ulight 3->7|0
D/LightsService( 120): BUTTON : 68
I/InputReader( 120): dispatchTouch::touch event's action is 1
I/InputDispatcher( 120): Delivering touch to current input target: action: 1, channel '409ad608 com.sdgtl.mediahub.spr/com.sdgtl.mediahub.spr.Main (server)'
D/VolumeCustomizer( 77): [VOL] getVolumetableIndex XAA
D/VolumeCustomizer( 77): [VOL] getVolumetableIndex mSelectindex 0, count[19]
D/AudioHardwareALSA( 77): Calling setDevice from write @..2348.
I/AudioHardwareALSA( 77): Initialized ALSA PLAYBACK device AndroidPlayback_Speaker_normal
D/AudioHardwareALSA( 77): Using 2 channels for PLAYBACK.
I/AudioHardwareALSA( 77): DEFAULT_SAMPLE_RATE is 44100, mDefaults->sampleRate is 44100
D/AudioHardwareALSA( 77): Set PLAYBACK sample rate to 44100 HZ
D/AudioHardwareALSA( 77): Buffer size: 4096
D/AudioHardwareALSA( 77): Latency: 92879
D/DataRouter( 75): fd is 21 Content read is PDA USB
D/DataRouter( 75): length is 8
W/AudioFlinger( 77): write blocked for 120 msecs, 796 delayed writes, thread 0x75bd8
W/PowerManagerService( 120): Timer 0x7->0x3|0x0
I/PowerManagerService( 120): Ulight 7->3|0
D/DataRouter( 75): fd is 21 Content read is PDA USB
D/DataRouter( 75): length is 8
D/LightsService( 120): BUTTON : 0
D/AudioHardwareALSA( 77): Inside AudioStreamOutALSA::standby
I/AudioHardwareALSA( 77): Output standby called!!. Turn off PCM device.
D/DataRouter( 75): fd is 21 Content read is PDA USB
D/DataRouter( 75): length is 8
D/DataRouter( 75): fd is 21 Content read is PDA USB
D/DataRouter( 75): length is 8
D/DataRouter( 75): fd is 21 Content read is PDA USB
D/DataRouter( 75): length is 8
D/DataRouter( 75): fd is 21 Content read is PDA USB
D/DataRouter( 75): length is 8
I'm not sure exactly what's going on, but it looks like it's trying to initialize audio, so it may be that the APK (from the 1st couple of posts) is not compatible hardware-wise with the SGP5 (US).
Jim
jimcpl said:
It installed ok, but I got "Unknown error" when tried to run it.
Jim
Click to expand...
Click to collapse
I did not test it, but like you when I installed it on my SGP I aldo got the unknown error.

SM-T330NU Rom Development Cyanogenmod 11 -DEAD

CLOSED
Sources
CLOSED
Reserved for Updates and or Room to breathe.
The logs, Where things stand logcat -dC | grep audio
Sorted
logcat -dC | grep media
Sorted
moonbutt74 said:
Code:
[email protected]:~# adb shell logcat -dC | grep media
[COLOR="Red"]E/mm-camera-sensor( 254): sensor_init_probe:326 num_media_devices = 0
E/mm-camera-sensor( 254): sensor_init_probe:328 dev_name = /dev/media0
E/mm-camera-sensor( 254): sensor_init_probe:335 num_media_devices = 1
E/mm-camera-sensor( 254): sensor_init_probe:326 num_media_devices = 1
E/mm-camera-sensor( 254): sensor_init_probe:328 dev_name = /dev/media1
E/mm-camera-sensor( 254): sensor_init_probe:335 num_media_devices = 2
E/mm-camera-sensor( 254): sensor_init_probe:356 Done enumerating media entities
E/mm-camera-sensor( 254): sensor_init_probe:326 num_media_devices = 2
E/mm-camera-sensor( 254): sensor_init_probe:328 dev_name = /dev/media2
E/mm-camera-sensor( 254): sensor_init_probe:331 Done enumerating media devices
E/mm-camera-sensor( 254): module_sensor_find_sensor_subdev:4406 media device number = 1 msm_config
E/mm-camera-sensor( 254): module_sensor_find_sensor_subdev:4419 Done enumerating media entities
E/mm-camera-sensor( 254): module_sensor_find_sensor_subdev:4406 media device number = 2 msm_cam_dummy
E/mm-camera-sensor( 254): module_sensor_find_sensor_subdev:4419 Done enumerating media entities
E/mm-camera-sensor( 254): module_sensor_find_sensor_subdev:4406 media device number = 3 msm_camera
E/mm-camera-sensor( 254): module_sensor_find_sensor_subdev:4419 Done enumerating media entities
E/mm-camera-sensor( 254): module_sensor_find_sensor_subdev:4406 media device number = 4 msm_camera
E/mm-camera-sensor( 254): module_sensor_find_sensor_subdev:4419 Done enumerating media entities
E/mm-camera-sensor( 254): module_sensor_find_sensor_subdev:4394 Done enumerating media devices-failed: 4[/COLOR]
[COLOR="Olive"]I/mediaserver( 250): ServiceManager: 0xb87da448
I/dalvikvm( 244): threadid=1: recursive native library load attempt (/system/lib/libmedia_jni.so)
I/dalvikvm( 244): threadid=1: recursive native library load attempt (/system/lib/libmedia_jni.so)
I/dalvikvm( 244): threadid=1: recursive native library load attempt (/system/lib/libmedia_jni.so)
I/dalvikvm( 244): threadid=1: recursive native library load attempt (/system/lib/libmedia_jni.so)[/COLOR]
[COLOR="Olive"]I/AppOps ( 711): Pruning old package media/1013: new uid=-1[/COLOR]
D/ExtendedUtils( 250): printFileName fd(24) -> /system/media/audio/ui/Lock.ogg
D/SystemUIService( 783): loading: class com.android.systemui.media.RingtonePlayer
D/SystemUIService( 783): running: [email protected]
D/ExtendedUtils( 250): printFileName fd(24) -> /system/media/audio/ui/Unlock.ogg
[COLOR="Olive"]I/ActivityManager( 711): Start proc android.process.media for broadcast com.android.providers.media/.MtpReceiver: pid=862 uid=10006 gids={50006, 1028, 1015, 1023, 1024, 2001, 3003, 3007}[/COLOR]
D/ActivityThread( 862): handleBindApplication:android.process.media
[COLOR="Red"]E/MediaFocusControl( 711): at android.media.MediaFocusControl.registerRemoteControlDisplay_int(MediaFocusControl.java:2182)
E/MediaFocusControl( 711): at android.media.MediaFocusControl.registerRemoteController(MediaFocusControl.java:217)
E/MediaFocusControl( 711): at android.media.AudioService.registerRemoteController(AudioService.java:4538)
E/MediaFocusControl( 711): at android.media.IAudioService$Stub.onTransact(IAudioService.java:614)[/COLOR]
[COLOR="Olive"]I/ActivityManager( 711): Start proc com.google.android.gms for service com.google.android.gms/.cast.media.CastRemoteDisplayProviderService: pid=1061 uid=10076 gids={50076, 3003, 1007, 1028, 1015, 1006, 3002, 3001, 3007, 2001, 3006}[/COLOR]
[COLOR="Red"]E/MediaFocusControl( 711): at android.media.MediaFocusControl.registerRemoteControlDisplay_int(MediaFocusControl.java:2182)
E/MediaFocusControl( 711): at android.media.MediaFocusControl.registerRemoteControlDisplay(MediaFocusControl.java:230)
E/MediaFocusControl( 711): at android.media.AudioService.registerRemoteControlDisplay(AudioService.java:4542)
E/MediaFocusControl( 711): at android.media.IAudioService$Stub.onTransact(IAudioService.java:593)[/COLOR]
[COLOR="Olive"]I/iu.UploadsManager( 1061): End new media; added: 0, uploading: 0, time: 58 ms[/COLOR]
[COLOR="DarkOrange"]W/ContextImpl( 711): Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1607 android.bluetooth.BluetoothHeadset.doBind:283 android.bluetooth.BluetoothHeadset.<init>:276 android.bluetooth.BluetoothAdapter.getProfileProxy:1369 android.media.AudioService.getBluetoothHeadset:2364
W/ContextImpl( 711): Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1607 android.bluetooth.BluetoothA2dp.doBind:165 android.bluetooth.BluetoothA2dp.<init>:158 android.bluetooth.BluetoothAdapter.getProfileProxy:1372 android.media.AudioService$AudioServiceBroadcastReceiver.onReceive:4388 [/COLOR]
D/ExtendedUtils( 250): printFileName fd(26) -> /system/media/audio/ui/Effect_Tick.ogg
D/ExtendedUtils( 250): printFileName fd(26) -> /system/media/audio/ui/KeypressStandard.ogg
D/ExtendedUtils( 250): printFileName fd(26) -> /system/media/audio/ui/KeypressSpacebar.ogg
D/ExtendedUtils( 250): printFileName fd(26) -> /system/media/audio/ui/KeypressDelete.ogg
D/ExtendedUtils( 250): printFileName fd(26) -> /system/media/audio/ui/KeypressReturn.ogg
D/ExtendedUtils( 250): printFileName fd(26) -> /system/media/audio/ui/KeypressInvalid.ogg
[COLOR="Olive"]I/ActivityManager( 711): Delay finish: com.android.providers.media/.MtpReceiver
I/iu.UploadsManager( 1061): End new media; added: 0, uploading: 0, time: 88 ms[/COLOR]
@Zaphodspeaks,
Z, try a dpi setting of 176, @180 i lose the splitscreen in settings, but at 176 text size seems less unreasonable.
Click to expand...
Click to collapse
Will do, personally I don't care much for split screen, but Ill give it a shot!
so far with out posting a Logcat, the only issue that bothers me is that it will not connect to my 2.4 GHZ & 5G, while using WPA2 AES Wireless encryption, it plain out does not like my Linksys E3000 Router even when I left it unencrypted, but will connect to my neighbors wifi which is left open. I feels like it can be used as a daily driver if you don't mind the lack of sound.. It runs smooth, its snappy and has not given me any kind of error or crash so far..
Z,
hi, thanks i'll see what i can find on Linksys routers, also i will be looking at what sbu77 and starlight are doing with wifi,wcnss and mac issues.
You have no issue connecting with stock rom, because of the above issue if i understood what i read on the mac address issue correctly.
This current build would suffer from the same issue.
m
Edit, i am wondering how many times i can say issue in a post about a specific issue.
I have issues. xD
Kernel Updated concerning wifi/mac address ISSUE as discussed ny @starlightknight in this post at his?/her? thread
http://forum.xda-developers.com/showpost.php?p=60354789&postcount=188
see OP for details
Kernel Update [OPTIONAL]
Sorted
moonbutt74 said:
Z,
hi, thanks i'll see what i can find on Linksys routers, also i will be looking at what sbu77 and starlight are doing with wifi,wcnss and mac issues.
You have no issue connecting with stock rom, because of the above issue if i understood what i read on the mac address issue correctly.
This current build would suffer from the same issue.
m
Edit, i am wondering how many times i can say issue in a post about a specific issue.
I have issues. xD
Kernel Updated concerning wifi/mac address ISSUE as discussed ny @starlightknight in this post at his?/her? thread
http://forum.xda-developers.com/showpost.php?p=60354789&postcount=188
see OP for details
Click to expand...
Click to collapse
Oh I forgot to mention that my Cisco/Linksys E3000 is running DD-WRT.. Not the stock ROM..
Edit, I'll post my results as soon as I finish some chores..
I'm really eager to work with this.. Even with out sound, and if the WIFI fix works.. and I'm sure it will..
This will become my daily driver.. for a couple of weeks..
Edit2:
I reinstalled your build, plus adding the updated Kernel..
Same exact issue, could not connect to anything... Even when I left my WiFi open..
Neighbors wifi does connect still as it did yesterday.. Which is not encrypted..
Edit3!!!!!
BINGO I GOT IT!
It was my MAC address filtering that prevented the device from connecting, even though it was on the safe list..
By disabling MAC Filtering, I was successfully able to connect!
moonbutt74 said:
Z,
hi, thanks i'll see what i can find on Linksys routers, also i will be looking at what sbu77 and starlight are doing with wifi,wcnss and mac issues.
You have no issue connecting with stock rom, because of the above issue if i understood what i read on the mac address issue correctly.
This current build would suffer from the same issue.
m
Edit, i am wondering how many times i can say issue in a post about a specific issue.
I have issues. xD
Click to expand...
Click to collapse
You are an issue!
Opinion / Feedback
My opinion/feedback:
I'm an average not-knowing-code person. This ROM by far is great, WiFi works, apps work, Speaker sound doesn't work but the headphone jack works great, besides i use headphones like 95% of all time. Main operations work well for me and i will take this as my daily driver. I will report if there is any issue and will try to provide a logcat. Thanks for the Developers on bringing a better ROM to our device than boring, laggy TouchWiz!
Rusell said:
My opinion/feedback:
I'm an average not-knowing-code person. This ROM by far is great, WiFi works, apps work, Speaker sound doesn't work but the headphone jack works great, besides i use headphones like 95% of all time. Main operations work well for me and i will take this as my daily driver. I will report if there is any issue and will try to provide a logcat. Thanks for the Developers on bringing a better ROM to our device than boring, laggy TouchWiz!
Click to expand...
Click to collapse
The phones work ? No 5hit ? so something's not routing right. Russ, huge good tip, thanks for the assist !:good:
m
Been using this ROM since yesterday afternoon and it is quite stable. There is a few issues here and there but all in all it is snappy and way better than stock. The main issues I have had were the magnetic case not waking the device up when opening and as mention by the OP, the speaker sound issue
wire55 said:
Been using this ROM since yesterday afternoon and it is quite stable. There is a few issues here and there but all in all it is snappy and way better than stock. The main issues I have had were the magnetic case not waking the device up when opening and as mention by the OP, the speaker sound issue
Click to expand...
Click to collapse
Also as stated in op, I will not be taking requests of any kind, which the magnetic cover mention sounds like.
I have no interest in in the subject, sound is my concern. I do appreciate your interest though, thank you.
I also expressed a desire in the OP for a more capable developer to pick this project up.
To be straight foward, i totally suck at building roms and am suprised i got this far. :silly:
Every build since the one posted has once again begun to not boot, fail, to mount storage, or surface flinger dies.
This is truly going to drive me mad.
moonbutt74 said:
Also as stated in op, I will not be taking requests of any kind, which the magnetic cover mention sounds like.
I have no interest in in the subject, sound is my concern. I do appreciate your interest though, thank you.
I also expressed a desire in the OP for a more capable developer to pick this project up.
To be straight foward, i totally suck at building roms and am suprised i got this far. :silly:
Every build since the one posted has once again begun to not boot, fail, to mount storage, or surface flinger dies.
This is truly going to drive me mad.
Click to expand...
Click to collapse
I am asking of nothing. I was just stating something that I came upon in the ROM. I do thank you for all the support you have given. I would pick this up if I had passed experience, but I have never attempted because of how old my laptopvis.
wire55 said:
Been using this ROM since yesterday afternoon and it is quite stable. There is a few issues here and there but all in all it is snappy and way better than stock. The main issues I have had were the magnetic case not waking the device up when opening and as mention by the OP, the speaker sound issue
Click to expand...
Click to collapse
OMG, i hear you on the old laptop my builds take so freakin long i can feel my hair turning grey.
moonbutt74 said:
OMG, i hear you on the old laptop my builds take so freakin long i can feel my hair turning grey.
Click to expand...
Click to collapse
Yeah! Thank god I'm not the only one using old technology. My laptop is from 2008 with 4gb ram and core 2 duo that runs really slow and overheats and crashed frequently.
wire55 said:
Yeah! Thank god I'm not the only one using old technology. My laptop is from 2008 with 4gb ram and core 2 duo that runs really slow and overheats and crashed frequently.
Click to expand...
Click to collapse
Slow is coooool !
xD
okay seriously though, any thoughts as to the sound issue ?
@moonbutt74 thanks for taking this on and spending all of the frustrating months on it your already have. I am not a ROM builder or developer, I just read a lot on forums of devices I have. With that on my Note 4 there is a mod that enables the front speaker with the rear speaker by @sshafranko in which he used the mixer_paths.xml file. I do not know if this will help at all, nor do I know exactly what is does, just trying to help. Here is his original thread (for people that don't read everything, this link is not for the Tab 4, it is reference only): http://forum.xda-developers.com/note-edge/development/mod-sm-915t-surround-sound-t2955648
Op if this is completely useless and you request, I will delete this post
moonbutt74 said:
Slow is coooool !
xD
okay seriously though, any thoughts as to the sound issue ?
Click to expand...
Click to collapse
If you ask me, I think the sound issue is kernel related.

Mate 10 pro bug: YouTube + Messenger

Hi everyone.
I come here beacause I recently received my Mate 10 pro. It's quite perfect, but I've got an issue with it.
It's a kind of compatibility thing I guess, between youtube and messenger.
To explain it in the easier way, when I'm using both apps, the phone crashes and lock itself automatically. For example when I'm using youtube and I receive a messenger notification, the phone crashes and go to the lockscreen. When I unlock it, I'm still on youtube but no sign of messenger.
Another example: when I've got a Messenger Bubble on the screen, I open the youtube app. And when I'm shutting down the messenger bubble (with YouTube on the background) , the phone go the the lockscreen again...
I went to the settings, I thought it was related to the application overlay but it's not the case...
If someone has an idea I take It. And If some users of the mate 10 pro can try this on his own phone, I would be pleased.
Thanks by advance.
OH MY GOD, THANK YOU
I really began to think I was the only one having this bug, and I feel so relieved right now, not being the only one.
Sadly, I tried various things, I even dug in logcat to find some clues, but sadly I did not managed to find any relevant error.
I would be really glad to further discuss about this issue, and now I can go to Huawei saying I'm not the only one (I also found 1 other French guy discussing this topic on another forum, not finding any solution)
I'm really pissed off by this issue, and would be glad if I could help in any way.
PS: English is not my native language so sorry in advance if anything of what I said seems unclear.
Hi everyone !
I came back just to correct something : I am able to obtain logs of the error.
In fact, when I was browsing logcat, I was doing it on the wrong phone (common mistake when you have 2 devices connected to the same PC)
So, in fact, I'm able to tell that the exact error creating this crazy mess is this one :
11-23 15:22:40.511 30098 29788 E ActivityThread: Failed to find provider info for com.facebook.mlite.sso.MessengerLoggedInUserProvider
11-23 15:22:42.012 570 570 E DE H DisplayEngineImpl: [effect] setBLC: 560: can not support this mode: 0x20!
11-23 15:22:42.224 1579 1579 E AndroidRuntime: FATAL EXCEPTION: main
11-23 15:22:42.224 1579 1579 E AndroidRuntime: Process: com.android.systemui, PID: 1579
11-23 15:22:42.224 1579 1579 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.view.View.setTag(int, java.lang.Object)' on a null object reference
11-23 15:22:42.224 1579 1579 E AndroidRuntime: at com.android.systemui.statusbar.ViewTransformationHelper.addRemainingTransformTypes(ViewTransformationHelper.java:218)
11-23 15:22:42.224 1579 1579 E AndroidRuntime: at com.android.systemui.statusbar.notification.NotificationHeaderViewWrapper.addRemainingTransformTypes(NotificationHeaderViewWrapper.java:167)
11-23 15:22:42.224 1579 1579 E AndroidRuntime: at com.android.systemui.statusbar.notification.NotificationHeaderViewWrapper.notifyContentUpdated(NotificationHeaderViewWrapper.java:142)
11-23 15:22:42.224 1579 1579 E AndroidRuntime: at com.android.systemui.statusbar.NotificationContentView.onNotificationUpdated(NotificationContentView.java:1151)
11-23 15:22:42.224 1579 1579 E AndroidRuntime: at com.android.systemui.statusbar.ExpandableNotificationRow.onNotificationUpdated(ExpandableNotificationRow.java:322)
11-23 15:22:42.224 1579 1579 E AndroidRuntime: at com.android.systemui.statusbar.ExpandableNotificationRow.onNotificationUpdated(ExpandableNotificationRow.java:318)
11-23 15:22:42.224 1579 1579 E AndroidRuntime: at com.android.systemui.statusbar.BaseStatusBar.inflateViews(BaseStatusBar.java:2073)
11-23 15:22:42.224 1579 1579 E AndroidRuntime: at com.android.systemui.statusbar.BaseStatusBar.createNotificationViews(BaseStatusBar.java:2544)
11-23 15:22:42.224 1579 1579 E AndroidRuntime: at com.android.systemui.statusbar.phone.PhoneStatusBar.addNotification(PhoneStatusBar.java:1778)
11-23 15:22:42.224 1579 1579 E AndroidRuntime: at com.android.systemui.statusbar.BaseStatusBar$7$2.run(BaseStatusBar.java:778)
11-23 15:22:42.224 1579 1579 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:808)
11-23 15:22:42.224 1579 1579 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:101)
11-23 15:22:42.224 1579 1579 E AndroidRuntime: at android.os.Looper.loop(Looper.java:166)
11-23 15:22:42.224 1579 1579 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7358)
11-23 15:22:42.224 1579 1579 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
11-23 15:22:42.224 1579 1579 E AndroidRuntime: at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:245)
11-23 15:22:42.224 1579 1579 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:926)
Click to expand...
Click to collapse
I don't know if this could help us, but this is definitely the reason of our crashes
Same Problem on mine
Hi Guys,
I have the same problem. My phone gets locked and there is no other means for me to unlock it but to restart my phone. I have Mate 10 as well, there is no problem like this. Only in Pro version.
For time being, I disabled my Messenger Chat Heads and rely on the standard view to prevent this problem. Let us hope a fix will be done soon. We just do not know it is issue from youtube or messenger or the phone software itself.
Regards
VIN0130 said:
Hi Guys,
I have the same problem. My phone gets locked and there is no other means for me to unlock it but to restart my phone. I have Mate 10 as well, there is no problem like this. Only in Pro version.
For time being, I disabled my Messenger Chat Heads and rely on the standard view to prevent this problem. Let us hope a fix will be done soon. We just do not know it is issue from youtube or messenger or the phone software itself.
Regards
Click to expand...
Click to collapse
Hi VIN0130 !
After showing the logs to an Android engineering colleague, he seemed to confirm what I originally thought, being that the bug is OS related.
In fact, it looks like the phone is destroying a Messenger view, thinking it became useless to the app, which leads to the NullPointerException when Messenger tries to access this view.
So, it may have something to do with, for example, the phone trying to optimize the battery usage of background apps execution...
Of course, it's just a superficial analysis, not having access to any source code of the concerned actors (Messenger, Youtube, or even the OS), but It may be a lead...
HI VC...
Thanks for the info. My only doubt is that why in Mate 10 (not the Pro) doesn't have this problem. It has same specs with the Pro except the Amoled type and Screen Resolution.
I think there could be an issue on Full Screen Option with the Pro which is causing the problem. And I wonder why it goes to lock screen when I receive a message in Messenger if Chat Head is active.
BR
Indeed, it's kinda odd that the Mate 10 doesn't have this issue, I would have thought it was a bug in EMUI 8, not depending on the device...
Maybe it is in fact a weird combination between having a full screen app with video embedded inside, but there's nothing I'm sure of...
I can't remember the resolution of the Mate 10 screen ; do you ? Discussing with my colleague, I've been told that, maybe, the video app is taking too much memory, which would lead to this background view destruction I was referring earlier (to free up memory and optimize battery usage).
So maybe video is taking much more memory on the 10 Pro than on the other one. I was thinking about its HDR display too, which is supported, if I remember quite well, by YouTube and the native Huawei video player, the two apps that lead to this bug on my phone.
I'm really trying to guess what is happening here, but It's cleary not something we could handle by ourselves, even with the right skills (unless by flashing our device with another ROM ha ha ha).
So, I think our only chance is to bring Huawei's attention to this issue
Hello Again...
I have just received an official update. It seems the issue has been fixed with the new fw update. I just tried youtube + messenger (chat head active) for about 5x, my phone didn't locked.
Let me know if the issue has been resolved from your end as well. Out of curiosity only or should I say... Excited - Fixed!
?
Version Update: BLA-L29 8.0.0.119(C185)
BR
Woh, thanks VIN, you're bringing me hope ha ha.
Sadly, no update available for me right now, but be assured I'll give my own feedback when that happens Thanks for yours either way !
Hi VC,
I just tried to manually check for update on mine and luckily it is available. Try yours. I've been playing with youtube while chatting w/ my brother just to check if the error will still occur. No issues happened at all!
Good Luck!
BR
Was just about to make a post and found this waiting for my update as well its a really annoying bug....
Hopefully it comes quickly
Whatsapp too!
Hi everyone!
I bought this device 2 days ago and I'm quite scared because I can't see a single video on youtube without the phone locking itself. When I read your messages I started having hope and deleted facebook messenger to be able to see youtube videos, but now it's happening with the Whatsapp too. I' ve looked for updates but there aren't any available yet. Can someone help?
Thanks.
Same here
Just started using my mate 10 Pro and I have the same issue, freezes when i get a message on messanger and I run youtube in full screen.
Haven't recieved an update recently, thus running:
BLA-L29 8.0.0.115(C432)
I have this same issue on my mate 10 lite... It's not related to any chat heads though. I can be watching YouTube for like 30 minutes and bam, locked with black screen. I even uninstalled youtube and reverted back to the old one. Same issue. I am on the latest update, build number ending in b110.
Is there perhaps a side solution?
I have the same issue. It happens when video play on full screen and message incoming from Skype, telegram, messenger or SMS. I solve that issue by desable option 'draw over other apps' in these apps. You can find that option in settings>apss&notifications>apps>... Here click messenger app and turn off this option
Was thinkin im alone with that bug... Now im a bit more Chill
@nuficek
I have the same issue but unfortunately no new system update available yet. Does anyone have any idea about releasing new update in other regions?
install a generic messenger it will solve for now
we got apps like facebook and messenger in one app
less ram...battery and more fast
I don't have the bug with YouTube + Messenger, but this bug (screen lock while using some apps) happened to me.
Sadly you just have to wait for updates.
Huawei Mate 10 pro - BLA-L29 8.0.0.120(C432)
Bla-l29 8.0.0.127(c432)
BLA-L29 8.0.0.127(C432)
on 115 , no VoLTE or VoWiFi settings , had the same bug(mainly due to screen overlay) , the phone will often crash if also the eye comfort was on and numerous stutters here and there .
on 127 (via OTA) all the issues were solved

Categories

Resources