yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] cedesmith:
i don't understand... that tablet seams to come with android... so it got a android boot loader, just replace kernel/system and done.

hmm... except if partition table is fixed and need a custom partition layout... then i guess you can replace operating system kernel ( wince one for hd2, linux for tablet in question ) with lk and send another partition layout atag to kernel.

ooohh and btw is NOT my bootloader. is codeaurora's bootloader i just made it work on hd2
[HD2 Android NAND Development] Beretta93:
I'm no dev and I might say some crap, but I think nobody can't write to NAND because the whole system is read only. The only way to run custom builds right now is to install Archos' special Dev Firmware (voiding warranty by the same way), install the custom build by some complicated process, and run it from SD or, since very recently, internal flash drive.

I just thought that maybe, advising cLK would help $aur0n to run his build from NAND, but I'm not sure it would really help...
[HD2 Android NAND Development] Unconn:
I am looking forward to a flashable 1.3. Looking forward to trying this again.
[HD2 Android NAND Development] arif-ali:
system greater than 255M

@cedesmith

is it possible to increase the partition size greater than 255, i.e. FF 00 00 00 is 255, but I tried many combinations, but anything greater that FF would not work.

In the image you specify 4 HEX areas, I wanted 300M, and I tried 01 2C 00 00, which I thought would be 300M, but couldn't get that working.

Do I need to change the source code to enable that??

thanks in advance
[HD2 Android NAND Development] cedesmith:
@Unconn and @arif-ali

I am working on releasing a full package with following:

- bootloader

- modified CWM to properly reboot on any key when on off mode charging

- android build (ppp for network)

- last 24 MB fix

- binary partition editor tool for clk that will accept manual partitions, input from magldr flash.cfg and copy/paste from magldr ad listpart.

i'm going for 4in1 approach because very few seam interested in my work and i think 1 release will be more interesting.

unfortunately i have a very tight deadline at my job and i don't have enough time to work on hd2.

if someone is interested in clk 1.3 source code just ask and i will upload it.
[HD2 Android NAND Development] M..N:
How stable is ppp though when using lk, is it any different from when running android on sd.
[HD2 Android NAND Development] seadersn:
i don't understand why there's not much interest in it :( this is much nicer than the other loader i think. it's the same with charansinghs cm7, which is absolutely nice. noone sees the work envolved in and the power behind it.

i would absolutely support you in coding if i would understand code... *grmpf*
[HD2 Android NAND Development] letama:
Hi Cedesmith,

Glad to see that you solved the power collapse problem.

I'm interested in sources, I looked a little at the reset vector problem and want to see how you solved it to see if I was going the right way. Sorry that I can't help more, I'm also out of free time these days and do not know enough to be of much help.

Best,

LeTama
[HD2 Android NAND Development] Unconn:
Yes, releasing it as one install might get some people using it and would make it more official. This might help gain some interest. So far this has looked like a coding project and not much of a tool for everyday use. I hope that changes as more support for this might mean tighter inigration, like actaully rebooting into bootloader or recovery from the OS, to name just a few. I for one would like to be almost completely native and get WinCE away from my bootloader.

"...i don't have enough time to work on hd2." I hope you mean, you do not have as much time as you would like. I would hate to see this project die. I would help, but I am a hack programer and would not feel confident working on OS level, much less kernel level.
[HD2 Android NAND Development] MontAlbert:
i hear you- i think, or at least hope, that a lot of people are watching it and will jump on board when it becomes a bit more user friendly to the general public. Coming from android devices i would love for this project to work out, as i do Charansingh's....
[HD2 Android NAND Development] cedesmith:
ver 1.3

so here it is:

changes:

- removed other targets from source

- removed tinboot like wrapper, now romhdr is in crt0

- power collapse fix

- off charge support.

- misc partition check removed

more detailed info:

removed tinboot like wrapper:

before tinboot wrapper was loaded at 0x11800000 making lk part (and interrupt vectors) be at 0x11801000 and necessary for lk to relocate himself at 0x28000000. now we can tell SPL(by ROMHDR in crt0.S) the correct address where to load lk.

power collapse fix:

android kernel writes reset vector at 0x00000000 with the following instructions:

0x00000000: ldr pc,4

0x00000004: phys_address_of msm_pm_collapse_exit

when cpu exits power collapse code at 0 is executed.

unfortunately 0x00000000 is protected by MPU(Memory Protection Unit) and the code never end up in memory.

when cpu exits power collapse it executes trash instruction, crash and reboots.

the fix is quite simple and accidentally discovered :) :

until 1st NAND flash access (needed to load kernel) MPU is not enabled :eek: allowing me to modify reset vector to:

0x00000000: mov r0, #0x11800000

0x00000004: ldr	r15, [r0, #4]

this makes cpu jump at address stored at 0x11800004 and properly resume android.

the catch is that is needs kernel to save his address properly so you need a patched kernel with cLK_power_collapse.patch or phone will still reboot.

off charge support:

when phone is off and one plugs power cable phone starts as if you would press power button only with display off.

clk detects this and boots recovery with androidboot.mode=offmode_charging added to cmdline.

kernel in cwm charges the battery but it requires kernel patch off_mode_charging_kernel.patch because panel is off and is not detected making kernel BUG()

this still needs some work done on CWM to just loop till a hardware key is pressed and then reboot.

misc partition check removed:

misc partition is used by android and boot loader to send messages to each other.

supported messages in LK are boot-recovery and update-radio.

since update-radio is out of the question and recovery can be accessed by pressing home key at boot misc partition is just a waste of space.
[HD2 Android NAND Development] seadersn:
damn, and i'm not at home to test this :( but todays evening... i hope :-)

suggestion: wouldn't it be nice to have the boot to recovery function, (for that the misc partition seems to be needed) so that one can use the cm rom manager with the cm7 build of charnsingh_online for example? anyways: sounds very nice, thank you!! :)
[HD2 Android NAND Development] arif-ali:
clk 1.3

Thanks cedesmith,

I managed to create the nbh file without any issues.

Will test tonight after work, when I have patched my kernel

thanks again
[HD2 Android NAND Development] stirkac:
codesmith i think you're already ahead of magldr :) nice work i've been following this since dec '10.

i really wish to see more people booting without magldr as it really isn't needed to load android-we need it for WP7.

my suggestion: Upload a rom you're working on(or more if you have) with all fixes in kernel etc, make a batch script and readme to install it, including CWM. not much work i believe.

this way you can give people what they want and probably more chefs will start building around LK if it proves to be better.

why am i even writing this? well tbh i was little afraid for first time i used lk...command prompt, rebuilding boot.img....it's for few of us "experimenters" or people with ORD who need to have sth new every day.

just my $0.02

and keep up with good work mate
[HD2 Android NAND Development] seadersn:
is it sufficient to use custom partition size in rules.mk?
[HD2 Android NAND Development] arif-ali:
I think it is, I just changed it to 300M, and I got 2C 01 in hexeditor, so I was trying 01 2c earlier, now I know where I went wrong.

will confirm later though
[HD2 Android NAND Development] cedesmith:
if you comment SYSTEM_PARTITION_SIZE in rules.mk you can use magldr partition layout so you don't have to flash rom for clk and keep magldr rom.

if you want to switch back to magldr then all you need to do is flash magldr (i am on lk since power_collapse fix and all is great except rmnet ofc).

see init.c partitions for more on that
[HD2 Android NAND Development] seadersn:
yep, i've noticed this "behaviour" already with the last version; the partitions stay. thx :)
[HD2 Android NAND Development] seadersn:
k, testing session will begin within one hour :)

arif-ali, could you patch a kernel for me, too...? i really don't know how to do this :(
[HD2 Android NAND Development] cedesmith:
http://www.megaupload.com/?d=SXD6JDK0 quick upload of my kernel + modules i use now, is stock linux_on_wince_htc with my patches
[HD2 Android NAND Development] seadersn:
first: thx :)

second: can't get it to work :( adb / fastboot doesn't recognize the device, no matter what i've tested. with / w/o usb plugged in, with / w/o task29, compiling 'from stock' / with edited partition size etc. sry, no report possible atm :) maybe i've done sth wrong or overseen sth, i'll test it again tomorrow with more than only an hour of time ;)

best regards!
[HD2 Android NAND Development] arif-ali:
I have tried it as well,

My phone doesn't even start booting the phone

It get's stuck at the initial boot picture, i.e. it seems that it doesn't load LK

will continue to diagnose

FYI, I have tried having 300M, 250M, and commented out the SYSTEM partition variable in the rules.mk, all did the same thing
[HD2 Android NAND Development] despy1989:
Hi Cedesmith

I am not a coder or programmer but do have a HD2 to spare. I have 8 months of ROM flashing experience ;) though.

If you need a tester for your loader and ROM be happy to to donate time as needed. I still follow this thread and watch the development very closely. Please keep up the good work and drop me a PM if you need a testing device-person.

:)
[HD2 Android NAND Development] dharvey4651:
Done. :cool:
[HD2 Android NAND Development] cedesmith:
CWM 3.0.0.6 with off charge fix

CWM 3.0.0.6 recovery img with fixed off charge and patched kernel built from cyanogen git for leo.

patch details in post #2

EDIT: recovery image attachment removed due to newer version on post#1
[HD2 Android NAND Development] seadersn:
nice, now it's almost complete :D do you have an idea what could be wrong @ our compiling trials...?

is ppp enabled in your kernel?
[HD2 Android NAND Development] arif-ali:
My compilation, this is with no changes

http://pastebin.com/7kgjQfxb

My diffs from compile and compile-arif

--- compile	2011-02-23 01:00:56.000000000 +0000
+++ compile-arif	2011-02-25 22:00:38.000000000 +0000
@@ -1,5 +1,9 @@
#!/bin/bash

+export ARM=/home/arif/android/HD2/android/kernels/arm-2010.09/bin
+export WINE=/opt/cxoffice/bin
+export PATH=$ARM:$WINE:$PATH
+
#use codesourcery toolchain
TOOLCHAIN_PREFIX="arm-none-eabi-"
export TOOLCHAIN_PREFIX

I am running Ubuntu 10.10 amd64, and have crossover's wine. I have tried with root and as a user. same results

The unfortunate problem is that, there's no errors, logs for debugging. Unless there is a way to totally remove the initial boot screen image, and see what is happening. Is this possible?
[HD2 Android NAND Development] cedesmith:
I did not upload one on purpose.

I need ppl that try it to be able to understand that they need to build boot.img with patched kernel so compiling cLK was intended as a filter.

I think it may hurt adoption if ppl try it now and it reboots and/or does not work because is still in [DEV] and they don't understand the steps needed to properly use it.

4 the ones it hangs:

hspl version, radio version and panel type (from dmesg) would be useful

since you ware able to compile it can you try to find where it hangs.

add to htcleo_boot_s.S

.global htcleo_flash
htcleo_flash:
ldr r4, =0xa9000864
ldr r5, =0xa9000814
orr r6, r4, #0x200000
str r6, [r5, #0]
bx	lr
.ltorg

then place htcleo_flash(); in init.c/other code to see if camera flash turns on and execution reaches checkpoint.

i think it hangs at display_init because different display type but is just a guess as 4 me everything is fine.
[HD2 Android NAND Development] arif-ali:
HSPL3: 2.08

radio: 2.15.50.14

panel type: see below

$ adb shell dmesg | grep -i panel
[ 1.486694] Init Panel
[ 1.486755] panel type is 1 :board id is 4 : AUO
[ 2.476959] msmfb_probe() installing 480 x 800 panel

FYI, your compiled version of 1.1 worked for me without any problems, other than I didn't have the PPP options in my kernel at the time, so therefore didn't use it.

will debug, to see what I can find, on where it is having a problem

btw, again thanks, and I have removed my file from the previous post

Edit:

OK, I have tried now compiling 1.1, 1.2 and 1.3, but none of them work. I have a feeling there is a problem with my build environment. as the clk1.1, binary from the first post works.

it doesn't even get to keys_init(); I have tried putting the htcleo_flash into init.c before that call

will continue to debug...

Will try on 32bit machine, could be that ...

Edit 2,

Tried on 32 bit OS, same problem. I found differences between your compiled version compared to mine.

Which version of codesourcery are you using. So at least we are at the same level
[HD2 Android NAND Development] cedesmith:
hold call for console, home for console+recovery, back for fastboot+console keys during bootup. it should will display console as in 1.1
[HD2 Android NAND Development] safwan1982:
most of the rom has bluetooth problem and no one know solve it, the problem is when i switch the bluetooth the battery dies very quickly 4 to 5 hours only.. is this the same as the other roms.. please help with solving bluetooth problem, i know that there is fix for gps which it take 1 minute or less to loadup..
[HD2 Android NAND Development] songokussm:
Could someone post a noob guide for me. I tired and fot fastboot to flash, but nothing happend after.

so maybe im not understanding. Once i get cwm working can i flash any cwm for thr hd2? Typhoon's CM7 currently has my ORD under control, but... I want to try this way.

Thank you for all you've done for the hd2 community.
[HD2 Android NAND Development] Blaggah:
Please make a tut vid on how to flash the patches to phone, it'd be greatly appreciated.. Thanks.
[HD2 Android NAND Development] clio94:
is it possible in next version to have clockwork recovery inside the ruu.nbh;

what is my thought behind this;

sometimes i want to use wm.so i have in my sd card a wm cooked rom renamed to leoimg.nbh and then i go to bootloader and flash it.then when i want to go back to magldr and nand android i put in root of sd card magldr.nbh renamed to leoimg.nbh and flash it

but... i must use pc to flash again cwm.

so my point is if your bootloader could flash recovery from device.and we`ll able to switch from wm to nand android and vice versa directly without need of a pc
[HD2 Android NAND Development] arif-ali:
After several days of testing and compiling, It was the when compiled with arm-2009q3 that worked both 2010.09 and 2010q1 don't work, and at least now cLK boots.

cedesmith, maybe useful to put that in OP

Now testing the OS side, will report back soon

Edit:

Android OS, and recovery installation works without any problems

The PPP connnection seems to have a problem, not sure what this is, as this worked again with 1.1, If I can get this working, that would be the final straw, and a full convert
[Surround General] xSebast:
Hi, i was looking some information about how to access the Surround via MyPC window, apparently it comes hidden by Zune.

I found a few steps on how to enable it.

1. Open Windows Registry Editor by typing regedit in your start menu

2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB

3. Perform a search for ZuneDriver

1. The search should yield a result similar to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_045E&PID_04EC&MI_00\6&27ffd631&0&0000\Device Parameters\WUDF

4. Click up one level to the Device Parameters key

5. Change ShowInShell from 0 to 1

6. Change PortableDeviceNameSpaceExcludeFromShell from 1 to 0

7. Change EnableLegacySupport from 0 to 1

8. Change EnableDefaultAutoPlaySupport

That's it! You can now plug your HTC Surround into your Windows PC using the supplied USB cable and it will be recognized as a USB drive.

(source: MobileTechWorld)

Hope this help! :)
[Surround General] eegorr:
If you make those changes only, your Windows Phone will appear twice under portable devices. There are a couple more changes you should make to the registry - one of them is to fix this (don't remember which one):

Under Device Parameters, you should see two sub-folders: one is called WUDF and the other is ZuneDriver.

1) Under WUDF, you will find a key called Exclusive - change the value of this key from 1 to 0.

2) Under ZuneDriver, you will find a key called UseWpdPrivateInterface - change the value of this key from 1 to 0, as well.

Now you should see only one occurrence of your Windows Phone in the Portable Devices section.

Don't forget to close the Zune software if it opens when you connect your phone.
[Surround General] itsjaylin:
Great :) It works for me!
[Surround General] boochye:
thanks that worked but no internal folders are shown under storage. can i transfer custom ringtones to the phone with this change?
[Surround General] rjotto1@pacbell.net:
HTC As A USB REG EDIT Question

The last line of the instructions say to change the EnableDefaultAutoplaySupport

but doesn't indicate what the change should be. I would assume if it is '0' then the change should be to '1' ? Just checking. Thanks.
[Surround General] rjotto1@pacbell.net:
One other quick question on this - if these changes are made, then can ZUNE still interact with the phone, or do you have to change these back?
[G2 and Desire Z Themes and Apps] Beagan:
How far have people got with over clocking their Visions?

Mines over clocked at 1GHz, i don't think id be increasing it any time soon think it would ruin my battery life

How far have all you all got to? Stable of course :)
[G2 and Desire Z Themes and Apps] Beagan:
just realised its in the wrong thread sorry il repost in the right one, sorry for an inconvenience caused
[G2 and Desire Z Themes and Apps] wileykat:
You didnt need to open another one. For future ref,.... Just hit and a mod will move it. I'll do it now.
[G2 and Desire Z Themes and Apps] Beagan:
where is that icon btw? i cant seem to find it
[G2 and Desire Z Themes and Apps] wileykat:
Yeah, its tiny aint it. Good job for asking.
[G2 and Desire Z Themes and Apps] shadyx513:
i've got the flashable zip and i'm set to 1804 Mhz and running o so smooth, to save battery i dim the screen and use 2g whenever not using the web
[G2 and Desire Z Themes and Apps] KCRic:
Holy sh** son! I used that kernel for a bit just for fun a few times, you don't tick away at 1.8GHz all the time do you? 1.1 - 1.2GHz for me all the time.
[G2 and Desire Z Themes and Apps] Delta105RUS:
My G2 Is oveclocked to 1.51Ghz. I am running DezireZ ROM Vitreous v1.81. Great sense rom.

Sent from my HTC Vision
[G2 and Desire Z Themes and Apps] stafly17:
yeah the G2 FAST rom is amazazing. As long as you set profiles for screen off, temperature, and battery life.... you are gravy. mines clocked @ 1.89 for about 1/2 the day, and i only charge my battery once a day. JUST MAKE PROFILES!!!!!!!
[G2 and Desire Z Themes and Apps] Ibleedandroid:
If you give cyanogenmod a shot it comes with a 1.516 kernal.. I get quad scores in the 2200 zone. If you use rom manager (koush is a hero!) You can download cyanogenmod 6.1.1 and do a backup if you don't like it.

G2 CM6.1.1
[Fascinate General] DarthCivicus:
Just curious because I'm not sure how this works but if Verizon switches to 4g like they keep advertising is the Fascinate going to be compatible? Or will everyone wanting 4G have to upgrade their phones?
[Fascinate General] lthibeault:
the fascinate does not have the needed hardware for 4g connection.

however you will still have 3g on the fascinate... and 4G will take a while to spread to most of the country.
[Fascinate General] devistator18:
Well we should still get 3G coverage, but our phones to not support LTE(4G). I am not even going to bother with LTE until I have coverage where I live anyway. They have it in denver, but I only go up there once a month so it's basically useless. I spend more time at home and school and use the wifi, which is usually better than 4G.
[Fascinate General] uslacson1:
This is from Verizon Q & A for 4g LTE

Can I use my current 3G device on the 4G Mobile Broadband network?

No, as Verizon Wireless introduces new services, such as 4G Mobile Broadband, you will need to purchase new 4G devices to take advantage of the 4G network. However, you will still be able to use your existing devices for the foreseeable future on our 3G network.
[Fascinate General] s44:
LTE = data surcharge and probably a cap

I'll stick to 3g.

Swyped from my Voodoo-powered Fascinate via XDA
[Fascinate General] AlexDeGruven:
Possible, but not confirmed. Sprint was pretty up-front about the EVO and Epic requiring additional data plans when they were announced. Verizon has been quiet about it so far.

But then, they also haven't announced any devices yet, so they might be tied in there.
[Fascinate General] J Shed:
There's a data surcharge and cap on 3g. Lte data will probably just cost more per month.

Considering the 2g network seems to be still active, you should be fine with 3g devices for a while.
[Nexus S General] dls5375:
In phone info ns uses GSM/cdma auto(PRL) as default while n1 uses WCDMA preferred. Does anyone know why the change, what's the difference, which ones better. I've tried switching but haven't noticed much difference. Any thoughts or info would be appreciated.
[Nexus S General] RogerPodacter:
i dont know, but on my nexus one since day one i have always switched from wcdma preffered to gsm auto (prl) and always got better battery life from it. and it still uses 3G just fine on that setting. its something to do with the preferred roaming list and not searching for other networks i believe.
[Nexus S General] unremarked:
Link: http://bit.ly/dYhO1v
[Nexus S General] dls5375:
Thanks for the link. That's exactly what I was looking for!
[Nexus S General] leyvatron:
same here but my nexus s won't save under any other settings.
[General Questions and Answers] zanderdk:
On apple phones you can use 2 fingers to move around and zoom at the same time.

in android browser you need to zoom then release and use one finget to move around.

My question is are there any browser for android there can do the same as iphne?

Samasung galaxy S
[General Questions and Answers] shubh.27hd2:
I don think so... not yet.. btw iphone .. dont even compare..
[General Questions and Answers] kushXmaster:
Opera mobile has pinch to zoom. The default browser should have it also.

Sent from HTC HD2 using XDA app.
[G2 and Desire Z General] Beagan:
How far have people got with over clocking their Visions?

Mines over clocked at 1GHz, i don't think id be increasing it any time soon think it would ruin my battery life

How far have all you all got to? Stable of course
[G2 and Desire Z General] PanCubano:
That I know, we're at 1.8ghz so far. I keep mine at 806mhz all day since I barely use it throughout the day. Once I get home, I clock it up to 1.5ghz when I'm using it.

I've ran it once at 1.8ghz running a couple of benchmarks (linpack, neocore, quadrant)

It did very well, but, ran very hot (could be due to the fact I had it connected to the charger at the same time)

Either case, how much you get out of your battery depends on how you use it, how you set up your cpu profiles (dependant on which you use. I.e. cpu tuner, setcpu), and what frequency you're constantly letting your phone run on.