yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] pananza:
I cannot imagine people complaining about red button ending a call. Your previous mapping was much better. This is my which mapping, and the most logical in my opinion:

Green: Dialer

Red: End call, or back if not in a call

IE: Menu button

Nav: Home

Voice call: Show runnning tasks

Middle: Enter

Wheel buttons: Right, Left, Up, Down

Wheel rotation: Nothing
[Touch Cruise Android Development] life02:
Same file with but with the new Keymaps (End Call button working as End Call, etc....) Keep in mind I'm testing with Radio 1.59.42.15. So if you have issues with calls... try switching to the radio i'm using first.
[Touch Cruise Android Development] life02:
The End Call key map is linked to the power settings somewhere.... haven't really had time to look where. If I can get the End Call button to work as back outside of a call then I will move the Home keymap back to the Nav button. Would yall rather have back mapped to VoiceDial button and home mapped to Nav until I can get it fixed?
[Touch Cruise Android Development] vilord:
end call is linked to power within the android system, not something that is easy to change (or worth changing). Take a look at all the official android devices currently on the market, end call is always dual use with power.
[Touch Cruise Android Development] life02:
That's what I was kinda thinking... I had a G1 a while back but forgot if that was the way it was set up.
[Touch Cruise Android Development] pananza:
I charged the mobile in WinMo all night and with 100% battery I started haret and booted your new zImage. Immediately in Android battery level was reported down to 86%. I rebooted back to WinMo and the battery was back to 100% again. So the battery level is still off with quite a bit.
[Touch Cruise Android Development] Mormy:
Just tried this last zImage:

1) I made a call and I can ear and talk :)

2) I end the call with power button, now that I learn how to do it :)

3) My wallpaper (the leopard??) has better color and seams more in background (it's difficult to explain)

4) I tried Neocore demo: 15,1 fps, but the strange is that this is the first time it starts properly, until now I didn't have texture :O
[Touch Cruise Android Development] life02:
New default.txt

Try this new default.txt with some adjustments to the mddi clock settings that dzo recommended to me. I am now able to get 16.7 fps in neocore.
[Touch Cruise Android Development] roms5:
I have the same problem...

Have you a 4GB+ Micro sd card?

maybe it dont work with much storage.

Is your card formated in FAT 32?

Or have we to format the card in ext2??

The old release work for me...

http://xdaforums.com/showthread.php?t=385023&highlight=android
[Touch Cruise Android Development] bally3:
deleted all files from root of card (including hidden files) and left just android files there.

Booted successfully to Android screen! :)

Will have a play and see what works. Looks promising.. very promising!

Nice one again Rogro :)
[Touch Cruise Android Development] bally3:
ok pretty much same a s kensou.8 on the workings.

Anyone having issues, please ensure you have bno previous installations of Android on your card and also that you have no android related files in the root apart from the ones we are using and you should boot fine.
[Touch Cruise Android Development] bally3:
Card is fat 16 and is a 4Gb SDHC card.

1) Used kvstrien's link to the files http://xdaforums.com/showpost.php?p=3092252&postcount=159 (thanks my friend - fast download!)

2) Unpacked and copied to root of SD Card - left only my tom tom files that need to be in the root and deleted/moved all other files.

3) Booted Successfully!
[Touch Cruise Android Development] adderz91:
Booted first time for me. Didnt have to remove any of my other files (although i hadnt installed Android before which might of had smething to do with it)

Gullum TF2D Beta 2

1.59.42.15

No phone as above etc etc
[Touch Cruise Android Development] radem205:
On a totally empty sd card I installed the files (http://vstrien.csoft.net/Polaris-build/polaris-build.tar.bz2) in the map "ANDROID". When I run Haret.exe I get an error "gZip: /Sdcard/system.gz: No such file or directory".

Does anyone know what I do wrong?

I think it has to do with the new sd card that I have inserted into the device. I remember that this new sd card has a new identified id, but I don't know how I can edit this in the default.txt
[Touch Cruise Android Development] kensou.8:
You have to put system.img or system.gz at the root of the card.

the init script check if there is a system.gz or not. if not, it uncompress the .gz else it use system.img
[Touch Cruise Android Development] radem205:
Thank you! It's working now! Very promising!
[Touch Cruise Android Development] kensou.8:
Like me, I dream to kick out WM for android :rolleyes:
[Touch Cruise Android Development] belabartok:
It`s booting here, only extracted the files to the root.I have a 4 gb sd.
[Touch Cruise Android Development] roms5:
I have used the working android from rodro

what have I to do with ht .out files?
[Touch Cruise Android Development] neborkia:
It boots on an Official WM 6.1 ITA version, Radio 1.49.42.15 :D

It seems that video res doesn't fit perfectly in some screens (like booting android, dialer, etcetc)

Can't connect to the operator to try a call and SD Card is not recognized.

After the device puts the display in standby i'm not able to recover it and i've to restart.
[Touch Cruise Android Development] excogitation:
that deserves some applause

unfortunately didn't happen

what do you mean by size? the bootscreen doesn't quite seem to fit

keyboard doesn't work for me either, also there's now only the keyboard visible but not working (can't we get this one easily?)

it shows but freezes when I try to enter a number

I can confirm that too although the dialer and calculator seem to be due to a wrong - too big font.

You can turn it back on pressing the red button the first seconds after the screen goes off, but after that no way to resurrect it.

A shame the cyclon is gone :-)

I'm using the

radio 1.59.42.15 and the

original HTC 6.1 German rom it came with.

In the 0.8 version from here:

http://xdaforums.com/showpost.php?p=2114746&postcount=1

the dialer doesn't show, I can't make nor receive calls,

and the internet doesn't work - although I can send SMS.

Might that be because of the radio version I'm using?

Maybe we can extend/clean/confirm/keep the Polaris Linux wiki page up-to-date? (if that makes sense)
[Touch Cruise Android Development] redhoerbi:
Hello,

I also have the same error: mdp_dma_to_mddi: Busy.

How can I help to find the bug? Is it possible the log the complete output into a file?

I hope some will solve this soon, can't await to see Android 1.0 running on my device. :)
[Touch Cruise Android Development] rogro82:
Update your radio this should fix it.
[Touch Cruise Android Development] imfloflo:
Yeah rogro82's back, maybe some news from android polaris edition ?

when i boot using your workingandroid zip, i can read lot of mdp_dma_to_mddi error but when i just patient and it boots fine all the time
[Touch Cruise Android Development] redhoerbi:
Hi rogro82,

I'm "just" a .NET developer, I have no linux skills and I dont know how to update the radio. I think I have to replace the radio driver and recompile android? I'd like to lern how it does work, but i need some time. How can I start with this? Are there any "beginners" manuals for this tasks? Thank for your help.
[Touch Cruise Android Development] Swifty:
Don't need to recompile anything.. this is what you want; http://xdaforums.com/showthread.php?t=453190
[Touch Cruise Android Development] redhoerbi:
I get also another an IO error and then it exits. I will buy today a 2. card, which i can format. I think there are troubles with my card.

btw.: I have also the problem that i have to try around 5 times until linux boots. The most times, it hangs when i the progressbar is on 95% or 100%. Is this "normally" or am I the only one with this problem?
[Touch Cruise Android Development] redhoerbi:
Oh, thank you. Do you prefer to install the new rom (89MB exe download) or just update the radio using RUU?
[Touch Cruise Android Development] radem205:
@Life02, Vilord and Dzo: Thank you so much for your great efforts on the polaris!!

When the phone is in sleepmode (with the default.txt in the post above) the only solution to get the phone out of sleepmode is to press a random key (not the power button) and then the power button. With only the power button it's impossible to get the phone out of sleepmode (only when red led is displayed). Anyone has this problem too?

Ps: With the newest files I get 15,9 fps in Neocore.
[Touch Cruise Android Development] w04g005:
with the new default text I'm not able to make or receive any phone calls!

THe only difference between the last working default.txt and the leatest posted by life02 is:

clock-7x00.mddi=0xa51 so i assume it has to to with the clock setting
[Touch Cruise Android Development] x_coRe_x:
New kernel image has been released =)

Here it is.

--

Oh gosh, i put new kernel image to the /, dowload default.txt by life02, changed it and run haret. Then I made soft reset and.. it's stopped on boot screen. So i had to make a hard reset :(

Maybe I did something wrong?

--

hm, now it's ok. I just deleted all stuff from earlier android verison and then installed android again with new kernel image.
[Touch Cruise Android Development] imfloflo:
With the lastest zImage the right key doesn't work anymore :s

The led is block on the blue color and always on
[Touch Cruise Android Development] x_coRe_x:
Same here.

Btw, i've noticed that center button works as right button, at the same time right button doesn't work at all. It is in the both last zImages. :confused:
[Touch Cruise Android Development] briggs81:
The sleep mode thing has been like that forever, nothing new. Change sleep mode to 0 instead of 1 if you want, may not get as good of a battery but at least you can "wake it up" without a problem.

Sometimes it won't wake up, but usually you just have to press any button a few times and then unlock it.
[Touch Cruise Android Development] briggs81:
This has always been the case with Android on Polaris, until a few weeks ago when life02 came on board and fixed the keys for us. So for now when you see a new zimage on the google code site, you have to wait for life02 to make his modifications, until he is able to push his changes via that website.
[Touch Cruise Android Development] briggs81:
It's been like this for awhile with the latest zImages. except life02's latest where it's either no color when in use, orange when charging or red while sleeping
[Touch Cruise Android Development] bally3:
Correct me if I'm wrong, but it appears to me that the POLA100 users are the ones having issues with calls?
[Touch Cruise Android Development] briggs81:
Seems like it, but there are pola100 users who can make and receive calls.. life02 for example. So still kinda weird.
[Touch Cruise Android Development] freddycs:
new default.txt by life02

with using the lastest zImage (zImage-Polaris-TESTING-07-18-NewKeymaps.zip) and default.txt released by life02, i get 16.1 fps in neocore, and the speed of Android is now smoother and faster, especially sliding between the tabs in the main screen, and the scrolling in the program menu listing.

i'm yet to test on the battery, but it seems not much improvement for the battery usage. when it is 100% fully charged in winmo, it is also showing 100% when i load into android. however, i notice that after few hours of playing around with android and when go back into winmo, the battery level in winmo is much lower than in android.

another thing is that, with the new zImage, after i run neocore, there are something wrong with the background graphic whenever there is any pop up menu. such as when you press on the home screen to add widgets, when the menu pops up, the pixel in the background graphic of the main screen become scattered... anyone face the same problem?

when android is in sleep mode, the solid red led is always on. i press menu button, the red led disappear and appear again in a short while...besides, other function just like normal, i'm able to make and receive calls, no problem with GPS and data connection.
[Touch Cruise Android Development] freddycs:
but i'm the pola100 user without having any problem in making and receiving calls...... could it be the radio version?

i'm using:

pcarvalho eXtreme (3.19.WM65X) OS 5.2.21815 ROM 3.19 R0 Release

radio: 1.59.46.12

android version: android-1.5-2009-07-09.zip

initrd.gz, zImage and default.txt released by life02

1GB Sandisk MicroSDCard formatted with FAT32
[Touch Cruise Android Development] vilord:
I'm about 90% sure that the dialing out problems are specific to the SIM card / carrier.
[Touch Cruise Android Development] radem205:
I have a POLA100 and I don't have problems with making calls (outgoing and incoming).
[Touch Cruise Android Development] briggs81:
i don't think I've ever been able to dial out with android, if I did, the most i would get is the green calling screen and that's it. I have tried bunches of roms and radios etc.. and as vilelord says.. seems like it's the carrier. It's a newish 3g sim card too so meh.
[Touch Cruise Android Development] life02:
My observations:

*Better speeds in android with the new 3D settings but it's still not ideal.

*The background color problem has to do with the 3D settings... I'm working on it with dzo. It only appears after running neocore and clears up with a restart.

*Battery life is still about the same but it is charging to 100% in android (it wasn't doing this before for me)

*With light usage I was able to use it from 9:00 - 6:30 before it dropped to 4%

*With USB changing, it now knows when it's actually being charged (ie cable plugged into a pc)

*Yes the red led is signifying sleep right now, and orange charging. I'm still playing with the leds to make them more useful.
[Touch Cruise Android Development] Mormy:
Me too have discovered the same pro and cons like freddycs: smoother by strange background.

I'll wait life02 & dzo works to adjust it, but in the meanwhile I obtained a 16.8fps in Neocore :)

No more problem with in & out calls, sms is perfect, gps working, data connection too :)
[Touch Cruise Android Development] w04g005:
I'm having the same problem. When i play city stage (a racing game) and close it the background graphic is also blurred. Maybe it has to do with the usage of the 3d hardware?
[Touch Cruise Android Development] briggs81:
Just wondering if anyone has been playing around wtih screen dentisty and your resolutions and what you think.

I have removed the mddi heights and widths and just let android default settings take over, and changed the lcd.density to 128. Everything is obviously bigger and sharper, but there is a bit of cut off, and probably more cut off with screen density set at 160 as default. Keyboard is definitely screwed up though.

My fps from neocre was at 16.6 this time, which is the higest it's ever been, but we're talking a change between 2 and 3 fps since i've been running tests with it.
[Touch Cruise Android Development] vilord:
I can't wait for donut... supposed to fully support lcd.density so we won't have to use mddi scaling.
[Touch Cruise Android Development] bally3:
I'm using 1.59.42.15 at the mo and everything works fine call-wise. I would advise anyone having problems to change to this radio if they can.

I'll test 1.59.44 and 1.59.46 on my current android set up and see if theres any difference.
[Touch Cruise Android Development] briggs81:
Are all sim cards basically the same, or is there a general sort of code or number that says what "type" they are?
[Touch Cruise Android Development] bally3:
How long for donut? ...mmm... donuts... aaaarrrrr..:)
[Touch Cruise Android Development] :
SIM and U-SIM

Hi Briggs...

From my understanding there ares 2 main types of simcards:

- Traditional GSM card: SIM (Subscriber Identity Module)

- New for 3G services: U-SIM (UMTS - Subscriber Identity Module)

I cannot tell the exact difference but the storage capacity, their ability to run some kind of scripts when the phone starts up, and may be also some scripts when running the operator's application based on the SIM toolkit (this is usually an operator icon which calls a menu to call emergency launch applications, web applications, and so on - usually is made and customized by the operator).

I hope this can help. if there is other specific question y could help to research about it.

JM
[Touch Cruise Android Development] briggs81:
Ah i see, thanks.

I was basically just trying to figure out if there would be something different about my 3g sim card from Rogers/Fido compared to other 3g sim cards that might stop me from being able to make calls with polaris w/ android on it. I don't know any other people using Rogers/Fido and Android so hard to compare results.
[Touch Cruise Android Development] bally3:
right.. tested all three radios and all three of them worked flawlessly with 1.59.44.02 seemingly faster on data connection, but its said 1.59.46.12 is better on battery, so I might stick with this and see if theres any battery improvements (is this relevant in Android?)

ps. LCD density seems to work for me.. top of your heads, does anyone know the best resolution in between 240x320 and 480x640 that I can try.. there was a list of resolutions in the Kaiser post.. will have to go look ..
[Touch Cruise Android Development] life02:
new zImage for testing

Here is a new zImage for the Polaris with the newest changes from the vogue-android branch. I'll be pushing my changes to their repository today so we can all use the same zImage in the future and hopefully stop all the confusion with those that aren't keeping up with the development thread.
[Touch Cruise Android Development] bally3:
Thanks life02, testing now- you really have help breath new life into this project (pardon the pun) :)
[Touch Cruise Android Development] briggs81:
Can someone post the 1.59.44.02 radio, mine keeps crashing when trying to flash it.
[Touch Cruise Android Development] briggs81:
I've tried a bunch and have settled on mddi.width=324 mddi.height=432. I wouldn't mind one that made everything a tiny bit bigger though. Maybe I'll try something different too. I use to use 336 x 448
[Touch Cruise Android Development] bally3:
Skola48 posted this in the Kaiser thread if anyone wants to test and report on these resolutions:

Try some of these:

240x320 <-- Screens native resolution.

288x384

336x448 <-- This is is my resolution. Good mix of size and clarity.

384x512 <-- This appeared to make the Unit freeze. Gets to Waiting for SD Card

432x576 <-- Doesn't quite work correctly. Will boot, but screen lags.

480x640 <-- Doesn't quite work correctly. Will boot, but half the screen is finicky. This may be a video memory issue. Seems that the lagging and refresh becomes progressively worse as you increase the resolution.

Note, these are all on 16bit even increments. By dropping to an 8 or even 4 bit increment, you can come up with much more options, but I'm not sure if they are 'safe'. For example, I tried a resolution that was NOT support (garbled text, crazy lines), and after restarting, it had blown away a bunch of my settings!

If you are really bold, here is the full list of 4bit spacings:

240x320 252x336 264x352 276x368 288x384 300x400 312x416 324x432 336x448 348x464 360x480 372x496 384x512 396x528 408x544 420x560 432x576 444x592 456x608 468x624 480x640
[Touch Cruise Android Development] bally3:
hmm.. dont know whether this was the kernel or the resolution but I was just testing 300x400 with lcd density set at 128 and a whole load of my apps are now showing with updates available :rolleyes:

Its running qite fast as well..I'm pretty happy with this res, it does seem to be much smoother, though no where near the clarity of 240x320.
[Touch Cruise Android Development] briggs81:
is they keyboard usable?
[Touch Cruise Android Development] bally3:
Very much so.. as is google maps from what I can see.. try it and see :)
[Touch Cruise Android Development] briggs81:
Not bad, just a bit too tiny for me though I think!
[Touch Cruise Android Development] kalmenchia:
Hi,

with using the lastest zImage (zImage-Polaris-TESTING-07-18-NewKeymaps.zip) and default.txt released by life02, i get neocore already.

And the Blue Led is no longer on. However with my battery around 90% ,

I left in stayed in Andriod for the whole night from 11pm till morning 8am next day and the battery is flat .

At this moment modules that are no working in my PDA:

1. Camera / Video

2. GPS , not yet tried , because I could not set up my data connection

3. Internet connection (gmail,calendar,browser,youtube...) same as above.

Can't wait to see Andriod is completed and thanks for all the effort made so far. Great Job!
[Touch Cruise Android Development] life02:
Battery stats for today:

10:30am - 9:20pm with light data usage and a few calls. ~11hrs.

Background Sync is on.

My battery is now 56%. I know it dies a little while after it hits ~30% but this has been the best battery life I have seen so far.
[Touch Cruise Android Development] briggs81:
Is the polaris zimage on google code the most recent?

Battery has been not bad for me too today, as long as its accurate!
[Touch Cruise Android Development] vilord:
the polaris one is, yes.
[Touch Cruise Android Development] life02:
Made a few more tweaks to the kernel.

16.9 to 17.6 fps in neocore now with no multicolored background after it runs!
[Touch Cruise Android Development] freddycs:
Yeah the multicolor background issue is now solved with the new zImage released by life02. For battery usage, its fully charged since 9:30 this morning. Now it's at 58% after 5 hours with moderate usage,such as a couple of calls and sms, then I run neocore 4 times.

Regarding the red button, actually it can be assigned to display home screen when pressed. The setting can be changed in spare parts.
[Touch Cruise Android Development] micky972:
Hi newbie in the area

:p

So here i am thanks the developpers for all that stuff it's amazing

I'd like to know if it(s possible to connect to the internet by usb and if possible how can i make it work

thanks for the answer :):):p:p:D:D:cool::cool:
[Touch Cruise Android Development] bally3:
Just tried new build, got 16.5 fps on the first try and then changed back to the normal 324 x 432 res without the lcd density and it gave me 12.9 fps with the fuzziness on the top.

Incoming call ringing isnt working btw, dont know whether that was reported. Just missed an important call as I had it on vibrate and it didnt vibrate either.
[Touch Cruise Android Development] Mormy:
I stat trying the last zImage this late morning with resolution and lcd.density suggested by bally3: neocore 16.9/16.7fps

First time I boot up android I receive a call but no sound either in and out, I can't end the call :(

I reset, stay a while in winmo because I haven't got time to check if is all right.

Second boot I try immiditly a call (out) and it works. After a while I receive a call and it works.

I don't know if making a call unblock the phone or the first time boot isn't working for a reason :confused:
[Touch Cruise Android Development] bally3:
i havent had any issues making or receiving calls since 1.5, its the ringing thats broken for me. could do with at least the vibrate on call working.
[Touch Cruise Android Development] kulen:
I've been using new life02 zimage from this morning and his new default.txt.

and incoming calls, outgoing calls ringing and vibrating is working.
[Touch Cruise Android Development] radem205:
For me ringtones are working well. Make sure you unzip the resources.zip folder (attached with the newest android files) and copy the media folder to the root of your sd card!
[Touch Cruise Android Development] life02:
Not quite sure what's going on with yours. I've had no trouble with ringing or vibrating... even on the first call after a boot. I'm using the settings in my default.txt and don't have the fuzziness at top. You may want to try moving your data.img to another folder (to keep a copy of it) and start with a clean slate to see if you still have problems.