[REQ] Csc Menüs des Honor oder Audio Mods

[atonal]

Hallo, ich bin selbst Note 2 User, hab aber langjährige Erfahrung im Flashen und Rooten. So habe ich das Honor eines Bekannten gerootet, hat auch alles gut geklappt.... Leider habe ich bis dato für die 924 kein CWM Recovery gefunden.....
Da das Honor mit Kopfhörern wirklich sehr leise ist, habe ich nach nem Audio Mod oder sowas gesucht, aber bis dato noch nichts gefunden.... Weiss hier jemand was (Beats Audio o. Ä. konvertiert auf das Honor)?
Oder den Zugang zum Csc Menü des Honor, sprich, Eingabe von Csc Codes, z. B. #*233#*xxxxx usw, um in das interne Audio Menü zu kommen, wo man die Kopfhörer Lautstärke anheben kann...?

Wäre echt super.. .

Lg Steff

 

[reraiseace]

Jetzt verweise mal auf meinen Blog -> Lautstärke beim Huawei Honour erhöhen - GFX-Stylez.blog - IT - Web - Android - Sicherheit

Das sollte dir weiterhelfen.

 

[det-happy]

zu 1)
Der gesperrte Bootloader verhindert CWM installation. Alternative: http://www.droidwiki.de/Hauwei_Honor/cWM-ADB

zu 2) Engineering Menü *#*#2846579#*#*

zu 3) Das Programm Volume+ habe ich ebenfalls gekauft und klappt 1a

Ich werd gleich mal die 2 versch. audio_effects.conf zum vergleich posten

Der ursprüngliche Beitrag von 18:08 Uhr wurde um 18:18 Uhr ergänzt:

Spoiler: Modifiziert

# List of effect libraries to load. Each library element must contain a "path" element
# giving the full path of the library .so file.
# libraries {
# <lib name> {
# path <lib path>
# }
# }
libraries {
bundle {
path /system/lib/soundfx/libbundlewrapper.so
}
reverb {
path /system/lib/soundfx/libreverbwrapper.so
}
visualizer {
path /system/lib/soundfx/libvisualizer.so
}
pre_processing {
path /system/lib/soundfx/libaudiopreprocessing.so
}
}

# list of effects to load. Each effect element must contain a "library" and a "uuid" element.
# The value of the "library" element must correspond to the name of one library element in the
# "libraries" element.
# The name of the effect element is indicative, only the value of the "uuid" element
# designates the effect.
# The uuid is the implementation specific UUID as specified by the effect vendor. This is not the
# generic effect type UUID.
# effects {
# <fx name> {
# library <lib name>
# uuid <effect uuid>
# }
# ...
# }

effects {
bassboost {
library bundle
uuid 8631f300-72e2-11df-b57e-0002a5d5c51b
}
virtualizer {
library bundle
uuid 1d4033c0-8557-11df-9f2d-0002a5d5c51b
}
equalizer {
library bundle
uuid ce772f20-847d-11df-bb17-0002a5d5c51b
}
volume {
library bundle
uuid 119341a0-8469-11df-81f9- 0002a5d5c51b
}
reverb_env_aux {
library reverb
uuid 4a387fc0-8ab3-11df-8bad- 0002a5d5c51b
}
reverb_env_ins {
library reverb
uuid c7a511a0-a3bb-11df-860e-0002a5d5c51b
}
reverb_pre_aux {
library reverb
uuid f29a1400-a3bb-11df-8ddc-0002a5d5c51b
}
reverb_pre_ins {
library reverb
uuid 172cdf00-a3bc-11df-a72f-0002a5d5c51b
}
visualizer {
library visualizer
uuid d069d9e0-8329-11df-9168-0002a5d5c51b
}
agc {
library pre_processing
uuid aa8130e0-66fc-11e0-bad0-0002a5d5c51b
}
aec {
library pre_processing
uuid bb392ec0-8d4d-11e0-a896-0002a5d5c51b
}
ns {
library pre_processing
uuid c06c8400-8e06-11e0-9cb6-0002a5d5c51b
}
}
# Audio preprocessor configurations.
# The pre processor configuration consists in a list of elements each describing
# pre processor settings for a given input source. Valid input source names are:
# "mic", "camcorder", "voice_recognition", "voice_communication"
# Each input source element contains a list of effects elements. The name of the effect
# element must be the name of one of the effects in the "effects" list of the file.
# Each effect element may optionally contain a list of parameters and their
# default value to apply when the pre processor effect is created.
# A parameter is defined by a "param" element and a "value" element. Each of these elements
# consists in one or more elements specifying a type followed by a value.
# The types defined are: "int", "short", "float", "bool" and "string"
# When both "param" and "value" are a single int, a simple form is allowed where just
# the param and value pair is present in the parameter description
# pre_processing {
# <input source name> {
# <fx name> {
# <param 1 name> {
# param {
# int|short|float|bool|string <value>
# [ int|short|float|bool|string <value> ]
# ...
# }
# value {
# int|short|float|bool|string <value>
# [ int|short|float|bool|string <value> ]
# ...
# }
# }
# <param 2 name > {<param> <value>}
# ...
# }
# ...
# }
# ...
# }

#
# TODO: add default audio pre processor configurations after debug and tuning phase
#

Spoiler: Original

# List of effect libraries to load. Each library element must contain a "path" element
# giving the full path of the library .so file.
# libraries {
# <lib name> {
# path <lib path>
# }
# }
libraries {
bundle {
path /system/lib/soundfx/libbundlewrapper.so
}
reverb {
path /system/lib/soundfx/libreverbwrapper.so
}
visualizer {
path /system/lib/soundfx/libvisualizer.so
}
pre_processing {
path /system/lib/soundfx/libaudiopreprocessing.so
}
}

# list of effects to load. Each effect element must contain a "library" and a "uuid" element.
# The value of the "library" element must correspond to the name of one library element in the
# "libraries" element.
# The name of the effect element is indicative, only the value of the "uuid" element
# designates the effect.
# The uuid is the implementation specific UUID as specified by the effect vendor. This is not the
# generic effect type UUID.
# effects {
# <fx name> {
# library <lib name>
# uuid <effect uuid>
# }
# ...
# }

effects {
bassboost {
library bundle
uuid 8631f300-72e2-11df-b57e-0002a5d5c51b
}
virtualizer {
library bundle
uuid 1d4033c0-8557-11df-9f2d-0002a5d5c51b
}
equalizer {
library bundle
uuid ce772f20-847d-11df-bb17-0002a5d5c51b
}
volume {
library bundle
uuid 119341a0-8469-11df-81f9- 0002a5d5c51b
}
reverb_env_aux {
library reverb
uuid 4a387fc0-8ab3-11df-8bad- 0002a5d5c51b
}
reverb_env_ins {
library reverb
uuid c7a511a0-a3bb-11df-860e-0002a5d5c51b
}
reverb_pre_aux {
library reverb
uuid f29a1400-a3bb-11df-8ddc-0002a5d5c51b
}
reverb_pre_ins {
library reverb
uuid 172cdf00-a3bc-11df-a72f-0002a5d5c51b
}
visualizer {
library visualizer
uuid d069d9e0-8329-11df-9168-0002a5d5c51b
}
agc {
library pre_processing
uuid aa8130e0-66fc-11e0-bad0-0002a5d5c51b
}
aec {
library pre_processing
uuid bb392ec0-8d4d-11e0-a896-0002a5d5c51b
}
ns {
library pre_processing
uuid c06c8400-8e06-11e0-9cb6-0002a5d5c51b
}
}
# Audio preprocessor configurations.
# The pre processor configuration consists in a list of elements each describing
# pre processor settings for a given input source. Valid input source names are:
# "mic", "camcorder", "voice_recognition", "voice_communication"
# Each input source element contains a list of effects elements. The name of the effect
# element must be the name of one of the effects in the "effects" list of the file.
# Each effect element may optionally contain a list of parameters and their
# default value to apply when the pre processor effect is created.
# A parameter is defined by a "param" element and a "value" element. Each of these elements
# consists in one or more elements specifying a type followed by a value.
# The types defined are: "int", "short", "float", "bool" and "string"
# When both "param" and "value" are a single int, a simple form is allowed where just
# the param and value pair is present in the parameter description
# pre_processing {
# <input source name> {
# <fx name> {
# <param 1 name> {
# param {
# int|short|float|bool|string <value>
# [ int|short|float|bool|string <value> ]
# ...
# }
# value {
# int|short|float|bool|string <value>
# [ int|short|float|bool|string <value> ]
# ...
# }
# }
# <param 2 name > {<param> <value>}
# ...
# }
# ...
# }
# ...
# }

#
# TODO: add default audio pre processor configurations after debug and tuning phase
#

 

[MadsHH]

Moin Det-Happy,
vielen Dank für den Tipp mit Volume+, habe ich mir direkt mal gezogen.
Allerdings kann ich die "audio_effects.conf" Datei nicht finden.
Wo ist die denn versteckt?

 

[det-happy]

/system/etc

Aber ich konnte (noch) keinen Unterschied gefunden, die app muss wohl andere Stellschrauben nutze.

...using tapatalk on my huawei honor smartphone

 

[reraiseace]

Du bekommst die Version 1.9.0.4 auch kostenlos aus dem Entwickler-Forum. Muss man sich halt mal eben anmelden und schon spart man sich die 1,50 Euro. Mit der version läufts auch super, selbst ohne Root.

@det-happy
Die App nutzt eine Schwachstelle in Android aus, die aber mit Jelly Bean geschlossen wurde und daher nicht mehr auf allen Geräten funktioniert. Frag mich aber bitte nicht welche Lücke das genau ist.

 

[MadsHH]

Da habe ich mir die auch gezogen
Aber danke für den Tipp (hatte zum Glück auch vorher deinen Blog Eintrag gelesen)

 

[det-happy]

ich warte seit 1h auf die Aktivierungsmail des herstellerforums :b

...using tapatalk on my huawei honor smartphone

 

[MadsHH]

Bei mir kam die innerhalb von ein paar Sek...
Evt. noch mal neu probieren?