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?
Hi All,
I would have posted in the developer forum under one of the CM7 threads but this is my first post on xda so here it goes:
I've been following the developer forums for a while now and I too am plagued with the wonks on my N1 with CM7. For me the wonkiness = phone not being responsive with black screen and no audio when making a phone call, then after about 15 to 25 seconds the screen shows the call and audio is back on).
This is understandable since it's still in an alpha state not ready for production so I wanted to post my logcat (running build 27) snapshot (attached) to see if it will help some developer figure out how to fix the wonk of terror.
Here's how I reproduce the wonk:
I turn my N1 on and as soon as it boots up I press the power button to shut the screen off. After about 2 to 3 minutes I press the power button, unlock my phone and try to make a call. I am guaranteed a wonk every time.
My temporary fix is the CM7 Dewonkificator Add-on. It definitely fixes my N1's wonkiness problem for the time being.
Thanks for listening!
markhm1978 said:
Hi All,
I would have posted in the developer forum under one of the CM7 threads but this is my first post on xda so here it goes:
I've been following the developer forums for a while now and I too am plagued with the wonks on my N1 with CM7. For me the wonkiness = phone not being responsive with black screen and no audio when making a phone call, then after about 15 to 25 seconds the screen shows the call and audio is back on).
This is understandable since it's still in an alpha state not ready for production so I wanted to post my logcat (running build 27) snapshot (attached) to see if it will help some developer figure out how to fix the wonk of terror.
Here's how I reproduce the wonk:
I turn my N1 on and as soon as it boots up I press the power button to shut the screen off. After about 2 to 3 minutes I press the power button, unlock my phone and try to make a call. I am guaranteed a wonk every time.
My temporary fix is the CM7 Dewonkificator Add-on. It definitely fixes my N1's wonkiness problem for the time being.
Thanks for listening!
Click to expand...
Click to collapse
If I'm not mistaken, CM has noted the source of the error (mic) and they are conjuring up a fix. It should most likely be ready to go in one of the next few nightlies.
Thanks! Didn't happen to come across that piece of information in my travels on xda forums.
markhm1978 said:
Thanks! Didn't happen to come across that piece of information in my travels on xda forums.
Click to expand...
Click to collapse
You must've taken a right instead of a left...
rickytenzer said:
If I'm not mistaken, CM has noted the source of the error (mic) and they are conjuring up a fix. It should most likely be ready to go in one of the next few nightlies.
Click to expand...
Click to collapse
That first attempt fix was released in build 27 earlier today.
Unfortunately some peoples are still reporting the call wonkiness.
rickytenzer said:
You must've taken a right instead of a left...
Click to expand...
Click to collapse
Yeah, it's pretty easy to get lost in all of the chocolaty goodness here.
baseballfanz said:
That first attempt fix was released in build 27 earlier today.
Unfortunately some peoples are still reporting the call wonkiness.
Click to expand...
Click to collapse
Thanks for the info. I am one of the unfortunate ones.
Just tried Build 28 and the phone call still wonks out. logcat snapshot attached.
Call Wonks for me on Build 29. Dewonkificator is still working as a temporary fix.
It's been hit or miss with me - no wonks until I think build 17 and then twenty-something...
It's still worth it - you get wonks in brand new phones sometimes and the solution isn't likely contained in a flash update within another 24 hours!
I will suffer the pain of wonkiness until it is finally solved by those brilliant minds working away on polishing this gorgeous CM7 port. Thank you - your efforts are REALLY appreciated here
should post this on the cyan forums if u havent already, im sure they could use it if it actually works.
Basil 123 said:
It's been hit or miss with me - no wonks until I think build 17 and then twenty-something...
It's still worth it - you get wonks in brand new phones sometimes and the solution isn't likely contained in a flash update within another 24 hours!
I will suffer the pain of wonkiness until it is finally solved by those brilliant minds working away on polishing this gorgeous CM7 port. Thank you - your efforts are REALLY appreciated here
Click to expand...
Click to collapse
I too love the CM7 port! So much that I'm about to donate $20 to buy Cyanogen some beer.
I figured instead of *****ing about how my phone calls are wonking out, I'd post some info to try and help with the situation and keep track of any wonks per build in this thread.
Have you tried Dewonkificator yet? It works really well for me. Here's the link: http://forum.xda-developers.com/showthread.php?t=935250
Buck Shot said:
should post this on the cyan forums if u havent already, im sure they could use it if it actually works.
Click to expand...
Click to collapse
I am creating an account on the Cyan forums now and will post a link to this thread.
Thanks for the suggestion.
Build 30, Wonks for me. Dewonkificator still working as a temp fix.
rickytenzer said:
You must've taken a right instead of a left...
Click to expand...
Click to collapse
lol you should have said: Sorry, but our princess is in another castle.
logcats are only half, posting dmesg's would be more helpful if any dev was going to check out your logs.
fitsnugly said:
lol you should have said: Sorry, but our princess is in another castle.
logcats are only half, posting dmesg's would be more helpful if any dev was going to check out your logs.
Click to expand...
Click to collapse
Thanks! I will look in to how to capture the dmesg's. While I look, do you have any suggestions for capturing this info?
fitsnugly said:
lol you should have said: Sorry, but our princess is in another castle.
logcats are only half, posting dmesg's would be more helpful if any dev was going to check out your logs.
Click to expand...
Click to collapse
Okay, figured it out. Attached the dmesg of my Wonkiness for Build 30.
Hi. I am on #31. The wonky is still here. dmesg output attached.
View attachment 2011-02-04-04.txt
I suppose this is a log of the wonky call:
Code:
<6>[ 644.924621] request_suspend_state: wakeup (3->0) at 640894655059 (2011-02-04 07:41:27.847267217 UTC)
<6>[ 644.927429] lcdc_resume: resuming
<6>[ 644.951568] mahimahi_ts_power: power 1
<6>[ 644.989440] lcdc_unblank: ()
<6>[ 644.990478] samsung_oled_panel_unblank: +()
<6>[ 645.281188] samsung_oled_panel_unblank: -()
<6>[ 648.953430] pcm_out: open
<6>[ 648.953918] acdb: 588 bytes for device 607, rate 48000.
<6>[ 650.724761] a1026_set_config: change to mode 1
<6>[ 650.724975] a1026_set_config: block write start (size = 56)
<6>[ 650.730865] a1026_set_config: block write end
<6>[ 650.755981] a1026_set_config: CMD ACK block read start
<3>[ 653.738586] msm_i2c msm_i2c.0: Error waiting for notbusy (0)
<3>[ 653.739074] msm_i2c msm_i2c.0: Transaction timed out
<3>[ 653.739868] msm_i2c msm_i2c.0: Error during data xfer 3e (-110)
<4>[ 653.740448] msm_i2c msm_i2c.0: Still the bus master, status 9b00, intf 0
<4>[ 653.741271] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 1
<4>[ 653.918853] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 653.919738] a1026_i2c_read: transfer error -110
<3>[ 653.920166] a1026_set_config: CMD ACK block read error
<6>[ 653.920928] a1026_i2c_sw_reset: 80020000
<3>[ 655.900756] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 655.901336] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 655.902130] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 656.080993] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 656.081573] a1026_i2c_write: transfer error -16
<3>[ 656.082000] a1026_ioctl: A1026_SET_CONFIG (1) error -110!
<6>[ 656.082824] a1026_set_config: change to mode 1
<6>[ 656.083282] a1026_set_config: block write start (size = 56)
<3>[ 658.063629] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 658.064239] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 658.065032] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 658.243072] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 658.243927] a1026_i2c_write: transfer error -16
<3>[ 658.244384] A1026 CMD block write error!
<6>[ 658.245117] a1026_i2c_sw_reset: 80020000
<3>[ 660.224914] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 660.225830] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 660.226318] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 660.405181] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 660.405761] a1026_i2c_write: transfer error -16
<3>[ 660.406524] a1026_ioctl: A1026_SET_CONFIG (1) error -16!
<6>[ 660.407012] a1026_set_config: change to mode 1
<6>[ 660.407440] a1026_set_config: block write start (size = 56)
<3>[ 662.387023] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 662.387634] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 662.388427] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 662.567291] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 662.568206] a1026_i2c_write: transfer error -16
<3>[ 662.568634] A1026 CMD block write error!
<6>[ 662.569427] a1026_i2c_sw_reset: 80020000
<3>[ 664.549560] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 664.550476] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 664.550964] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 664.729370] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 664.729919] a1026_i2c_write: transfer error -16
<3>[ 664.730712] a1026_ioctl: A1026_SET_CONFIG (1) error -16!
<6>[ 664.731170] a1026_set_config: change to mode 1
<6>[ 664.731628] a1026_set_config: block write start (size = 56)
<3>[ 666.721221] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 666.721801] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 666.722625] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 666.901550] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 666.902435] a1026_i2c_write: transfer error -16
<3>[ 666.902862] A1026 CMD block write error!
<6>[ 666.903656] a1026_i2c_sw_reset: 80020000
<3>[ 668.883361] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 668.884277] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 668.884765] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 669.063629] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 669.064178] a1026_i2c_write: transfer error -16
<3>[ 669.064941] a1026_ioctl: A1026_SET_CONFIG (1) error -16!
<3>[ 669.067352] msm_i2c msm_i2c.0: IRQ but nothing to do!, status 8302
<4>[ 669.083496] msm_i2c msm_i2c.0: Warning bus was busy (102)
<4>[ 669.085998] msm_i2c msm_i2c.0: 1 unrequested bytes read
<6>[ 669.127288] a1026_bootup_init: starting to load image (863 passes)...
<6>[ 672.336761] a1026_bootup_init: firmware loaded successfully
<6>[ 672.341888] batt: 54%, 3791 mV, -277 mA (-246 avg), 30.3 C, 728 mAh
<6>[ 672.497192] a1026_bootup_init: initialized!
<6>[ 672.658020] a1026_set_config: change to mode 1
<6>[ 672.658477] a1026_set_config: block write start (size = 56)
<6>[ 672.664947] a1026_set_config: block write end
<6>[ 672.687408] a1026_set_config: CMD ACK block read start
<6>[ 672.693542] a1026_set_config: CMD ACK block read end
<6>[ 672.747741] acdb: 974 bytes for device 2, rate 48000.
<6>[ 672.909057] acdb: 819 bytes for device 1, rate 8000.
<6>[ 673.097686] capella_cm3602_open
<6>[ 673.097869] capella_cm3602_ioctl cmd 2
<6>[ 673.098022] capella_cm3602_enable
<6>[ 673.098175] proximity 1
<6>[ 673.121124] request_suspend_state: wakeup (0->0) at 669063729306 (2011-02-04 07:41:56.016341464 UTC)
<6>[ 682.863403] capella_cm3602_ioctl cmd 2
<6>[ 682.863739] capella_cm3602_disable
<6>[ 682.864044] capella_cm3602_release
<6>[ 682.864349] capella_cm3602_disable
<6>[ 682.864868] capella_cm3602_disable: already disabled
<6>[ 682.874908] a1026_set_config: change to mode 13
<6>[ 682.875457] a1026_set_config: block write start (size = 16)
<6>[ 682.877563] a1026_set_config: block write end
<6>[ 682.907012] a1026_set_config: CMD ACK block read start
<6>[ 682.908966] a1026_set_config: CMD ACK block read end
<6>[ 682.909271] acdb: 871 bytes for device 507, rate 8000.
<6>[ 685.739837] pcm_out: release
PS @markhm1978
Compared your dmesg output with mine. It is quite the same...
dolphin77 said:
Hi. I am on #31. The wonky is still here. dmesg output attached.
View attachment 508500
I suppose this is a log of the wonky call:
Code:
<6>[ 644.924621] request_suspend_state: wakeup (3->0) at 640894655059 (2011-02-04 07:41:27.847267217 UTC)
<6>[ 644.927429] lcdc_resume: resuming
<6>[ 644.951568] mahimahi_ts_power: power 1
<6>[ 644.989440] lcdc_unblank: ()
<6>[ 644.990478] samsung_oled_panel_unblank: +()
<6>[ 645.281188] samsung_oled_panel_unblank: -()
<6>[ 648.953430] pcm_out: open
<6>[ 648.953918] acdb: 588 bytes for device 607, rate 48000.
<6>[ 650.724761] a1026_set_config: change to mode 1
<6>[ 650.724975] a1026_set_config: block write start (size = 56)
<6>[ 650.730865] a1026_set_config: block write end
<6>[ 650.755981] a1026_set_config: CMD ACK block read start
<3>[ 653.738586] msm_i2c msm_i2c.0: Error waiting for notbusy (0)
<3>[ 653.739074] msm_i2c msm_i2c.0: Transaction timed out
<3>[ 653.739868] msm_i2c msm_i2c.0: Error during data xfer 3e (-110)
<4>[ 653.740448] msm_i2c msm_i2c.0: Still the bus master, status 9b00, intf 0
<4>[ 653.741271] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 1
<4>[ 653.918853] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 653.919738] a1026_i2c_read: transfer error -110
<3>[ 653.920166] a1026_set_config: CMD ACK block read error
<6>[ 653.920928] a1026_i2c_sw_reset: 80020000
<3>[ 655.900756] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 655.901336] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 655.902130] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 656.080993] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 656.081573] a1026_i2c_write: transfer error -16
<3>[ 656.082000] a1026_ioctl: A1026_SET_CONFIG (1) error -110!
<6>[ 656.082824] a1026_set_config: change to mode 1
<6>[ 656.083282] a1026_set_config: block write start (size = 56)
<3>[ 658.063629] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 658.064239] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 658.065032] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 658.243072] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 658.243927] a1026_i2c_write: transfer error -16
<3>[ 658.244384] A1026 CMD block write error!
<6>[ 658.245117] a1026_i2c_sw_reset: 80020000
<3>[ 660.224914] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 660.225830] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 660.226318] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 660.405181] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 660.405761] a1026_i2c_write: transfer error -16
<3>[ 660.406524] a1026_ioctl: A1026_SET_CONFIG (1) error -16!
<6>[ 660.407012] a1026_set_config: change to mode 1
<6>[ 660.407440] a1026_set_config: block write start (size = 56)
<3>[ 662.387023] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 662.387634] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 662.388427] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 662.567291] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 662.568206] a1026_i2c_write: transfer error -16
<3>[ 662.568634] A1026 CMD block write error!
<6>[ 662.569427] a1026_i2c_sw_reset: 80020000
<3>[ 664.549560] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 664.550476] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 664.550964] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 664.729370] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 664.729919] a1026_i2c_write: transfer error -16
<3>[ 664.730712] a1026_ioctl: A1026_SET_CONFIG (1) error -16!
<6>[ 664.731170] a1026_set_config: change to mode 1
<6>[ 664.731628] a1026_set_config: block write start (size = 56)
<3>[ 666.721221] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 666.721801] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 666.722625] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 666.901550] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 666.902435] a1026_i2c_write: transfer error -16
<3>[ 666.902862] A1026 CMD block write error!
<6>[ 666.903656] a1026_i2c_sw_reset: 80020000
<3>[ 668.883361] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 668.884277] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 668.884765] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 669.063629] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 669.064178] a1026_i2c_write: transfer error -16
<3>[ 669.064941] a1026_ioctl: A1026_SET_CONFIG (1) error -16!
<3>[ 669.067352] msm_i2c msm_i2c.0: IRQ but nothing to do!, status 8302
<4>[ 669.083496] msm_i2c msm_i2c.0: Warning bus was busy (102)
<4>[ 669.085998] msm_i2c msm_i2c.0: 1 unrequested bytes read
<6>[ 669.127288] a1026_bootup_init: starting to load image (863 passes)...
<6>[ 672.336761] a1026_bootup_init: firmware loaded successfully
<6>[ 672.341888] batt: 54%, 3791 mV, -277 mA (-246 avg), 30.3 C, 728 mAh
<6>[ 672.497192] a1026_bootup_init: initialized!
<6>[ 672.658020] a1026_set_config: change to mode 1
<6>[ 672.658477] a1026_set_config: block write start (size = 56)
<6>[ 672.664947] a1026_set_config: block write end
<6>[ 672.687408] a1026_set_config: CMD ACK block read start
<6>[ 672.693542] a1026_set_config: CMD ACK block read end
<6>[ 672.747741] acdb: 974 bytes for device 2, rate 48000.
<6>[ 672.909057] acdb: 819 bytes for device 1, rate 8000.
<6>[ 673.097686] capella_cm3602_open
<6>[ 673.097869] capella_cm3602_ioctl cmd 2
<6>[ 673.098022] capella_cm3602_enable
<6>[ 673.098175] proximity 1
<6>[ 673.121124] request_suspend_state: wakeup (0->0) at 669063729306 (2011-02-04 07:41:56.016341464 UTC)
<6>[ 682.863403] capella_cm3602_ioctl cmd 2
<6>[ 682.863739] capella_cm3602_disable
<6>[ 682.864044] capella_cm3602_release
<6>[ 682.864349] capella_cm3602_disable
<6>[ 682.864868] capella_cm3602_disable: already disabled
<6>[ 682.874908] a1026_set_config: change to mode 13
<6>[ 682.875457] a1026_set_config: block write start (size = 16)
<6>[ 682.877563] a1026_set_config: block write end
<6>[ 682.907012] a1026_set_config: CMD ACK block read start
<6>[ 682.908966] a1026_set_config: CMD ACK block read end
<6>[ 682.909271] acdb: 871 bytes for device 507, rate 8000.
<6>[ 685.739837] pcm_out: release
PS @markhm1978
Compared your dmesg output with mine. It is quite the same...
Click to expand...
Click to collapse
It is quite the same. I am on 31 also, still experiencing the Wonkiness. Will post more logs when 32 hits.
Wonks for me on Build 32. Dewonkificator still working as a temporary fix: http://forum.xda-developers.com/showthread.php?t=935250
i have report the problem to syiahkernels author and i want to discuss this issue here.
according my experience, every kernel published recently lose the bluetooth hid support, they are all about 6~7 mb,and my zckj1 cfroot is 8mb ,working well with bt keyboard.
so ihope the developer solve this problem. thanks
here is the kernel msg by cmd dmesg
1. dmesg from XWKJ3 CF Kernel(HID doesnt work)
[ 880.984918] mmc_do_discard_ops(475): receive discard start(1683376), len(48) [ 881.436692] mmc_do_discard_ops(475): receive discard start(5099520), len(48) [ 881.796870] ######## bthid_open: ######## [ 881.796893] ######## bthid_open: done ######## [ 881.911969] cpu1 turning on! [ 881.911993] >made stopper [ 881.976460] bthid_write: Oops, HID report descriptor not configured [ 881.976607] ######## bthid_ioctl: cmd = 5 ######## [ 881.976630] ######## bthid_release: ######## [ 881.976641] ######## bthid_release: done ######## [ 882.150897] CPU1: Booted secondary processor
2.dmesg from ZCKJ1 CF kernel (HID supported)
<4>[ 88.851353] ######## bthid_open: ######## <4>[ 88.851403] ######## bthid_open: done ######## <4>[ 88.878610] bthid_write: Oops, HID report descriptor not configured <4>[ 88.879213] ######## bthid_ioctl: cmd = 5 ######## <4>[ 88.879258] command is not BTHID_IOCTL_RPT_DSCP. return######## bthid_ioct l: cmd = 3 ######## <4>[ 88.879414] command is not BTHID_IOCTL_RPT_DSCP. return######## bthid_ioct l: cmd = 1 ######## <4>[ 88.898847] ######## bthid_ll_parse: hid = e252b000 ######## <4>[ 88.904472] ######## bthid_ll_parse: status = 0, ret = 0 ######## <4>[ 88.904549] ######## bthid_ll_start: hid = e252b000 ######## <6>[ 88.909026] input: Broadcom Bluetooth HID as /devices/virtual/input/input9 <4>[ 88.909150] ######## bthid_ll_open: hid = e252b000 ######## <6>[ 88.916108] generic-bluetooth 0005:0000:0000.0001: input: BLUETOOTH HID v0 .00 Keyboard [Broadcom Bluetooth HID] on <4>[ 88.916224] hid_add_device: ret = 0, hid->status = 3 <4>[ 88.916265] ######## bthid_ioctl: done ########
Sent from my GT-I9100 using XDA App
maybe someone here can replace the extra part in zckj1 to the popular kernels?
Sent from my GT-I9100 using XDA App
Compare modules of both kernels (/lib/modules), especially bthid.ko
thanks alot ，
Sent from my GT-I9100 using XDA App
Did you solve the problem? I have the same issues with xwkj3 cf kernel. Is it just replacing the bthid.ko? If so, were to get it from?
Thanks in advance.
efzwo
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,
I bought a second hand i9505, which i used for several days with the standard Samsung stuff.
After a few day's i installed CM11, but after a day my wifi stopped working.
Then i started googling, found several other treads with the same problem, tried those solutions.
But at the this point none of them worked for me.
Things that i tried:
-Different modems
-Stock Samsung rom
-Factory reset
-Format /system , and reflash stock rom with Odin
-Pull the battery out for 30mins
-Reconnected the Wifi antenna
-Deleted the WPA_Supplicant file
-Disable the powersaving mode under *#0011#
Al of them did not work for me.
Is there anybody who has an idea?
Thanks in advance!
sven93 said:
Hi,
I bought a second hand i9505, which i used for several days with the standard Samsung stuff.
After a few day's i installed CM11, but after a day my wifi stopped working.
Then i started googling, found several other treads with the same problem, tried those solutions.
But at the this point none of them worked for me.
Things that i tried:
-Different modems
-Stock Samsung rom
-Factory reset
-Format /system , and reflash stock rom with Odin
-Pull the battery out for 30mins
-Reconnected the Wifi antenna
-Deleted the WPA_Supplicant file
-Disable the powersaving mode under *#0011#
Al of them did not work for me.
Is there anybody who has an idea?
Thanks in advance!
Click to expand...
Click to collapse
Hi,
Maybe is hardware related did you check if the WIFI Antenna Signal Flex Cable is well connected?
https://www.ifixit.com/Teardown/Samsung+Galaxy+S4+Teardown/13947
MAX 404 said:
Hi,
Maybe is hardware related did you check if the WIFI Antenna Signal Flex Cable is well connected?
Click to expand...
Click to collapse
Thanks, but i already tried this.
Reconnected both connections, and made sure both were aligned flat on the connector.
Unfortunately without any result.
sven93 said:
Thanks, but i already tried this.
Reconnected both connections, and made sure both were aligned flat on the connector.
Unfortunately without any result.
Click to expand...
Click to collapse
Maybe is the chip....can you scan , do you see wifi networks or did you try the option wifi direct , between your phone and another unit?
MAX 404 said:
Maybe is the chip....can you scan , do you see wifi networks or did you try the option wifi direct , between your phone and another unit?
Click to expand...
Click to collapse
Well, lets hope its not the chip.
I can't turn on the wifi, if i tap the wifi button (either in settings or at the notifications area) it goes green for 0.5 sec and goes to grey right after.
Haven't tried wifi-direct as i don't have any compatible devices.
Just tried to turn on the tether service, there is states "Error" when i try to turn it on.
Is there any logfile that i can use to determine the cause?
sven93 said:
Well, lets hope its not the chip.
I can't turn on the wifi, if i tap the wifi button (either in settings or at the notifications area) it goes green for 0.5 sec and goes to grey right after.
Haven't tried wifi-direct as i don't have any compatible devices.
Just tried to turn on the tether service, there is states "Error" when i try to turn it on.
Is there any logfile that i can use to determine the cause?
Click to expand...
Click to collapse
Not sure about the log file ...
Here i found a thread , it talks about a solution but they use a SPT box, for what i see the problem is efs related, do you have an EFS backup?
http://forum.gsmhosting.com/vbb/f45...nlock-default-efs-imei-solution-here-1788263/
Nope, unfortunately i didn't backup the EFS folder.
Flashed my S2 a thousand times, with backup, never happened anything. I flash my S4 1 time without,...
Compared the content with the S2, and for me is looks like everything needed is still there. (not an expert though)
Any other ideas?
sven93 said:
Nope, unfortunately i didn't backup the EFS folder.
Flashed my S2 a thousand times, with backup, never happened anything. I flash my S4 1 time without,...
Compared the content with the S2, and for me is looks like everything needed is still there. (not an expert though)
Any other ideas?
Click to expand...
Click to collapse
1. Dial *#1234# in Stock Rom and check if your Csc is correct.
2. Reflash 2 times the stock rom.
Joku1981 said:
1. Dial *#1234# in Stock Rom and check if your Csc is correct.
2. Reflash 2 times the stock rom.
Click to expand...
Click to collapse
CSC Seems to match.
Tried flashing it 3 times in a row with the same (stock) ROM, still nothing.
sven93 said:
Hi,
I bought a second hand i9505, which i used for several days with the standard Samsung stuff.
After a few day's i installed CM11, but after a day my wifi stopped working.
Then i started googling, found several other treads with the same problem, tried those solutions.
But at the this point none of them worked for me.
Things that i tried:
-Different modems
-Stock Samsung rom
-Factory reset
-Format /system , and reflash stock rom with Odin
-Pull the battery out for 30mins
-Reconnected the Wifi antenna
-Deleted the WPA_Supplicant file
-Disable the powersaving mode under *#0011#
Al of them did not work for me.
Is there anybody who has an idea?
Thanks in advance!
Click to expand...
Click to collapse
I have the same problem. Wifi won't turn on no matter what I do. I was on cm-11-20140627-NIGHTLY-jflte and then decided to upgrade to cm-11-20140908-NIGHTLY-jflte. With that upgrade I lost wifi. I tried every possible thing that I found on forums and nothing helped. I also tried to upgrade to latest stock. I was on old bootloader until then, now I have the KNOX sh...t.
I have a feeling that something is wrong with wifi firmware. Is there a way to somehow check or reflash wifi firmware only?
regards.
ajax505 said:
I have the same problem. Wifi won't turn on no matter what I do. I was on cm-11-20140627-NIGHTLY-jflte and then decided to upgrade to cm-11-20140908-NIGHTLY-jflte. With that upgrade I lost wifi. I tried every possible thing that I found on forums and nothing helped. I also tried to upgrade to latest stock. I was on old bootloader until then, now I have the KNOX sh...t.
I have a feeling that something is wrong with wifi firmware. Is there a way to somehow check or reflash wifi firmware only?
regards.
Click to expand...
Click to collapse
Sad to hear you have the same.
Pretty strange, i haven't used the S4 since Wednesday, but the phone was still turned on, ten minutes ago i wanted to check something, turns out wifi is working again, until i decided to reboot, now its doing the same as before...
It does indeed smells software/firmware related.
Just made a dumpfile of the logs (bugreport > /mnt/sdcard/dump.txt) , and saw some interesting stuff in the kernel log:
<4>[ 9.717163] failed to power up wifi chip, retry again (5 left) **
<4>[ 9.717163]
<4>[ 9.733306] ## wifi_remove
<4>[ 9.733612] wifi_set_power = 1
<4>[ 9.733612] WiFi: trying to acquire BT lock
<4>[ 9.733612] ####btlock acquired cookie: WiFi
<4>[ 9.733642] wifi_set_power: btlock acquired
<6>[ 9.733642] ------------------------------------------------
<6>[ 9.733642] ------------------------------------------------
<6>[ 9.733642] brcm_wlan_power Enter: power on
<3>[ 9.733642] brcm_wlan_power: WL_REG_ON failed to pull up
<4>[ 9.733734] wifi_probe: set_power failed. err=-5
<4>[ 9.733734] wifi_set_power = 0
<4>[ 9.733734] ####btlock released, cookie: WiFi
<6>[ 9.733734] ------------------------------------------------
<6>[ 9.733795] ------------------------------------------------
<6>[ 9.733825] brcm_wlan_power Enter: power off
<3>[ 9.733825] brcm_wlan_power: WL_REG_ON failed to pull down
Click to expand...
Click to collapse
Then after a bit:
<4>[ 11.727294]
<4>[ 11.727294] failed to power up wifi chip, retry again (4 left) **
<4>[ 11.727294]
<4>[ 11.743499] ## wifi_remove
<4>[ 11.743835] wifi_set_power = 1
<4>[ 11.743835] WiFi: trying to acquire BT lock
<4>[ 11.743835] ####btlock acquired cookie: WiFi
<4>[ 11.743835] wifi_set_power: btlock acquired
<6>[ 11.743835] ------------------------------------------------
<6>[ 11.743865] ------------------------------------------------
<6>[ 11.743865] brcm_wlan_power Enter: power on
<6>[ 11.743865] barcode_emul_ice4: ice_gpiox_set : num = 3 , val = 1
<6>[ 11.754608] [email protected]: Start PackageManagerService
<6>[ 11.775604] [SSP] Updated 73599 bytes / 139282 bytes
<4>[ 11.977172] wifi_set_carddetect = 1
<4>[ 11.977172] brcm_wifi_status:267 status 1
Click to expand...
Click to collapse
For people who want to view the log: https://dl.dropboxusercontent.com/u/15503253/dumpfile.txt
I also get those kind of messages in my system logs:
<4>[ 1837.921936] failed to power up wifi chip, retry again (1 left) **
<4>[ 1837.921966]
<4>[ 1837.941497] ## wifi_remove
<4>[ 1837.941497] wifi_set_power = 0
<4>[ 1837.941528] ####btlock released, cookie: WiFi
<6>[ 1837.941558] ------------------------------------------------
<6>[ 1837.941558] ------------------------------------------------
<6>[ 1837.941589] brcm_wlan_power Enter: power off
<6>[ 1837.941619] barcode_emul_ice4: ice_gpiox_set : num = 3 , val = 0
<4>[ 1838.182006] wifi_set_carddetect = 0
<4>[ 1838.182037] brcm_wifi_status:267 status 0
<6>[ 1838.182067] mmc1: Slot status change detected (1 -> 0)
<4>[ 1838.187591]
<4>[ 1838.187622] failed to power up wifi chip, max retry reached, exits **
Click to expand...
Click to collapse
I also get a lot of "mmc1: Data CRC error":
<3>[ 1826.574645] mmc1: Data CRC error
<3>[ 1826.577178] msmsdcc_data_err: opcode 0x00000035
<3>[ 1826.581542] msmsdcc_data_err: blksz 4, blocks 1
<6>[ 1826.586883] sps:BAM 0x12182000 enabled: ver:0x5, number of pipes:6dhd_detach(): thread:dhd_sysioc:392 terminated OK
<4>[ 1826.651245] dhd_detach(): thread:dhd_watchdog_thread:38f terminated OK
<4>[ 1826.651336] dhd_dpc_thread: Unexpected up_cnt 0
<4>[ 1826.651428] dhd_detach(): thread:dhd_dpc:390 terminated OK
<4>[ 1826.651733] dhd_detach(): thread:dhd_rxf:391 terminated OK
<6>[ 1826.670593] CFG80211-INFO2) wl_event_handler : was terminated
<4>[ 1826.670898] wl_destroy_event_handler(): thread:wl_event_handler:38e terminated OK
<4>[ 1826.682250] dhdsdio_disconnect : the lock is released.
<4>[ 1826.683807] ## wifi_remove
<4>[ 1826.683837] wifi_set_power = 0
<4>[ 1826.683868] ####ignore lock release, cookie mismatch: WiFi owner ˙˙˙˙
<6>[ 1826.683898] ------------------------------------------------
<6>[ 1826.683898] ------------------------------------------------
<6>[ 1826.683929] brcm_wlan_power Enter: power off
<6>[ 1826.683959] barcode_emul_ice4: ice_gpiox_set : num = 3 , val = 0
<4>[ 1826.920593] wifi_set_carddetect = 0
<4>[ 1826.920623] brcm_wifi_status:267 status 0
<6>[ 1826.920654] mmc1: Slot status change detected (1 -> 0)
<6>[ 1826.928405] mmc1: card 0001 removed
<6>[ 1828.083618] synaptics_rmi4_i2c 3-0020: [0][P] 0x01
<6>[ 1828.142578] synaptics_rmi4_i2c 3-0020: [0][R] 0x00 M[4] V[5c]
<4>[ 1828.178527] wifi_set_power = 1
<4>[ 1828.178558] WiFi: trying to acquire BT lock
<4>[ 1828.178558] ####btlock acquired cookie: WiFi
<4>[ 1828.178558] wifi_set_power: btlock acquired
<6>[ 1828.178558] ------------------------------------------------
<6>[ 1828.178588] ------------------------------------------------
<6>[ 1828.178588] brcm_wlan_power Enter: power on
<6>[ 1828.178588] barcode_emul_ice4: ice_gpiox_set : num = 3 , val = 1
<4>[ 1828.411895] wifi_set_carddetect = 1
<4>[ 1828.411926] brcm_wifi_status:267 status 1
<6>[ 1828.411956] mmc1: Slot status change detected (0 -> 1)
<3>[ 1828.473205] mmc1: msmsdcc_switch_io_voltage: MCIDATIN_3_0 is still not all zeros
<3>[ 1828.480651] mmc1: CMD7: Command CRC error
<3>[ 1828.484039] mmc1: SDCC PWR is ON
<3>[ 1828.487426] mmc1: SDCC clks are ON, MCLK rate=400000
<3>[ 1828.492217] mmc1: SDCC irq is enabled
<3>[ 1828.495849] ===== SDCC-CORE: Register Dumps @phys_base=0x12180000, @virt_base=0xe337a000 =====
<3>[ 1828.504608] Reg=0x00: 0x00000001, 0x01209300, 0x00000000, 0x00000447
<3>[ 1828.510955] Reg=0x10: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.517120] Reg=0x20: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.523620] Reg=0x30: 0x00000000, 0x004c0000, 0x00000000, 0x408001ff
<3>[ 1828.529785] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.536285] Reg=0x50: 0x06000018, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.542633] Reg=0x60: 0x67356400, 0x00000000, 0x00000018, 0x00000000
<3>[ 1828.548797] ===== SDCC-DML: Register Dumps @phys_base=0x12180800, @virt_base=0xe3534800 =====
<3>[ 1828.557495] Reg=0x00: 0x00000000, 0x00010001, 0x00000000, 0x00000000
<3>[ 1828.563629] Reg=0x10: 0x00000000, 0x00001000, 0x00001000, 0x00020001
<3>[ 1828.570159] Reg=0x20: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.576477] Reg=0x30: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.582641] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.589172] ===== SDCC-BAM: Register Dumps @phys_base=0x12182000, @virt_base=0xe33d8000 =====
<3>[ 1828.597503] Reg=0x00: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.604003] Reg=0x10: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.610351] Reg=0x20: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.616516] Reg=0x30: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.623016] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.629180] mmc1: MCI_TEST_INPUT = 0x0000003e
<3>[ 1828.633697] mmc1: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0, req_tout_ms=10000
<3>[ 1828.644012] mmc1: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspending=0
<3>[ 1828.650817] mmc1: RPM: runtime_status=0, usage_count=2, is_suspended=0, disable_depth=0, runtime_error=0, request_pending=0, request=0
<4>[ 1828.663024] mmc1: Skipped tuning.
<3>[ 1828.686431] mmc1: error -110 whilst initialising SDIO card
<4>[ 1830.421936]
<4>[ 1830.421966] failed to power up wifi chip, retry again (4 left) **
Click to expand...
Click to collapse
As long as I know mmc0 is internal memory and mmc2 is external sd card. Can anyone explain what mmc1 device is?
Bump...