yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] ALIEN_:
Thanks Enatefox. I've been reading this thread http://xdaforums.com/showthread.php?t=393182 however i'll lok through the thread you posted.

Cheers
[Tilt, TyTN II, MDA Vario III Android Development] stringbean82:
Looking forward into testing this, been playing all day with Android :) perfect test
[Tilt, TyTN II, MDA Vario III Android Development] szymonunion:
enatefox, stringbean82,

testing now... 1st thing:

I will try from console
[Tilt, TyTN II, MDA Vario III Android Development] szymonunion:
there is no /sys/power/wake_lock - I did 'find' for it, but I found only /sys/power/ directory and there is only state file, but with so small font I cannot read 'cat state' ;)

edit: started from console gave me: TIWLAN: TIWLAN - failed to start config manager

Regards,
[Tilt, TyTN II, MDA Vario III Android Development] archongtv:
Stupid question - why I can't connect to google account with 1.5 version? ;) I know that I have to use 1.1 and then upgrade, but why?
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
@szymonunion,

thanks for the feedback. Don't you love regressions? I used to be able to assign an IP to tiwlan0.

I don't know what Okibi did when he put the drivers in but I'm going to do it the way that I know of. I would assume he did the usual methods but I'd rather do it myself to be sure there's nothing amiss.

I wasn't able to touch /sys/power/wake_lock and I forget why at the moment. I didn't mean where it is when Android's running but if it came from initrd.gz or system.img. I believe the file needs to say "my_lock" or something like that. I'll find out later.

I'll update swifi, redo the drivers, etc. and post an updated image when I have a moment. I was getting "Failed to start..." and "No such device" errors but I didn't really investigate it further thanks to no "wake_lock" file.
[Tilt, TyTN II, MDA Vario III Android Development] okibi:
Regressions? That's what happens when you start from scratch on a new 1.5 build. Everything that was put in to make 1.1 work was not in the scratch 1.5 sdk build I started with. I've been adding tweaks that are compatible with 1.5. Others have simply taken everything from 1.1 that we changed, but then you pretty much end up with a hybrid that is not optimized at all.

The wifi drivers were added the usual way, however my initial builds did not use the drivers that you linked to a few posts back, but one that I had been working on. Here recently, I upgraded to other kaiser drivers (pretty sure the ones you posted a link to).

This wifi method isn't going to work in 1.5 just yet as wake_lock and wake_unlock are not in /sys/power/. They do, however, need to be added and setup in initrd.gz. I will do this when I get a chance or feel free to do it yourself.

Also, while I'd love to see ubuntu running on the kaiser, I have to agree with dzo in that it's not going to help with the wifi/gps/bluetooth at all. That stuff still has to be done in the kernel or else no matter what you set up isn't going to be able to interface with it.
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
My 2 cents... what i have found :)

We have several copies of the same files... of diferent versions and it seems... compiled diferently.

Example... we have a busybox in /bin and anothe one somewhere else.

the /bin one does not have the cp command... but does have the rm command... strange...

If i use this one, insmod and modprobe "work" but never find the modules.

If i use the other one, cp works etc etc... but insmod complains with

insmod: chdir (/system/modules)

modprobe as well, but the modules ar not there, they are in /system/lib/modules. i tried to find where insmod and modprobe search for the modules.. i though about export... or modules.conf... no luck...

so now, here we go... can't insert the wlan.ko...

Nevermind this, i've managed to insert the module. Now i'm at the wake_lock halt...

BTW...

I wasn't able to touch /sys/power/wake_lock and I forget why at the moment. I didn't mean where it is when Android's running but if it came from initrd.gz or system.img. I believe the file needs to say "my_lock" or something like that. I'll find out later. <- /sys is mounted in a sysfs filesystem... where "WE" don't create files.... the system does... layman explanation :)

Edit:

Might be wrong here.... i'v read a explanation site on the wake_lock file... aparently it forbids the cell from suspending or entering idle.

Many devs found this method useless, prefering the other ones.... those that use the refered STATE file...

now... looking at this site

http://android.git.kernel.org/?p=pl...ff;h=24f0be0e9a23b41683dea619ead9739615c83fac

i could see:

-#include <hardware/power.h>

+#include <hardware_legacy/power.h>

this in the "diff --git a/sta_dk_4_0_4_32/CUDK/tiwlan_loader/tiwlan_loader.c b/sta_dk_4_0_4_32/CUDK/tiwlan_loader/tiwlan_loader.c" section.

is the wlan_loader trying to use/find a file, to lock the phone from entering idle/suspend state when this file isn't used anymore ? is wlan_loader to old or too new to the zImage we're trying to use ?
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
So.much.information..

@Okibi,

I'm going to look over those files. I wasn't sure if you had been using the standard drivers from TI or not so thanks for clarifying that. It's too bad that 1.0 and 1.1 made it relatively easy to configure tiwlan0 and now cupcake is throwing us a curve. One thing that is helping is the multiple devs and versions coming out only increase our chances of patching together a better Android. I don't know if what you and dzo are getting at is that without the interface/kernel support it won't matter but isn't that what swifi (when it is working) is supposed to do? Seems like if we can just get back to the original status of assigning arbitrary IPs that we can either finish Android's side or maybe I can get a small chroot of Linux, with full tools available, to bind to the host's IP and feed it a connection.

@daedric,

I'll look at duplicate tools as there are some in both initrd.gz and system.img that do overlap. I don't know which takes precedence but I would assume system.img's. That might be why I was getting different types of errors.

Possibly, when switching to bash or using busybox it was changing the PATH but I haven't checked that-- just a guess. Maybe that is switching which is being used. A simple `which` command would have been fun to have added to toolbox but oh well. Somewhere between the different versions we should be able to establish harmony even if I put an absolute path to each one at different steps.

>>...where "WE" don't create files

I figured that was the case but it has to draw the files from somewhere. Maybe someone knows more about that than I do (like I even know a quarter of all that's being done here..) and can explain how to edit it.

I honestly don't know why the need for the wake_lock file is even relevant and that's probably why it's thrown in hardware_legacy. I guess we'll have to look through and either fix or prevent that call so that we can move to the next step.
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
The precedence comes from the path variable... wherever it finds the file first, it stops... so if theres a su in /bin and /system/bin, and $path=/bin;/system/bin, /bin/su will be executed.

About the wake_lock, sysfs and such...we CAN try to cheat and fool the wlan_loader.

Acording to http://lwn.net/Articles/318611/

and

My guessing is wlan_loader is trying to prevent the android from suspending... wild guess....

I've also stumbled upon something like... "how to write a sysfs file in 7 lines of code" or something.... :D

OR

citing http://android.git.kernel.org/?p=pl....c;h=d2af19b2673984d5628c4b89877c8104b5afc127 with its tiwlan_loader.c , wake_lock only shows up in:

#ifdef ANDROID
acquire_wake_lock(PARTIAL_WAKE_LOCK, PROGRAM_NAME);
#endif

if( init_driver(g_drv_name, eeprom_file_name, init_file_name, firmware_file_name) != 0 ) {
print_error("init_driver() failed\n");
#ifdef ANDROID
check_and_set_property("wlan.driver.status", "failed");
release_wake_lock(PROGRAM_NAME);
#endif
return -1;
}

So we could try and bypass and see what we get...
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
I did see that but was thrown off when I couldn't write to that file. Since kernel/module development experience for me is exactly "1" for high values of "0" I don't know yet how to go about fooling it but that's part of the magic I guess. I think I'll stick to my guide about writing sysfs files in 4 lines of code because I'm over level 9000 with this stuff.

What I was thinking though is that toolbox, bash and busybox might be setting or referencing different PATH orders but I don't know which is using what since toolbox has no which command. No biggie, some trial and error will let us switch off as needed to get the interface connected.

By the way, where were you when I needed to write my college essays? You're quick with the references like an old episode of Family Guy.
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
You can write to the file... you just can't create the file... i think ! :) at least no with touch blabla.

First i'll try and really sort out this multitude of the same file of diferent versions, then i'll try and make su + busybox + bash work and read /etc/profile or something else... Next i'll try and remove the blue background from the terminal, i can hardly see dir names...

Ok... was random browsing and came back to see updates... found none... but found something... perhaps dzo or anyone else might help.

What we are missing to make wlan_loader work... is most probably in the kernel.

Looking to dzo .config, i found some lines that jumped to the eye... example

# CONFIG_HTCKAISER is not set
CONFIG_VOGUE_TS=y

What does htckaiser do ? found no info about it on the net..

But what really caught me was :

#

CONFIG_PM=y

# CONFIG_PM_LEGACY is not set

Will enableing PM_LEGACY do any harm ?

Update... or not... this is what i did:

1.1... config gsync for contacts and such... go to 1.5 normal.

Terminal emulation

manual insert the wlan.ko

this complains to dmesg with "wlan: version magic '2.6.25-01843-gfea26b0 preempt mod_unload ARMv6 should be 2.65.25-00788-g195f096 preempt mod_unload ARMv6" but the module is still loaded...

Now back to the wlan_loader failure...

i saw in /proc/android the whole wakelock list... so the wake locks are there... its just the userland sysfile in /sys/power/wake_lock that isn't created...

Re-Update: Think i got it...

Nevermind the garbage, we probably have wake lock, wake lock stats, but we need userspace wake locks... probably... i'm no kernel/android hacker.

I've compiled linux kernels before... but only for x86 and to the machine being used... never crosscompiled....
[Tilt, TyTN II, MDA Vario III Android Development] ALIEN_:
Hi All,

Ok I've manged to upgrade to:

Radio 1.71.09.01

Protocol Version 25.75.40.02eMo

I've installed Okibi v1.1 and after it gets through the bootup process I get the following error:

GSM Phone Found

Failed

No partition found on SD card

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

I also get this error with trying v1.5

Anyone have any suggestions as to what the problem might be?

Cheers
[Tilt, TyTN II, MDA Vario III Android Development] archongtv:
I think you should try formating SD card with FAT32.
[Tilt, TyTN II, MDA Vario III Android Development] loserskater:
I'm having some strange issues and was wondering if anybody could help me out.

I've run okibi's 1.5 builds and i keep getting either loss of data connection or the phone wont power back on. I'm getting the blinking LED and I can tell the screen is turning on because the black hue gets a shade lighter when i hit the power button, but thats all i can do. ive tried seeing if texting/calling the phone will wake it up but it just sits there. Ive tried DZO's 1.1 build and the same thing happens.

The data connection issue hasnt happened too frequently but after some time the browser and any app that accesses the internet wont access it anymore. the modem says im still connected so i disconnect and try reconnecting but nothing.

I'm using the setup in my sig except ive upgraded to the 1.71 eMo radio. and Im using joshs mayhem 2 rom (which im pretty sure doesnt have any affect but just in case)

ive tried using the default/startup txt that came with each build except changing the apn values.

again. any help would be greatly appreciated.
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
So about that.. Not too sure what to do. I'm going to regit the Android sources. I know there's at least one flag that has to be enable for wifi to work, not even what you listed. I think some crafty sleuthing will be the only way. Too bad it requires recompiling a system.img not meant for our phones. I'm not too keen on making them efficient on our hardware like dzo, okibi, et all are.

I'd assume the "CONFIG_PM_LEGACY" part is the same as the power_legacy/power.c file you referenced before.

I'd also suppose that "CONFIG_VOGUE_TS=y" was put in there by dzo as our initrd.gz also references Vogue.

Should we come up with a formal plan to delegate this all? I don't see how relying on people 'just funning around' until it works is going to get us further. I think a good start would be working together to map out the code a little bit so we know specifically where things are. Then we can tweak parameters around and have the users test the results.

That's what I'm going to start doing because kernel land was always a treacherous journey but I can pretty much know what I'm looking at. I'll post back with a spreadsheet maybe others can help build up.

Thanks again devs and testers.
[Tilt, TyTN II, MDA Vario III Android Development] JeckyllHavok:
Yes man, you're totaly right, i think one of the probs is that many people here just want to see nother os running on there devices.

I think we shall make a method were only the "higher" dev posts are, and another one for the help of "noobs" (sorry i don't want to p**s of somone, but here are too many people that ask the same questions ever, and ever again).

Sure there are many issues with android for now, but hey..

we're just at the begining, i know i have nearly no coding skills but i think i can help you with testing, reporting and supporting others, If we all work together (efficently) it's possible to make this child fully working on our devices........
[Tilt, TyTN II, MDA Vario III Android Development] d.bobo:
my data connection still doesn't work :(! I tried to upgrade a several times but nothing will help.

Got the Okibi 1.1 android, set everything up.. data connection works in 1.1 with togga and synced with the google servers. Then I overwrite the system.img initrd.gz and a new zimage (that comes with 1.5 last version available).

And booting then in android 1.5, starting modem.. modem says connected (but the 3g icon is only active (bright white color) for 5 secs and then goes back in idle (gray color).

Somebody :) ?
[Tilt, TyTN II, MDA Vario III Android Development] JeckyllHavok:
Maybe it has something to do with the newest version, i got connection problems with this version, too which rom/radio are you running?
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
http://xdaforums.com/showpost.php?p=3965918&postcount=5788

From version 1.5 dont use togga anymore but modem, you will find it new in the menu

How are you starting the connection?
[Tilt, TyTN II, MDA Vario III Android Development] okibi:
I know I said I would probably be out for awhile, but I had time tonight. Anyway, there's a new build on my repo!

Changes in this build:

several permission changes in system

fixed build info in system

improved checking for data partition on sd card

improved initrd performance

As usual, get it from my repo:

http://ratedo.com/android/

Also, quick poll: How do you all feel about having a stock image vs putting out custom or themed images? I always add several apps, some themes, and change the home system. This can be done on the actual release if that's what you want.

@enatefox: What's with all the checking for /sys/power/wake_lock and unlock? I thought the kernel was changed awhile back to utilize /sys/android_power/release_wake_lock and the like?

Thanks!
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
I say keep it stock, and we can decide what we like on our own. Of course by stock I mean the default 1.5 or the htc version :D
[Tilt, TyTN II, MDA Vario III Android Development] okibi:
This is kinda the response I would expect. We are working on getting android fully functional, not customizing packages. I think it should be bare minimal, with the exceptions of what people need to test and use.
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
I dont know about minimal, but i say as close to stock as possible with some enhancements of course that dont detract from the experience. Themes would really take away from that for those of us that want to try just android for what it is. :P
[Tilt, TyTN II, MDA Vario III Android Development] andboy:
image development

I think a standard image is helpful. We all have basically the same system and we can help each other with problems. Ideally, it would be good if several people pitch in by making improvements which can be included in the standard image.

It seems like some of the priority projects are as follows. I'm sure there are more.

Userspace projects

Persistent Settings

Keyboard issues (">" on Tilt)

Kernel Tasks

wifi

USB (usbnet) on Kaiser

Keyboard issues (arrows bounce)

I've posted some brief tutorials on the xda wiki based on forums posts and other info. Not all of them are complete. Are there people who know how to solve any of these?

* Getting su and busybox to work

* ?Getting a mobile data connection to work

* Android data.gz image Customization

* Android system.img Customization

* Customizing initrd.gz

* Android Keyboard Customization

* ?Android Saving Settings

* ?Android Kaiser wifi

* ?Android Kaiser USB

Could you add or correct a tutorial or submit a patch so we can make Kaiser Android even better?
[Tilt, TyTN II, MDA Vario III Android Development] Pandemic187:
I'm using a system.img from the Vogue port so I can have a theme. But that's just me.
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
Okibi, most certainly Wake Locks are working, from my reading andoid depends on them. What we are probably missing, is the User space

config USER_WAKELOCK
bool "Userspace wake locks"
depends on WAKELOCK
default y
---help---
User-space wake lock api. Write "lockname" or "lockname timeout"
to /sys/power/wake_lock lock and if needed create a wake lock.
Write "lockname" to /sys/power/wake_unlock to unlock a user wake
lock.

Question: the zImage we're using... who compiled it ?
[Tilt, TyTN II, MDA Vario III Android Development] okibi:
dzo compiled the kernel.

Can you explain what /sys/android_power/* are for then?
[Tilt, TyTN II, MDA Vario III Android Development] enatefox:
Okibi, we can post custom images but it shouldn't replace the original images. The wake locks are there when wifi is being configured/initialized. Run swifi and you'll get a couple of different answers depending on if you use toolbox, bash or busybox. Since the wake_lock file isn't in /sys/android_power/* it's erroring out. It should be created or the routine bypassed. I think daedric's right so far but I just finished downloading the source so I can start looking at it.

I did have a thought, I'm going to try to compile a new kernel image within my Ubuntu chroot instead of my x86 laptop. Since I can mount all the points to Android I should have the drivers and hardware auto-detected. The only issue is that without wifi and no data plan, I have to manually resolve dependencies since I can't get QEMU networking to work for some reason. If someone is better at that then let me know.
[Tilt, TyTN II, MDA Vario III Android Development] okibi:
I know what the /sys/power/wake_* file are for and how they are being used in our current wifi setup, but that's not what I asked. What are the /sys/android_power/* files used for? I was under the impression that you could now pass a lock to /sys/android_power/acquire_full_wake_lock to obtain a full lock, much like you could pass a lock to /sys/power/wake_lock in 1.1. As for unlocking, you could also pass the lock to /sys/android_power/release_wake_lock much like /sys/power/wake_unlock in 1.1. Please correct me if I'm wrong and help explain what these are for. You can check these in the current 1.5 build.

Thanks!

NOTE: If you experience any data connection issues with my latest build, please try replacing initrd.gz with the file in the testing folder of my repo.
[Tilt, TyTN II, MDA Vario III Android Development] AngryUndead:
I wanted to thank everyone in this thread (and others) that have helped the Android experience along.

Android is the only thing that made my last few months with my HTC bearable.

I've crossed to the dark side: as of yesterday I'm the proud owner of an iPhone 3GS. Can't say that I like iPhoneOS over the Android OS but I certainly like the hardware and form-factor much better. The music management stuff is second to none. I listen to audiobooks and music almost constantly and I couldn't continue along with gimped solutions.

In any case I'm going to miss the notification bar from android and the seamless integration with google apps. I'm also going to miss having a chat client that stays connected until the 3.0 push notification features start to go live. I'm also going to miss having an open Java platform. Being a Java developer means I really don't want to have to learn another language and API to start making useful apps, but there it is.

In the end: I wish the Android on HTC community nothing but the best.

So long, and thanks for all the fish.
[Tilt, TyTN II, MDA Vario III Android Development] okibi:
Yeah, the iPhone is an excellent phone hardware-wise. You pretty much nailed why I don't use it, though. Android is far superior in my opinion in that regards. If only we could get android running on the iPhone...

Love the Douglas Adams reference!
[Tilt, TyTN II, MDA Vario III Android Development] bravekid20:
Camera and Bluetooth?

Hi Everyone,

I noticed that wifi is so far the only thing that is being talked about. What about camera and bluetooth?? Those are also major things. So lets also try to start with that also.

Thank You
[Tilt, TyTN II, MDA Vario III Android Development] ajclai08:
Yeah I'm waiting for a Tegra based device with Windows Mobile..not just android. The advantages those devices have over a iphone will be enough for ppl like us..
[Tilt, TyTN II, MDA Vario III Android Development] AngryUndead:
I'm with you there. It really comes down to the music thing. Every person has a different software need. Now... running android on the iPhone would rock. Best of both worlds, though, I'd still miss the iPod "application".
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
Okibi, point is.... /sys/android...* are there and probably working, but wlan_loader immediately fails without /sys/power/* files being present.

IMO, they have the same purpose, but are placed in different places... might be wrong though...

@dzo : you made camera work in the Vogue, and assuming that the Vogue suffered from the same camera performance as the kaiser, how good did it get ?

@all: Completly unrelated but a little on topic, what do people have to say of this : http://www.h-online.com/open/Source-code-for-Palm-WebOS-released--/news/113572
[Tilt, TyTN II, MDA Vario III Android Development] okibi:
I know they are there and are working. I guess some people just don't follow clues... Just hack away however you want. :)

I find it quite interesting and appreciate the link. I'll read more into it later.

Thanks!