yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] Niscandia:
.... well I feel stupid <laughs> I should brush back up on my shell scripting, and try not to confuse it with C or Lua....

So as I asked before, what one should be used...

Though I wonder if the -t option is needed in mount command for the partitions. Linux has normally been very good at figuring out the type of partition... I'll give that a try, (along with fixing the > with -ge....).

If it works, then the end user could decided (with information like what you've listed above.) Just as long as the format supports appropriate permissions... I'm not sure if I want to see what Android would do if the system was fat32....
[Tilt, TyTN II, MDA Vario III Android Development] Sheytoon:
Hello friends,

I hope everybody is doing great. I was out of country for a month (and didnt have access to internet) but was thinking about this project a lot. I thought by the time I am back there have been lots of improvements made. I just got back and see the last image is from March 12th. Please dont get me wrong, I am not pushing, I am just wondering if things have changed or moved to other places.

Is the zImage from March 12th the latest?

http://it029000.massey.ac.nz/vogue/files
[Tilt, TyTN II, MDA Vario III Android Development] SharpieMarker:
I would assume its some bottleneck regarding running the OS off of the micro sd card and reading images off of the flash card at the same time. Like attempting to copy files from multiple directories on an external hard drive.
[Tilt, TyTN II, MDA Vario III Android Development] beardface:
Does anyone know why my location currently shows me traveling around east palo alto?

When i open google maps, i was surprised to see 'my' location actually updating.

I know GPS isn't working yet (I'm on the Kaiser (ATT Tilt))... But whose location am I actually getting?

It doesn't appear to be a fixed default location, since its actually traveling.
[Tilt, TyTN II, MDA Vario III Android Development] Completenutter2:
This has been answered a few times, but you're seeing a demo. don't worry.
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
Ok, to get you up to date: http://www.androidonhtc.com/kaiser/latest_builds ;)

I have set up a site (gigatron.de, linked in above) where you can get the latest kernels and also a link to the list of changes made.

I have to ask dzo if he wants to share/commit that change which enables calls via headset. Maybe we can merge it into biktor_gj's proposed change, which looks good. But I actually wonder if not moving the whole Kaiser stuff out to a separate module wouldn't be even better. Right now I'm a bit short of time, though.

Stefan
[Tilt, TyTN II, MDA Vario III Android Development] SharpieMarker:
Does anyone else have a problem with having audio notifications with a data usb cable plugged in? I get audio notifications just fine with a charger plugged in but had no alerts (text messages mostly). My phone rings for incoming calls though.
[Tilt, TyTN II, MDA Vario III Android Development] Sheytoon:
Cool Thanks for the quick update. I appreciate it.
[Tilt, TyTN II, MDA Vario III Android Development] Pandemic187:
So this is kind of a delayed question, but I get no sound in calls. I'm using the 4/03 kernel, and I did the things the wiki said to do. Any way I can fix this?
[Tilt, TyTN II, MDA Vario III Android Development] Sheytoon:
4/3 kernel? Where did you get that? I thought the latest kernel is March 12th.
[Tilt, TyTN II, MDA Vario III Android Development] ajclai08:
http://gigatron.de/.android/builds/
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
Hi,

I just pushed a heap of usb code to git. It works for the mass_storage function driver but not for ether which would be more useful. I haven't tried it much on kaiser and haven't implemented usb plug/unplug except on vogue but it should work if you boot plugged in. Mass storage isn't much use to us because we need the sd card mounted and so it can't be exported as a raw disk. To test, I created a new partition on the card and added:

echo /dev/block/mmcblk0p2 > /sys/devices/platform/usb_mass_storage/lun0/file

to the end of the init script in initrd.

Mounting mass storage worked on Ubuntu 8.10 and Win XP machines but not Fedora 8 or Vista.

To try the ether driver, comment out usb_mass_storage and adb at line 104 in common.c, boot and then do:

ifconfig usb0 192.168.1.2 up

on the device and:

ifconfig usb0 192.168.1.1 up

on the host (must have a linux box for this)

You can see it does send and receive data but there is something wrong, I don't know why.

Anyway it's a start and hopefully will only get better.

Enjoy.
[Tilt, TyTN II, MDA Vario III Android Development] joel2009:
No the market does not work over proxy, this has even been a problem for unlocked g1 owners from what i have read.
[Tilt, TyTN II, MDA Vario III Android Development] ibanezbass:
I can't send mms messages... i think i have all the right settings but maybe i missed something?

AT&T

mmsc: http://mmsc.cingular.com

proxy: wireless.cingular.com

port: 80

? Is that right?
[Tilt, TyTN II, MDA Vario III Android Development] lanwin:
Ok, good to know know that i am dose not doing it wrong :-) Dose they told if it would work with the next sdk?
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
I found the USB problem, it needs DMA to be page aligned, latest git commit makes ether work. If you start telnetd and bring up usb0 you can telnet to the phone over the usb connection, root password is vogue.
[Tilt, TyTN II, MDA Vario III Android Development] poly_poly-man:
wow, dzo... haven't gotten a chance to test any of your commits yet, but given the bulk and descriptions of them, they sound good!

I was watching them come in one by one on my rss reader as I was writing a thesis for history... what a drag... anyway, I won't get a chance to test the stuff out or check out the code until at least tomorrow... I should be sleeping now :P

wow.. what a pointless post.. I really am tired...
[Tilt, TyTN II, MDA Vario III Android Development] radem205:
Thank you dzo for your hard work! Great job!

Do we have to use a new initrd or only compile a new zimage? Could you post the new initrd if we need this too?

What are the benefits of a working USB driver? Could we get more information of our android phone now?
[Tilt, TyTN II, MDA Vario III Android Development] coincoinlapin:
Amazing work as usual.

By the way, I can't remember if data autoconnect on startup has been disabled on purpose or the reasons to do so.

If it hasn't been disabled, then does it mean that my settings in default.txt are wrong (my apn requires no login/password, just ebouygtel.com).
[Tilt, TyTN II, MDA Vario III Android Development] stringbean82:
As soon as I find some spare time am going to test it out on the Kaiser.

Dzo: did you already have the new zImage available on your website? tnx
[Tilt, TyTN II, MDA Vario III Android Development] radem205:
Here you have the new zimage (I don't know if a new initrd is needed too).
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
Just go to http://gigatron.de/.android/builds/ (the changes dzo made are in the repo, so the kernels are up-to-date).

Great work, dzo, thanks! Can you tell us what you did for the headset to work in calls? Then we can apply that seperately...

Concerning WiFi: I have played a bit, and I have the feeling that it really doesn't work because the eeprom data is not fed to wlan_loader. "-e /proc/calibration" is really just a stub argument, because that file doesn't exist. The wlan_loader source code loads the eeprom data (40000 bytes) from /dev/mem @0x13f13000 if "-n" is given instead of "-e ...", but I think that wouldn't work because that address is not mapped. Anyway, I tried a full eeprom dump (as I understand it, it is just a matter of reading the NAND storage) by enabling the MSM NAD device, MTD and MTD block/character devices and dd'ing from the character device to a file. I found my WLAN MAC address (in reversed order, see http://xdaforums.com/showthread.php?t=322225) in the dump but in a block of what seems to be only 4K of useful data - IIRC at offset 0x250000 or 0x2500000.

If someone with more time could try this: extract the 4K block in which you find you MAC address to a separate file, and feed this to wlan_loader via the "-e" arg. The other thing to try out would be to not disable and not reset wlan as we boot and load the driver and see if it is working then.

So much for now,

Stefan
[Tilt, TyTN II, MDA Vario III Android Development] empy16:
Hello and sorry about the off-topic.

I just wanted to ask, why some of the programs put in the Androidapps don't apper in the menu? (In my case all of the programs except solitaire)

Thank you in advance
[Tilt, TyTN II, MDA Vario III Android Development] biktor_gj:
Great work dzo! Of course it doesn't work for the nike, it doesn't do the usb reset on boot, and doesn't detect it later, and unplug and plugging back doesn't work either, but I guess is normal. I was wondering, how do you tell the driver it has been plugged in? I would want to trigger it manually to test if I can wake it up from the usb_detect gpio pin, but don't know how to tell the driver there has been a change and it should go online...
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
htc_cable_status_update(CHARGER_USB) should call msm_hsusb_set_vbus_state and take it online.
[Tilt, TyTN II, MDA Vario III Android Development] imfloflo:
God work Dzo.

Just test on Polaris and we have some little issue.

We must plug in USB to boot android.

LED don't work anymore.

and USB plug in doesn't detect and don't charge the device anymore.
[Tilt, TyTN II, MDA Vario III Android Development] biktor_gj:
That was fast! :)

Shame it's already doing that from battery.c so then it's got to be something else... Will keep looking then! thanks!
[Tilt, TyTN II, MDA Vario III Android Development] krisje8:
I tried to do that, but it errors on my pc when doing that ifconfig:

krisje8-debian:/home/krisje8# ifconfig usb0 192.168.1.1 up
SIOCSIFADDR: No such device
usb0: ERROR while getting interface flags: No such device
usb0: ERROR while getting interface flags: No such device

Also, lsusb does not show my kaiser at all.

dmesg only shows a device unregistering when I boot android.

(Yes I did uncomment those 2 things and compiled my own kernel).
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
I've looked more into Wifi, and added some more info at http://projects.linuxtogo.org/tracker/index.php?func=detail&aid=32&group_id=37&atid=273

I think we really need to recompile the wlan module and probably wlan_loader (which could in turn load the eeprom data from the right position) for using it with the current kernel.

Stefan
[Tilt, TyTN II, MDA Vario III Android Development] Ratpack309:
Battery Life?

First, a giant thanks for the devs getting this far this fast.

I'm wondering what experience people are having with battery life on a standard tilt battery. I'm using the 4/7 build from http://gigatron.de/.android/builds/.

I lost the post now, but I saw a while back Stefan mentioned something about 2 days of life on this build. I have pm.sleep_mode set to 1, but I'm getting a few hours of life at the most. The battery seems fairly normal under WinMo. I get around a day / day and a half depending on use.

I wonder, at this point without many of the power saves being activated, is the general consensus that leaving togga connected drains that much extra power? Or is it something more sinister like a failing battery?
[Tilt, TyTN II, MDA Vario III Android Development] beardface:
Help with build

I'm trying to build the zImage as a starting point; (for kaiser), following directions found here:

http://www.androidonhtc.com/get_involved

I'm getting the following build error when trying to make the kernel (zImage)

drivers/build-in.o: In function 'akmd_ioctl':
drivers/i2c/chips/akm8976.c:766: undefined reference to 'get_akm_cal_ram'
make: *** [.tmp_vmlinux1] Error 1
[Tilt, TyTN II, MDA Vario III Android Development] Pandemic187:
The newest kernel won't boot on my phone, which is strange since I've never had a problem with any of the other kernels that I've tried.
[Tilt, TyTN II, MDA Vario III Android Development] skola28:
Make sure your phone is plugged into your computer via USB.
[Tilt, TyTN II, MDA Vario III Android Development] poly_poly-man:
you made vogue_defconfig, right?
[Tilt, TyTN II, MDA Vario III Android Development] Pandemic187:
I don't quite understand. Why make a build that requires the user to do this? I've never had to do this with any previous builds.
[Tilt, TyTN II, MDA Vario III Android Development] radem205:
All the builds are experimental builds, so sometimes it isn't working as it should be, but they are working on it. So be patient and you will get a fully working android version in the future!
[Tilt, TyTN II, MDA Vario III Android Development] seidler2547:
Somehow the USB code does something that prevents booting for some devices. I never had a problem on my Kaiser, though. We need to investigate...

I have data connected all the time, and 2 days of battery life. DId you do read this? It's not totally up-to-date, but short version: run down the battery in Android until the phone shuts off, start up Android and charge fully (3hrs+).

We need to update those. Read http://wiki.xda-developers.com/index.php?pagename=BuildTheKaiserKernel

HTH,

Stefan
[Tilt, TyTN II, MDA Vario III Android Development] SharpieMarker:
Something about the new kernel doesn't like me. I managed to boot into android via a USB cable (I have a tilt/kaiser). It didn't like coming back from screen off mode and would lock up until I slid the keyboard out. This worked for a few minutes until android locked up all together with the screen off and the amber led lit. I reverted back to the old image for now.
[Tilt, TyTN II, MDA Vario III Android Development] rkadar1:
sharpiemarker.... same thing happens to be with most of the new kernels... android always gets stuck after sleeping!!! which build did you revert back to? and if you dont mind sharing ur default txt again
[Tilt, TyTN II, MDA Vario III Android Development] Ratpack309:
Thanks. I'll give that a shot. Don't know how I missed those directions.

I've been working on my PS3buntu lately, but I think I might take a break and try my hand at some of the issues left with android. I probably won't be a giant help, but I suppose it's the effort that counts.

Thanks again for all the work so far.
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
Looks like the USB gets powered down by wince when you unplug it and so the first write to it crashes everything. I'll trace it when I have some time and see what's happening.
[Tilt, TyTN II, MDA Vario III Android Development] SharpieMarker:
I reverted back to Dzo's 1.1 from a while ago (possibly march 1st) which is the one I've been using every day for a couple weeks now. I'd be more than happy to share my default.txt but its just a modified default-kaiser from Dzo with my subscriber info in it. If you need it I'd be more than happy to post it.
[Tilt, TyTN II, MDA Vario III Android Development] outsider787:
Just a comment on Kaiser freezing/being unresponsive once it's put in sleep mode.

I'm still using the 03 April build, and from time to time I still get in a situation where I can't wake the phone up except by sliding out the keyboard.

And when the keyboard is closed, and the phone is put back into sleep, the only way to wake it is with the keyboard being opened.

Now this doesn't happen often. I've been using the 03April build since it came out, and I've only had this issue a couple of times.

What I did notice that the LED that flashes, is flashing green (meaning the CPU is actually working, and not in sleep mode).

When the LED is flashing red, I can wake up the phone every time. Green... no go. I urge others to note the state/color of the flashing LED when they can't get into the phone.
[Tilt, TyTN II, MDA Vario III Android Development] stringbean82:
Just want to comfirm that happens here as well, my collegue and I have both Android running on a Kaiser and both have this issue sometimes, just happend 1 minute again.

Slide it open and the console appears and back to the gui and fine again.
[Tilt, TyTN II, MDA Vario III Android Development] ibanezbass:
I have this problem as well. Except sometimes even sliding the keyboard out does nothing.
[Tilt, TyTN II, MDA Vario III Android Development] krisje8:
I compiled myself a kernel, and I can confirm that booting without usb cable attached works now :)

P.S.: Can someone please fix the forcing connection bug? I haven't been able to actually use android for a few weeks now because of it.

(I want to be able to use android _without_ a data connction, like I could a few weeks before).
[Tilt, TyTN II, MDA Vario III Android Development] 4242:
andriod issue on kaiser

Trying to run andriod and keep getting this message

I have formatted to fat32 on the sd card and i still get this message, how do I fix this?

Failed

No partition found on SD card

/bin/sh: can't access tty; job control turned off

[ 3.510000] SND: ch 3 CLOSED --> OPENED

[ 3.510000] SND: ch 2 CLOSED --> OPENED
[Tilt, TyTN II, MDA Vario III Android Development] joshkoss:
Hi sir,

I've merged your new thread into the existing andriod dev thread we have here in kaiser.. Hope you find your answer.

Take care,

Joshua
[Tilt, TyTN II, MDA Vario III Android Development] renegade29a:
I can confirm this, but the usbnet stuff is not working yet. Nothing happens when I connect my Kaiser to the USB port. Do I have to load the modules manually on my Linux PC?

PS: How do I get from Android to the boot console? FN+Left doesn't work for me. (Doh, it's the key above R)
[Tilt, TyTN II, MDA Vario III Android Development] QAvatar:
Rookie

All,

I have spent the last hour reading through the last few weeks of posts and trying to understand all of the stuff that you are all doing. I appreciate you doing all of this.

I loaded the zipped action from 3/12/09 and it worked well. It had some issues and I decided to wait a while before using Android full time. The little that I did see was AWESOME! You all have done a great job and I am impressed with your understanding of all of this.

My dilemma is as follows. I grabbed the latest zImage from the gigatron location and I copied it to my SD card. When I launch the haret and try to start android, it tells me that it can't load the initrd.gz file from 'storage card/initrd.gz'. The only initrd.gz file that I have is the one from the 3/12 experimental build. Can any of you tell me why it is saying that? Is there a new initrd.gz file? I have read and read and read and tried to find one, but couldn't see anything.

Sorry for the rookie question. I just want to help test. I work in QA and think that I could help this project from the testing side.
[Tilt, TyTN II, MDA Vario III Android Development] outsider787:
How does one return to the graphic OS from the boot console?
[Tilt, TyTN II, MDA Vario III Android Development] outsider787:
Strange behavior on battery life/charging.

I was draining the battery in android to reset the counter, and after the phone died, I plugged it to recharge it (The phone would not re-boot without the charger, so I thought the battery was totally drained)

When I booted into WinMo, the battery indicator showed about 10% battery left, so I pulled the charging plug, to let it drain further. Next minute the phone shut off.

Began charging it again, and booted into WinMo, and battery life is still around 10%.

Booted into Android, and it's been showing 42% battery life (and charging) for the past 1/2 hour...

something's not right... using the 03 April kernel.
[Tilt, TyTN II, MDA Vario III Android Development] renegade29a:
outsider787: To return press FN+Right Softkey (the one above I)

QAvatar: You have to put the initrd.gz, system.img and data.gz in the root folder of your SD card. You can put the other files in a different folder.
[Tilt, TyTN II, MDA Vario III Android Development] Chaisu:
"Failed No partition found on SD card"

I'm having this same issue and have done all that I know how with the default txt to no avail. I have also reformatted my sd card to fat32 and made sure all needed files are on the root of the mSD card. this is the error message i get when linux is loading "Failed

No partition found on SD card

/bin/sh: can't access tty; job control turned off"

then it just freezes and I have to soft reset.

Thanks for any help.
[Tilt, TyTN II, MDA Vario III Android Development] Niscandia:
Well quick question, what archive did you get your initrd.gz from?

Since there are quite a few versions of builds... It would help to know what one your are using.

I would guess you should be using the 3/1 archive. Possibly with a newer Zimage.

And the only time I got that error is when I miss packaged the initrd.gz... (big blunder, didn't include some key items....) So you might check to make sure you have the correct initrd.gz. Other then that, you'll probably have to wait for someone that had dug into the system more then I have.
[Tilt, TyTN II, MDA Vario III Android Development] Chaisu:
i used the march 1st bundle from http://www.androidonhtc.com/kaiser:latest_builds

i've also tried some of the experimental zimages.

i'm currently installing an android cab from this users youtube video http://www.youtube.com/watch?v=isnKZJsStvo but have no idea if it will work. I'll post back if it does.
[Tilt, TyTN II, MDA Vario III Android Development] joel2009:
android doesn't yet directly work with the power chip, it just starts at a value goes up or down with charging/draining while in android. (from what i understand... someone correct me if i'm wrong)

EDIT: http://xdaforums.com/showpost.php?p=3443635&postcount=4183
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
I put a kernel and initrd on my site with working usb on kaiser. To try it out you need a linux machine.

http://it029000.massey.ac.nz/vogue/files/?C=M;O=D

Boot with usb plugged in, disconnect and reconnect the usb cable.

Now do:

ifconfig usb0 192.168.2.2 up

telnet 192.168.2.1

On the host machine and you should be able to log into the phone, the root password is "vogue".

If you unplug the cable it will stop working and not reconnect properly.

Martin
[Tilt, TyTN II, MDA Vario III Android Development] rkadar1:
kernel downloads but initrd link not working
[Tilt, TyTN II, MDA Vario III Android Development] catchfire:
awesomeness and win. it works :)
[Tilt, TyTN II, MDA Vario III Android Development] marcelkordek:
hi martin, tested on polaris... don't boot stopped at "set sd clock - 0 1"

i think it only works on kaiser ?!

marcel
[Tilt, TyTN II, MDA Vario III Android Development] Smultie:
Same problem here :(
[Tilt, TyTN II, MDA Vario III Android Development] imfloflo:
on polaris zImage and initrd.gz boot fine but no USB cause no keyboard to type the commande in a terminal :s
[Tilt, TyTN II, MDA Vario III Android Development] marcelkordek:
have you plugged or unplugged usb at boot ?
[Tilt, TyTN II, MDA Vario III Android Development] radem205:
You have to plugin the usb while booting. Then it will work. But for the polaris I can't reach the phone by using this command:

ifconfig usb0 192.168.2.2 up

telnet 192.168.2.1

I've replugged the USB cable after booting, without results.
[Tilt, TyTN II, MDA Vario III Android Development] marcelkordek:
thanks... copy the new files again, and now it works (boot also without usb)
[Tilt, TyTN II, MDA Vario III Android Development] renegade29a:
Thanks Martin, nice work.

It seems though the usb driver is a bit unstable.

After a few commands I got disconnected, so I reconfigured usb0 on my machine and reconnected. Got disconnected again and couldn't reconnect. (Like you said)

If this works I could finally ip_forward through my machine.

I still don't get a data connection, not even gsm.

Android says "Not connected" but recognizes and shows "Simyo" (my provider)

Seems to be a problem with this provider. Does anyone get a connection with simyo and android?

(My radio was a 1.65.x one, now I tried a new 1.7.x didn't work either)

I removed my PIN in WM and now calls and Internet works.