Related
So i got the Tab and had a chance to use it extensively over the past few days.
Below is my day-to-day use comparison with the SGS:
1) Quadrant score is about 1000 (just like 2.2 on SGS) but THERE IS NO LAG. i have about 87 apps installed and it runs flawlessly.
2) GPS is very accurate and have a stronger lock signal. It gets a lock even at the first floor of my house, where the SGS would never lock. Too a drive from San Jose to San Francisco - it never lost track.
3) Screen has "color saturation level" option under the display settings. Even though the Tab does not have SAMOLED screen, if you pull the saturation level all the way to the max, you get a very vibrant color display. not as milky as other TFT screens.
4) The browser does not lag as much as on JPK. it is not super smooth (even with flash disabled), but it does not lag as much. i would hope this can be improved with future firmware.
5) The Tab has 444MB RAM available to the user. it usually uses 280MB. rarely i see usage goes all the way up to 328MB. There is plenty of RAM to go around and it seems to have a much better memory management algorithm than the SGS on JPK (i do not notice memory leaks).
6) Battery life on the Tab is impressive. seems like you can get about 8 hours of CONSTANT usage (i.e. with the screen on) on s single charge. Of course if you don't keep the screen on all the time, you can easily get through the day and then some.
7) Flash 10.1 runs the same as on the SGS. there is room for optimization . My DroidX runs flash much better than both SGS and the Tab.
8) The LED flash is fairly strong. it is not Xenon flash but it is fairly strong for a single LED.
9) The stereo speakers are loud and crisp on the Tab.
10) The TAB DOES fit in the back and front jeans pockets. you do not need an XXL per of jeans for it to fit. it sticks our of the back pocket but it surely fits. I would not site down though while having the tab in my pocket.
11) It has a better reception comparing to the SGS by at least 5db on average (maybe bigger and better antenna? maybe it has more power because it is not designed to be next to our heads, not sure)
12) Some apps on the Tab do not scale well. Samsung sorta have a work around by enabling "compatibility mode" by default in the Android OS. what this does is centering such apps while showing them on a smaller part of the screen. most apps i testes do scale. Those that do not are showing like the iphone apps on the ipad (smaller and in the center of the screen).
13) typing on the TAB is actually very convenient. I use smart Keyboard pro and it is extremely responsive.
14) Graphics FPS are capped at 60fps on the Tab vs 56fps on the SGS.
Overall i am extremely pleased with the Tab. it is an amazing device and very convenient and responsive to work with. Get a nice bluetooth headset and it can easily become my "work phone" while i carry it around in my bag. I am still going to be using the SGS with i want to walk around with something "lighter" LOL.
If the Tab's 2.2 stability and speed is what Samsung has i mind for the SGS, i will be fairly pleased.
The ONLY thing Samsung needs to improve on both the SGS and the Tab is the browser fluidity. I would like to see it as fluid as the Droid X with flash enabled. i know it is possible as the browsing the web on the X is an absolute pleasure.
Feel free to ask any questions you would like about the Tab. i will try to answer from time to time.
Can you actually make phone calls with it? Does it have the phone app/button like the SGS or you can only make calls via VOIP? Can you receive call? assign a number?
I'm wondering if it could replace my SGS completely and use the TAB along with a bluetooth headset to make all my calls.
I have the euro version. Yes it is a full fledged phone if you have a Bluetooth headset.
Nice comparison. Hope that some, if not all of these improvements are received by us with the official froyo update for the SGS. However, I didn't see the point in this comparison really. A phone and a tablet fit completely different applications, even if the manufacturer and the internal hardware is same...
clubtech said:
Feel free to ask any questions you would like about the Tab. i will try to answer from time to time.
Click to expand...
Click to collapse
It's a lot to ask but do you think you could:
1. Install Android Terminal Emulator on the Tab, or use adb shell if you have installed the Android SDK on your PC.
2. Restart the Tab.
3. As soon as possible after the restart, go into Terminal Emulator and type "toolbox dmesg" (Enter) at the command line
4. Also type "toolbox cat /proc/meminfo" (Enter)
4. Paste the messages you get here.
You don't need to root the device to do this.
This will let us look at the memory allocation on this device, including the memory reserved for the hardware at startup. Thanks!
Hi!
What about screen quality? Viewing angles? Do colours change when you are looking at the screen from some angle? What about minimum brightness - is it good for reading books in dark conditions? And how the screen looks under the sun?
Prasad007 said:
Nice comparison. Hope that some, if not all of these improvements are received by us with the official froyo update for the SGS. However, I didn't see the point in this comparison really. A phone and a tablet fit completely different applications, even if the manufacturer and the internal hardware is same...
Click to expand...
Click to collapse
Disagree, first I barely use the phone as a phone, if these were announced at the same time I would've seriously considered the tab instead, particularly if I could've gotten away with cheaper monthly rates and skype. Second, I think your assumption is based on having the SGS, or any smartphone, but that isn't the only audience for this device. In all likelihood, a high majority of us have an SGS, but those who do and don't will be intrigued if they are interested in both or have the SGS and were wondering what this would bring to the table.
I don't disagree with what you're saying, but this comparison is only applicable in terms of specs, features and the wide range of applications that both products can handle. I think we are forgetting that a phone is still primarily a phone! So that is no reason to put a phone and a tablet pc in the same basket. You will never see smartphones being replaced by tablets in the decades to come... In fact it would more likely be quite the opposite, for that is miniaturization. I would like to see phones with very high computing power, and that are easily, conveniently and wirelessly connectable to large screens like monitors and TVs, thereby completely replacing larger computing systems AKA Tab (or even conventional PC's for that matter...). Nanotech anyone ? ;-)
Still, the OP will seemingly be useful towards SGS owners and that's cool!
Hi Congrats on getting the Tab!
For the phone functions eg making calls, does it work without a Bluetooth headset or the speaker phone function? Ie. Could you hold it you your ear and use it like a big (albeit dorky. Heh) phone? What I want is to be able to replace my SGS completely :]
I think it's definitely in the eye of the beholder, until it's easier to replicate what you have on your screen into a computer/TV (I'm thinking wireless, DLNA not covering it, and preferably nothing like a TV-out where you are replicating the screen and therefore, I assume, requiring the screen to be on). Essentially, a wireless docking station, much like bluetooth with auto-pairing potential.
I think the fact that many people aren't interested in tablets is a sign that people don't just want smaller, they want something with plenty of function. Connecting to screens you already have with pocket computers would do that, however, I'm thinking of multimedia on the go and 4.0-4.3" barely cuts it in my book. Personally, I have absolutely no use for a 2.0" device if a 4.0" is just as powerful. If/when things get cheap and powerful enough, yes, redundancy would make me desire something that is essentially weightless and unobtrusive, but until then I don't want smaller than my 4.0" (personally, I don't try to talk for everyone, but the desire for larger devices than 3.5" somewhat speaks for itself.)
Also, I think something with the best of both worlds, small and portable, yet potential for better magazine/e-reader/multimedia on the go is here Future of Screen Technology by TATMobileUI , featured on the Engadget show. There is overlap in our thoughts and where we agree, I understand your original point better, but don't fully agree with it still. If people only wanted smaller, the iPad and Galaxy Tabs wouldn't even exist as these are smartphones masquerading as tablets (product differentiation, even archos is calling a device that might be less than 3" a tablet, it's just a buzz word in a lot of ways). Nonetheless, some good points put in by you.
TheBeano said:
It's a lot to ask but do you think you could:
1. Install Android Terminal Emulator on the Tab, or use adb shell if you have installed the Android SDK on your PC.
2. Restart the Tab.
3. As soon as possible after the restart, go into Terminal Emulator and type "toolbox dmesg" (Enter) at the command line
4. Also type "toolbox cat /proc/meminfo" (Enter)
4. Paste the messages you get here.
You don't need to root the device to do this.
This will let us look at the memory allocation on this device, including the memory reserved for the hardware at startup. Thanks!
Click to expand...
Click to collapse
$ toolbox cat /proc/meminfo
toolbox cat /proc/meminfo
MemTotal: 454248 kB
MemFree: 119708 kB
Buffers: 3892 kB
Cached: 268808 kB
SwapCached: 0 kB
Active: 105148 kB
Inactive: 200552 kB
Active(anon): 33056 kB
Inactive(anon): 0 kB
Active(file): 72092 kB
Inactive(file): 200552 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 136 kB
Writeback: 0 kB
AnonPages: 33008 kB
Mapped: 52100 kB
Shmem: 56 kB
Slab: 9124 kB
SReclaimable: 4052 kB
SUnreclaim: 5072 kB
KernelStack: 1120 kB
PageTables: 2520 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 227124 kB
Committed_AS: 602484 kB
VmallocTotal: 155648 kB
VmallocUsed: 63288 kB
VmallocChunk: 65532 kB
<4>[ 3.392077] [SIF:INF] Number of Free Block ( 25)
<4>[ 3.392088] [SIF:INF] Active Log List : Num ( 8)
<4>[ 3.392100] [SIF:INF] ===> STL Zone[ 4, 0] Open Zone Post
<4>[ 3.393005] [SIF:INF] Partition [0, 24] open is success
<4>[ 3.400760] [SIF:INF] Zone[ 4, 0]: nDgn( 0) nVbn( 33) S( 0)-E( 53)
nCPOffs( 54)
<4>[ 3.401428] [SIF:INF] Zone[ 4, 0]: nDgn( 4) nVbn( 26) S( 28)-E( 28)
nCPOffs( 29)
<4>[ 3.403713] [SIF:INF] Zone[ 4, 0]: nDgn( 1) nVbn( 67) S( 7)-E( 17)
nCPOffs( 18)
<4>[ 3.413550] [BIF: ] FSR VERSION: FSR_1.2.1p1_b129_RTM
<4>[ 3.413571] [BIF: ] FSR_BML_Open(nVol:0, nFlag:0x0, nOpenCnt:6) / 1176
line
<4>[ 3.413605] [SIF:INF] ===> STL Clst[ 0] Scan Root Info
<4>[ 3.414211] [SIF:INF] ===> STL Zone[ 0, 0] Open Zone Meta
<4>[ 3.415104] [SIF:INF] Latest Header Index ( 0) Vbn ( 2)
<4>[ 3.416408] [SIF:INF] Latest Header Clean Page Offset ( 9)
<4>[ 3.416421] [SIF:INF] POR write timer : 0x2d
<4>[ 3.416580] [SIF:INF] Latest Context BlockIdx ( 0) Offset ( 8)
Vpn ( 136)
<4>[ 3.416743] [SIF:INF] Number of Free Block ( 2)
<4>[ 3.416777] [SIF:INF] Active Log List : Num ( 8)
<4>[ 3.416795] [SIF:INF] ===> STL Zone[ 0, 0] Open Zone Post
<4>[ 3.417704] [SIF:INF] Partition [0, 20] open is success
<4>[ 3.419321] [SIF:INF] Zone[ 0, 0]: nDgn( 0) nVbn( 23) S( 2)-E( 10)
nCPOffs( 11)
<4>[ 3.422316] [SIF:INF] Zone[ 0, 0]: nDgn( 1) nVbn( 5) S( 0)-E( 17)
nCPOffs( 18)
<4>[ 3.440639] [onedram_init]
<4>[ 3.440765] [onedram_probe]
<4>[ 3.455304] [svnet_init]
<4>[ 3.466788] [modemctl_init]
<4>[ 3.466913] [modemctl_probe]
<6>[ 3.467643] modemctl xmm: PHONE ACTIVE: 0
<4>[ 3.473325] Storage device init
<4>[ 3.480423] ######## bthid_init: ########
<4>[ 3.481236] ######## bthid_init: done ########
<3>[ 3.485622] init: ro.build.id:FROYO
<3>[ 3.487717] init: ro.build.display.id:FROYO.XXJI5
<3>[ 3.492354] init: ro.build.version.incremental:XXJI5
<3>[ 3.497295] init: ro.build.version.sdk:8
<3>[ 3.501202] init: ro.build.version.codename:REL
<3>[ 3.505759] init: ro.build.version.release:2.2
<3>[ 3.510187] init: ro.build.date:2010. 09. 12. (일) 05:47:00 KST
<3>[ 3.516171] init: ro.build.date.utc:1284238020
<3>[ 3.520589] init: ro.build.type:user
<3>[ 3.524135] init: ro.build.user:root
<3>[ 3.527697] init: ro.build.host:sep-56
<3>[ 3.531429] init: ro.build.tags:release-keys
<3>[ 3.535682] init: ro.product.model:GT-P1000
<3>[ 3.539838] init: ro.product.brand:samsung
<3>[ 3.543915] init: ro.product.name:GT-P1000
<3>[ 3.547992] init: ro.product.device:GT-P1000
<3>[ 3.552244] init: ro.product.board:GT-P1000
<3>[ 3.556406] init: ro.product.cpu.abi:armeabi-v7a
<3>[ 3.561001] init: ro.product.cpu.abi2:armeabi
<3>[ 3.565332] init: ro.product.manufacturer:samsung
<3>[ 3.570024] init: ro.product.locale.language:en
<3>[ 3.574524] init: ro.product.locale.region:GB
<3>[ 3.578867] init: ro.wifi.channels:
<3>[ 3.582338] init: ro.board.platform:s5pc110
<3>[ 3.586524] init: ro.build.product:GT-P1000
<3>[ 3.590668] init: ro.build.description:GT-P1000-user 2.2 FROYO XXJI5 relea
se-keys
<3>[ 3.598125] init: ro.build.fingerprint:samsung/GT-P1000/GT-P1000/GT-P1000:
2.2/FROYO/XXJI5:user/release-keys
<3>[ 3.607842] init: ro.build.PDA1000XXJI5
<3>[ 3.611826] init: ro.build.hidden_ver1000XXJI5
<3>[ 3.616428] init: ro.build.changelist:562468
<3>[ 3.620678] init: ro.tether.denied:false
<3>[ 3.624549] init: rild.libpath:/system/lib/libsec-ril.so
<3>[ 3.629824] init: rild.libargs:-d /dev/ttyS0
<3>[ 3.634077] init: ro.sf.lcd_density:240
<3>[ 3.637890] init: ro.sf.hwrotation:90
<3>[ 3.641533] init: dalvik.vm.heapsize:48m
<3>[ 3.645438] init: ro.opengles.version:131072
<3>[ 3.649687] init: windowsmgr.max_events_per_sec:60
<3>[ 3.654459] init: keyinputqueue.use_finger_id:true
<3>[ 3.659227] init: viewConfig.adjusted_density:1.0
<3>[ 3.663910] init: ro.url.legal:http://www.google.com/intl/%s/mobile/androi
d/basic/phone-legal.html
<3>[ 3.672849] init: ro.url.legal.android_privacy:http://www.google.com/intl/
%s/mobile/android/basic/privacy.html
<3>[ 3.682819] init: ro.com.google.locationfeatures:1
<3>[ 3.687591] init: ro.setupwizard.modeISABLED
<3>[ 3.692011] init: ro.com.google.gmsversion:2.2_r5
<3>[ 3.696695] init: media.stagefright.enable-player:true
<3>[ 3.701815] init: media.stagefright.enable-meta:true
<3>[ 3.706762] init: media.stagefright.enable-scan:true
<3>[ 3.711698] init: media.stagefright.enable-http:true
<3>[ 3.716647] init: keyguard.no_require_sim:true
<3>[ 3.721066] init: ro.config.ringtone:01_Samsung_tune.ogg
<3>[ 3.726358] init: ro.config.notification_sound:01_Sherbet.ogg
<3>[ 3.732081] init: ro.config.alarm_alert:Good_Morning.ogg
<3>[ 3.737376] init: ro.config.media_sound:Media_preview_Beyond_Samsung.ogg
<3>[ 3.744050] init: net.bt.name:Android
<3>[ 3.747692] init: net.change:net.bt.name
<3>[ 3.751600] init: dalvik.vm.stack-trace-file:/data/anr/traces.txt
<3>[ 3.758019] init: ro.com.google.clientidbase:android-skt-kr
<3>[ 3.763220] init: ro.com.google.clientidbase.yt:android-skt-kr
<3>[ 3.769032] init: ro.com.google.clientidbase.am:android-skt-kr
<3>[ 3.774841] init: ro.com.google.clientidbase.gmm:android-skt-kr
<3>[ 3.780740] init: ro.com.google.clientidbase.vs:android-skt-kr
<3>[ 3.786566] init: ro.com.google.clientidbase:android-samsung
<3>[ 3.792173] init: ro.com.google.clientidbase.yt:android-samsung
<3>[ 3.798067] init: ro.com.google.clientidbase.am:android-samsung
<3>[ 3.803971] init: ro.com.google.clientidbase.gmm:android-samsung
<3>[ 3.809950] init: ro.com.google.clientidbase.vs:android-samsung
<3>[ 3.817418] init: persist.sys.country:US
<3>[ 3.819984] init: persist.sys.localevar:
<3>[ 3.824522] init: persist.service.adb.enable:1
<3>[ 3.828937] init: persist.sys.timezone:America/Los_Angeles
<3>[ 3.834401] init: persist.sys.language:en
<3>[ 3.838498] init: ro.FOREGROUND_APP_ADJ:0
<3>[ 3.841674] init: ro.VISIBLE_APP_ADJ:1
<3>[ 3.845394] init: ro.SECONDARY_SERVER_ADJ:2
<3>[ 3.849556] init: ro.BACKUP_APP_ADJ:2
<3>[ 3.853206] init: ro.HOME_APP_ADJ:4
<3>[ 3.856673] init: ro.HIDDEN_APP_MIN_ADJ:7
<3>[ 3.860661] init: ro.CONTENT_PROVIDER_ADJ:14
<3>[ 3.864907] init: ro.EMPTY_APP_ADJ:15
<3>[ 3.868555] init: ro.FOREGROUND_APP_MEM:1536
<3>[ 3.872801] init: ro.VISIBLE_APP_MEM:2048
<3>[ 3.876792] init: ro.SECONDARY_SERVER_MEM:4096
<3>[ 3.881216] init: ro.BACKUP_APP_MEM:4096
<3>[ 3.885123] init: ro.HOME_APP_MEM:4096
<3>[ 3.888848] init: ro.HIDDEN_APP_MEM:5120
<3>[ 3.892752] init: ro.CONTENT_PROVIDER_MEM:5632
<3>[ 3.897175] init: ro.EMPTY_APP_MEM:6144
<3>[ 3.901002] init: wifi.interface:eth0
<3>[ 3.904633] init: ro.bt.bdaddr_path:/data/misc/bluetoothd/bt_addr
<3>[ 3.911598] init: net.tcp.buffersize.default:4096,87380,196608,4096,16384,
110208
<3>[ 3.918091] init: net.change:net.tcp.buffersize.default
<3>[ 3.923291] init: net.tcp.buffersize.wifi:4095,87380,393216,4096,16384,110
208
<3>[ 3.930398] init: net.change:net.tcp.buffersize.wifi
<3>[ 3.935353] init: net.tcp.buffersize.umts:4094,87380,196608,4096,16384,110
208
<3>[ 3.942451] init: net.change:net.tcp.buffersize.umts
<3>[ 3.947400] init: net.tcp.buffersize.edge:4093,26280,35040,4096,16384,3504
0
<3>[ 3.954333] init: net.change:net.tcp.buffersize.edge
<3>[ 3.959284] init: net.tcp.buffersize.gprs:4092,8760,11680,4096,8760,11680
<3>[ 3.966042] init: net.change:net.tcp.buffersize.gprs
<3>[ 3.973814] init: cannot find 'dd', disabling 'create_dfta'
<3>[ 3.978236] init: init.svc.console:running
<3>[ 3.982260] init: init.svc.playlogo:running
<3>[ 3.991717] init: init.svc.pvrsrvinit:running
<3>[ 3.994847] init: init.svc.servicemanager:running
<4>[ 4.001280] [SIF:INF] Zone[ 2, 0]: nDgn( 5) nVbn( 28) S( 0)-E( 1)
nCPOffs( 2)
<3>[ 4.015334] init: init.svc.vold:running
<3>[ 4.017983] init: init.svc.notified_event:running
<3>[ 4.051242] init: init.svc.netd:running
<3>[ 4.068426] init: init.svc.debuggerd:running
<3>[ 4.095162] init: init.svc.ril-daemon:running
<3>[ 4.113133] init: init.svc.DR-deamon:running
<3>[ 4.124102] init: init.svc.mobex-daemon:running
<3>[ 4.146657] init: init.svc.glgps:running
<3>[ 4.164714] init: init.svc.zygote:running
<3>[ 4.181102] init: init.svc.media:running
<6>[ 4.183700] PVR_KWarning): SysFinalise: Version string: SGX540 S5PC110 [
475, services4/system/s5pc110/sysconfig.c]
<3>[ 4.192597] init: init.svc.killmediaserver:running
<6>[ 4.200570] warning: `rild' uses 32-bit capabilities (legacy support in us
e)
<3>[ 4.216998] init: init.svc.dbus:running
<3>[ 4.225825] init: init.svc.installd:running
<3>[ 4.228619] init: cannot find '/system/etc/install-recovery.sh', disabling
'flash_recovery'
<3>[ 4.286769] init: init.svc.keystore:running
<3>[ 4.303820] init: init.svc.immvibed:running
<3>[ 4.320610] init: init.svc.tvout:running
<3>[ 4.335457] init: init.svc.adbd:running
<3>[ 4.337927] init: init.svc.pvrsrvinit:stopped
<6>[ 4.368049] [USB] adb_enable_open
<4>[ 4.368063] [USB] enable_adb
<4>[ 4.368073] [USB] enable_adb - enable(0x10), prev_status(0x04)
<4>[ 4.368082] Here is [email protected]@@@
<4>[ 4.368121] [enable_adb]USBSTATUS_ADB
<4>[ 4.368131] [usb_change_config] list_del 'UMS Only (No debugging mode)'
<6>[ 4.368143] acm_function_config_changed
<6>[ 4.368152] mass_storage_function_config_changed
<6>[ 4.368160] adb_function_config_changed
<4>[ 4.368171] interface 0 = acm/c4d2d0c0
<4>[ 4.368180] interface 1 = acm/c4d2d0c0
<4>[ 4.368188] interface 2 = usb_mass_storage/dfa16800
<4>[ 4.368198] interface 3 = adb/c4d2d240
<4>[ 4.368673] [ap_usb_power_on]AP USB Power ON, askon: 0, mtp : 0
<4>[ 4.368684] !!!!!!!!!!! [ap_usb_power_on]AP samsung_kies_mtp_mode_flag0, m
tp:0
<3>[ 4.393758] init: init.svc.immvibed:stopped
<3>[ 4.442149] init: debug.sf.nobootanimation:0
<4>[ 4.475052] [BIF: ] FSR VERSION: FSR_1.2.1p1_b129_RTM
<4>[ 4.475074] [BIF: ] FSR_BML_Open(nVol:0, nFlag:0x0, nOpenCnt:7) / 1176
line
<4>[ 4.476774] [BIF: ] FSR_BML_Close(nVol: 0, nFlag: 0x0, nOpenCnt: 6)
<4>[ 4.560550] OTG core got reset (1)!!
<4>[ 4.710729] [USB_SWITCH] print_switch_state(1011): usbstatus = 0x1, curren
tusbstatus = 0x10
<3>[ 4.853901] init: ro.csc.country_code:ITALY
<3>[ 4.860794] init: ro.csc.sales_code:ITV
<4>[ 4.924533] acm_disconnected
<4>[ 5.179539] [USB:UMS] fsg_function_setup, return to PC fsg->nluns=2
<4>[ 5.180760] printk:do_inquiry fsg->cdrom 0 curlun->id 0
<4>[ 5.181138] printk:do_inquiry fsg->cdrom 0 curlun->id 0
<4>[ 5.186479] printk:do_inquiry fsg->cdrom 0 curlun->id 1
<4>[ 5.186869] printk:do_inquiry fsg->cdrom 0 curlun->id 1
<3>[ 5.426038] init: sys_prop: permission denied uid:2000 name:adb.connected
<4>[ 5.972389] [ wm8994.c (wm8994_startup,1556) ] Turn on codec
<4>[ 6.041874] [ wm8994.c (wm8994_set_playback_path,397) ] routing to SPK
<4>[ 6.041883]
<4>[ 6.041896] [ wm8994_p1.c (wm8994_set_playback_speaker,1707) ]
<4>[ 6.077282] [ wm8994.c (wm8994_shutdown,1586) ] Stream_type = 0, Stream_st
ate = [0x1], Codec State = [0x1]
<4>[ 6.077301] [ wm8994.c (wm8994_shutdown,1601) ] Turn off Codec!!
<4>[ 6.077313] [ wm8994_p1.c (audio_ctrl_mic_bias_gpio,313) ] MICBIAS Off
<4>[ 6.078199] [ wm8994.c (wm8994_startup,1556) ] Turn on codec
<4>[ 6.142324] [ wm8994.c (wm8994_set_playback_path,397) ] routing to SPK
<4>[ 6.142333]
<4>[ 6.142346] [ wm8994_p1.c (wm8994_set_playback_speaker,1707) ]
<4>[ 6.179672] [SIF:INF] Zone[ 3, 0]: nDgn( 5) nVbn( 71) S( 35)-E( 42)
nCPOffs( 43)
<4>[ 6.226365] [ wm8994.c (wm8994_shutdown,1586) ] Stream_type = 0, Stream_st
ate = [0x1], Codec State = [0x1]
<4>[ 6.226385] [ wm8994.c (wm8994_shutdown,1601) ] Turn off Codec!!
<4>[ 6.226397] [ wm8994_p1.c (audio_ctrl_mic_bias_gpio,313) ] MICBIAS Off
<4>[ 6.227282] [ wm8994.c (wm8994_startup,1556) ] Turn on codec
<4>[ 6.290877] [ wm8994.c (wm8994_set_playback_path,397) ] routing to SPK
<4>[ 6.290887]
<4>[ 6.290899] [ wm8994_p1.c (wm8994_set_playback_speaker,1707) ]
<4>[ 6.534725] [email protected]()
<4>[ 7.960106] [BIF: ] FSR VERSION: FSR_1.2.1p1_b129_RTM
<4>[ 7.960134] [BIF: ] FSR_BML_Open(nVol:0, nFlag:0x0, nOpenCnt:7) / 1176
line
<4>[ 9.169446] [SIF:INF] Zone[ 0, 0]: nDgn( 13) nVbn( 14) S( 0)-E( 1)
nCPOffs( 2)
<4>[ 9.565723] [BIF: ] FSR_BML_Close(nVol: 0, nFlag: 0x0, nOpenCnt: 6)
<3>[ 10.683021] init: audioflinger.bootsnd:0
<4>[ 11.458574] [email protected]()
<4>[ 11.716408] [email protected]()
<4>[ 11.876286] [email protected]_init1()
<4>[ 12.022840] [email protected]_init1()
<3>[ 12.024139] init: init.svc.samsungloop:running
<4>[ 12.362599] [email protected]
<6>[ 12.376356] modemctl xmm: PHONE ACTIVE: 1
<3>[ 12.658166] init: ril.lac:0000
<3>[ 12.660252] init: ril.cid:00000000
<4>[ 13.067815] [SIF:INF] Zone[ 2, 0]: nDgn( 1239) nVbn( 1037) S( 0)-E( 18)
nCPOffs( 19)
<4>[ 13.225751] acm_connected
<6>[ 13.415670] kernel_sec_get_debug_level_from_param: debuglevel.inf read suc
cessfully.
<5>[ 13.415692] (kernel_sec_get_debug_level_from_param) kernel debug level is
0x44494d44 !!
<3>[ 13.415975] init: ril.RildInit:1
<4>[ 13.796113] [ wm8994.c (wm8994_shutdown,1586) ] Stream_type = 0, Stream_st
ate = [0x1], Codec State = [0x1]
<4>[ 13.796133] [ wm8994.c (wm8994_shutdown,1601) ] Turn off Codec!!
<4>[ 13.796145] [ wm8994_p1.c (audio_ctrl_mic_bias_gpio,313) ] MICBIAS Off
Prasad007 said:
Nice comparison. Hope that some, if not all of these improvements are received by us with the official froyo update for the SGS. However, I didn't see the point in this comparison really. A phone and a tablet fit completely different applications, even if the manufacturer and the internal hardware is same...
Click to expand...
Click to collapse
The purpose is the compare the performance on one to one comparison to the SGS.
We would like to figure out why the Tab has 444MB RAM while the SGS is stuck with 304MB RAM.
There is also no lag with the Tab which is ineteresting.
The rest of my post is informative to the interested people.
Prasad007 said:
I don't disagree with what you're saying, but this comparison is only applicable in terms of specs, features and the wide range of applications that both products can handle. I think we are forgetting that a phone is still primarily a phone! So that is no reason to put a phone and a tablet pc in the same basket. You will never see smartphones being replaced by tablets in the decades to come... In fact it would more likely be quite the opposite, for that is miniaturization. I would like to see phones with very high computing power, and that are easily, conveniently and wirelessly connectable to large screens like monitors and TVs, thereby completely replacing larger computing systems AKA Tab (or even conventional PC's for that matter...). Nanotech anyone ? ;-)
Still, the OP will seemingly be useful towards SGS owners and that's cool!
Click to expand...
Click to collapse
Well, in this case it is a Tab that can make phone calls
I have both the SGS and the Tab and in the past few days i have been using the Tab as both my phone (with a BT headset) and as a Tablet.
I now use the SGS when i go out and i need something fits in the pocket more easily.
Honestly guys, maybe it's just me.... But I really have to be more convinced to spend a considerable amount of money on something that does lesser than my laptop, but performs equally as my phone, only less portable...
alovell83 said:
Nonetheless, some good points put in by you.
Click to expand...
Click to collapse
Likewise.
clubtech said:
<4>[ 3.392077] [SIF:INF] Number of Free Block ( 25)
<4>[ 3.392088] [SIF:INF] Active Log List : Num ( 8)
<4>[ 3.392100] [SIF:INF] ===> STL Zone[ 4, 0] Open Zone Post
<4>[ 3.393005] [SIF:INF] Partition [0, 24] open is success
<4>[ 3.400760] [SIF:INF] Zone[ 4, 0]: nDgn( 0) nVbn( 33) S( 0)-E( 53)
nCPOffs( 54)
<4>[ 3.401428] [SIF:INF] Zone[ 4, 0]: nDgn( 4) nVbn( 26) S( 28)-E( 28)
nCPOffs( 29)
<4>[ 3.403713] [SIF:INF] Zone[ 4, 0]: nDgn( 1) nVbn( 67) S( 7)-E( 17)
nCPOffs( 18)
<4>[ 3.413550] [BIF: ] FSR VERSION: FSR_1.2.1p1_b129_RTM
Click to expand...
Click to collapse
Thanks so much, but it looks like the kernel log buffer has already wrapped so we didn't get the start of the kernel boot process, you need to be about 4 seconds faster.
I'm looking for the "system memory reserved" messages to compare with this from the Galaxy S.
Have you used adb shell before? You can connect to the device quite early in the boot process and get the dmesg output then.
P.S. Tell me to take a hike if this is too much hassle. We can always wait for the open-source kernel to be released for the Tab to find this out.
Prasad007 said:
Honestly guys, maybe it's just me.... But I really have to be more convinced to spend a considerable amount of money on something that does lesser than my laptop, but performs equally as my phone, only less portable...
Likewise.
Click to expand...
Click to collapse
It's definitely not just you, but you mentioned the cause, people wanting something smaller than their laptop. Not everyone has a netbook and it's not like netbooks aren't the gold-standard for content creation either. Again, not everyone has, or even desires a smartphone. Some people don't even really want this to be "portable", they want it as an in-home e-reader with more functionality than a Kindle. There are plenty of people this device is for, there are plenty more (like you) who it isn't for.
There's one thing that is for sure, this device is all about size, as is the other iterations Samsung will put out (10" & 12"). 10M to sell in 2011, which I think is too optimistic at these prices, marketed at well over 1B people means that these devices are still largely niche devices.
I am very keen to hear what your thoughts are on the Camera.
1. What is the Camera software like?
2. Does it have similar if not the same functions as the SGS...
i.e. Shooting Mode
Single Shot/Beauty/Continuous/Self Shot/Smile Shot/Panorama/Vintage/Action Shot/Add Me/Cartoon
SCN Mode
None/Landscape/Sports/Portait/Night/Party/etc... etc..
3. What is the quality of shots like?
Can you provide any samples or links to a good sample
4. What is the Video recording like using the Camera?
5. Anything special or different?
I appreciate the Camera is a lower 3MP but I think it uses the same sensor that is fitted in the SGS.
If that is the case then it won't make that much of a difference in shooting.
Thanks in advance.
TheBeano said:
Thanks so much, but it looks like the kernel log buffer has already wrapped so we didn't get the start of the kernel boot process, you need to be about 4 seconds faster.
I'm looking for the "system memory reserved" messages to compare with this from the Galaxy S.
Have you used adb shell before? You can connect to the device quite early in the boot process and get the dmesg output then.
P.S. Tell me to take a hike if this is too much hassle. We can always wait for the open-source kernel to be released for the Tab to find this out.
Click to expand...
Click to collapse
Well the open sourch is out check the developers section i uplaoded it there..
Anyone noticed.. There is no JIT enabled there like in the build.prop in our Galaxy S Froyo roms :S
Is it the RFS filesystem?
So, I switched to CLK today because I missed charging while my phone was powered off, did it all using the HD2 toolkit, using the latest Typhoon ROM CLK version, and the latest CWM
My phone was fine for a few hours, I went and did some errands, however, once I got home, and after a few minutes of using my phone, it simply reboots. Now every few minutes it has rebooted for about 6 hours, and I've done everything I can think of. My thought was that it was the voltage script in the typhoon ROM so I overvolted it, still rebooting, a few hours of searching the internet have prevailed nothing besides this
adb shell cat /proc/kmsg
and using this litttle tidbit, I played with my phone for a few minutes until the below spit out at me and crashed while I was playing Kingdoms Live
Code:
<6>[ 412.050384] alarm_release: clear alarm, pending 0
<6>[ 412.050445] alarm_release: clear alarm, pending 0
<6>[ 412.050476] alarm_release: clear alarm, pending 0
<6>[ 412.050476] alarm_release: clear alarm, pending 0
<6>[ 412.073852] request_suspend_state: wakeup (0->0) at 411171329509 (2011-06-
13 23:03:21.853766391 UTC)
<3>[ 412.075744] init: untracked pid 62 exited
<6>[ 412.093078] __spi_bma150_set_mode: BMA get into SLEEP mode!
<3>[ 412.095245] init: untracked pid 66 exited
<3>[ 412.095703] init: untracked pid 681 exited
<3>[ 412.096069] init: untracked pid 393 exited
<3>[ 412.114501] init: untracked pid 418 exited
<3>[ 412.405975] init: untracked pid 752 exited
<3>[ 412.459716] init: untracked pid 673 exited
<3>[ 412.467864] init: untracked pid 544 exited
<3>[ 412.478790] init: untracked pid 408 exited
<3>[ 412.484588] init: untracked pid 638 exited
<3>[ 412.485992] init: untracked pid 426 exited
<6>[ 412.487701] htc-acoustic: open
<6>[ 412.487823] htc-acoustic: release
<6>[ 412.488159] Audio: voice: stop
<3>[ 412.516082] init: untracked pid 760 exited
<3>[ 412.585784] init: untracked pid 735 exited
<3>[ 412.646118] init: untracked pid 724 exited
<3>[ 412.716094] init: untracked pid 712 exited
<3>[ 412.775604] init: untracked pid 703 exited
<3>[ 412.836975] init: untracked pid 665 exited
<3>[ 412.915649] init: untracked pid 629 exited
<3>[ 412.975555] init: untracked pid 621 exited
<3>[ 413.025665] init: untracked pid 613 exited
<3>[ 413.086944] init: untracked pid 599 exited
<3>[ 413.175872] init: untracked pid 584 exited
<3>[ 413.236419] init: untracked pid 574 exited
<3>[ 413.305999] init: untracked pid 566 exited
<3>[ 413.643402] init: untracked pid 964 exited
<3>[ 413.653442] init: untracked pid 813 exited
<3>[ 413.663909] init: untracked pid 450 exited
<3>[ 413.693298] init: untracked pid 452 exited
<6>[ 415.173156] msm_kgsl: initilized dev=1 mmu=on
<6>[ 415.173339] misc kgsl: firmware: requesting yamato_pm4.fw
<6>[ 415.175781] misc kgsl: firmware: requesting yamato_pfp.fw
<3>[ 415.177001] init: untracked pid 1049 exited
<3>[ 415.196441] init: untracked pid 1050 exited
<6>[ 415.212677] __spi_bma150_set_mode: BMA get into NORMAL mode!
<6>[ 415.453002] __spi_bma150_set_mode: BMA get into SLEEP mode!
<4>[ 443.564605] [D:BATT] V=4052(67d) I=201(1fd) C=1978.0/2300(1879) id=5(9f) T
=260(27) KADC=882
<6>[ 443.564697] batt: ds2784_notify: 1 86 at 442662204752 (2011-06-13 23:03:53
.344641635 UTC)
<6>[ 443.564788] batt: batt:power_supply_changed: battery at 442662296305 (2011
-06-13 23:03:53.344733188 UTC)
<4>[ 459.908081] STA connect received 1
<7>[ 469.112701] eth0: no IPv6 routers present
one interesting thing I noticed is that the phone doesn't fully crash, ADB stayed tagged along through the reboot and the device never disconnected from my PC
any ideas?
The current typhoon rom coms with the 1.2 gps libs from tytung with agps support...unfortunatly they are causing random reboots.
2 solutions:
1. flash the 1.1 libs - missing agps support
2. just leave your gps on - it won't drain any battery, just permits an app that asking for gps.
Because i can not post in the Dev section i try it here.
On the new Utopia RC4 ROM the Wlan can not be activated, it just say's scanning is not possible an then it gets deactivated.
Sirius1977 said:
Because i can not post in the Dev section i try it here.
On the new Utopia RC4 ROM the Wlan can not be activated, it just say's scanning is not possible an then it gets deactivated.
Click to expand...
Click to collapse
Try reflashing because its supposed
to be working!!
Nope, didn't work. Tried to flash again via fastboot and at the second try i made a recovery version which also didn't make the wifi work.
Same message: Networkscan is not possible
dmesg output:
Code:
<4>[ 560.902218] register_mmc_card_pm: [WiFi] Callbacks registered successfully.
<3>[ 560.902608] [yoohoo] dhd_register_hwakeup : start
<3>[ 560.902848] [dhd_hostwakeup_isr] HostWakeup Get GPIO 94: 1
<3>[ 560.903240] [yoohoo] dhd_register_hwakeup : OK
<4>[ 560.903445] [yoohoo] dhd_enable_hwakeup : succeed irq 158
<3>[ 560.903810] [dhd_register_early_suspend] HostWakeup Get GPIO 94: 1
<4>[ 560.904012]
<4>[ 560.904017] Dongle Host Driver, version 4.217.91.0
<4>[ 561.104080] =========== WLAN going back to live ========
<6>[ 561.104328] mmc1: Slot status change detected (0 -> 1)
<3>[ 561.104886] (swift_sdcc_setup_power)vdd :12
<3>[ 561.107221] (swift_sdcc_setup_power)vdd :12
<3>[ 561.109586] (swift_sdcc_setup_power)vdd :12
<3>[ 561.112228] (swift_sdcc_setup_power)vdd :12
<3>[ 561.120059] (swift_sdcc_setup_power)vdd :12
<3>[ 561.121993] (swift_sdcc_setup_power)vdd :12
<7>[ 561.183765] mmc1: queuing CIS tuple 0x80 length 51
<7>[ 561.191050] mmc1: queuing CIS tuple 0x80 length 7
<7>[ 561.194554] mmc1: queuing CIS tuple 0x80 length 2
<7>[ 561.204207] mmc1: queuing CIS tuple 0x80 length 10
<7>[ 561.206143] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.207915] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.209852] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.211637] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.213400] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.215332] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.217095] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.219025] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.220790] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.222560] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.224492] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.227047] mmc1: queuing CIS tuple 0x02 length 1
<3>[ 561.228268] (swift_sdcc_setup_power)vdd :12
<3>[ 561.228515] (swift_sdcc_setup_power)vdd :12
<6>[ 561.231190] mmc1: new SDIO card at address 0001
<4>[ 561.236461] mem_prealloc: section [3] size[139264]
<4>[ 561.236671] mem_prealloc: This data is using!!!
<4>[ 561.237255] alloc static buf at cccc0000!
<4>[ 561.237451] mem_prealloc: section [4] size[0]
<4>[ 561.239636] DHD: dongle ram size is set to 393216(orig 393216)
<4>[ 561.240125] mem_prealloc: section [0] size[10312]
<4>[ 561.240371] mem_prealloc: This data is using!!!
<4>[ 561.241366] mem_prealloc: section [1] size[10300]
<4>[ 561.241623] mem_prealloc: This data is using!!!
<4>[ 561.241890] mem_prealloc: section [2] size[32768]
<4>[ 561.242338] mem_prealloc: This data is using!!!
<6>[ 561.765387] wlan0 (): not using net_device_ops yet
<4>[ 561.770128] wlan0: Broadcom Dongle Host Driver mac=00:26:e8:af:0b:bb
<4>[ 563.957310] wlan0: non-BDC packet received, flags 0x10
<3>[ 578.949398] init: untracked pid 2131 exited
<4>[ 579.974021] unregister_mmc_card_pm: [WIFI] Unregistering suspend/resume callbacks.
<4>[ 580.243393] =========== WLAN placed in RESET ========
<6>[ 580.243909] mmc1: Slot status change detected (1 -> 0)
<6>[ 580.258381] mmc1: card 0001 removed
<3>[ 580.260527] (swift_sdcc_setup_power)vdd :0
#
Hmm... also the MAC adress didn't appear the Advanced Wifi settings.
For now i'm back to RC3 and ... wifi works
It is my mistake!
Try this fix!
Hmm... simply cut & paste didn't work. How can i apply the fix?
Sirius1977 said:
Hmm... simply cut & paste didn't work. How can i apply the fix?
Click to expand...
Click to collapse
install with recovery
No chance to install in CWM
Always getting Error on applying (Status 6)
Sirius1977 said:
No chance to install in CWM
Always getting Error on applying (Status 6)
Click to expand...
Click to collapse
last fix was broken? download fix again.
Error (Status 6) again
I try to set the permissions for the .so manually
Ok... I got it
adb shell
cd /system/lib
chmod 06755 libhardware_legacy.so
exit
dont't forget to mount the system partition as r/w in root explorer
Thanks to all for the fast response.
Great ROM
Ok that was to fast.
Wifi is on and it can scan for AP's but it can't connect.
Sirius1977 said:
Ok that was to fast.
Wifi is on and it can scan for AP's but it can't connect.
Click to expand...
Click to collapse
Does your router work?
Sent from my GT540 using XDA App
Yes, meanwhile the problem was confirmed by others.
No wifi........MIROSLAV_MM where are you;-)
Edit-Forgot to add 'I love your work'
Sent from my GT540 using xda premium
sanmit said:
No wifi........MIROSLAV_MM where are you;-)
Edit-Forgot to add 'I love your work'
Sent from my GT540 using xda premium
Click to expand...
Click to collapse
RC4 has been withdrawn due to this wifi issue.
Sent from my GT540 using xda premium
I am trying to boot ubuntu from my nexus 7, here's what i did:
1. Unlock and root the device
2. Install MultiRom, and the apply kernel patch(TWRP Menu->Install->kernel_kexec_42.zip)
3. Download the Ubuntu for Nexus 7 Rom
4. Install the rom from the multirom(Advanced->MultiRom->Add ROM->Ubuntu->ubuntu-xxxx.img.gz)
However I cannot boot into the system, the error is:
An Error Occurred,
Multirom is shut down to prevent data corruption.
What I've done to try to fix the problem:
1. fix file permissions
2. Inject boot.img file. inject current boot sector
3. checked that the downloaded ubuntu image has the same MD5 with the server.
Can anyone help me with the problem?
Here's the Error Log
<6>[ 5.807195] EXT4-fs (mmcblk0p9): recovery complete
<6>[ 5.808362] EXT4-fs (mmcblk0p9): mounted filesystem with ordered data mode. Opts: user_xattr,acl,barrier=1,data=or
dered
<3>[ 5.819800] trampoline: Running multirom
<3>[ 5.828873] multirom: Loading MultiROM status...
<3>[ 5.829147] multirom: Adding ROM Internal
<3>[ 5.829902] multirom: Adding ROM nexus7
<3>[ 5.831551] multirom: Could not find rom to auto-boot
<3>[ 5.831632] multirom: Dumping multirom status:
<3>[ 5.831830] multirom: is_second_boot=0
<3>[ 5.831905] multirom: current_rom=Internal
<3>[ 5.831978] multirom: auto_boot_seconds=0
<3>[ 5.832109] multirom: auto_boot_rom=NULL
<3>[ 5.832181] multirom: curr_rom_part=NULL
<3>[ 5.832311] multirom:
<3>[ 5.832383] multirom: ROM: Internal
<3>[ 5.832457] multirom: base_path: /realdata/media/0/multirom/roms/Internal
<3>[ 5.832589] multirom: type: 0
<3>[ 5.832661] multirom: has_bootimg: 1
<3>[ 5.832733] multirom: ROM: nexus7
<3>[ 5.832864] multirom: base_path: /realdata/media/0/multirom/roms/nexus7
<3>[ 5.832938] multirom: type: 6
<3>[ 5.833069] multirom: has_bootimg: 0
<3>[ 29.220323] multirom: Found part mmcblk0p9: 57f8f4bc-abf4-655f-bf67-946fc0f9f25b, ext4
<3>[ 29.220493] multirom: Dumping multirom status:
<3>[ 29.220568] multirom: is_second_boot=0
<3>[ 29.220641] multirom: current_rom=Internal
<3>[ 29.220772] multirom: auto_boot_seconds=0
<3>[ 29.220846] multirom: auto_boot_rom=NULL
<3>[ 29.220920] multirom: curr_rom_part=NULL
<3>[ 29.221048] multirom:
<3>[ 29.221119] multirom: ROM: Internal
<3>[ 29.221192] multirom: base_path: /realdata/media/0/multirom/roms/Internal
<3>[ 29.221325] multirom: type: 0
<3>[ 29.221398] multirom: has_bootimg: 1
<3>[ 29.221531] multirom: ROM: nexus7
<3>[ 29.221604] multirom: base_path: /realdata/media/0/multirom/roms/nexus7
<3>[ 29.221735] multirom: type: 6
<3>[ 29.221808] multirom: has_bootimg: 0
<3>[ 29.225028] multirom: Failed to get initrd path
Hi guys,
I have a problem with my N4 ever since updating to 5.1: The phone randomly reboots every two to five days while it's asleep. The screens lights up, the Google logo shows and it boots up normally. The device is rooted, now running LMY48T stock ROM with stock recovery. I upgraded to the latest handful of security releases by manually flashing radio, recovery, boot and system from factory images via fastboot.
Did a quick search and came up with 2 similar threads ([1],[2]) on the forums and this one on the Google forums. There's a multitude of solutions discussed (safe mode, keep WiFi off, keep Bluetooth on, clear cache, full wipe), but none is confirmed to be a global solution - probably because nobody seems to know what the actual problem is. I always cleared the cache after any update and because I flashed partitions from 4 or 5 factory images since the problem first appeared, it can't be a problem with corrupt images. Didn't try the other "solutions" yet, because they're all just poking around in the dark.
But I got lucky an hour ago and caught a reboot while the phone was sitting on the table in front of me. I tried a logcat, but this seems to show the after-boot stuff only. But the last_kmesg got it:
Code:
[28518.648487] msm_pm_enter
[28518.648487] msm_pm_enter: power collapse
[28518.648487] msm_mpm_irqs_detectable: cannot monitor 000000,00000000,00000000,00000000,00000000,00000020,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000
[28518.648487] msm_pm_enter: return
[28518.648487] gic_show_resume_irq: 234 triggered
[28518.648487] Resume caused by IRQ 234, wcnss_wlan
[28518.650288] PM: noirq resume of devices complete after 1.586 msecs
[28518.652669] PM: early resume of devices complete after 0.976 msecs
[28518.654408] wakeup wake lock: qcom_rx_wakelock
[28518.657064] msm_fb_ext_resume: Turning on HPD circuitry
[28518.660665] PM: resume of devices complete after 7.963 msecs
[28518.662954] Restarting tasks ... done.
[28518.665518] PM: suspend exit 2015-10-14 15:36:25.007841530 UTC
[28518.665640] suspend: exit suspend, ret = 0 (2015-10-14 15:36:25.007963577 UTC)
[28518.665701] active wake lock qcom_rx_wakelock, time left 3
[28518.665823] suspend: abort suspend
[28518.695489] wake lock qcom_rx_wakelock, expired
[28518.695763] PM: Syncing filesystems...
[28518.704279] suspend: enter suspend
[28518.704431] PM: suspend entry 2015-10-14 15:36:25.046700550 UTC
[28518.706720] sync done.
[28518.706842] PM: Syncing filesystems...
[28518.716670] sync done.
[28518.773163] Freezing user space processes ... (elapsed 0.005 seconds) done.
[28518.779359] Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done.
[28518.783632] Suspending console(s) (use no_console_suspend to debug)
[28518.795443] msm_fb_ext_suspend: Turning off HPD circuitry
[28518.812870] PM: suspend of devices complete after 25.373 msecs
[28518.814488] PM: late suspend of devices complete after 1.585 msecs
[28518.817875] power_suspend_late return 0
[28518.817906] PM: noirq suspend of devices complete after 3.415 msecs
[28518.817936] Disabling non-boot CPUs ...
[28518.818791] msm_pm_enter
[28518.818791] msm_pm_enter: power collapse
[28518.818791] msm_mpm_irqs_detectable: cannot monitor 000000,00000000,00000000,00000000,00000000,00000020,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000
[28518.818791] msm_pm_enter: return
[28518.818791] gic_show_resume_irq: 234 triggered
[28518.818791] Resume caused by IRQ 234, wcnss_wlan
[28518.821996] PM: noirq resume of devices complete after 2.653 msecs
[28518.825414] PM: early resume of devices complete after 1.555 msecs
[28518.828374] wakeup wake lock: qcom_rx_wakelock
[28518.832861] msm_fb_ext_resume: Turning on HPD circuitry
[28518.837195] PM: resume of devices complete after 11.741 msecs
[28518.839514] Restarting tasks ... done.
[28518.842231] PM: suspend exit 2015-10-14 15:36:29.008051614 UTC
[28518.842292] suspend: exit suspend, ret = 0 (2015-10-14 15:36:29.008143110 UTC)
[28518.842383] active wake lock qcom_rx_wakelock, time left 4
[28518.842444] suspend: abort suspend
[28518.877054] wake lock qcom_rx_wakelock, expired
[28518.877237] PM: Syncing filesystems...
[28518.885692] suspend: enter suspend
[28518.885844] PM: suspend entry 2015-10-14 15:36:29.051657969 UTC
[28518.889873] sync done.
[28518.890117] PM: Syncing filesystems...
[28518.901288] sync done.
[28518.953142] Freezing user space processes ... (elapsed 0.005 seconds) done.
[28518.959215] Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done.
[28518.963274] Suspending console(s) (use no_console_suspend to debug)
[28518.975269] msm_fb_ext_suspend: Turning off HPD circuitry
[28518.992604] PM: suspend of devices complete after 25.283 msecs
[28518.994222] PM: late suspend of devices complete after 1.585 msecs
[28518.997640] power_suspend_late return 0
[28518.997671] PM: noirq suspend of devices complete after 3.415 msecs
[28518.997671] Disabling non-boot CPUs ...
[28518.998556] msm_pm_enter
[28518.998556] msm_pm_enter: power collapse
[28518.998556] msm_mpm_irqs_detectable: cannot monitor 000000,00000000,00000000,00000000,00000000,00000020,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000
[28518.998556] msm_pm_enter: return
[28518.998556] gic_show_resume_irq: 230 triggered
[28518.998556] Resume caused by IRQ 230, smd_dev
[28519.001761] PM: noirq resume of devices complete after 2.653 msecs
[28519.005270] PM: early resume of devices complete after 1.525 msecs
[28519.010612] wlan: [27367:E :PE ] limDeactivateAndChangeTimer: 1438: Deactivated probe after hb timer
[28519.011039] wakeup wake lock: event0-585
[28519.012351] msm_fb_ext_resume: Turning on HPD circuitry
[28519.016899] PM: resume of devices complete after 11.620 msecs
[28519.019279] Restarting tasks ... done.
[28519.029961] PM: suspend exit 2015-10-14 15:36:39.014333914 UTC
[28519.030084] suspend: exit suspend, ret = 0 (2015-10-14 15:36:39.014455882 UTC)
[28519.030145] active wake lock alarm, time left 500
[28519.030236] suspend: abort suspend
[28528.470065] wlan: [27367:E :PE ] limHandleHeartBeatFailureTimeout: 7199: Probe_hb_failure: SME 12, MLME 16, HB-Count 1
[28528.475895] wlan: [27367:E :SME] sme_QosPmcDeviceStateUpdateInd: 7219: nothing to process in PMC state 6
[28528.476017] wlan: [27367:E :TL ] ----> CRegion 1, hRSSI -74, Alpha 5
[28528.496587] adjust_soc: ibat_ua = 297200, vbat_uv = 3830741, soc = 57, batt_temp=238
[28528.518226] active wake lock alarm, time left 500
[28528.518318] suspend: abort suspend
[28528.518501] active wake lock alarm, time left 500
[28528.518562] suspend: abort suspend
[28528.518989] active wake lock alarm, time left 500
[28528.519050] suspend: abort suspend
[28528.519325] active wake lock alarm, time left 500
[28528.519417] suspend: abort suspend
[28528.519905] active wake lock alarm, time left 500
[28528.519966] suspend: abort suspend
[28528.520363] active wake lock alarm, time left 500
[28528.520424] suspend: abort suspend
[28528.520760] active wake lock alarm, time left 500
[28528.520882] suspend: abort suspend
[28528.521217] active wake lock alarm, time left 500
[28528.521339] suspend: abort suspend
[28528.521675] active wake lock alarm, time left 500
[28528.521736] suspend: abort suspend
[28528.522133] active wake lock alarm, time left 500
[28528.522194] suspend: abort suspend
[28528.522438] active wake lock alarm, time left 500
[28528.522560] suspend: abort suspend
[28528.522957] active wake lock alarm, time left 500
[28528.523049] suspend: abort suspend
[28528.523415] active wake lock alarm, time left 500
[28528.523476] suspend: abort suspend
[28528.523689] active wake lock alarm, time left 500
[28528.523812] suspend: abort suspend
[28528.524117] active wake lock alarm, time left 500
[28528.524208] suspend: abort suspend
[28537.426909] wlan: [27367:E :PE ] limDeactivateAndChangeTimer: 1438: Deactivated probe after hb timer
[28537.466738] wlan: [27367:E :PE ] limHandleHeartBeatFailureTimeout: 7199: Probe_hb_failure: SME 12, MLME 16, HB-Count 1
[28538.431152] wlan: [27367:E :SME] sme_QosPmcDeviceStateUpdateInd: 7219: nothing to process in PMC state 6
[28538.431396] wlan: [27367:E :TL ] ----> CRegion 1, hRSSI -74, Alpha 5
[28539.806583] wlan: [27367:E :SME] csrNeighborRoamResultsRefreshTimerCallback: 2615: Non 11R or CCX Association:results refresh timer expired
[28544.910169] healthd: battery l=57 v=3832 t=23.8 h=2 st=3 c=322 chg=
[28545.312641] wlan: [27367:E :SME] csrNeighborRoamPrepareScanProfileFilter: 1197: Filtering for SSID ******** from scan results,length of SSID = 11
[28545.312824] wlan: [27367:E :SME] csrNeighborRoamProcessScanComplete: 1867: No candidate found after scanning in state 3..
[28549.796694] adjust_soc: ibat_ua = 210900, vbat_uv = 3838052, soc = 58, batt_temp=237
[28549.805881] healthd: battery l=57 v=3839 t=23.8 h=2 st=3 c=254 chg=
[28557.704462] wlan: [27367:E :PE ] limDeactivateAndChangeTimer: 1438: Deactivated probe after hb timer
[28557.746610] wlan: [27367:E :PE ] limHandleHeartBeatFailureTimeout: 7199: Probe_hb_failure: SME 12, MLME 16, HB-Count 1
[28558.700463] wlan: [27367:E :SME] sme_QosPmcDeviceStateUpdateInd: 7219: nothing to process in PMC state 6
[28558.700799] wlan: [27367:E :TL ] ----> CRegion 1, hRSSI -79, Alpha 5
[28562.721492] healthd: battery l=57 v=3850 t=23.8 h=2 st=3 c=165 chg=
[28566.003500] wlan: [27367:E :PE ] limDeactivateAndChangeTimer: 1438: Deactivated probe after hb timer
[28566.036462] wlan: [27367:E :PE ] limHandleHeartBeatFailureTimeout: 7199: Probe_hb_failure: SME 12, MLME 16, HB-Count 1
[28567.000814] wlan: [27367:E :SME] sme_QosPmcDeviceStateUpdateInd: 7219: nothing to process in PMC state 6
[28567.001028] wlan: [27367:E :TL ] ----> CRegion 1, hRSSI -79, Alpha 5
[28572.460665] wlan: [27367:E :PE ] limDeactivateAndChangeTimer: 1438: Deactivated probe after hb timer
[28572.496679] wlan: [27367:E :PE ] limHandleHeartBeatFailureTimeout: 7199: Probe_hb_failure: SME 12, MLME 16, HB-Count 1
[28573.461062] wlan: [27367:E :SME] sme_QosPmcDeviceStateUpdateInd: 7219: nothing to process in PMC state 6
[28573.461458] wlan: [27367:E :TL ] ----> CRegion 1, hRSSI -79, Alpha 5
[28579.829259] wlan: [27367:E :PE ] limDeactivateAndChangeTimer: 1438: Deactivated probe after hb timer
[28579.876566] wlan: [27367:E :PE ] limHandleHeartBeatFailureTimeout: 7199: Probe_hb_failure: SME 12, MLME 16, HB-Count 1
[28580.166754] adjust_soc: ibat_ua = 245800, vbat_uv = 3826937, soc = 58, batt_temp=238
[28580.174750] healthd: battery l=57 v=3839 t=23.8 h=2 st=3 c=245 chg=
[28580.980152] wlan: [27367:E :SME] sme_QosPmcDeviceStateUpdateInd: 7219: nothing to process in PMC state 6
[28580.980518] wlan: [27367:E :TL ] ----> CRegion 1, hRSSI -79, Alpha 5
[28583.295153] healthd: battery l=57 v=3839 t=23.8 h=2 st=3 c=222 chg=
[28586.280808] wlan: [27367:E :PE ] limDeactivateAndChangeTimer: 1438: Deactivated probe after hb timer
[28586.316487] wlan: [27367:E :PE ] limHandleHeartBeatFailureTimeout: 7199: Probe_hb_failure: SME 12, MLME 16, HB-Count 1
[28587.280473] wlan: [27367:E :SME] sme_QosPmcDeviceStateUpdateInd: 7219: nothing to process in PMC state 6
[28587.280839] wlan: [27367:E :TL ] ----> CRegion 1, hRSSI -79, Alpha 5
[28588.904736] suspend: enter suspend
[28588.904858] PM: suspend entry 2015-10-14 15:37:48.888561905 UTC
[28588.904950] PM: Syncing filesystems...
[28588.973773] Freezing user space processes ... (elapsed 0.002 seconds) done.
[28588.980427] sync done.
[28589.216502] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[28589.218760] Suspending console(s) (use no_console_suspend to debug)
[28589.222698] msm_fb_ext_suspend: Turning off HPD circuitry
[28589.239606] PM: suspend of devices complete after 19.319 msecs
[28589.240796] PM: late suspend of devices complete after 1.159 msecs
[28589.243146] active wake lock alarm, time left 473
[28589.243146] power_suspend_late return -11
[28589.243177] dpm_run_callback(): power_suspend_late+0x0/0x58 returns -11
[28589.243207] PM: Device power.0 failed to suspend noirq: error -11
[28589.244642] PM: noirq resume of devices complete after 1.434 msecs
[28589.247328] PM: early suspend of devices complete after 1.251 msecs
[28589.247328] PM: Some devices failed to power down
[28589.250837] msm_fb_ext_resume: Turning on HPD circuitry
[28589.252119] PM: resume of devices complete after 4.761 msecs
[28589.254011] Restarting tasks ... done.
[28589.256697] PM: suspend exit 2015-10-14 15:37:49.240370238 UTC
[28589.256758] suspend: exit suspend, ret = -11 (2015-10-14 15:37:49.240461800 UTC)
[28589.256850] active wake lock alarm, time left 471
[28589.256911] suspend: abort suspend
[28594.575971] wlan: [27367:E :PE ] limDeactivateAndChangeTimer: 1438: Deactivated probe after hb timer
[28594.606461] wlan: [27367:E :PE ] limHandleHeartBeatFailureTimeout: 7199: Probe_hb_failure: SME 12, MLME 16, HB-Count 1
[28595.580335] wlan: [27367:E :SME] sme_QosPmcDeviceStateUpdateInd: 7219: nothing to process in PMC state 6
[28595.580671] wlan: [27367:E :TL ] ----> CRegion 1, hRSSI -79, Alpha 5
[28600.103546] wlan: [27367:E :PE ] limDeactivateAndChangeTimer: 1438: Deactivated probe after hb timer
[28600.146610] wlan: [27367:E :PE ] limHandleHeartBeatFailureTimeout: 7199: Probe_hb_failure: SME 12, MLME 16, HB-Count 1
[28600.485112] wlan: [27367:E :TL ] Current Region number is 0, cannot decrease anymore
[28600.485325] wlan: [27367:E :TL ] ----> CRegion 0, hRSSI -79, Alpha 5
[28600.485783] wlan: [27367:E :TL ] ----> CRegion 0, hRSSI -79, Alpha 5
[28600.486058] wlan: [27367:E :TL ] ----> CRegion 1, hRSSI -79, Alpha 5
[28600.486546] wlan: [27367:E :TL ] ----> CRegion 1, hRSSI -79, Alpha 5
[28600.487065] wlan: [27367:E :TL ] ----> CRegion 0, hRSSI -79, Alpha 5
[28600.487309] wlan: [27367:E :TL ] ----> CRegion 0, hRSSI -79, Alpha 5
[28600.487767] wlan: [27367:E :TL ] ----> CRegion 1, hRSSI -79, Alpha 5
[28600.488011] wlan: [27367:E :TL ] ----> CRegion 1, hRSSI -79, Alpha 5
[28600.733212] wlan: [27367:E :SME] csrNeighborRoamPrepareScanProfileFilter: 1197: Filtering for SSID ******** from scan results,length of SSID = 11
[28600.733792] wlan: [27367:E :SME] csrNeighborRoamProcessScanComplete: 1867: No candidate found after scanning in state 3..
[28600.734250] wlan: [27367:E :SME] csrNeighborRoamHandleEmptyScanResult: 1669: Registering DOWN event neighbor lookup callback with TL for RSSI = -79
[28600.973071] wlan: [27367:E :SME] csrNeighborRoamPrepareScanProfileFilter: 1197: Filtering for SSID ******** from scan results,length of SSID = 11
[28600.973651] wlan: [27367:E :SME] csrNeighborRoamProcessScanComplete: 1867: No candidate found after scanning in state 3..
[28601.110993] wlan: [27367:E :SME] sme_QosPmcDeviceStateUpdateInd: 7219: nothing to process in PMC state 6
[28601.716670] adjust_soc: ibat_ua = 192800, vbat_uv = 3831619, soc = 57, batt_temp=238
[28604.752989] wlan: [27367:E :SME] csrNeighborRoamPrepareScanProfileFilter: 1197: Filtering for SSID ******** from scan results,length of SSID = 11
[28604.753416] wlan: [27367:E :SME] csrNeighborRoamProcessScanComplete: 1797: Get Scan Result status code 39
[28604.753783] wlan: [27367:E :SME] csrNeighborRoamProcessScanComplete: 1867: No candidate found after scanning in state 3..
[28605.301928] healthd: battery l=57 v=3834 t=23.8 h=2 st=3 c=226 chg=
[28618.545023] wlan: [27367:E :PE ] limDeactivateAndChangeTimer: 1438: Deactivated probe after hb timer
[28618.586592] wlan: [27367:E :PE ] limHandleHeartBeatFailureTimeout: 7199: Probe_hb_failure: SME 12, MLME 16, HB-Count 1
[28619.313984] healthd: battery l=57 v=3824 t=23.8 h=2 st=3 c=272 chg=
[28619.540384] wlan: [27367:E :SME] sme_QosPmcDeviceStateUpdateInd: 7219: nothing to process in PMC state 6
[28622.376642] adjust_soc: ibat_ua = 215400, vbat_uv = 3826353, soc = 57, batt_temp=238
[28624.991872] wlan: [27367:E :PE ] limDeactivateAndChangeTimer: 1438: Deactivated probe after hb timer
[28625.026543] wlan: [27367:E :PE ] limHandleHeartBeatFailureTimeout: 7199: Probe_hb_failure: SME 12, MLME 16, HB-Count 1
[28625.990224] wlan: [27367:E :SME] sme_QosPmcDeviceStateUpdateInd: 7219: nothing to process in PMC state 6
[28633.291887] wlan: [27367:E :PE ] limDeactivateAndChangeTimer: 1438: Deactivated probe after hb timer
[28633.336447] wlan: [27367:E :PE ] limHandleHeartBeatFailureTimeout: 7199: Probe_hb_failure: SME 12, MLME 16, HB-Count 1
[28634.300067] wlan: [27367:E :SME] sme_QosPmcDeviceStateUpdateInd: 7219: nothing to process in PMC state 6
[28650.799227] wlan: [27367:E :PE ] limDeactivateAndChangeTimer: 1438: Deactivated probe after hb timer
[28650.846534] wlan: [27367:E :PE ] limHandleHeartBeatFailureTimeout: 7199: Probe_hb_failure: SME 12, MLME 16, HB-Count 1
[28651.800143] wlan: [27367:E :SME] sme_QosPmcDeviceStateUpdateInd: 7219: nothing to process in PMC state 6
No errors detected
Boot info:
Last boot reason: watchdog
I once did some kernel hacking on a Samsung phone, but I'm no pro and do not really know what the log is telling me. Can anybody who know's have a look and help identify the problem? Any help is greatly appreciated - this bug is really bugging me!
(sorry for pun)
I had the same problem on stock L ... CM12.1 solved it
Envoyé de mon Nexus 4 en utilisant Tapatalk
Check on off switch in Mobile phone
Andr006 said:
I had the same problem on stock L ... CM12.1 solved it
Click to expand...
Click to collapse
I'm keeping that in mind. If Google doesn't fix this until christmas, I may switch to CM.
kamleshmore said:
Check on off switch in Mobile phone
Click to expand...
Click to collapse
Thanks. The switch is fine.
Another reboot the other morning after midnight (time stamp is UTC, don't get confused). It's the second time the phone rebooted just minutes after I put it down to go to sleep. kmsg:
Code:
[61553.727499] active wake lock qcom_rx_wakelock, time left 4
[61553.727560] suspend: abort suspend
[61553.762933] wake lock qcom_rx_wakelock, expired
[61553.763849] suspend: enter suspend
[61553.763879] PM: Syncing filesystems...
[61553.764306] PM: suspend entry 2015-10-18 22:17:29.043910320 UTC
[61553.783382] sync done.
[61553.783626] PM: Syncing filesystems...
[61553.802732] sync done.
[61553.823119] Freezing user space processes ... (elapsed 0.004 seconds) done.
[61553.828521] Freezing remaining freezable tasks ... (elapsed 0.006 seconds) done.
[61553.836335] Suspending console(s) (use no_console_suspend to debug)
[61553.847047] msm_fb_ext_suspend: Turning off HPD circuitry
[61553.865054] PM: suspend of devices complete after 24.825 msecs
[61553.866824] PM: late suspend of devices complete after 1.738 msecs
[61553.870334] power_suspend_late return 0
[61553.870365] PM: noirq suspend of devices complete after 3.537 msecs
[61553.870395] Disabling non-boot CPUs ...
[61553.877720] msm_pm_enter
[61553.877720] msm_pm_enter: power collapse
[61553.877720] msm_mpm_irqs_detectable: cannot monitor 000000,00000000,00000000,00000000,00000000,00000020,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000
[61553.877720] msm_pm_enter: return
[61553.877720] gic_show_resume_irq: 234 triggered
[61553.877720] Resume caused by IRQ 234, wcnss_wlan
[61553.878239] Enabling non-boot CPUs ...
[61553.882054] CPU1 is up
[61553.885015] PM: noirq resume of devices complete after 2.897 msecs
[61553.889013] PM: early resume of devices complete after 1.677 msecs
[61553.891210] wakeup wake lock: qcom_rx_wakelock
[61553.894415] msm_fb_ext_resume: Turning on HPD circuitry
[61553.899725] PM: resume of devices complete after 10.643 msecs
[61553.902198] Restarting tasks ... done.
[61553.904761] PM: suspend exit 2015-10-18 22:19:09.009362002 UTC
[61553.904975] suspend: exit suspend, ret = 0 (2015-10-18 22:19:09.009544973 UTC)
[61553.905311] active wake lock qcom_rx_wakelock, time left 3
[61553.905494] suspend: abort suspend
[61557.938914] suspend: enter suspend
[61557.939249] PM: suspend entry 2015-10-18 22:19:13.043177926 UTC
[61557.939493] PM: Syncing filesystems...
[61557.956310] sync done.
[61557.958111] Freezing user space processes ... (elapsed 0.002 seconds) done.
[61557.960644] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[61557.962811] Suspending console(s) (use no_console_suspend to debug)
[61557.966718] msm_fb_ext_suspend: Turning off HPD circuitry
[61557.976698] PM: suspend of devices complete after 12.391 msecs
[61557.977308] PM: late suspend of devices complete after 0.610 msecs
[61557.978559] active wake lock alarm, time left 498
[61557.978559] power_suspend_late return -11
[61557.978559] dpm_run_callback(): power_suspend_late+0x0/0x58 returns -11
[61557.978559] PM: Device power.0 failed to suspend noirq: error -11
[61557.979445] PM: noirq resume of devices complete after 0.854 msecs
[61557.980849] PM: early suspend of devices complete after 0.579 msecs
[61557.980879] PM: Some devices failed to power down
[61557.982283] msm_fb_ext_resume: Turning on HPD circuitry
[61557.983626] PM: resume of devices complete after 2.746 msecs
[61557.985701] Restarting tasks ... done.
[61557.987380] PM: suspend exit 2015-10-18 22:19:13.091308448 UTC
[61557.987471] suspend: exit suspend, ret = -11 (2015-10-18 22:19:13.091369488 UTC)
[61557.987563] suspend: enter suspend
[61557.987624] PM: suspend entry 2015-10-18 22:19:13.091552610 UTC
[61557.987838] PM: Syncing filesystems...
[61557.994186] sync done.
[61558.037952] Freezing user space processes ... (elapsed 0.002 seconds) done.
[61558.040424] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[61558.042500] Suspending console(s) (use no_console_suspend to debug)
[61558.045674] msm_fb_ext_suspend: Turning off HPD circuitry
[61558.053853] PM: suspend of devices complete after 10.102 msecs
[61558.054464] PM: late suspend of devices complete after 0.610 msecs
[61558.055684] active wake lock alarm, time left 498
[61558.055715] power_suspend_late return -11
[61558.055715] dpm_run_callback(): power_suspend_late+0x0/0x58 returns -11
[61558.055715] PM: Device power.0 failed to suspend noirq: error -11
[61558.056600] PM: noirq resume of devices complete after 0.885 msecs
[61558.057974] PM: early suspend of devices complete after 0.579 msecs
[61558.058004] PM: Some devices failed to power down
[61558.059835] msm_fb_ext_resume: Turning on HPD circuitry
[61558.061087] PM: resume of devices complete after 3.082 msecs
[61558.063101] Restarting tasks ... done.
[61558.064993] PM: suspend exit 2015-10-18 22:19:13.168891081 UTC
[61558.065085] suspend: exit suspend, ret = -11 (2015-10-18 22:19:13.169013162 UTC)
[61558.065207] active wake lock alarm, time left 500
[61558.065268] suspend: abort suspend
[61559.177766] healthd: battery l=37 v=3757 t=23.8 h=2 st=3 c=226 chg=
[61575.933969] adjust_soc: ibat_ua = 223800, vbat_uv = 3751488, soc = 38, batt_temp=237
[61593.110011] healthd: battery l=37 v=3757 t=23.7 h=2 st=3 c=221 chg=
[61600.413963] adjust_soc: ibat_ua = 195600, vbat_uv = 3751198, soc = 38, batt_temp=238
[61603.041035] healthd: battery l=37 v=3750 t=23.7 h=2 st=3 c=269 chg=
[61613.739097] healthd: battery l=37 v=3765 t=23.8 h=2 st=3 c=170 chg=
[61619.180116] healthd: battery l=37 v=3755 t=23.8 h=2 st=3 c=235 chg=
[61621.113948] adjust_soc: ibat_ua = 222100, vbat_uv = 3746501, soc = 38, batt_temp=238
[61623.379017] active wake lock alarm, time left 500
[61623.379353] suspend: abort suspend
[61623.379536] active wake lock alarm, time left 500
[61623.379719] suspend: abort suspend
[61623.380024] active wake lock alarm, time left 500
[61623.380208] suspend: abort suspend
[61623.380391] active wake lock alarm, time left 500
[61623.380726] suspend: abort suspend
[61623.380910] active wake lock alarm, time left 500
[61623.381093] suspend: abort suspend
[61623.381398] active wake lock alarm, time left 500
[61623.381581] suspend: abort suspend
[61623.381764] active wake lock alarm, time left 500
[61623.382100] suspend: abort suspend
[61624.061544] healthd: battery l=37 v=3753 t=23.8 h=2 st=3 c=228 chg=
[61634.042347] healthd: battery l=37 v=3753 t=23.8 h=2 st=3 c=230 chg=
[61641.073875] adjust_soc: ibat_ua = 221000, vbat_uv = 3745324, soc = 38, batt_temp=238
[61644.042378] healthd: battery l=37 v=3752 t=23.8 h=2 st=3 c=236 chg=
[61654.041462] healthd: battery l=37 v=3751 t=23.8 h=2 st=3 c=235 chg=
[61662.574104] adjust_soc: ibat_ua = 222800, vbat_uv = 3745621, soc = 38, batt_temp=238
[61663.551763] active wake lock alarm, time left 500
[61663.551824] suspend: abort suspend
[61663.552007] active wake lock alarm, time left 500
[61663.552129] suspend: abort suspend
[61663.552220] suspend: enter suspend
[61663.552281] PM: suspend entry 2015-10-18 22:20:58.656208663 UTC
[61663.552404] PM: Syncing filesystems...
[61663.569434] sync done.
[61663.569648] Freezing user space processes ... (elapsed 0.002 seconds) done.
[61663.572059] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[61663.574195] Suspending console(s) (use no_console_suspend to debug)
[61663.578071] msm_fb_ext_suspend: Turning off HPD circuitry
[61663.592812] PM: suspend of devices complete after 17.182 msecs
[61663.593423] PM: late suspend of devices complete after 0.610 msecs
[61663.594796] active wake lock alarm, time left 497
[61663.594796] power_suspend_late return -11
[61663.594827] dpm_run_callback(): power_suspend_late+0x0/0x58 returns -11
[61663.594827] PM: Device power.0 failed to suspend noirq: error -11
[61663.595681] PM: noirq resume of devices complete after 0.854 msecs
[61663.597085] PM: early suspend of devices complete after 0.579 msecs
[61663.597085] PM: Some devices failed to power down
[61663.598947] msm_fb_ext_resume: Turning on HPD circuitry
[61663.600229] PM: resume of devices complete after 3.143 msecs
[61663.602213] Restarting tasks ... done.
[61663.604166] PM: suspend exit 2015-10-18 22:20:59.004944301 UTC
[61663.604227] suspend: exit suspend, ret = -11 (2015-10-18 22:20:59.005005342 UTC)
[61663.604715] active wake lock alarm, time left 500
[61663.604776] suspend: abort suspend
[61663.604838] active wake lock alarm, time left 500
[61663.604960] suspend: abort suspend
[61663.605021] active wake lock alarm, time left 500
[61663.605112] suspend: abort suspend
[61663.605173] active wake lock alarm, time left 500
[61663.605234] suspend: abort suspend
[61663.605356] suspend: enter suspend
[61663.605417] PM: suspend entry 2015-10-18 22:20:59.006165116 UTC
[61663.605570] PM: Syncing filesystems...
[61663.611369] sync done.
[61663.659866] Freezing user space processes ... (elapsed 0.002 seconds) done.
[61663.662277] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[61663.664261] Suspending console(s) (use no_console_suspend to debug)
[61663.667496] msm_fb_ext_suspend: Turning off HPD circuitry
[61663.675645] PM: suspend of devices complete after 10.094 msecs
[61663.676133] PM: late suspend of devices complete after 0.487 msecs
[61663.677201] active wake lock alarm, time left 498
[61663.677201] power_suspend_late return -11
[61663.677232] dpm_run_callback(): power_suspend_late+0x0/0x58 returns -11
[61663.677232] PM: Device power.0 failed to suspend noirq: error -11
[61663.677995] PM: noirq resume of devices complete after 0.762 msecs
[61663.679216] PM: early suspend of devices complete after 0.457 msecs
[61663.679216] PM: Some devices failed to power down
[61663.680864] msm_fb_ext_resume: Turning on HPD circuitry
[61663.682115] PM: resume of devices complete after 2.897 msecs
[61663.684160] Restarting tasks ... done.
[61663.685717] PM: suspend exit 2015-10-18 22:20:59.086407693 UTC
[61663.685808] suspend: exit suspend, ret = -11 (2015-10-18 22:20:59.086529688 UTC)
[61663.685869] active wake lock alarm, time left 500
[61663.685991] suspend: abort suspend
[61679.179048] healthd: battery l=37 v=3750 t=23.8 h=2 st=3 c=232 chg=
[61690.264657] adjust_soc: ibat_ua = 218200, vbat_uv = 3744153, soc = 38, batt_temp=237
[61743.104761] adjust_soc: ibat_ua = 253100, vbat_uv = 3736228, soc = 38, batt_temp=238
[61743.105219] healthd: battery l=37 v=3736 t=23.8 h=2 st=3 c=253 chg=
[61743.122005] healthd: battery l=37 v=3742 t=23.8 h=2 st=3 c=259 chg=
[61743.135678] healthd: battery l=37 v=3741 t=23.7 h=2 st=3 c=247 chg=
[61743.154509] healthd: battery l=37 v=3743 t=23.7 h=2 st=3 c=197 chg=
No errors detected
Boot info:
Last boot reason: watchdog
I had many Reboots too on my N4 with Lollipop, complete Stock and with a Custom Kernel.
But after changing my CPU Governor from ondemand to conservative the Reboots are gone.