[CAB] GSM&CDMA Project Android Port and Startup Utility [01/23] FRX04 Reference!

[arrrghhh]

Originally Posted by 2phonejones

When i play some games the g sensor or whatever doesnt seem right, like when i lean it left the game doesnt respond right. am i missing something in my startup?

Nothing in your startup would effect the g-sensor... I think it's not quite perfect yet. I just disabled it.

[demonlordoftheround]

Originally Posted by 2phonejones

When i play some games the g sensor or whatever doesnt seem right, like when i lean it left the game doesnt respond right. am i missing something in my startup?

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline " lcd.density=240 clock-7x00.a11=500 msmvkeyb_toggle=off gsensor_axis=-1,-2,3 force_cdma=1 physkeyboard=rhod400 rel_path=andboot acpuclock.oc_freq_khz=786432 "

boot

No, the G-sensor has always been a bit off. Still a work in progress I guess.

[imnuts]

The g-sensor does work, but I doubt it's accurate enough for games. I'm sure there is an application in the market somewhere that you could see how the g-sensor picks up device movements, similar to the calibration function in WinMo.

[ThrottleAbuse]

Originally Posted by t0mmyr

hmmm, i havent been able to get the 9/26 or 9/28 builds to boot, froyo or blazn....get stuck in the linux boot text screen.....

Originally Posted by chunnel

Now, I have downloaded the new version from 9/28, but both versions (overclock and standard) freeze up the phone just after selecting Rhodium 500 and clicking boot!.

I had the same issue. Click the advanced settings tab then make sure CDMA and HW3D are checked. Also go to the Enable overclock settings and try level medium or less. Mine would do the same thing when I tried to use max. Should boot up no problem.

Originally Posted by nrupalp

I just installed this from SD card and on SD card. I started it up and select RHOD400 since i have sprint tp2. it booted into xandiord okay but there is no signal. It ahs X on the bars. What am i doing wrong?

A buddy had the same issue. His startup.txt file had two separate CDMA commands in it. I think you need to add one that says "htc_hw.force_cdma=1" and delete the one that is says "force_cdma=0" or at minimum make it say "force_cdma=1" Good luck.

[Reefermattness]

Originally Posted by 2phonejones

When i play some games the g sensor or whatever doesnt seem right, like when i lean it left the game doesnt respond right. am i missing something in my startup?

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline " lcd.density=240 clock-7x00.a11=500 msmvkeyb_toggle=off gsensor_axis=-1,-2,3 force_cdma=1 physkeyboard=rhod400 rel_path=andboot acpuclock.oc_freq_khz=786432 "

boot

Originally Posted by demonlordoftheround

No, the G-sensor has always been a bit off. Still a work in progress I guess.

Originally Posted by arrrghhh

Nothing in your startup would effect the g-sensor... I think it's not quite perfect yet. I just disabled it.

You guys are usually the ones in here answering questions, but this time you all fail, epically.

The FAQ has ALL of the startup.txt in a database by the way. On another note the startup tool also correctly assigns your gsensor controls automatically, not to mention all the other stuff that people are having problems with. It could all easily be fixed by using the new start utility.

Guys, this is directly from the FAQ:

"Configure gsensor - gsensor_axis=2,1,3 - For Rhodiums"

[oZo]

Is anyone else having trouble with the new Startup Utility not allowing you to manually edit your startup.txt?
I couldn't keep the added entry about North America dialing in the cmd line.
I believe that every time I boot, using the Startup Utility, it re-writes the startup.txt
I had to create a shortcut to haret.exe to get the added line to stick.
Am I doing something wrong?

[arrrghhh]

Originally Posted by Reefermattness

You guys are usually the ones in here answering questions, but this time you all fail, epically.

The FAQ has ALL of the startup.txt in a database by the way. On another note the startup tool also correctly assigns your gsensor controls automatically, not to mention all the other stuff that people are having problems with. It could all easily be fixed by using the new start utility.

Guys, this is directly from the FAQ:

"Configure gsensor - gsensor_axis=2,1,3 - For Rhodiums"

Fail indeed. What does the different options do tho...?

Originally Posted by skank_boy

Is anyone else having trouble with the new Startup Utility not allowing you to manually edit your startup.txt?
I couldn't keep the added entry about North America dialing in the cmd line.
I believe that every time I boot, using the Startup Utility, it re-writes the startup.txt
I had to create a shortcut to haret.exe to get the added line to stick.
Am I doing something wrong?

This is how the new startup utility works... I think if you want to edit your startup manually, you cannot use the startup utility...

[NSTar]

My startup.txt gets written over somehow. now it's 0kb... had to put a new one in.

[arrrghhh]

Originally Posted by NSTar

My startup.txt gets written over somehow. now it's 0kb... had to put a new one in.

The startup utility causes this issue.

[tpdjr]

hi i am on the blazn 8-26 build and everything was working perfect until this morning. All the programs I downloaded of the marker keeps on saying x has stopped unexpectedly please try again. I tried to open the program multiple times and tried soft resetting the phone multiple times but nothing seems to fix it.
If you have any advice I would really appreciate it because i dont want to update the kernel until they have the battery meter fix built into it.