Related
Something happened to my phone.. think its from updating the SPL, wifi and sd card will no longer work.
Anyone know of a way to downgrade SPL without SD Card access?
i do not know the exact steps but you should be able to flash it via fastboot since it does not use the sdcard. but you will need adb working on your computer
KHannel said:
Something happened to my phone.. think its from updating the SPL, wifi and sd card will no longer work.
Anyone know of a way to downgrade SPL without SD Card access?
Click to expand...
Click to collapse
I find it hard to believe that upgrading your spl would effect your wifi and sd card. You able to give more details.
More Details
Well here is what happened and where the phone is now.
I had installed Drizzy Touch Flo 2.8 had it up and running ( Haykuro's new SPL and yes, I upgraded Radio first ) , everything was working fine. Took the back off my phone and somehow the battery fell out. Put the battery back in and the phone was stuck in the htc boot loop. Went into recovery to see what was happening and the phone wasn't able to mount the SD Card. Went into /dev/block and there was no mmcblk0 showing at all.
I got home, I put the card into a reader on my computer and it read just fine, all partitions and everyhing intact. I figured maybe it messed up a sector and just wasn't being read, so just for the heck of it I wiped the partition table and repartitioned it. Put it back into the phone and still stuck at htc boot loop with no mmcblk0.
So I flashed the phone back to the 1.5 dev rom from the HTC web site ( using fastboot ). Got the phone up and running but now it shows an error on the notification bar "SD Card Removed". I've tried 3 different SD Cards, nothing. Here is the dmesg upon insertion of an SD Card:
<7>[ 77.724578] msmsdcc_platform_status_irq: 194
<6>[ 77.725433] mmc1: Slot status change detected (0 -> 1)
<4>[ 80.221893] trout_sdslot_switchvdd: Setting level to 2950
<3>[ 80.230895] mmc1: Command timeout
<3>[ 80.237640] mmc1: Command timeout
<3>[ 80.243896] mmc1: Command timeout
<3>[ 80.250183] mmc1: Command timeout
<3>[ 80.256835] mmc1: Command timeout
<3>[ 80.263549] mmc1: Command timeout
<3>[ 80.269775] mmc1: Command timeout
<3>[ 80.276214] mmc1: Command timeout
<3>[ 80.282623] mmc1: Command timeout
<3>[ 80.288909] mmc1: Command timeout
<4>[ 80.294464] trout_sdslot_switchvdd: Disabling SD slot power
#
Had taken a break from working the SD Card issue, and decided to check my email. Turned on wifi after about 60 seconds I get an error saying "Unable to start Wifi". After that error it won't even attempt to turn it on again. Here is dmesg while turning on wifi
<6>[ 181.843994] TIWLAN: Driver loading
<4>[ 181.844665] wifi_probe
<4>[ 181.844940] trout_wifi_power: 1
<4>[ 182.051116] trout_wifi_reset: 0
<4>[ 182.102478] trout_wifi_set_carddetect: 1
<7>[ 182.102783] mmc0: card_present 1
<6>[ 182.103057] mmc0: Slot status change detected (0 -> 1)
<3>[ 184.613708] mmc0: Command timeout
<4>[ 184.620727] mmc0: card claims to support voltages below the defined range. These will be ignored.
<4>[ 184.621582] mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
<6>[ 184.629089] mmc0: new SDIO card at address 0001
<6>[ 184.635101] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 184.641021] TIWLAN: Driver initialized (rc 0)
<3>[ 185.643066] mmc0: Data timeout
<3>[ 185.643524] SDIO_SyncRead: Read operation failed (-110) (retries = 5)
<3>[ 186.646179] mmc0: Data timeout
<3>[ 186.646789] SDIO_SyncRead: Read operation failed (-110) (retries = 4)
<3>[ 187.649719] mmc0: Data timeout
<3>[ 187.650329] SDIO_SyncRead: Read operation failed (-110) (retries = 3)
<3>[ 187.651336] SDIO_SyncRead: Retry succeeded
<4>[ 187.651794] TIWLAN: invalid chip id = 0x 0 0 0 0!
<6>[ 187.652221] TIWLAN: Driver loaded
<3>[ 189.092773] mmc0: Data timeout
<3>[ 189.093170] SDIO_SyncRead: Read operation failed (-110) (retries = 5)
<3>[ 190.095825] mmc0: Data timeout
<3>[ 190.096466] SDIO_SyncRead: Read operation failed (-110) (retries = 4)
<3>[ 191.098968] mmc0: Data timeout
<3>[ 191.099945] SDIO_SyncRead: Read operation failed (-110) (retries = 3)
<3>[ 191.100616] SDIO_SyncRead: Retry succeeded
<3>[ 192.101654] mmc0: Data timeout
<3>[ 192.102264] SDIO_SyncRead: Read operation failed (-110) (retries = 5)
<3>[ 193.104766] mmc0: Data timeout
<3>[ 193.105743] SDIO_SyncRead: Read operation failed (-110) (retries = 4)
<3>[ 194.106292] mmc0: Data timeout
<3>[ 194.107238] SDIO_SyncRead: Read operation failed (-110) (retries = 3)
<3>[ 194.107940] SDIO_SyncRead: Retry succeeded
<3>[ 195.125518] mmc0: Data timeout
<3>[ 195.126220] SDIO_SyncRead: Read operation failed (-110) (retries = 5)
<3>[ 196.128784] mmc0: Data timeout
<3>[ 196.129760] SDIO_SyncRead: Read operation failed (-110) (retries = 4)
<3>[ 197.132293] mmc0: Data timeout
<3>[ 197.132934] SDIO_SyncRead: Read operation failed (-110) (retries = 3)
<3>[ 197.133972] SDIO_SyncRead: Retry succeeded
<3>[ 198.136474] mmc0: Data timeout
<3>[ 198.137481] SDIO_SyncRead: Read operation failed (-110) (retries = 5)
<3>[ 199.140197] mmc0: Data timeout
<3>[ 199.140838] SDIO_SyncRead: Read operation failed (-110) (retries = 4)
<3>[ 200.143768] mmc0: Data timeout
<3>[ 200.144409] SDIO_SyncRead: Read operation failed (-110) (retries = 3)
<3>[ 200.145416] SDIO_SyncRead: Retry succeeded
<3>[ 201.148010] mmc0: Data timeout
<3>[ 201.148651] SDIO_SyncRead: Read operation failed (-110) (retries = 5)
<3>[ 202.151855] mmc0: Data timeout
<3>[ 202.152496] SDIO_SyncRead: Read operation failed (-110) (retries = 4)
<3>[ 203.155426] mmc0: Data timeout
<3>[ 203.156066] SDIO_SyncRead: Read operation failed (-110) (retries = 3)
<3>[ 203.157073] SDIO_SyncRead: Retry succeeded
<3>[ 204.161895] mmc0: Data timeout
<3>[ 204.162536] SDIO_SyncRead: Read operation failed (-110) (retries = 5)
<3>[ 205.165588] mmc0: Data timeout
<3>[ 205.166229] SDIO_SyncRead: Read operation failed (-110) (retries = 4)
<3>[ 206.169158] mmc0: Data timeout
<3>[ 206.169799] SDIO_SyncRead: Read operation failed (-110) (retries = 3)
<3>[ 206.170806] SDIO_SyncRead: Retry succeeded
<3>[ 207.173858] mmc0: Data timeout
<3>[ 207.174499] SDIO_SyncRead: Read operation failed (-110) (retries = 5)
<3>[ 208.177551] mmc0: Data timeout
<3>[ 208.178192] SDIO_SyncRead: Read operation failed (-110) (retries = 4)
<3>[ 209.181152] mmc0: Data timeout
<3>[ 209.181793] SDIO_SyncRead: Read operation failed (-110) (retries = 3)
<3>[ 209.182464] SDIO_SyncRead: Retry succeeded
<3>[ 210.188385] mmc0: Data timeout
<3>[ 210.189025] SDIO_SyncRead: Read operation failed (-110) (retries = 5)
<3>[ 211.192230] mmc0: Data timeout
<3>[ 211.192871] SDIO_SyncRead: Read operation failed (-110) (retries = 4)
<3>[ 212.195373] mmc0: Data timeout
<3>[ 212.196380] SDIO_SyncRead: Read operation failed (-110) (retries = 3)
<3>[ 212.197052] SDIO_SyncRead: Retry succeeded
<3>[ 213.276336] mmc0: Data timeout
<3>[ 213.277008] SDIO_SyncRead: Read operation failed (-110) (retries = 5)
<3>[ 214.279937] mmc0: Data timeout
<3>[ 214.280578] SDIO_SyncRead: Read operation failed (-110) (retries = 4)
<3>[ 215.283233] mmc0: Data timeout
<3>[ 215.284210] SDIO_SyncRead: Read operation failed (-110) (retries = 3)
<3>[ 215.284881] SDIO_SyncRead: Retry succeeded
<3>[ 216.287963] mmc0: Data timeout
<3>[ 216.288604] SDIO_SyncRead: Read operation failed (-110) (retries = 5)
<3>[ 217.291259] mmc0: Data timeout
<3>[ 217.292236] SDIO_SyncRead: Read operation failed (-110) (retries = 4)
<3>[ 218.295043] mmc0: Data timeout
<3>[ 218.295684] SDIO_SyncRead: Read operation failed (-110) (retries = 3)
<3>[ 218.296722] SDIO_SyncRead: Retry succeeded
<3>[ 219.299468] mmc0: Data timeout
<3>[ 219.300476] SDIO_SyncRead: Read operation failed (-110) (retries = 5)
<3>[ 220.303131] mmc0: Data timeout
<3>[ 220.304107] SDIO_SyncRead: Read operation failed (-110) (retries = 4)
<3>[ 221.306610] mmc0: Data timeout
<3>[ 221.307250] SDIO_SyncRead: Read operation failed (-110) (retries = 3)
<3>[ 221.308258] SDIO_SyncRead: Retry succeeded
<3>[ 222.310913] mmc0: Data timeout
<3>[ 222.311889] SDIO_SyncRead: Read operation failed (-110) (retries = 5)
<3>[ 223.314453] mmc0: Data timeout
<3>[ 223.315093] SDIO_SyncRead: Read operation failed (-110) (retries = 4)
#
I'm not exactly blaming the SPL, but its that and the Radio are the ONLY things left that has not been changed. I can't downgrade the radio without first changing the SPL because we know that will brick with Haykuro's SPL that I'm running.
Hmm, someone had suggested a short in the phone... startin to look more and more like that now that I'm looking at the Wifi dmesg output.
I've loaded every partition on the phone, boot, recovery, system, etc. However, I think SPL is the only thing I can't change without SD Card access. I've thought of maybe being able to re-write the recovery to have it read from another directory than the SD Card... anyone ever done this?
Thanks for the help,
Ken
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 have downloaded the 6.1.0-RC2-Aria ROM a couple of days ago, installed it on my phone and everything is working great - thanks again attn1!
Now I would like to do some testing/dev with it; instead of tampering with my device.
I created a NANdroid back-up and then tried running the ROM on the SDK emulator following threads instructions found over here and other forums, e.g. :
http://forum.xda-developers.com/archive/index.php/t-572497.html
http://forum.xda-developers.com/showthread.php?t=525930&page=2
http://android.modaco.com/content/g...p-and-running-a-full-rom-with-the-market-etc/
The emulator seems to be running OK, but the kernel gets stuck before it even gives me the boot animation. (- c.f. below for the parameters passed and the kernel boot log; adb logcat does not report anything at all -)
Anyone has been able to run this particular ROM on the SDK emulator or may give me pointers as to how to do so successfully?
Thank you.
+++++++++++++++++++++++++++++++++++++++++++++++++++++
C:\android-sdk-windows\tools>emulator -avd testing -show-kernel -sdcard mycard
Uncompressing Linux............................................................................................. done, booting the kernel.
Initializing cgroup subsys cpu
Linux version 2.6.29-00261-g0097074-dirty ([email protected]) (gcc version 4.4.0 (GCC) ) #20 Wed Mar 31 09:54:02 PDT 2010
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00093177
CPU: VIVT data cache, VIVT instruction cache
Machine: Goldfish
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048
Kernel command line: qemu=1 console=ttyS0 android.checkjni=1 android.qemud=ttyS1 android.ndns=1
Unknown boot option `android.checkjni=1': ignoring
Unknown boot option `android.qemud=ttyS1': ignoring
Unknown boot option `android.ndns=1': ignoring
PID hash table entries: 2048 (order: 11, 8192 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 512MB = 512MB total
Memory: 515840KB available (2616K code, 681K data, 104K init)
Calibrating delay loop... 238.38 BogoMIPS (lpj=1191936)
Mount-cache hash table entries: 512
Initializing cgroup subsys debug
Initializing cgroup subsys cpuacct
Initializing cgroup subsys freezer
CPU: Testing write buffer coherency: ok
net_namespace: 520 bytes
NET: Registered protocol family 16
bio: create slab <bio-0> at 0
NET: Registered protocol family 2
IP route cache hash table entries: 16384 (order: 4, 65536 bytes)
TCP established hash table entries: 65536 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 65536 bind 65536)
TCP reno registered
NET: Registered protocol family 1
checking if image is initramfs... it is
Freeing initrd memory: 160K
goldfish_new_pdev goldfish_interrupt_controller at ff000000 irq -1
goldfish_new_pdev goldfish_device_bus at ff001000 irq 1
goldfish_new_pdev goldfish_timer at ff003000 irq 3
goldfish_new_pdev goldfish_rtc at ff010000 irq 10
goldfish_new_pdev goldfish_tty at ff002000 irq 4
goldfish_new_pdev goldfish_tty at ff011000 irq 11
goldfish_new_pdev smc91x at ff012000 irq 12
goldfish_new_pdev goldfish_fb at ff013000 irq 13
goldfish_new_pdev goldfish_mmc at ff005000 irq 14
goldfish_new_pdev goldfish_memlog at ff006000 irq -1
goldfish_new_pdev goldfish_events at ff014000 irq 15
goldfish_new_pdev goldfish_nand at ff015000 irq -1
goldfish_new_pdev goldfish-switch at ff016000 irq 16
goldfish_new_pdev goldfish-switch at ff017000 irq 17
goldfish_pdev_worker registered goldfish_interrupt_controller
goldfish_pdev_worker registered goldfish_device_bus
goldfish_pdev_worker registered goldfish_timer
goldfish_pdev_worker registered goldfish_rtc
goldfish_pdev_worker registered goldfish_tty
goldfish_pdev_worker registered goldfish_tty
goldfish_pdev_worker registered smc91x
goldfish_pdev_worker registered goldfish_fb
goldfish_pdev_worker registered goldfish_mmc
goldfish_pdev_worker registered goldfish_memlog
goldfish_pdev_worker registered goldfish_events
goldfish_pdev_worker registered goldfish_nand
goldfish_pdev_worker registered goldfish-switch
goldfish_pdev_worker registered goldfish-switch
ashmem: initialized
Installing knfsd (copyright (C) 1996 [email protected]).
yaffs Mar 26 2010 13:38:48 Installing.
msgmni has been set to 1008
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
allocating frame buffer 320 * 480, got ffa00000
Console: switching to colour frame buffer device 40x30
console [ttyS0] enabled
brd: module loaded
loop: module loaded
nbd: registered device at major 43
smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre <[email protected]>
eth0 (smc91x): not using net_device_ops yet
eth0: SMC91C11xFD (rev 1) at e084c000 IRQ 12 [nowait]
eth0: Ethernet addr: 52:54:00:12:34:56
goldfish nand dev0: size 6ea0000, page 2048, extra 64, erase 131072
goldfish nand dev1: size 4000000, page 2048, extra 64, erase 131072
goldfish nand dev2: size 4000000, page 2048, extra 64, erase 131072
mice: PS/2 mouse device common for all mice
*** events probe ***
events_probe() addr=0xe0854000 irq=15
events_probe() keymap=qwerty2
input: qwerty2 as /devices/virtual/input/input0
goldfish_rtc goldfish_rtc: rtc core: registered goldfish_rtc as rtc0
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: [email protected]
logger: created 64K log 'log_main'
logger: created 256K log 'log_events'
logger: created 64K log 'log_radio'
IPv4 over IPv4 tunneling driver
GRE over IPv4 tunneling driver
TCP cubic registered
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
802.1Q VLAN Support v1.8 Ben Greear <[email protected]>
All bugs added by David S. Miller <[email protected]>
VFP support v0.3: implementor 41 architecture 1 part 10 variant 9 rev 0
goldfish_rtc goldfish_rtc: setting system clock to 2010-12-05 03:32:33 UTC (1291
519953)
Freeing init memory: 104K
mmc0: new SD card at address e118
mmcblk0: mmc0:e118 SU02G 1.00 GiB
mmcblk0:
init: cannot open '/initlogo.rle'
yaffs: dev is 32505856 name is "mtdblock0"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.0, "mtdblock0"
yaffs_read_super: isCheckpointed 0
save exit: isCheckpointed 0
yaffs: dev is 32505857 name is "mtdblock1"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.1, "mtdblock1"
yaffs: restored from checkpoint
yaffs_read_super: isCheckpointed 1
yaffs: dev is 32505858 name is "mtdblock2"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.2, "mtdblock2"
yaffs: restored from checkpoint
yaffs_read_super: isCheckpointed 1
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
request_suspend_state: wakeup (3->0) at 4206070790 (2010-12-05 03:32:36.48957032
7 UTC)
init: untracked pid 34 exited
init: untracked pid 42 exited
request_suspend_state: wakeup (0->0) at 4256118986 (2010-12-05 03:32:36.53963374
7 UTC)
init: untracked pid 44 exited
init: untracked pid 53 exited
request_suspend_state: wakeup (0->0) at 9387505566 (2010-12-05 03:32:41.67101886
1 UTC)
init: untracked pid 54 exited
init: untracked pid 60 exited
init: untracked pid 68 exited
init: untracked pid 69 exited
request_suspend_state: wakeup (0->0) at 14518491192 (2010-12-05 03:32:46.8020076
30 UTC)
init: untracked pid 74 exited
init: untracked pid 82 exited
init: untracked pid 83 exited
request_suspend_state: wakeup (0->0) at 19655651551 (2010-12-05 03:32:51.9391665
92 UTC)
init: untracked pid 89 exited
request_suspend_state: wakeup (0->0) at 24731037643 (2010-12-05 03:32:57.0145514
97 UTC)
init: critical process 'servicemanager' exited 4 times in 4 minutes; rebooting i
nto recovery mode
save exit: isCheckpointed 1
save exit: isCheckpointed 1
Restarting system with command 'recovery'.
Reboot failed -- System halted
+++++++++++++++++++++++++++++++++++++++++++++++++++++
LOL, root the emulated device!
I would if I knew how to do so on the emulator itself
I have rooted my actual device, but I have no idea how to accomplish this on the emulator; could you elaborate or send links on how to do this please?
I have googled and nothing relevant has showed up other than the emulator is supposed to be already root-ed; by issuing adb root I get:
C:\android-sdk\android-sdk-windows\tools>adb root
adbd is already running as root
I also tried running the emulator with the '-shell' parameter, but got the same result and the boot process gets stuck as well...
A little bit of extra guidance would be great.
Thank you.
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
Because i can not post in the Dev section i try it here.
On the new Utopia RC4 ROM the Wlan can not be activated, it just say's scanning is not possible an then it gets deactivated.
Sirius1977 said:
Because i can not post in the Dev section i try it here.
On the new Utopia RC4 ROM the Wlan can not be activated, it just say's scanning is not possible an then it gets deactivated.
Click to expand...
Click to collapse
Try reflashing because its supposed
to be working!!
Nope, didn't work. Tried to flash again via fastboot and at the second try i made a recovery version which also didn't make the wifi work.
Same message: Networkscan is not possible
dmesg output:
Code:
<4>[ 560.902218] register_mmc_card_pm: [WiFi] Callbacks registered successfully.
<3>[ 560.902608] [yoohoo] dhd_register_hwakeup : start
<3>[ 560.902848] [dhd_hostwakeup_isr] HostWakeup Get GPIO 94: 1
<3>[ 560.903240] [yoohoo] dhd_register_hwakeup : OK
<4>[ 560.903445] [yoohoo] dhd_enable_hwakeup : succeed irq 158
<3>[ 560.903810] [dhd_register_early_suspend] HostWakeup Get GPIO 94: 1
<4>[ 560.904012]
<4>[ 560.904017] Dongle Host Driver, version 4.217.91.0
<4>[ 561.104080] =========== WLAN going back to live ========
<6>[ 561.104328] mmc1: Slot status change detected (0 -> 1)
<3>[ 561.104886] (swift_sdcc_setup_power)vdd :12
<3>[ 561.107221] (swift_sdcc_setup_power)vdd :12
<3>[ 561.109586] (swift_sdcc_setup_power)vdd :12
<3>[ 561.112228] (swift_sdcc_setup_power)vdd :12
<3>[ 561.120059] (swift_sdcc_setup_power)vdd :12
<3>[ 561.121993] (swift_sdcc_setup_power)vdd :12
<7>[ 561.183765] mmc1: queuing CIS tuple 0x80 length 51
<7>[ 561.191050] mmc1: queuing CIS tuple 0x80 length 7
<7>[ 561.194554] mmc1: queuing CIS tuple 0x80 length 2
<7>[ 561.204207] mmc1: queuing CIS tuple 0x80 length 10
<7>[ 561.206143] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.207915] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.209852] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.211637] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.213400] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.215332] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.217095] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.219025] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.220790] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.222560] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.224492] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.227047] mmc1: queuing CIS tuple 0x02 length 1
<3>[ 561.228268] (swift_sdcc_setup_power)vdd :12
<3>[ 561.228515] (swift_sdcc_setup_power)vdd :12
<6>[ 561.231190] mmc1: new SDIO card at address 0001
<4>[ 561.236461] mem_prealloc: section [3] size[139264]
<4>[ 561.236671] mem_prealloc: This data is using!!!
<4>[ 561.237255] alloc static buf at cccc0000!
<4>[ 561.237451] mem_prealloc: section [4] size[0]
<4>[ 561.239636] DHD: dongle ram size is set to 393216(orig 393216)
<4>[ 561.240125] mem_prealloc: section [0] size[10312]
<4>[ 561.240371] mem_prealloc: This data is using!!!
<4>[ 561.241366] mem_prealloc: section [1] size[10300]
<4>[ 561.241623] mem_prealloc: This data is using!!!
<4>[ 561.241890] mem_prealloc: section [2] size[32768]
<4>[ 561.242338] mem_prealloc: This data is using!!!
<6>[ 561.765387] wlan0 (): not using net_device_ops yet
<4>[ 561.770128] wlan0: Broadcom Dongle Host Driver mac=00:26:e8:af:0b:bb
<4>[ 563.957310] wlan0: non-BDC packet received, flags 0x10
<3>[ 578.949398] init: untracked pid 2131 exited
<4>[ 579.974021] unregister_mmc_card_pm: [WIFI] Unregistering suspend/resume callbacks.
<4>[ 580.243393] =========== WLAN placed in RESET ========
<6>[ 580.243909] mmc1: Slot status change detected (1 -> 0)
<6>[ 580.258381] mmc1: card 0001 removed
<3>[ 580.260527] (swift_sdcc_setup_power)vdd :0
#
Hmm... also the MAC adress didn't appear the Advanced Wifi settings.
For now i'm back to RC3 and ... wifi works
It is my mistake!
Try this fix!
Hmm... simply cut & paste didn't work. How can i apply the fix?
Sirius1977 said:
Hmm... simply cut & paste didn't work. How can i apply the fix?
Click to expand...
Click to collapse
install with recovery
No chance to install in CWM
Always getting Error on applying (Status 6)
Sirius1977 said:
No chance to install in CWM
Always getting Error on applying (Status 6)
Click to expand...
Click to collapse
last fix was broken? download fix again.
Error (Status 6) again
I try to set the permissions for the .so manually
Ok... I got it
adb shell
cd /system/lib
chmod 06755 libhardware_legacy.so
exit
dont't forget to mount the system partition as r/w in root explorer
Thanks to all for the fast response.
Great ROM
Ok that was to fast.
Wifi is on and it can scan for AP's but it can't connect.
Sirius1977 said:
Ok that was to fast.
Wifi is on and it can scan for AP's but it can't connect.
Click to expand...
Click to collapse
Does your router work?
Sent from my GT540 using XDA App
Yes, meanwhile the problem was confirmed by others.
No wifi........MIROSLAV_MM where are you;-)
Edit-Forgot to add 'I love your work'
Sent from my GT540 using xda premium
sanmit said:
No wifi........MIROSLAV_MM where are you;-)
Edit-Forgot to add 'I love your work'
Sent from my GT540 using xda premium
Click to expand...
Click to collapse
RC4 has been withdrawn due to this wifi issue.
Sent from my GT540 using xda premium