Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,806,408 Members 53,583 Now Online
XDA Developers Android and Mobile Development Forum

N900 BT_bt_wake wakelock

Tip us?
 
P30SiNa
Old
#1  
P30SiNa's Avatar
Senior Member - OP
Thanks Meter 93
Posts: 212
Join Date: Feb 2012
Location: Shahrood
Thumbs down N900 BT_bt_wake wakelock

Hello. I have this terrible wakelock. I searched the web and didn't find anything. I'm really tired of these wakelocks
Version MK2

It won't let my phone to go to deep sleep. my wifi was off all the time. if I turn it on other wakelocks happen too

Actually, Most of the times I have lots of kernel wakelocks. and Android OS battery drain
Another wakelocks are sec-battery-monitor and wlan_rx_wake when I turn on wifi.
Hope Samsung fix all of these terrible wakelocks...

But anyway... Does anyone know what is causing this wakelock?
Attached Thumbnails
Click image for larger version

Name:	Screenshot_2013-12-14-18-48-39.png
Views:	4268
Size:	196.6 KB
ID:	2454288   Click image for larger version

Name:	Screenshot_2013-12-14-18-55-28.jpg
Views:	4125
Size:	137.2 KB
ID:	2454289  
 
P30SiNa
Old
#2  
P30SiNa's Avatar
Senior Member - OP
Thanks Meter 93
Posts: 212
Join Date: Feb 2012
Location: Shahrood
No one knows? It's the only thing that won't let my phone to go to deep sleep.
I think it's related to bluetooth maybe. But it's off all the time.
Anyone can help me?

Sent from my SM-N900 using Tapatalk
 
sekely
Old
#3  
Junior Member
Thanks Meter 2
Posts: 7
Join Date: Dec 2013
Same here.

===================
General Information
===================
BetterBatteryStats version: 1.15.0.0
Creation Date: 2013-12-23 07:39:12
Statistic Type: Unplugged to Current
Since 7 h 56 m 25 s
VERSION.RELEASE: 4.3
BRAND: samsung
DEVICE: ha3g
MANUFACTURER: samsung
MODEL: SM-N900
OS.VERSION: 3.4.39-2217357
BOOTLOADER: N900XXUCMK2
HARDWARE: universal5420
FINGERPRINT: samsung/ha3gxx/ha3g:4.3/JSS15J/N900XXUCMK2:user/release-keys
ID: JSS15J
TAGS: release-keys
USER: dpi
PRODUCT: ha3gxx
RADIO: N900XXUCMK1
Rooted: false
============
Battery Info
============
Level lost [%]: Bat.: -20% (100% to 80%) [2.5%/h]
Voltage lost [mV]: (4317-4017) [37.8%/h]
===========
Other Usage
===========
Awake (): 7 h 56 m 25 s (28585 s) Ratio: 100.0%
Screen On (): 47 m 5 s (2825 s) Ratio: 9.9%
Wifi On (): 7 h 56 m 25 s (28585 s) Ratio: 100.0%
Wifi Running (): 2 h 50 m 14 s (10214 s) Ratio: 35.7%
Screen dark (): 40 m 55 s (2455 s) Ratio: 8.6%
Screen medium (): 6 m 9 s (369 s) Ratio: 0.6%
=========
Wakelocks
=========
AudioOut_F6 (1013): 4 m 54 s (294 s) Count:4 1.1%
android.media.MediaPlayer (com.sec.android.app.music.Music): 4 m 50 s (290 s) Count:6 1.1%
AudioOut_2 (1013): 2 m 21 s (141 s) Count:12 0.5%
ConnectivityService (Android System): 2 m 7 s (127 s) Count:1125 0.5%
FbClientConnManager (com.facebook.katana.Facebook): 1 m 56 s (116 s) Count:81 0.5%
TimaService (Android System): 1 m 26 s (86 s) Count:98 0.3%
AlarmManager (com.devexpert.weather.Android Weather): 1 m 10 s (70 s) Count:476 0.3%
NlpWakeLock (Google Services): 1 m 10 s (70 s) Count:65 0.3%
ActivityManager-Launch (Android System): 51 s (51 s) Count:403 0.2%
AlarmManager (Android System): 42 s (42 s) Count:1120 0.2%
*sync*_com.android.contacts_Account {name=a0edf64bcb96cc80c74f8b215dc4ded0, type=com.facebook.auth.login} (com.facebook.katana.Facebook): 31 s (31 s) Count:3 0.1%
*sync*_com.android.contacts_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.osp.app.signin} (Samsung Syncadapters): 26 s (26 s) Count:6 0.1%
*sync*_com.android.calendar_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.osp.app.signin} (Samsung Syncadapters): 16 s (16 s) Count:12 0.1%
AlarmReceiver (com.sec.android.app.clockpackage.Clock): 16 s (16 s) Count:6 0.1%
RILJ (Phone): 15 s (15 s) Count:457 0.1%
WifiStateMachine (Android System): 14 s (14 s) Count:523 0.1%
*sync*_gmail-ls_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (com.google.android.gm.Gmail): 10 s (10 s) Count:13 0.0%
*sync*_com.android.calendar_Account {name=0c074206062eebb0a95994421870ecb0, type=com.sec.android.app.sns3.facebook} (com.sec.android.app.sns3.SNS): 10 s (10 s) Count:3 0.0%
wakeLock (Android System): 9 s (9 s) Count:121 0.0%
*sync*_com.samsung.android.SmartClip_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.osp.app.signin} (com.samsung.android.app.pinboard.Scrapbook): 7 s (7 s) Count:3 0.0%
*sync*_com.google.android.gms.people_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (Google Services): 7 s (7 s) Count:415 0.0%
*sync*_com.sec.android.app.sbrowser_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.osp.app.signin} (Samsung Syncadapters): 6 s (6 s) Count:15 0.0%
GCM_CONN_ALARM (Google Services): 5 s (5 s) Count:171 0.0%
Icing (Google Services): 5 s (5 s) Count:514 0.0%
*sync*_com.android.calendar_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (com.google.android.syncadapters.calendar.Google Calendar Sync): 5 s (5 s) Count:18 0.0%
NlpCollectorWakeLock (Google Services): 5 s (5 s) Count:556 0.0%
NetworkLocationLocator (Google Services): 5 s (5 s) Count:517 0.0%
*sync*_com.android.contacts_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.linkedin.android} (com.linkedin.android.LinkedIn): 5 s (5 s) Count:3 0.0%
*sync*_com.android.contacts_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (Google Services): 4 s (4 s) Count:177 0.0%
AlarmManager (com.facebook.katana.Facebook): 4 s (4 s) Count:361 0.0%
NetworkStats (Android System): 4 s (4 s) Count:225 0.0%
SNS (com.sec.android.app.sns3.SNS): 4 s (4 s) Count:12 0.0%
*sync*_com.google.android.music.MusicContent_Accou nt {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (com.google.android.music.Google Play Music): 4 s (4 s) Count:20 0.0%
AlarmManager (Google Services): 3 s (3 s) Count:412 0.0%
*sync*_subscribedfeeds_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (Google Services): 3 s (3 s) Count:636 0.0%
*sync*_com.anydo.provider_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.anydo.account} (Any.DO): 2 s (2 s) Count:19 0.0%
SyncLoopWakeLock (Android System): 2 s (2 s) Count:1389 0.0%
E (net.dinglisch.android.taskerm.Tasker): 2 s (2 s) Count:111 0.0%
fullsync (com.whatsapp.WhatsApp): 2 s (2 s) Count:39 0.0%
*sync*_com.evernote.evernoteprovider_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.evernote} (com.evernote.Evernote): 2 s (2 s) Count:5 0.0%
M (net.dinglisch.android.taskerm.Tasker): 2 s (2 s) Count:99 0.0%
com.google.android.music.leanback.AutoCacheSchedul ingService (com.google.android.music.Google Play Music): 2 s (2 s) Count:17 0.0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 2 s (2 s) Count:4 0.0%
SyncService (com.evernote.Evernote): 2 s (2 s) Count:2 0.0%
DHCP (Android System): 1 s (1 s) Count:453 0.0%
ScheduleNextAlarmWakeLock (com.android.providers.calendar.Calendar storage): 1 s (1 s) Count:34 0.0%
Event Log Service (Google Services): 1 s (1 s) Count:583 0.0%
*sync*_com.google.android.gms.games.background_Acc ount {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (Google Services): 1 s (1 s) Count:3 0.0%
*sync*_com.google.android.location.reporting_Accou nt {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (Google Services): 1 s (1 s) Count:93 0.0%
show keyguard (Android System): 1 s (1 s) Count:126 0.0%
ConnectMQTT (com.nuance.swype.dtc.Swype + Dragon): 1 s (1 s) Count:33 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterB atteryStats): 1 s (1 s) Count:4 0.0%
SCREEN_FROZEN (Android System): 1 s (1 s) Count:455 0.0%
RILS (com.sec.phone.com.sec.phone): 1 s (1 s) Count:11 0.0%
AudioOut_F7 (1013): 1 s (1 s) Count:14 0.0%
================
Kernel Wakelocks !!! wakeup_sources !!!
================
BT_bt_wake (): 7 h 9 m (25740 s) Cntc/wc/ec)6/0/6 -387.9%
PowerManagerService.WakeLocks (): 17 m 34 s (1054 s) Cntc/wc/ec)2411/0/0 3.7%
l2_hsic (): 9 m 17 s (557 s) Cntc/wc/ec)1163/0/1163 2.0%
bluetooth_timer (): 7 m 21 s (441 s) Cntc/wc/ec)12/0/0 1.5%
umts_ipc0 (): 5 m 57 s (357 s) Cntc/wc/ec)1070/0/1070 1.3%
ril-fd (): 5 m 9 s (309 s) Cntc/wc/ec)23/0/0 1.1%
radio-interface (): 3 m 58 s (238 s) Cntc/wc/ec)342/0/0 0.8%
rmnet0 (): 2 m 43 s (163 s) Cntc/wc/ec)123/0/123 0.6%
wlan_rx_wake (): 2 m 37 s (157 s) Cntc/wc/ec)813/0/814 0.6%
wlan_ctrl_wake (): 1 m 41 s (101 s) Cntc/wc/ec)156/0/157 0.4%
wlan_wd_wake (): 56 s (56 s) Cntc/wc/ec)4838/0/0 0.2%
rpm_hsic (): 55 s (55 s) Cntc/wc/ec)1176/0/0 0.2%
alarm (): 22 s (22 s) Cntc/wc/ec)1790/0/0 0.1%
wlan_wake (): 20 s (20 s) Cntc/wc/ec)34092/0/0 0.1%
sec-battery-monitor (): 20 s (20 s) Cntc/wc/ec)952/0/0 0.1%
LightsService (): 16 s (16 s) Cntc/wc/ec)38/0/0 0.1%
bcm2079x_wake_lock_timeout (): 10 s (10 s) Cntc/wc/ec)12/0/12 0.0%
AudioOutLock (): 7 s (7 s) Cntc/wc/ec)5/0/0 0.0%
battery (): 6 s (6 s) Cntc/wc/ec)952/0/0 0.0%
PowerManagerService.Broadcasts (): 2 s (2 s) Cntc/wc/ec)18/0/0 0.0%
PowerManagerService.Display (): (0 s) Cntc/wc/ec)9/0/0 0.0%
bcm2079x_wake_lock (): (0 s) Cntc/wc/ec)13/0/0 0.0%
KeyEvents (): (0 s) Cntc/wc/ec)65473/0/0 0.0%
ApmCommand (): (0 s) Cntc/wc/ec)64/0/0 0.0%
event19-2744 (): (0 s) Cntc/wc/ec)118/0/0 0.0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
1.9 GHz (): 3 m 50 s 0.8%
1.8 GHz (): 1 m 21 s 0.3%
1.7 GHz (): 43 s 0.2%
1.6 GHz (): 1 m 26 s 0.3%
1.5 GHz (): 58 s 0.2%
1.4 GHz (): 21 s 0.1%
1.3 GHz (): 33 s 0.1%
1.2 GHz (): 54 s 0.2%
1.1 GHz (): 2 m 3 s 0.4%
1 GHz (): 1 m 19 s 0.3%
900 MHz (): 1 m 30 s 0.3%
800 MHz (): 5 m 46 s 1.2%
650 MHz (): 5 m 8 s 1.1%
600 MHz (): 15 m 45 s 3.3%
550 MHz (): 25 s 0.1%
500 MHz (): 51 s 0.2%
450 MHz (): 43 s 0.2%
400 MHz (): 2 m 43 s 0.6%
350 MHz (): 5 m 31 s 1.2%
300 MHz (): 2 m 36 s 0.5%
250 MHz (): 7 h 1 m 49 s 88.5%
Deep Sleep (): 0.0%
==================
Reference overview
==================
ref_boot: Reference ref_boot created 40 s (Wl: 7 elements; KWl: 9elements; NetS: null; Alrm: null; Proc: 9 elements; Oth: 3 elements; CPU: 1 elements)
ref_unplugged: Reference ref_unplugged created 9 h 47 m 1 s (Wl: 0 elements; KWl: 39elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 6 elements; CPU: 22 elements)
ref_charged: Reference ref_charged created 9 h 47 m 1 s (Wl: 0 elements; KWl: 39elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 6 elements; CPU: 22 elements)
ref_current: Reference ref_current created 17 h 43 m 27 s (Wl: 55 elements; KWl: 39elements; NetS: null; Alrm: null; Proc: 89 elements; Oth: 7 elements; CPU: 22 elements)
The Following User Says Thank You to sekely For This Useful Post: [ Click to Expand ]
 
contactsunny
Old
#4  
contactsunny's Avatar
Junior Member
Thanks Meter 3
Posts: 3
Join Date: Aug 2011
Location: Mysore

 
DONATE TO ME
Default Same here

My Note 3 is just a few days old. It was fine till now, with no funny wakelocks. But all of a sudden, it seeing the same BT_bt_wake activity today. It's draining like 3% every hour.
The Following User Says Thank You to contactsunny For This Useful Post: [ Click to Expand ]
 
xclub_101
Old
#5  
Senior Member
Thanks Meter 315
Posts: 1,110
Join Date: Oct 2012
Quote:
Originally Posted by contactsunny View Post
My Note 3 is just a few days old. It was fine till now, with no funny wakelocks. But all of a sudden, it seeing the same BT_bt_wake activity today. It's draining like 3% every hour.

My guess is that it is Bluetooth-related, and it should go away if you turn-off Bluetooth (for instance using the quick toggles), so this should be your first test.

If that is correct but you still need to use your Bluetooth-related devices then the next step is to see which device from your paired devices creates problems - my guess is that Bluetooth v4 devices would be fine, but maybe older Bluetooth devices are not handled so well in hardware and as a result keep a wakelock in software.

The problem might also be from a device that is not even paired with your Note 3 but is active around you and keeps sending (discovery?) packets around - in that case I really am curious what could be done (other than trying to turn-off that device).
N9005 Universal Root De La Vega / Mobile Odin Pro, Knox 0x0, MJ7
The Following User Says Thank You to xclub_101 For This Useful Post: [ Click to Expand ]
 
radicalisto
Old
#6  
radicalisto's Avatar
Senior Member
Thanks Meter 1,409
Posts: 3,491
Join Date: Nov 2013
Location: York

 
DONATE TO ME
http://forum.xda-developers.com/show....php?t=2473748



Sent from my SM-N9005 using XDA Premium 4 mobile app
// LG G3 (D855) // Stock // Stock //

S3(White) > M7(Red) > Note 3(Black) > Nexus 5(Black) > M8(Gunmetal) > LG G3 (Titan Grey)
The Following User Says Thank You to radicalisto For This Useful Post: [ Click to Expand ]
 
sekely
Old
#7  
Junior Member
Thanks Meter 2
Posts: 7
Join Date: Dec 2013
Quote:
Originally Posted by xclub_101 View Post
My guess is that it is Bluetooth-related, and it should go away if you turn-off Bluetooth (for instance using the quick toggles), so this should be your first test.

If that is correct but you still need to use your Bluetooth-related devices then the next step is to see which device from your paired devices creates problems - my guess is that Bluetooth v4 devices would be fine, but maybe older Bluetooth devices are not handled so well in hardware and as a result keep a wakelock in software.

The problem might also be from a device that is not even paired with your Note 3 but is active around you and keeps sending (discovery?) packets around - in that case I really am curious what could be done (other than trying to turn-off that device).
I just did a short test:
activated BT for 10 seconds, didn't connect anything to it.
deactivated BT.
left the device for an hour.

bt_bt_wakelock was stuck
The Following User Says Thank You to sekely For This Useful Post: [ Click to Expand ]
 
xclub_101
Old
#8  
Senior Member
Thanks Meter 315
Posts: 1,110
Join Date: Oct 2012
Quote:
Originally Posted by sekely View Post
I just did a short test:
activated BT for 10 seconds, didn't connect anything to it.
deactivated BT.
left the device for an hour.

bt_bt_wakelock was stuck

That is very interesting (and a little worrying, since it means that turning it off does not solve the problem, at least not immediately) - how many devices do you have in your list of paired devices? And how many other devices do you see around you?

I would assume that restarting the phone would fix things, but that is a really messy workaround.
N9005 Universal Root De La Vega / Mobile Odin Pro, Knox 0x0, MJ7
 
MTU79
Old
#9  
Junior Member
Thanks Meter 0
Posts: 4
Join Date: Dec 2013
Default Same stuff w. my SM-N900

Quote:
Originally Posted by P30SiNa View Post
No one knows? It's the only thing that won't let my phone to go to deep sleep.
I think it's related to bluetooth maybe. But it's off all the time.
Anyone can help me?

Sent from my SM-N900 using Tapatalk
Have same **** w. my SM-N900 - afther first on/off bluetooth phone does not go to "deep sleep" if I switch WiFi on. Tried wipe out / safe mode etc - does not help. Looks like either SW bug or something wrong w. hardware (unlikely). The only thing helps for a while - to swithch bluethooth on and off once again, then phone goes to bed till next WiFi on/off. Then you need to on-off your bluetooth once again - and os in the loop.

And yes - bt_bt_wake is whown by BBS as main system wakelock.

any ideas how to shoot this bt_bt_wake issue?... Probably buy IPas mini?.. but it does not have awesome stylus...
 
CoolPyr0
Old
#10  
CoolPyr0's Avatar
Member
Thanks Meter 7
Posts: 67
Join Date: Nov 2013
make Factory reset and try

Sent from my SM-N900 using xda app-developers app

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes