How's the sound?

Originally Posted by brainard52

Alright. I'll look into it. Anything cool going on with the ROM?

Unfortunately, the main cna dev had to take care of personnel matters & there haven't been any major updates to the code base.

Originally Posted by savage24x

How's the sound?

Same as any other ics AOSP based ROM(I'll look into tweaking sound eventually)

Sent from my R800x using Tapatalk 2

Originally Posted by paxChristos

Same as any other ics AOSP based ROM(I'll look into tweaking sound eventually)

Sent from my R800x using Tapatalk 2

Dammit! The only thing keeping me from ICS is the damn sound. Ugh!



Sent from my iDevice

*whines* Pax!?!?! Which files do I use for the update? I am on 0509... Or the stuff you released when 0509 was released. C:

Originally Posted by brainard52

*whines* Pax!?!?! Which files do I use for the update? I am on 0509... Or the stuff you released when 0509 was released. C:

I'm working on a new build, I spent sometime yesterday building a device tree for zeusc & now I'm fixing all the bugs with building it for all three

Sent from my R800x using Tapatalk 2

All three? O.o and I think it would be awesome if you integrated a basic bug report app. Maybe something that sends an email to you or something. IDK, I just think it would be really easy for us to report bugs immediately when we find them. Maybe something that we can bring up with a long press of some key?

Originally Posted by brainard52

All three? O.o and I think it would be awesome if you integrated a basic bug report app. Maybe something that sends an email to you or something. IDK, I just think it would be really easy for us to report bugs immediately when we find them. Maybe something that we can bring up with a long press of some key?

What do you mean? I have one already!

LOGCAT
For future reference, I'm going to include here how to use logcat (android debugging tool.)
There are two main ways to do a logcat, within android and through adb.
Logcat within android can be installed by a logcat app:
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.

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 is

adb logcat > name of problem.txt

you can also do

adb logcat -f name of problem.txt

how I prefer to do it is this way:

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)

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 search for an error in the logcat file (it's always e/ for error, f/ for fatal. those are the two main things that matter to me.)

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 <213 00:00:00:00:00:00 0.0.0.0 0 [down]>
D/NetworkManagementService(  203): flags <[down]>
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 <manifest>: 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:

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!

How this relates to xLoud. (or any other problem we have with future updates.)
Now, since xLoud is apparently causing all sorts of havoc including not granting root , screwing up volume & messing with equalizers, a logcat done the following way will help me immensely with figuring out how to go about fixing it:

adb logcat *:E -v long > name of problem.txt

will print out all errors, fatal exceptions (what causes android to crash) that happen with the xLoud (or any other risky) update.

my email (for sending me logcats): nielson.peter@gmail.com
Complaints, requests for add-ons, stupid questions, or anything else I feel like will be deleted upon receiving it. Logcats will not.
(If you wanna complain, request something or ask a stupid questions, that's why this thread is here)

Source: http://forum.xda-developers.com/show...06&postcount=2
(Ok, so not what you wanted, but i had to say it )

Pax

Lol, thanks xD I usually just go into the terminal emulator and type in logcat > /sdcard/output.txt I didn't realize the other things could be done too, though, so thanks. I'll just report problems on here for now. The ones that I can see right now are that anything under settings > performance > startup tweaks or settings > performance > Kernel Controls (in 05/12 build) don't stick. I leave the menu and go back and they've reverted. Oh, by the way, if you hadn't guessed, I've got the SDK all set up. For some reason that I don't remember, I decided to install Archbang until I get better with Arch, in which time, I'll reinstall official Arch.

Originally Posted by brainard52

Lol, thanks xD I usually just go into the terminal emulator and type in logcat > /sdcard/output.txt I didn't realize the other things could be done too, though, so thanks. I'll just report problems on here for now. The ones that I can see right now are that anything under settings > performance > startup tweaks or settings > performance > Kernel Controls (in 05/12 build) don't stick. I leave the menu and go back and they've reverted.

Yupp, I know of that one, I think it was because of issues either with my building (if it is this, it should be fixed in forthcoming update) or because the /boot partition is hidden

Pax

Alright, I kinda figured that you'd know. So how exactly does the 3G uncap work? I thought it was carrier-side that controlled the throttling. Also, I have no idea if this is possible, but I'd love to see a way to change the color of everything through one setting. Maybe in build.prop? I'm sure it could be done. Maybe a setting called "System Color" under interface?