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?
I am working on a a variant of the ROM from CTXz in this thread for the T715 (Samsung Galaxy Tab S2 8.0 LTE variant aka gts28lte) and got stuck on making the RIL work. I added the ril-daemon and the cpboot-daemon, but get the following errors when booting up:
Code:
<3>[ 9.942977] [c7] mif: cbd: check_debug_level: debug level=0, cp_debug=0
<6>[ 9.943035] [c7] muic-universal:muic_show_attached_dev attached_dev:1
<3>[ 9.943053] [c7] mif: cbd: check_factory_log_path: log path - /sdcard/log
<3>[ 9.943069] [c7] mif: cbd: main: Start CP Boot Daemon (CBD)
<3>[ 9.943123] [c7] mif: cbd: main: SS333 modem
<3>[ 9.943147] [c7] mif: cbd: main: partition number : 13
<3>[ 9.943162] [c7] mif: cbd: main: partition path : /dev/block/mmcblk0p13
<3>[ 9.943202] [c7] mif: cbd: main: Modem type = 9
<3>[ 9.943212] [c7] mif: cbd: main: Boot link = 3
<3>[ 9.943222] [c7] mif: cbd: main: Main link = 10
<3>[ 9.943250] [c7] mif: cbd: start_shannon333_boot: CP boot device = /dev/umts_boot0
<3>[ 9.943265] [c7] mif: cbd: start_shannon333_boot: CP binary file = /dev/block/mmcblk0p13
<3>[ 9.943279] [c7] mif: cbd: start_shannon333_boot: CP NV file = /efs/nv_data.bin
<3>[ 9.943387] [c7] mif: cbd: start_shannon333_boot: BOOT link SPI
<3>[ 9.943408] [c7] mif: cbd: start_shannon333_boot: MAIN link MIPI-LLI
<3>[ 9.943435] [c7] mif: cbd: start_shannon333_boot: NV validation done
<3>[ 9.943490] [c7] mif: cbd: std_boot_prepare_args: ERR! DEV(/dev/umts_boot0) open fail (No such file or directory)
<3>[ 9.943503] [c7] mif: cbd: prepare_boot_args: ERR! std_boot_prepare_args fail
<3>[ 9.943519] [c7] mif: cbd: start_shannon333_boot: ERR! prepare_boot_args fail
I checked all config for file contexts, sepoliy etc. and also config from the stock ROM but to no avail.
Has anyone seen this before on a similar device or has an idea where to look?
thx
-apc
Did you ever finish the Rom? Desperately want cm Rom on my t715
Ok same at here... At least I had a little success! I got CM13 booting up on T715! But there are some big issues at the moment. Modem is not working jet, I'll try to figure that out.
Philippovitsch said:
Ok same at here... At least I had a little success! I got CM13 booting up on T715! But there are some big issues at the moment. Modem is not working jet, I'll try to figure that out.
Click to expand...
Click to collapse
hello, How I build Cyanogenmod 12 for my T715Y? do you have tutorial step by step were I can follow? thanks
Sent from my SM-T715 using Tapatalk
bryntz said:
hello, How I build Cyanogenmod 12 for my T715Y? do you have tutorial step by step were I can follow? thanks
Sent from my SM-T715 using Tapatalk
Click to expand...
Click to collapse
Uhm... not really.
I started with compiling some roms for official supported devices (for example I choose my Oneplus One device https://wiki.cyanogenmod.org/w/Build_for_bacon ) just to get comfortable with linux and the build environment in general. You can choose a device out of the list https://wiki.cyanogenmod.org/w/Build_Guides .
After that I started reading thorugh that guide https://wiki.cyanogenmod.org/w/Doc:_porting_intro , looked through some existing git repos and tried to port them to my device.
That's where I am now, at the very beginning and much more to learn
Philippovitsch said:
Uhm... not really.
I started with compiling some roms for official supported devices (for example I choose my Oneplus One device https://wiki.cyanogenmod.org/w/Build_for_bacon ) just to get comfortable with linux and the build environment in general. You can choose a device out of the list https://wiki.cyanogenmod.org/w/Build_Guides .
After that I started reading thorugh that guide https://wiki.cyanogenmod.org/w/Doc:_porting_intro , looked through some existing git repos and tried to port them to my device.
That's where I am now, at the very beginning and much more to learn
Click to expand...
Click to collapse
lol, I got dizzy when try that.. (on last step: obtain openJDK 1.7), I got stuck and then I removed my vmware, lol..
can you compile cyanogenmod 12 for T715Y?
thanks
Sent from my iPhone using Tapatalk
Hi, I have just purchased my first Android device, a Huawei Nexus 6p, and tried to install MultiRom following your excelent guide. Rooted, installed MultiROM , added some ROMs, everything looks fine. But, I can choose between different ROMs while booting but nothing boots but primary (Android, stock).
I get the following error/log while booting a secondary rom (and get stuck, have to press power buttom to restart):
<14>[ 10.805852] trampoline: Updating device /dev/block/mmcblk0p44 to /dev/block/dm-0 in fstab due to encryption.
<4>[ 10.808527] EXT4-fs (dm-0): Ignoring removed nomblk_io_submit option
<6>[ 10.842087] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: barrier=1,data=ordered,nomblk_io_submit,noauto_da_alloc,discard,errors=panic
<14>[ 10.874351] trampoline: Starting adbd
<11>[ 10.874826] trampoline: Running multirom
<11>[ 10.884085] multirom: Running MultiROM v33
<14>[ 10.884246] multirom: Loading MultiROM status...
<11>[ 10.884339] multirom: Loading fstab "/fstab.angler"...
<14>[ 10.911487] multirom: Adding ROM Internal
<14>[ 10.915680] multirom: Adding ROM cm-13.0-20160419-SNAPSHOT-
<14>[ 10.916141] multirom: Adding ROM ResurrectionRemix-M-v5.6.8
<14>[ 10.916576] multirom: Adding ROM pure_nexus_angler-6.0.1-20
<14>[ 10.917440] multirom: Dumping multirom status:
<14>[ 10.917454] multirom: is_second_boot=1
<14>[ 10.917463] multirom: is_running_in_primary_rom=0
<14>[ 10.917471] multirom: current_rom=cm-13.0-20160419-SNAPSHOT-
<14>[ 10.917479] multirom: colors_v2=6
<14>[ 10.917487] multirom: brightness=40
<14>[ 10.917495] multirom: enable_adb=0
<14>[ 10.917503] multirom: rotation=0
<14>[ 10.917511] multirom: force_generic_fb=0
<14>[ 10.917538] multirom: anim_duration_coef=1.000000
<14>[ 10.917547] multirom: hide_internal=0
<14>[ 10.917555] multirom: int_display_name=Internal
<14>[ 10.917563] multirom: auto_boot_seconds=5
<14>[ 10.917571] multirom: auto_boot_rom=Internal
<14>[ 10.917579] multirom: auto_boot_type=0
<14>[ 10.917587] multirom: curr_rom_part=NULL
<14>[ 10.917594] multirom:
<14>[ 10.917601] multirom: ROM: Internal
<14>[ 10.917609] multirom: base_path: /realdata/media/0/multirom/roms/Internal
<14>[ 10.917618] multirom: icon_path: /realdata/media/0/multirom/icons/romic_android.png
<14>[ 10.917625] multirom: type: 0
<14>[ 10.917633] multirom: has_bootimg: 0
<14>[ 10.917640] multirom: ROM: cm-13.0-20160419-SNAPSHOT-
<14>[ 10.917648] multirom: base_path: /realdata/media/0/multirom/roms/cm-13.0-20160419-SNAPSHOT-
<14>[ 10.917657] multirom: icon_path: /realdata/media/0/multirom/icons/romic_default.png
<14>[ 10.917664] multirom: type: 1
<14>[ 10.917672] multirom: has_bootimg: 1
<14>[ 10.917679] multirom: ROM: pure_nexus_angler-6.0.1-20
<14>[ 10.917687] multirom: base_path: /realdata/media/0/multirom/roms/pure_nexus_angler-6.0.1-20
<14>[ 10.917695] multirom: icon_path: /realdata/media/0/multirom/icons/romic_default.png
<14>[ 10.917703] multirom: type: 1
<14>[ 10.917711] multirom: has_bootimg: 1
<14>[ 10.917718] multirom: ROM: ResurrectionRemix-M-v5.6.8
<14>[ 10.917725] multirom: base_path: /realdata/media/0/multirom/roms/ResurrectionRemix-M-v5.6.8
<14>[ 10.917734] multirom: icon_path: /realdata/media/0/multirom/icons/romic_default.png
<14>[ 10.917741] multirom: type: 1
<14>[ 10.917749] multirom: has_bootimg: 1
<11>[ 10.917767] multirom: Skipping ROM selection, is_second_boot=1, auto_boot_type=0x0
<11>[ 10.917792] multirom: No run-on-boot scripts for ROM cm-13.0-20160419-SNAPSHOT-
<14>[ 10.953280] multirom: Using fstab ./fstab.angler from rc files
<11>[ 10.953303] multirom: Modifying fstab: ./fstab.angler
<11>[ 10.955211] multirom: Could not open /system/build.prop to read api level!
<6>[ 10.955256] mdss_fb_blank_sub: mdss_fb_open+0x224/0x318 mode:0
<14>[ 10.955493] multirom: Left Split=720
<14>[ 10.955504] multirom: Right Split=720
<4>[ 10.980178] mdss_mdp_ov_xres_check: invalid use of RIGHT_MIXER flag.
<14>[ 10.980259] multirom: Framebuffer implementation: Qualcomm ION overlay
Can you help me please? (noob-friendly)
Thanks in advance.
Which kernel are you using on the primary ROM? Also, have you tried injecting boot from the MultiROM menu, within TWRP?
DJBhardwaj said:
Which kernel are you using on the primary ROM? Also, have you tried injecting boot from the MultiROM menu, within TWRP?
Click to expand...
Click to collapse
Thank you very much DJ.
I am using ElementalX-N6P-1.17 for Kernel for Android 6.0.1 (Marshmallow). In the TWRP - MultiROM - top right menu - Inject MultiROM - "Inject current boot sector" (swipe to confirm) already done. Successful boot partition injected and rebooted the system. But no luck.
Any sugestion? Thanks in advance.
Cya_Cya_Cya said:
Thank you very much DJ.
I am using ElementalX-N6P-1.17 for Kernel for Android 6.0.1 (Marshmallow). In the TWRP - MultiROM - top right menu - Inject MultiROM - "Inject current boot sector" (swipe to confirm) already done. Successful boot partition injected and rebooted the system. But no luck.
Any sugestion? Thanks in advance.
Click to expand...
Click to collapse
Just throwing in a wild guess.
Quite unsure, but I could only see vendor as a cause. See if all your builds are based on the same android branch?
DJBhardwaj said:
Just throwing in a wild guess.
Quite unsure, but I could only see vendor as a cause. See if all your builds are based on the same android branch?
Click to expand...
Click to collapse
I bought it directly from Google. Still no nano SIM card inside. Just testing Android and the excellent capabilities of MultiROM (nethunter, cyanogenmod, etc...).
I am thinking about starting from scratch and flash the latest Google factory image.
Cya_Cya_Cya said:
I bought it directly from Google. Still no nano SIM card inside. Just testing Android and the excellent capabilities of MultiROM (nethunter, cyanogenmod, etc...).
I am thinking about starting from scratch and flash the latest Google factory image.
Click to expand...
Click to collapse
Haha, not the retailer (vendor), but the vendor partition on your device.
If nothing works, starting from scratch is a good option.
DJBhardwaj said:
Haha, not the retailer (vendor), but the vendor partition on your device.
If nothing works, starting from scratch is a good option.
Click to expand...
Click to collapse
Hahaha... I am in the "being a noob" process...
Restored factory default, rooted again, added hard-lock kernel (another one), installed TWRP MultiROM edition and same error. I attach the file for reference. Hope anyone has seen this before.
Thanks in advance.
By the way... I followed your excellent guide:
http://www.droidorigin.com/enjoy-multiple-roms-with-multirom-on-nexus-6p/
Thank you for your work and time.
Cya_Cya_Cya said:
Hahaha... I am in the "being a noob" process...
Restored factory default, rooted again, added hard-lock kernel (another one), installed TWRP MultiROM edition and same error. I attach the file for reference. Hope anyone has seen this before.
Thanks in advance.
Click to expand...
Click to collapse
That's weird. I never have faced any issue with MultiROM. I hope you did install the MultiROM installer zip?
Have the same problem in my nexus 5
I build my our modem files following as: https://forum.xda-developers.com/android/software-hacking/dev-building-qualcomm-modem-sources-t3489833
I have a Moto G X1032 that already unlocked. and also replace the NON-HLOS partition by my our mba.b00/mba.mdt. but when starting, it logs:
4>[ 4427.564452,0] ------------[ cut here ]------------
<4>[ 4427.564673,0] WARNING: at ../../../../../../kernel/kernel/irq/manage.c:428 enable_irq+0x3c/0x74()
<4>[ 4427.564786,0] Unbalanced enable for IRQ 404
<4>[ 4427.564980,0] Modules linked in:
<4>[ 4427.565210,0] [<c010bb78>] (unwind_backtrace+0x0/0xec) from [<c0182278>] (warn_slowpath_common+0x54/0x64)
<4>[ 4427.565422,0] [<c0182278>] (warn_slowpath_common+0x54/0x64) from [<c01822b8>] (warn_slowpath_fmt+0x30/0x40)
<4>[ 4427.565633,0] [<c01822b8>] (warn_slowpath_fmt+0x30/0x40) from [<c01e8f3c>] (enable_irq+0x3c/0x74)
<4>[ 4427.565845,0] [<c01e8f3c>] (enable_irq+0x3c/0x74) from [<c0130a48>] (pil_boot+0x80c/0xbf0)
<4>[ 4427.565970,0] [<c0130a48>] (pil_boot+0x80c/0xbf0) from [<c01327a0>] (mss_start+0x2c/0x60)
<4>[ 4427.566183,0] [<c01327a0>] (mss_start+0x2c/0x60) from [<c015c7f0>] (subsystem_get+0x9c/0x178)
<4>[ 4427.566397,0] [<c015c7f0>] (subsystem_get+0x9c/0x178) from [<c014573c>] (msm_ipc_load_default_node+0x34/0x6c)
<4>[ 4427.566611,0] [<c014573c>] (msm_ipc_load_default_node+0x34/0x6c) from [<c014b27c>] (msm_ipc_router_ioctl+0x124/0x2dc)
<4>[ 4427.566827,0] [<c014b27c>] (msm_ipc_router_ioctl+0x124/0x2dc) from [<c0779a08>] (sock_ioctl+0x1c8/0x294)
<4>[ 4427.567043,0] [<c0779a08>] (sock_ioctl+0x1c8/0x294) from [<c026c4e8>] (do_vfs_ioctl+0x3f4/0x5a8)
<4>[ 4427.567166,0] [<c026c4e8>] (do_vfs_ioctl+0x3f4/0x5a8) from [<c026c708>] (sys_ioctl+0x6c/0x7c)
<4>[ 4427.567376,0] [<c026c708>] (sys_ioctl+0x6c/0x7c) from [<c0105ae0>] (ret_fast_syscall+0x0/0x30)
<4>[ 4427.567576,0] ---[ end trace 3373d290566a10f8 ]---
<3>[ 4427.593954,0] pil-q6v5-mss fc880000.qcom,mss: PBL returned unexpected status -274725888
<3>[ 4427.594121,0] pil-q6v5-mss fc880000.qcom,mss: mba: Failed to bring out of reset
<3>[ 4427.594382,0] modem_notifier_cb: sysmon_send_event error -19
<3>[ 4427.594469,0] M-Notify: General: 5
<3>[ 4427.594743,0] msm_ipc_load_default_node: Failed to load modem
<6>[ 4427.599158,0] pil-q6v5-mss fc880000.qcom,mss: mba: loading from 0x0c300000 to 0x0c349000
<4>[ 4427.604425,0] ------------[ cut here ]------------
any one know what cause this?
<3>[ 4427.593954,0] pil-q6v5-mss fc880000.qcom,mss: PBL returned unexpected status -274725888
after my investigation, i think it caused by my mba is blocked by PBL. i read the <<Qualcomm-Secure-Boot>> (you can google it, because i cannot attach a link for newbie) and use the tools in attachments to compared the mba with the official mba.
I got the Certification Store and analysis it. the tool is great that i can verify the mba.b00. but any one know how to generate the certification by reversing way?