yashsingh1/xdaforums huggingface dataset:
[Nexus One General] Mafian:
YES STOP SMOKING THAT CRAP... VIDEO CALLING WTF? Lol you must want to be in a matrix movie or some crap... send a fricken video and stfu and hope they respond with one back :D lol video calling made for dummies
[Nexus One General] NexusDro:
It would be great though, if the Nexus One could at least receive the call and do a one-sided video call. So even though the caller can't see me at least I can see the caller :). This can probably be done with software, right?
[Nexus One General] Amdathlonuk:
Nope, but there's an app for that........ :D
[Nexus One General] wolfman87:
That's just what we need, a bunch of people walking around or driving trying to hold the phone in front of their faces while video conferencing. I can see people walking into trash cans, street signs, poles, mailboxes.........

Better up your car insurance too! :p
[Nexus One General] GNOve:
Personally I dont think their laughing at the phone. They are laughing at you.

And wondering why the people that dont deserve good things in this world are the ones that have it.

Cant believe you saw superphone and figured it did everything lol hahaha

This should be a honorary mention in the failblog.

Thanks for the laugh pedobear :)
[Nexus One General] britoso:
wow so much hate!

The Nexus one, even with all its bugs is still one of the best phones (if not THE best) out there. Very happy with my $600 purchase (after adding tax and SD card). Its unfortunate that Google is taking forever to fix the high profile bugs.

Its definitely capable of atleast receiving video calls when on a good connection/WiFi.

Which app are you using?
[Nexus One Android Development] GlenH:
I was wondering if ianyone has any idea which files we might need to extract from a Desire ROM to replace the auto-brightness code in Nexus ROMs?

I've noticed that it seems to work much better on the Modaco Desire ROM, with a higher base level of brightness and more consistent reaction to the ambient light level.
[Nexus One Android Development] FormelLMS:
Wow, thats awesome.

Anybody an idea, where to find?

The script on Nexus is...****ty.

It has automatic brightness, but it's useless on this phone for now.
[Nexus One Android Development] hassan:
Thats right i don't even use it as it doesn't work as it should :mad:

It will be grate if some one could work it out.
[Nexus One Android Development] cred05:
Plus one on that. We need to combine all the best things from both devices to create one super rom...we shall then call it "Super ROM".
[Nexus One Android Development] 1wayjonny:
I was just discussing this with my brother, a steady 50% level of brightness looks better then the auto feature on the phone.

He just got his and I told him to shut it off its looks horrible, the green look so fake unless the brightness is on 55% steady and up
[Nexus One Android Development] jp2000:
I do agree with this: the Desire ROM is pretty damn consistent with the auto brightness.
[Nexus One Android Development] spyz88:
I didnt even bother checking for the auto-brightness on this ROM. I cant believe it works. Thanks OP :)
[Nexus One Android Development] guags99:
+1 on this! I figured I wasn't the only one.
[Nexus One Android Development] qvert:
would be cool if it's possible, but i am not sure if it will work?
[Nexus One Android Development] parrot5:
+$10 :D LOL
[Nexus One Android Development] cyanogen:
I know how to extract it. I'll have a look at try it out on my N1.
[Nexus One Android Development] jp2000:
Just use the desire rom. Why do some people not like it? I love it.
[Nexus One Android Development] cyanogen:
Because SenseUI sucks :)
[Nexus One Android Development] SPAS79:
I second that.
[Nexus One Android Development] spyz88:
Thirded (is that a word?) :P
[Nexus One Android Development] Lemim0uth:
I tried the Desire ROM some days ago, and the screen seemed brighter than the default Nexus ROM (both at max brightness). Anyone noticed that ?
[Nexus One Android Development] :
While we are on the subject of extracting things.... how about extracting the HTC Music app to be used on Cyanogen.... :D
[Nexus One Android Development] esincho:
the HTC stuff can't be
[Nexus One Android Development] erinata:
i am fine with the stock auto brightness.....

But I agree that it would be better if the base brightness is higher.
[Nexus One Android Development] erinata:
It's because those desire rom are all in alpha.

And I dun like app2sd >_<
[Touch Cruise Android Development] SuperJMN:
Hello friends! I'm back again with the newest configuration I've found.

It's an Eclair build that runs exceptionally, with wifi, GPS and sleep working from the very first time.

If you want to try and forget your Donut build (1.6) you will have to do the following:

Choose a POLAIMG dated 20-Feb-2010 with your correct paneltype (1 is very common) and resolution from this site: http://sourceforge.net/projects/androidhtc/files/. Mine was POLAIMG-PANEL1-320.NBH (the most downloaded of them).

Download this file (http://www.homecncfun.com/wp-content/plugins/download-monitor/download.php?id=2) and extract androidinstall.tar from it. Copy it to your SD Card under a folder called "andboot":

Flash the previously downloaded .NBH file as usual.

During the boot you have to enter the Android Installer. A message will appear on the screen saying that you have to press and hold a button in order to start it. There are some buttons that are valid, for example, pressing the center button into the jog-wheel will work. Press it and hold it until the installer appears.

Select both System from NAND, Data from NAND.

Select Install.

Quit.

Let it start (slow).

What's working?

Wifi

GPS

Data connection

Phone - Calls, SMS

Sleeping (as far as I know)

USB Tethering (with PDANet)

Not working?

Camera

Audio input fails after the first use

Bluetooth

Live wallpapers

NOTE: If the screen resolution is wrong for you, you can change it modify system/build.prop. Guide here: http://xdaforums.com/showthread.php?p=5709153

Enjoy!

More info:

http://xdaforums.com/showthread.php?t=634782

To report bugs:

http://bugs.homecncfun.com/
[Touch Cruise Android Development] reiteravi:
i think poly's 2.1 beta is newer

http://xdaforums.com/showthread.php?t=600154

anyway on both roms on polaris nand wifi is turning on but almost

non productive-slow

as well as battery issues u need to calibrate as mentioned on other posts
[Touch Cruise Android Development] defroster:
*sigh* :(

was ALMOST about to finally try it out..

what's the gps like? is it just tomtom or whatever apps or some google thingie?
[Touch Cruise Android Development] Kiiv:
I've tried this one yesterday on SDCard with a partitioned system (cause I can't flash to NAND...) and it's very very slow :(

Don't know if it's better on NAND but I doubt that the difference could be so big...
[Touch Cruise Android Development] raist1976:
I don't find it really that slow... It's a little slower than 1.6 of course, but it's still quite usable.

One thing that really put it down is that I know have an audio bug that affect the phone calls.

After calling one (or beeing called) the sound will not work (either people won't hear what I say or I won't heat people).

I have yet to try the other 2.1 build but I think this could be the end of 2.1 for the time beeing and going back to 1.6 while waiting nexus to be out in france :)
[Touch Cruise Android Development] k_o_t_s:
Is there any way to run this with the classic haret method (all files into the root of sd card)?
[Touch Cruise Android Development] meknb:
http://xdaforums.com/showthread.php?t=600154

and follow the sdcard install method.
[Touch Cruise Android Development] Polarfuchs:
Hi, I installed this with the SD Method to use it from WinMobile

I once was in android but had to restart because I did not turn off key lock in windows mobile before.

But now i can't boot into android or only at 2% chance.

I get ther error "msm_i2c msm_i2c.0: Error waiting for notbusy" and android wont boot. What should I do?

I have partitioned my 8GB SDHC with gParted to "7GB Fat32/270MB EXT2/271MB EXT2"
[Touch Cruise Android Development] st_voss:
Just reboot to WM and run haret again. After two or three attempts the

Android boot works without "Error waiting for notbusy" messages.

Regards,

Stefan
[Touch Cruise Android Development] Polarfuchs:
You are right, but now I enter my pin it says sim is locked and i can't unlock the phone.

I already did deactivate throttlelock and keypad lock in winmo.

Also the pin-pad is too large for my polaris.

What can I do?

And another question:

In the haret.zip there were two images, zImage and zImage-eclair.

Did I install Donut, because in my default.txt there is

and not zImage-eclair
[Touch Cruise Android Development] reiteravi:
if installing 2.1 than change in default.txt to zimage-eclair

if 1.6 leave it as zimage
[Touch Cruise Android Development] Polarfuchs:
Ok then obviously I installed donut 1.6

And I will redo with eclair 2.1 and see if I have the sim locked error and too large screen there too.
[Touch Cruise Android Development] raist1976:
For you information, I just went back to Warm's Donut as any 2.1 build only allows me to call once then the audio will stop working. Ergo I need to reboot after each call... not usable !

Maybe people can tell me if they have the same problem or not ? Maybe it has to do with the radio that I'm using ? (I haven't updated since more than 1 year)...
[Touch Cruise Android Development] Polarfuchs:
This is really annoying, because it means you can only boot at 20-30% chance.

And every time I have to wait until win mobile has rebooted.
[Touch Cruise Android Development] Kiiv:
Don't know why, but it's really slower than all hero or tattoo builds I tried, to make a comparison.

Maybe my SDCard isn't in its best days...
[Touch Cruise Android Development] Polarfuchs:
Same with eclair, keypad really to big. One complete row is missing, numbers 7,8,9,0 and enter. (even though I set lcd.density to 128 in default.txt)

And the display always turns off after one second till i use the jog wheel again.

I cant enter the pin.

OK, I just read that with "turn off pin in win mobile" it is meant to turn off phone-sim pin. And not device pin. Then I will turn on my phone in win mobile to turn off pin requirement and see if android works.

--------------------------------------------------------

Need help again.

Eclaire runs pretty smooth, I had worse expectations.

But when I click on the android logo to start, I then click skip and the only option left is to create a google account or log into an existing google account. Even if I log into the account it says I can add more google accounts or press back. But if I press back I get to the google thing again.

And more worse it costs 3G data, 0,09€/minute

EDIT: I did turn off my phone function in win mobile and instead did turn on wifi. Then it took my again 3 times to boot android, but now the wizard no longer blocks android gui. yeay
[Touch Cruise Android Development] Polarfuchs:
How can I turn off the phone function in android?

EDIT: found it under "Modem" pretty weird

EDIT2: Im not quite sure, but i think phone is still on, where the hack can I shut off the usage of phone :confused:
[Touch Cruise Android Development] raist1976:
Well ... after putting back the warm donut I do can see the speed difference...

But over the two eclair builds, the kaiserdroid seemed the fastest.

There are some speed problems for some actions, but most of the time it's usable.

Anyway I went back to donut hoping to fix my problem of "one call allowed or reboot" without success... might be the new nbh that I flashed lately ... or the radio not compatible ?
[Touch Cruise Android Development] Polarfuchs:
I can't boot again. I tried 9 times and it show "error waiting for notbusy" every time.

Does this come from taking out the SIM card? I did this because I found no option to deactivate the phone function in android.

EDIT: Now I set the "ppp.nostart=1" and could boot into android after 2 tries withot SIM card inserted"

Wifi is really sloooooow

It is only tech-demo, wifi not really good, market place does not open, keyboard too large (fills 80% of screen), many other things.

I'll wait either for a better version of android for polaris or till I can afford a HTC desire :D
[Touch Cruise Android Development] tmcfarland:
I have flashed my Polaris using the same nbh and rom as described in the first post. To fix the density, I tried to edit build.prop file from 160 to 120 using Astro but Astro will not save my changes to the file. I checked the file properties and I do not appear to have rw access even after issuing the $"su" and #"mount /system -o rw,remount" commands using the terminal program. I am not very Linux savvy ... have I missed something? Thanks!
[Touch Cruise Android Development] Polarfuchs:
Can't you just edit the default.txt and reboot android?

In the default.txt are comments which say that you just have to add lcd.density=128 in the file.

Like this:

#alloctest 0x2000
set RAMSIZE 0x08000000
set MTYPE 1723
set KERNEL zImage-eclair
set initrd initrd.gz

set cmdline "ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 board-htcpolaris.panel_type=1 lcd.density=128 no_console_suspend clock-7x00.mddi=0xa51"
boot
[Touch Cruise Android Development] tmcfarland:
I think that default.txt is specific to booting via haret where I have flashed to nand. From what I have read, I have to edit build.prop to change the density ... but I seem to be having difficulty getting rw permission to do so. Thanks.
[Touch Cruise Android Development] Polarfuchs:
Ah, yes. You are right, I overlooked that you are on NAND.

Here are the instructions for getting permission:

http://xdaforums.com/showpost.php?p=5708867&postcount=6

And here some resolution/density recommendations:

http://xdaforums.com/showpost.php?p=5710465&postcount=10
[Touch Cruise Android Development] tmcfarland:
Those are the instructions that I have been following, but I do not appear to be getting write access to build.prop after issuing the first su and mount commands. I am unable to save changes, the file properties appear to be read only. I have entered the commands using terminal several times and can't see what I have missed ...
[Touch Cruise Android Development] Polarfuchs:
And you are right again.

Even though I run android on SD Card i have the build.prop present, too. And if I try tu get permission with su mount command I also can't get access like you. :(

BIG EDIT: you must not type the su and mount command in one row

you have to type

then hit enter then afterwards you can go on with

EDIT again:

it seemed to work but it sadly does not, as you mentioned :(
[Touch Cruise Android Development] tmcfarland:
Got it, thanks to berardi ... the build.prop can be edited in androidinstall.tar before applying to nand, worked like a charm. This is for when you give in and flash to android. ;) Thanks for your input!
[Touch Cruise Android Development] Polarfuchs:
Then I will have to go to my linux Vm on my pc and edit the build.prob there. Because my build prop lies on the ext2 sd card.

EDIT: that worked for my SD Android, :)
[Touch Cruise Android Development] QAN:
Sound problem when calling

I do not have this problem. Do you have the latest radio installed?

Gerald
[Touch Cruise Android Development] Polarfuchs:
Hi,

I really heave problems with wifi.

Android market tries to load and suddenly quits.

Surfing does not work-the url gets displayed in the url bar bot then the browser loads and loads and.... and no page comes up.

As you can see in my signature I have radio rom 1.59.44.02 and have no wifi probs at winmobile6.1
[Touch Cruise Android Development] tmcfarland:
Which build are you using? I had this problem with Poly's 2.1 from the kaiser forum, but not with kaiser-eclair ...
[Touch Cruise Android Development] Polarfuchs:
I took the zImage-eclair from sourceforge http://sourceforge.net/projects/androidhtc/files/ from 20.02.2010

But I have to admit that i can use wifi but with very few range and very slow.
[Touch Cruise Android Development] chourmovs:
i've tested everything since Christmas and eclair build become slower and slower on each kernel release, for sd card method i mean

with donut you can say bye bye to gps and even wifi with new kernel

I'm tired of that and I'm going to make a pause of a month in my test of android on POLA100 :o

I'm not really interested on nand flashing too
[Touch Cruise Android Development] SuperJMN:
Are you having problems with speed? I think Eclair is still a lot slower than Donut.
[Touch Cruise Android Development] chourmovs:
that what i said, and donut give gps,3g and wifi issue at my last attempt (myn's rom) :(
[Touch Cruise Android Development] ufo2121:
same error

Hi,

I am getting the same error on my polaris every thime.

What did you do to fix it?

Radio: 1.65.30.09

ROM: 5.2.23016 WWE
[Touch Cruise Android Development] Polarfuchs:
I did set board-htckaiser.panel_type=1 in the default.txt But I'm not sure that this solved it completely.
[Touch Cruise Android Development] Polarfuchs:
That is weird.

I thought I fixed it, but after I power down my phone completey over night.. Now I booted win mobile to start android.

And again even after 5 times, I'm not able to boot to Android because of the "error - waiting for notbusy"
[Touch Cruise Android Development] raist1976:
The radio version was the culprit ! I had a bad version (1.70 olinex). After I upgraded to 1.59.44.02, I was able to call several time in a row without losing sound.
[Touch Cruise Android Development] Polarfuchs:
Is there a proof, that editing the defaults.txt does influence the android boot from Sd card after the installation.

For me it seems, that default.txt only applies when installing.

For example I edited the lcd.density in default.txt but after android booted up it had the old lcd.density setting.

Only after I took out my Sd card and edited the build.prop in linux the lcd.density had changed.
[Touch Cruise Android Development] ArtaxXP:
hey guys, i've a really bad problem...

i flashed the .nbh file...after reboot, it vibrates two times and nothing happens...just a flickering white screen.

i'm unable to get into the bootloader again. i've tryed nearly everything...is it possible to enter (if it is still there^^) or rewrite the bootloader via software + usb without recognizing the polaris? because there is no reaction when i plug in the usb cable...any ideas?

please help!

edit:

ok fixed...removed the battery for 1 minute...starting bootloader works now!
[Touch Cruise Android Development] reiteravi:
u probably could search but anyway

take out the batt for 1 min and put it back

take out the sdcard and keep it out

switch on

as soon as u see looking for sdcard hold soft-reset (stylus) and camera

when u see the tricolor boot loader leave the stylus and when it says serial

leave the camera and voila boot loader ready to flash
[Touch Cruise Android Development] guanodude:
Mmm... Let's see if and how and how good this works.

If only I could get my usb drivers to work in Vista, because of the resolution-problem...

Work in progress for now thus...

Update: I've now changed the tar-file and reïnstalled it, seems to fix it. Will provide a link tomorrow.

But I don't have internet, though.

Is there any way to remap buttons?
[Touch Cruise Android Development] Arkish:
Thanks

Just installed NAND method on 02 Orbit 2, Panel Type 3 - 320.

Running polys 2.1 will now try others.

I had a lot of issues doing an install with a Sandisk 8GB SDHC, but changed it to a 2GB SD card and it worked fine. The 8GB card was corrupted :mad:

Best tip on here: If you are having problems REMOVE the battery for 30 seconds and then reflash.
[Touch Cruise Android Development] Polarfuchs:
That is weird. I have it on my Sandisk 8GB SDHC card and no problems.

But I made these 2 EXT2 partitions additionally to the standard fat32 Partition.
[Touch Cruise Android Development] Haru13:
I've tried the version within the link on the first post and touchscreen doesn't work...furthermore, the screen def looks to be more than 320x240 (altough i've put the 320x240 parameters in the deault.txt)...have you got this problem?
[Touch Cruise Android Development] larstnt:
Yes, is a problem with the LCD density in the build.prop, it is 160, and it must be 120 or 110. You must correct this manually. In the first post is the link to how to do this.

I have done this:

1 - Donwload Better Terminal

2 - Follow this instructions:
[Touch Cruise Android Development] Haru13:
Ok...Is it also possible to change it in the defaut.txt? Because i'm not even able to enter in android...I'm stuck on the first step on installation (where we have to press on the green android) the tactile thing doesn't work...
[Touch Cruise Android Development] raist1976:
New Polarythmic build ! FAST !!!

I'm now testing a new build from polarythmic for kaiser (http://xdaforums.com/showthread.php?t=600154) and let me tell you that the speed is incredible !! I don't see any difference with Myn's warm donut !!

Well from stock install, there was a difference : the home screen was often reloading due to low memory threshold, but I've adjusted this by taking the values Myn was using on his build (see this post : http://xdaforums.com/showpost.php?p=5806066&postcount=2156) and I now have the BEST ECLAIR BUILD EVER.

You definitely have to try this ! He even included some settings icons taken from the desire rom :cool:

Best of all, every single f***ing live wallpaper works on our Polaris !!

YES even the one with the couloured dots running on the screen.

Of course don't expect fast live wallpaper like on the nexus, and It seems not to respond to touch, but still, what an improvement !
[Touch Cruise Android Development] Polarfuchs:
And how get I running it without msm-i2c error? I really want to run android on my polaris.
[Touch Cruise Android Development] rcravero:
After every call I have to reset the phone. The audio is missing. Even if I receive or I make a call
[Touch Cruise Android Development] SuperJMN:
How are you getting more speed? Installed data to NAND or to an Ext2 partition?
[Touch Cruise Android Development] raist1976:
Don't temper with the sysinit.rc like I did. it's way too memory intensive for the polaris... It was better at first but system because close to non responsive.

I'll try to change only the home application setting but polyrythmic suggested to use the spare parts tool for keeping home app in memory (my main concern about this build)
[Touch Cruise Android Development] raist1976:
I'm on nand, both data ans system and it's really the fastest eclair I've seen.

I have to use a little more to see if it will be able to replace myn's warm donut until he gets his 2.1 ready, but so far so good (except for the home app that doesn't stay in memory and tempering with sysinit.rc is not an option for now)
[Touch Cruise Android Development] peciss:
Caller can't hear me in outgoing call. - problem with radio?

Is some update with working camera?
[Touch Cruise Android Development] raist1976:
I had this problem and it was fixed with this radio rom : http://xdaforums.com/showthread.php?t=453190
[Touch Cruise Android Development] peciss:
How to flash it? I have android in NAND.

Got it - just pull out the battery and turn on with hold down camera button.

I'll test it!
[Touch Cruise Android Development] ZeGuido:
I give it a try. This Eclair is slightly slower than donut (on SD) but usable with a NAND install. I couldn't install Data on SD so I have everything on NAND.

Wifi works perfectly.

No problem with call or audio.

I couldn't manage to get GPS work (with GPStest, it shows satelittes but cannot give a fix). I downloaded GoogleMaps, and get the same. I remember there was once a different map app to install to get GPS working, but I cannot get reference anymore. If anyone can help, thanks in advance.

Also found this report but I couldn't find the exact widget on the market. Everytime I plug usb, my SD card is unmounted and Android give me a notification of missing SD. If I try to take it ou and in again, it doesn't mount. I have to reboot to get the SD back.

Also reboot or turn off while charging doesn't work correctly (need a reset afterward).

Cool work.