Re: Another Android port: NITdroid
 

This "remove battery trick" has been here couple of times...

And yes, battery is charging if the charger is pugged and the battery is in, it does not matter is it Nitdroid, Maemo, Mer, or Deblet...

Re: Another Android port: NITdroid
 

I went to bed the first night with the battery at 8%, plugged in the charger under Nitdroid, and woke up the next day with it at 7%. Reflashed to Maemo, and the battery showed 5%, confirming it does not charge under Nitdroid. I now reflash to Maemo to charge it before bed each night. Charging may have worked under earlier Nitdroid versions, but a number of us confirm that the battery holds steady, but does not charge, under 0.3.2.

Re: Another Android port: NITdroid
 

That is really really strange... whatever poweroffs maemo, when battery is removed is not running when nitdroid is up, maybe something to do with that? I tought it would charge for sure, when there is no control for it at all. At least earlier versions were able to charge my n810s battery.

Re: Another Android port: NITdroid
 

Definitely strange. I wonder if its related to the warnings I get at each boot about something in Settings no longer responding.

Re: Another Android port: NITdroid
 

Charging works for me in my N810 with 0.3.2 although I always turn off the WiFi before as the open source WiFi driver knows next to nothing about power management and in my observations will drain the battery maybe faster than the charging speed, YMMV.

On other news, Google release many fixes to the master branch which hopefully soon will land in a new NITdroid release. I have been busy testing calibration with tslib and finding why USB in the latest kernel is broken but is very time consuming :mad:

Re: Another Android port: NITdroid
 

Thanks for the tip about the WiFi, that would be great. Is there anything we can do for you on a daily basis? I wish there was a testing suite we could run for you that would automatically collect data for you showing how well it performs for us.

In particular, we could type a phrase, such as the famous "A quick brown fox jumps over the lazy dog" using the OSK and the app would record how many double (or triple!) letters we get (and have to delete) and where the touches are being registered relative to the respective letters on the OSK. With the right logic behind it, if enough of us run such an app, the best calibration settings could be calculated for you.

EDIT: I can confirm that shutting off WiFi in Nitdroid allows the battery to charge.

EDIT 2: I spoke too soon. I just watched for 6 hours as the battery charge climbed from 5% to 100% under nitdroid with the wifi turned off. I unplugged it and was immediately greeted with a "low battery" warning. I reflashed to Maemo and was given the low battery alarm on powerup. The battery charge % indicator climbs under nitdroid when wifi is turned off, but now after two multi-hour tests, the battery was dead the instant I removed the AC power.

Re: Another Android port: NITdroid
 

For that we need to solve first the tslib integration, then any calibration settings can be used although I plan on using the data from the calibration settings in Maemo or the good defaults that ship with it.

EDIT: new release on it's own thread as this is getting massive.

Re: Another Android port: NITdroid
 

Hi all!

With the ADP1 (or rooted G1) one have the following firmware options:

Android 1.0 from firmwares US-TMob < RC33, UK-TMob < RC8, ADP1 1.0
Android 1.1 from firmwares US-TMob RC33, UK-TMob RC8, ADP1 1.1*
Android 1.5 (Cupcake) from source.

*shipped with my ADP1.

I flashed yesterday to a Cupcake firmware and it is exactly as NITDroid 0.4.2.

So I was wondering if the developers would like the idea a NITDroid version based on Android 1.1, better if based on US-TMob RC33 which includes the coolest features.

Cupcake is nice but it's in development and not usable for a daily basis as the stable versions. Just my opinion.

Thanks.

Re: Another Android port: NITdroid
 

Maybe... It seems to me that Android 1.1 is all bug fixing that went into the master tree just before the cupcake drop, I could compile a NITdroid version of that so RC33 apps works.

It seems xda-developers is distributing all those goodies without problems, I'm asking Google if I can distribute those Google apps within NITdroid, let's see what happens.

EDIT: Google response: you can't re-distribute.

Re: Another Android port: NITdroid
 

If you plan a NITdroid based on Android 1.1 I could help you test all the Google apps and differences between NITdroid and Android 1.1 on a ADP1 if you want.