yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] Quilapvd:
Very nice rogro :).

I've resized the bootscreen and the robot,

From Vga(320x480) to Qvga (240x320) percents:

320/100% = 3.2

240/3.2 = 75%

480/100%= 4.8

320/4.8 = 66,666666666666666666666666666667%

The robot was 64x64 px it's resized to 48x43 px.

So probarly the size is now fixed.

-

We are getting it to the right direction :).

Edit:

Noticed that the android text and robot is getting wider.

I could fix it to stretch it the right way *rebuild the image* (because it not 2:1 but 2:0,75 or something > see the % calculation).

Working on it.

Edit:

Added now an fixed zip, with the android text and robot fixed at the right way, same size (240x320) but the text 75%-75% and not 75%-66,666666666666666666666666666667%.

So the first 3 png's, are resized with a vga to qvga calculation.

The zip is with qvga resolution but with the android text and robot normal resized to keep the same propositions.

Two choices ;).

Greetings.
[Touch Cruise Android Development] rogro82:
Ok attention to all people that cant get the SMS system.img to work ( for example most t-mobile nld people who have a pin set ), this is how it will work for you!:

You will have to disable the pin-code in windows mobile because the ril is using at+cpin/at+cfun messages i think.

To do this you just press the phone/signal icon in the top bar in winmo... choose settings, then security and then disable pin.

Now boot the sms system.img and it will work!

Finally i can try to fix the sound on this image :)
[Touch Cruise Android Development] excogitation:
Try clearing the browser cache (also had that problem).

I thought it was clear you needed to disable the pin.

Or do some parts even work with enabled ping?
[Touch Cruise Android Development] rogro82:
With the old images it always worked... there was no cpin calls or what so ever because of the cdma ril
[Touch Cruise Android Development] marcelkordek:
without pin, right apn settings and a working gprs/umts connection (in winmo)

SMS, CALL (WITHOUT AUDIO), IMPORTING SIM CONTACS AND INTERNET WORKS GREAT =)

big thanks to rogro82 for his new zimage and dzo for his system.img with working sms.
[Touch Cruise Android Development] Michel82:
Nice work! Rogro ... is it possible to include these in a new version? I extracted the originals from \system\framework\framework-res.apk inside the *.apk \assets\images
[Touch Cruise Android Development] Michel82:
Haha ... who would have thought that? Trying right now ...
[Touch Cruise Android Development] bally3:
Good to see more involvement by other Polaris users, nice work everyone. :)

Not been around as much recently, life/work issues etc, but kept up-to-date on the progress.

Rogro, get well mate first, dont be over-doing it, even though we're all benefiting from your efforts - health comes first, though being bed-ridden IS a pain I know! ;)

Marcel, can you post up in the testing thread your success with this build and also some instruction for user to follow please? can i also ask all of you not to entertain the "its not booting" questions on this thread to enable us to keep it clean. The only problems that should be posted here are curent issues when new images/files are tested. All other issues should be posted in the Marcel's Testing and Bug Reporting thread.

If users insist on posting these type of posts, keep directing them to the right thread please. We really need to keep this thread as clean as possible as we have a lot of developement ahead of us. Once we have a stable version 1 build that can be used from day-to-day, we will start a new thread as previously suggested by Dubbeld00 for application development.

I have been approached by a professional designer who has offered to create icons and themes for our linux build, so I may start an Android wallpapers, themes and icons thread once we get to our initial goal.
[Touch Cruise Android Development] Michel82:
I can confirm that calling, sms, internet and external audio are working with the latest system.img. It seems like internet connection is also faster this way. As expected no in-call audio.

I find the built-in cupcake keyboard very functional. Why would we need another keyboard? Isn't it possible to invoke this keyboard with a hw button (voice memo for instance) and use it everywhere?
[Touch Cruise Android Development] Quilapvd:
Sounds great Bally,

If needed I can also design some stuff (I'm also an proffesional graphic designer, vector based and pixel based).

It's great that this community is getting better and bigger in a good way.
[Touch Cruise Android Development] Quilapvd:
Double.. -.-
[Touch Cruise Android Development] bally3:
My goodness! two professional designers already on-board? We will have to get a thread started as soon as possible then!

Verigo, thank you for the contribution and the offer, its greatly appreciated. it would be great if you would take lead on the themes thread. If you are interested, just create a "Polaris Linux Android - Wallpapers, Themes and Icons" thread when you start creating the themes,

I agree its great to see the Polaris community growing and buzzing again! :)
[Touch Cruise Android Development] excogitation:
There should be a non device specific Android sub forum for those kind of things (also app thread) don't you think?
[Touch Cruise Android Development] Quilapvd:
Not for this one, because this is Polaris - Android specific > We're making it for qvga don't we?

I will look after it this evening, topic is coming soon, first I need to get the android sdk and files :).
[Touch Cruise Android Development] bally3:
ok.. I've made a wierd discovery :cool:

I downloaded the files Shadowline uploaded onto the Kaiser forum here and replaced all the files except the zimage and the default which I left as the new zimage from rogro and my normal default file.

I was unable to access the sim card and my contacts before, and only able to get gprs if I was connected in windows mobile and no mms or sms. I could make calls though.

i now have full access to contacts, i can send sms and my phone seems to be registering on the network (says its doing it but just stays there).

no audio is calls, music player works and I have a load more apps to play with but the main thing is I now have sim access and the phone signal works at the top of the screen too. Touchscreen alignment seems to be a little worse than before (is there a touch screen alignment program in Android?).

Let me know if you try it what you think.. I cant see whats changed that makes the difference. I edited the APN settings and added mine and thats all the changes I made.
[Touch Cruise Android Development] cr1960:
Bally, I can confirm things are working as you indicate.

Got off to a bit of a shaky start when the thing got itself into a boot-loop but on second try all cranked up fine.

Wish more of the apps worked so I could have a bit of a play. All in all, no doubt we are getting closer to having all the core functionality of Android available on the Polaris for everyday use. If you look at what's been achieved in just a few weeks, imagine where we will be in a couple of months?!
[Touch Cruise Android Development] xonx:
somebody, an idea? :(

there's nobody that can give me at least one idea for the problem in post #453?

I really want to try out Android.

thanks,

Cosmin
[Touch Cruise Android Development] bpmorris:
Hi Cosmin,

You really should be posting in the testing thread, this one is for development only really. Here is the link...

http://xdaforums.com/showthread.php?p=3192731#post3192731

I am only new here myself so only learning too, if I was you I would do the following..

* Install a ROM that everyone is having success with such as M-Amine 2.0 WWE

* Install a radio version that other people are having success with, I think 1.59.44.02 is pretty much the standard version I see people settling on at the moment.

* Re-format your SD card

* Cross your fingers and try Android again...

Any Responses to my suggestions above should be posted to the testing thread!!!

Cheers

Ben
[Touch Cruise Android Development] dubbeld00:
If rogro is still using the polaris-ts driver almost unmodified, no there isn't. DZO made touchscreen alignment possible by building it into the driver, rogro can easily port that if you ask me (it's also added in the Kaiser ts now).

The only thing is, it's not saving your alignment at the moment (so it's working till you reboot).
[Touch Cruise Android Development] excogitation:
Did you try another SD card - or copy everything off your SD card, reformat it (Fat16, Fat32) and try again.
[Touch Cruise Android Development] rogro82:
Im still using the original base, but all keyboard related stuff is taken out so putting the alignment code in there shouldnt be a problem...

Maybe i can write the alignment to disk and try to load it at start...

But im first concentrating on other stuff to work.

Yesterday I added keyboard backlight support ( thnx exco for finding the right gpio ) and also added a timer that times out 10 seconds after pressing a button. This way the backlight gets turned on on a keypress and turns off after 10 seconds.

Going to do the same for the screen backlight after i found the right gpio.

Dubbeld00 ive spoken to dcordes an he will apply my new files to the htc-msm branch so you can see what ive done so far. Im going to send the files to him tomorrow.
[Touch Cruise Android Development] excogitation:
Does it also get turned off when pressing power (not that it really is important ;-)

Nice. I couldn't find it.

Did you also make out the leds?
[Touch Cruise Android Development] imfloflo:
I try to find the led gpios. I sync it with usb and wait until charge is 100%, cause the LED pass orange to green, but nothing appears on my haretconsole :s always the same code again and again
[Touch Cruise Android Development] excogitation:
Just rechecked (several times), rogro82.

I'm fairly certain that the backlight and the leds don't get controlled through gpio.

I don't get any events when watching e.g. the blue led blink.

Also afaict the backlight never gets turned off unless you turn the screen off.

(on lowest backlight setting it is still on and when you set a timeout for win to turn backlight off it is at this same lowest brightness setting).
[Touch Cruise Android Development] imfloflo:
There is two part, the backlight and the screen.

you can swtich off the backlight but not the screen.

or you can switch off screen but not the backlight.

or both.

try it several times too and nothing too :s
[Touch Cruise Android Development] biktor_gj:
I guess you already know, but just in case, there's no orange led, orange appears when both the red and green lights are on, so you should find two gpios active while charging, and one when charge is complete (green).
[Touch Cruise Android Development] imfloflo:
Wifi and bluetooth log from haret http://pastebin.com/m14990e91

when i launch the wifi on, my watch gpios, stop after 4 sec :s do'nt know why.
[Touch Cruise Android Development] dubbeld00:
Great :) why the msm branch... and not the vogue? Since they don't include DZO's patches immediately (or am I missing the point somewhere). I'll try to create some (spare) time (freelance working isn't that great (always got something to do)) to help you fix some things (porting some of the vogue fixes (and "align the touchscreen") of the ts for example (the only thing I know to improve for so far)).

About the leds, isn't it the same as kaiser:

39 // Blue
40 #define KAISER_GPIO_LED0 (KAISER_GPIO_MISC1_BASE + 3)
41 // Green
42 #define KAISER_GPIO_LED1 (KAISER_GPIO_MISC1_BASE + 4)
43 // Red
44 #define KAISER_GPIO_LED2 (KAISER_GPIO_MISC1_BASE + 5)
45 // Flash
46 #define KAISER_GPIO_LED3 (KAISER_GPIO_MISC1_BASE + 6)

Someone had ported it before to the polaris... if it wasn't the kaiser implementation that was already working.
[Touch Cruise Android Development] rogro82:
The problem i think with the existing code is that its not really done in a clean way...

They call gpio_set_value every time they want to control a state.

I just created a board-htcpolaris-generic, which has some functions like:

set_backlight(bool on);

set_backlight_keyboard(bool on);

set_led_state(int led, bool state);

set_vibrate(bool on);

set_vibrate_timed(int msec);

bool get_osd_active();

set_osd_active(bool state);

this way we can just add board-htcpolaris-generic.h to each file where we want some state changes without thinking about specific gpios or needed functions.

I think this i a much more cleaner way to set things up.

The code changes can be both made to the vogue branch as well as the htc-msm one, so they can be added to both... Ill leave that up to dcordes, but ill ask him to do both or send them to DZO, so he can add them.
[Touch Cruise Android Development] excogitation:
Does that suffice for backlight control (as it has more states than just on/off)?

dzo is on vacation for a week
[Touch Cruise Android Development] rogro82:
I think the set_backlight should become set_backlight_brightness(int level), but i first need to know how to set it. :)
[Touch Cruise Android Development] rogro82:
I can confirm i can now set the backlight brightness... So im going to implement the set_backlight_brightness(int level) call, will take me some time to get all the calculations right but hopefully ill have it done by tomorrow so i can add it to my commits.

The backlight now dims after 10 secs inactivity just like the keypad backlight :)
[Touch Cruise Android Development] excogitation:
Good job!

Already from within Android? ;-)

I suppose "power button" also switches off keypad backlight?
[Touch Cruise Android Development] rogro82:
For now i only set the brightness at a preset level after the 10 seconds of inactivity.. Ill look into settings it from Android.

First ill need to calculate the levels and then try to incorporate them into an exported function.

Ive set it up so that when the screen powers off both the keypad backlight and the normal backlight turns off, else you will get a nice black screen with some light :D

If all is ok ill upload a new zImage tomorrow with the changes made.
[Touch Cruise Android Development] bally3:
Did any of you devs try the files from shadowline?

was wondering what the difference was with his files to the ones we were using?

Shadowline mentioned that his data.img might be reason its working, might be a clue.

ps. I sold my Polaris today after someone offered me a price I couldnt refuse... after searching ebay for another decent phone I ended up bidding for and buying.... another Polais! lol :p

Well...its still the best phone around IMHO, the newer phones have bigger memories and brighter screens and are twice the price for those features.. not worth it I think, I'll stick with my Polaris thank you guvnor - besides for the price I sold my old one, i've bought an identical brand new one. (the old one did get thrashed a "little" from all them hard resets from 3D driver project!:cool:)
[Touch Cruise Android Development] marcelkordek:
hi all,

i have upgraded my radio to Polaris Radio 1.64.08.21 all works fine. start hared and now i can make a call with audio (only rear speaker). when i press the menue key audio is disabled =(

great work rogro with the backlight issue.
[Touch Cruise Android Development] radem205:
Does the microphone also work when you call somebody?
[Touch Cruise Android Development] excogitation:
Benchmark

Caffeine Mark 3 Scores

Touch Cruise (CaffeineMark 3.0 MIDP2.0 CLDC1.1)

Sieve: 461 (98)

Loop: 545 (2017)

Logic: 390 (0)

String: 443 (708)

Float: 325 (185)

Method: 394 (166650)

Overall: 420

Kaiser (taken from here)

Sieve: 465

Loop: 550

Logic: 392

String: 429

Float: 341

Method: 397

Overall: 424

G1 ("stolen from" here)

Sleve score = 458 (98)

Loop score = 546 (2017)

Logic score = 390 (0)

String score = 516 (708)

Float score = 343 (185)

Method score = 398 (166650)

Overall score = 436

compare it to a PC

Not bad ...
[Touch Cruise Android Development] rogro82:
Ok im going to upload a new zImage in a few with the working backlight/keypad backlight... if people can test if its working and let me know asap then i can send the code to dcordes so it can be commited.

Edit:

File attached
[Touch Cruise Android Development] worstenbrood:
Seems to work great !
[Touch Cruise Android Development] imfloflo:
Working great like the volume keys. working great very responsive :)

the sound produce by the keypad during a call is very high. this version is very good. Well done Rogro82.
[Touch Cruise Android Development] rogro82:
Ok exco found one thing... seems the power buttons sometimes behaves strangely ( on long press it sometimes power down the screen while it only should show the menu ), but that wont be too hard to fix.
[Touch Cruise Android Development] marcelkordek:
yes mic works, but only for one call =(
[Touch Cruise Android Development] Michel82:
Backlight works like a charm. Also noticed the vibration works, nice! I cannot seem to end a call, the contextmenu option "End call" simply doesn't do anything. Had to reset my polaris to end.

If this and the audio diversion (both in- and external) would work this would get usefull to use on a day to day basis. Then just a working Gmail, Calendar and contact synchronization and it would be perfect.
[Touch Cruise Android Development] biktor_gj:
Great work rogro82!

In the meantime, could you upload the code elsewhere? I don't own a Polaris, but a Nike, and your kernel works almost perfectly, except for the fact that the Polaris' SD card detect switch is Nike's power button, so I have to keep the key pressed while android is running and would like to fix it (among other things...)

Lots of thanks!
[Touch Cruise Android Development] rogro82:
Ive just send you a pm. ;)

Also just send all files to dcordes so hopefully it wont take long until they are commited
[Touch Cruise Android Development] rogro82:
This is also because of the audio path I think... somehow hanging up doesnt work when i use the latest code DZO commited, but i dont want to work against old files.

My problem is I still cant get registered on a network ( eventhough i removed the pin ), somehow it doesnt recognize the provider. I can send SMS and make a data connection but making calls is a no go for me, so making sure audio is working well is almost impossible for me at this moment.

I see you also have T-Mobile. Dont you have any problems setting up a call? For me it immediatly quits when trying to... Or are you using an older system.img?
[Touch Cruise Android Development] Michel82:
Yes im also on t-mobile-nl. I can receive calls, haven't tried making calls myself. Network registration from within the settings menu is impossible for me, but i have auto network directly after booting up. I'll try if i can make a call myself tomorrow.
[Touch Cruise Android Development] imfloflo:
Michel82 what system.img did you use? the one from AndroidSMS1-23.zip package form DZO on kaiser forum ?
[Touch Cruise Android Development] rhov23:
HTC Dream?

I had a horrible dream last night about installing an Android ROM on my device, and everything went from bad to brick. I really thought it was real (Yeah well even though I thought I was part of the device) :o
[Touch Cruise Android Development] adabra:
Hi Rogro,

I realized that, unlike in WM, touching the screen turns on the keypad backlight, too. In Windows it is lid only when a hardware button is pressed (it has a separate timeout, too).

Thanks for your efforts anyway!
[Touch Cruise Android Development] rogro82:
Discussed this on IRC if i should seperate them immediatly, but for now i just coupled them ( so also the keypad turns on when pressing the screen ).

Its not hard to change but its up to people...
[Touch Cruise Android Development] excogitation:
yada yada yada

To help clear things up - at least include a the origin (url) of the file - better the checksum (worse but sitll: filesize):

That's the latest system.img (SMS working):

system.img <- md5: d2e8ba7e0e299bfdd2b98d46f520ed2d

By dzo on 20.01. from #2146

http://cs-alb-pc3.massey.ac.nz/vogue/system.img (this file might change)

this one is also in:

AndroidSMS1-23.zip

With the latest kernel from Rogro82 post #502

this should be working: (there might be a problem connecting to your provider - don't know why yet)

- audio works

- internet works (after setting up APN in Android)

- calling works

- audio in calls works outgoing

- audio incoming doesn't work

- buzzer works

- all buttons work (wheel has no function yet - but how it works is known)

- changing screen brightness doesn't work in android yet (not all brightness levels are known yet)

If you use older system.img's - no one here cares that you have internet working / audio in calls - we already know that.

If you know of changes to be made to system.img, of more recent versions (and the benefits) - let us know.

If you want to get involved : look here what needs to be done (you can also expand that if there are things missing).
[Touch Cruise Android Development] adabra:
It would be great if users could set it from Android as per their taste.

Actually, I'd switch keypad backlight completely off, as I know where to find the buttons even in dark. And, of course, it consumes some battery, too... :)
[Touch Cruise Android Development] bally3:
Works well, realise this is not kernel related and more OS or app related but I tried to download the zimage whilst in Android using the browser. It refused to download it saying it was an unknown file format... bit odd, might try and download something else.

Screens more responsive on this image in fact I'd say its just right.
[Touch Cruise Android Development] brumbrum:
Now when the system is actually usable for some persons, is it possible that we can start to experiment with creating a working flashable image of Android to flash the phones with instead of using the Haret-application?

Would also be nice to have a boot-loader to be able to switch kernel on the bootup, and then boot up Android for real on the phones when they are switched on, like Lilo on x86*-systems.

Would this be possible to do?

Anyone with any hints of how to do it?

I am willing to try it out on the Polaris I have, since I get my Blackstone (HTC HD) very soon (it should have arrived last week though, so I hope it will arrive today or tomorrow).
[Touch Cruise Android Development] Michel82:
Don't know if the one in that package is the same but im using this one: http://xdaforums.com/showpost.php?p=3194496&postcount=2146 from DZO posted on the 20th.

Before someone misunderstands my reply on rogro: i still do not have in-call audio, but i'm able to receive calls. We just cannot hear eachother. I mentioned being able to receive calsl because rogro said he wasn't able to call or make a network connection at all.

I think we need to do something about the release version management ...
[Touch Cruise Android Development] bally3:
This has been discussed in the Kaiser thread recently and as stated there, its still too early in the game to start thinking of alternative boot options.

The image we have is still far from a stable version with repeated crashed whenever you attempt to do much and we still have to fix some basic functionality like phone audio and gprs (without having to activate it in WinMo).

The time for discussion about whether we stick with the haret boot method or create alternate boot systems like rom images should be left till we have stable version 1 which is capable of phone functions and wireless/gprs etc.

The poll we created on the thread was just to gauge user preference. Now that other methods have been brought forward, I may change the poll to reflect this in the near future.