Related
Hi all,
Does anyone managed to compile latest CM 6.2 (froyo) sources?¿?¿. I get errors when compiling CMParts and if I choose not to compile CMParts, I get a package that gets me in to crash loops on first start.....
Many Thanks in Advance,
Perdita2000
perdita2000 said:
Hi all,
Does anyone managed to compile latest CM 6.2 (froyo) sources?¿?¿. I get errors when compiling CMParts and if I choose not to compile CMParts, I get a package that gets me in to crash loops on first start.....
Many Thanks in Advance,
Perdita2000
Click to expand...
Click to collapse
You need CMParts. Can you post the compilation errors?
These are my compile errors...
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/DisplayActivity.java:72: cannot find symbol
symbol : variable config_enableScreenOffAnimation
location: class com.android.internal.R.bool
getResources().getBoolean(com.android.internal.R.bool.config_enableScreenOffAnimation) ? 1 : 0) == 1);
^
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/DisplayActivity.java:83: cannot find symbol
symbol : variable ACCELEROMETER_ROTATE_180
location: class android.provider.Settings.System
Settings.System.ACCELEROMETER_ROTATE_180, 0) == 1);
^
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/DisplayActivity.java:96: cannot find symbol
symbol : variable ELECTRON_BEAM_ANIMATION_ON
location: class android.provider.Settings.System
Settings.System.ELECTRON_BEAM_ANIMATION_ON, value ? 1 : 0);
^
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/DisplayActivity.java:102: cannot find symbol
symbol : variable ELECTRON_BEAM_ANIMATION_OFF
location: class android.provider.Settings.System
Settings.System.ELECTRON_BEAM_ANIMATION_OFF, value ? 1 : 0);
^
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/DisplayActivity.java:108: cannot find symbol
symbol : variable ACCELEROMETER_ROTATE_180
location: class android.provider.Settings.System
Settings.System.ACCELEROMETER_ROTATE_180, value ? 1 : 0);
^
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/UIActivity.java:125: cannot find symbol
symbol : variable OVERSCROLL_EFFECT
location: class android.provider.Settings.System
Settings.System.OVERSCROLL_EFFECT, 1);
^
packages/apps/CMParts/src/com/cyanogenmod/cmparts/activities/UIActivity.java:196: cannot find symbol
symbol : variable OVERSCROLL_EFFECT
location: class android.provider.Settings.System
Settings.System.putInt(getContentResolver(), Settings.System.OVERSCROLL_EFFECT,
^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
11 errors
make: *** [out/target/common/obj/APPS/CMParts_intermediates/classes-full-debug.jar] Error 41
make: *** Waiting for unfinished jobs....
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Many Thanks for you Help!!!
Perdita2000
I'm not modifyng any code because first compilation of any CM sources I always use source as is, then I try this created CM-untouched-sources rom and start to make changes (I am developing on CM7 and would like to have my own CM6.2 too...)
Many Thanks,
Perdita2000
I would check two things:
A. That you updated all the repositories. Do another "repo sync" to make sure everything is up to date. If you are using some repositories which you forked (or someone else) they also need to be updated "manually".
B. Do a clean build, by totally removing the "out" directory and then try to recompile it.
If you are still having trouble I can try to look into it, maybe even tonight.
Download froyo_stable CMParts,then it is no problem to compile,or I upload my modified CMParts 6.2.0 with setcpu etc... if you want that
This should fix the issue:
Code:
cd packages/apps/CMParts && git checkout 69613a248519fed7d971bd6292013d36097d0107
- taken from http://forum.cyanogenmod.com/topic/15353-froyo-compile-cannot-find-symbol-error/
At least, that fixed the issue for me.
erasmux said:
I would check two things:
A. That you updated all the repositories. Do another "repo sync" to make sure everything is up to date. If you are using some repositories which you forked (or someone else) they also need to be updated "manually".
B. Do a clean build, by totally removing the "out" directory and then try to recompile it.
If you are still having trouble I can try to look into it, maybe even tonight.
Click to expand...
Click to collapse
I have done A and B yet a few days ago, but nothing was solved and I found k0ner solution too, but It seems to solved compilation issue (can't find what patch 69613a248519fed7d971bd6292013d36097d0107 do?¿?¿, don't know how to search this code on git...) but ROM compiled doesn't boot (boot loop, but don't have error now, I will reproduce it and send logcat...).
Where can I find CMParts stable?¿?¿
Many Thanks to ALL,
Perdita2000
Elelinux, do you mean use froyo-stable branch for CMParts??
Many Thanks,
Perdits2000
perdita2000 said:
Where can I find CMParts stable?¿?¿
Many Thanks to ALL,
Perdita2000
Click to expand...
Click to collapse
Here https://github.com/CyanogenMod/android_packages_apps_CMParts/tree/froyo-stable
perdita2000 said:
Elelinux, do you mean use froyo-stable branch for CMParts??
Many Thanks,
Perdits2000
Click to expand...
Click to collapse
Yes as you see in post above,download it and replace it with that CMParts you have now.
A fully up to date CM6 ROM? I sincerely hope this works out! I think this would be the ideal ROM for our HTC Hero. Gingerbread's a bit slow on the Hero, but Froyo has always worked well.
I'm just writing this to let you know I'd be hugely appreciative of any ROM that you end up producing here!
I am getting same boot loop as when I applied mentioned patch....
I have synced CMParts git with froyo-stable brunch and compile again (clean before new compile) and no errors (typical VM cores from out of memory .... I always get one or two during compilation on CM7 but everything works fine... not enough memory for compilations ( ), but after flash new rom it loops on HTC HERO with following errors...
I/dalvikvm( 161): System server process 164 has been created
I/Zygote ( 161): Accepting command socket connections
I/dalvikvm( 164): Unable to dlopen(/system/lib/libandroid_servers.so): Cannot load library: link_image[2033]: failed to link libandroid_servers.so
I/dalvikvm( 164):
D/AndroidRuntime( 164): Shutting down VM
W/dalvikvm( 164): threadid=1: thread exiting with uncaught exception (group=0x400207e0)
E/AndroidRuntime( 164): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
E/AndroidRuntime( 164): java.lang.UnsatisfiedLinkError: Library android_servers not found
E/AndroidRuntime( 164): at java.lang.Runtime.loadLibrary(Runtime.java:461)
E/AndroidRuntime( 164): at java.lang.System.loadLibrary(System.java:557)
E/AndroidRuntime( 164): at com.android.server.SystemServer.main(SystemServer.java:592)
E/AndroidRuntime( 164): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 164): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 164): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
E/AndroidRuntime( 164): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
E/AndroidRuntime( 164): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 164): Error reporting crash
E/AndroidRuntime( 164): java.lang.NullPointerException
E/AndroidRuntime( 164): at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:76)
E/AndroidRuntime( 164): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:887)
E/AndroidRuntime( 164): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:884)
E/AndroidRuntime( 164): at dalvik.system.NativeStart.main(Native Method)
I/Process ( 164): Sending signal. PID: 164 SIG: 9
I/Zygote ( 161): Exit zygote because system server (164) has terminated
D/AndroidRuntime( 172):
D/AndroidRuntime( 172): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
I/AndroidRuntime( 172): Heap size: -Xmx16m
D/AndroidRuntime( 172): CheckJNI is OFF
D/AndroidRuntime( 172): --- registering native functions ---
I/SamplingProfilerIntegration( 172): Profiler is disabled.
I/Zygote ( 172): Preloading classes...
D/dalvikvm( 172): GC_EXPLICIT freed 824 objects / 47648 bytes in 7ms
D/dalvikvm( 172): GC_EXPLICIT freed 368 objects / 19104 bytes in 7ms
I/bluetooth_ScoSocket.cpp( 172): Entry name = MY-CAR ScoTypes = 0x7f
I/bluetooth_ScoSocket.cpp( 172): Entry name = Motorola HF850 ScoTypes = 0x7
D/dalvikvm( 172): GC_EXPLICIT freed 319 objects / 18080 bytes in 8ms
D/dalvikvm( 172): GC_EXPLICIT freed 464 objects / 28864 bytes in 9ms
D/dalvikvm( 172): GC_EXPLICIT freed 2096 objects / 108592 bytes in 13ms
I'm going to take a look at /system/lib/libandroid_servers.so compilation because I think is the problem...
Many Thanks to All,
Perdita2000
Hi all,
I have tried a couple of times with no luck, can't find if there is some problem with repos or just a code error, because it compiles without any error...
Have tried to sync froyo-stable but no luck too....
Syncing work tree: 4% (9/210) error: revision master in CyanogenMod/android_device_advent_vega not found
Perdita2000
perdita2000 said:
Hi all,
I have tried a couple of times with no luck, can't find if there is some problem with repos or just a code error, because it compiles without any error...
Have tried to sync froyo-stable but no luck too....
Syncing work tree: 4% (9/210) error: revision master in CyanogenMod/android_device_advent_vega not found
Perdita2000
Click to expand...
Click to collapse
In your /android/system/.repo/manifest/ you find default.xml edit the file and remove the path for advent_vega then run repo sync again
Many Thanks Elelinux ... and sorry about "my newbie questions" .... I'm starting to use github today (more than repo init/sync ... etc)..
Perdita2000
Checked out the "froyo" branch, did a "repo sync", added HTC proprietary files and ROM Manager and started the compile.
Ran into the same compilation error from the start of this thread.
Then applied bjk's fix from here (added the diff files there so you can apply then automatically with "git apply"), then compilation completed smoothly. Boots up just fine here.
What exactly is the error you are getting?
Boot error is posted thread . Did you tried stable or current branch?
Many thanks,
Sent from my Hero using XDA App
perdita2000 said:
Boot error is posted thread . Did you tried stable or current branch?
Many thanks,
Sent from my Hero using XDA App
Click to expand...
Click to collapse
Ok, sorry didn't see it. Doesn't make much sense to me. I used the "froyo" branch (not "froyo-stable"). But this shouldn't matter.
From where did you take your proprietary libs? Try taking them from here: https://github.com/koush/proprietary_vendor_htc/tree/froyo (notice the froyo branch).
I always use device propietary files from device itself. Do you mean they could be wrong?, in fact extract-files.sh didn't pull every needed file (I thought it was wrong because haven't got any issue compiling CM7?¿?¿?).
I will try device files from koush and let you know!!!
Many Thanks to Everyone!!!
Perdita2000
My phone is currently subscribed to a CDMA network. I am able to receive text messages fine in WinMo, but when I boot FRX07.1 I am unable to receive them.
I can send and receive calls, and send texts with no problem. I have tried a variety of radio roms, and I have also set up the "special" RIL that is in the frx07 thread.
I am running energyROM in winmo world.
Can anyone shed some light on this issue for me?
scottrea said:
My phone is currently subscribed to a CDMA network. I am able to receive text messages fine in WinMo, but when I boot FRX07.1 I am unable to receive them.
I can send and receive calls, and send texts with no problem. I have tried a variety of radio roms, and I have also set up the "special" RIL that is in the frx07 thread.
I am running energyROM in winmo world.
Can anyone shed some light on this issue for me?
Click to expand...
Click to collapse
Last time I checked, this is the WinMo section not the Android section... You should've posted in the build thread. I know, you probably tried and it said you don't have enough posts .
Anyhoo, boot Android with WinMo in airplane mode. No radios should on in WinMo when booting Android.
Also might be a good idea to make sure your phone is on the latest radio firmware. I don't think there's any "special" RIL needed if you follow the steps above.
The description of this section makes no reference to one OS or the other...
Anyway,
I am currently on "Other" carrier, (tbaytel, municipally owned provider in Ontario Canada)
Do you have a suggestion for the radio? I have tried:
SPCS 2.32.00WF
Telus_1.92.00WV
2.37WV (from Neodium rom install)
Tried the airplane mode on boot thing with no luck.
The RIL fix I tried was posted by you actually: http://forum.xda-developers.com/showpost.php?p=17783461&postcount=1269
scottrea said:
The description of this section makes no reference to one OS or the other...
Anyway,
I am currently on "Other" carrier, (tbaytel, municipally owned provider in Ontario Canada)
Do you have a suggestion for the radio? I have tried:
SPCS 2.32.00WF
Telus_1.92.00WV
2.37WV (from Neodium rom install)
Tried the airplane mode on boot thing with no luck.
The RIL fix I tried was posted by you actually: http://forum.xda-developers.com/showpost.php?p=17783461&postcount=1269
Click to expand...
Click to collapse
You're not very observant, are you.
First, that post was clearly made by detule (he only quoted my directions on where to put it/how to bind mount it). Second, booting Android while WinMo is in airplane mode fixes the issue that is patched in that RIL, so if that doesn't fix the problem than the RIL won't do anything either.
Third, of course this section is for WinMo. It's the Touch Pro2 "General" section - last time I checked, WinMo was made for this device from the factory, and Android is just an add-on/port that currently sits on top of WinMo. Hence the Android section .
I use 2.37WV, which is the newest Verizon radio. I have a Sprint device, but this new radio seems to work really well, despite the provider being different.
I grabbed this log after sending a sms to the phone, which was not received. Would anyone be interested in looking at it?
Edit: I ran GetLogs again and found the following lines in the radio log:
12-06 11:38:54.650 D/RILC ( 1335): Inside responseCdmaSms
12-06 11:38:54.660 D/RILJ ( 1433): [UNSL]< UNSOL_RESPONSE_CDMA_NEW_SMS
12-06 11:38:54.660 D/SMS ( 1433): New SMS Message Received
12-06 11:38:54.660 E/SMS ( 1433): BearerData decode failed: com.android.internal.telephony.cdma.sms.BearerData$CodingException: invalid SMS address DTMF code (0)
12-06 11:38:54.670 E/SMS ( 1433): Exception dispatching message
12-06 11:38:54.670 E/SMS ( 1433): java.lang.NullPointerException
12-06 11:38:54.670 E/SMS ( 1433): at com.android.internal.telephony.cdma.SmsMessage.parseSms(SmsMessage.java:552)
12-06 11:38:54.670 E/SMS ( 1433): at com.android.internal.telephony.cdma.CdmaSMSDispatcher.dispatchMessage(CdmaSMSDispatcher.java:121)
12-06 11:38:54.670 E/SMS ( 1433): at com.android.internal.telephony.SMSDispatcher.handleMessage(SMSDispatcher.java:307)
12-06 11:38:54.670 E/SMS ( 1433): at android.os.Handler.dispatchMessage(Handler.java:99)
12-06 11:38:54.670 E/SMS ( 1433): at android.os.Looper.loop(Looper.java:123)
12-06 11:38:54.670 E/SMS ( 1433): at android.app.ActivityThread.main(ActivityThread.java:4627)
12-06 11:38:54.670 E/SMS ( 1433): at java.lang.reflect.Method.invokeNative(Native Method)
12-06 11:38:54.670 E/SMS ( 1433): at java.lang.reflect.Method.invoke(Method.java:521)
12-06 11:38:54.670 E/SMS ( 1433): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:858)
12-06 11:38:54.670 E/SMS ( 1433): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
12-06 11:38:54.670 E/SMS ( 1433): at dalvik.system.NativeStart.main(Native Method)
12-06 11:38:54.680 D/RILJ ( 1433): [0032]> RIL_REQUEST_CDMA_SMS_ACKNOWLEDGE false 96
12-06 11:38:54.690 D/RIL ( 1335): onRequest: CDMA_SMS_ACKNOWLEDGE (88)
12-06 11:38:54.690 D/RILJ ( 1433): [0032]< RIL_REQUEST_CDMA_SMS_ACKNOWLEDGE
12-06 11:38:54.960 D/AT ( 1335): AT< [MSM] Call End, curr_mode 2, call_type 3, end_status 25
DTMF code 0 is not caught in this code:
private static String decodeDtmfSmsAddress(byte[] rawData, int numFields)
throws CodingException
{
/* DTMF 4-bit digit encoding, defined in at
* 3GPP2 C.S005-D, v2.0, table 2.7.1.3.2.4-4 */
StringBuffer strBuf = new StringBuffer(numFields);
for (int i = 0; i < numFields; i++) {
int val = 0x0F & (rawData[i / 2] >>> (4 - ((i % 2) * 4)));
if ((val >= 1) && (val <= 9)) strBuf.append(Integer.toString(val, 10));
else if (val == 10) strBuf.append('0');
else if (val == 11) strBuf.append('*');
else if (val == 12) strBuf.append('#');
else throw new CodingException("invalid SMS address DTMF code (" + val + ")");
}
return strBuf.toString();
}
This must be an issue with the provider. Can I fool this into working somehow by changing the source?
Edit: adding the line:
else if (val == 0) strBuf.append('0');
fixed the issue. Sms now received.
Had to move to GB as I could not get Froyo to compile.
I've never heard of this (on CDMA). What carrier?
He gave the carrier in one of his previous posts, no name canadian carrier. Anyways, we had a similar problem with Sprint, apparently the way some carriers choose to encode their sms messages is inconsistent and thus a Mms.apk modification is needed to support the non-standard encoding. If your carrier has a native android phone, see if you can find a Mms.apk from it, if you can you can replace yours with that one and it should work. If not, you'd really need to wireshark your mms download and analyze the format as opposed to a dump of a working mms, or "step into" the process and watch what happens as it tries to decode it, if you want to make the change in code. It's certainly not easy, luckily for sprint highlandsun was willing to take a look at it for us. It still took us days to get it solved properly.
Based on what rpierce99 has said above and some Googling, I think I have the file you need.
Edit: Didn't read that last part of his log post. Oh well, disregard this unless it has some pertinence to you.
JDog2pt0 said:
Based on what rpierce99 has said above and some Googling, I think I have the file you need.
Edit: Didn't read that last part of his log post. Oh well, disregard this unless it has some pertinence to you.
Click to expand...
Click to collapse
If that's the Mms.apk from a native android device on this local canadian carrier, then it should fix the problem.
rpierce99 said:
If that's the Mms.apk from a native android device on this local canadian carrier, then it should fix the problem.
Click to expand...
Click to collapse
If he wants to use Froyo. He's got it working in GB. Anyways, a Google search pulled up this http://www.droidforums.net/forum/hacking-help/81656-no-incoming-texts-unless-using-zeusdroid.html and after some digging I found a working zeusdroid download where I extracted the mms.apk
Can I say for sure it'll work? No, but based on what I found it should.
JDog2pt0 said:
If he wants to use Froyo. He's got it working in GB. Anyways, a Google search pulled up this http://www.droidforums.net/forum/hacking-help/81656-no-incoming-texts-unless-using-zeusdroid.html and after some digging I found a working zeusdroid download where I extracted the mms.apk
Can I say for sure it'll work? No, but based on what I found it should.
Click to expand...
Click to collapse
Experiencing the same issue on a D2G, also on TBayTel's CDMA network. Tried swapping in Zeusdroid's mms.apk for the stock messaging.apk, to no avail. Any help in solving this would be appreciated... see my D2G thread here: http://forum.xda-developers.com/showthread.php?t=2156261
Thanks in advance!
kanuckdroid said:
Experiencing the same issue on a D2G, also on TBayTel's CDMA network. Tried swapping in Zeusdroid's mms.apk for the stock messaging.apk, to no avail. Any help in solving this would be appreciated... see my D2G thread here: http://forum.xda-developers.com/showthread.php?t=2156261
Thanks in advance!
Click to expand...
Click to collapse
Because asking for help for a device not supported by these forum groups, which we do not have access to, in a thread that is over a year old, which was posted in the wrong group to begin with, on an OS that is a generation behind what is being worked with.... is a brilliant idea. :victory:
Good luck with that:good:
wizardknight said:
Because asking for help for a device not supported by these forum groups, which we do not have access to, in a thread that is over a year old, which was posted in the wrong group to begin with, on an OS that is a generation behind what is being worked with.... is a brilliant idea. :victory:
Good luck with that:good:
Click to expand...
Click to collapse
Gee, Wiz, thanks for the warm welcome!
I'm a self-professed noob. In posting this in a new thread in the right group for the right phone, this thread came up as related. Since it has the same problem and a working solution on the same generation of the same OS, I thought I might post a link. I get that this thread is old and posted in the wrong group. I'm grasping at straws here... it's not a common problem.
Anyway, your point and the attached lashing are taken. Sorry for thinking I might find help here.
kanuckdroid said:
Gee, Wiz, thanks for the warm welcome!
I'm a self-professed noob. In posting this in a new thread in the right group for the right phone, this thread came up as related. Since it has the same problem and a working solution on the same generation of the same OS, I thought I might post a link. I get that this thread is old and posted in the wrong group. I'm grasping at straws here... it's not a common problem.
Anyway, your point and the attached lashing are taken. Sorry for thinking I might find help here.
Click to expand...
Click to collapse
Glad you found the right group.
This is basically the Dolby Digital Plus audio effect ported from the latest Huawei Ascend P6 beta kitkat rom.
I also ported the configuration app which you can launch from the launcher.
- Notes
If you flash this on Lollipop, make sure you uncheck "Use NuPlayer" in Developer options!!
When having FC's, put SELinux in permissive!!! SELinuxModeChanger
This started out as a Nexus 4 only project, but should work on any device now
- Versions
v1 - 20/03/2014
- Initial release
v2 - 20/03/2014
- Added /system/etc/dolby_config.xml
- Modified DolbyMobileAudioEffectService to load config from /system/etc instead of /data/cust/.../xml
- Added revert
v2.1 - 20/03/2014
- GlobalDolbyEffect uses default theme now, not Light anymore
- Flash this update after flashing v2 (it only updates the apk)
v2.2 - 23/03/2014
- Removed unused permissions from DolbyMobileAudioEffectService
- Resigned DolbyMobileAudioEffectService with CM platform key
- Flash this update after flashing v2 (it only updates the apk)
v3 - 25/03/2014
- Two versions now, one for stock based roms, one for CM based roms
- In CM based version, the DolbyMobileAudioEffectService uses shareduserid android.uid.system. This should make the service running without
a notification.
v4 beta - 27/03/2014
- Merged DolbyMobileEffectService into GlobalDolbyEffect
- Disabled call to startForeground (This disables the notification, but now the service could be killed by the system in case of memory shortage)
- When connecting a headset, a notification icon will be shown and you can change presets by clicking on the notification.
- Still in beta, I'm still testing it, but it seems to run fine, and the service wasn't killed yet in a few hours of listening to music.
Feedback is welcome !
v5 - 23/05/2014
- Target sdk changed to 17
- GlobalDolbyEffect.apk signed with private key
r6 beta - 26/11/2014
- New install script
- On lollipop or higher, new app folder structure is used. On older versions old structure is used.
- Audio_effects.conf is patched now, not overwritten, flashing this mod doesn't disable other effects.
- Added audio effects api v2 library, so it should work on <4.3 versions
- Revert zip patches audio_effects.conf now, so no other effects will be disabled during revert.
r7 - 09/12/2014
- Materialized icon
- Added addon.d script, on supported roms it survives rom updates now
- Reverter deletes addon.d script
r8 - 03/01/2014
- Hide from recents
r9 - 08/01/2015
- Also hide alert dialog from recents
- Final release, i don't think i can improve it much further.
Downloads
XDA:DevDB Information
Dolby Digital Plus (Huawei), App for the Google Nexus 4
Contributors
worstenbrood
Version Information
Status: Stable
Current Stable Version: r9
Stable Release Date: 2015-01-08
Created 2014-12-02
Last Updated 2015-01-08
Thanks for the new mod! :good:
Does it require DSP along with it, or does it work without it?
tykate said:
Thanks for the new mod! :good:
Does it require DSP along with it, or does it work without it?
Click to expand...
Click to collapse
It doesn't need DSP manager. If you have DSP manager, enabling one of the options in there will disable the dolby effect. Once you disable all effects in DSP manager, the dolby kicks back in.
worstenbrood said:
This is basically the Dolby Digital Plus audio effect ported from the latest Huawei Ascend P6 beta kitkat rom.
I also ported the configuration app which you can launch from the launcher.
- Notes
This mod works in combination with DSP Manager other effects may be disabled by flashing this mod.
- Versions
v1 - 20/03/2014 - Initial release
- Git
https://bitbucket.org/worstenbrood/dolby_digital_plus_mako
Click to expand...
Click to collapse
worstenbrood said:
It doesn't need DSP manager. If you have DSP manager, enabling one of the options in there will disable the dolby effect. Once you disable all effects in DSP manager, the dolby kicks back in.
Click to expand...
Click to collapse
is there a revert?
tykate said:
is there a revert?
Click to expand...
Click to collapse
Not yet :// I'll make one tomorrow
worstenbrood said:
It doesn't need DSP manager. If you have DSP manager, enabling one of the options in there will disable the dolby effect. Once you disable all effects in DSP manager, the dolby kicks back in.
Click to expand...
Click to collapse
superb bro... clearly hear the difference ... surround sound effects also there ...
Also, very easy to switch between DSP and dolby ...turn on dsp turn off dsp... no need to delete or revert anything
thanks again buddy ...
thx my nigga.. its so good.. thx..
It seems not working for me on Purity rom.... When I click the checkbox it doesnt happen anything. Cant check the box
Tried before and after flashing DSP Manager
EDIT: Reading the logcat it says: mDolbyMobileSystem = null
bamsbamx said:
EDIT: Reading the logcat it says: mDolbyMobileSystem = null
Click to expand...
Click to collapse
Thats not necessarily a bad thing, could you provide a full (or filtered on dolby) logcat after changing a preset in the app ?
worstenbrood said:
Thats not necessarily a bad thing, could you provide a full (or filtered on dolby) logcat after changing a preset in the app ?
Click to expand...
Click to collapse
Well, it doesnt give so much info:
Code:
E/DolbyMobileAudioEffectClient(14802): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient(14802): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient(14802): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient(14802): setDolbyEffectOn() FAILED: mDolbyMobileSystem = null.
E/DolbyMobileAudioEffectClient(14802): setGlobalEffectOn() FAILED: mDolbyMobileSystem == null
E/DolbyMobileAudioEffectClient(14802): getGlobalAudioHeadsetByPass() FAILED: mDolbyMobileSystem == null
E/DolbyMobileAudioEffectClient(14802): setDolbyEffectByPass() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient(14802): getGlobalAudioPreset() FAILED: mDolbyMobileSystem == null
E/DolbyMobileAudioEffectClient(14802): setDolbyEffect() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient(14802): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null
bamsbamx said:
Well, it doesnt give so much info:
Code:
E/DolbyMobileAudioEffectClient(14802): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient(14802): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient(14802): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient(14802): setDolbyEffectOn() FAILED: mDolbyMobileSystem = null.
E/DolbyMobileAudioEffectClient(14802): setGlobalEffectOn() FAILED: mDolbyMobileSystem == null
E/DolbyMobileAudioEffectClient(14802): getGlobalAudioHeadsetByPass() FAILED: mDolbyMobileSystem == null
E/DolbyMobileAudioEffectClient(14802): setDolbyEffectByPass() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient(14802): getGlobalAudioPreset() FAILED: mDolbyMobileSystem == null
E/DolbyMobileAudioEffectClient(14802): setDolbyEffect() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient(14802): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null
Click to expand...
Click to collapse
Is the dolbymobileaudioeffectservice running ? Do you see the notification ?
Sent from my Nexus 4 using xda app-developers app
worstenbrood said:
Is the dolbymobileaudioeffectservice running ? Do you see the notification ?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Nope... I cant enable it
bamsbamx said:
Nope... I cant enable it
Click to expand...
Click to collapse
Would you mind posting the complete logcat so i can find out why the service isn't running ?
Sent from my Nexus 4 using xda app-developers app
worstenbrood said:
Would you mind posting the complete logcat so i can find out why the service isn't running ?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
The logs I posted above are all the logs related to Dolby, no service logs found
bamsbamx said:
It seems not working for me on Purity rom.... When I click the checkbox it doesnt happen anything. Cant check the box
Tried before and after flashing DSP Manager
EDIT: Reading the logcat it says: mDolbyMobileSystem = null
Click to expand...
Click to collapse
bamsbamx said:
The logs I posted above are all the logs related to Dolby, no service logs found
Click to expand...
Click to collapse
There must be a reason why the service isn't running, search for it in the logcat
worstenbrood said:
There must be a reason why the service isn't running, search for it in the logcat
Click to expand...
Click to collapse
Okay, I think I found something, activityManager says that it was unable to start service intent with U=0
Code:
I/ActivityManager( 691): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.huawei.android.globaldolbyeffect/.GlobalDolbyEffectActivity} from pid 1227
I/ActivityManager( 691): Start proc com.huawei.android.globaldolbyeffect for activity com.huawei.android.globaldolbyeffect/.GlobalDolbyEffectActivity: pid=2914 uid=10023 gids={50023}
I/DolbyMobileAudioEffectClient( 2914): activity bindToRemoteRunningService()
W/ContextImpl( 2914): Implicit intents with startService are not safe: Intent { act=android.media.dolby.IDolbyMobileSystemInterface } android.content.ContextWrapper.bindService:517 android.media.dolby.DolbyMobileAudioEffectClient.bindToRemoteRunningService:121 com.huawei.android.globaldolbyeffect.GlobalDolbyEffectFragment.initDolbyMobileAudioEffectClient:236
W/ActivityManager( 691): Unable to start service Intent { act=android.media.dolby.IDolbyMobileSystemInterface } U=0: not found
E/DolbyMobileAudioEffectClient( 2914): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null
I/ActivityManager( 691): Displayed com.huawei.android.globaldolbyeffect/.GlobalDolbyEffectActivity: +460ms
E/DolbyMobileAudioEffectClient( 2914): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient( 2914): setDolbyEffectOn() FAILED: mDolbyMobileSystem = null.
E/DolbyMobileAudioEffectClient( 2914): setGlobalEffectOn() FAILED: mDolbyMobileSystem == null
E/DolbyMobileAudioEffectClient( 2914): getGlobalAudioSpeakerByPass() FAILED: mDolbyMobileSystem == null
E/DolbyMobileAudioEffectClient( 2914): setDolbyEffectByPass() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient( 2914): setDolbyEffect() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient( 2914): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null
bamsbamx said:
Okay, I think I found something, activityManager says that it was unable to start service intent with U=0
Code:
I/ActivityManager( 691): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.huawei.android.globaldolbyeffect/.GlobalDolbyEffectActivity} from pid 1227
I/ActivityManager( 691): Start proc com.huawei.android.globaldolbyeffect for activity com.huawei.android.globaldolbyeffect/.GlobalDolbyEffectActivity: pid=2914 uid=10023 gids={50023}
I/DolbyMobileAudioEffectClient( 2914): activity bindToRemoteRunningService()
W/ContextImpl( 2914): Implicit intents with startService are not safe: Intent { act=android.media.dolby.IDolbyMobileSystemInterface } android.content.ContextWrapper.bindService:517 android.media.dolby.DolbyMobileAudioEffectClient.bindToRemoteRunningService:121 com.huawei.android.globaldolbyeffect.GlobalDolbyEffectFragment.initDolbyMobileAudioEffectClient:236
W/ActivityManager( 691): Unable to start service Intent { act=android.media.dolby.IDolbyMobileSystemInterface } U=0: not found
E/DolbyMobileAudioEffectClient( 2914): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null
I/ActivityManager( 691): Displayed com.huawei.android.globaldolbyeffect/.GlobalDolbyEffectActivity: +460ms
E/DolbyMobileAudioEffectClient( 2914): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient( 2914): setDolbyEffectOn() FAILED: mDolbyMobileSystem = null.
E/DolbyMobileAudioEffectClient( 2914): setGlobalEffectOn() FAILED: mDolbyMobileSystem == null
E/DolbyMobileAudioEffectClient( 2914): getGlobalAudioSpeakerByPass() FAILED: mDolbyMobileSystem == null
E/DolbyMobileAudioEffectClient( 2914): setDolbyEffectByPass() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient( 2914): setDolbyEffect() FAILED: mDolbyMobileSystem = null
E/DolbyMobileAudioEffectClient( 2914): getDolbyEffectOn() FAILED: mDolbyMobileSystem = null
Click to expand...
Click to collapse
You sure you flashed v2 before v2.1 or 2.2 ?
Sent from my Nexus 4 using xda app-developers app
worstenbrood said:
You sure you flashed v2 before v2.1 or 2.2 ?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Oooooppsss nope, i didnt.... I got excited and didnt read the post... Hahahaha
Flashed v2 then v2.1.went to dsp manager, disabled all and now its working
Sorry for making you waste your time in so silly way
bamsbamx said:
Oooooppsss nope, i didnt.... I got excited and didnt read the post... Hahahaha
Flashed v2 then v2.1.went to dsp manager, disabled all and now its working
Sorry for making you waste your time in so silly way
Click to expand...
Click to collapse
Hahaha, no problem. I'll create a full 2.2 zip tomorrow for the overexcited ones
Sent from my Nexus 4 using xda app-developers app
I don't see any changes when disable/enable service
Sent from my Nexus⁴
[Q&A] [SM-T325] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 8.4 LTE (mondrianlte)
Q&A for [SM-T325] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 8.4 LTE (mondrianlte)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
alarm clock
Recently discussed the problem that the included headphones alarm clock rang only from external speakers. Now it rings only from the headphones. But it would be optimal to it when headphones are connected rang simultaneously and external speakers and headphone out. So it is correct and it is so sold on the official firmware.
Sorry for my bad English.
Del
---------- Post added at 03:30 AM ---------- Previous post was at 03:24 AM ----------
Hi, will snapshot m12 for LTE?
Do you just dirty flash the nightlife? I tried going the update route but it doesn't work.
Hi all!
First of all thank you for the Roma and the whole tutorial is perfect on my side on my "tab pro lte"
I would like to know how to overclock the processor above its Standard power?
sorry for the mistakes, I'm French and I use google translation ... oO
thank you!
No mobile data
Thanks to the dev for his continuous efforts on this rom, keep up the good work. However, i noticed that mobile data doesn't work for 2g networks. I've tried using the "preferred network type" and even changing the sim but it still won't work. When i get into 3g or LTE zonse the mobile data begins to work. Please could you suggest a fix. I'm currently limited to 2g so it would be a big help. Thanks
Any hints on building CM12 for this device ? I'm willing to do it if there is any documentation help.
Firmware crude
CM-12 test
Deleted
DensonX said:
Sorry if this is off-topic, but I have seen a lot of people requesting CyanogenMod 12 for this device. I managed to build CM-12 for the mondrianlte, however it does not flash on my device. I get an error saying E: error executing binary in zip. I suspect this may be due to the fact that I have a european Tab Pro, so if anyone with a US Tab Pro LTE wants to try to install it here's a file. https://drive.google.com/file/d/0Bxf2YUR9_3hDX3JUbnJYbWVfTTA/view?usp=sharing
Do NOT forget to backup before attempting to install this, as it likely will not work.
Also if anyone knows how to solve my problem with flashing this please let me know.
Click to expand...
Click to collapse
Please do not post links to other builds in my thread. Especially ones that you can't even flash because it doesn't work for you!
This only adds confusion.
I will try to release something soon. It may have a broken camera (the camera is broken on picassolte and if I can't figure it out I'll have to just leave it broken for both mondrianlte and picassolte for now) but otherwise has been working well for me on picassolte.
SM-T325, CM12 and encryption
Hello,
First Thank you crpalmer for your great work on mondrianlte. I've been using for roughly one month and did not encounter any serious issue, it is working so much better than stock Samsung ROMs ! I only got into problems when trying to encrypt the tablet (with cm-12-20150321-UNOFFICIAL-mondrianlte).
Once the process was started it rebooted very quickly and got stuck on the boot cyanogenmod screen. A forced off/on cycle was able to restore the tablet normal operation, but it had not been encrypted.
Relevant portions of the adb log seem to be :
(just after the beginning of the encrytion process)
Code:
E/Cryptfs ( 243): Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
D/Cryptfs ( 243): Just asked init to shut down class main
and later when the tablet reboots :
Code:
D/Cryptfs ( 243): unmounting /data succeeded
D/QSEECOMAPI: ( 243): QSEECom_get_handle sb_length = 0x2000
D/QSEECOMAPI: ( 243): App is not loaded in QSEE
E/QSEECOMAPI: ( 243): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt
E/QSEECOMAPI: ( 243): Error::Loading image failed with ret = -1
D/QSEECOMAPI: ( 243): QSEECom_get_handle sb_length = 0x2000
D/QSEECOMAPI: ( 243): App is not loaded in QSEE
E/QSEECOMAPI: ( 243): Error::Cannot open the file /firmware/image/keymaste.mdt
E/QSEECOMAPI: ( 243): Error::Loading image failed with ret = -1
E/QCOMKeyMaster( 243): Loading keymaster app failed
E/Cryptfs ( 243): could not open keymaster device in keystore (Operation not permitted)
E/Cryptfs ( 243): Failed to init keymaster
--------- beginning of crash
F/libc ( 243): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x3c in tid 315 (vold)
F/libc ( 243): Unable to open connection to debuggerd: Connection refused
I/Vold (26973): Vold 2.1 (the revenge) firing up
D/Vold (26973): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold (26973): Volume usbdisk state changing -1 (Initializing) -> 0 (No-Media)
I/Cryptfs (26973): Check if PFE is activated on Boot
E/Cryptfs (26973): Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
E/Cryptfs (26973): Error getting crypt footer and key
files /vendor/firmware/keymaster/keymaster.* have permission 644, user/group root, and are symlinks into /firmware/image/. In /firmware/image/, keymaste.* files have permission 440, user system, group drmrpc. Based on the QSEECOMAPI errors above, I am unable to determine whether these access rights are correct. I assume that even if they were, some incorrect SElinux configuration could cause access problems ?
Is anyone able to figure out what is happening ? Is it useful that I post a full log of the process ?
Hello, when these issues will be resolved:
- Bluetooth call disconected
- HotSpot only work with reboot
- QuickRemote
- Probably telephony framework missing some stuff..
Thanks..
faifer13 said:
Hello, when these issues will be resolved:
- Bluetooth call disconected
- HotSpot only work with reboot
- QuickRemote
- Probably telephony framework missing some stuff..
Thanks..
Click to expand...
Click to collapse
Do some reading. It has all been discussed. Use ao-shi to revive Bluetooth instead of restarting phone. All ROMs except stock hack ROMs have Bluetooth issues. All ROMs have hotspot issue as well. And quick remote doesn't work because of some LP driver missing I think. So that won't work any time soon.
zombigrn said:
Do some reading. It has all been discussed. Use ao-shi to revive Bluetooth instead of restarting phone. All ROMs except stock hack ROMs have Bluetooth issues. All ROMs have hotspot issue as well. And quick remote doesn't work because of some LP driver missing I think. So that won't work any time soon.
Click to expand...
Click to collapse
Thanks .. my question is when is solved .. or if no more work on them
faifer13 said:
Thanks .. my question is when is solved .. or if no more work on them
Click to expand...
Click to collapse
QRemote will probably never be resolved, because e980 never got an official Lollipop build, so we're missing half of lollipop libs (not sure how much F240 ones will help), and I'm slowly moving towards the Marshmallow builds. Also, telephony framework isn't missing a thing, hotspot is working, for some people, after a reboot, for some people at once; and bluetooth is mostly working - not every device and not every handsfree/handset combo will work fine. It's fine when I test it on cheap bluetooth handsfree set I have, it works fine with my PC and other phone (file transfer etc.) but I can't test it on every device out there. Unfortunately, crash logs show nothing so I can't hunt it down.
And please, don't ask for ETAs.
ShadySquirrel said:
QRemote will probably never be resolved, because e980 never got an official Lollipop build, so we're missing half of lollipop libs (not sure how much F240 ones will help), and I'm slowly moving towards the Marshmallow builds. Also, telephony framework isn't missing a thing, hotspot is working, for some people, after a reboot, for some people at once; and bluetooth is mostly working - not every device and not every handsfree/handset combo will work fine. It's fine when I test it on cheap bluetooth handsfree set I have, it works fine with my PC and other phone (file transfer etc.) but I can't test it on every device out there. Unfortunately, crash logs show nothing so I can't hunt it down.
And please, don't ask for ETAs.
Click to expand...
Click to collapse
Ok, one question more.. my sd-ext partition is unavaliable, how activate?
faifer13 said:
Ok, one question more.. my sd-ext partition is unavaliable, how activate?
Click to expand...
Click to collapse
Isn't sd-ext an OTG drive? sdcard0 is internal, sdcard1 is external, sd-ext is otg as far as I remember.
ShadySquirrel said:
Isn't sd-ext an OTG drive? sdcard0 is internal, sdcard1 is external, sd-ext is otg as far as I remember.
Click to expand...
Click to collapse
I can not move apps to sd..
Depending which apps, not every app supports that. I'll need some logs if all appa are messy, simply because it worked fine for me.
ShadySquirrel said:
Depending which apps, not every app supports that. I'll need some logs if all appa are messy, simply because it worked fine for me.
Click to expand...
Click to collapse
I can not move all apps.. the error is "Couldn't move app. Not enough storage space"
faifer13 said:
I can not move all apps.. the error is "Couldn't move app. Not enough storage space"
Click to expand...
Click to collapse
When I say log, I mean logcat, not a error message android is displaying...
ShadySquirrel said:
When I say log, I mean logcat, not a error message android is displaying...
Click to expand...
Click to collapse
ok.. i tried move aliexpress app.. this is the text in logcat:
12-30 15:09:47.516 E/PackageHelper( 1667): Failed to create secure container smdl1560851173.tmp
12-30 15:09:47.516 E/Vold ( 245): Error creating imagefile (Read-only file system)
12-30 15:09:47.516 E/Vold ( 245): ASEC image file creation failed (Read-only file system)
12-30 15:09:47.516 W/Vold ( 245): Returning OperationFailed - no handler for errno 30
12-30 15:09:47.516 W/DefContainer( 1667): Failed to copy package at /data/app/com.alibaba.aliexpresshd-1
12-30 15:09:47.516 W/DefContainer( 1667): java.io.IOException: Failed to create container smdl1560851173.tmp
12-30 15:09:47.516 W/DefContainer( 1667): at com.android.defcontainer.DefaultContainerService.copyPackageToContainerInner(DefaultContainerService.java:326)
12-30 15:09:47.516 W/DefContainer( 1667): at com.android.defcontainer.DefaultContainerService.access$000(DefaultContainerService.java:67)
12-30 15:09:47.516 W/DefContainer( 1667): at com.android.defcontainer.DefaultContainerService$1.copyPackageToContainer(DefaultContainerService.java:108)
12-30 15:09:47.516 W/DefContainer( 1667): at com.android.internal.app.IMediaContainerService$Stub.onTransact(IMediaContainerService.java:60)
12-30 15:09:47.516 W/DefContainer( 1667): at android.os.Binder.execTransact(Binder.java:446)
12-30 15:09:47.666 I/art ( 640): Explicit concurrent mark sweep GC freed 73830(3MB) AllocSpace objects, 8(4MB) LOS objects, 29% free, 38MB/54MB, paused 1.587ms total 119.426ms
12-30 15:09:47.676 D/PackageManager( 640): Install result for move: INSTALL_FAILED_CONTAINER_ERROR
12-30 15:09:47.756 V/WindowManager( 640): not Base app: Adding window Window{3fad750f u0 com.android.settings/com.android.settings.SubSettings} at 8 of 14
12-30 15:09:48.958 W/qcom_sensors_hal( 640): hal_sensor1_data_cb: msg_type 1 for svc id 24 txn id 1
12-30 15:09:49.248 D/audio_hw_primary( 254): out_set_parameters: enter: usecase(1: low-latency-playback) kvpairs: routing=2
12-30 15:09:49.248 I/ActivityManager( 640): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.teslacoilsw.launcher/.NovaLauncher} from uid 1000 on display 0
12-30 15:09:49.438 I/Timeline( 1115): Timeline: Activity_idle id: [email protected] time:75894828
12-30 15:09:49.658 I/Timeline( 640): Timeline: Activity_windows_visible id: ActivityRecord{2b711392 u0 com.teslacoilsw.launcher/.NovaLauncher t2529} time:75895043
12-30 15:09:49.949 W/OpenGLRenderer( 1115): Incorrectly called buildLayer on View: agt, destroying layer...
12-30 15:09:49.949 W/OpenGLRenderer( 1115): Incorrectly called buildLayer on View: agt, destroying layer...
12-30 15:09:50.419 W/ResourceType( 863): No package identifier when getting value for resource number 0x00000000
12-30 15:09:50.429 W/PackageManager( 863): Failure retrieving resources for com.android.settings: Resource ID #0x0
12-30 15:09:50.539 D/audio_hw_primary( 254): out_set_parameters: enter: usecase(1: low-latency-playback) kvpairs: routing=2
12-30 15:09:50.549 E/WindowManager( 640): Unknown window type: 2033
12-30 15:09:51.941 D/audio_hw_primary( 254): out_set_parameters: enter: usecase(1: low-latency-playback) kvpairs: routing=2
12-30 15:09:52.091 I/Timeline( 8487): Timeline: Activity_idle id: [email protected] time:75897486
12-30 15:09:52.191 W/qcom_sensors_hal( 640): hal_sensor1_data_cb: msg_type 1 for svc id 24 txn id 1
12-30 15:09:52.351 I/Timeline( 640): Timeline: Activity_windows_visible id: ActivityRecord{14edd835 u0 com.tortel.syslog/.MainActivity t2646} time:75897745
12-30 15:09:53.212 D/audio_hw_primary( 254): out_set_parameters: enter: usecase(1: low-latency-playback) kvpairs: routing=2
12-30 15:09:53.222 V/WindowManager( 640): not Base app: Adding window Window{3d652b2a u0 com.tortel.syslog/com.tortel.syslog.MainActivity} at 9 of 15