Develop Bugs

Multi ROM crash I can't seem to figure out.

I had originally posted this under the CM9 nightly, but that's not inclusive as much as it should be..
I keep getting what I guess would be UI crashes. It happens sometimes with the screen off, I'll get a vibration and when I unlock the screen it's wanting to email a bug report. I started having this a while ago while running MCR, and I thought it might be related to that ROM. Having not looked at CM9 since early January, I read that it was quite stable now so I switched to it yesterday and I'm still getting these. Probably about 6-8 a day. I'm running 0327.
Is there something I could determine from these, or is this something I should submit, somewhere? I've tried as many things as I can think of that I've done in the past, including but not limited to: full wipes. restoring titanium backups (apps and data, and just the apps), downloading all the apps on initial install, fixing permissions, trying other ROMs..
Not sure where to go with this.. Thanks for any help you can offer.

LOL. Wear your bullet proof vests. You're about to get fired upon

Post a logcat
Sent from my A500 using XDA

bombs away.
subhramani said:
LOL. Wear your bullet proof vests. You're about to get fired upon
Click to expand...
Click to collapse
yeah I know that could be expected.. thanks for the heads up.
bomb the boats, feed the fish

robkoehler said:
Post a logcat
Sent from my A500 using XDA
Click to expand...
Click to collapse
I shall do that - thanks

Mount /System as R/W in Root explorer and find file in /system/bin called bugmailer.sh. Rename to bugmailer.sh-orig or something similar (or delete if brave) , save and then reboot. Should stop it.
Its actually a feature of Android that is both useful (sending bug reports) and annoying (can be done by holding both volume and power together accidently). Chose to use if you wish

Wrong section.
This belongs to Q&A

dario3040 said:
Wrong section.
This belongs to Q&A
Click to expand...
Click to collapse
ok thanks... I always spend my time just grabbing ROMs and info from here

Thread moved to Q&A.
Mark.

killyouridols said:
Mount /System as R/W in Root explorer and find file in /system/bin called bugmailer.sh. Rename to bugmailer.sh-orig or something similar (or delete if brave) , save and then reboot. Should stop it.
Its actually a feature of Android that is both useful (sending bug reports) and annoying (can be done by holding both volume and power together accidently). Chose to use if you wish
Click to expand...
Click to collapse
This is correct.
Just in case you missed it.

Jubakuba said:
This is correct.
Just in case you missed it.
Click to expand...
Click to collapse
Thanks. Yeah I'm going to try and catch one of these crashes in the logs.. of course now its not doing it. Ain't that how it goes? Like a watched kettle never boils.

here's logcat from a crash
This crash happened, I opened the phone to find it had generated one of those crash emails, I then got a call which I ignored, so it was before the call, here's the logcat - should I post this somewhere else instead of here?
--------- beginning of /dev/log/system
I/ActivityManager( 213): No longer want com.google.android.apps.maps:NetworkLocationService (pid 10277): hidden #16
W/ActivityManager( 213): Scheduling restart of crashed service com.google.android.apps.maps/com.google.android.location.internal.server.NetworkLocationService in 5000ms
I/ActivityManager( 213): Start proc com.google.android.apps.maps:NetworkLocationService for service com.google.android.apps.maps/com.google.android.location.internal.server.NetworkLocationService: pid=11597 uid=10088 gids={3003, 1015}
--------- beginning of /dev/log/main
D/dalvikvm(11597): GC_CONCURRENT freed 168K, 3% free 12929K/13255K, paused 3ms+3ms
I/ActivityManager( 213): Start proc com.google.android.apps.maps:FriendService for broadcast com.google.android.apps.maps/com.google.googlenav.friend.android.ServiceReceiver: pid=11611 uid=10088 gids={3003, 1015}
D/dalvikvm(11597): GC_CONCURRENT freed 150K, 3% free 13254K/13575K, paused 4ms+4ms
D/dalvikvm(11611): GC_CONCURRENT freed 171K, 3% free 12927K/13255K, paused 3ms+2ms
D/dalvikvm(11611): GC_CONCURRENT freed 161K, 3% free 13224K/13575K, paused 2ms+2ms
D/dalvikvm(11597): GC_CONCURRENT freed 169K, 3% free 13632K/13959K, paused 3ms+4ms
I/ActivityManager( 213): Start proc com.google.android.apps.maps:LocationFriendService for broadcast com.google.android.apps.maps/com.google.googlenav.friend.reporting.LocationReportingIntentReceiver: pid=11631 uid=10088 gids={3003, 1015}
I/ActivityManager( 213): No longer want com.twitter.android (pid 10476): hidden #16
D/dalvikvm(11631): GC_CONCURRENT freed 173K, 3% free 12924K/13255K, paused 3ms+3ms
D/dalvikvm( 213): GC_CONCURRENT freed 844K, 20% free 22808K/28423K, paused 4ms+8ms
D/dalvikvm(11597): GC_CONCURRENT freed 160K, 3% free 14001K/14343K, paused 2ms+8ms
D/dalvikvm(11631): GC_CONCURRENT freed 178K, 3% free 13240K/13639K, paused 2ms+3ms
I/System.out(11631): VectorGlobalState: Server:https://mobilemaps.clients.google.com/glm/mmap Type:3
I/dalvikvm(11597): Total arena pages for JIT: 11
I/dalvikvm(11597): Total arena pages for JIT: 12
I/dalvikvm(11597): Total arena pages for JIT: 13
I/dalvikvm(11597): Total arena pages for JIT: 14
I/dalvikvm(11597): Total arena pages for JIT: 15
I/dalvikvm(11597): Total arena pages for JIT: 16
I/dalvikvm(11597): Total arena pages for JIT: 17
I/ActivityManager( 213): No longer want com.gau.go.launcherex.gowidget.twitterwidget (pid 10878): hidden #16
D/dalvikvm(11631): GC_CONCURRENT freed 236K, 4% free 13456K/13895K, paused 3ms+3ms
I/dalvikvm(11597): Total arena pages for JIT: 18
D/dalvikvm(11597): GC_CONCURRENT freed 848K, 7% free 13652K/14663K, paused 5ms+4ms
D/dalvikvm(11597): GC_CONCURRENT freed 286K, 7% free 13759K/14663K, paused 6ms+6ms
D/dalvikvm(11597): GC_CONCURRENT freed 491K, 7% free 13780K/14663K, paused 4ms+3ms
D/dalvikvm( 8282): GC_FOR_ALLOC freed 612K, 8% free 13335K/14343K, paused 24ms
D/dalvikvm( 8282): GC_CONCURRENT freed 344K, 6% free 13494K/14343K, paused 2ms+6ms
D/dalvikvm( 8282): GC_CONCURRENT freed 367K, 6% free 13581K/14343K, paused 5ms+5ms
V/SmsReceiverService( 9663): onStart: #1 mResultCode: -1 = Activity.RESULT_OK
D/dalvikvm( 9663): GC_CONCURRENT freed 473K, 5% free 13140K/13831K, paused 2ms+4ms
V/AudioManager( 292): shouldVibrate, group: a126d48a-aaef-47c4-baed-7f0e44aeffe5 mode: DEFAULT
V/AudioManager( 213): Not applying override for 'android' package
V/SmsReceiverService( 9663): onStart: #1 mResultCode: -1 = Activity.RESULT_OK
D/dalvikvm( 425): GC_EXPLICIT freed 535K, 11% free 17247K/19335K, paused 2ms+14ms
D/dalvikvm( 9663): GC_EXPLICIT freed 110K, 6% free 13070K/13831K, paused 5ms+4ms
D/dalvikvm( 213): GC_EXPLICIT freed 1104K, 20% free 22863K/28423K, paused 4ms+9ms
V/AudioManager( 213): Not applying override for 'android' package
V/AudioManager( 292): shouldVibrate, group: a126d48a-aaef-47c4-baed-7f0e44aeffe5 mode: DEFAULT
I/Gmail ( 9784): MainSyncRequestProto: lowestBkwdConvoId: 0, highestHandledServerOp: 2349710, normalSync: true
D/dalvikvm( 9784): GC_EXPLICIT freed 372K, 5% free 13323K/14023K, paused 5ms+4ms
I/Gmail ( 9784): MainSyncRequestProto: lowestBkwdConvoId: 0, highestHandledServerOp: 2349733, normalSync: true
D/dalvikvm( 9784): GC_EXPLICIT freed 340K, 5% free 13338K/14023K, paused 5ms+4ms
I/Gmail ( 9784): MainSyncRequestProto: lowestBkwdConvoId: 0, highestHandledServerOp: 2349733, normalSync: true
W/Gmail ( 9784): Scheduling index for 300000 ms from now
I/Gmail ( 9784): Sending notification intent: Intent { act=android.intent.action.PROVIDER_CHANGED dat=content://gmail-ls/unread/^i (has extras) }
W/Gmail ( 9784): Showing notification with unreadCount of 4 and unseenCount of 4
V/AudioManager( 213): Not applying override for 'android' package
V/SmsReceiverService( 9663): onStart: #1 mResultCode: -1 = Activity.RESULT_OK
V/AudioManager( 213): Not applying override for 'android' package
V/AudioManager( 292): shouldVibrate, group: a126d48a-aaef-47c4-baed-7f0e44aeffe5 mode: DEFAULT
D/dalvikvm( 292): GC_CONCURRENT freed 402K, 9% free 14751K/16071K, paused 5ms+5ms
I/power ( 213): *** set_screen_state 1
I/WindowManager( 213): Lock screen displayed!
D/SurfaceFlinger( 134): Screen about to return, flinger = 0xc77918
I/keystore( 140): uid: 1000 action: p -> 1 state: 1 -> 1 retry: 4
D/OpenGLRenderer( 213): Flushing caches (mode 0)
D/PhoneStatusBar( 292): disable: < expand* icons alerts ticker* system_info BACK HOME recent* CLOCK >
D/NfcService( 439): NFC-C ON
D/Beautiful Widgets( 8282): UserPresent from ClockWidget41
D/Beautiful Widgets( 8282): Screensaver mode: false
D/PhoneStatusBar( 292): disable: < expand icons alerts ticker system_info back* home* recent clock* >
D/CallNotifier( 425): RINGING... (new)
D/CallNotifier( 425): onNewRingingConnection(): state = RINGING, conn = { incoming: true state: INCOMING post dial state: NOT_STARTED }
D/CallNotifier( 425): SignalInfoTonePlayer.run(toneId = 98)...
D/AccelerometerListener( 425): enable(false)
D/PhoneStatusBar( 292): disable: < expand icons ALERTS* ticker system_info back home recent clock >
V/AudioManager( 425): shouldVibrate, group: d393035d-ea71-4f2a-bdbd-b65f6bf298f1 mode: DEFAULT
D/CallNotifier( 425): showIncomingCall()... phone state = RINGING
D/PhoneStatusBar( 292): Notification has fullScreenIntent; sending fullScreenIntent
I/ActivityManager( 213): START {act=android.intent.action.MAIN flg=0x10840000 cmp=com.android.phone/.InCallScreen} from pid -1
D/InCallScreen( 425): onNewIntent: intent = Intent { act=android.intent.action.MAIN flg=0x10c40000 cmp=com.android.phone/.InCallScreen }, phone state = RINGING
D/PhoneStatusBar( 292): disable: < EXPAND* icons ALERTS ticker system_info BACK* HOME* RECENT* clock >
I/power ( 213): *** set_screen_state 1
W/InputManagerService( 213): Starting input on non-focused client [email protected] (uid=10072 pid=8458)
W/IInputConnectionWrapper( 8458): showStatusIcon on inactive InputConnection
I/ActivityManager( 213): No longer want com.google.android.apps.maps (pid 10949): hidden #16
D/dalvikvm( 8282): GC_CONCURRENT freed 673K, 7% free 13348K/14343K, paused 2ms+2ms
D/dalvikvm( 8282): GC_CONCURRENT freed 375K, 7% free 13476K/14343K, paused 8ms+2ms
D/dalvikvm( 8282): GC_CONCURRENT freed 401K, 6% free 13549K/14343K, paused 5ms+2ms
D/dalvikvm( 8282): GC_FOR_ALLOC freed 99K, 5% free 13649K/14343K, paused 33ms

Anything look like an issue there? Should I post this somewhere else, or the dozens of bug reports that have been generating for weeks

gribbler said:
Anything look like an issue there? Should I post this somewhere else, or the dozens of bug reports that have been generating for weeks
Click to expand...
Click to collapse
If your not actually seeing errors within apps or the UI and nothing seems amiss, just rename bugmailer.sh as I said above and enjoy the phone. I used to get 4 or 5 a day but never had any visible issues.
Sent from my Galaxy Nexus using XDA

[DEV-WIP] MIC testing (To enable GoogleNow function in JB)

NOTE: This requires some knowledge of the ALSA subsystem. If you're not comfortable doing this, PLEASE DONT. You can in theory damage the audio hardware with bad settings.
With the migration to Jelly Bean, we can see how powerful having a working MIC would be.
On my latest AOSP Jelly Bean ROM (7/13), I have 3 new binaries so that anyone who is comfortable with the audio system can jump in and help:
tinymix
tinycap
tinyplay
Also, you can install "AlsaMixer" from the Market which gives you a bit of control over the audio system's low level devices.
I feel like if we can get a few devs / knowledgeable users looking at these settings, that we could identify where in our audio driver the mixer for the MIC is getting off track.
THE GOAL:
Get a small list of mixer changes (tinymix / AlsaMixer) which enable the MIC for use in the OS.
Then I can replicate those in the audio driver.
GAME ON.

Hashcode said:
NOTE: This requires some knowledge of the ALSA subsystem. If you're not comfortable doing this, PLEASE DONT. You can in theory damage the audio hardware with bad settings.
With the migration to Jelly Bean, we can see how powerful having a working MIC would be.
On my latest AOSP Jelly Bear ROM (7/13), I have 3 new binaries so that anyone who is comfortable with the audio system can jump in and help:
tinymix
tinycap
tinyplay
Also, you can install "AlsaMixer" from the Market which gives you a bit of control over the audio system's low level devices.
I feel like if we can get a few devs / knowledgeable users looking at these settings, that we could identify where in our audio driver the mixer for the MIC is getting off track.
THE GOAL:
Get a small list of mixer changes (tinymix / AlsaMixer) which enable the MIC for use in the OS.
Then I can replicate those in the audio driver.
GAME ON.
Click to expand...
Click to collapse
Perfect person to probably ask for help would be supercurio, although his specialty is wolfson codecs

times_infinity said:
Perfect person to probably ask for help would be supercurio, although his specialty is wolfson codecs
Click to expand...
Click to collapse
Yeah you're right .
Envoyé depuis mon GT-I9000 avec Tapatalk

Hashcode said:
NOTE: This requires some knowledge of the ALSA subsystem. If you're not comfortable doing this, PLEASE DONT. You can in theory damage the audio hardware with bad settings.
With the migration to Jelly Bean, we can see how powerful having a working MIC would be.
On my latest AOSP Jelly Bear ROM (7/13), I have 3 new binaries so that anyone who is comfortable with the audio system can jump in and help:
tinymix
tinycap
tinyplay
Also, you can install "AlsaMixer" from the Market which gives you a bit of control over the audio system's low level devices.
I feel like if we can get a few devs / knowledgeable users looking at these settings, that we could identify where in our audio driver the mixer for the MIC is getting off track.
THE GOAL:
Get a small list of mixer changes (tinymix / AlsaMixer) which enable the MIC for use in the OS.
Then I can replicate those in the audio driver.
GAME ON.
Click to expand...
Click to collapse
This would be great! Btw, is your rom's codename Jelly Bear?
Mike T

webdroidmt said:
This would be great! Btw, is your rom's codename Jelly Bear?
Mike T
Click to expand...
Click to collapse
Nice catch!

I don't think the Google Now crash is related to the microphone....
Here's the logcat I'm getting:
Code:
W/dalvikvm( 3429): threadid=1: thread exiting with uncaught exception (group=0x41199300)
E/AndroidRuntime( 3429): FATAL EXCEPTION: main
E/AndroidRuntime( 3429): java.lang.IllegalArgumentException: requested provider network doesn't exisit
E/AndroidRuntime( 3429): at android.os.Parcel.readException(Parcel.java:1429)
E/AndroidRuntime( 3429): at android.os.Parcel.readException(Parcel.java:1379)
E/AndroidRuntime( 3429): at android.location.ILocationManager$Stub$Proxy.requestLocationUpdates(ILocationManager.java:646)
E/AndroidRuntime( 3429): at android.location.LocationManager._requestLocationUpdates(LocationManager.java:660)
E/AndroidRuntime( 3429): at android.location.LocationManager.requestLocationUpdates(LocationManager.java:482)
E/AndroidRuntime( 3429): at com.google.android.apps.sidekick.inject.SystemLocationManagerInjectable.requestLocationUpdates(SystemLocationManagerInjectable.java:33)
E/AndroidRuntime( 3429): at com.google.android.apps.sidekick.LocationOracleImpl.registerForAndroidNlpFix(LocationOracleImpl.java:495)
E/AndroidRuntime( 3429): at com.google.android.apps.sidekick.LocationOracleImpl.start(LocationOracleImpl.java:139)
E/AndroidRuntime( 3429): at com.google.android.velvet.VelvetApplication.startTgServices(VelvetApplication.java:175)
E/AndroidRuntime( 3429): at com.google.android.velvet.tg.FirstRunActivity.completeOptIn(FirstRunActivity.java:350)
E/AndroidRuntime( 3429): at com.google.android.velvet.tg.FirstRunActivity$OptInHander.handleMessage(FirstRunActivity.java:421)
E/AndroidRuntime( 3429): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 3429): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 3429): at android.app.ActivityThread.main(ActivityThread.java:4745)
E/AndroidRuntime( 3429): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3429): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 3429): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
E/AndroidRuntime( 3429): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
E/AndroidRuntime( 3429): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 257): Force finishing activity com.google.android.googlequicksearchbox/com.google.android.velvet.tg.FirstRunActivity
That doesn't look microphone-related. I think our smoking gun is Wi-Fi location. Unfortunately, disabling location services didn't help :/ Hash, when you get the 2nd part of Wi-Fi location working, try Now and see what it does.

You guys could try (sp?)Meltus as well...the Volume+ guy.
Sent from my Galaxy Nexus using xda app-developers app

roothorick said:
I don't think the Google Now crash is related to the microphone....
Here's the logcat I'm getting:
Code:
W/dalvikvm( 3429): threadid=1: thread exiting with uncaught exception (group=0x41199300)
E/AndroidRuntime( 3429): FATAL EXCEPTION: main
E/AndroidRuntime( 3429): java.lang.IllegalArgumentException: requested provider network doesn't exisit
E/AndroidRuntime( 3429): at android.os.Parcel.readException(Parcel.java:1429)
E/AndroidRuntime( 3429): at android.os.Parcel.readException(Parcel.java:1379)
E/AndroidRuntime( 3429): at android.location.ILocationManager$Stub$Proxy.requestLocationUpdates(ILocationManager.java:646)
E/AndroidRuntime( 3429): at android.location.LocationManager._requestLocationUpdates(LocationManager.java:660)
E/AndroidRuntime( 3429): at android.location.LocationManager.requestLocationUpdates(LocationManager.java:482)
E/AndroidRuntime( 3429): at com.google.android.apps.sidekick.inject.SystemLocationManagerInjectable.requestLocationUpdates(SystemLocationManagerInjectable.java:33)
E/AndroidRuntime( 3429): at com.google.android.apps.sidekick.LocationOracleImpl.registerForAndroidNlpFix(LocationOracleImpl.java:495)
E/AndroidRuntime( 3429): at com.google.android.apps.sidekick.LocationOracleImpl.start(LocationOracleImpl.java:139)
E/AndroidRuntime( 3429): at com.google.android.velvet.VelvetApplication.startTgServices(VelvetApplication.java:175)
E/AndroidRuntime( 3429): at com.google.android.velvet.tg.FirstRunActivity.completeOptIn(FirstRunActivity.java:350)
E/AndroidRuntime( 3429): at com.google.android.velvet.tg.FirstRunActivity$OptInHander.handleMessage(FirstRunActivity.java:421)
E/AndroidRuntime( 3429): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 3429): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 3429): at android.app.ActivityThread.main(ActivityThread.java:4745)
E/AndroidRuntime( 3429): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3429): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 3429): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
E/AndroidRuntime( 3429): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
E/AndroidRuntime( 3429): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 257): Force finishing activity com.google.android.googlequicksearchbox/com.google.android.velvet.tg.FirstRunActivity
That doesn't look microphone-related. I think our smoking gun is Wi-Fi location. Unfortunately, disabling location services didn't help :/ Hash, when you get the 2nd part of Wi-Fi location working, try Now and see what it does.
Click to expand...
Click to collapse
Even if the mic isn't the issue I would still like to see this implemented this would let many more apps function like shazam, voice typing and of course voice search...
Sent from my Amazon Kindle Fire using xda premium

roothorick said:
I don't think the Google Now crash is related to the microphone....
Here's the logcat I'm getting:
Code:
{removed}
That doesn't look microphone-related. I think our smoking gun is Wi-Fi location. Unfortunately, disabling location services didn't help :/ Hash, when you get the 2nd part of Wi-Fi location working, try Now and see what it does.
Click to expand...
Click to collapse
Ah, I was seeing an "AudioRecord" error talking about trying to use a non-existant device. This error above I can work on.

Hashcode said:
NOTE: This requires some knowledge of the ALSA subsystem. If you're not comfortable doing this, PLEASE DONT. You can in theory damage the audio hardware with bad settings.
With the migration to Jelly Bean, we can see how powerful having a working MIC would be.
On my latest AOSP Jelly Bean ROM (7/13), I have 3 new binaries so that anyone who is comfortable with the audio system can jump in and help:
tinymix
tinycap
tinyplay
Also, you can install "AlsaMixer" from the Market which gives you a bit of control over the audio system's low level devices.
I feel like if we can get a few devs / knowledgeable users looking at these settings, that we could identify where in our audio driver the mixer for the MIC is getting off track.
THE GOAL:
Get a small list of mixer changes (tinymix / AlsaMixer) which enable the MIC for use in the OS.
Then I can replicate those in the audio driver.
GAME ON.
Click to expand...
Click to collapse
No ALSA experience other than ticking a box or two on my Puppy Linux install - sure wish I did.
This needs to be nailed down for Jelly Bean to work well.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hashcode said:
Ah, I was seeing an "AudioRecord" error talking about trying to use a non-existant device. This error above I can work on.
Click to expand...
Click to collapse
This is purely speculation, but did the other stacktrace come from the 7/11 build? Maybe your half-fix for Wi-Fi location actually broke things, and we actually have TWO blockers here. We won't know for sure until you get location working all the way though.

BUMP
Sent from my PC36100 using xda premium

Alsa mixer keeps installing
I had no luck trying to experiment with alsa mixer sound variables - I installed it from store successfully, but anytime I leave alsa mixer in a way to check is external mic working with some recording app, when I come back to alsa mixer it demands to be again installed. Someone went further with alsa mixer on Kindle JB?

No luck
I've tested it as well but without luck!.
Hoping it works in the near future...

any one here
hope this will work

minhchick said:
any one here
hope this will work
Click to expand...
Click to collapse
Seems it won't.

BrooklynNY said:
Seems it won't.
Click to expand...
Click to collapse
I wouldnt hold my breath...

Hashcode said:
On my latest AOSP Jelly Bean ROM (7/13), I have 3 new binaries so that anyone who is comfortable with the audio system can jump in and help:
tinymix
tinycap
tinyplay
Click to expand...
Click to collapse
Hi Hash,
I've no idea wether anybody else tried, but I just did on your CM10.1 ROM (actually no nightly, I've build one myself as I wanted to learn more about the build process, but it's very close to the latest nightly). And guess what... 2 minutes into trying... it WORKS!!!!! :good::good::good:
Here's what I did:
tinycap xxx.wav -d 3 -c 1 -r 16000 -b 16
I used some regular white Apple iPhone Headset I had lying around (those with the 4-ring plug and the mic in the vol +/- housing).
Except for trying the other capture devices, I promise... I did nothing else, not even played around with tinymix. -d 3 was important... 0 doesn't have capture and the other capture devices didn't even like these simple settings. Now, let's get the audio routed to Google Voice Search .
Best,
STYLON
P.S.: please check out my backlight fix... I fear that what we've there now drains the batteries as even though it seems to be off (screen really completely dark), it's not off very often for me.

stylon said:
Hi Hash, I've no idea wether anybody else tried, but I just did on your CM10.1 ROM (actually no nightly, I've build one myself as I wanted to learn more about the build process, but it's very close to the latest nightly). And guess what... 2 minutes into trying... it WORKS!!!!! :good::good::good:
Here's what I did: tinycap xxx.wav -d 3 -c 1 -r 16000 -b 16......
Click to expand...
Click to collapse
Can it be done with this ROM?

stylon said:
Hi Hash,
I've no idea wether anybody else tried, but I just did on your CM10.1 ROM (actually no nightly, I've build one myself as I wanted to learn more about the build process, but it's very close to the latest nightly). And guess what... 2 minutes into trying... it WORKS!!!!! :good::good::good:
Here's what I did:
tinycap xxx.wav -d 3 -c 1 -r 16000 -b 16
I used some regular white Apple iPhone Headset I had lying around (those with the 4-ring plug and the mic in the vol +/- housing).
Except for trying the other capture devices, I promise... I did nothing else, not even played around with tinymix. -d 3 was important... 0 doesn't have capture and the other capture devices didn't even like these simple settings. Now, let's get the audio routed to Google Voice Search .
Best,
STYLON
P.S.: please check out my backlight fix... I fear that what we've there now drains the batteries as even though it seems to be off (screen really completely dark), it's not off very often for me.
Click to expand...
Click to collapse
I'm not sure hashcode follows this thread anymore...you may want to PM him or try him on another thread
Sent from my GT-N7000 using Tapatalk 2

[MOD] Hidden setting discovered!

So, my good pal freeza found this one. I am merely posting it. We are working on getting it enabled by porting some code over from the galaxy note 2 (if it exists)... but for now, you can see the hidden setting in settings>more settings>"auto power on/off" by adding this line of code here to the very end of your /system/csc/feature.xml file:
</SamsungMobileFeature>
<CscFeature_Clock_ExclusiveEnablingAutoPowerSetting>true
</CscFeature_Clock_ExclusiveEnablingAutoPowerSetting>
(make sure you leave one extra blank line at the end)
you can add these lines using a file explorer that is able to edit system file's text..
after you add this feature, and save it, reboot.
what does this feature do? you can basically set a time interval for your phone to shut off and on automatically. pretty slick.
the trick is, when we were playing around with this, tried to enable it, and it force closes the settings app... I ran a logcat and it showed the classes.dex was not found. boooooo... but looking into and I will keep you guys posted. I have a note 2 rom downloaded right now and so does freeza. cross your fingers, because this is an awesome extra setting!!!
hats off to freeza for finding this.... because when he gets bored he decompiles apks and looks for cool ***t... lol
here is a screenshot of the setting

Nice effin find!!!
Sent from my SGH-T999 using xda premium

Great find dev
Sent from my SGH-T999 using xda premium

agreed! the man is a boss
as i said, we are both investigating this further as we speak (type.. )
Edit** didn't realise I copied an extra line from my feature.xml file.. the "samsung mobile feature" (the first line) does not need to be added because it is already there at the end of your file

AOKP has this already I love it! Good to see it available for a stock Rom.

This doesn't work for me on Frosty v11..any ideas why? I also tried pasting the lines under the settings heading in the feature.xml file but that had no effect also..

Adds option ... But crashes

WarlockW said:
Adds option ... But crashes
Click to expand...
Click to collapse
right. this:
12-04 21:41:49.433 E/AndroidRuntime( 4685): Caused by: android.app.Fragment$InstantiationException: Unable to instantiate fragment com.android.settings.autopoweronoff.AutoPowerOnOffSettings: make sure class name exists, is public, and has an empty constructor that is public
12-04 21:41:49.433 E/AndroidRuntime( 4685): at android.app.Fragment.instantiate(Fragment.java:584)
12-04 21:41:49.433 E/AndroidRuntime( 4685): at android.preference.PreferenceActivity.switchToHeaderInner(PreferenceActivity.java:1222)
12-04 21:41:49.433 E/AndroidRuntime( 4685): at android.preference.PreferenceActivity.switchToHeader(PreferenceActivity.java:1238)
12-04 21:41:49.433 E/AndroidRuntime( 4685): at android.preference.PreferenceActivity.onCreate(PreferenceActivity.java:611)
12-04 21:41:49.433 E/AndroidRuntime( 4685): at com.android.settings.Settings.onCreate(Settings.java:185)
12-04 21:41:49.433 E/AndroidRuntime( 4685): at android.app.Activity.performCreate(Activity.java:5048)
12-04 21:41:49.433 E/AndroidRuntime( 4685): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1094)
12-04 21:41:49.433 E/AndroidRuntime( 4685): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2052)
12-04 21:41:49.433 E/AndroidRuntime( 4685): ... 11 more
12-04 21:41:49.433 E/AndroidRuntime( 4685): Caused by: java.lang.ClassNotFoundException: com.android.settings.autopoweronoff.AutoPowerOnOffSettings

GB27 stock settings keeps crashing

After the upgrade any time I try to open the settings it crashes. Any suggestions. Updated through kies.
Also. Is there any way to get vanilla android launcher on JB. Before I used to be able to clear defaults on tw launcher.
Sent from my SPH-D710 using Tapatalk 2

Here is what log cat shows when starting settings.
Code:
--------- beginning of /dev/log/main
D/dalvikvm( 7818): GC_CONCURRENT freed 364K, 18% free 10095K/12295K, paused 1ms+4ms, total 31ms
D/AbsListView( 7818): [unregisterDoubleTapMotionListener]
I/MotionRecognitionManager( 7818): .unregisterListener : / listener count = 0->0, ubvf 9budiwrd5ordgfl5BakTrklMrfo$,@,)8()ba8
D/AbsListView( 7818): [unregisterDoubleTapMotionListener]
I/MotionRecognitionManager( 7818): .unregisterListener : / listener count = 0->0, ubvf 9budiwrd5ordgfl5BakTrklMrfo$,@,)8*((88
D/AbsListView( 7818): Get MotionRecognitionManager
W/ResourceType( 7818): Failure getting entry for 0x010802c8 (t=7 e=712) in package 0 (error -75)
W/ResourceType( 7818): Failure getting entry for 0x010802c8 (t=7 e=712) in package 0 (error -75)
W/ResourceType( 7818): Failure getting entry for 0x010802c8 (t=7 e=712) in package 0 (error -75)
[\code]
Sent from my SPH-D710 using Tapatalk 2

Any thoughts. If I long press the items in the drop down hose settings display. Its almost as off the settings apk is screwed up for the main intent.
Maybe someone can post their settings.apk I could flash? Would that work.
Sent from my SPH-D710 using Tapatalk 2

Unofficial CM-12.0 for T-Mobile Note 4 Build thread.

CyanogenMod is a free, community built distribution of Android which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This thread is for build questions. See other thread for general info, reports of bugs etc.
NOTE: Be sure to read post #2 in this thread as it contains important info on non-T-Mobile devices, how to build this yourself, and more
The code is now being opened up for community development. Fattire has some instructions below to help you build. Just note the code is still under heavy development and will be changing often.
Just for clarification, myself and fattire are NOT paid employees of Cyngn INC. This is our hobby, and our free time to make this work.
Download
See Official CM-12.0 for Note 4 Thread, go here download.cyanogenmod.org
Also, follow us if you like. We're on the Twitter!
Slayher
fattire
↓↓↓↓↓ Don't forget to read the next post for the CHANGELOG, tips, and info on building this yourself ↓↓↓↓↓
XDA:DevDB Information
CM-12.0 for Tmobile Note 4, ROM for the T-Mobile Samsung Galaxy Note 4
Contributors
slayher, fattire
Source Code: http://github.com/slayher
ROM OS Version: 5.0.x Lollipop
Based On: CyanogenMod
Version Information
Status: Beta
Created 2014-12-07
Last Updated 2015-01-26

I also have to give a big thanks to @fattire for his assistance in getting this up and running.
Click to expand...
Click to collapse
It has been a ton of fun!!! This is my first samsung device and I think we got pretty far in something like 10 days 3 weeks (time flies)
IRC
You *might* find some people hanging out on freenode in #cm-note4. Don't know what that means? No worries, here's a link you can use.
DON'T HAVE T-MOBILE?
That's okay. While the major porting work to the Note 4 is being done by people with TMO, there are threads pertaining to other variants (who work off the T-Mobile version). You can find them here. If your particular device isn't here, start a new device repository for your flavor of the Note 4 and then start a new thread!
Sprint thread (SM-910P). Slayher has started a new repository specifically for sprint users here.
International "EU" thread (SM-910F)
LET THE GAMES BEGIN!
RECENT CHANGES
Official CM nightlies are coming very soon. The latest few releases from Slayher above have last-minute fixes (to audio, bluetooth, battery, etc.) to prepare for the nightly builds... read the last few posts for details.
CHANGES IN 1-20-15 BUILD
Battery Improvements
Audio Updates.
Settings FC's are fixed.
A few other upstream changes.
CHANGES IN 1-18-15 BUILD
More Audio enhancements
Fixes and Cleanups in the init scripts
Kernel adjustments, including disabling the UV and FP sensors
And hopefully some power draw improvements.
FIXED IN 1-9-15 BUILD
Selinux is setup, and fully functional. I have not enforced yet, but it should be good to go.
Revamped the hardware backed keystore system.
UHD (4K) Now working in the Normal Camera APK as well as Google Camera.
The audio stack is now sharing the same HAL as the msm8974.
. Attempted to raise recording Volume. Lets see what happens.
Changed the default DPI to 560. Its better than 640, not as extreme as 515, and its a fully supported DPI in Google Play store.
Upstream CM changes effected normal root access. If you dirty flash, your current root stuff should stay. If you clean wipe you have to enable root in development settings.
Updated the Lockscreen Notification config. Now when the notification comes in, you can interact with the black and white "Ambient Display". It still does not turn on the display when you pick the device up, or remove it from a pocket.
Now you may ask, "What does all this mean?" Well it means that the device tree should be at a point to merged in to CM mainline code, which means..... NIGHTLIES and M-Releases!
FIXED (etc.) IN 1-1-15 BUILD
hefty changes to the power hal system (better battery)
changes to audio HAL and Kernel audio drivers.
Music playback after a resume from pause should be fixed.
Performance profiles are back, and set to "Balanced" The other 2 options are Performance and Power Save.
If you buy the App Cinema FV-5 you will be able to record video in UHD/4k. (stock camera not fixed yet)
More fixes and features from mainline CM12.
FIXED (we think) IN 12-30-14 BUILD
Time service (finally?) fixed (??)
keystore stuff fixed (hardware-backed)
cpu settings fixed
A ton of new stuff forward-ported upstream from CM11->CM12.
BTW you may have to forget and reconnect wifi networks, BT stuff etc, cause of the new crypto routine
FIXED (we think) IN 12-28-14 BUILD
Near-field communication (NFC)
LED color/blink pattern customization (in Settings->Sound & Notification)
SmartCover sleep/wake on open/closing cover
Stylus cursor replaced with new circley-one
Time service (we THINK.. time will tell on this one-- no that is not a pun)
Audio volume reversal now fixed
Many fixes from mainline CM since last time.
FIXED (we think) IN 12-20-14 BUILD
DRM Video (Google Movies, Netflix, etc.) works
Blank screen on some banking apps fixed
MPEG-DASH player
Stylus orientation bug fixed
capacitive buttons works with stylus
p2p fixed
wifi direct works
MMS bug fixed for native MMS app
menu item should appear now in many apps
Simcard Toolkit enabled
Random crash that caused reboots appears to be fixed
Android 5.0.2 merged (because...)
Tons of upstream CM-12 improvements
FIXED (we think) IN 12-11-14 BUILD
Capacitive screen can now be disabled/replaced by soft keys (Settings->Buttons)
SD card/MTP issues fixed (hopefully)
Play Store works w/apps you want.
offmode charging
IR mostly works apparently (I can't test this as I don't have a thing.)
Hangouts now does video/audio chat
NFC shut off (to preserve battery-- wont' keep trying to start)
LOTS of goodness from upstream CM.
You may need to wipe caches, clear settings in the play store and/or wipe /data if nothing else works. Don't come and complain in the thread until you've tried these steps.
OVERALL LIST OF STUFF THAT SEEMS TO WORK
screen w/accelerated graphics
sleep and return from sleep
touchscreen multitouch
panel backlight (adaptive brightness)
audio
SmartCover support
headphone jack detection/playing/buttons
s-pen as mouse (w/ pressure data)
wifi
Camera (front and back)
SD card and internal storage and MTP
voice calls
LED lights (in correct colors)
A ton more sensors (accelerometer/light sensor/proximity/gyroscope/sound/magnetic/pressure) work.
vol/power/capacitive buttons + button backlight
Torch
Mobile data
MMS/SMS
Vibrator (with adjustable intensity)
Video (w/o DRM) works w/sound & rotates correctly. Youtube, etc.
screenshots/screenrecord
GPS
IR
Hangouts video chat
Bluetooth pairing/audio
wireless charging
Play store compatibility
turn off capacitive buttons feature
DRM Video (Google Movies, Netflix, etc.) works
Secure apps
MPEG DASH
p2p/wifi direct
Simcard Toolkit
NFC
UHD (4k) video
hardware-backed encryption
selinux: enforcing
much much more!
In the TODO column still
???
MIGHT GET TO SOMEDAY
fingerprint sensor (There is undocumented support for it in Android 5.0 but no UI in the Settings app to enter your fingerprints. So I think someone would need to write one, if someone hasn't already. Here is the HAL component)
pop s-pen in-out [should it do something special? Let us know what you think...]
UNLIKELY TO EVER WORK (but who knows)
TMobile wifi calling
Samsung-specific magic
touchwiz
THINGS OF INTEREST
User @bttfpromo says you can return the stock cursor (instead of the mouse pointer) with these instructions.
User @DragonAndLance posted a link to boost the in-call sound for those who feel that the defaults aren't high enough.
If you don't like the default screen density, @slayher points out that the following adb command will change it: adb shell wm density 515. I prefer smaller icons (which actually match the physical size of a Nexus 5). Note that these changes will "stick" to the next boot.
Want handwriting recognition? Try the Stylus beta -- a handwriting keyboard similar to the one in TouchWiz.
A terrific demo of the pressure sensitivity of the S-pen stylus is Markers-- it's open source too!
If you need something special to happen when you pop the pen in and out (or press the button), check out this app.
TO BUILD YOURSELF
Building CyanogenMod yourself? That's encouraged here. If you want to learn to build (and thus never have to bother weirdo strangers), you've come to the right place. Start reading about the building process on the wiki, and then join in on the fun.
There are specific step-by-step build instructions for Lollipop on the note 4 (TMO) right here (T-Mobile) and here (Sprint).
Please fix stuff and submit your code pull requests to Slayher's github! Muchas gracias!

wow glad to see CM here its early in the build im sure the bugs will be worked out

Good to go.

Nice ! But how to download source code ? On this link:
slayher said:
Source Code: http://github.com/slayher
Click to expand...
Click to collapse
I don't see any repo I can clone is that correct ? Thanks !

fattire said:
Note: Might want to hold off a few seconds on getting this as a fix to sdcard is coming... right now it shows up in Android but not in file manager and shell /sdcard etc until the fix gets checked in.
Slayher's uploading a fix now...
Click to expand...
Click to collapse
Thanks for the work you have done - been eagerly waiting for this - I knwo a lot is yet to be done - but thanks for all you guys have done so far..
Can you tell me .WHich Gapps are reccomended?

Unoffcial CM-12.0 for T-Mobile Note 4. (trltetmo)
I love u slayher and fattire. Lol. I've been waiting for this day.
---------- Post added at 09:37 PM ---------- Previous post was at 09:33 PM ----------
By the way, I have an account on dev-host if you would like to use it to host your work. Just let me know

Dec 6 2014
fattire said:
Might want get checked in now...
Click to expand...
Click to collapse
T-Mobile Note 4 Owners Should Mark This Day...
Because.. This is the Day it all begins.
The Birth of CM has just arrived for the T-Mobile Samsung Galaxy Note 4 Family..
Congratulations! "Live Long.. And Prosper" :good:

My mobile data doesn't work. but for a first build it's pretty damn impressive.

Oh no Lord. I'm gonna party lol thanks.

Thanks for getting the Ball Rolling! :good:

Oh yeah let the games begin ??????! Very nice to see this & thank you man!

I had a feeling this was gonna happen soon; thanks so much for getting this started guys:good::good:

Thanks so much for this. So glad to have cyanogenmod and not touchwiz. Runs extremely well for me.
For those having issues connecting to WiFi, it seems as though it won't connect if a password is enabled. I configured my router to just use a mac address filter and removed the password to get it working.
Here is a guide for linksys routers: http://kb.linksys.com/Linksys/GetAr...ksys_Wireless_N_Router.xml&pid=80&converted=0

ChrisJ951 said:
Thanks so much for this. So glad to have cyanogenmod and not touchwiz. Runs extremely well for me.
For those having issues connecting to WiFi, it seems as though it won't connect if a password is enabled. I configured my router to just use a mac address filter and removed the password to get it working.
Here is a guide for linksys routers: http://kb.linksys.com/Linksys/GetAr...ksys_Wireless_N_Router.xml&pid=80&converted=0
Click to expand...
Click to collapse
That's interesting... I didn't have any such issue w/my router, which does have a password... actually I've set it up on 3 different routers-- so question, what kind of security settings does your router use?
Mine: WPA2 personal w/AES (possibly not as secure as it could be..) should probably use TKIP-AES but anyhoo
second question-- if you go to /data/misc/wifi/wpa_supplicant.conf you sohuld see some settings that look like this:
network={
ssid="My Router Name"
psk="donttellanyone"
key_mgmt=WPA-PSK
priority=132
}
Are you able to set it up manually by changing this file? Or does it still not work?
MAC address works too for now, but the more we know about the router, the easier it would be to fix...

Ya, I can't connect to my wifi. Haven't tried removing password. Don't feel like going through all that. Seems really smooth though

Great work man..

Don't forget that lollipop has WiFi connectivity issues with routers that have dashes (and spaces?) I believe in the network name. Its been reported on google bug tracker. Does yours have a dash in it by chance ChrisJ951? It affects me connecting to networks at work on the nexus 6.

Actually I just got my wifi working!! Went into advanced wifi menu and changed the Wi-Fi frequency band from auto to 2.4 GHz only

fattire said:
That's interesting... I didn't have any such issue w/my router, which does have a password... actually I've set it up on 3 different routers-- so question, what kind of security settings does your router use?
Mine: WPA2 personal w/AES (possibly not as secure as it could be..) should probably use TKIP-AES but anyhoo
second question-- if you go to /data/misc/wifi/wpa_supplicant.conf you sohuld see some settings that look like this:
network={
ssid="My Router Name"
psk="donttellanyone"
key_mgmt=WPA-PSK
priority=132
}
Are you able to set it up manually by changing this file? Or does it still not work?
MAC address works too for now, but the more we know about the router, the easier it would be to fix...
Click to expand...
Click to collapse
Was using WPA2 personal. Let me re-enable it and try modifying the file manually. Also I don't believe it's a lollipop issue as I have no issue connecting from a Nexus 6
EDIT: So re-enabling the password and it seems to work now. I had rebooted twice without success so I'm unsure of the exact reasoning why it was failing earlier? If it happens again I'll try to get more information on it. It used to immediately popup saying it failed to connect as soon as I entered the password.
2nd edit:
Here was an adb logcat back from when it was happening
Code:
D/DownloadManager( 946): [119] Starting
D/DownloadManager( 946): [119] Finished with status SUCCESS
E/SQLiteLog( 4016): (284) automatic index on sqlite_sq_AFFF7780(url)
D/DownloadManager( 946): [120] Starting
I/LatinIME( 1074): Starting input. Cursor position = 0,73
D/StatusBar.NetworkController( 920): refreshViews: Data not connected!! Set no data type icon / Roaming
D/DownloadManager( 946): [120] Finished with status SUCCESS
D/hardware_info( 369): hw_info_append_hw_type : device_name = speaker
I/art ( 784): Explicit concurrent mark sweep GC freed 21200(971KB) AllocSpace objects, 1(16KB) LOS objects, 29% free, 38MB/54MB, paused 1.105ms total 65.83
1ms
D/DownloadManager( 946): [121] Starting
D/DownloadManager( 946): [121] Finished with status SUCCESS
I/ActivityManager( 784): Killing 2925:com.google.android.gms.unstable/u0a19 (adj 15): empty #17
W/libprocessgroup( 784): failed to open /acct/uid_10019/pid_2925/cgroup.procs: No such file or directory
D/DownloadManager( 946): [122] Starting
E/wpa_supplicant( 890): recvfrom(ctrl_iface): Try again
D/DownloadManager( 946): [122] Finished with status SUCCESS
D/DownloadManager( 946): [123] Starting
D/StatusBar.NetworkController( 920): refreshViews: Data not connected!! Set no data type icon / Roaming
D/DownloadManager( 946): [123] Finished with status SUCCESS
I/art ( 946): Explicit concurrent mark sweep GC freed 41968(2MB) AllocSpace objects, 0(0B) LOS objects, 24% free, 18MB/25MB, paused 549us total 38.970ms
D/DownloadManager( 946): [124] Starting
I/Timeline( 4016): Timeline: Activity_launch_request id:com.google.android.googlequicksearchbox time:665124
I/ActivityManager( 784): START u0 {act=android.intent.action.WEB_SEARCH cat=[android.intent.category.DEFAULT] cmp=com.google.android.googlequicksearchbox/com.g
oogle.android.search.core.google.GoogleSearch (has extras)} from uid 10028 on display 0
W/IInputConnectionWrapper( 4016): endBatchEdit on inactive InputConnection
W/IInputConnectionWrapper( 4016): getTextBeforeCursor on inactive InputConnection
D/WebViewTimersControl( 4016): onBrowserActivityPause
D/WebViewTimersControl( 4016): Pausing webview timers, view=com.android.browser.BrowserWebView{2743b901 VFEDHVCL .F...... 0,0-1440,1225}
E/RichInputConnection( 1074): Unable to connect to the editor to retrieve text.
D/RichInputConnection( 1074): Will try to retrieve text later.
I/QSB.GoogleSearch( 4431): Got intent: #Intent;action=android.intent.action.WEB_SEARCH;category=android.intent.category.DEFAULT;launchFlags=0x800000;component=c
om.google.android.googlequicksearchbox/com.google.android.search.core.google.GoogleSearch;S.com.android.browser.application_id=com.android.browser;S.query=reddi
t;end
W/LocationOracleImpl( 4431): Best location was null
W/IInputConnectionWrapper( 4016): getTextBeforeCursor on inactive InputConnection
E/RichInputConnection( 1074): Unable to connect to the editor to retrieve text.
W/RichInputConnection( 1074): Unable to connect to the editor. Setting caps mode without knowing text.
I/ActivityManager( 784): START u0 {act=android.intent.action.VIEW dat=https://www.google.com/search?redir_esc=&client=ms-android-google&hl=en-US&safe=images&oe
=utf-8&q=reddit&source=android-browser-type&qsubts=1417921621917 flg=0x10000000 pkg=com.android.browser cmp=com.android.browser/.BrowserActivity (has extras)} f
rom uid 10028 on display 0
W/ActivityManager( 784): Duplicate finish request for ActivityRecord{37917e3f u0 com.google.android.googlequicksearchbox/com.google.android.search.core.google.
GoogleSearch t16 f}
W/InputMethodManagerService( 784): Window already focused, ignoring focus gain of: [email protected] attribute=n
ull, token = [email protected]
D/WebViewTimersControl( 4016): onBrowserActivityResume
D/WebViewTimersControl( 4016): Resuming webview timers, view=com.android.browser.BrowserWebView{2743b901 VFEDHVCL .F...... 0,0-1440,1225}
I/Timeline( 4016): Timeline: Activity_idle id: [email protected] time:665287
I/art ( 784): Explicit concurrent mark sweep GC freed 16627(695KB) AllocSpace objects, 3(4MB) LOS objects, 30% free, 36MB/52MB, paused 1.041ms total 73.512
ms
D/DownloadManager( 946): [124] Finished with status SUCCESS
D/DownloadManager( 946): [125] Starting
D/DownloadManager( 946): [125] Finished with status SUCCESS
D/DownloadManager( 946): [126] Starting
D/DownloadManager( 946): [126] Finished with status SUCCESS
I/ActivityManager( 784): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.cyanogenmod.trebuchet/com.android.l
auncher3.Launcher} from uid 1000 on display 0
D/WebViewTimersControl( 4016): onBrowserActivityPause
D/WebViewTimersControl( 4016): Pausing webview timers, view=com.android.browser.BrowserWebView{2743b901 VFEDHVCL .F...... 0,0-1440,2479}
I/ThermalEngine( 303): Sensor:tsens_tz_sensor6:90000 mC
I/ThermalEngine( 303): Sensor:tsens_tz_sensor6:90000 mC
W/IInputConnectionWrapper( 4016): showStatusIcon on inactive InputConnection
I/ThermalEngine( 303): Sensor:tsens_tz_sensor6:88000 mC
I/ThermalEngine( 303): Sensor:tsens_tz_sensor6:88000 mC
I/Timeline( 1247): Timeline: Activity_idle id: [email protected] time:666164
D/DownloadManager( 946): [127] Starting
I/ThermalEngine( 303): Sensor:tsens_tz_sensor8:92000 mC
I/ThermalEngine( 303): Sensor:tsens_tz_sensor8:92000 mC
I/ThermalEngine( 303): Sensor:tsens_tz_sensor8:91000 mC
I/ThermalEngine( 303): ACTION: CPU - Setting CPU[0] to 2572800
I/ThermalEngine( 303): ACTION: CPU - Setting CPU[1] to 2572800
I/ThermalEngine( 303): ACTION: CPU - Setting CPU[2] to 2572800
I/ThermalEngine( 303): ACTION: CPU - Setting CPU[3] to 2572800
I/ThermalEngine( 303): Sensor:tsens_tz_sensor8:87000 mC
I/ThermalEngine( 303): ACTION: CPU - Setting CPU[0] to 2649600
I/ThermalEngine( 303): ACTION: CPU - Setting CPU[1] to 2649600
I/ThermalEngine( 303): ACTION: CPU - Setting CPU[2] to 2649600
I/ThermalEngine( 303): ACTION: CPU - Setting CPU[3] to 2649600
I/ThermalEngine( 303): Sensor:tsens_tz_sensor8:87000 mC
I/Timeline( 784): Timeline: Activity_windows_visible id: ActivityRecord{5fd96ce u0 com.cyanogenmod.trebuchet/com.android.launcher3.Launcher t11} time:666423
D/DownloadManager( 946): [127] Finished with status SUCCESS
D/DownloadManager( 946): [128] Starting
W/OpenGLRenderer( 1247): Incorrectly called buildLayer on View: ShortcutAndWidgetContainer, destroying layer...
W/OpenGLRenderer( 1247): Incorrectly called buildLayer on View: ShortcutAndWidgetContainer, destroying layer...
E/AudioTrack( 784): AudioTrack::set : Exit
D/audio_hw_primary( 369): out_set_parameters: enter: usecase(1: low-latency-playback) kvpairs: routing=2
E/audio_hw_primary( 369): voice_extn_compress_voip_is_active: COMPRESS_VOIP_ENABLED is not defined
E/msm8974_platform( 369): voice_extn_compress_voip_is_active: COMPRESS_VOIP_ENABLED is not defined
D/audio_hw_primary( 369): select_devices: out_snd_device(2: speaker) in_snd_device(0: )
D/hardware_info( 369): hw_info_append_hw_type : device_name = speaker
D/ACDB-LOADER( 369): ACDB -> send_audio_cal, acdb_id = 15, path = 0
D/ACDB-LOADER( 369): ACDB -> send_adm_topology
D/ACDB-LOADER( 369): ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TOPOLOGY_ID
D/ACDB-LOADER( 369): ACDB -> send_asm_topology
D/ACDB-LOADER( 369): ACDB -> ACDB_CMD_GET_AUDPROC_STREAM_TOPOLOGY_ID
D/ACDB-LOADER( 369): ACDB -> send_audtable
D/ACDB-LOADER( 369): ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TABLE
D/ ( 369): ACDBFILE_MGR:Read the devices count as zero, please check the acdb file
D/ACDB-LOADER( 369): ACDB -> AUDIO_SET_AUDPROC_CAL
D/ACDB-LOADER( 369): ACDB -> send_audvoltable
D/ACDB-LOADER( 369): ACDB -> ACDB_CMD_GET_AUDPROC_GAIN_DEP_STEP_TABLE
D/ ( 369): ACDBFILE_MGR:Read the devices count as zero, please check the acdb file
D/ACDB-LOADER( 369): ACDB -> AUDIO_SET_AUDPROC_VOL_CAL
D/ACDB-LOADER( 369): ACDB -> send_afe_cal
D/ACDB-LOADER( 369): ACDB -> ACDB_CMD_GET_AFE_COMMON_TABLE
D/ ( 369): ACDBFILE_MGR:Read the devices count as zero, please check the acdb file
D/ACDB-LOADER( 369): ACDB -> AUDIO_SET_AFE_CAL
D/DownloadManager( 946): [128] Finished with status SUCCESS
W/OpenGLRenderer( 1247): Incorrectly called buildLayer on View: SlidingUpPanelLayout, destroying layer...
I/art ( 784): Explicit concurrent mark sweep GC freed 17401(696KB) AllocSpace objects, 0(0B) LOS objects, 28% free, 39MB/55MB, paused 1.108ms total 66.484m
s
D/DownloadManager( 946): [129] Starting
E/wpa_supplicant( 890): recvfrom(ctrl_iface): Try again
D/DownloadManager( 946): [129] Finished with status SUCCESS
D/DownloadManager( 946): [130] Starting
I/ThermalEngine( 303): Sensor:tsens_tz_sensor5:70000 mC
I/ThermalEngine( 303): Sensor:tsens_tz_sensor6:70000 mC
I/ThermalEngine( 303): Sensor:tsens_tz_sensor7:70000 mC
D/DownloadManager( 946): [130] Finished with status SUCCESS
I/ThermalEngine( 303): Sensor:tsens_tz_sensor6:70000 mC
I/ThermalEngine( 303): Sensor:tsens_tz_sensor7:70000 mC
D/DownloadManager( 946): [131] Starting
I/ThermalEngine( 303): Sensor:tsens_tz_sensor5:87000 mC
D/DownloadManager( 946): [131] Finished with status SUCCESS
The only thing of use that I could see was: E/wpa_supplicant( 890): recvfrom(ctrl_iface): Try again