1.1 sdk found! - G1 Android Development

Because my G1 is running with the 1.1 version of android, I really needed the 1.1 SDK... but... google only offers the 1.0 SDK on the download page :-(
But I found out, that by modifying the download URL, you can get the 1.1 SDK
http://dl.google.com/android/android-sdk-windows-1.0_r2.zip
becomes
http://dl.google.com/android/android-sdk-windows-1.1_r1.zip
Never thought it would be that easy...
Enyoy!

Huh. The linux version is there as well. Also 1.1-r1.

is there an offical place to download the ADP1 rom?

And still no changes in the implementation of WPA 2 Enterprise ,
they have changend nothing in the class which is actually responsible for the WIFI Connections. Sad

Gedomania said:
And still no changes in the implementation of WPA 2 Enterprise ,
they have changend nothing in the class which is actually responsible for the WIFI Connections. Sad
Click to expand...
Click to collapse
Yeah, noticed it too... Maybe in 1.2 (And noooooo that link doesn't exist, yet )

Anyone know what the differences are?

Wijnbo said:
Because my G1 is running with the 1.1 version of android, I really needed the 1.1 SDK... but... google only offers the 1.0 SDK on the download page :-(
But I found out, that by modifying the download URL, you can get the 1.1 SDK
http://dl.google.com/android/android-sdk-windows-1.0_r2.zip
becomes
http://dl.google.com/android/android-sdk-windows-1.1_r1.zip
Never thought it would be that easy...
Enyoy!
Click to expand...
Click to collapse
nice find
personally, not useful to me at all because i don't know anything about programming and such, but i'm sure it will come in handy to someone

SDK 1.1r1 Now Available!!!
get it while it's hot!
http://developer.android.com/sdk/1.1_r1/index.html

and it has 64bit drivers

I just got the new SDK & in the usb drivers folder, there's 2 folders now. Do I have to update the drivers again? If so, which driver should I use? I'm running XP on my laptop

Gedomania said:
And still no changes in the implementation of WPA 2 Enterprise ,
Click to expand...
Click to collapse
This is just missing UI. It's wpa_supplicant underneath, so get root and edit /data/misc/wifi/wpa_supplicant.conf as you like. I just appended this:
Code:
network={
ssid="MyEmployer"
key_mgmt=WPA-EAP
identity="myusername"
password="mypassword"
}
It worked like a charm; the network even appears in the list in the UI. Of course, there are many varieties of WPA2 Enterprise, which is probably why they haven't done the UI yet, so check the wpa_supplicant docs online if the above doesn't cut it or if your network needs e.g. a certificate / tunnel modes.

Related

Linux applications ported to Android

Hi all of you, XDA fans!
After googling and looking in XDA forums, I was not able to find any ways to port linux apps to Android and was wondering if it was even possible.
Knowing that Android runs on 2.6.25 kernel, I thought that maybe it was possible.
I recently purchased a G1, successfully rooted it, and now am looking for ways to port linux apps to Android.
Is there a way to build apps from source code on Android, using the build tools provided with desktop distros? (I am using Ubuntu atm).
Anybody want to share some lights on this?
I'll keep you posted if I find anything intresting...
XDA ROCKS!!!
I'm looking into this myself, especially with respect to vlc, mplayer, and some console emulators...all of which have been compiled for ARM before, most successfully on the GP2X handheld.
Cross-compiling apps on an Ubuntu system is possible, but I'm not sure how well compiled apps will work with the Android framebuffer. There's also no x-windows system, so you know graphical apps that need it won't cut it at all.
Let us know what you find out.
Found this: Debian on Android
Hey i found this, Thought it might be intresting to look into this.
Debian & Android Together on G1
It's a guide to have Debian running alongside android, at least for what I understand...
I haven't tried yet since I have rooted rc8 and it's written for rc29/Mrc30, but that seems like a good solution.
Would be nice to be able to compile on android rather than on eclipse on ubuntu...
I've got no programming knowledge, that's why I'm looking for a solution allowing to compile directly on android...
"There's also no x-windows system, so you know graphical apps that need it won't cut it at all."
I was thinking as an experience to compile aircrack-ng, and it has no gui... The hardware might not support it but tha g1 might be able to handle it.
Yeah I wanted to compile the No-IP app for the phone so I could know what the IP address of my phone was on Tmo's network. That way I could run a webserver on my phone (apache anyone?). Does Tmo have firewalls in place to prevent this type of thing?
efbenson said:
Yeah I wanted to compile the No-IP app for the phone so I could know what the IP address of my phone was on Tmo's network. That way I could run a webserver on my phone (apache anyone?). Does Tmo have firewalls in place to prevent this type of thing?
Click to expand...
Click to collapse
enable telnetd from terminal and see if you can telnet from your computer to it via 3G (i.e. your wireless computer ---> G1)
My G1's edge ip is 25.97.51.2XX tried to telnet in, host unreachable. Did a traceroute from both my web server and home computer, both showed that the 3rd hop and all hops after that did not respond, and as expected ICMP echo (ping) sent to the phone timed out. Therefor we can i think say that T-mobile was not dumb and put a firewall up as any network administrator would. Gonna double check the IP of my G1 and i'll get back if it figure out my ip is different or something.
EDIT: pinged my router this time, got the IP 208.54.4.61, still same story times out and my G1 died so im going to reboot it and plug it in to try again.
well i'm sure t-mobile was wiser on that end, but did you try telnetting on port 80? also if you were to get a webserver running on your g1, you could always just use a non-standard port (81?) and just use a service like dyndns to control the port redirect, since i'm assuming they're already managing the dyndns updates.
rak500 said:
Hey i found this, Thought it might be intresting to look into this.
Debian & Android Together on G1
It's a guide to have Debian running alongside android, at least for what I understand...
I haven't tried yet since I have rooted rc8 and it's written for rc29/Mrc30, but that seems like a good solution.
Click to expand...
Click to collapse
I actually just got Deb working alongside Android (not terribly difficult but I did have some wonky-ness getting ext2.ko insmodded).
Having RC30 on my phone makes me really miss ADP1
deprecate said:
I actually just got Deb working alongside Android (not terribly difficult but I did have some wonky-ness getting ext2.ko insmodded).
Having RC30 on my phone makes me really miss ADP1
Click to expand...
Click to collapse
If you have JF 1.3+ you don't need to insmod ext2.ko. Just type "busybox insmod ext2".
deprecate said:
I actually just got Deb working alongside Android (not terribly difficult but I did have some wonky-ness getting ext2.ko insmodded).
Having RC30 on my phone makes me really miss ADP1
Click to expand...
Click to collapse
Do you think I can have it working on my rooted UK RC8?
I want to try it but it seems the configuration are slightly different for RC19 and RC29 according to the tutorial, so I thought it might be different on RC8 too.
I tried the web server in the market, didn't seem to work on edge
I'm not quite sure but I believe that T-mobile's VPN add-on might provide an externally accessible IP.
does anyone know if you can compile samba for the g1 ?
I've never dealt with linux on anything besides x86 and x64, so forgive me if this is stupid, but what about running gentoo on the G1 here? Seems to me that portage for ARM might be a little bit better for the G1 than the Debian repositories.
Although, NONE of us will be excited about having our G1 churning away for hours/days just to get Xorg compiled, as well as the headaches associated with installing and configuring gentoo.
I'm sure someone's thought of this, and Debian is pretty great anyway, just thought I'd put this out there.
kash04 said:
does anyone know if you can compile samba for the g1 ?
Click to expand...
Click to collapse
I am using Samba by way of Debian. So, yeah, it's possible.
DDM123 said:
I've never dealt with linux on anything besides x86 and x64, so forgive me if this is stupid, but what about running gentoo on the G1 here? Seems to me that portage for ARM might be a little bit better for the G1 than the Debian repositories.
Although, NONE of us will be excited about having our G1 churning away for hours/days just to get Xorg compiled, as well as the headaches associated with installing and configuring gentoo.
I'm sure someone's thought of this, and Debian is pretty great anyway, just thought I'd put this out there.
Click to expand...
Click to collapse
It's not stupid. If it works for you and is to your liking, go for it. It is debatable, however, whether portage (as good as it is) is any better for the G1 than Debian's packaging system. Packages compiled for the ARM architecture are already optimized for ARM processors. There wouldn't be as much self-compiling gain in this architecture as there would be optimizing between i386, i686, amd-64, etc. You'd be doing a lot of work and wasting a lot of time having portage compile your apps...and you'd have very little pluses to show for it.
Oh ok, I just thought that many apps were being compiled manually and portage might make some of that easier. I figured there wouldn't be any speed gains over Debian or other binary-based distros, and the barebones installation of gentoo is absolute hell, but I hoped it might get us into full-blown X quicker somehow.
It could definitely work with Portage. Keep in mind, though, that apt-get under Debian *can* download and build the source into a package automatically as well.
Web Server on TMO
Hey guys,
I'm new on XDA, getting my galaxy S tomorrow, I was a nokia fan up untill maemo 5 and the N900...
Anyway, one thing to remember is - Cellular Operators usually manage their own IP address pools, they don't give "Real" IP addresses to cellular phone, but rather use NAT services and all sort of nasty hacks to the IP system.
Therefore, in order for port 80 (http web server) to work on your server, it's not enough to just run it and get the IP, you also need the provider/operator to forward TCP packets coming to your External IP on port 80 to be forwarded to your internal IP > to your phone.
This, will never happen. If it will, you will get charged heavily for this as it will increase traffic and allow upstream traffic to your phone, and also risk your phone to potential hackers.
Edit : And I just noticed I resurrected an almost 2 years old thread Oopsy.
efbenson said:
Yeah I wanted to compile the No-IP app for the phone so I could know what the IP address of my phone was on Tmo's network. That way I could run a webserver on my phone (apache anyone?). Does Tmo have firewalls in place to prevent this type of thing?
Click to expand...
Click to collapse
get dyndns account there is an app on the market that will sync it.

Yes! Wifi App for connecting in university Wifi

Hey guys,
I just got my Xperia X10 to work in our university wifi. WPA-EAP PEAP with MSCHAPV2. I used the app Wifi-Config Editor Pro from the market. You don't even need to root your phone. I hope this works on everyone else also. I was so thankful with the developer. This app saved my phone.
is this wifi-config?
Cant find the exact name you mention anywhere.
links please?
I did a search in the android market "wifi config". After that first two results would be wifi config and wifi config editor pro. The free version doesn't have the enterprise configuration. The pro does.
I would love to try this out, but the app is obviously not yet certified for the latest firmware release...
Even with this link (hxxp://bubiloop.com/android-tools-wifi-config-editor-pro), there are no results in the market.
If, like me (X10 mini pro, UK unlocked latest firmware) wifi config pro isn't showing for you in the market you can do the following:
1) Root the phone following the instructions here:
http://android.doshaska.net/x10miniroot
(this works for me on my X10 mini pro)
With the phone connected and usb debugging on/wifi toggled off, from the androidSDK on a PC (Windows,Linux,Mac) get a shell
2) adb shell
3) su
4) cd /data/misc/wifi
5) busybox vi wpa_supplicant.conf
(to edit the wpa configuration file)
6) add this at the end
network={
ssid="eduroam"
key_mgmt=WPA-EAP IEEE8021X
eap=PEAP
identity="MYIDENTITY"
password="SECRET"
phase1="peapver=0"
phase2="auth=MSCHAPV2"
priority=7
}
or similar, where MYIDENTITY is your eduroam login ID and SECRET is your password. This is taken verbatim from another phone (HTC Desire, Android 2.2) which does work OK
7) save
8) log out
Then connect and surf...
Cosmodia - I don't know why you can't see it in the market. You have Android 1.6 right? At first I cannot see it also since the app was only for Android 2.0 but the developer made it to work with Android 1.6 so now I can see it and got it to work. You can contact the developer and ask questions.
Professordes - I think this should help people who didn't want or don't know how to root their phone
Android 2.x Enterprise settings coming soon
Android WiFi Internal API's changed between version 1.5/1.6/2.x Android 1.6 added a lot of the requirements to enable an enterprise WiFi network, however the published API and UI's don't make it easy to connect to them. They then changed them in 2.0 making virtually all Enterprise configurations valid. Unfortunately the UI still lacks in the ability to configure them. I needed my android device on the WiFi network at work so I wrote an app do to just that.
As of about a week ago I had everything all versions without the enterprise settings working. This is the "WiFi Config Editor" you can find on the market now. I was in the process of enabling the editing of the enterprise settings for Android 2.0+ when I was contacted about getting an X10 on a WPA-EAP network with PEAP authorization. Being the X10 is a 1.6 device I made the changes necessary and released the 1.6 version of "WiFi Config Editor Pro". This version will only work with Android 1.6 as the Enterprise API's are different.
Currently I'm testing the "WiFi Config Editor Pro" for Android 2.0+ and should have it released in the next few days. As I hinted at earlier, the enterprise settings are hidden in Internal API's. This makes developing against them difficult. Google actually places a number of roadblocks in the way to make this harder. But being that Android is open source, it just takes a little bit of persistence to make it all work. Best part of all. NO ROOT REQUIRED!
To my knowledge this is the only app that exists that will allow you to edit WiFi settings at this level without requiring root access. I'm open to suggestions to help make it better. Let me know if anyone has any issues with the app or connecting to specific configurations.
Thanks,
--OddRain
Hello OddRain,
this sounds very promising and I am looking forward to trying it out as soon as the latest firmware release for the X10 gets full Market access again.
Hi Oddrain,
I can't find any other way to contact you.
I am desperately looking to connect to my companies WPA2 enterprise network, with Peap. It also uses a certificate.
I cannot however purchase pro as I am in South Africa and we can only get free apps on the market.
Can you please advise when the android 2.1+ version is available, if it will work for what i need and how I can pay.
Florbid
I still can't seem to find the Wifi Config Editor (neither the free nor the pro version) in the Market, everything else appears to be there.
Is the application limited to some region, firmware or branding?
I'm trying to access the Market from Germany, my X10 is on R2BA026, unbranded phone.
I'm not sure why the app doesnt show up in the market sometimes. The free version supports Android 1.5 and up. There are 2 pro versions, one for Android 1.6 and one for Android 2.0+. All versions should be in the market right now. There are no limits within the application other than the Android Versions supported.
The most reliable way I know of searching the app store is not by the application name, but by the developer name. pub:OddRain would be the Android Market search string, it is Case Sensitive.
--OddRain
Thank you very much for the reply. Unfortunately, I don't get any result with that search term as well.
Could somebody else with the same firmware version please search for this to see if it maybe depends on that?
can wifi config editor (free version) solve the issue of the campus wifi (WPA/WPA2-EAP PEAP with MSCHAPV2) ?
Thanks!
can you just extract the .apk and post it here please and make it easier for all?

Connect to adhoc Wifi network

Hi,
I need the captivate to be able to connect to a adhoc wifi network created using my laptop. However, android doesn't seem to be supporting it, just access point networks. Has anyone tried this, any success?
Searching revealed one thread where a guy modified some code on an htc phone, and got it to work, but seemed a little dated. Not sure if that would work with the android 2.1 and the Samsung phone.
Help appreciated.
The Captivate can connect to ad-hoc networks, but not through the native GUI interface. I tested mine via adb shell issuing some iwconfig commands via script to connect to a MyWi router on a friend's iPad. It's buggy, to say the least..
agentdr8 said:
The Captivate can connect to ad-hoc networks, but not through the native GUI interface. I tested mine via adb shell issuing some iwconfig commands via script to connect to a MyWi router on a friend's iPad. It's buggy, to say the least..
Click to expand...
Click to collapse
agentdr8,
Thanks for the reply.
Care to share details on the commands you ran? Or are you saying it's not worth it because it's so buggy?
thanks
To avoid a hard lockup, start with the wifi turned off. I tested it numerous times with it already on, and it resulted in a battery pull.
You'll need busybox 1.7x (maybe 1.8x will work too?). You'll also need a working iwconfig binary (I symlinked mine from the WifiTether app dir: /data/ext2data/data/android.tether/bin to /system/xbin)
With an adb shell, try something like this:
$ su
# /system/xbin/ifconfig eth0 up
# /system/xbin/iwconfig eth0 mode ad-hoc
# /system/xbin/iwconfig eth0 essid YourEssidHere
# /system/xbin/iwconfig eth0 key WEPkeyhere
Now with wifi turned off, these commands will all error since the interface is down/off (eth0 is the wifi, at least on my Cap). Turn your wifi on and rerun the same commands, followed by:
# netcfg eth0 dhcp
This may or may not error out, but ultimately, you should see a dhcp address for eth0 as handed out by your dhcp server/mywi device.
You may need to also manually add the ad-hoc network in the GUI with its key. I can't remember if I needed that or not, but with it I can see the connection status and when it's grabbing the IP. Even shows connected and signal strength once it does connect (assuming it doesn't lockup).
agent can you help me pls. Im a newbie still.
Do i run all those commands in windows when my phone is connected or do i run it through something like terminal emulator an app on the phone??
You can either use adb shell on your Windows machine (part of the Android SDK), or you can use a terminal on the device itself (ConnectBot is my preferred). Your phone needs to be rooted if it isn't already.
Okay, I'll try out the connectbot. Can you tell me how to do this part then if it's needed??
"You'll also need a working iwconfig binary (I symlinked mine from the WifiTether app dir: /data/ext2data/data/android.tether/bin to /system/xbin)"
how do you do this symlinked part?? I don't really understand it.
I tried ur commands without doing the symlinked part....everything just returned a "not found" message.
Maybe you could give me a dumbed down step by step way of doing this hahahaha??? Im rooted and i have busybox 1.7x, just missing the working iwconfig because im not really sure what it is.
If you're not too familiar with linux commands, it would be best to wait for someone to build a widget/GUI app around this, as poking around in a root shell on your phone is never a good idea if you're not aware of the potential consequences of blindly running commands.
It's possible that with the Froyo update adhoc connections may just work as intended, not that I've read anything that suggests that.
The portal had a write up on how to connect an android device to an adhoc network a couple days ago.
Sent from my AOSP on XDANDROID MSM using XDA App
boborone said:
The portal had a write up on how to connect an android device to an adhoc network a couple days ago.
Sent from my AOSP on XDANDROID MSM using XDA App
Click to expand...
Click to collapse
Okay, i'll go look for it though a link would help.
Maybe i'll just wait until something like Cyanogens ROM comes, i hear it usually comes with ad-hoc connectivity.
Try this: http://www.xda-developers.com/android/android-ad-hoc-wireless-network-support/
Sent from my HTC Dream using XDA App
only problem is it's compiled for froyo and i think geared towards the Desire according to the replies.
I feel like it might mess up my captivate
Well if you're computer is windows7 you can use a program called conectify.
It makes win7's adhoc networks work as real hotspots
Sent from my HTC Dream using XDA App
Wanted to enable ad-hoc so I could tether the captivate to my iPhone
Yes I woild also know on a workaround , would love to tether my unlimited data from my iphone to my captivate
pewpewbangbang said:
Wanted to enable ad-hoc so I could tether the captivate to my iPhone
Click to expand...
Click to collapse
Why would you do that? Do you prefer safari over android browser or something?
Sent from my Nexus One using XDA App
cowballz69 said:
Yes I woild also know on a workaround , would love to tether my unlimited data from my iphone to my captivate
Click to expand...
Click to collapse
Then You need to jailbreak your iphone and get a tethering app
boborone said:
Then You need to jailbreak your iphone and get a tethering app
Click to expand...
Click to collapse
Issue isn't on iPhone-end, nor wpa-supplicant end (as the wpa-supplicant binary included in the android wireless tether app has this ability).
The problem is the GUI end of things (i.e., settings.apk) ALSO filters the results.
So it goes beyond simpy modifying the wpa-applicant (yes; this is sufficient for the basic-functionality), but is very crude & diffcult to do on the go from the tiny terminal emulator, etc.
What I've personally been looking for, is an update that modifies the neceasary files, and enables this extewmely useful function.
Something similar to the update package posted for the froyo-build, but instead for the ECLAIR-2.1 build of the captivate.
If anyone knows of anything availible like I'm describing (a GUI-centered mod that will remove ALL the STUPID damn (pardon language lol) IBSS filtration form the settings.apk, wpa-supplicant, wireless configuration files, etc for the ECLAIR-2.1 build of the Captivate so that it JUST WORKS lol -- this way we can SEE and CONNECT via our native GUI .
I've gotten this to work through running command line / configuration file hacks, but it's very messy/annoying AND to make things MORE annoying, once you've put it into Ad-hoc mode and have it all setup very nicely, guess what? The settings.apk application (which is needed to load the device into kernel), will actually COMPLETELY UNDO all the tedious command line efforts you've just made, and takes the wifi chip out of Ad-hoc mode every x amount of minutes! ARGH!! LOL!
Anyway, I've gone through the source code and patch diff's myself and it really doesn't seem very involved. I actually was planning on compiling the necessary modded binary (making a nice update.zip for all the frustrated captivate owners like myself lol), but I simply haven't had the time to setup the build environment for it at the moment (have several other build environments I'm juggling as it is with work).
Anyway, I apologize for the rant lol -- I just wanted to clarify exactly what is needed and point out it really wouldn't be much work (and would be VERY much appreciated!!!!) if someone with the skill, time, and a build environment for the galaxy s (captivate, speifically lol , could post an eclair mod for us -- you would receive AN ENORMOUS amount of praise & thanks lol .
OR -- if someone who has a little time, could simply modify the android wireless-tether-app to have one extra feature, 'connect to ad-hoc network' lol . This would also be ideal, as it already fully supports the initialization & loading of the captivate wireless driver properly, and can fully manage the interface & connections while running in the background (independent of settings.apk). PLUS -- it even already has full ad-hoc support built into it's own pre-packaged wpa-supplicant. Basically, all the hard work has already been done with the wireless-tether-app, just need a few extra functions to handle scanning for networks and connecting to them (relatively simple, considering they've already done ALL the hard work..lol)..
Okay, my rant is officially done! Lol! I just hope this helps those who have the capability to help, give a clear picture of all that's required. It's late, so some of this stuff may have already been mentioned and I missed it! Shoot, maybe someone just finished doing exactly what I just went on & on about? Lol.
In any case, if anyone is willing to help out -- or already knows of a solution already out there I've missed -- PLEASE let me' know! This functionality would truly help a great deal in my day to day work with my captivate! Thanks in advance!!!
holy need a bump batman!
i would really like this too!
I found this post last night, but I couldn't get it to work: http://forum.xda-developers.com/showpost.php?p=16632147&postcount=7758

WindowsAndroid

The folks over at Socketeq have released WindowsAndroid. It runs natively on your Windows machine, meaning that there is no need for emulation. WindowsAndroid runs on the Windows kernel, instead of the Linux kernel. Currently they are on Android v4.0.3. It's compatible with Vista, Win7, and Win8. Keyboard and Mouse are fully supported. This is the early release, so there might be some bugs.
Normally download is hosted on Socketeq's website, but right now the site is down due to heavy loads. Here is and alternate link if your interested:
http://www.androidfilehost.com/?fid=9390288116658471029
v/r
Kritec
Kritec said:
The folks over at Socketeq have released WindowsAndroid. It runs natively on your Windows machine, meaning that there is no need for emulation. WindowsAndroid runs on the Windows kernel, instead of the Linux kernel. Currently they are on Android v4.0.3. It's compatible with Vista, Win7, and Win8. Keyboard and Mouse are fully supported. This is the early release, so there might be some bugs.
Normally download is hosted on Socketeq's website, but right now the site is down due to heavy loads. Here is and alternate link if your interested:
http://www.androidfilehost.com/?fid=9390288116658471029
v/r
Kritec
Click to expand...
Click to collapse
I actually read about this today lol
seems pretty cool.
If you want to tinker with it further edit the system/build.prop file in the windowsandroid_root folder and add this line:
ro.sf.lcd_density=120
It will switch the interface to tablet.
Sent from my SGH-T999 using xda
premium
Woah, this is cool
tried it out right away. pretty sweet. will do the screen density thing too. thanks for this link.
Anyone get anything to install from the play store? I only get error 491.
Also Settings fc for me when I tap the Security tab.
Mirror if needed:
WindowsAndroid_earlyrelease.exe (64.9 MB)
https://mega.co.nz/#!PFckRBJK!DP3bLVzL0FhI7378KmWB5l664xlBwmZTLa5a12dmQ_I
md5 - d3ea9d70b2a374d4b5d3f0123ac9f87b
get error opengl 1 lower
I get the error opengl is old 1 must better 2 version. . .
How can update or plz give dwnld link for it.

Wine 3.0 on Android

It is here,
https://dl.winehq.org/wine-builds/android/
But ain't working on pixel. I am pissed off. Any workarounds?
It is not compatible with Oreo yet.
Just let them know on their forums:
https://forum.winehq.org/viewforum.php?f=2
NoobInToto said:
It is here,
https://dl.winehq.org/wine-builds/android/
But ain't working on pixel. I am pissed off. Any workarounds?
Click to expand...
Click to collapse
Look into Crossover. It uses WINE. http://www.androidpolice.com/2017/11/07/crossover-android-chrome-os-enters-open-beta/
skawtnyc said:
Look into Crossover. It uses WINE. http://www.androidpolice.com/2017/11/07/crossover-android-chrome-os-enters-open-beta/
Click to expand...
Click to collapse
Unfortunately, it is not for ARM devices...
I hope they'll update it so it's compatible with Android Oreo devices.
Looks like the new WIne 3.0 is ARM-compatible, and has been compiled for ARM devices:
https://dl.winehq.org/wine-builds/android/
I have Oreo on my Nexus 7 2013, wine works, tried to install some apps but no luck, only errors. Internet Explorer works, but i see only blank white web pages
numbazZ said:
I have Oreo on my Nexus 7 2013, wine works, tried to install some apps but no luck, only errors. Internet Explorer works, but i see only blank white web pages
Click to expand...
Click to collapse
what kind if binaries / apps were u trying to run?
nine7nine said:
what kind if binaries / apps were u trying to run?
Click to expand...
Click to collapse
Tried Live For Speed installer, also exe from unpacked game, and some photoshop cs6 repack) as i know LFS works good on wine.
Will try something else tomorrow
numbazZ said:
Tried Live For Speed installer, also exe from unpacked game, and some photoshop cs6 repack) will try something else tomorrow
Click to expand...
Click to collapse
how about trying actual arm binaries?
ie; windows rt, win8 arm && win10 arm PEs
last I heard, while the wine devs are working on x86 on arm, it wasn't ready - when compared to say; win10 for arm's x86 emulation layer...
I also know that in the past to run x86 binaries in wine on arm, you have to have binfmt_misc enabled in the kernel + qemu (emulator) to make it all work...
not sure, where things are at, at the moment. but I'd try running actual Arm compiled windows app and see if they run.... idk, I can't imagine that Wine is super useful on android yet. that said, I am curious - as I used to maintain buillds and patchsets for wine...
Only binaries compiled for ARM will function under Wine. You can find an updated list in the second post of this thread: https://forum.xda-developers.com/showthread.php?t=2092348
skawtnyc said:
Only binaries compiled for ARM will function under Wine. You can find an updated list in the second post of this thread: https://forum.xda-developers.com/showthread.php?t=2092348
Click to expand...
Click to collapse
it should be noted, this is specifically windows rt / win8 arm apps... and hasn't been updated in 3yrs.
I suspect that if u were to investigate the windows app store / UWP apps - there are probably a much higher number of windows apps that potentially could run in wine / for arm - but then you would likely require the Microsoft store or some other way to get the apps running in wine (not sure if wine even supports them).
skawtnyc said:
Looks like the new WIne 3.0 is ARM-compatible, and has been compiled for ARM devices:
https://dl.winehq.org/wine-builds/android/
Click to expand...
Click to collapse
It is not pixel compatible, and that is all this thread is about.
NoobInToto said:
It is not pixel compatible, and that is all this thread is about.
Click to expand...
Click to collapse
To be honest I only installed it on my Pixel C, not my Pixel phone. Doing so would have been pointless since the resolution makes it very difficult to use. Also there's no way to access the software keyboard, making it even more difficult to use.
Even if you could install it, and those other issues were resolved, it doesn't have a x86 emulation layer so you're pretty much stuck with those old Windows RT apps and not much else. You're looking at something that really doesnt have much more value than proof of concept. I'm probably going to end up migrating my tablet to something like the Pixelbook so I can run Crossover on it and have both android and x86 Windows apps run natively.
skawtnyc said:
To be honest I only installed it on my Pixel C, not my Pixel phone. Doing so would have been pointless since the resolution makes it very difficult to use. Also there's no way to access the software keyboard, making it even more difficult to use.
Even if you could install it, and those other issues were resolved, it doesn't have a x86 emulation layer so you're pretty much stuck with those old Windows RT apps and not much else. You're looking at something that really doesnt have much more value than proof of concept. I'm probably going to end up migrating my tablet to something like the Pixelbook so I can run Crossover on it and have both android and x86 Windows apps run natively.
Click to expand...
Click to collapse
Well, I would still like to try it out. If they manage to make it work with windows 10, say, windows 10S , it would be cool, since windows 10 is more touch friendly than 7 . It is in the works I believe, to be made possible via qemu (full arm compatibility). Time will tell.
NoobInToto said:
It is not pixel compatible, and that is all this thread is about.
Click to expand...
Click to collapse
NoobInToto said:
Well, I would still like to try it out. If they manage to make it work with windows 10, say, windows 10S , it would be cool, since windows 10 is more touch friendly than 7 . It is in the works I believe, to be made possible via qemu (full arm compatibility). Time will tell.
Click to expand...
Click to collapse
My biggest regret about this is that I don't have an emulator to run Diablo II on my tablet. Sure, there are other games, but they don't really capture the experience the same way.
skawtnyc said:
My biggest regret about this is that I don't have an emulator to run Diablo II on my tablet. Sure, there are other games, but they don't really capture the experience the same way.
Click to expand...
Click to collapse
I managed to make doom 3 to work on my phone ( I don't recollect which one, pixel or nexus 6p, I switched to pixel about 2 months ago). I am not sure about diablo.
NoobInToto said:
It is not pixel compatible, and that is all this thread is about.
Click to expand...
Click to collapse
beyond installing, it doesn't seem to work for me... also, i'm unclear on whether this build is arm64 compatible.? (I know wine has an arm64 preloader though).
skawtnyc said:
Even if you could install it, and those other issues were resolved, it doesn't have a x86 emulation layer so you're pretty much stuck with those old Windows RT apps and not much else. You're looking at something that really doesnt have much more value than proof of concept. I'm probably going to end up migrating my tablet to something like the Pixelbook so I can run Crossover on it and have both android and x86 Windows apps run natively.
Click to expand...
Click to collapse
I suspect that running qemu + wine-x86 would be the better route to go (vs wine-arm or running qemu + windows)... i'm not too sure what the overhead would look like, but people are doing it on the rasberry pi 2/3...
it's probably also possible that using some of wine's env variables would improve performance (realtime priviledges for wineserver, critical threads, etc) and patching wine to support other enhancements (which is what I would do anyway, on my linux box).
NoobInToto said:
Well, I would still like to try it out. If they manage to make it work with windows 10, say, windows 10S , it would be cool, since windows 10 is more touch friendly than 7 . It is in the works I believe, to be made possible via qemu (full arm compatibility). Time will tell.
Click to expand...
Click to collapse
i'd like to, as well...
technically, you can run qemu + x86 wine on arm, right now. I just don't believe that anyone has packaged it up nicely for android...
and it would require additional manual configuration, init script, possibly a script/wrapper for launching apps too, depending... Another issue would be the vast majority of stock kernels don't have the support or enable stuff that is going to be required... mine suports binfmt_misc (which qemu will require), but i think other stuff may be needed. not positive.
it can't be that hard though, but I don't have much experience with qemu (and none on android), wine on the other hand - lots of experience with on linux. same goes for winelib...
does anyone know how to get access to the internal storage?
I cant even try to install anything, because I dont know where the Wine-Files are located.
Btw I'm using a Lenovo YogaBook
Thanks
trfr3ak said:
does anyone know how to get access to the internal storage?
I cant even try to install anything, because I dont know where the Wine-Files are located.
Btw I'm using a Lenovo YogaBook
Thanks
Click to expand...
Click to collapse
you'll have to figure out how to get into your internal storage yourself, but having a a proper file manager helps. you may need root to view the files (I did on my pixel)... also, not sure why you are asking for help for your yogabook in the google pixel forum...? (you probably shouldn't be).
as for where the files are. it's android, so app data is usually stored in /data/data/your.app.name... and this would be where wine installs it's binaries and prefix too. (org.winehq.wine)
---------- Post added at 10:22 PM ---------- Previous post was at 10:18 PM ----------
so yeah. looking at the binaries. they are compiled as arm-v7a. ... they should run (although, by default after install, they aren't in the PATH / can't be executed from a terminal)....
I guess maybe the arm64 version just isn't ready at this point && wine-3.0 for arm requires some manual setup on the pixel... might tinker with it later, or look into qemu + wine x86... we'll see

Categories

Resources