yashsingh1/xdaforums huggingface dataset:
[Windows Phone 7 General] RoboDad:
I just waited for a couple of days, and then all of my Twitter contacts showed up. Didn't have to do anything. :)
[Windows Phone 7 General] elcapo24682:
yea that's because they already fixed it by that time. the prior solutions were just workarounds.
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] LexerEP:
Hey there,

finally I installed Mango. Marketplace and everything is working well.

Then i've installed "SD unlocking tool" and resized partions on my sd with

"DEV_EXTRAPART_7G.cab" to realize dualboot.

The Tool is working. My cardreader recognises the sd-card, but everytime I

want to boot wp7 I can't touch anything to insert my pin. Or without simcard I

can't click cancel or something else.

BUT: I turn OFF and ON 10 times, by dropping the battery, my hd2 get back all

functions. This isn't a solution and random :D

Anyone with me? Any idea? THX

############

excuse my english | i hope this is the right forum for this
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] michael.hu:
I have the same problem, the only thing to do, restart you phone then try it again. Good luck!
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] LexerEP:
now it happens every time by reboot :-/

sd-card problem, or maybe fix it with a new installation?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] henock:
How can i increase the download speed of my internet in usin opera or default web browser? Is there a download manager for BA if there is where did I get?
[HD2 Android NAND Development] marc1706:
CyanogenMod Kernel 2.6.35.8 for HTC HD2​

First of all a big "Thanks" to Markinus for his initial work of porting the CyanogenMod 2.6.35.7 kernel to the HD2.

This thread is for development purposes only, so don't expect any support.

If you find a bug in the kernel that hasn't been posted yet, please post it in this thread. Please use the search function before posting.

Credits: Cotulla, DFT, Markinus, hastarin, tytung, etc.

Currently working:

Data

Wifi

Bluetooth (still not sure to what extent it is working or not working)

LED Notifications

G-Sensor

Camera

Camcorder

Auto-Backlight

CPU scaling

Not working:

Boot issues with cLK while trying to boot without usb cable plugged in

You tell me ;)

Changes:

0.0.4l to 0.0.4m:

Fixed AC charging on boot & clean-up

0.0.4k to 0.0.4l:

Enabled ext2 and ext3 drivers in defconfig

Removed htcleo_usb_phy_reset

0.0.4j to 0.0.4k:

Revert: Updated usb code to more up-to-date version from desire kernel

Clean up in device files

Removed unneeded bcm4329 files

Fixed bug that prevented some AC chargers from working

0.0.4g to 0.0.4j:

Added BFS Scheduler v0.357

Raised power_collapse_khz back to 245000

Fixed incorrect setting of BFS in defconfig

Small changes to defconfig and htc_battery.c

Updated usb code to more up-to-date version from desire kernel

0.0.4e to 0.0.4g:

Reduced power_collapse_khz to 128000 (=128 MHz)

Added patch for clk

Added usb code from desire kernel

Applied rafpigna's gsensor fix for i2c

​

0.0.4d to 0.0.4e:

09.Nov.11: Solved color banding issue

0.0.4c to 0.0.4d:

07.Nov.11: Fixed usb notifier function

0.0.3b to 0.0.4c:

05.Nov.11: Enabled 128 MHz

05.Nov.11: Fixed video recording & added a few tweaks

04.Nov.11: Disabled camera led on boot (battery drain should be fixed now)

first test version to 0.0.3b:

29.Sep.11: Added smartassv2

28.Sep.11: Patched to 2.6.35.8

Kernel source:

https://github.com/marc1706/cm-on-wince-htc

Current version:0.0.4m

Note: This kernel is not designed for sense builds !!

Download:
[HD2 Android NAND Development] clio94:
I tried this new kernel in typhoon 3.6.6.Before flashing i removed initrd.gz from zip.It boots ok,bluetooth works for my bt headset (motorola h300) but 60ma battery drain.Thank you guys. :)

edit

i tried to close bluetooth and it made reboot
[HD2 Android NAND Development] djsolidsnake86:
phone work?
[HD2 Android NAND Development] clio94:
phone work ok.I made an outgoing call and i had an incoming call without problems.With wifi off,data off,gps off battery drain is 16-20 ma
[HD2 Android NAND Development] kikisp:
What a great day for hd2..first libaudio gets fixed than this...

thx devs
[HD2 Android NAND Development] YZ:
Nice thread.
[HD2 Android NAND Development] djsolidsnake86:
can you add 128mhz?
[HD2 Android NAND Development] goldlocke:
great job Marc1706!

can somebody test this on a Sense3.0/3.5 ROM without the haldric glitches fix? thx.
[HD2 Android NAND Development] bachmark:
Hi

is there a chance to boot this kernel on a SD Build?

I tried it but it stops on "Jump to Kernel"

Thanks
[HD2 Android NAND Development] pirlano:
please don't stop!!! :D big thanks!!!
[HD2 Android NAND Development] Kefir.net:
The greatest news, thank you! ;)

Running fine on Typhoon CM7!

The only problem I get is 17mA without wi-fi..and even in Airplane mode.
[HD2 Android NAND Development] theslam08:
Could not get it to boot on the new DHD 3.06 v1.3 from DUNG. Replaced the initrd.gz file, resigned but stuck at go go go. Will keep fiddling.
[HD2 Android NAND Development] tobiascrystal:
What a great day, hopefully this will prepare us for the ice cream sandwich in the near future, downloading now :-)

Well, I know it clearly states CM but gave it a shot anyways. I deleted the initrd and installed it on daekins rom and no luck, stuck at gogogo. I'm guessing something in the initrd from his rom needs updating, better luck next time I guess.

Keep up the great work.
[HD2 Android NAND Development] Moon2:
Tried it on dungphp's dhd sense 3, still has gfx glitches
[HD2 Android NAND Development] Mafioso:
Watching this thread with great expectations :-) Awesome work :D
[HD2 Android NAND Development] goldlocke:
Thanks. How did you get it to boot?
[HD2 Android NAND Development] zagzag99:
What does the new kernel version introduce?

What are the expected benefits right now from running Kefir.net 0.9.7.4?
[HD2 Android NAND Development] djsolidsnake86:
there are market FC
[HD2 Android NAND Development] stirkac:
Awesomeeeee:D now just desire/bravo .35 and hd2 flies into future:D
[HD2 Android NAND Development] g30rg10u:
any cLK zip file. its working hours.... :P
[HD2 Android NAND Development] marc1706:
What bootloader did you use?

I tested clk yesterday and was able to reproduce the usb issue. Unfortunately I'm kind of new with clk and was not able to get a dmesg log out of it. Could anyone enlighten me on how I can get a dmesg log from clk? :rolleyes:
[HD2 Android NAND Development] ph03n!x:
That is the challenge :) After the phone is locked up, it does not respond to logcat or DMESG.

But don't take my word for it, am just an amateur tester :) @arif had taken a logout, he will be of more help in having this fixed that I!!
[HD2 Android NAND Development] SlyRder83:
I'm using MAG
[HD2 Android NAND Development] Rick_1995:
Sync with cLK sources, cd into ./cLK/bin and do "oemcmd dmesg", Unfortunately that is for windows as no one really ever needed it on *nix only system. Although i could look into it if or if needed you can contribute too.

Here is how it converts kernel ram console's content and sends it to fastboot client when doing "fastboot oem dmesg"

static char charVal(char c)
{
c&=0xf;
if(c<=9) return '0'+c;
return 'A'+(c-10);
}
static void send_mem(char* start, int len)
{
char response[64]; // Fastboot protocol specified response limit.
while(len>0)
{
int slen = len > 29 ? 29 : len;
memcpy(response, "INFO", 4); // Fastboot stuff.. (response flag)
response[4]=slen;

for(int i=0; i<slen; i++)
{
response[5+i*2] = charVal(start[i]>>4);
response[5+i*2+1]= charVal(start[i]);
}
response[5+slen*2+1]=0; // set null end
fastboot_write(response, 5+slen*2); // write to usb

start+=slen; // setup for next loop
len-=slen;
}
}
static void cmd_oem_dmesg()
{
if(*((unsigned*)0x2FFC0000) == 0x43474244 /* DBGC */ ) //see ram_console_buffer in kernel ram_console.c
{
send_mem((char*)0x2FFC000C, *((unsigned*)0x2FFC0008));
}
fastboot_okay("");
}
[HD2 Android NAND Development] marc1706:
Thx for the help Rick. Now I can finally see the dmesg log. :rolleyes:

edit:

I was able to reproduce the unability to boot on cLK and that's the dmesg log:

http://pastebin.com/Rn0iSWNs

And another one after having successfully booted:

http://pastebin.com/qVyYeg8P

So this is actually related to the battery driver. Now I just need to find out why this happens. :rolleyes:
[HD2 Android NAND Development] Germypan:
hi marc, i would like to try your kernel in my cyanogenmod rom (ice-droid) but i use the clk bootloader. when you could repack your kernel with cLK support? i expect your news. I'm sure that your kernel will be perfect for my rom!! Thanks for your job, you are a big genius!!
[HD2 Android NAND Development] Visentinel:
What are if any the differences in the battery driver in this kernel compared to the 2. 6. 32 kernels?

I will explain later... I need to confirm my suspicions :) let's just say if what i think I am seeing is true I have great news for everyone.
[HD2 Android NAND Development] djsolidsnake86:
what news?
[HD2 Android NAND Development] daedric:
Sir... secrecy is not our 'motto'.

Besides... I HATE SUSPENSE :D
[HD2 Android NAND Development] Visentinel:
It's not a secret I just need to be absolutely certain of this. I have inadvertently falsely claimed I have found the solution before or found a kernel that did this correctly.

I just want to be sure before I go saying you can go buy this of eBay now it will work.

I will surely know within a couple of hours if its all good :)

I'm sure I have given away some clues by now :p
[HD2 Android NAND Development] daedric:
extended batteries... ?
[HD2 Android NAND Development] Visentinel:
Ok ok il share all my thoughts becuase you are so curious to know :cool:

Yes extended batteries but not in the common way we are used to thinking of them.

Firstly, almost a year ago i had a HTC Desire, i got an $11 shonky battery from hong kong and it worked "perfectly". The simple reason for this is simple. The battery driver running on the custom kernels and roms in the desire thread are the real thing. Those battery drivers calculate the percentage based on actual values read from the battery and battery stats, the primary indicator been voltage.

Voltage is the key.

But... the Desire is a native android phone

The HD2 is not, we may think it is now but NO it is not, and it was made for windows mobile.

The way windows mobile does battery percentages is based on currents. The winmo kernel for a particular phone is hard coded to a battery capacity and monitors current draw so if the battery is 2400mah and you have used 1230mah it probably going to start telling you to plug in the charger and turn off.

That is crap my freinds.... winmo IS crap.

Last night i was going through my draws trying to find my green laser pointer to play with my cat when i saw my other el cheap shonky HD2 2400mah extended battery and instantly i thought... HAY ! im running that new kernel i think was made from desire sources or some other awesome native android source... maybe... just maybe i can use this awesome thing.

It charged from 3.6 volts and at 3.6 it said 46% and didn't say 100% until it sat at 4.202 for over an hour. So it charged correctly and did the last 20% or so of topping charge correctly with the percentage. So far So Good.

Now this is where i am not sure if this is going to work.... that's why I am hesitant to say yes or no on this.

it was 3H 14M since i took it off the charger and came to work, the screen has been used for 46 minutes and i have %70 left at 4.06 volts. Yes it "Seems" like FINALLY we have a kernel that works properly not some third concept garbage of calculating through MAH usage but i need to wait and see and it could take hours before i truly see I have say 40% and 3.6 volts again. I know if it doesn't work my phone will be 0% at 3.8 volts,
[HD2 Android NAND Development] daedric:
I might be wrong, but android is a little smarter than that, though you're probably saying it might depend on the kernel.

Android couldn't care less about what battery you have. I trust that most roms come with a generic battery calibration, but after a few drop to 0% and charge to 100% (True 100%, not when the gree light comes on, but when the charge current is 20mA or less), Android starts guessing pretty good how many mAh your battery have. (and not how many it has printed on the label)

So, do this:

Install CurrentWidget (, activate log file if you wish, ) and let your HD2+Ext battery charge until the widget outputs 0mA or 2mA charge (or near). Then, and only then, will Android belive the battery is fully charged.

After that... let it go... waste it all! But remember, if you're on MAGLRD, do not let your HD2 be without enough charge to power on. MAGLDR does not charge the battery if powered off.

After a couple of these cycles, you should have a pretty good battery calibration :)
[HD2 Android NAND Development] securecrt:
I am using 2700mAh custom extand battery I modify the capacity parameters in the kernel (r14) . My battery can continusly use for 3 days.

infact the r14 kernel use current to calcuate the percentage but you should tell the kernel the real capacity. the capacity related to the batteries id. so if you want to custom you own battery driver first you must use dmesg cmd to find out you id.
[HD2 Android NAND Development] securecrt:
HD2 kernel report the % in kernel. the android layer is not accuacy for showing the %. if you are trying to use a none standard extanded battery(2300mAh made by HTC is standard ex bat the id is 5 in kernel defines) you MUST change the kernel.
[HD2 Android NAND Development] Visentinel:
Or stop using predefined values and measure percentage based on voltages. Global support for any battery. No need for calibration or kernel customization.

It's silly. Just run from voltages for goodness sake. I have done allot of research into lithium ion and mah draw monitoring is great for charging but terrible for calculating how much you have left, and batteries get old and degrade throwing out predefined values over time.

Deadric battery calibration does not work on the hd2 with shonky ext batteries.

What people experience is the battery drains exactly 1230mah and Android shutdown the phone. And you can't boot back up. You need to physically remove the battery and put it back in, then winmo and Android alike will show 60% and drain again.

But a good well made battery driver would ignore the dumbo hardware of the hd2 and base its analysis from reality and this will allow android to take charge "pun fully intended" and make its own ruling on percentage allowing Android to stay running until the voltage reaches around 3. 2 volts and then says battery low.
[HD2 Android NAND Development] Visentinel:
I don't know how to make kernels. I would be immensely gratefully if someone could make me a compile of this kernel that completely ignores the battery. Maybe just always says 90% forever and I will just monitor my voltage myself or compiles a capacity of 2400mah

Again please if anyone with the ability? I would be grateful :)

At the moment I have 3. 9 volts and 50% so I dont think its working out on this kernel either :(
[HD2 Android NAND Development] securecrt:
I can help you to make a kernel based on the tytung R14 magldr version 2wrec , please use dmesg command to show your battery id for me

dmesg | grep id
[HD2 Android NAND Development] Visentinel:
Thank-you so much.

I guess its is 4

<4>[ 493.765014] [D:BATT] V=3904(640) I=-2(fffffffa) C=469.0/1230(992) id=4(96) T=150(1cc) KADC=652

<4>[ 494.347198] [D:BATT] V=3906(641) I=-5(fffffff3) C=468.0/1230(991) id=4(96) T=150(1cd) KADC=659

<4>[ 495.300720] [D:BATT] V=3906(641) I=-2(fffffffa) C=468.0/1230(991) id=4(96) T=150(1ce) KADC=656

<4>[ 495.761108] [D:BATT] V=3906(641) I=-5(fffffff2) C=468.0/1230(991) id=4(96) T=150(1d0) KADC=659

<4>[ 498.726806] [D:BATT] V=3872(633) I=-203(fffffdfd) C=468.0/1230(990) id=4(94) T=150(1d0) KADC=775

<4>[ 523.870086] [D:BATT] V=3840(626) I=-328(fffffcc1) C=464.0/1230(987) id=4(92) T=150(1c8) KADC=809

<4>[ 573.936676] [D:BATT] V=3830(622) I=-367(fffffc5e) C=460.0/1230(97b) id=4(91) T=160(1c1) KADC=811

<4>[ 623.991088] [D:BATT] V=3847(629) I=-214(fffffde2) C=455.0/1230(970) id=4(93) T=160(1bd) KADC=749

$
[HD2 Android NAND Development] securecrt:
which kernel and android version are you using now?
[HD2 Android NAND Development] Visentinel:
This latest kernel and an oxygen Rom for hd2

Android 2. 3. 7
[HD2 Android NAND Development] securecrt:
can you switch to the r14 kernel firstly and to check the battery id ?

I think currently the 2.6.35.8 still not support the extanded battery.
[HD2 Android NAND Development] Visentinel:
This battery doesn't identify as an extended battery on any kernel. It's one of those people need to remove and put back while off to get the rest of the capacity.

Anyways yeah ok switch the kernel and post id under tytung r 14

Gimme 10 minutes
[HD2 Android NAND Development] Visentinel:
Same ID

<4>[ 268.390594] [D:BATT] V=3716(5f3) I=-547(fffffa97) C=731.0/1230(c29) id=4(8a) T=170(1af) KADC=776

<4>[ 318.551116] [D:BATT] V=3755(603) I=-293(fffffd1b) C=726.0/1230(c1c) id=4(8d) T=170(1a8) KADC=645

<4>[ 368.632476] [D:BATT] V=3718(5f4) I=-357(fffffc78) C=721.0/1230(c10) id=4(8d) T=170(1a2) KADC=638

<4>[ 419.858245] [D:BATT] V=3755(603) I=-326(fffffcc6) C=715.0/1230(c02) id=4(8d) T=180(19b) KADC=661

<4>[ 469.894439]

So where after a kernel for ID 4 with 2400mah capacity.

Either this kernel or tytung r 14 callrec I don't mind.

Edit ok that call recording feature is really cool.
[HD2 Android NAND Development] securecrt:
View attachment r14kernel_2400.zip

after you flash this kerenl please recharge your battery to full then use a new software named Battery Monitor Widget to log all the battery infomation

until your HD2 shutdown by itself. you can get the real capacity of your battery. if it is not 2400mAh you must change the kernel parameters to match with the real value , then you can get the right % show.
[HD2 Android NAND Development] Visentinel:
Thank-you! For the generosity of your time to help me out. My original battery is actually running real bad coz its old so that's why I have been trying to find a solution to the battery problem with unofficial ext bats.
[HD2 Android NAND Development] ph03n!x:
Let me bump this thread up - am waiting for this kernel (cLK :( ) as much as I am waiting to ICS on our phones :)
[HD2 Android NAND Development] dorimanx:
thaks for that,.i will also fix it. in my older kernel.

Sent from my HD2
[HD2 Android NAND Development] karmadelic702:
Sound / Audio Issues - Choppy sound

I searched the thread and did not see mention of any audio issues. I am running Typhoon's Nightly CM ROM (latest version) and the latest version of this kernel. I am noticing that randomly, the audio cuts out for a split second when listening to MP3s. It happens at least once per song. Is this a kernel issue or a ROM issue? I havent done much troubleshooting yet, but I plan to change kernels back to Tytung R14 to see if the issue persists. I will keep you updated.

UPDATE:

I wiped my phone, reinstalled unmodified Typhoon CM ROM (with Tytung 13 kernel), cleared all caches and the issue persisted. This issue appears to be ROM related and not related to kernel.
[HD2 Android NAND Development] daedric:
IIRC, the kernel stores battery charge in units. Some time ago, someone altered the battery driver on the Kaiser's kernel to re-adapt itself.

So, if the max unit is 1230 like in here:

And while charging the units had maxed out but voltage kept increasing and current draw as well above 2/4 mA, then the Kernel would start increasing the 1230 to something higher to compensate.
[HD2 Android NAND Development] ph03n!x:
Try deleting DSP Manager and see if the issue persists - I remember reading that the DSP Manager may not play well with the kernel's audio driver (HTC Audio Driver?)
[HD2 Android NAND Development] warrenb213:
I am now officially on the scene.

Adding in the long awaited cLK support tonight. Will be testing tonight. If all goes well, commits and kernel compile will be available tomorrow night.
[HD2 Android NAND Development] sbryan12144:
While your at it, you should help me with my 2.6.35.14 kernel ;)
[HD2 Android NAND Development] rudeblunt:
My two cents.

So, I wanted to ask... what's the deal with the _raw version added on the first post?

Also, I've been experiencing bluetooth issues I can turn BT on and it will work... if I turn it off and on again android reboots...
[HD2 Android NAND Development] g30rg10u:
it contains only the zImage (kernel) and the kernel modules.

No libs.

---------- Post added at 06:38 PM ---------- Previous post was at 06:35 PM ----------

Can i have a compiled version of the latest commit (including Nov 12, Nov 18). ?

I am currently on MAGLDR, since this kernel was not for cLK, since today i guess.

If you could provide me with MAGLDR zip file that would be great.

Thanks.

P.S. I desperately need the gsensor fix. I cannot sms anyone or play with the phone during bed time.
[HD2 Android NAND Development] marc1706:
Updated the first post with the newest compile.
[HD2 Android NAND Development] arif-ali:
attached is a cLK CWM zip for this kernel including the ramdisk from the CM7 nightly
[HD2 Android NAND Development] clio94:
i am using cm nightly 18-11-2011 magldr.Ι tried 0.0.4g latest kernel from http://cyanogenmod.arif-ali.co.uk/kernels/ but it doesnt pass boot animation without usb connection :( if i connect usb,it goes until lockscreen and it freezes there
[HD2 Android NAND Development] g30rg10u:
thanks a lot. installed already ;)
[HD2 Android NAND Development] marc1706:
I uploaded a newer version with BFS (Brain **** Scheduler).

That's version 0.0.4g with added BFS scheduler. As BFS caused some issues on Dorimanx's kernel I'd like to get some feedback first before I call this the newest version. ;)

@clio94: On cLK or Magldr?
[HD2 Android NAND Development] clio94:
Magldr
[HD2 Android NAND Development] maverick.bg:
CM 7 Nightlies and clk, with usb boots up normally but after disconnect it freezes. I'm trying to get dmesg.

EDIT:

That is from cat /proc/kmsg when bluetoth is turned off and phone freeze.

<6>[ 299.036865] -- RK ON --

<6>[ 299.250640] [BT]-- S UP --

<4>[ 328.297912] [D:BATT] V=4187(6b4) I=268(2a7) C=1161.0/1230(1069) id=4(a5) T=330(e2) KADC=1000

<4>[ 378.356475] [D:BATT] V=4184(6b3) I=294(2e9) C=1165.0/1230(1072) id=4(a5) T=330(e2) KADC=1000

<6>[ 405.165924] input: AVRCP as /devices/virtual/input/input6

<6>[ 422.760772] input: AVRCP as /devices/virtual/input/input7

<4>[ 428.440765] [D:BATT] V=4172(6ae) I=259(28f) C=1168.0/1230(107b) id=4(a4) T=330(e1) KADC=1000

<6>[ 444.062957] -- RK OFF --

<6>[ 444.065795] [BT]-- S DN --

<6>[ 448.314270] -- RK ON --

<6>[ 448.351806] [BT]-- S UP --

<6>[ 469.409637] input: AVRCP as /devices/virtual/input/input8

<4>[ 478.495056] [D:BATT] V=4172(6ae) I=160(197) C=1172.0/1230(1084) id=4(a4) T=330(e1) KADC=1000

<6>[ 478.495086] batt: ds2784_notify: 1 96 at 477128302451 (2011-11-18 18:48:50.655548781 UTC)

<6>[ 478.495635] batt: batt:power_supply_changed: battery at 477128820744 (2011-11-18 18:48:50.656097562 UTC)

<3>[ 504.932586] msm_i2c msm_i2c.0: Error waiting for notbusy (addr=66, msgs=78)

<3>[ 504.932647] msm_i2c msm_i2c.0: Still busy after xfer completion (66)

<6>[ 521.795410] Audio: SWITCH DEVICE 17280136, acdb 0

<6>[ 521.795532] Audio: SWITCH DEVICE 17280141, acdb 0

<4>[ 528.549804] [D:BATT] V=4199(6b9) I=273(2b4) C=1176.0/1230(108d) id=4(a6) T=330(e1) KADC=1000

Look at this:

<3>[ 504.932586] msm_i2c msm_i2c.0: Error waiting for notbusy (addr=66, msgs=78)

<3>[ 504.932647] msm_i2c msm_i2c.0: Still busy after xfer completion (66)
[HD2 Android NAND Development] fhasovic:
cLK still doesn't work :-(
[HD2 Android NAND Development] SlyRder83:
I'm on MAG and the same problem here to
[HD2 Android NAND Development] mdskrzypczyk:
Clk works just fine for me on Typhoon cm7. Haven't booted with USB in but booting without so far functions perfectly

Sent from my HTC HD2
[HD2 Android NAND Development] fhasovic:
I can't make it boot hyperdroid 5.5
[HD2 Android NAND Development] mdskrzypczyk:
I booted into CWM, wiped cache, wiped dalvik cache, installed zip, fixes permissions, and booted

Sent from my HTC HD2