yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] kapollo:
xmoo I know that the Kaiser's drivers have problems :). I was curious if Vogue has similiar problems, and since it doesn't, did someone tried to port them to our kernel?
[Tilt, TyTN II, MDA Vario III Android Development] Orphee:
I tried Android on my Kaiser, and I must say it is really not stable !

I crash really often, I must soft reset, i can't use it more than a few seconds if I try to use navigator or maps... :/
[Tilt, TyTN II, MDA Vario III Android Development] shylohmonster:
WOW - must investigate further. I reckon checking on this will be added to my list of daily addictions. Thanks for the info.
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
I put a link into the README.txt where you can see what happens when the SD problem occurs. see http://headfuzz.co.uk/files/android/sderror-extrapolated2.txt :

baz added/changed printks to make the nature of the problem show.

And yea that is the thing that keeps us from providing android images where you can make data persistent on SD. If you wonder now "why don't they save it in the itnernal flash?" That's because we have the NAND driver not working at all yet, so it is only possible to access the SD card from within linux.

edit2:

We didn't put images with the emulator filesystem from 0.9 sdk yet because they are too big to boot as ramdisk. If you are interested, fetch the the system.gz from dzo, gunzip, mount it with loop option (it's an ext3 image file) and remove some non boot/use critical stuff until the image gets smaller than 20M in gzipped state. Then you can cpio pack and gzip it and boot it as ramdisk. dzo suggests to

delete all images, unused libs and all the contents of /data

edit3: @xmoo can you change the topic into something like "Linux and Android for Kaiser" ?
[Tilt, TyTN II, MDA Vario III Android Development] dbo87:
QUESTION

I was reading, and I saw that there wasn't a radio created for this yet and was wondering if anyone knows if anyone is working on this and do you think it may be completed so that you would be able to make/receive calls, and also if you flashed to the android then wanted to flash back to any other rom, would there be any real issue ????
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
....

Android runs like a program on top of windows mobile at the moment. nothing touched, nothing lost, nothing flashed. Call and Data are also working, more or less.
[Tilt, TyTN II, MDA Vario III Android Development] dbo87:
Oh ok thanks shadowline, so after you were to flash and it boots successfully, do you have to do those steps that were shown in the 3rd posting, the whole creating zImage process??? sorry not trying to be a pain, just trying to understand
[Tilt, TyTN II, MDA Vario III Android Development] icewhitenewyear:
You're probably not going to have to worry about that. And once again you dont FLASH. Right now it boots out of a kernal, like linux, You open a program and press start. There is no loss of your data on your phone, no flashing issues. But at the moment we are currently working on getting Andriod 0.9 Working.
[Tilt, TyTN II, MDA Vario III Android Development] o2xdaexec:
ive got lost reading this post,what do i download and where from to try it
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
sorry but this is wrong. we must run the bootloader from windows, but after the linux kernel is booted from there, windows does nothing, it doesn't run in the background or below linux or however you might call that. it's simply gone and linux is in charge of the system processor.

regarding the modem flash person: we don't need a different modem for use with linux and can use the normal radio roms.

maybe you stumbled across that question because windows/linux are different operating systems and thus there could be a compatibility issue. but that thought is wrong since the modem is an autonomous entity, what it provides is neutral towards operating system compatibility. you could communicate with the modem from virtually any operating system. hope this helps
[Tilt, TyTN II, MDA Vario III Android Development] xmoo:
Download the files in post #1

Copy to your phone, run Haret.exe and boot linux.

Haret is a program what boots up linux/android.

So no rom flashing or whatever is requierd.

It's easy, just read good :)
[Tilt, TyTN II, MDA Vario III Android Development] o2xdaexec:
will i have to load windows back on again after
[Tilt, TyTN II, MDA Vario III Android Development] badbrad4080:
NO, as stated before the way it works is you boot windows run the boot loader (haret.exe) linux loads and takes control of the cpu, windows is dropped meaning not being ran anymore, not meaning deleted, all you have to do is soft reset and windows will boot and redo the process of running haret to load android again and no you cant exit android and revert back to windows you have to do a soft reset.
[Tilt, TyTN II, MDA Vario III Android Development] o2xdaexec:
haa i get it now... i think sorry for sounding thick.right just put it on and wow its mint just very plain and simple comes up really quick gonna play somemore at work tmorro.well done guys
[Tilt, TyTN II, MDA Vario III Android Development] spiritofseth:
nice

Great Progress so far, my buddy saw a dream the other day from an HTC exec, very nice reviews. long live the FOSS movement.
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
I meant only to simplify it, that it is run as an app from windows mobile, and not like a rom flash. :D
[Tilt, TyTN II, MDA Vario III Android Development] xmoo:
HAHAHAH +1 for this one.
[Tilt, TyTN II, MDA Vario III Android Development] gthing:
Anyone? Anyone?
[Tilt, TyTN II, MDA Vario III Android Development] Rhys'Droid:
enatefox, I apologize if I am coming across as a newb, I do feel that I know a little bit (definetly still learning...its a process...haha) about this stuff. I'm pretty sure that I understand how Compcache works...it allocates a certain portion of RAM for itself, which it compresses and gives to the system as a swapfile (obviously much faster than a "physical" swapfile since it is in ram). I am using "free" to keep tabs on how much of the compcache swap is being used by the system, and it usually is not even close to being fully utilized even when I have a 32 mb cache size, so I am not sure how having a larger cache will help. I understand the ROM issue slightly less, but what you are saying makes sense. I guess I am just somewhat confused as to how the ROM that I am using (unchanged for several months) is suddenly adversely affecting Android. Bleh...perils of running "unsupported" software I suppose...haha. Thanks for your help and patience, trying to become a little bit more informed every day!

-Rhys

meh...I think that I am going to make a stripped down Rogers build for myself tonight...that seems to be the system that has historically worked the best for me...
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
Well, after HardSPL erased itself from my phone, I've still never been able to install it again and ROMs have had a shelf life since-- when things go bad I have to flash again. I don't know why but point is that things can just happen even if it worked before.

From what I understand (pmos69..), compcache has a "pressure" setting just like how Android's Dalvik VM has a process killer when it feels it's nearly full. Consider scraping cake mix out of a bowl-- it's easier to get the first 1/2 but it gets more and more difficult as you run out-- it takes more effort to get less return. At the sweet spot is where things will tend to reside. In my case that's usually 40-60MB of cc in use of 100MB total. If I just put the size to 60MB it might hover around 25-35MB for the same reason.

Hope that helps explain it somewhat in pseudo-science.
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
No, that's not OK. It should be board-htckaiser.panel_type=1 (or 2 or 3).

Also make sure you have pm.sleep_mode=1 (not 0).
[Tilt, TyTN II, MDA Vario III Android Development] plutarcian:
ok ill give it a try. but form what u say i think u have a pretty fast runing build. ill try and see if the comcache thing works but can u post ur conf file. and a link to the ROM and radio u using. i wouldnt mind flasjing a bare rom just to get android usable :).

also can u tell me if the SWAPINESS in the conf helps. or should i put it to 0
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
Well, I made a crappy video of JACHeroSki1.6r2a with compcache @ 100MB and after using it for a little bit to let things settle.

For an everyday, I'm using:

Blurry Hero.

10-15 zImage

10-15v3 base files

conf file is untouched except for compcache disk size.

Until of course we get Tattoo/Donut bugs fixed or my hands on the new Magic ROM
[Tilt, TyTN II, MDA Vario III Android Development] plutarcian:
wow that was a quick response. thnx for the video link. restored my faith in hero :). rom and radio info would also help. ill try ur settings in the morning. its 4 AM here and i think im need some shut eye :).

by the way, does your cell tpwer based location work?? never worked for me
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
Blurry Hero runs a little faster. I have the stock ATT ROM and the radio I think is 1.6x something. I only tried network location which said I was 500 miles off but I don't ever need it-- I know where I'm at.
[Tilt, TyTN II, MDA Vario III Android Development] xxbabiboi228xx:
You have to make sure location services are installed and location picker is installed on any Hero build sometimes who ever ports the hero build they leave those apk.s out.
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
Doubt: Originaly, dafault/startup.txt also had lines for "overclocking" the MSM to the same speed of the diamond and such.

Why were this lines removed? IS the MSM7200 overclocked by default now?

Are we still able to overclock it? Is it worth it?

# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller

# clock-7x00.mddi - MDDI clock (try 0xa51 or 0xe2c)
# clock-7x00.ahb_div - Advanced Host Bus divider, default is 4
# 2 is faster but uses more power
# clock-7x00.a11 - ARM11 clock speed in MHz, best to leave this alone

Second Doubt: Do we still have hardware OpenGLES ?
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
The overclocking should still work but I don't use it since it will make the device less stable. The only one I use is the ahb_div, making it 3 doesn't seem to affect stability and gives a slight increase in performance.

Yes, hardware OpenGL-ES should still work.
[Tilt, TyTN II, MDA Vario III Android Development] Rhys'Droid:
enatefox- well, I'm going to try flashing back to the official AT&T ROM. Do you think that I need to revert the SPL too? Right now I've (obviously) got HardSPL installed... Thanks again for your explanations, they have been quite enlightening.
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
There's a lot of ROMs to pick, just grab one. Search this thread for what people are using like Hyperdragon, Iolite and AthineOS. Leave HardSPL always.
[Tilt, TyTN II, MDA Vario III Android Development] Rhys'Droid:
Already chose one ;-)

(I know better than to ask anyone something like "what ROM is the best!???! OMG! I can't use the search button!!" lol)
[Tilt, TyTN II, MDA Vario III Android Development] xxbabiboi228xx:
My opinion i think

Garmin.DK.10.Naked

for the battery life.That all you really need to worry about if your running android all the time.Plus you dont really have to have a fancy rom if your gonna be running android all the time.Me i went back with the stock rom like 3 weeks ago not that i was having problems with

Garmin.DK.10.Naked

really all you need is a stock rom with

Advanced Configuration Tool

installed so you can go in and enable everything in

Power Management

for good battery usage
[Tilt, TyTN II, MDA Vario III Android Development] Rhys'Droid:
Yep, I had been running a pretty minimal ROM (witschey's Minimal 6.5), but it has started to give me issues, so I'm going back to the AT&T official ROM. Do the settings from Advanced Configuration Tool carry over in any way to Android? I hadn't even considered that possibility, although with the new found understanding of "the ROM" vs "WinMo" bestowed upon me by enatefox, that shouldn't surprise me I suppose...
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
No, maybe power or GPS if you disable it. Any hardware related settings may carry over to Haret
[Tilt, TyTN II, MDA Vario III Android Development] tyeo098:
Ok The reason I went through the trouble of installing andriod again (no microsd reader) was for the awesomeness of the camera.

Now the phone app crashes. Yay. Is this bothering anyone else?
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
The inbuilt camera apps don't work. You need Pro Paint or fxcamera apps and it will work.
[Tilt, TyTN II, MDA Vario III Android Development] tyeo098:
Well that's odd because the built in camera app works fine for me. I just can't make phone calls or send txts.
[Tilt, TyTN II, MDA Vario III Android Development] mad_bouy:
Sorry For asking a Noob Question. But are you telling me that the batter power from the Android system is dependant on what type of WM rom you have installed. Whether it is WM 6.1 or 6.5??
[Tilt, TyTN II, MDA Vario III Android Development] 160bpm:
Yep, i have changed my Radio ROM and had better battery performance... to bad for me that the Radio ROM was not working correct for my place so i switched back.

But it is true that it is different when you use a WinMO with a Radio ROM and try out...
[Tilt, TyTN II, MDA Vario III Android Development] plutarcian:
finally its getting better.

hey enatefox i tried what u suggested. flashed an official rom (HTC). i dont have ATT so i didnt try that rom. will it lock or something my phone if i try that. the reposnse is pretty better with the htc rom and setting cc_disksize=100 ( the comment in front of it says 1 to 98 ???) ill try the roms suggested here aswell.

p.s. the radio now is 1.7 something

thtnx for all the help.
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
Stability... should we fear overheating/damage ?

Otherwise i would test the OC... question is...

Which values should go where? the DIV i have at 2... but the Hz one i can't remember...

One thing i noticed, is that on API Demos... the OpenGLES section... nothing works... no error... just black screen... can it be the resolution/lcd density ?
[Tilt, TyTN II, MDA Vario III Android Development] 2girls1cup:
for me the inbuilt camera app works. fx camera doesn't work for me weird
[Tilt, TyTN II, MDA Vario III Android Development] tyeo098:
Can you make phone calls with the latest files?
[Tilt, TyTN II, MDA Vario III Android Development] j101399j:
I have found the normal camera program only works with ION, I have to use the other program with Rongers and Hero.

One hing wierd, when I try and load the latest Rogers, after the harnet cods runs, I get a blank screen with the button lit up. I let it sit for 45 minues, and it never started, I saw a post on this before and they said something about the system file? not sure. Anyone else have that problem?

[EDIT] I just copied the new basefiles, along with the brand new kernel and roofts files from the vogue-hero site and I was able to get the system-kb7sqi-magic.mod.themed.img (newest roger's build) working. It stayed blank for about 5 minutes and now works perfectly. Don't know if it matters but here is my default txt (with mddi at 320 X 480):

set RAMSIZE 0x07000000
set RAMADDR 0x10000000
set MTYPE 1553
set KERNEL zImage
set initrd initrd.gz
set cmdline "ppp.nostart=0 mddi.width=320 mddi.height=480 msm_sdcc.msmsdcc_fmax=32000000 pm.sleep_mode=0 board-htcvogue.panel_type=1 no_console_suspend"
boot
[Tilt, TyTN II, MDA Vario III Android Development] tyeo098:
Does your camera app work? It seems to crash on me.
[Tilt, TyTN II, MDA Vario III Android Development] MiZi666:
it is possible to install the new market on any systems? like the blurry hero (love this..)?

when it's possible, how do i install it/remove the old market?

or can someone build it into a blurry hero? or any blurry sys..?
[Tilt, TyTN II, MDA Vario III Android Development] cybershrike:
Hi guys, I've tried a few builds and keep getting different issues each time. Currently running xROM1.5 with all the latest files but I can't seem to a) get connected over 3g (but wireless works) and b) make phone calls.

Camera doesn't work either, but that's not a deal breaker.

Shame as well, was looking forward to running Android day to day! Any suggestions for a ROM that plays nice with T-Mobile UK?
[Tilt, TyTN II, MDA Vario III Android Development] polyrhythmic:
forum double post error, apologies
[Tilt, TyTN II, MDA Vario III Android Development] polyrhythmic:
Running Blurry Hero with the new compcache thanks to kb7sqi. Very snappy.

The new camera driver does show me a picture in fxCamera, until I click shoot! Then it's a digital mess of green or white zigzags.

I'm working on getting a stable overclock with this Blurry build... wish me luck.
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
Same on the camera, at least with Hero. All's good until you click. Tried 3 apps. Clearly full resolution though. Maybe there's a combination of apps and files to get it to work.
[Tilt, TyTN II, MDA Vario III Android Development] polyrhythmic:
Overclocking: Data, questions, and tests

Alright, I've been working with the CPU settings, Googling, and even tried #htc-linux -- and all it's given me more questions, as I don't want to fry my device.

DATA:

clock-7x00.ahb_div is the 'PLL for the Advanced Host Bus'. Default is 4

clock-7x00.a11 is the setting for the clock speed. Default is 400 Mhz

Now from Dzo's new kernel:

clock_7x00.slow=1 Allow cpu clock to be slowed [off by default]

clock_7x00.voltage=1 Allow cpu to change voltage [off by default]

QUESTIONS:

From what dzo said, it seems that the AHB works like the reverse of what I'm used to with the FSB on desktops: Instead of the ARM chip determining its frequency by multiplying the AHB, the AHB determines its frequency by dividing the ARM11 frequency.

I asked this in #htc-linux since I know those guys are familiar with the ARM internals, but unfortunately they ignored my request and called it useless :confused:. The reason it's important to know the difference is so that I don't fry my chip by setting the div=2 and the a11=528 and ending up with a clock speed of 1056 :eek: . Can someone confirm that the AHB freq is dependent on the ARM11 freq and in no case is the other way around?? What am I actually speeding up (display, memory, SD card access?) with the div, and why is that more stable than the a11?

TESTING:

I can get Blurry Hero to run with the div=3 and no a11 setting, but that is the fastest stable setting. I can get BH to boot with div=4 and a11 settings of 480, 500, or 528, but they all freeze between 1 and 5 minutes after boot. I get the farthest watching the console logs... with any a11 overclock BH crashes quickly as soon as I try to view the SenseUI or unlock the screen.

BH Boots with div=2, seems to be much slower to boot, but speeds up after a few minutes. Hard to tell if it's actually faster.

The most responsive Android I've used was 9-Sept-09 mssmisson ION build, with div=4 and a11=528. A 25% overclock made a noticable difference so I'd love to see that again, especially now that clock_7x00.slow and .voltage are possible the clock speed should have a much lesser effect on battery life -- which was the main problem with overclocking before.

Lastly, is anyone seeing a noticeable difference with elevator=noop? I don't seem to.
[Tilt, TyTN II, MDA Vario III Android Development] polyrhythmic:
SIDENOTE: Is there anyone in Seattle running Android on Kaiser? I've never been able to get Cell Tower Location to work in any build... it always puts me right next to Golden Gate Park in San Francisco.
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
The AHB clock is definitely derived from the CPU clock rather than the other way around. The AHB clock isn't the main memory clock but it does govern the A11 read,write and dma speed. I did some experiments and it made about 10% difference changing it from 4 to 3. (see attached diagram for where the ahb fits in).

To get the CPU overclocking I used a spare PLL but i'm not completely sure that this PLL is never used so the crashes may not be due to the overclock but to the device trying to use that PLL for something else. The clock slow and voltage probably aren't compatible with overclocking because they may change the voltage when using a high clock rate. In any case these option don't seem to make any difference to power consumption.

Contrary to what other people may say a high CPU clock does not necessarily use much more power than a lower one. The ARM is very good at slowing it's clock when idle. When the OS is not doing anything it calls msm_idle which executes a SWFI (suspend and wait for interrupt) instruction that effectively slows the clock to 0. Only under heavy load does the current consumption go up (you can see it using "cat /sys/class/vogue_hw/battery") and even then this is completely dominated by the power used by the backlight.

Try it and see, you can change any of the boot parameters on the fly by writing values to /sys/module/clock_7x00/parameters/xxxx (though some need a power collapse to take effect). Use a separate adb shell to run a loop to load up the system. Even the leds make more difference than changing the cpu clock.
[Tilt, TyTN II, MDA Vario III Android Development] cybershrike:
Dang, I decided to try Blurry Hero and it just sits on a loop screen of "Hero" then "HTC" over and over. This is with the latest rootfs and zImage from kb7sqi, just won't load though.
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
cybershrike, try the data image I uploaded to Vogue Hero GC. It's got some Sprint apps cached on there but they won't affect anything. It will solve that problem, or does for me anyways. BTW, Sprint apps work on Hero.

Also, I'm working on some themes. Hopefully I'll have time to finish Hero and Rogers so I can drop it on the vanilla builds. I'll upload them with screenies when I'm done. Any requests/images would help
[Tilt, TyTN II, MDA Vario III Android Development] loserskater:
also make sure you have "mddi.width=320 mddi.height=480" in your default/startup.txt
[Tilt, TyTN II, MDA Vario III Android Development] cybershrike:
Ahh that could be it, I'm using 312 x 416:

@enatefox: is yours the HeroBlurry_9-25.sqsh?
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
Yea, that was made by Zenulator but I re-uploaded it. Your res is definately wrong.
[Tilt, TyTN II, MDA Vario III Android Development] cybershrike:
Just realised I'd forgotten to change my panel density.

Tell you what though, that Hero loading screen is well swish with it's drop shadow and strobing light.

Yeah I've probably seen enough of it now.

EDIT: Just hung again, but the power buttons worked? Very strange! That's after changing all my width and panel settings. Going to give jacheroski2.2b a whirl
[Tilt, TyTN II, MDA Vario III Android Development] j101399j:
Nope, sorry I was wrong, I can only get the camera to with the Ion build. All others crash.
[Tilt, TyTN II, MDA Vario III Android Development] polyrhythmic:
I can confirm this. When clock slow and voltage are used with the overclock, Haret doesn't even boot out of WM.

I have a standard battery and although Android uses more power than WM (mostly due to constant data use) I didn't notice significant loss due to OCing. Glad to hear you confirm it. If there's no battery life improvement, what advantages do clock slow and voltage have?

Hmm, this sounds a little dangerous, but I might try it. Thanks tons for your diagram and explanation, I have a much better difference of what is going on now. I wonder what the difference is between kernels that makes OCing stable/unstable...