yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] vilord:
Hi there! I'm sorry but I'm not exactly sure what you mean... What are you having trouble with?
[Touch Cruise Android Development] briggs81:
I tried to monitor mine today. At about 10:00am i was at 100%, for the rest of the day I left it on my desk, did some text messaging, Google reader and downloaded like 3 apps, 3g connection was left on.. screen at half brightness. By the time 5:00 came along I was at about 58% I think. THough when rebooted into windows I think I was only at 1 bar.. maybe 2.. can't remember now.. damnit! Anyways.. it seemed to be better today then it was last night when i lost about 50% over night and it was just sitting there not being used.

Still, hard to tell.

If i had everythign on like you did, I don't think i'd even last 3-4 hours!
[Touch Cruise Android Development] life02:
So besides the keymaps that I changed for one of the kernels, are there any things that I have changed that anyone doesn't like or is having issues with?

Also be sure to try the new initrd.gz file that vilord posted on the android-vogue code google page. It has possible battery enhancements.
[Touch Cruise Android Development] life02:
Ok I have set up an IRC room on my home server... #POLARIS_DEV... it stays up 24/7 - minus power/data outages. I have logging enabled. Polaris devs, feel free to log in and discuss the development progress.

irc://freenode/POLARIS_DEV
[Touch Cruise Android Development] briggs81:
I have not had any problems with your files I don't think. My system is a little laggy sometimes.. but probably has to do wtih all the apps i am downloading and all the services that are runninG :D

I tried those new files but didn't notice anything different, but i only tested functionality. Perhaps i will put the new initrd back on and test the battery though.

p.s. 14.8 fps on neocore benchmark
[Touch Cruise Android Development] life02:
new zImage for TESTING

I just recompiled the kernel with all the updates from the vogue-android branch.

All my changes still seem to be in place as well. I don't believe the new updates have broken anything but I haven't fully tested yet.

I will be pushing my changes to the vogue-android repo soon so I won't have to recompile each time they push an update. DZO just setup my account.

Might want to try my new zImage with the new initrd.gz: http://code.google.com/p/vogue-android/downloads/list
[Touch Cruise Android Development] briggs81:
I was just getting use to the d pad working correctly so I think I'll wait until your changes are pushed ^^. I think that new zImage has the old/weird d pad settings.
[Touch Cruise Android Development] life02:
yeah it does... and none of the other changes I've made... my new zImage has their new changes and mine. I forgot to post it when I first added the comment... it's getting late here... lol.
[Touch Cruise Android Development] briggs81:
yeah I was a little confused :P I will try it now.
[Touch Cruise Android Development] life02:
just FYI... I'm watching the battery level drop (in spare parts - battery info) on my polaris and it's down to 25% (using my new zImage and the new initrd.gz). I for one have never seen it get that low without immediately dropping to critical 4% and dying.

Hopefully the battery is reporting more accurately now and using less juice... I will try to test more tomorrow... Goodnight all!
[Touch Cruise Android Development] kalmenchia:
Hi ,

tested the latest zImage and Andriod 1.5 , can boot into Andriod with

my C_S rom 1.60.014aCS with radio 1.58.25.14 , but no sound at all ,

may i know whether is the radio driver not compatibles with this

Andriod ?

Quite eager to get the andriod run ... :)

Anywhere just would like to thanks for all the contributors of this thread ...

learn so much.
[Touch Cruise Android Development] pananza:
Although GPS porsitioning is working, speed and altitude are reported 0 in all apps I've tried. Unsure if it has to do with the driver or the apps.
[Touch Cruise Android Development] Michel82:
I'm not that quick as the rest of you guys testing the battery performance, i'm still testing that first kernel. I can give you an update of my findings so far.

Charging seems to have taken a very long time. It was around 60% yesterday at around 12:00 when i updated and took to around 17:00 to charge to 100%. It also looks like it was taking longer at the end. It was to 80% in about an hour and then it took another 4 hour to get to 100%.

The battery is currently at 26% (9:27) from 17:00 yesterday. I haven't really stressed the device as i would during daytime but i just left it on overnight.

Excerpted:

- Charging seems to take longer. 5 hours for 40% (from 60 to 100).

- Battery lasts from 100% to 26% for 16.5 hours with minimal usage.

- No sudden dropping below a certain percentage.

I let the device on till it dies now and let you know if i find the sudden dropping.

EDIT: And it just dropped from 25 to 0 in 15 minutes.
[Touch Cruise Android Development] Mormy:
I'm sorry I can't follow the thread for a while....

I assume that you are Italian and like mine connection you don't need any username and password.

So I add "none" to your default.txt, then you must create an APN account inside Android, where you put in your MMC & MNC, type again "internet.wind" and leave blank the field username and password.

I "Modem" to connect and it works quite always, just a bunch of time I need to restart Android, but with the last image always works.
[Touch Cruise Android Development] Michel82:
Just found out that (since the latest changes??) i do have some GSM based locationing functions. I started Gmaps without having a GPS fix (animating satdish icon) and it indicated it found my current location by GSM (with the blue circle around it). It is something like 30km off my real location though.
[Touch Cruise Android Development] vilord:
just FYI the latest initrd should be giving you better battery life because it turns off the signal quality updates from the radio. I don't know yet if they get turned off completely, but I think from the spec it is supposed to only be turned off when the screen is off (it was not implemented that way afaik, dzo did the latest update).

Edit: One more thing, does the polaris have an extROM?
[Touch Cruise Android Development] Michel82:
If you're referring to the locked rom that helds system files with WinMo roms; Polaris doesn't have this. I remember from back when i was still upgrading windows roms.
[Touch Cruise Android Development] life02:
I'm experiencing similar long charging periods for the last percentages too. Last night after I posted that it got down to 25 it suddenly dropped to 4% a few minutes later before I got it plugged in.
[Touch Cruise Android Development] tranceman1989:
How and where to insert my operator in the file default.txt?:confused: Sorry for my bad english
[Touch Cruise Android Development] life02:
I just ported the gps from the vogue-android branch to our device. Currently, the kaiser and vogue only have gps positioning working.
[Touch Cruise Android Development] Michel82:
Another finding; Since i updated to both the latest initrd and zImage the phone hang twice today. It completely froze. Setting the phone to sleep and resume again scrambles the screen and resetting is the only option. Could this have something to do with the power changes?
[Touch Cruise Android Development] briggs81:
Yep.. that's what I cam onto post.. I was hovering around that 25 and then went right down to 4. Used it until it hit 2%, then turned it off complety for the night.

In the morning i plugged it into pc to charge (still turned off) for 30 minutes, turned it on, died right away! Which is odd, because the night before it only took 2 hours for a full charge from 0% to 100% in winmo, so if i give it 30 minutes it should at least get to 20% to 25%.. oh well! Charging now.. will test again after its at full charge.

14.4. fps from neo core tested also.

Noticed the screen went all blurry though after running neo core.. but will test that again just in case.
[Touch Cruise Android Development] life02:
Possibly. I don't know what all changed in their initrd.gz. try going back to the 0709 initrd.gz while using my new zImage.
[Touch Cruise Android Development] vilord:
The new initrd simply turns off monitoring the signal meter, that is the only change.

Lockups and scrambled screen sounds like the memory addresses of the 3d chipset aren't quite right. Also, the 3d framerate should be closer to 20 or 22 fps, so something is up...

Or maybe some of the libaudio changes that you brought into your zimage might be related?
[Touch Cruise Android Development] briggs81:
14.9 fps \o/. It went up .5 from last night!
[Touch Cruise Android Development] vilord:
Someone over in kaiserland mentioned lockups too related to CPLD changes in the kernel... that might be what brought it on.
[Touch Cruise Android Development] pananza:
I too experience freezes with the latest combination zImage og initrd.gz.

I had freezes before too, but perhaps one or two a day. Now I get them all the time.
[Touch Cruise Android Development] life02:
Thanks for the tip Jessie. I'll check the 3d memory addresses when I get home tonight.
[Touch Cruise Android Development] briggs81:
Can someone test something out for me.

Put your phone on vibrate via your volume slider.. then let it go into sleep mode, or whatever it does when the screen turns off.. then wake it up.

I am trying to pinpoint what is causing my phone to switch from vibrate to sound, and it happens sometimes when it "wakes up", but am not sure yet.

I thought i was going crazy, thinking I was NOT putting it on vibrate, but i really am.. it just keeps getting switched back. I wonder if the "Locale" app has anything to do with it.. or if its a bug.

edit: It seems to happen after I wake up the device after a few minutes.. but randomly.
[Touch Cruise Android Development] vilord:
I had problems with locale, it would put me in the wrong location and pick the wrong settings.

I ended up removing it and installing timeriffic to set the ring/vibrate automatically based on time of day instead of location.
[Touch Cruise Android Development] Mormy:
I'm a little lost....

I saw that 5h ago a new zimage exited at the "vouge-android"

The people that have continuous freeze are using this zimage or the "beta" from Life02?? :confused::confused:

EDIT: If is necessary that I go back with a previous ver. of radio (like 1.59.xx) to be the same of other, it isn't a problem. Just say it and I downgrade it ;)
[Touch Cruise Android Development] avs333:
Same here. For this radio, audio used to work with old kernels (roughly, before May), now it just doesn't: either at all, or after you hang up the first call (no matter incoming or outgoing).

Personally I don't think anybody would (and should) waste time on it now when such a great progress is being made. Just upgrade the radio to 1.59/1.60, it *will* work.
[Touch Cruise Android Development] kalmenchia:
Hi ,

Thanks and got my Andriod 1.5 os running with "sound" after upgrade Radio to 1.59 but found that the Neocore demo wasn't working anymore ,where I have tested it in Andriod 1.1 , it is working fine , any idea ?

"The problem is Rendered Error , your device does not support Qualcomm accelerated graphics. Neocore will shut down"
[Touch Cruise Android Development] life02:
Personally I've had no freezing issues using my zImage and the latest initrd.gz from vogue-android.

You really need to be on radio 1.59.xx as that has been the version that we have had the most success with. The zImage from the vogue-android branch will not have any of my fixes.
[Touch Cruise Android Development] life02:
Are you using my testing zImage or the one on the vogue-android site... the vogue-android zImage does not have any of my changes.
[Touch Cruise Android Development] bally3:
Using life02's zimage and the latest initrd, battery life seems fine, but I left my phone with about 50% battery last night and woke to find the battery complete dead.

Otherwise, its working great, speed is good. If anyones interested, heres my default.txt:
[Touch Cruise Android Development] bally3:
Just to keep everyone in the loop, vilord purchased a POLA200 xda orbit II from the uk ebay site yesterday, so in about a week or so hopefully he'll be in reciept of the device and he can help Life02 and the other devs, though Life02 is cooking up a storm all by himself it seems :)

Thanks again for all your contributions, like Jesse (vilord) said, hope we can live up to all your expectations.
[Touch Cruise Android Development] mikfaina:
HI,

I can't mobile internet gets work... no driver for vista, but i'm working on it, very busy during the week.

I have a question? which is the difference between bzImage e Initrd? What they do?

And Where i found old bzImage? I usualy take last from coogle code vogue but there is only 2 bzImage? There is a repository??

Mik
[Touch Cruise Android Development] bally3:
driver for mobile internet or adb?
[Touch Cruise Android Development] pt-1:
Hi,

would

ppp.apn=internet ppp.username=web ppp.password=web

be the correct setting for Vodafone UK ..?

I can see the little Sat Dish flashing on teh Top when using Google maps but nothing happens....

In Wim6.1 I have google Latitude running before I start

EDIT: When booting Android I can see in the shell:

This is before the web,web Details ... The writing is a bit fuzzy
[Touch Cruise Android Development] bally3:
Post moved to Bug Reporting and Testing thread, please do not post support requests here. This is a DEVELOPMENT thread.

Thank you.
[Touch Cruise Android Development] bally3:
Can I request that the regulars on here help out on the bug reporting and testing thread please till we get some people to cover there.

If this thread starts getting flooded by support requests then it will become historically useless as large dev threads become.

Thank you.
[Touch Cruise Android Development] vilord:
--from my vogue thread... this will easily transfer to polaris with a little testing once the device arrives next week--

after giving up on it last night I got an idea this morning... tried it out, I now have 160 megs set aside on the NAND for linux! Yippee!

Next steps are for dzo to help me to get the nand driver working (there's a setting i can't find), then I'll write a wrapper that'll read the windows partitions to see where windows internal memory ends (because that is where linux memory begins).

This way you'll be able to use whatever rom you want (as long as it is really small), with a modified boot sector, and it'll work.

Some quick changes to initrd for automatic updates from SD, and we'll have a flashable image!
[Touch Cruise Android Development] Mormy:
ok, I downgrade my radio to 1.59.46.12

I put last initrd e Life02 zimage with gps and "new" keymap.

I'll tell you difference with the new radio
[Touch Cruise Android Development] bally3:
Jesse, thats fantastic news! :)

I'm astounded by the progress being made here, its a credit to the devs the speed of the development and the hard work, time and effort devs are putting into this project.

I did some testing last night and realised that adb is only picked up if my device is plugged into the pc BEFORE I run haret. If I plug into the pc after booting into android, nothing happens either on the pc or in android. I assume then that this is not a plug and play type connection?

If thats is the case, will it mean we would have to reboot the device when we flash an android based rom? or will there be another plug and play activesync-type connection possible in the future? not just to sync but also to view the device filesystem and move/copy files etc as is possible with Activesync?
[Touch Cruise Android Development] vilord:
On vogue, the usb connect/disconnect is registered by the kernel, so it is plug and play for ADB. We'll have to investigate why the co/disco isn't registered for polaris.

Once we have an android ROM, we'll be able to use mass storage mode and access the SD card just like a USB key (the same way it works on G1).

To access the system or data images, you'll have to use ADB (also the same way it works on G1).

Updates will occur by placing a new system.img on the SD card either via ADB, usb mass storage mode, or by putting the SD card into a computer.
[Touch Cruise Android Development] Michel82:
Noticed this too. Strange thing is that this is only the case when sleep_mode=1 when set to 0 it does PnP.
[Touch Cruise Android Development] vilord:
good diagnostic skills there!

sleep_mode=0 is totally nonfunctional on polaris, so nothing is getting turned off. Sounds like the powersave drivers are putting the USB controller to sleep and not waking it back up :)
[Touch Cruise Android Development] imfloflo:
On the lastest zimage avalaible the volume up and down key don't work :s
[Touch Cruise Android Development] vilord:
Yup, known issue. You are going to want life02's kernel for working keys. He's working on commenting his code changes, then he's going to push them to the general repository (also will fix GPS)
[Touch Cruise Android Development] Mormy:
ok, I know that maybe you already explain it, but I don't know where :(

How I can change the:

" public static final String PROPERTY_SIM_OPERATOR_NUMERIC

The MCC+MNC (mobile country code+mobile network code) of the provider of the SIM. 5 or 6 decimal digits. Availablity: SIM state must be "READY" "

Inside: "android.telephony.TelephonyProperties"

I would like to put in the MCC & MNC codes for IT the carrier: 22299 = H3G - Italy

EDIT:

My notebook is under Vista, but if needed I have 2 virtual machine XP and Kubuntu
[Touch Cruise Android Development] vilord:
It should be easy to do this... on the phone go to settings -> wireless controls -> mobile networks -> access point names

Then hit menu and add a new APN

From there you should be able to fill in the MCC, MNC, and APN information.
[Touch Cruise Android Development] freddycs:
Hi Bally3, it's strange. for my case, it seems to be plug and play for my polaris. i do not have to connect polaris to pc first before booting from haret in order to use adb function. after android is loaded, i plug in the usb cable to my pc and i'm able to see the adb interface in my device manager.

if polaris went into sleep mode or i unplug the usb cable, the adb interface disappear from device manager. however, if i plug the cable back again, or wake up the device, the adb interface will appear again. i'm using windows xp pro sp3.
[Touch Cruise Android Development] bally3:
cr

Maybe its the OS? I'm using Windows 7 (against my better judgement :( )

Remind me which one you have again? POLA100 or POLA200? ( Can all testers on this thread add this crucial bit of info to their signatures please, ever since I learnt that the two models had different makes of components I'm convinced there lies the clues to some of our issues)

** That reminds me, can I have some volunteers to look after the Wiki - I've added the names of the devs to the first post and will add names of testers and Wiki updaters so we know whose in the development team. - thanks.
[Touch Cruise Android Development] Mormy:
It must be my bad English... I try to explain.

I have done my apn with all the settings, in fact my data connection is perfect.

What I miss is that android didn't recognize my carrier: in the "screen locked" where it would be the name of my carrier (Telecom, O2 and so on) I have a blank section.
[Touch Cruise Android Development] vilord:
I'm guessing that the name needs to be filled in somewhere in the APN settings page, i think there is one called "Name"... maybe it is that? If not, then it is separate. Check your log for the +COPS response, it should have the system long name, system short name, and MCC/MNC... if your SIM is responding with blank then that is where the blank comes from...

an example from Rogers wireless:

D/AT ( 87): AT< +COPS: 0,0,"Rogers Wireless",2

D/AT ( 87): AT< +COPS: 0,1,"ROGERS",2

D/AT ( 87): AT< +COPS: 0,2,"302720",2
[Touch Cruise Android Development] freddycs:
I'm using POLA100 :cool:

you can add me as one of the testers :cool:
[Touch Cruise Android Development] life02:
Testing zImage

New Polaris zImage for testing:

*Ported over the kaiser usb-charging tweaks

*Did some more battery tweaks

*Merged the board-htcpolaris-generic code with board-htcpolaris

*Lots of code cleanup

*Switched back to the kaiser notification LEDs

As always let me know if anything works better or worse.
[Touch Cruise Android Development] briggs81:
Ah the dreaded blue light is gone, thank god!
[Touch Cruise Android Development] briggs81:
It does not seem to want to charge via my pc. It say's its charging, but there are no leds and its staying at 82%.

I do not have any drivers install though on this machine for android device, is that the problem?

Actually it seems to be random now. I rebooted phone and it says its charging and now an orange led is blinking.. ok now orange led stopped blinking, battery info says its charging but I don't believe it is.. guess I will keep watching it.
[Touch Cruise Android Development] life02:
Mine is plugged into my Ubuntu laptop right now... no drivers... and it's charging with a solid orange led. The battery icon is showing charging. I get the same results on my Windows Xp and Vista desktops.

What initrd.gz are you using? I'm using the latest one on vogue-android (2 days old).

Mine is a POLA100 as well
[Touch Cruise Android Development] briggs81:
I've plugged it into my vista laptop and the led was orange and blinking then went solid.. stayed solid until screen went off and now it's solid red.

Before, my battery icon said it was charging too but the value never went up.

Once I wake it up orange led comes back. Iw ill wait a few minutes an dsee if actually goes up in charge.

Using the same files as you from google code repository.

edit: charging seems to be working now, using the laptop. Will have to play with visa pc tomorrow, see what the problem was.
[Touch Cruise Android Development] imfloflo:
Charging working on my device via usb under windows 7.

No device found in ADB, no sound on PC when i plug the usb.

So we need camera and wifi and we can have a fully working Polaris with android.

For camera its says he doesn't find the SDcard

Great progress in this thread <3

Thanks Dev and people spending time for the thread (Bally3 ;) )
[Touch Cruise Android Development] Mormy:
With the last zImage I can charge without problem under Vista. The orange led is stable.

But just a few moment ago I receive a call and there isn't sound and I can't end the call. I tried again calling myself from my second phone, same result: no sound (in and out) and I can't end the call :(
[Touch Cruise Android Development] bally3:
Just add yourself to the POLA100 user group in briggs81's signature, then start adding your results there. - thanks :)
[Touch Cruise Android Development] meknb:
Maybe its the radio im using 1.59.44.02 and works fine to end the call i have to press the menu button (bottom right) and click end call.
[Touch Cruise Android Development] bally3:
New kernel seems to be a bit faster, same as reported above, call issues with no ringer sound and cant end call with end call button. Will report more when I get some more tests done.
[Touch Cruise Android Development] bally3:
Seems like the power button has now become the call end key :confused:
[Touch Cruise Android Development] briggs81:
I can confirm that. Power key ends the call, end call key does not. I wonder if that was part of my problem awhile ago too.. some zimages i could not end call.. thought it was frozen so would pull battery out.. shoulda pressed the power key!

I can still receive calls and have a conversation with this zimage too, no calls outgoing though, as per normal. I also have ringer sound.
[Touch Cruise Android Development] life02:
Yeah I went back to the original keymapping since people complained about using the red button as end call.
[Touch Cruise Android Development] life02:
I'm using radio 159.42.15.. just fyi
[Touch Cruise Android Development] life02:
I tried multiple incoming and outgoing calls this morning... all worked fine.

I'm testing on a POLA100 with radio 1.59.42.15