Mer has you copy over the drivers from maemos /lib/firmware to Mer's. Maybe we need to do same in android so the kernel side of things will work.
MER is much more similar to Maemo than Android is to Maemo, dj_steve can answer this much better than me, but I think that wont be possible... Heck it might have been something he has already done.
Lets just hope that he can apply his findings on Android 2.1 to Android 2.2 without any unforeseen problems and really really fast when the source gets released
Something has been bothering me:
Someone (I can't remember who) linked to this device earlier.
It has wifi, but no GSM. How does it get to Google Apps?
This bothers me. It seems to be something Google did, and there must be a way around it.
Something has been bothering me:
Someone (I can't remember who) linked to this device earlier.
It has wifi, but no GSM. How does it get to Google Apps?
This bothers me. It seems to be something Google did, and there must be a way around it.
I think it requires specialized apps from slatedroids site, not sure
wifi is more permissions issue than drivers, the driversand firmware loads up fine, just permissions on folders is dodgy and i cant work out why at min.
wifi is more permissions issue than drivers, the driversand firmware loads up fine, just permissions on folders is dodgy and i cant work out why at min.
Stupid question, cant you just chmod every file that has to do with wifi to 755?
yea but since 1 is not created until wpa_supplicant starts and android promptly shuts down wpa_supplicant after scan fails its a bit hard
You have the source of the binary that is creating the file? I know this would be a dirty hack, but cant you just make the same binary chmod the file after it spawns it? Than you would not even have to change the algorithm of how the file is made.
Oh, you would also have to figure out (if you dont know) what binary is creating it, but you might be able to do that with ssh and top if your lucky.
