yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] vilord:
new rootfs with compcache, thanks to magister for the scripts and help.

also new zImage with better button support... now power wakes the phone, power is home, and record button is rotate!
[Touch Cruise Android Development] BeRo1985:
On my Polaris 100 are the touchscreeen input events under the lastest Android build from this thread translated by some pixels in direction down (i guess +64 to +96 pixels translated to down), so it's unusable, so that I cann't for example reach the notifcation above on the screen, to slide this up, and any other touchscreen fingerpress is also too misstranslated in the y-coord 64-96 pixels in direction down.

Under windows mobile 6.1 is working the touchscreen without any issuses without any misstranslation at me.

Does know anybody a solution for this? For example a touchscreen celebrate setting?
[Touch Cruise Android Development] briggs81:
woohoo rotate, nice! Will play with this tomorrow.

I've been playing with this htc magic for someone the past few days, and the polaris is VERY comparable in speed of general operations to it. Polaris is so good.
[Touch Cruise Android Development] vilord:
i think you can calibrate by setting options in default.txt, but I'm not 100% sure what they are for polaris. for vogue it is vogue-ts.XMIN, vogue-ts.YMIN, vogue-ts.XMAX, vogue-ts.YMAX
[Touch Cruise Android Development] radem205:
It's working great vilord. Thank you very much! How do you get the phone in sleepmode manually? And when I press the power button for a long time I don't get the power off function. How can I power off the phone
[Touch Cruise Android Development] pananza:
Decided to reformat my sd-card and downloaded latest zImage, initrd.gz, rootfs.img, and system.img from 2009-08-08.

Phone works even more snappy than ever, sms, market, calls and even battery life seems to be much better. But for some reason Neocore now crashes upong "unpacking" when I try to run it. Anyone else experiencing this? Here's my default.txt

#Polaris
set RAMSIZE 0x08000000
set MTYPE 1723
set KERNEL zImage
set initrd initrd.gz

set cmdline "board-htcpolaris.panel_type=1 ppp.nostart=0 pm.sleep_mode=1 mddi.width=320 mddi.height=428 no_console_suspend"
boot
[Touch Cruise Android Development] Mormy:
I have the same clock error, but I think also in the standard linux installation until some distribution ago.

When I tried the ubuntu/kubuntu 9.04 it asked me which type of "time" I would like to use. I sorry that I don't remember well the choice :(
[Touch Cruise Android Development] bally3:
Its good that other users are taking up the initiative to help in their desired way on the project but we need to be careful we dont give the impression that it is a finished product they are seeing.

We're still way off a fnished kernel with lots of small things that need doing with improvements and porting required for things already working on other devices.
[Touch Cruise Android Development] Kiiv:
Very great work, men! It's a very beautifull project and I think it's already working fine.

Thank you so much!

I will test it more and report what I see.
[Touch Cruise Android Development] briggs81:
I just want to make sure: it's normal for me to have to wait 1 minute or now to get a cellular and data connection right? I just don't want to keep reporting the same thing if that is what it's suppose to do, in order to work :D
[Touch Cruise Android Development] KeRmiT80:
hi i read in one post people modified ram line in the default.txt and that that should be ininfluent...

so i tried (i have 2 polaris) same windows rom, same sd card same hero build (i actually copied all files from one card to the second)

i booted them at the same time: no difference during boot, but once loaded the one with original default.txt started htc blablabla force close, freeze during scrolling etc etc, the second with the line of ram modified (i just changed 08000000 to 040000000) worked almost perfect...or at least it began "usable"

dunno i'm not a developer but i saw a boost in performance (or maybe there are many others factors i did not calculate)
[Touch Cruise Android Development] vilord:
nah, it should be quicker, but if it is only 1-2 minutes, lets leave it as is for now and revisit it after wifi is working. If you're still seeing the 5 mins for a connection, thats not going to cut it.
[Touch Cruise Android Development] bally3:
In all the new builds data doesnt work correctly for me.

I get "starting pppd" and then thats it.. a reboot and reconnect sometimes gives me an ip address but no data connection.
[Touch Cruise Android Development] Mormy:
Me too had similar problems.

Until latest zimage and rootfs, I couldn't start modem and/or connection. With the the rootfs-2009-08-16 I could use the browser and mail, but when I start to download anything with the market, it crashes :(
[Touch Cruise Android Development] whashnez:
Calendar, WiFi & Battery Life

Hello there, I'm using Android 1.5 from the Google-Vogue repository on my Polaris...Works fine (well ecxept camera & bluetooth) but it can't turn on wifi.(I heard that it's partially working, well mine does not work at all). Also I can't get the calendar to work, it just does nothing, as well as I cannot change the console fonts & colors, it also does nothing. Finally the biggest problem is that it drains my battery in some hours, so it cannot be used...I would like to use it more regularly, so does anybody know any zImages, or default.txt that make the battery last longer?Thank you!
[Touch Cruise Android Development] freddycs:
so far the data connection is working fine for me, it even gets connected automatically....

when on landscape mode in Android ION, the keyboard is not able to fit in the screen fully. my screen resolution is 324 X 432. However, I do not have this problem when using Hero build, the keyboard fits to the screen perfectly.
[Touch Cruise Android Development] imfloflo:
@freddycs try to use the same resolution as in hero

mddi.width=320 mddi.height=480 lcd.density=160
[Touch Cruise Android Development] briggs81:
Alrighty. I will pay more attention to it. Lately just been turning it on and not looking at it for awhile. It still has not refused to give me a signal or data connection though, so that's alright. But now that I think about it, I have not reallly turned it on the past few days, just charging it. I'll observe it some more.
[Touch Cruise Android Development] belabartok:
When I boot into android and unlock it, I only get the white bar in the top and nothing more, the rest is all in black.Can someone help me?
[Touch Cruise Android Development] Swifty:
I get the same issue as bally3, radio 1.59.44.02

*edit - haretlog attached
[Touch Cruise Android Development] bally3:
I deleted everything below the line:

"set initrd initrd.gz"

and then "boot" at the bottom and then tried again and it booted fine.

I get the Audio disabled warning as user mentioned before but Im back into android and can see the changes Rogro made.

Must be something not commented out on the lines that were commented before. Also would it make a difference that both myself and Swifty are in the UK as per phone settings?
[Touch Cruise Android Development] bally3:
Reading Swifty's haretlog, it seems the following parameters are being picked up:

CMDLINE='ppp.username=tmobile ppp.password=tmobile ppp.apn=internet msm_sdcc.msmsdcc_fmax=32000000 pm.sleep_mode=0 board-htcvogue.panel_type=1'

Do we need to start putting our own operator settings in then?
[Touch Cruise Android Development] Swifty:
Good find, booting now :)
[Touch Cruise Android Development] bally3:
I've narrowed it down to this line "board-htcvogue.panel_type=1"

remove it and it boots fine. I wonder why thats a problem now and only for some people?
[Touch Cruise Android Development] rogro82:
Weird indeed... can it be that some Polaris devices have other panels? can you try panel 2 and 3?

Weird thing is that for as far as i can remember panel 1 is the default.
[Touch Cruise Android Development] excogitation:
just fyi - I can boot with htcvogue.panel_type=0 and 1,

with 2 I get a black display (backlight working), and with 3 some colored pattern.
[Touch Cruise Android Development] radem205:
It doens't make any difference when you change these values, because the MCC and MNC codes have to be change also.
[Touch Cruise Android Development] bally3:
Thats even stranger!

I get working with "0" and "3"

"1" I get blinking white screen

"2" I get non-blinking white screen

with "0" and "3" if I dont unlock the screen as soon as it boots then sometimes it freezes and wont unlock.
[Touch Cruise Android Development] radem205:
See here: http://67.228.199.237/forum.ppcgeeks/showpost.php?p=481028&postcount=305

Quote:

# board-htcvogue.panel_type - Panel type used to power the panel off and on

# 0=Don't power off the panel (Default)

# 1=Hitachi 2=Topoly 3=Samsung
[Touch Cruise Android Development] bally3:
Sorry I dont get the connection radem205? :confused:
[Touch Cruise Android Development] excogitation:
I didn't want to be rude ... but I also thought - "what is he trying to tell us?" (since we already had that information).

I didn't know that there are different LCD's in our devices, but this topic also indicates that there are different brands.

Apparently the Orbit 2 has the display from Samsung (because I have a TC with the Hitachi one).

A quick search on ebay makes me believe that there are several screens that fit our devices

60H00111-00

60H00111-01

60H00117-00

60H00117-01

60H00111-00M

60H00111-01M

60H00117-00M

60H00117-01M
[Touch Cruise Android Development] bally3:
Aah.. Well that makes some sense then I suppose. I wonder if theres any way of checking which make of LCD screen a phone has?
[Touch Cruise Android Development] imfloflo:
ok f00bar version works for me some improve but still no working keyboard :s

http://pastebin.com/m75fc406d
[Touch Cruise Android Development] excogitation:
keyboard wrong

rogro82 there seems to be something wrong with your latest 2 kernels.

This keyboard

appears when pressing the camera button, but letters only get entered when pressing

where this previous keyboard was (you even get the vibrating feedback):
[Touch Cruise Android Development] bally3:
Relax imfloflo, Rogro82 is working on his own at this time, I'm hoping we will be able to remedy that soon and get some co-ordinated effort going as its a huge task for one person to take on and I'm sure Rogro will appreciate some help at some point.

On that note, Rogro, could you please list the issues that we need fixing that other devs could hopefully start lookng at? I know dubbeld00 has pledged to get involved this week but theres also Dwaradzyne and others who should be able to get involved again soon. In the meantime, I'm still trying to contact a few of the other devs who were involved to get their input and of course DZO has said he will help us when he gets back.
[Touch Cruise Android Development] imfloflo:
I see the white keyboard, but no matter where I typed, I get the key that is located below the screen original android. As if the keyboard was not there, seen on the dialer.​

I know it but i'm very happy to view all progress in little time. :)

I have the cupcake keyboard in the browser very beautiful
[Touch Cruise Android Development] excogitation:
This might be of interest regarding a coordinated effort:

MSM7200 devices.
[Touch Cruise Android Development] bally3:
good source of info. I didnt know we have a service manual??

http://rapidshare.com/files/166056085/HTC_Polaris_Service_Manual.pdf
[Touch Cruise Android Development] dubbeld00:
DZO is also fixing the SMD code for the kaiser (which is the same on the polaris), if my attempt won't work, then I think it's better to wait for him.

Btw, rogro, do you have an instant messenger (MSN/Yahoo/Skype) (or are you on IRC) so I can ask some quick questions and don't waste time on stupid things that I have to figure out again? If so, and you want to share it, please PM it to me (if not, well I use this board to ask things).
[Touch Cruise Android Development] vilord:
bally3, why won't yours work??? it doesn't make sense :(

if you could hook up adb while it is in that stuck state,

adb shell cat /etc/ppp/pap-secrets > papsec.txt

adb logcat -b radio > rlog.txt

and try turning on and back off airplane mode...

I really want this fixed!
[Touch Cruise Android Development] whashnez:
WiFi turns on but...

I'm using the 08-08-2009 android 1.5 from Vogue repository with the 15-08-09 zimage and 16-08-09 rootfs on Polaris, running good! I tried enabling wifi and it turned on but I couldn't browse the wireless networks menu, it freezed. Also can anyone tell me how to turn off Background Syncing? It asks for google account when I go to the Sync settings.
[Touch Cruise Android Development] bally3:
Trying it now.. I'm in irc room now if you're about.
[Touch Cruise Android Development] bally3:
ok here goes.. I couldnt run the commands to log to text files., so I pasted it into a test file myself. I kept telling me in adb shell that it couldnt do it as it was only as read-only system.

I reloaded a whole new setup with nk hero themed, it automatically set up my apn but still got stuck at starting pppd.. Airplane mode and back didnt cure it unfortunately.
[Touch Cruise Android Development] vilord:
okay the radio looks fine... lets see

cat /etc/ppp/pap-secrets

and a regular logcat
[Touch Cruise Android Development] Mormy:
I don't know what file is responsible of this, but I just tried the latest rootfs and I couldn't connect, modem app remain in gray :(

Another couple of things are from last zimage:

1) I permanently have the handset icon in the top bar

2) Finally there is the "Reboot Phone" button/option, but my phone neither reboot or turn off :(
[Touch Cruise Android Development] vilord:
modem app staying gray is related somehow to the rootfs. I'll look at what is causing it, but I'm not 100%... maybe try turning on airplane mode, then go to modem, wait a bit and hit disconnect.

I wonder if togga would work better... hmm...

the reboot phone option is due to a different system you're using... maybe is that a rogers rom?

the handset icon is likely related to the zImage.
[Touch Cruise Android Development] bally3:
Addisu is helping life02 and myself with wifi in irc at the moment... fingers crossed :)
[Touch Cruise Android Development] iseeka:
tried to access via http://webchat.freenode.net/ to #POLARIS-DEV but nobody there..
[Touch Cruise Android Development] life02:
that's b/c it's #POLARIS_DEV

but it's for dev chat only.. not troubleshooting
[Touch Cruise Android Development] life02:
This is b/c you are prolly using mssimison's rom that has the donut stuff implemented. We are not supporting that rom yet.

If you want better results stick with NK ION (non themed) or the NK Hero Themed roms. Jessie and I are developing based on those two.
[Touch Cruise Android Development] life02:
This thread is Polaris Android Linux Kernel Development Project. There are other threads for troubleshooting and bug reporting.
[Touch Cruise Android Development] zy2zyy:
thanx to you developers on this great job, and i am from china, wishing that the zh-cn language could be saved in the system.img file, so i can experience it in my native language:)

thanx again. wish i could give some help here.;)
[Touch Cruise Android Development] Mormy:
oops, sorry. I don't understand that is a parallel work.

I'll change my system asap ;)
[Touch Cruise Android Development] imfloflo:
So for information is there any progress with the wifi? Bally3, Addisuand life02 working on it last night but no return yet.
[Touch Cruise Android Development] bally3:
yes there is no return, we will let you know when we have something to report.
[Touch Cruise Android Development] iseeka:
what a pitty.. thanks for your work

orange yesterday proposed me a hero or diamond 2 (with 18 months contract) but i´m going to keep my polaris just becouse of this project

thanks again!
[Touch Cruise Android Development] imfloflo:
joke : @iseeka or accept the hero/diamond2 and send your polaris to DZO :p
[Touch Cruise Android Development] SuperJMN:
LOL

Oh boy, or send it to me while my Polaris is being repaired! I'm going cold turkey. And even more with this thread riddled with words like "wifi", "updates", "developers", "fix",...

All of those are forbidden words that you should never say when I have no device :rolleyes:
[Touch Cruise Android Development] iseeka:
I see you ate forgetting all the spare time we are spending having fun with our devices trying new zimages.. etc (even I do not develop y enjoy seing new improvements etc)

diamond 2 not much to offer (3d,screen..) and NO android (it doesnt even boot)

hero ... android still need more software imo (igo,tomtom... i hope we see it soon)

i think that in wm polaris developers are almost gone (still some new good ones thanks god) but android poroject is exciting.

i think i can wait a bit with my polaris (maybe they release better devices meanwhile) and watch everyday (lot of times) this forum

would´nt it be a bit boring otherwise?
[Touch Cruise Android Development] bally3:
got sick of data connection issues and downgraded my radio from 1.59.44.02 to 1.59.42.15 which is an official radio and it connected data straight away in Android.

Still no connection in Market, but I've got web access again.
[Touch Cruise Android Development] iseeka:
i always had connection to market...how strange
[Touch Cruise Android Development] bally3:
Had a bit of break-through with Wifi today - inadvertantly. Will post my findings later when I get home. :)
[Touch Cruise Android Development] zy2zyy:
:pwaiting for u

er.. when will you get home? its 10:17 pm here. will i try your break-through "today"?
[Touch Cruise Android Development] iseeka:
One question...

what are the "particularities" os polaris android? (if any)

can I try any of kaiser or vogue?

Vogue-Hero Project Home: http://code.google.com/p/vogue-hero/

Vogue-Android Project Home: http://code.google.com/p/vogue-android/

dzo's Kernel Thread: http://xdaforums.com/showthread.php?t=382265

Vilord's Google Ion Thread: http://xdaforums.com/showthread.php?t=523692

mssmisions Android Builds Thread: http://xdaforums.com/showthread.php?t=540854

I´m using now:

HERO on Kaiser / Android + SenseUI with rootfs-18-08-09.img (rootfs-2009-08-18.zip doesnt start) works quite fast and as wifi doesnt work on polaris yet i dont mind this hero version doent have it
[Touch Cruise Android Development] bally3:
with the new rootfs, kernel and nkhero themed image and a fresh install on a fresh card:

Wifi turns on but does not scan. I was able to add a network manually and it told me it was "out of range, but remembered".

I tried to switch wifi off and ran a dmesg posted below:

http://pastebin.com/d37ccb62a

The good news is it doesnt crash anymore :)
[Touch Cruise Android Development] iseeka:
did the same, got the same
[Touch Cruise Android Development] imfloflo:
Just test with this files

zImage: http://vogue-android.googlecode.com/files/zImage-18-08-09

rootfs: http://vogue-android.googlecode.com/files/rootfs-2009-08-18.zip

system.img: http://vogue-android.googlecode.com/files/system-nkhero-2009-08-12.img

initrd.gz: http://vogue-android.googlecode.com/files/initrd.gz

default.txt: http://xdaforums.com/attachment.php?attachmentid=206479&d=1247977771

And it says unable to start the wifi after showing "activation " during one minute.

In advanced settings the mac adresse is blank :s

edit: just retry without having wifi on under windows and it's working like you said @bally3
[Touch Cruise Android Development] bally3:
we're getting closer thanks to life02 and Addisu (the man's a genius!)

Hopefully we'll get more done tonight, but we could do with a few testers in the same timezones to help out. I'm falling asleep at the time our devs come online usually after 11pm BST.

If you can help with the testing join in the irc room but please remember its a KERNEL dev room and not for complaining about why the last hero build doesnt work etc.

You'll need adb, the latest files and nkhero system image.

ps. finally got connection to Market.. funnily I did this last time at night time too.. :rolleyes:
[Touch Cruise Android Development] Mormy:
I would like to help, but I don't know so much of how to use adb and most of all..wrong time zone (Italy) :(

But if you want me friday night (for me) I could give it a try when I'll came back home after the pub...
[Touch Cruise Android Development] bally3:
I've spotted something interesting on the new files. On mine if I click Network Notifications, it it intermittently scanning now.

Looks like its looking for a network but not finding it. I'll post a dmesg when I can.

Looks promising though! :)
[Touch Cruise Android Development] zy2zyy:
cool!

that means you can manually connect to WIFI now, and move on to automatic connection?
[Touch Cruise Android Development] bally3:
Have a look at the images - I have a wifi named OK which i didnt create thats turned up. I cant connect to it, it just says "forget" or "cancel". I was able to switch on and off wifi without crashes and it intermittently seems to be scanning for networks.

I've also attached my dmesg when its doing this.

Update: after switching the wifi on and off a few times it freezes and needs rebooting, but its back to where it was again with the scanning after reboot.

So exciting! :)
[Touch Cruise Android Development] imfloflo:
Great find @bally3

Are you using new files? cause I try playing with this Notification checkbox yesterday but nothing appended.
[Touch Cruise Android Development] bally3:
I am doing, its possible that with trying to get data and market working I've swapped a file or two, I'll post up what I'm using when I get home today.
[Touch Cruise Android Development] bally3:
output from dmesg|grep -i wlan :

dmesg|grep -i wlan
[ 2498.178682] wlan: version magic '2.6.25-01843-gfea26b0 preempt mod_unload ARM
v6 ' should be '2.6.25-00876-gc2a9b40-dirty preempt mod_unload ARMv6 '
[ 2540.597306] wlan: version magic '2.6.25-01843-gfea26b0 preempt mod_unload ARM
v6 ' should be '2.6.25-00876-gc2a9b40-dirty preempt mod_unload ARMv6 '
#
[Touch Cruise Android Development] bally3:
For reference:

http://vinayharugop.blogspot.com/2009/02/android-wifi-driver-integration.html
[Touch Cruise Android Development] bally3:
# ifconfig -a

ifconfig -a
dummy0 Link encap:Ethernet HWaddr E2:31:F4:AB:3C:DA
BROADCAST NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:413 errors:0 dropped:0 overruns:0 frame:0
TX packets:413 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:24576 (24.0 KiB) TX bytes:24576 (24.0 KiB)
ppp0 Link encap:Point-to-Point Protocol
inet addr:10.139.205.55 P-t-P:10.64.64.64 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:36 errors:0 dropped:0 overruns:0 frame:0
TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:8525 (8.3 KiB) TX bytes:8233 (8.0 KiB)
tiwlan0 Link encap:Ethernet HWaddr 00:18:41:78:32:1F
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
usb0 Link encap:Ethernet HWaddr B2:EE:ED:2F:AA:BE
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
#
[Touch Cruise Android Development] imfloflo:
Where the ifconfig -a comes from your polaris or your PC where polaris is sync in usb ?
[Touch Cruise Android Development] bally3:
from adb shell on my pc.

I've just discovered that if you press the "ok" button and then click Advanced in the menu it shows that the MAC address is unavailable.

Which means we may be getting a false-positive, I'm sure the wifi card should show a MAC address regardless of whether its found a network or not.

It seems to be scanning without having a MAC address? :confused: