I don't like quite speaker of DHD, and don't want use non sense rom.
After small research i have found working solution
DSP manager needs customized libaudioflinger.so, but if just replace it, all sound gone on sense rom.
I have taken libaudioflinger.so and libaudio.so from CyanogenMod 6.1.0 Beta 3, and replaced. DSP Manager WORKS fine!
But then i have found another problem, DSP Manager disables it's eq when phone in call (also when it's ringing), so i have modified manager source and added new page for speaker settings when phone ringing.
All what you do, you doing on own risk, I'm not responsible for any damage!
Backup libaudioflinger.so and libaudio.so from /system/lib/ before continue
This patch will break dolby and srs features of preinstalled music player
2010.11.29 This patch also breaks working of stereo bluetooth headset, but in in call bluetooth headset works well
- Install patch using Recovery
Download DSPManager-DHD-update.zip
Copy it to phones sdcard
Reboot to recovery and apply this update.
- Install manually (using adb) * you need to know what is adb and how use it, and have S-OFF with ENG HBOOT
Download DSPManager-DHD-files.zip
Unpack files to temporary directory
Remount /system on phone as rw (run 'adb shell', then rund command in shell 'mount -o remount,rw /dev/block/mmcblk0p25 /system')
Run commands from computer
#adb push libaudio.so /system/lib/
#adb push libaudioflinger.so /system/lib/
#adb push DSPManager-DHD.apk /system/app/
and then reboot your phone.
- Uninstall manually (using adb) * you must have S-OFF with ENG HBOOT
Connect phone to computer using usb
Open adb shell (run adb shell)
Remount system as read write (run in shell 'mount -o remount,rw /dev/block/mmcblk0p25 /system')
Then you need copy to /system/lib/ on phone backuped files libaudioflinger.so and libaudio.so.
If you backuped it on computer, then locate they and in backup folder run
#adb push libaudio.so /system/lib/
#adb push libaudioflinger.so /system/lib/
if you backuped files on sdcard, then from adb shell run commands
cp libaudio.so /system/lib/
cp libaudioflinger.so /system/lib/
rm /system/app/DSPManager-DHD.apk
then reboot your phone
- Uninstall with recovery, rollback libs to stock v 1.32.405.6
Download DSPManager-DHD-uninstall.zip
Place it on sdcard, and install this update from recovery.
How it's works (amplify about +6db):
to moderators: i'm posting in
'Desire HD Android Development' because using this patch required changing /system/ partition
So is it a lot louder with DSP manager installed?
I am especially interested in ring volume and notification volume as i am finding that I tend to miss some calls and SMS's because i dont hear them
Speaker it self not so good.
But overal volume can be increased. Is it will be enough for you - don't know.
All changes made by 5band equalized, in range +/- 10db (as drawn in configuration utility)
Works great, thanks!
I find the trick with the DHD is to make sure you put it in your pocket with the screen facing your leg since the back speaker is much more powerful than the front one.
exidler said:
Speaker it self not so good.
But overal volume can be increased. Is it will be enough for you - don't know.
All changes made by 5band equalized, in range +/- 10db (as drawn in configuration utility)
Click to expand...
Click to collapse
Ok I have installed it.
What settings are you using for gain in the 5 bands? I have tried +6 in all five.
Will this also work for notifications and sms notifications?
I posted about this app on the LeeDroid Rom thread. Maybe Lee could add the app to his Rom if enough people are interested...
Just to inform you all this knocks out dolby and srs. Restoring the system lib files should restore them though.
broncogr said:
What settings are you using for gain in the 5 bands?
Click to expand...
Click to collapse
i have using 5.0, 6.7, 6.5, 6.0, 4.3 (i'm don't like high pich of speaker)
SkilletDesire said:
Just to inform you all this knocks out dolby and srs. Resorting the system lib files should restore them though.
Click to expand...
Click to collapse
thanks, i will write about it in first post.
Would it be possible to hack the Dolby / SRS feature in a way that you can globally enable it so that every music player and even system sounds/notifications can benefit from it?
That would be pretty awesome, I kinda like the sound of those features, but I dislike the music player. I think this would be a cool thing to explore / include on custom ROMs.
Nice job! Was getting round to this one, its already an add-on for my Desire ROM
Swyped from my LeeDrOiD loaded HTC Desire HD using my thumb....
Excellent work
maybe some one would be so kind to make a before and after video so that we can all see how great this patch works?
lukesky said:
maybe some one would be so kind to make a before and after video so that we can all see how great this patch works?
Click to expand...
Click to collapse
I have uploaded video, look in first post.
Noticed the difference...great work !
Doesn't work on Legend/FroYo
I am using an unofficial froyo build for the legend. http://forum.xda-developers.com/showthread.php?t=841517
Unfortunately the DSPManager doesn't work with that rom
E/AndroidRuntime( 122): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
E/AndroidRuntime( 122): java.lang.UnsatisfiedLinkError: Library android_servers not found
E/AndroidRuntime( 122): at java.lang.Runtime.loadLibrary(Runtime.java:461)
E/AndroidRuntime( 122): at java.lang.System.loadLibrary(System.java:557)
E/AndroidRuntime( 122): at com.android.server.SystemServer.main(SystemServer.java:908)
E/AndroidRuntime( 122): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 122): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 122): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
E/AndroidRuntime( 122): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
E/AndroidRuntime( 122): at dalvik.system.NativeStart.main(Native Method)
I/Process ( 122): Sending signal. PID: 122 SIG: 9
E/AndroidRuntime( 122): Error reporting crash
E/AndroidRuntime( 122): java.lang.NullPointerException
E/AndroidRuntime( 122): at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:76)
E/AndroidRuntime( 122): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:887)
E/AndroidRuntime( 122): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:884)
E/AndroidRuntime( 122): at dalvik.system.NativeStart.main(Native Method)
I/Zygote ( 121): Exit zygote because system server (122) has terminated
D/AndroidRuntime( 130):
Click to expand...
Click to collapse
Just a quick side note...
Couldn't get the CWM.zip to work so I pushed the files using root explorer...worked fine
Excellent job I can hear now lol
Kimi123 said:
I am using an unofficial froyo build for the legend. http://forum.xda-developers.com/showthread.php?t=841517
Unfortunately the DSPManager doesn't work with that rom
Click to expand...
Click to collapse
This *.so libraries only for Desire HD hardware.
Look for original DSP Manger package
@exidler
I have written a little guide for your DSPManager patch on our website, hope you don't mind.
http://hemorrdroids.net/do-you-wish-your-desire-hd-speaker-could-be-louder/#more-2424
Thanks a lot for this development. At least we know this low speaker issue can be developed or fixed via software update, I hope HTC engineers will see and integrate it this into new batches with a few developments so that new users al least will not suffer
I think my qualcomm mobile development platform MSM8655 based android phone has been bricked. I was trying to install browser.apk on my phone from my computer using adb. I followed the instructions below.
adb push (location of stock Browser.apk) /system/app/Browser.apk
adb shell
mount -o ro,remount -t yaffs2 /dev/block/mtdblock4 /system
sync
For some reason, when I was "mounting" the phone, it gave me a message that " the device is busy". I still went ahead and did the "sync".
After that, I switched off the phone. When I tried to switch on the phone, nothing comes on the screen. Not even the android logo!
I tried to do a hard reset by holding both the power and volume up button. But it still didnot work.
In some forums, I read that this problem may occur because of USB charging. They had suggested to charge the phone using the plug and removing the battery and placing it again. I tried it and it also did not work.
I did found that adb is detecting the device. Is there anything that I can do using adb?
I am very desperate. Please help me.. Thanks
So you went ahead after if hadn't mounted the device. That means what you thought you put onto what you were trying to mount hasn't gone there at all.
Update
I guess you are right about it. I think the browser.apk which I was trying to install did not get installed.
Anyway, I went ahead and tried to do some debugging using adb. When I typed "adb logcat *:W", I am seeing an error message saying "Error preloading android.webkit.WebViewCore". Can anybody decipher the meaning of this? Thanks for the help
Update
I think my phone is stuck in a boot loop. The adb log message keeps printing the stuff below. Can anybody decipher the meaning of it? I think it has to do something with the browser installation which I was playing with.
I don't have a custom recovery or nandroid backup. So I am in a big soup. Please help me. Any pointers will be greatly appreciated...
W/MediaProfiles( 8660): could not find media config xml file
W/dalvikvm( 8660): Exception Ljava/lang/UnsatisfiedLinkError; thrown during Land
roid/webkit/WebViewCore;.<clinit>
E/Zygote ( 8660): Error preloading android.webkit.WebViewCore.
E/Zygote ( 8660): java.lang.ExceptionInInitializerError
E/Zygote ( 8660): at java.lang.Class.classForName(Native Method)
E/Zygote ( 8660): at java.lang.Class.forName(Class.java:235)
E/Zygote ( 8660): at java.lang.Class.forName(Class.java:182)
E/Zygote ( 8660): at com.android.internal.os.ZygoteInit.preloadClasses(Zyg
oteInit.java:302)
E/Zygote ( 8660): at com.android.internal.os.ZygoteInit.main(ZygoteInit.ja
va:579)
E/Zygote ( 8660): at dalvik.system.NativeStart.main(Native Method)
E/Zygote ( 8660): Caused by: java.lang.UnsatisfiedLinkError: Library webcore no
t found
E/Zygote ( 8660): at java.lang.Runtime.loadLibrary(Runtime.java:461)
E/Zygote ( 8660): at java.lang.System.loadLibrary(System.java:557)
E/Zygote ( 8660): at android.webkit.WebViewCore.<clinit>(WebViewCore.java:
61)
E/Zygote ( 8660): ... 6 more
E/Zygote ( 8660): setreuid() failed. errno: 17
W/dalvikvm( 8660): threadid=1: thread exiting with uncaught exception (group=0x4
001d7d8)
Hard bricking sucks
I just bricked a week old atrix, so I know exactly how you feel... It really sucks when something like that happens.
I was bricked my alcatel one touch 990 ,but i now use Htc hd2 and its soo nice and good phone,i love it
So is your device rooted??? If so, could you wipe and re-install your OS???
Please try to refrain from practicing thread necromancy just to say "me too." Start your own thread if you're having issues.....
There are many ways to unbrick your phone, just find a valid forum post and follow the iunstructions
Since adb is able to detect the phone, if you can find an ruu for your particular device then perhaps you can restore everything to stock.
Have you tried putting it in download mode and connecting to Odin to flash?
GL!
A couple of weeks ago I bricked my Samsung Galaxy S plus, but I just put it into download mode and flashed it. Maybe that will help.
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:
Moscow Desire said:
Just a little more info when doing logcat.
Remember, Logcat will run till you end the session. And it won't always create the file till you do so. It's possible you may not see the logfile for a minute or so.
Edit: For phones/tablets with internal storage & external sd:
(note that the location naming convention may be different depending on device)
Open your terminal app;
Type: logcat > /sdcard/logcat.txt (this should create it in internal memory on the tablet)
To send to ext sd card: logcat > /mnt/external_sd/logcat.txt
I use a tablet for example Phones may have a different naming convention.
MD
Click to expand...
Click to collapse
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
FuzzyMeep Two said:
I have made a tool to simplify this for people. I will send you the .bat version, to see the validity of the file, and post the .exe for everyone else.
http://logcat-tool.googlecode.com/files/logcatHELPER.exe
I made this in about a half hour, so if you fnd any issues let me know. I believe i worked out all functionality issues, and do plan on expanding functionality in the future.
Click to expand...
Click to collapse
(If you used his tool, here's his post, thank him for his work!)
Very nicely done, now i have something i can refer people to
Perfect tutorial. Well done. ... I'll translate your tutorial into my language to share it other people.
pRo_lama said:
Perfect tutorial. Well done. ... I'll translate your tutorial into my language to share it other people.
Click to expand...
Click to collapse
Thank you! And thanks for taking your time to translate it!
If you need me to clarify anything shoot me a PM, and I'll help! (Same goes for anybody else interested in porting to their language)
Pax
Very nice, but I do have a question (and I started programming for Android recently): What do you do when the system reboots while debugging (in my case musb_hdrc.ko)? I tried catlog, but the logs are empty... Is there another way to do that?
Thank you in advance
Krain said:
Very nice, but I do have a question (and I started programming for Android recently): What do you do when the system reboots while debugging (in my case musb_hdrc.ko)? I tried catlog, but the logs are empty... Is there another way to do that?
Thank you in advance
Click to expand...
Click to collapse
Use adb instead of an in-android method to capture the logs, you can start when the boot animation starts (note: Not when the kernel splash screen appears) and when it reboots, it'll automatically end. (i.e. run the following in command prompt:
Code:
adb logcat *:E > oh_nos_it_crashed.txt
)
If you're not getting to the boot animation (keeps cycling on the Kernel splash screen) then you have kernel issues, and you need a kernel that has integrated last_kmsg (a whole different ball of wax that I'm still learning about) to figure out what's going on. (kmesg's are direct kernel output)
Maybe if someone like AdamOutler (or any other Dev who has a much better handle on them than myself) were to explain them, it'd help
Pax
Hey man regarding your guide .
I was testing a built of cm9 from my htc one v and it wasnt booting so the dev told me to do a logcat for it .
Just wondering what the process and commands would be?
Thanks.
Just a little more info when doing logcat.
Remember, Logcat will run till you end the session. And it won't always create the file till you do so. It's possible you may not see the logfile for a minute or so.
But what if you can't connect ADB to your device? You can do this
(note that the location naming convention may be different depending on device)
Open your terminal app;
Type: logcat > /sdcard/logcat.txt (this should create it in internal memory on the tablet)
To send to ext sd card: logcat > /mnt/external_sd/logcat.txt
I use a tablet for example Phones may have a different naming convention.
Nice definition of the display terminology
MD
tranceph0rmer said:
Hey man regarding your guide .
I was testing a built of cm9 from my htc one v and it wasnt booting so the dev told me to do a logcat for it .
Just wondering what the process and commands would be?
Thanks.
Click to expand...
Click to collapse
What you'll wanna do is run the following,
Code:
adb logcat *:E > crash.txt
And look at the output file specifically for lines that say 0x0deadbaad (if you see that, that means there's a problem with the Java libraries it references above it) otherwise look for other F/ lines, that'll point you in the right direction.
If you're having issues where and is not accessible for to buy having USB debugging turned off because of doing a /data wipe (factory data reset) first install a similar Rom (in your case, a prior, stable CM9, boot into it, turn on usb debugging, reboot into recovery & only write /cache & dalvik cache before installing the offending Rom & getting your logcat (sorry if I rambled, just got done working a double )
Pax
Sent from my R800x using Tapatalk 2
Moscow Desire said:
Just a little more info when doing logcat.
Remember, Logcat will run till you end the session. And it won't always create the file till you do so. It's possible you may not see the logfile for a minute or so.
But what if you can't connect ADB to your device? You can do this
(note that the location naming convention may be different depending on device)
Open your terminal app;
Type: logcat > /sdcard/logcat.txt (this should create it in internal memory on the tablet)
To send to ext sd card: logcat > /mnt/external_sd/logcat.txt
I use a tablet for example Phones may have a different naming convention.
Nice definition of the display terminology
MD
Click to expand...
Click to collapse
Thanks, MD!
The problem is when you can't access terminal (bootloops, fc'ing like it's going out of style, etc.) that adb is really useful. Sometimes to trick the system into working, you can (esp with AOSP based roms) install a same version of android (I.e. 4.0.4) & not wipe /data (after turning on usb debugging) & still have an access (I learned this after spending about 2-3 months crack flashing my own builds & getting tired of titanium restoring all my apps)
Pax
Sent from my R800x using Tapatalk 2
Great guide, thanks! Found it through the portal. I just added to my sig so maybe it will help stop some of those questions.
paxChristos said:
What you'll wanna do is run the following,
Code:
adb logcat *:E > crash.txt
And look at the output file specifically for lines that say 0x0deadbaad (if you see that, that means there's a problem with the Java libraries it references above it) otherwise look for other F/ lines, that'll point you in the right direction.
If you're having issues where and is not accessible for to buy having USB debugging turned off because of doing a /data wipe (factory data reset) first install a similar Rom (in your case, a prior, stable CM9, boot into it, turn on usb debugging, reboot into recovery & only write /cache & dalvik cache before installing the offending Rom & getting your logcat (sorry if I rambled, just got done working a double )
Pax
Sent from my R800x using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the info.
Will do that the next time i get stuck at the boot animation
can anyone tell me how to clear / reset logcat?
Thanks in advance
riteshbendre said:
can anyone tell me how to clear / reset logcat?
Thanks in advance
Click to expand...
Click to collapse
Why would you want to do that?
To my knowledge, the only way logcat is reset is if you reboot your phone.
That's why filtering your results is very helpful, because no matter how long it's been running, you can get the info that you want without extraneous information
Pax
Thanks for the clarifications
Man thank you so much for the awesome guide!
Now I can actually filter out my logcat results instead of searching through the entire log.
Sent using Tapatalk
Helpful Tool
paxChristos said:
Here's how to use logcat.....
Click to expand...
Click to collapse
I have made a tool to simplify this for people. I will send you the .bat version, to see the validity of the file, and post the .exe for everyone else.
FIXED HUGE ISSUE CAUSING EMPTY FILES
DOWNLOAD
PM or post here if you run into any issues. They WILL be addressed.
I have made a tool to simplify Logcat creation for people. The creation of this tool was inspired, and guided, by the thread started HERE by paxChristos.
UPDATE 4.1
Corrected an issue causing empty files.
apparently, if the process id contained a space ( 1234) the file would parse correctly, but if the numbers came up to the parenthesis (12345) it would output an empty file named ACTIVITY(12345) with no extension.
This was a huge issue, and i apologize for not seeing it sooner. It has been corrected, and the logcat tool works better than ever. I just ran through a 20,000 line logcat without any empty files appearing.
a couple more things to help with stability.
Underscores (_) will be replaced by dashes (-)
Brackets ([]) and arrows (<>) will be replaced with paranthesis(())
-------------------------------------------------------------------------------------------------------------
HUGE UPDATE
Added the ability to "SUPER PARSE" Files, which separates files into folders by log level and creates a TXT file for each activity
Super parse DOES NOT Work with LONG format Logs.
SUPER PARSE is in its infancy I do expect errors, please let me know if you run into anything.
OLD STUFF
EDIT V3.6 DONE
Added ability to filter logcats by activity name. (logcat -s "FILTER")
Fixed Log Level Setting
EDIT V3.5 DONE
NOW PROPERLY PARSES "LONG" FORMAT LOGCATS.
Thank you to Senior Member jes0411 for pointing out the issues that lead me to create V3.4 and 3.5. If any of you have an issue please let me know. It could be hours before i get to it or weeks, but i will get to fixing it.
EDIT V3.4 DONE
Changed the way the date variable was handled to hopefully fix issues experienced by users of non-English versions of windows.
EDIT V3.3 DONE
EDIT V 3.2 Finished
Google code won't allow any new uploads, so i uploaded the new update to XDA in a ZIP file.
Fixed ADB Location settings, some users were having trouble if they input the ADB folder with any quotation marks in the path name, it will now automatically remove quotation marks to ensure correct syntax.
Fixed issue with ADB Location setting not exiting to previous menu.
Fixed issue with Log Level setting not exiting to previous menu.
Capitalized some stuff
Added a feature that will automatically create the selected folder if no output folder exists and the user attempts to run a log.
Added a check when selecting an output folder that will ask if you want the folder created if it does not exist
EDIT V3.1 DONE
FIXED OPTIONS 7 & 8, URLS WERE MISSING A "?"
CHANGELOG EDITS
SAVES AND PARSES FILES IN TO DIFFERENT OUPUT FILES BASED ON LOG LEVEL (E , I , D , W , ETC)
LOGCAT TOOL v1.1 by FuzzyMeep TWO
I made this in about a half hour, so if you fnd any issues let me know. I believe i worked out all functionality issues, and do plan on expanding functionality in the future.
reposted HERE
Edit: source here.
Batch Source
EDIT: UPDATED TO V1.1
added the framework to add filtering to your logcat, it is in the exe, but not utilized yet (still bugy). i have also worked out a few minor bugs in this release.
Very nice tut. Will try
thanks a ton for the in depth guide. I was always fairly confused on how to approach this, so now I'll have something to refer to in order to help all of the awesome devs here.
mcmb03 said:
thanks a ton for the in depth guide. I was always fairly confused on how to approach this, so now I'll have something to refer to in order to help all of the awesome devs here.
Click to expand...
Click to collapse
+1