I have a newer model KIA with A2DP Bluetooth streaming capabilities and I've always had more issues with connections and with play/pause headset controls on AOSP-based ROMs like CM vs. sense ROMs. Recently, I've been running Tiny's CM 10.1 rom and had the same issues intermittently. Then I noticed the DSP Manager FC'd one day and it immediately cleared up some issues. So I removed the DSP Manager via TB and I can report that although the issues have not completely disappeared, it is much more responsive and the headset controls seem to work much more consistently. I don't have enough posts to comment in the development thread but I thought I'd share FWIW.
Known issue with android 4.2. Google supposedly has it fixed for the upcoming 4.2.2 release. For some reason not everyone has this problem.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
Known issue with android 4.2. Google supposedly has it fixed for the upcoming 4.2.2 release. For some reason not everyone has this problem.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Good to know, and thanks for all your work. I should note that in my experience, the exact same A2DP issues have cropped up for me on CM6 and CM7 in the past but not on any sense-based GB roms or MIUI GB. I have no explanation for why MIUI works better than CM, as I was under the assumption it was AOSP-based and borrowed heavily from the CM team.
thelazy8 said:
Good to know, and thanks for all your work. I should note that in my experience, the exact same A2DP issues have cropped up for me on CM6 and CM7 in the past but not on any sense-based GB roms or MIUI GB. I have no explanation for why MIUI works better than CM, as I was under the assumption it was AOSP-based and borrowed heavily from the CM team.
Click to expand...
Click to collapse
Your issues are not 4.2 related it seems.
Sent from my Galaxy Nexus using Tapatalk 2
Do you know what specifically the 4.2 issues are? I have a few theories about mine but I only have the one device (car) to test the setup with. I think some of my issues stem from my car automatically syncing address book data on each connection in the background while I'm trying to simultaneously play music over the same connection.
thelazy8 said:
Do you know what specifically the 4.2 issues are? I have a few theories about mine but I only have the one device (car) to test the setup with. I think some of my issues stem from my car automatically syncing address book data on each connection in the background while I'm trying to simultaneously play music over the same connection.
Click to expand...
Click to collapse
Some experience playing audio over Bluetooth. That is the acknowledged issue. Connecting itself shouldn't be affected.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
Some experience playing audio over Bluetooth. That is the acknowledged issue. Connecting itself shouldn't be affected.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Do you think any possible fixes for this in upcoming updates from Google will make it to our device? Too soon to tell?
thelazy8 said:
Do you think any possible fixes for this in upcoming updates from Google will make it to our device? Too soon to tell?
Click to expand...
Click to collapse
4.2.2 should merge no problem so the answer is probably. If your issue isn't related to 4.2 exclusively as in it doesn't work on older Android version then 4.2.2 won't fix your issue. It sounded like you had issues in CM7 even.
Sent from my Galaxy Nexus using Tapatalk 2
I'm using Tiny's CM10.1 (2013-2-21) and I'm definitely getting Bluetooth streaming problems. I just started using BT audio more recently and after about 7 minutes the whole phone locks up. Sometimes it comes back after 4-5 minutes. I'm copying in a recent alogcat trace and I added "..." where there were many almost identical lines:
Code:
E/GKI_LINUX( 1235): ##### ERROR : timer_thread: tick delayed > 5 slots (-67369384,-50000000) -- cpu overload ? #####
...
E/GKI_LINUX( 1235): ##### ERROR : timer_thread: tick delayed > 5 slots (-58498535,-50000000) -- cpu overload ? #####
I/Choreographer(11058): Skipped 131 frames! The application may be doing too much work on its main thread.
W/bt-btif ( 1235): ### UNDERRUN :: ONLY READ 0 BYTES OUT OF 512 ###
E/GKI_LINUX( 1235): ##### ERROR : timer_thread: tick delayed > 5 slots (-798387449,-50000000) -- cpu overload ? #####
W/bt-btif ( 1235): ### UNDERRUN :: ONLY READ 0 BYTES OUT OF 512 ###
E/GKI_LINUX( 1235): ##### ERROR : timer_thread: tick delayed > 5 slots (-1344443103,-50000000) -- cpu overload ? #####
W/AudioTrack( 97): obtainBuffer timed out (is the CPU pegged?) 0x40a1cd88 name=0x1user=00ee8e00, server=00ee6600
W/bt-btif ( 1235): ### UNDERRUN :: ONLY READ 0 BYTES OUT OF 512 ###
E/GKI_LINUX( 1235): ##### ERROR : timer_thread: tick delayed > 5 slots (-142488247,-50000000) -- cpu overload ? #####
W/AudioFlinger( 97): write blocked for 20638 msecs, 2 delayed writes, thread 0x41a80008
D/dalvikvm( 376): GC_CONCURRENT freed 1918K, 20% free 13640K/16844K, paused 39ms+65ms, total 21113ms
D/dalvikvm( 376): WAIT_FOR_CONCURRENT_GC blocked 21006ms
D/dalvikvm( 376): WAIT_FOR_CONCURRENT_GC blocked 232ms
D/dalvikvm( 376): WAIT_FOR_CONCURRENT_GC blocked 223ms
D/dalvikvm( 376): WAIT_FOR_CONCURRENT_GC blocked 20ms
D/HeadsetPhoneState( 1235): sendDeviceStateChanged. mService=1 mSignal=3 mRoam=0 mBatteryCharge=4
D/HeadsetPhoneState( 1235): sendDeviceStateChanged. mService=1 mSignal=2 mRoam=0 mBatteryCharge=4
I/Choreographer(11058): Skipped 1297 frames! The application may be doing too much work on its main thread.
E/GKI_LINUX( 1235): ##### ERROR : timer_thread: tick delayed > 5 slots (-220421086,-50000000) -- cpu overload ? #####
...
E/GKI_LINUX( 1235): ##### ERROR : timer_thread: tick delayed > 5 slots (-285830022,-50000000) -- cpu overload ? #####
Does this match the known bugs that Google has been working on? Is there any information or testing/debugging that I can do to help?
I have no problems with a2dp on my gs3
nicu28 said:
I'm using Tiny's CM10.1 (2013-2-21) and I'm definitely getting Bluetooth streaming problems. I just started using BT audio more recently and after about 7 minutes the whole phone locks up. Sometimes it comes back after 4-5 minutes. I'm copying in a recent alogcat trace and I added "..." where there were many almost identical lines:
Code:
E/GKI_LINUX( 1235): ##### ERROR : timer_thread: tick delayed > 5 slots (-67369384,-50000000) -- cpu overload ? #####
...
E/GKI_LINUX( 1235): ##### ERROR : timer_thread: tick delayed > 5 slots (-58498535,-50000000) -- cpu overload ? #####
I/Choreographer(11058): Skipped 131 frames! The application may be doing too much work on its main thread.
W/bt-btif ( 1235): ### UNDERRUN :: ONLY READ 0 BYTES OUT OF 512 ###
E/GKI_LINUX( 1235): ##### ERROR : timer_thread: tick delayed > 5 slots (-798387449,-50000000) -- cpu overload ? #####
W/bt-btif ( 1235): ### UNDERRUN :: ONLY READ 0 BYTES OUT OF 512 ###
E/GKI_LINUX( 1235): ##### ERROR : timer_thread: tick delayed > 5 slots (-1344443103,-50000000) -- cpu overload ? #####
W/AudioTrack( 97): obtainBuffer timed out (is the CPU pegged?) 0x40a1cd88 name=0x1user=00ee8e00, server=00ee6600
W/bt-btif ( 1235): ### UNDERRUN :: ONLY READ 0 BYTES OUT OF 512 ###
E/GKI_LINUX( 1235): ##### ERROR : timer_thread: tick delayed > 5 slots (-142488247,-50000000) -- cpu overload ? #####
W/AudioFlinger( 97): write blocked for 20638 msecs, 2 delayed writes, thread 0x41a80008
D/dalvikvm( 376): GC_CONCURRENT freed 1918K, 20% free 13640K/16844K, paused 39ms+65ms, total 21113ms
D/dalvikvm( 376): WAIT_FOR_CONCURRENT_GC blocked 21006ms
D/dalvikvm( 376): WAIT_FOR_CONCURRENT_GC blocked 232ms
D/dalvikvm( 376): WAIT_FOR_CONCURRENT_GC blocked 223ms
D/dalvikvm( 376): WAIT_FOR_CONCURRENT_GC blocked 20ms
D/HeadsetPhoneState( 1235): sendDeviceStateChanged. mService=1 mSignal=3 mRoam=0 mBatteryCharge=4
D/HeadsetPhoneState( 1235): sendDeviceStateChanged. mService=1 mSignal=2 mRoam=0 mBatteryCharge=4
I/Choreographer(11058): Skipped 1297 frames! The application may be doing too much work on its main thread.
E/GKI_LINUX( 1235): ##### ERROR : timer_thread: tick delayed > 5 slots (-220421086,-50000000) -- cpu overload ? #####
...
E/GKI_LINUX( 1235): ##### ERROR : timer_thread: tick delayed > 5 slots (-285830022,-50000000) -- cpu overload ? #####
Does this match the known bugs that Google has been working on? Is there any information or testing/debugging that I can do to help?
Click to expand...
Click to collapse
Try the latest cm 10.1 build. They did some fixing up on Bluetooth add far add quality. Next time it freezes see if it reboots after 30 seconds and three finger salute to reboot if it doesn't reboot automatically. Then pull the last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2
Related
I see engadget is reporting a leaked version of Skype with video for thunderbolt
http://m.engadget.com/default/artic...olt-celebrations/&category=classic&postPage=1
I wondered if anyone could get it working on our EVO. I have CM7 and it would not install for me
Sent from my CM7 final.
Yeah I tried too but didn't work. Dang :-/
Doesn't install on stock either
This would be pretty awesome.
Sent from my PC36100 using XDA App
Yeah its true phandroids reporting the same thing
Sent from my PC36100 using XDA App
I have it on my TB... super win
That would be cool if it was working on the EVo
I am sure a few devs here will figure it out soon. TB is running 2.2, like our EVO's, so it's just a matter of time.
Once this apk starts getting modded to run on different phones, it's really going to explode. I hope Skype is ready for this... I foresee an iPhone/AT&T network debacle in the making.
khov07 said:
I am sure a few devs here will figure it out soon. TB is running 2.2, like our EVO's, so it's just a matter of time.
Once this apk starts getting modded to run on different phones, it's really going to explode. I hope Skype is ready for this... I foresee an iPhone/AT&T network debacle in the making.
Click to expand...
Click to collapse
All theyll do is start blocking it like they did when fring was using it.
Here's an APK that was updated to remove the check for "VerizonPlatform" and "VerizonMerlin" condition check. I also had to remove the line
Code:
<uses-library android:name="com.htc.device" />
from the AndroidManifest.xml just to get the APK to install.
It will get to the sign-in page, but the SkypeService fails...
Code:
I/com.skype.merlin_mecha.service.a(17177): system board:supersonic bootloader:2.10.0001 brand:sprint product:htc_supersonic model:PC36100 manufacturer:HTC device:supersonic display:3.70.651.1 fingerprint:sprint/htc_supersonic/supersonic/supersonic:2.2/FRF91/294884:user/release-keys host:AA109 user:root radio:2.15.00.09.01 tags:release-keys type:user
I/global (17177): Default buffer size used in BufferedInputStream constructor. It would be better to be explicit if an 8k buffer is required.
D/dalvikvm(17177): GC_FOR_MALLOC freed 5340 objects / 712528 bytes in 124ms
I/LSState (12428): EventReceiver:android.intent.action.NOTIFICATION_UPDATE
I/StartSkypeKitOperation(17177): REMOVE THIS ONCE VERIFIED: appToken = KdXVSo6qB9
I/dalvikvm(17177): Jit: resizing JitTable from 4096 to 8192
D/dalvikvm(15756): GC_EXPLICIT freed 3901 objects / 412584 bytes in 100ms
I/ActivityManager(12428): Process com.skype.merlin_mecha (pid 17177) has died.
W/ActivityManager(12428): Scheduling restart of crashed service com.skype.merlin_mecha/.service.SkypeServiceController in 5000ms
I don't have any more time tonight to work on this, maybe someone else can look into why the service is failing.
Link to APK file... [warning: this is for devs, this is not functional yet]
http://db.tt/umgHYVq
-Daryel
daryelv said:
Here's an APK that was updated to remove the check for "VerizonPlatform" and "VerizonMerlin" condition check. I also had to remove the line
Code:
<uses-library android:name="com.htc.device" />
from the AndroidManifest.xml just to get the APK to install.
It will get to the sign-in page, but the SkypeService fails...
Code:
I/com.skype.merlin_mecha.service.a(17177): system board:supersonic bootloader:2.10.0001 brand:sprint product:htc_supersonic model:PC36100 manufacturer:HTC device:supersonic display:3.70.651.1 fingerprint:sprint/htc_supersonic/supersonic/supersonic:2.2/FRF91/294884:user/release-keys host:AA109 user:root radio:2.15.00.09.01 tags:release-keys type:user
I/global (17177): Default buffer size used in BufferedInputStream constructor. It would be better to be explicit if an 8k buffer is required.
D/dalvikvm(17177): GC_FOR_MALLOC freed 5340 objects / 712528 bytes in 124ms
I/LSState (12428): EventReceiver:android.intent.action.NOTIFICATION_UPDATE
I/StartSkypeKitOperation(17177): REMOVE THIS ONCE VERIFIED: appToken = KdXVSo6qB9
I/dalvikvm(17177): Jit: resizing JitTable from 4096 to 8192
D/dalvikvm(15756): GC_EXPLICIT freed 3901 objects / 412584 bytes in 100ms
I/ActivityManager(12428): Process com.skype.merlin_mecha (pid 17177) has died.
W/ActivityManager(12428): Scheduling restart of crashed service com.skype.merlin_mecha/.service.SkypeServiceController in 5000ms
I don't have any more time tonight to work on this, maybe someone else can look into why the service is failing.
Link to APK file... [warning: this is for devs, this is not functional yet]
http://db.tt/umgHYVq
-Daryel
Click to expand...
Click to collapse
Nice Work! Good start on what I am sure will be something a dev would be interested in phucking with.
daryelv said:
Here's an APK that was updated to remove the check for "VerizonPlatform" and "VerizonMerlin" condition check. I also had to remove the line
Code:
<uses-library android:name="com.htc.device" />
from the AndroidManifest.xml just to get the APK to install.
It will get to the sign-in page, but the SkypeService fails...
Code:
I/com.skype.merlin_mecha.service.a(17177): system board:supersonic bootloader:2.10.0001 brand:sprint product:htc_supersonic model:PC36100 manufacturer:HTC device:supersonic display:3.70.651.1 fingerprint:sprint/htc_supersonic/supersonic/supersonic:2.2/FRF91/294884:user/release-keys host:AA109 user:root radio:2.15.00.09.01 tags:release-keys type:user
I/global (17177): Default buffer size used in BufferedInputStream constructor. It would be better to be explicit if an 8k buffer is required.
D/dalvikvm(17177): GC_FOR_MALLOC freed 5340 objects / 712528 bytes in 124ms
I/LSState (12428): EventReceiver:android.intent.action.NOTIFICATION_UPDATE
I/StartSkypeKitOperation(17177): REMOVE THIS ONCE VERIFIED: appToken = KdXVSo6qB9
I/dalvikvm(17177): Jit: resizing JitTable from 4096 to 8192
D/dalvikvm(15756): GC_EXPLICIT freed 3901 objects / 412584 bytes in 100ms
I/ActivityManager(12428): Process com.skype.merlin_mecha (pid 17177) has died.
W/ActivityManager(12428): Scheduling restart of crashed service com.skype.merlin_mecha/.service.SkypeServiceController in 5000ms
I don't have any more time tonight to work on this, maybe someone else can look into why the service is failing.
Link to APK file... [warning: this is for devs, this is not functional yet]
http://db.tt/umgHYVq
-Daryel
Click to expand...
Click to collapse
from the code it looks like the skype apk sees that its runnin on the supersonic, and then at the end com.skype.merlin_mecha dies. i know the htc mecha is the incredible HD (thunderbolt) so when the sign in is authenticating it crashes because it doesnt match. i dont know how to spoof the device name, but i know the devs will figure it out
http://forum.xda-developers.com/showthread.php?t=1031944
Hope that the Skype team has it running for EVO's real soon.
Sent from my PC36100 using XDA Premium App
the admins should make a sticky of this and its progress..so many questions and threads..
can't wait to see this in action!
Come on guys there no developer who can unlock that fcking app?????????//
brownhornet said:
I have it on my TB... super win
Click to expand...
Click to collapse
You have a evo and tb?
Sent from my PC36100 using XDA App
daryelv said:
Here's an APK that was updated to remove the check for "VerizonPlatform" and "VerizonMerlin" condition check. I also had to remove the line
Code:
<uses-library android:name="com.htc.device" />
from the AndroidManifest.xml just to get the APK to install.
It will get to the sign-in page, but the SkypeService fails...
Code:
I/com.skype.merlin_mecha.service.a(17177): system board:supersonic bootloader:2.10.0001 brand:sprint product:htc_supersonic model:PC36100 manufacturer:HTC device:supersonic display:3.70.651.1 fingerprint:sprint/htc_supersonic/supersonic/supersonic:2.2/FRF91/294884:user/release-keys host:AA109 user:root radio:2.15.00.09.01 tags:release-keys type:user
I/global (17177): Default buffer size used in BufferedInputStream constructor. It would be better to be explicit if an 8k buffer is required.
D/dalvikvm(17177): GC_FOR_MALLOC freed 5340 objects / 712528 bytes in 124ms
I/LSState (12428): EventReceiver:android.intent.action.NOTIFICATION_UPDATE
I/StartSkypeKitOperation(17177): REMOVE THIS ONCE VERIFIED: appToken = KdXVSo6qB9
I/dalvikvm(17177): Jit: resizing JitTable from 4096 to 8192
D/dalvikvm(15756): GC_EXPLICIT freed 3901 objects / 412584 bytes in 100ms
I/ActivityManager(12428): Process com.skype.merlin_mecha (pid 17177) has died.
W/ActivityManager(12428): Scheduling restart of crashed service com.skype.merlin_mecha/.service.SkypeServiceController in 5000ms
I don't have any more time tonight to work on this, maybe someone else can look into why the service is failing.
Link to APK file... [warning: this is for devs, this is not functional yet]
http://db.tt/umgHYVq
-Daryel
Click to expand...
Click to collapse
shiiii.. Thank you for getting us this far..... im not a dev, but a flashaholic tried to instal on MYN TWOpointTWO RLS 5 MYN Z & Koni's ES III ... I can't wait...lol
I think this one is definitely needed for this forum. So posting this here.
Here's how to use logcat:
There are two main ways to do a logcat, within android, and through adb.
Logcat within android can be done one of two ways, through a Logcat app:
Here are two good examples are either: aLogcat or Catlog
I prefer catlog, because in my opinion it has a little bit nicer UI. Both of these programs can dump their logs to a txt file, which is very useful for debugging. Or, you can do it in terminal emulator (same rules as running through adb(see below))
From Moscow Desire:
On the other hand, using adb to run logcat, in my opinion is much more useful, because you can start using it when android boots (i.e. once the boot animation appears.)
The code for logcat to output to a file is
Code:
adb logcat > name of problem.txt
you can also do
Code:
adb logcat -f name of problem.txt
how I prefer to do it is this way:
Code:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
Code:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
I then could do the following with logcat:
Code:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Sources: http://developer.android.com/tools/help/logcat.html
http://developer.android.com/tools/help/adb.html
Update for windows users:
Thank go to FuzzyMeep Two, Here's what he's posted for windows
(If you used his tool, here's his post, thank him for his work!)
Note : I am just sharing. Original post here.
Don't be a noob. Be a newbie..!!
Details here.
Great Guide! Should become a sticky.
You know,today morning you said you were not an expert with logcats.I see this thread and i am awestruck,but then i read the second last line :|
Prawesome said:
You know,today morning you said you were not an expert with logcats.I see this thread and i am awestruck,but then i read the second last line :|
Click to expand...
Click to collapse
I said i am no expert. That doesn't mean i cannot take, read or understand logcat..!!
Don't be a noob. Be a newbie..!!
Details here.
This thread is perfect to be a sticky in the Android Development Section.
Newcommers should know how to properly report bugs. I also leave a redirect in the Original Android Development.
I rather use ddms for all
Command prompt is the most basic thing same old Windows
Sent from my GT-P7300 using xda app-developers app
helped me out. Thanks
Fro "noobs" it will be easier to use qtadb https://qtadb.wordpress.com/download/ , just download, install and run. Nice GUI for adb, contains access to logcat too.
Fro "noobs" it will be easier to use qtadb https://qtadb.wordpress.com/download/ , just download, install and run. Nice GUI for adb, contains access to logcat too.
Click to expand...
Click to collapse
And it colours out errors according to their priority
I am a potato, problem?
Thanks bro
Sent from my GT-S5830 using Tapatalk 2
Extremely useful,
thank you!
However, catlog force closes when I added it as system app.
How can i get application specific logcat like i want to get logcat of systemui only
Really helpful!
Aman
Wysłane z mojego GT-I8190 przy użyciu Tapatalka
Thanks Sir...its helped me a lot..about understanding logcat
---------- Post added at 07:17 AM ---------- Previous post was at 07:12 AM ----------
Thanks Sir...its helped me a lot..about understanding logcat
Hi,
I intensively searched for my problem, but found always other non-related stuff.
Recently (last 1, 2 days) my WiFi didn't connect to any APs any more. I was using CN nightlies and franco kernel, so today I did update CN without franco. Afterwards I downgraded CN and did a radio update and now I tried the stock 4.2.2 image with the flash-all script, which also seemed to reflash my radio.
The default wifi dialog always displayed the saved wifis only. And after installing stock, the initial wifi dialog displayed "searching" only for a very long time. Sometimes I see some networks and I even managed to connect to mine, but it dropped immediately.
I know, this is very undetailed, but do you have any recommendations / logs to look out / smth which could point me in the right direction? Or is my hardware just broken?
logcat outputs this when turning wi-fi on (on stock 4.2.2, unrooted):
D/WifiService( 499): setWifiEnabled: true pid=1942, uid=1000
D/BluetoothAdapter( 1942): 1110956336: getState() : mService = null. Returning STATE_OFF
W/Netd ( 156): No subsystem found in netlink event
D/NetlinkEvent( 156): Unexpected netlink message. type=0x11
W/Netd ( 156): No subsystem found in netlink event
D/NetlinkEvent( 156): Unexpected netlink message. type=0x11
D/Tethering( 499): sendTetherStateChangedBroadcast 1, 0, 0
D/Tethering( 499): InitialState.processMessage what=4
D/Tethering( 499): sendTetherStateChangedBroadcast 0, 0, 0
D/SoftapController( 156): Softap fwReload - Ok
D/CommandListener( 156): Setting iface cfg
D/CommandListener( 156): Trying to bring down wlan0
E/NetdConnector( 499): NDC Command {219 softap fwreload wlan0 STA} took too long (739ms)
I/wpa_supplicant( 9715): Successfully initialized wpa_supplicant
I/wpa_supplicant( 9715): rfkill: Cannot open RFKILL control device
I/wpa_supplicant( 9715): rfkill: Cannot open RFKILL control device
D/CommandListener( 156): Setting iface cfg
D/CommandListener( 156): Trying to bring up p2p0
D/BluetoothAdapter( 1942): 1110956336: getState() : mService = null. Returning STATE_OFF
Click to expand...
Click to collapse
when flashing stock (via the official google flash scripts), stock firmware files (qualcom, ..) are also flashed, right? or could I do something useful with the official google binaries?
Stupid post.... Ignore
Hello, sorry when i post a new Thread i think that many users have the same Problem but my english is not so good that i can find the right Thread ... I have Flash :
I9505_Omega_v2.0_GUEUBMG8_Android_4.3_md5_830353DC5EB14151A017C340C1285E51
Now i have flash a other Rom:
aokp_i9505_unofficial_2013-05-19
and that:
I9505XXUAMDM_I9505OXAAMDM_I9505XXUAMDM_HOME.tar
Now i dont have Sound anymore (micro and Sound are Dissable) Now i have read, that i have make a Bootloader Downgrade and have shoot i up my Bootloader with that :S
What can i doo that Sound works again !? Thanks for Help
wolfsstolz said:
Hello, sorry when i post a new Thread i think that many users have the same Problem but my english is not so good that i can find the right Thread ... I have Flash :
I9505_Omega_v2.0_GUEUBMG8_Android_4.3_md5_830353DC5EB14151A017C340C1285E51
Now i have flash a other Rom:
aokp_i9505_unofficial_2013-05-19
and that:
I9505XXUAMDM_I9505OXAAMDM_I9505XXUAMDM_HOME.tar
Now i dont have Sound anymore (micro and Sound are Dissable) Now i have read, that i have make a Bootloader Downgrade and have shoot i up my Bootloader with that :S
What can i doo that Sound works again !? Thanks for Help
Click to expand...
Click to collapse
wipe data and cache.
if not, reflash your stock firmware, wipe data and cache, reboot
no, that dosnt work, that is a buck in bootloader (4.3 downgrade) i have do flash all roms (wipe too) i have flash a pit rom too but this PRoblem with Bootloader brick is the same. I have Read that many German Users have the same Problem when they flash a higher rom and downgrade it then.I think i must wait for a Developer who have the same Problem :S
When another User Have the same Problem it Please write it here to see that is a big problem for other Users too
Sorry but with Apple i dont have this PRoblem maybe i go back XD
wolfsstolz said:
no, that dosnt work, that is a buck in bootloader (4.3 downgrade) i have do flash all roms (wipe too) i have flash a pit rom too but this PRoblem with Bootloader brick is the same. I have Read that many German Users have the same Problem when they flash a higher rom and downgrade it then.I think i must wait for a Developer who have the same Problem :S
Click to expand...
Click to collapse
why dont you flash MH8 or 5 firmware, it contains the newer bootloader
Edit: please take a look here http://forum.xda-developers.com/showthread.php?t=2436368
when i flash that Sound dont go anymore too. the Problem is a bug in botloader in the newer FW when i have read that correctly
Sorry, i have read that not right .....
Can you give me a link from Rom ?! I only found a rom
forum.xda-developers.com/showthread.php?t=2299087
but this is only without new Bootloader and i think i need that with bootloader or works that too !?
Thansk for Help
Push Thread Too ....
I have Problem with Sound(Downgrade to Stock Rom from Omega Rom)
Now i have Read that i must install fallow Roms:
Factory_Firmware_Full_Wipe_I9505XXUBMGA_I9505OXXBM G3_NEE
and that:
GT-I9505-Factory-Firmware-Full-Wipe-DBT
Basis I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8
This Roms are in Forum but Theme is Close and Files only on **** hoster (Hotfile)
Who can upload that to another hoster (Hotfile is very slow in Germany 30 kb and 1 gb download go of :S ) like upoaded.to or mega.co.nz ?!
Who can help me for Sound come back please help. I have do all what i have read in Forum but nothing works for me.
Thanks for Help.
No People have a Idea !????
I have make a Photo from logger, it was nice when a dev can look ...
Who can tell me from that Folder:
My Android Folder:
1. i have more "mnt" Folder (mnt + mnt_1)
2. On Storage Folder i can see: USBDriveA ,USBDriveB, USBDrive ..... looks folfer i can see: ExtSdCard - sdcard_3
3. I have a folder named: Firmware + Firmware-mdm
4. ALL Files in : sys/fs/selinux are empty, 0kb , Subfolder too
5. In mnt_1 sys/fs/ext4 Folder are too mutch Folders !? looks on mmcblk0p10 + 16+18+26+29 with same Files
and many more .... Please , who can look on his Machine to this Folders, is that the same !?
Here Are Photos from logger that my Sound dosnt work:
{
"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"
}
I cant believe that no People can help me to bring back my Sound ....
Here a logcat answer from Sound .....
D/ALSADevice(10225): No valid input device: 0
V/ALSADevice(10225): switchDevice,rxDev:Speaker, txDevnull), curRxDev:None, curTxDev:None
D/alsa_ucm(10225): snd_use_case_set(): uc_mgr 0x40f97fb0 identifier _enadev value Speaker
E/alsa_ucm(10225): Invalid current verb value: Inactive - -1
E/alsa_ucm(10225): No valid device Speaker found
D/ALSADevice(10225): switchDevice: mCurTxUCMDevivce None mCurRxDevDevice Speaker inCallDevSwitch = 0
V/ALSADevice(10225): switchDevice Done
D/alsa_ucm(10225): snd_use_case_set(): uc_mgr 0x40f97fb0 identifier _verb value HiFi
E/alsa_ucm(10225): Control device not initialized
E/alsa_ucm(10225): Control device not initialized
W/alsa_ucm(10225): error snd_use_case_apply_mixer_controls
D/ALSADevice(10225): close: handle 0x40026d40 h 0x0
D/ALSADevice(10225): open: handle 0x40026d40, format 0x2
V/ALSADevice(10225): Music case
D/ALSADevice(10225): Device value returned is hw:0,0
V/ALSADevice(10225): flags 0, devName hw:0,0
E/alsa_pcm(10225): cannot open device '/dev/snd/pcmC0D0p', errno 2
V/ALSADevice(10225): pcm_open returned fd -1
E/ALSADevice(10225): open: Failed to initialize ALSA device 'hw:0,0'
E/AudioHardwareALSA(10225): Device open failed
I/audio_a2dp_hw(10225): adev_open: adev_open in A2dp_hw module
I/AudioFlinger(10225): loadHwModule() Loaded a2dp audio interface from A2DP Audio HW HAL (audio) handle 3
I/AudioFlinger(10225): loadHwModule() Loaded usb audio interface from SEC USB audio HW HAL (audio) handle 4
D/tms_audio_hw/AudioTmsIpc(10225): adev_open : Enter
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsInitSilenceFrames : Enter
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsInitSilenceFrames : Exit
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerInit :Enter
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerInit: thread started with name =TerminalModeAudioServer and id = 1073900584
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerInit exit
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsClientSetup : Enter
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerListen :Enter
D/tms_audio_hw/AudioTmsIpc(10225): initMutex: AudioClientSocketMutex Mutex Created
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsClientSetup : Exit
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsClientInit :Enter
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsClientInit: thread started with name =TerminalModeAudioClient and id = 1073900664
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsClientInit exit
D/tms_audio_hw/AudioTmsIpc(10225): adev_open : Exit
D/tms_audio_hw/AudioTmsIpc(10225): adev_init_check : Enter
D/tms_audio_hw/AudioTmsIpc(10225): adev_set_master_volume : Enter 1.000000
I/AudioFlinger(10225): loadHwModule() Loaded tms audio interface from TMS Audio HW HAL (audio) handle 5
E/AudioPolicyManagerBase(10225): Not output found for attached devices 00000003
E/AudioPolicyManagerBase(10225): Failed to open primary output
E/AudioPolicyManagerBase(10225): getDeviceForStrategy() speaker device not found
E/AudioPolicyManagerBase(10225): getDeviceForStrategy() speaker device not found
E/AudioPolicyManagerBase(10225): getDeviceForStrategy() speaker device not found
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerListen Socket Success Name /data/TMAudioSocketServer
E/AudioPolicyService(10225): couldn't init_check the audio policy (No such device)
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerListen Bind Success gAudioServerLocalSockFd 20
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerListen Listen Done gAudioServerLocalSockFd 20 ret 0
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerListen PLATFORM_AUDIO_CMD SIZE 16
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerListen PLATFORM_AUDIO_DATA SIZE 24
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerListen PLATFORM_AUDIO_META_DATA SIZE 20
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerListen SizeInBytes 12288
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerListen : Givimg Permission 0777 mode , 0 ret
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerListen accept Start len 110 gAudioServerLocalSockFd 20
V/TranscoderService(10225): TranscoderService created
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsClientListen :Enter
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsClientListen Socket Success Name /data/TMAudioSocketClient
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsClientListen Bind Success gAudioClientLocalSockFd 23
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsClientListen Listen Done gAudioClientLocalSockFd 23 ret 0
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsClientListen PLATFORM_AUDIO_CMD SIZE 16
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsClientListen PLATFORM_AUDIO_DATA SIZE 24
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsClientListen PLATFORM_AUDIO_META_DATA SIZE 20
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsClientListen accept Start len 110 gAudioClientLocalSockFd 23
D/tms_audio_hw/AudioTmsIpc(10225): AudioTmsServerListen : Givimg Permission 0777 mode , 0 ret
I/power ( 5291): *** release_dvfs_lock : lockType : 1
D/CustomFrequencyManagerService( 5291): releaseDVFSLockLocked : Getting Lock type frm List : DVFS_MIN_LIMIT frequency : 1566000 uid : 10135 pid : 8603 tag : [email protected]
flash this firmware, wipe data and cache after, reboot http://www.hotfile.com/dl/243289856/5f90db9/I9505XXUDMH8_I9505OXXDMHA_BTU.zip.html
Flash stock kernel again and you would be good.
I had this issue too and found it hard way that it's custom kernel causing this issue.
You can also try this.
Switch off your phone (not restart) and wait for 15-20 secs. And turn it back on. Some users are saying, this will get back your sound.
I have flash that many Times but i will test that again .... Thanks for Help.
Is that the same Rom ? :
I9505XXUDMH8_I9505OXXDMHA_I9505XXUDMH8_HOME.tar.md5
ok, i have Flash now the Rom again, have 3 Times make a Factory Reset + Cache Wipe
Then i have Flash the Kernel only and power of for 20 Seconds my Galaxy then i have Reboot that but no Sound again
Then i have make a LogCat and the Same here: (No Speaker found)
D/ALSADevice( 6355): No valid input device: 0
V/ALSADevice( 6355): switchDevice,rxDev:Speaker, txDevnull), curRxDev:None, curTxDev:None
D/alsa_ucm( 6355): snd_use_case_set(): uc_mgr 0x407ba2f8 identifier _enadev value Speaker
E/alsa_ucm( 6355): Invalid current verb value: Inactive - -1
E/alsa_ucm( 6355): No valid device Speaker found
D/ALSADevice( 6355): switchDevice: mCurTxUCMDevivce None mCurRxDevDevice Speaker inCallDevSwitch = 0
V/ALSADevice( 6355): switchDevice Done
D/alsa_ucm( 6355): snd_use_case_set(): uc_mgr 0x407ba2f8 identifier _verb value HiFi
E/alsa_ucm( 6355): Control device not initialized
E/alsa_ucm( 6355): Control device not initialized
W/alsa_ucm( 6355): error snd_use_case_apply_mixer_controls
D/ALSADevice( 6355): close: handle 0x43d4ad40 h 0x0
D/ALSADevice( 6355): open: handle 0x43d4ad40, format 0x2
V/ALSADevice( 6355): Music case
D/ALSADevice( 6355): Device value returned is hw:0,0
V/ALSADevice( 6355): flags 0, devName hw:0,0
E/alsa_pcm( 6355): cannot open device '/dev/snd/pcmC0D0p', errno 2
V/ALSADevice( 6355): pcm_open returned fd -1
E/ALSADevice( 6355): open: Failed to initialize ALSA device 'hw:0,0'
E/AudioHardwareALSA( 6355): Device open failed
I/audio_a2dp_hw( 6355): adev_open: adev_open in A2dp_hw module
I/AudioFlinger( 6355): loadHwModule() Loaded a2dp audio interface from A2DP Audio HW HAL (audio) handle 3
I/AudioFlinger( 6355): loadHwModule() Loaded usb audio interface from SEC USB audio HW HAL (audio) handle 4
D/tms_audio_hw/AudioTmsIpc( 6355): adev_open : Enter
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsInitSilenceFrames : Enter
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsInitSilenceFrames : Exit
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerInit :Enter
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerInit: thread started with name =TerminalModeAudioServer and id = 1138011176
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerInit exit
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerListen :Enter
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsClientSetup : Enter
D/tms_audio_hw/AudioTmsIpc( 6355): initMutex: AudioClientSocketMutex Mutex Created
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsClientSetup : Exit
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsClientInit :Enter
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsClientInit: thread started with name =TerminalModeAudioClient and id = 1138011256
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsClientInit exit
D/tms_audio_hw/AudioTmsIpc( 6355): adev_open : Exit
D/tms_audio_hw/AudioTmsIpc( 6355): adev_init_check : Enter
D/tms_audio_hw/AudioTmsIpc( 6355): adev_set_master_volume : Enter 1.000000
I/AudioFlinger( 6355): loadHwModule() Loaded tms audio interface from TMS Audio HW HAL (audio) handle 5
E/AudioPolicyManagerBase( 6355): Not output found for attached devices 00000003
E/AudioPolicyManagerBase( 6355): Failed to open primary output
E/AudioPolicyManagerBase( 6355): getDeviceForStrategy() speaker device not found
E/AudioPolicyManagerBase( 6355): getDeviceForStrategy() speaker device not found
E/AudioPolicyManagerBase( 6355): getDeviceForStrategy() speaker device not found
E/AudioPolicyService( 6355): couldn't init_check the audio policy (No such device)
V/TranscoderService( 6355): TranscoderService created
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsClientListen :Enter
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsClientListen Socket Success Name /data/TMAudioSocketClient
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsClientListen Bind Success gAudioClientLocalSockFd 21
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsClientListen Listen Done gAudioClientLocalSockFd 21 ret 0
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerListen Socket Success Name /data/TMAudioSocketServer
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerListen Bind Success gAudioServerLocalSockFd 22
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsClientListen PLATFORM_AUDIO_CMD SIZE 16
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerListen Listen Done gAudioServerLocalSockFd 22 ret 0
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerListen PLATFORM_AUDIO_CMD SIZE 16
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerListen PLATFORM_AUDIO_DATA SIZE 24
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerListen PLATFORM_AUDIO_META_DATA SIZE 20
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerListen SizeInBytes 12288
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerListen : Givimg Permission 0777 mode , 0 ret
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerListen accept Start len 110 gAudioServerLocalSockFd 22
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsClientListen PLATFORM_AUDIO_DATA SIZE 24
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsClientListen PLATFORM_AUDIO_META_DATA SIZE 20
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsClientListen accept Start len 110 gAudioClientLocalSockFd 21
D/tms_audio_hw/AudioTmsIpc( 6355): AudioTmsServerListen : Givimg Permission 0777 mode , 0 ret
W/ActivityManager( 764): Launch timeout has expired, giving up wake lock!
it maybe a hardware issue.
dial *#7353# and make test
I have a Pit Rom here
Factory_Firmware_Full_Wipe_I9505XXUBMGA_I9505OXXBMG3_NEE
and:
GT-I9505-Factory-Firmware-Full-Wipe-DBT I9505OXABMF8
But when i load that in Odin , i will become a error , invalid .....
Same is with that Rom (one File Rom)
I9505XXUBMEA_I9505OXABMEA_I9505XXUBMEA_HOME.tar.md5 is invalid
I can only flash 1 File Roms
<OSM> MD5 hash value is invalid
<OSM> PDA_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is invalid.
<OSM> End...
no sound here too , here are log Files:
E/Encryption( 187): created DirEncryptionManager
D/Vold ( 187): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Encryption( 187): enable android secure container 'sdcard'
D/Vold ( 187): Volume sda state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 187): Volume sdb state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 187): Volume sdc state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 187): Volume sdd state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 187): Volume sde state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 187): Volume sdf state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 187): '/dev/block/mmcblk0' : disk_size (15758000128)
D/DirectVolume( 187): DirectVolume::readId -> path '/sys/devices/platform/msm_sdcc.2/mmc_host/mmc2/mmc2:e624/block/mmcblk1/device/cid'
D/DirectVolume( 187): DirectVolume::readId -> id '035344535530384780303189d800cab0'
D/DirectVolume( 187): DirectVolume::handleDiskAdded -> mDiskMajor 179, mDiskMinor 32, NPARTS:1
D/Vold ( 187): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
W/PackageManager( 766): Unknown permission com.sec.android.permission.VIDEOHUB in package com.sec.android.app.videoplayer
W/PackageManager( 766): Unknown permission android.permission.SYSTEM_ALERT in package com.sec.android.app.videoplayer
I have upload the LogFile, when you have time for that, you can look on that. Thanks
http://ul.to/k34sopfp
wolfsstolz said:
I have a Pit Rom here
Factory_Firmware_Full_Wipe_I9505XXUBMGA_I9505OXXBMG3_NEE
and:
GT-I9505-Factory-Firmware-Full-Wipe-DBT I9505OXABMF8
But when i load that in Odin , i will become a error , invalid .....
Same is with that Rom (one File Rom)
I9505XXUBMEA_I9505OXABMEA_I9505XXUBMEA_HOME.tar.md5 is invalid
I can only flash 1 File Roms
<OSM> MD5 hash value is invalid
<OSM> PDA_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is invalid.
<OSM> End...
no sound here too , here are log Files:
E/Encryption( 187): created DirEncryptionManager
D/Vold ( 187): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Encryption( 187): enable android secure container 'sdcard'
D/Vold ( 187): Volume sda state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 187): Volume sdb state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 187): Volume sdc state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 187): Volume sdd state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 187): Volume sde state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 187): Volume sdf state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 187): '/dev/block/mmcblk0' : disk_size (15758000128)
D/DirectVolume( 187): DirectVolume::readId -> path '/sys/devices/platform/msm_sdcc.2/mmc_host/mmc2/mmc2:e624/block/mmcblk1/device/cid'
D/DirectVolume( 187): DirectVolume::readId -> id '035344535530384780303189d800cab0'
D/DirectVolume( 187): DirectVolume::handleDiskAdded -> mDiskMajor 179, mDiskMinor 32, NPARTS:1
D/Vold ( 187): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
W/PackageManager( 766): Unknown permission com.sec.android.permission.VIDEOHUB in package com.sec.android.app.videoplayer
W/PackageManager( 766): Unknown permission android.permission.SYSTEM_ALERT in package com.sec.android.app.videoplayer
I have upload the LogFile, when you have time for that, you can look on that. Thanks
http://ul.to/k34sopfp
Click to expand...
Click to collapse
sound wont work with older firmware even with the pit. you have to flash official updated firmware hard reset your device.also make sure its your phones official firmware.if that don't work try kies emergency firmware upgrade. hope this helps.
Hello,
i got a D802 phone which apparently has some sensors disabled in some way. When apps try to use them (so the system see them as existent) they fail or crash.
here some example log:
-Orientation:
Code:
W/OrientationEventListener( 957): Cannot detect sensors. Invalid disable
-Calibration:
Code:
E/AndroidRuntime( 7456): java.lang.NullPointerException: Attempt to invoke virtual method 'int android.hardware.Sensor.getType()' on a null object reference
E/AndroidRuntime( 7456): at com.qualcomm.sensors.sensortest.SensorID$SensorTyp e.getSensorType(SensorID.java:61)
E/AndroidRuntime( 7456): at com.android.settings.lge.MotionSensorCalibration$C alThreadRunnable.run(MotionSensorCalibration.java: 228)
E/AndroidRuntime( 7456): at java.lang.Thread.run(Thread.java:818)
-Gravity:
Code:
I/SensorManager(14094): registerListenerImpl() [Sensor: LGE Gravity Sensor, Rate: 200000, SensorEventListener: [email protected]] by com.kfodor.MySensors.SensorView.registerSensorListener():735
D/sensors_hal_SAM( 949): batch:sensor(android.sensor.gravity) handle:29 freq:1 report_rate:1 max:1.000000 min:0.000000
D/sensors_hal_Gravity( 949): enable: handle=29
D/sensors_hal_Gravity( 949): enable: handle=29, freq=1 report_rate=1 batch_rate=0 batched=0 wakeup 0
D/sensors_hal_Gravity( 949): enable: handle=29 synchronous req
I/sensors_hal_SAM( 949): sendEnableReq:sensor(android.sensor.gravity) Sending enable to svc no:20
E/Sensors ( 474): sns_acm_mr.c(776):Request made to disabled service
E/Sensors ( 474): sns_main.c(1331):Error writing request. sns_err 3 error 0 qmi_err 0
E/sensors_hal_Gravity( 949): processResp: Msg 2; Result: 1, Error: 3
D/sensors_hal_Gravity( 949): enable: Received Response: 1
-Acceleration:
Code:
I/sensors_hal_SAM( 949): sendEnableReq:sensor(android.sensor.linear_acceleration) Sending enable to svc no:20
E/Sensors ( 474): sns_acm_mr.c(776):Request made to disabled service
E/Sensors ( 474): sns_main.c(1331):Error writing request. sns_err 3 error 0 qmi_err 0
E/sensors_hal_LinearAccel( 949): processResp: Msg 2; Result: 1, Error: 3
-Rotation:
Code:
I/sensors_hal_SAM( 949): sendEnableReq:sensor(android.sensor.rotation_vector) Sending enable to svc no:18
E/Sensors ( 474): sns_acm_mr.c(776):Request made to disabled service
E/Sensors ( 474): sns_main.c(1331):Error writing request. sns_err 3 error 0 qmi_err 0
E/sensors_hal_RV( 949): processResp: Msg 2; Result: 1, Error: 3
I/SensorManager(14094): removeAllSensors() [Sensor: LGE Rotation Vector Sensor] by com.kfodor.MySensors.SensorView.registerSensorListener():732
I followed a lot of paths to find a solution, different distributions and full revert to all available stock versions. no way.
As my last trial I want to try to compare my NV data with a working one to search for some misconfigured parameter.
I found a great guide on how to access and extract all NV parameters and save to a text file, here:
http://www.droidviews.com/how-to-bac...imei-on-lg-g2/
As you can see, the guide is for changing IMEI, but the application permit to dump all parameters to a file.
I ask some good man to send me his dump. or i can send mine and get the differences. Because this file contains sensitive data, they should be removed (IMEI, S/N, MAC) even if i am not interested in stealing ids!
I have a D802 32GB.
thank you to everyone, hope to receive some useful feedback!.
Fabio T