Hey Guys
The beta of blue stacks in now available. Now u can run Android app on windows Downloading on CP now. Will post later how it is
I would not install it, caused me to get bluescreens after reboot
I have just installed it, played angry bird space and it works fine for me.
1/2asleep said:
I have just installed it, played angry bird space and it works fine for me.
Click to expand...
Click to collapse
On Windows 8?
I can't get BlueStacks to run in Windows 8 at all. Every time I run the installer I get a blue screen with a frown face saying that something went wrong and Windows needs to restart. I have been testing the private beta build on Windows 7 though and it is definitely fun and useful
After Few blue screen restarts it worked. Uninstalled it because it not what i expected to be. I cant run any app in full screen. I run in only a portion and i cant use gmail and angry birds because of some high performance driver issue. The alpha version before this was better.
At the moment, this is so bad
Thanks for the heads up! Going to try this.
I really wanted to try it on my Windows 8 netbook but the Thinstaller executable they gave me refused to install because my it claimed my graphics performance would be under the minimum recommended requirement. It was rather sad since the Alpha worked fine and even running the same version of Android they base their rootfs images off of (Android-x86) as a addition to my Linux dual-boot.
buggatti said:
After Few blue screen restarts it worked. Uninstalled it because it not what i expected to be. I cant run any app in full screen. I run in only a portion and i cant use gmail and angry birds because of some high performance driver issue. The alpha version before this was better.
Click to expand...
Click to collapse
Windows 8? I tried as many as 8 blue screen restarts so far. No luck. Still keeps crashing my system into the BSOD. Did alpha work on Windows 8 CP x64?
I was part of the closed beta 1 test and have been in email communication with Bluestacks development and they informed me that they do not have a beta ready for Windows 8 because it is still changing. It sounds like the focus is on Windows 7 for now.
Pls provide download links.....
Sent from my Dell Streak using XDA
nitin1978 said:
Pls provide download links.....
Click to expand...
Click to collapse
http://bluestacks.com/
nobody wants this cancer on their computers
Be on the lookout for this (when or if) it comes out
http://ces.cnet.com/8301-33377_1-57355786/bluestacks-goes-metro-with-windows-8/
o2neouzr said:
nobody wants this cancer on their computers
Click to expand...
Click to collapse
Indeed, Bluestacks should be avoided. They have no support forums (personal top gripe) and have made it quite clear they plan to try to make a quick buck leveraging VirtualBox and Android x86 while not giving anything back.
As best I can tell, they have just added an OpenGL pass through driver to Android x86 when running on VB as well as started to recompile some apps which use the ARM NDK to the x86 NDK. Far better to have the Android x86 community work on an automated NDK conversion and their own driver implementation than be shackled.
Also, their TOS lets them abuse your facebook page in new and interesting ways as well as do some serious data mining without any form of opt-out or transparency.
There are support forums:
https://getsatisfaction.com/bstk
BlueStacks even went as far as supplying a link on how to root and install gapps. I wouldn't say there is a lack of support. BlueStacks in my opinion also runs faster than x86 on a virtual machine.
aaronb1138 said:
Indeed, Bluestacks should be avoided. They have no support forums (personal top gripe) and have made it quite clear they plan to try to make a quick buck leveraging VirtualBox and Android x86 while not giving anything back.
As best I can tell, they have just added an OpenGL pass through driver to Android x86 when running on VB as well as started to recompile some apps which use the ARM NDK to the x86 NDK. Far better to have the Android x86 community work on an automated NDK conversion and their own driver implementation than be shackled.
Also, their TOS lets them abuse your facebook page in new and interesting ways as well as do some serious data mining without any form of opt-out or transparency.
Click to expand...
Click to collapse
Virtualbox and android are licensed under GPLv2/CDDL and apache respectively. Android specifically is exactly the same as stock device roms, they're under no obilgation to return code to upstream. (though every large project like this should return code, but bar the kernel they dont have to for the android portion).
virtualbox, i'm guessing they're using CDDL for it if they're not returning code.
Tell oracle (or whoever is developing it) and the android x86 teams to not release their sources under free software licenses that arnt also copyleft then.
At least with androidx86 I believe that they're free to migrate from apache -> gplv3 (according to wikipedia I dont believe gplv2 is applicable without relicensing?). But they didnt, they're still apache, which means they full well know that they can be forked and not have code returned.
Those two points are pretty much universally expected for android devices. Samsung and HTC are good enough that they provide mode then the minimal GPL modules, but they're closer to the exception then the norm. There's plenty of very low end (but inexpensive) ICS tabs being hawked on our own market. I cant really see them giving more then the bare minimum (even if that) much less providing any updates at all. They're just as much making a quick buck by only offering updates by buying a new model.
They've havnt required facebook since 0.5.0.2002, which I believe was their first public release. It was merely the cloud client that required it. You can easily use the alphas and betas without even having a facebook acct. I cant speak on how they are about people that actually opt-ed in to attachign their FB accts, but I dont have one period.
Perhaps their cloud sync isnt respecting your privacy as it should, because you right about that part. Bstacks doesnt have a clear privacy policy (or any at all on their site currently)
They're not the only ones using getsatisfaction, which acts as their support point. I cant say that I like it, but it's there. They've added a couple suggestions due to it, but it's not a forum.
Realistically, how long do you have to wait for androidx86 to be bundled in a way that lets you run it in a vm, have fair virtualization/emulation, and is stable? (though bstacks is still beta, and androidx86 is 'rc1') Androidx86 is targeting bare metal, bstacks isnt. Perhaps androidx86 actually runs perfectly well under a vm and also supports some level of hardware passthough too. Their site has instructions for using the eeepc froyo iso on virtualbox. But they obviously dont officially support virtualbox or qemu as they dont provide direct images, they merely happen to work/boot on them.
Androidx86 has 5 different isos targeting 5 different platforms, and none of them match my devices (or any of my vms explicitly). Bstacks explicitly supports vista/7 and implicitly is going to support xp/8 in the future.
I'd much rather have something working now that targets my interests then wait for something that might be more sustainable but isnt targeting me.
It's much like how xda has moto droid forums, really you shouldnt be supporting moto at least when it comes to their locked down bootloaders.
But we're not telling people to buy a different device, we give them workarounds and guides.
Finally, all bstacks is is just an opengl passthough, why has noone else done it already?
I dont expect that androidx86 on virtualbox integrates as well otherwise it'd already be huge news.
I want a virtualized android so my convertable laptop can double as a really high end android tablet, and that's what bstacks will eventually offer.
(if and when they migrate from 2.3.4 to 4.0.x)
If there's any errors, feel free to correct me. I'm rather unsure about how correct I am on the virtualbox parts.
Edit: after trying androidx86 2.3/3.2/4.0 it's fairly useless as a android tablet replacement. They dont support VM integration, and that's pretty much a requirement if you intend to use it to compliment your OS (vs merely being a utility on your os).
4.0 doesnt even work on vb with vb 4.1.8, it cant reach the home screen.
Dont take this as criticism of androidx86 though, they're always going to be undermanned and underfunded. And like previously mentioned VB isnt even a tier 1 target for them.
But realistically, there's no current alternative to bstacks for windows. Seriously suggesting androidx86 + virtualbox right now is like saying to trade for a transformer to someone asking how to install CM9 on the touchpad
moved to general - not dev
Related
Hi guys I am buying a eee pad but currently I am emailing Eclipse Google and others to try and get support to make developing for Android on Android possible.
I wish to start a foundation or support group toward this end if you want to contribute or help in anyway it would be great I will also add a poll for comparison of votes so please vote it all helps.
As I understand it porting Ubuntu to different devices is well still in beta stages for the most part but we all know that personalized mobile computing is the future and tablets or tf style devices will eventually replace laptops netbooks and the like.
As I understand the biggest problem is new tech!! that fresh out the box smell is still lingering and leaves support and development slim in some more common place computing needs where x86 has rained supreme leaving others to wish for such a client base of great support and programs.
So all in all this is to try push things in the right direction. Who to talk to when to talk to them and how to help the eee pad and other similar devices become fully fledged dual boot Android Ubuntu platforms with the option to develop and do all the other great things Ubuntu can offer.
Please only positive criticism or feedback this is the tech community anything is possible so please no comments of OMG YOU CANT DO THAT!!!! etc etc
Currently, you can compile C program or whatever without problems, using a chroot ubuntu or debian.
But developing for android implies that the android sdk has to be ported on arm platform. This is a paradox, but most android and java tools are working only on x86 platform, probably because at this time, phones was not meant to be dev platforms considering their cpu power.
Openjdk seems to work on arm but the android sdk relies on javac from sun.
There are now powerful tablet devices on the market - including our beloved tf - where we could potentially develop android apps ; I think that google will sooner or later release an arm version of the android sdk. Since then, we are almost pretty stuck : I'm not sure that all the android tools are opensource, and even if it is the case, there is still the problem of javac from sun which does not work on arm platform. However, doing our own dev platform implies that we can port ourselves the sdk on arm, and use openjdk as a replacement of sun-java runtime. Not a piece of cake My advice is to wait several months google next move to see what's going to happen, now that there are more and more tablets on the market.
If we get enough support though maybe we can push for both to be ported and released
Sent from my GT540RR using XDA App
Omg this doesn"t belong in the development forum!!!!!!!
Would love to see more development done on this!
As time progresses, more will be done definitely this is more about making sure that it is pushed as i believe at the moment its being over looked. I think manufacturers and Google and eclipse etc all under estimate there own products possibilities and the abilities of the tech community and in particular the xda community. Even if we had beta releases only for xda devs it would be a step in the right direction for developing android on android.
OK I'm going to bite the bullet and ask why would this be considered a good idea? I write software for Android and using Eclipse on lower screen resolutions isn't that productive IMHO, throw in poor keyboards and miniscule touchpads and it makes little sense. Finally considering the performance differences between a tablet and development laptop (i7, 8 GB RAM, SSD, etc) I just can't see getting the development tools working on an Android device to be all that useful at this point in time.
Nvidia is claiming the T3 will be as powerful as a Core 2. Seems a little exaggerated, but in the near future, it may be possible to dev. on a tab. Eclipse (and real games) are the last things tying me to my PC. Now I would not want to run Eclipse on a T2, but a T4??? Now we are talking.
GeraldNunn said:
OK I'm going to bite the bullet and ask why would this be considered a good idea? I write software for Android and using Eclipse on lower screen resolutions isn't that productive IMHO, throw in poor keyboards and miniscule touchpads and it makes little sense. Finally considering the performance differences between a tablet and development laptop (i7, 8 GB RAM, SSD, etc) I just can't see getting the development tools working on an Android device to be all that useful at this point in time.
Click to expand...
Click to collapse
Sent from my Transformer TF101
I tend to agree. I find even a powerful laptop is pretty marginal. I prefer a desktop with at least 2 monitors, one for code and one for the emulator.
All valid points but if no one is looking forward at the glass half full it wont become a reality
What I'm saying is work needs to start now infrastructure then city not a repeat of Auckland central we need the ground work done then the devices can catch up
Sent from my GT540RR using XDA App
I support, its something i would use.
danielmtp.mg said:
I support, its something i would use.
Click to expand...
Click to collapse
Sent from my GT540RR using XDA App
I've a script pack for installing Java's JDK to ARM either hard float or soft float that can be found at the following link
https://github.com/S0AndS0/Debian-Kit-Mods
Check the readme for how to download and enjoy the work I've done to get us this far. Furthermore there are other installers available that may be of interest; such as jMonkey and node.js and NoFlo installers for debian based Linux OS's running on Android.
Sent from my SPH-D700 using xda app-developers app
Anyone alive on this thread?
I've some links to information and projects relating to developments on Android and Linux Android systems.
For running GNU software on Android (better than busybox perhaps)
http://forum.xda-developers.com/showthread.php?t=2613243
Some maybe slower than the busybox versions but its a small sacrifice for better compatibility.
For running SDR (software defined radio) with Android or Android Linux
http://forum.xda-developers.com/showthread.php?t=2108053
https://github.com/martinmarinov/rtl_tcp_andro-
This github is really cool because the drivers are for either.
For running OpenBTS on Android Linux (turn your cellphone into a cell tower)
https://github.com/martinmarinov/rtl_tcp_andro-
Do some digging on this Dev's work; its amazing
For Crypto Currency mining on Android Linux (why buy an app when you'll have more for free here?)
http://bitbiz.io/threads/linux-script-cpu-minerd-installer-android-rpi-vps-32-64bit-pc.138/
Be sure to check out the example scripts I posted too; especially the ones relating to temp. monitoring or ya may blow a battery.
For MPI (message passing interface) on Android Linux (just modify the RPi directions to have the right username and networking options)
http://www.tinkernut.com/2014/04/27/make-cluster-computer/
Be sure to check out TinkerNut's other videos and guides; nearly anything a Raspberry Pi can do we can do on our phones for cheaper and with better specs/built in hardware.
For running Maptools server on Android (software for running custom table top games over a network)
http://forums.rptools.net/viewtopic.php?f=12&t=24082
I play DnD and Pathfinder so having a way to go mobile with it was something I had to do for them
For building Android NDK on Android Linux (step one of writing apps for Android on Android)
http://www.timelesssky.com/blog/building-android-sdk-build-tools-aapt-for-debian-arm
For building Android SDK on Android Linux (step two for writing/modding you phone with your phone)
http://www.timelesssky.com/blog/develop-app-on-android-with-android-sdk
Above two links are fantastic when combined with rdp or vnc for a larger screen size when at home.
For running Linux on Android without root (hidden goodies on FUSE filesystem)
http://www.timelesssky.com/blog/debian-android-with-no-root
There's a narrow window of compatibility but if your apposed to root on Android and still want Linux theses steps might just let you pull it off too.
For modifying Debian Kits' source code so you can have loop files larger than 2 Gigs and install hard floating point instead of soft float
http://www.timelesssky.com/blog/running-debian-armhf-alongside-android#comment-1525580294
If you've not found this Dev's blog then do some digging as there is some really cool guides posted.
For installing GPU drivers to Android Linux (scroll down to Related Projects for the other brands)
http://freedreno.github.io/
The above link and related software should allow for OpenCL/GL support and the added bonus of being able to run Blender on your tablet.
The above links should prove that developments on Android and Android Linux systems is very active; just hard to find sometimes.
I'm currently working at http://bitbiz.io/rf/?c=IGQ3ZLRT with a few other team members to bring together the above subjects into a new mesh-networking crypto coin system that allows users and developers to buy or rent hardware time from networked devices; others have tried and failed to make a AndroidCoin but this one will not as much of the core features have already been tested or scripted up in my other github repo as installers. Feel free to post feature requests and concerns.
http://bitbiz.io/threads/altcoin-taucoin-new-arm-excusive-coin.142/
Sent from: SPH-D700 or myTouch3Gs or Sero 7 Pro
Linux Install guide for Android devices that I'm writing:
http://forum.xda-developers.com/showthread.php?t=2240397
Or
https://docs.google.com/document/d/1ssVeIhdBuuy8CtpBP1lWgUkG6fR6oHxP20ToYPPw6zI/edit?usp=drive_web
And my script pack for installing; Java's JDK, node.js and more to your Linux OS
https://github.com/S0AndS0/Debian-Kit-Mods
Note: if you're new to Linux/scripting/command line; check readme file for instructions.
First, I know it's a little early for this, since Win8 isn't even in beta yet.
However, I just got a Kindle Fire, and would absolutely love a Win8 port when and if it becomes possible. So I had a few questions for devs that might take up this project.
Is anyone already planning on giving this a shot?
Would this have any legality issues, since Win8 will in all likely hood require a product key, even on the ARM version?
Is it even theoretically possible, since the Kindle Fire normally runs Android?
short answer: no
long answer: the Fire runs on an ARM CPU, while Windows 8 that has been released is 100% x86. Unless Windows 8 for ARM is released to the public - which is looking increasingly unlikely - then there's absolutely no hope. Even if it is, Only the hypothetical beta would be free of charge, and would expire fairly quickly. You would not be able to run any existing x86 programs on W8ARM, and there are rumors (with some evidence) of hardware compatibility that would prohibit it being put on any existing devices. So, even if it could be hypothetically possible, its not worth the effort. and what would you, as a consumer, get out of it, other than a UI you think is cool?
mtmerrick said:
short answer: no
long answer: the Fire runs on an ARM CPU, while Windows 8 that has been released is 100% x86. Unless Windows 8 for ARM is released to the public - which is looking increasingly unlikely - then there's absolutely no hope. Even if it is, Only the hypothetical beta would be free of charge, and would expire fairly quickly. You would not be able to run any existing x86 programs on W8ARM, and there are rumors (with some evidence) of hardware compatibility that would prohibit it being put on any existing devices. So, even if it could be hypothetically possible, its not worth the effort. and what would you, as a consumer, get out of it, other than a UI you think is cool?
Click to expand...
Click to collapse
The ability to run amd64 apps.
Sent from somewhere too far away from my computer
wtf is an AMD64app?
if you mean an x64 app, then um, no, you couldn't. x86 (x64 one name for 64 bit x86 processors) apps require an x86 processor. the kindle fire has an ARM processor. not even close to compatible, with one exception - most new metro apps will be cross compatible between windows 8 x86 and windows 8 ARM (and windows phone 8, if they decide to make it different form Window 8 ARM after all)
mtmerrick said:
wtf is an AMD64app?
if you mean an x64 app, then um, no, you couldn't. x86 (x64 one name for 64 bit x86 processors) apps require an x86 processor. the kindle fire has an ARM processor. not even close to compatible, with one exception - most new metro apps will be cross compatible between windows 8 x86 and windows 8 ARM (and windows phone 8, if they decide to make it different form Window 8 ARM after all)
Click to expand...
Click to collapse
You=noob
A 64 bit processor can run in either amd64 or intel64. Microsoft claim that windows 8 will be one big system. They also say that they can get arm to run with amd64 (and intel64) apps fine but they are accused of being unable to do so with i386. I watched the video released by Microsoft about it. All 2 hours....
If you don't know something don't pretend you know about it before posting.
Sent from somewhere too far away from my computer
really, huh. Everything I've heard puts down the rumor that 32 bit arm chips, which don't even approach the power of an i3 (and 64 bit arm chips don't exist yet) will be able to run the high end emulation needed to make an x86 apps (expecially cpu intensive 64 bit apps like most of us use on windows) work..... but that's just what I know, off all the research I've done.
If windows has managed to do the impossible, well, that's great. No sarcasm, that's awesome. But I've read press releases saying it can't be done, straight from Microsoft.
And I'm no noob - been here far longer than you, and been a tech junkie for years.
mtmerrick said:
really, huh. Everything I've heard puts down the rumor that 32 bit arm chips, which don't even approach the power of an i3 (and 64 bit arm chips don't exist yet) will be able to run the high end emulation needed to make an x86 apps (expecially cpu intensive 64 bit apps like most of us use on windows) work..... but that's just what I know, off all the research I've done.
If windows has managed to do the impossible, well, that's great. No sarcasm, that's awesome. But I've read press releases saying it can't be done, straight from Microsoft.
And I'm no noob - been here far longer than you, and been a tech junkie for years.
Click to expand...
Click to collapse
Go on wikipedia and search windows 8. Go to the compatibility section and read. Then I want an apology for being a [email protected]
Sent from somewhere too far away from my computer
Wikipedia said:
Windows 8 for ARM processors will not run software created for x86; software will have to be ported by its developers to create ARM executables from source code. [56][57]
Click to expand...
Click to collapse
You self righteous troll.
mtmerrick said:
You self righteous troll.
Click to expand...
Click to collapse
I'm sorry if I offended you but it's just my opinion fact.
And I'm sorry if your wrong. It wasn't my fault.
Sent from somewhere too far away from my computer
um, you proved yourself wrong - i was right, as i thought. You are acting self righteous, and your behavior is best described as trollish. And im not insulted -I'm laughing at your ignorance. In case you can't see quotes or something weird like that, lemme re-copypaste from Wikipedia
Originally Posted by Wikipedia
Windows 8 for ARM processors will not run software created for x86; software will have to be ported by its developers to create ARM executables from source code. [56][57]
benjamingwynn said:
I'm sorry if I offended you but it's just my opinion fact.
And I'm sorry if your wrong. It wasn't my fault.
Sent from somewhere too far away from my computer
Click to expand...
Click to collapse
1) You are an idiot, your attitude and language is discusting, i'm ashamed for you, and feel sorry for you family being related to such a duscusting little man.
2) There is no such thing as "Intel64", "AMD64" is just another name for x64 CPU's, this is because it was AMD that invented the 64bit insruction, even Intel chips use AMD's technology.
3) You have no right to be here if you are so retarded that you think an ARM CPU is compatible with either x86 or x64 based software.
Sent from my R800i using Tapatalk
wtf with the flameing people? no need to be argueing like morons to each like that. look there will be a version of windows that will work on ARM and the op is asking when that version will be released and portable to the fire. Got it????
AndroHero said:
1) You are an idiot, your attitude and language is discusting, i'm ashamed for you, and feel sorry for you family being related to such a duscusting little man.
2) There is no such thing as "Intel64", "AMD64" is just another name for x64 CPU's, this is because it was AMD that invented the 64bit insruction, even Intel chips use AMD's technology.
3) You have no right to be here if you are so retarded that you think an ARM CPU is compatible with either x86 or x64 based software.
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
Sorry for getting you involved.....
Anyway. Back to ideas on porting. It would be difficult as the Kindle Fire is Android based and running on a EXT3/4 filesystem. You would also need a different bootloader - this all involves a lot of work.
i think we should be trying to focus on the hp touchpad and the kindle fire, also the nook tablet to try to port win 8 to them once the ARM verson is released.
benjamingwynn said:
Sorry for getting you involved.....
Anyway. Back to ideas on porting. It would be difficult as the Kindle Fire is Android based and running on a EXT3/4 filesystem. You would also need a different bootloader - this all involves a lot of work.
Click to expand...
Click to collapse
Have you not listened to a single word in this thread? You can not port x86 Windows 8 to an ARM processor and expect x86 apps to run.
IF (and that's a big if) windows 8 ARM is released to the public, be it as a prerelase version or as a purchasable version, it'll be quite difficult to get it working on prexisting devices.
As i said before, there are roadblocks involved that may prohibit installing it at all. A W8 arm compatible 'BIOS' will be very difficult if not impossible to get working. It will be closed source, and quite possibly we will not be allowed to have it at all. Drivers will have to be rewritten, and windows 8 may still not be compatible with these drivers. plain old android (or whatever other ARM system) drivers will not work. There is also talk of Microsoft coding the OS as to not function with non-authorized hardware components (eg, will not work with some screens, cpus, ect) though i do not know how true this is.
Even if ARM is released to the public, and not available to OEMs only, don't expect to be able to do much to it - microsoft does not look kindly towards the modding community, and will be taking steps to hinder any changes we may need to make to the OS to get it to run.
The answer is, its unlikely at best.
mtmerrick said:
IF (and that's a big if) windows 8 ARM is released to the public, be it as a prerelase version or as a purchasable version, it'll be quite difficult to get it working on prexisting devices.
As i said before, there are roadblocks involved that may prohibit installing it at all. A W8 arm compatible 'BIOS' will be very difficult if not impossible to get working. It will be closed source, and quite possibly we will not be allowed to have it at all. Drivers will have to be rewritten, and windows 8 may still not be compatible with these drivers. plain old android (or whatever other ARM system) drivers will not work. There is also talk of Microsoft coding the OS as to not function with non-authorized hardware components (eg, will not work with some screens, cpus, ect) though i do not know how true this is.
Even if ARM is released to the public, and not available to OEMs only, don't expect to be able to do much to it - microsoft does not look kindly towards the modding community, and will be taking steps to hinder any changes we may need to make to the OS to get it to run.
The answer is, its unlikely at best.
Click to expand...
Click to collapse
It will be released to buy. It's not open-source, because of this it is unlikely... but possible
benjamingwynn said:
It will be released to buy. It's not open-source, because of this it is unlikely... but possible
Click to expand...
Click to collapse
If you dont have the source code then best wishes to you coding drivers for ARM windows 8.
johnston9234 said:
If you dont have the source code then best wishes to you coding drivers for ARM windows 8.
Click to expand...
Click to collapse
I don't need to. I'm not doing it. I came here to help and most of you threw that back in my face. I'm not here to flame.
I thought I could share my experiences with Windows since 95 and help you find hope for your kindle. If you don't want it then it's your loss. I don't have a kindle fire but I thought I should try to help you out anyway.
I can't help you with your problems unless you let me. I CAN code in a variety of different languages including C+ +, meaning I could easily pick up a arm driver for a sister device and port it.
Thanks for letting me voice my opinion. If you didn't like it then go tell someone who gives two....
A few road blocks against w8 on the fire
1) Storage: Will it actually fit in 8gig? Hopefully the arm version will without all the old bloat
2) Drivers: you are not going to see any windows8 tablet comes out with the "old" OMAP4430, they are talking about windows 8 tablets being quad core with 2gig of ram or something?
3) Ram: 512meg of ram will make running w8, if you even can get it to run, painful
4) Closed source: porting binary only OS's is hard/near imposable without a comparable device with a native version (See HD2 having almost the same hardware as WP7 and android devices).
I wouldnt bet against a port, as this is XDA, but I would consider it highly improbable.
(Also theres legal issues, MS would come down like a hammer on anyone sharing a w8 rom!)
Hey guys,
Windows 8 Developer Preview has been out for a while, and I really like what it offers... It has both the Windows 7 Phone layout for your start menu (sorta, I can't really explain it, you just have to try it to understand!), and a full windows framework and desktop to run applications. Since it's based off 7, it has a light footprint, and it works not only on x86 & x64, but armv7l aswell.
So I thought: At one time I did something to use my windows drivers on linux... (There wasn't a wifi driver, so I searched around and found a util that could let me do it) So why couldn't someone do it the other way around, for the Atrix? It would be like having Full windows on your phone but scaled down to match screen size, and then when you place it on the webtop, and voila! you get full scaled Windows 8...
I'm not saying that I can do it, but I'm just throwing the idea out there, for those of you who tried 8, you would get what I mean by the start page and full desktop thing, others just read about it!
No. One of the WOA requirements to boot is a locked AND signed bootloader, also there are NO plans to distribute WOA licenses outside of OEMs.
littleemp said:
No. One of the WOA requirements to boot is a locked AND signed bootloader, also there are NO plans to distribute WOA licenses outside of OEMs.
Click to expand...
Click to collapse
Yea I read an article on that like 5 minutes before you posted it. There don't have to be plans to release it. At some point its gonna get leaked, and as soon as that happens, devs who have the time and need for 8 will work in it...
That or have you ever tried to install mac os x on a pc? Yea it works they made some
kind of alt bootloader that will load mac bypassing all the requirements... That might happen to android devices....
Alaq said:
Yea I read an article on that like 5 minutes before you posted it. There don't have to be plans to release it. At some point its gonna get leaked, and as soon as that happens, devs who have the time and need for 8 will work in it...
That or have you ever tried to install mac os x on a pc? Yea it works they made some
kind of alt bootloader that will load mac bypassing all the requirements... That might happen to android devices....
Click to expand...
Click to collapse
Assuming someone manages to get around the technical hurdles, it will still be something akin to piracy to freely distribute WOA without microsoft's consent. This has been discussed a thousand times on different tablet forums and it's the same conclusion everytime, Microsoft has put a bunch of failsafes to stifle development on their own platform let alone porting to others. WOA is going to be much closer to iOS than Windows 7 as far as distribution goes.
The dev preview is for x86 and x86_64 architecture. An ARM build hasn't been released, so there's you're first problem.
Sent from my MB860 using XDA App
xiontinsu said:
The dev preview is for x86 and x86_64 architecture. An ARM build hasn't been released, so there's you're first problem.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
An ARM build won't be released... That's the problem...
Yo, so I installed the windows phone 8 SDK today, only to figure out that most computers in this world will not run this SDK's emulator.
You will need in an i3 or better CPU from intel or equivalent from AMD (aka latest generation) to run the emulator.
You also have to run this emulator on windows 8 x64 (yep, it HAS to be x64, otherwise it won't work). This, by itself, asks for at least 4 GB of RAM to run the system at a decent speed, also forces you to upgrade to windows 8 (i got it for free due to msdn) and to get Visual Studio 12.
This is, in my opinion, a terrible move from microsoft.
Not everybody has CPUs that have all the requirements. In fact, not even all the newest CPUs have this requirement (Second Level Address Translation it is called). This, automatically, makes developers like me either:
get a new PC
Get a windows phone 8 device.
Luckily for me i have a fairly new laptop, which has an i3 CPU capable to run this stupid emulator.
On top of that, there comes the non-backward compatibility from wp8 to wp7.5 apps. Applications compiled for windows phone 8 SDK will not work on Windows phone 7.5, unless you make another project for 7.5, compile it as dll and reference it from your 8 app. This is kinda overkill.
Windows phone 8 will probably bring in a lot of users, but for developers, it is a blow to the head. I bet windows phone 8 submissions will be very, very low in the next 1 to 2 years.
So, is microsoft risking a bit too much with the switch from 7.5 to 8? On top of all the development slaughter, there's the non-upgradable old devices...
Good question , but it's been shockingly quiet in here. One would think that after a new launch the forum would be jumping with activity.
Sent from my iPhone using Tapatalk
vetvito said:
Good question , but it's been shockingly quiet in here. One would think that after a new launch the forum would be jumping with activity.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Well, to be honest, I think XDA isn't a good place for MS/WP anymore and I guess most of them know that. Just look at the front page, not even a single article/news about the Windows (Phone) 8 launch events. It's just android. Even the forum sections for the HTC 8X/S and Samsung ATIV S are missing whereas all the new Google devices have been added shortly after their announcement. So you see, even XDAdev isn't really well after Windows Phone at all.
morpheuszg said:
Well, to be honest, I think XDA isn't a good place for MS/WP anymore ....So you see, even XDAdev isn't really well after Windows Phone at all.
Click to expand...
Click to collapse
so, what forums do wp dev's hang out ?
Are there any lol? I saw about 6 new apps, and one of them (Pandora) won't be out until sometime in 2013!
Sent from my HD7 using XDA Windows Phone 7 App
MSDN forums for example or prior to launch those who were part of the developer preview program had a closed discussion forum on Microsoft Connect, die to the NDA it was not allowed to discuss the information publicly.
On the CPU requirements - yes it sucks and there are other issues with the Emulator like missing 3d acceleration die to the fact it uses HyperV which does not have that capability. Still I would not suggest for people to develop for any platform without being able to test on a real device. This will be possible even without the Emulator.
I disagree with your assumption that we won't see Apps for WP8. Devs who write software for Windows 8 also need a Windows 8 installation, so people who think of porting those Apps will most likely have the infrastructure in place already. For higher profile the costs of a development machine would not be that problematic and C++ as well as middleware support for many gaming engines will make for a lot easier porting of existing Games from other platforms.
The people for which these changes really suck are student developers lile you and me. Only my Windows tablet currently supports the Emulator (Core i5). But still it is a lot nicer then the situation with the Android Emulator in my experience. The later is running to slow for anything iseful on my Core 2 Quad Desktop so I have to use the device for debugging anyway. Additionally only the WP Emulators have Multi-Touch support so I can test those features without deploying to the device.
Concerning XDAs, it has always been more about hacking and tinkering on the system level then user software development. Given that Android due to it's Open Source nature allows for a lot more in that regard it takes no wonder that there is a lot more going on with those than witj WP. Also market share and number of devoces makes for a difference as well.
vetvito said:
Good question , but it's been shockingly quiet in here. One would think that after a new launch the forum would be jumping with activity.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
All in all WP8 announcement was not that good...
also, they didn't release the SDK for us devs in order to build nice apps ready to be distributed for new win8 devices...Making us wait for months like if winphone had killer features hidden..and then it was the same old stuff so... i'm also considering to jump the android ship...
StevieBallz said:
MSDN forums for example or prior to launch those who were part of the developer preview program had a closed discussion forum on Microsoft Connect, die to the NDA it was not allowed to discuss the information publicly.
On the CPU requirements - yes it sucks and there are other issues with the Emulator like missing 3d acceleration die to the fact it uses HyperV which does not have that capability. Still I would not suggest for people to develop for any platform without being able to test on a real device. This will be possible even without the Emulator.
I disagree with your assumption that we won't see Apps for WP8. Devs who write software for Windows 8 also need a Windows 8 installation, so people who think of porting those Apps will most likely have the infrastructure in place already. For higher profile the costs of a development machine would not be that problematic and C++ as well as middleware support for many gaming engines will make for a lot easier porting of existing Games from other platforms.
The people for which these changes really suck are student developers lile you and me. Only my Windows tablet currently supports the Emulator (Core i5). But still it is a lot nicer then the situation with the Android Emulator in my experience. The later is running to slow for anything iseful on my Core 2 Quad Desktop so I have to use the device for debugging anyway. Additionally only the WP Emulators have Multi-Touch support so I can test those features without deploying to the device.
Concerning XDAs, it has always been more about hacking and tinkering on the system level then user software development. Given that Android due to it's Open Source nature allows for a lot more in that regard it takes no wonder that there is a lot more going on with those than witj WP. Also market share and number of devoces makes for a difference as well.
Click to expand...
Click to collapse
ya, I saw that w8 64bit was required to develope at all, and thought wow, why would you limit developers to a brand new unproven ecosystem?
the prehighschool kids are going to be the ones with real innovation, new thinking, and the next Facebook, (I hate fb, but you get the idea) without them, what do you have? Office? really , just Office?
ohgood said:
ya, I saw that w8 64bit was required to develope at all, and thought wow, why would you limit developers to a brand new unproven ecosystem?
the prehighschool kids are going to be the ones with real innovation, new thinking, and the next Facebook, (I hate fb, but you get the idea) without them, what do you have? Office? really , just Office?
Click to expand...
Click to collapse
64 bit is likely to not be the big issue here. I haven't seen to many 32 bit Windows 7 machines. The more problematic move is to lock out everyone who is not using Windows 8. Given that students have access to Windows 8, Visual Studio and the Marketplace for free through Dreamspark that does not sound as that big an issue to me.
In the end it seems they had a reason to go with Hyper-V and Windows-8 simply is the only Desktop operating system which has Hyper-V functionality. The biggest problem is that hardware that is older then 2 years does not support the needed virtualization modes.
How the ecosystem argument plays into this I don't really understand but I guess you meant: new OS that has not that big an installed base yet. Well 4 million upgrades over the last 4 days, not counting the people who bought it with new Hardware or downloaded it from MSDN or Dreamspark it seems to go big rather quickly.
The emulator is a crucial part of application development.
I don't think you want to bring in your early app in alpha stages or even earlier than that on your phone, simply because:
a) you don't have it.
b) Your code might cause damage to the phone, especially on things that use hardware components like vibrators, camera, leds and stuff like that. An unleaded exception can wreck havoc on your phone.
c) The emulator is faster.
Yes, you will eventually need a windows phone 8 device before you publish it, but you should be able to develop your apps before you even have one...
The windows 8 issue is not big. The upgrade from win7 costs like 50 bucks. It is really not that much of an effort.
The insane hardware requirements are, however, and most PCs will not have them. From intel's side, only i3, i5 and i7 processors have what they need, and Pentium dual core for sandy bridge won't...
This is the biggest issue here.
ohgood said:
so, what forums do wp dev's hang out ?
Click to expand...
Click to collapse
i'm just a noob, but i think when the devs don't hang out here they hang out nowhere or compared to android extremely rare so that it makes no sense to spend time on...
I wish WP8 RT a good future with Dualboot Android.
Hey,
I have really been wanting to root my Galaxy-S8, and the only computer I have available to me currently is a Acer Chromebook. I've been doing a little research on the subject, and it doesn't seem like there's a lot of info on the topic - is that a sign I'm wasting my time?
Really curious if this is possible...
hammer280 said:
Hey,
I have really been wanting to root my Galaxy-S8, and the only computer I have available to me currently is a Acer Chromebook. I've been doing a little research on the subject, and it doesn't seem like there's a lot of info on the topic - is that a sign I'm wasting my time?
Really curious if this is possible...
Click to expand...
Click to collapse
Root is only achievable on a nougat system Oreo and pie nope. I don't know if it's possible from a chrome book most of the rooting tools are based for windows. But jrkruse safestrap rev 5. Is the way
TheMadScientist said:
Root is only achievable on a nougat system Oreo and pie nope. I don't know if it's possible from a chrome book most of the rooting tools are based for windows. But jrkruse safestrap rev 5. Is the way
Click to expand...
Click to collapse
Uhmm...
Actually, I'm afraid that's incorrect. I understand this post was from 2019, but Chromebooks have never been able to use Windows packages and programs. Their OS is Chrome OS, which is basically android but with an enhanced chrome browsing experience. And everyone knows that Android is solely Linux based,... as android uses the linux kernel. You see, Linux is open source, right?... therefore, using the Linux kernels, the android developers were able to implement the various modifications that fit their needs.
Now, the Chromebooks, have actually brought even more Linux computing to the table. First off, they have a full fledged Linux distro in beta, that you can enable... Actually even without enabling the linux beta, Chromebooks all have access to the developer shell. As well as Chrome's very own "Crosh" terminal. Both of which are operable using linux commands. (Not windows)
And on just another note...
Google, over the past few years, actually has been working on a new Chrome browser. And by "past few years", I mean even at the time off this original post, up untill now, they've continuously been working on this thing. Lol Yes, I know... Incredible isn't it? Lol Any way, even though it is still currently being worked on Chromebook users now have access to this new brower, via enabling it through turning on a few flags in "Chrome://flags". So the main idea for this browser is actually to decouple the browser from the OS, giving the new Chrome Web browser, much more of a separation. (Which I'm definitely in favour of, and is far less confusing lol). So this new browser, has yet to actually be "officially named" (probably will just stay as "Chrome")... But for now, the developers have made it identifiable to us users, and have been referring to it as "LaCrOS". So, I just want to point out, that the name "LaCrOS" is actually derived from both the words "Linux" and "Chrome OS".
One thing, maybe is what you were thinking of, is that some Chromebooks (like my own) use the amd x86 processors, instead of Arm64, which is the same processors that you'd find in any windows computer (that is aside from, well... now Apple lol) But even though The Chromebooks that use x86 processing offer more of a powerful performance (as well as a powerful consumption of battery & memory) they still very much are Linux based machines... And are VERY VERY different than a windows computer. In order to run any Windows program or package on a Chromebook, you'd need some type of emulator allowing you to do so. Chromebooks, alike Androids, without use of an emulator, are only able to read, install, and run .apk files and not a windows .exe file.
Gorvetco said:
Uhmm...
Actually, I'm afraid that's incorrect. I understand this post was from 2019, but Chromebooks have never been able to use Windows packages and programs. Their OS is Chrome OS, which is basically android but with an enhanced chrome browsing experience. And everyone knows that Android is solely Linux based,... as android uses the linux kernel. You see, Linux is open source, right?... therefore, using the Linux kernels, the android developers were able to implement the various modifications that fit their needs.
Now, the Chromebooks, have actually brought even more Linux computing to the table. First off, they have a full fledged Linux distro in beta, that you can enable... Actually even without enabling the linux beta, Chromebooks all have access to the developer shell. As well as Chrome's very own "Crosh" terminal. Both of which are operable using linux commands. (Not windows)
And on just another note...
Google, over the past few years, actually has been working on a new Chrome browser. And by "past few years", I mean even at the time off this original post, up untill now, they've continuously been working on this thing. Lol Yes, I know... Incredible isn't it? Lol Any way, even though it is still currently being worked on Chromebook users now have access to this new brower, via enabling it through turning on a few flags in "Chrome://flags". So the main idea for this browser is actually to decouple the browser from the OS, giving the new Chrome Web browser, much more of a separation. (Which I'm definitely in favour of, and is far less confusing lol). So this new browser, has yet to actually be "officially named" (probably will just stay as "Chrome")... But for now, the developers have made it identifiable to us users, and have been referring to it as "LaCrOS". So, I just want to point out, that the name "LaCrOS" is actually derived from both the words "Linux" and "Chrome OS".
One thing, maybe is what you were thinking of, is that some Chromebooks (like my own) use the amd x86 processors, instead of Arm64, which is the same processors that you'd find in any windows computer (that is aside from, well... now Apple lol) But even though The Chromebooks that use x86 processing offer more of a powerful performance (as well as a powerful consumption of battery & memory) they still very much are Linux based machines... And are VERY VERY different than a windows computer. In order to run any Windows program or package on a Chromebook, you'd need some type of emulator allowing you to do so. Chromebooks, alike Androids, without use of an emulator, are only able to read, install, and run .apk files and not a windows .exe file.
Click to expand...
Click to collapse
Ummm. As I stated years ago. I didn't know. I didn't say yes.
We didn't need a long drawn out explanation of a chrome book. And so you know. I've had a hp windows laptop that I've swapped back and forth between windows and chrome os. For my kid.
Your post is completely irrelevant. As it is so old of a topic. Either way the methods for these devices are completely depreciated.
I am one of the people who helped out on these devices with heavy testing. Plus much much more.
By you telling me I was incorrect just shows that you are acting like a pompous know it all and trying to prove me wrong where I specifically said I didn't know. How does me saying I don't know make me incorrect?
On a side note. We here at xda don't much care to drag up old deals topics that have long since been gone and irrelevant.
Clutters the pages with old useless information
It wasn't irrelevant. I disagree.
Furthermore, the original question was regarding Chromebooks specifically, and not Chrome OS. So my apologies, but shouldn't even the oldest of threads be contemporized if the new information or tools now available have changed since then? But as I did mention, this was not the point of what I wanted to make clear.
I did not say anything regarding the effectiveness or ineffectiveness of utilizing a Chromebook to obtain root on an seperate android device. Nor did I state that you were incorrect. I'm well aware, that it would be ignorant and frankly just unfair to disparage you based on the knowledge available at the given point in time. However, it's unfortunate that you felt obligated to retaliate in such a manner, as It was very clear of what my actual intensions here were, and that it was not in any way a means to belittle you.
There is something you may just have me on though. For in the sense that I guess I am unsure of the protocol here at XDA. But I still do not feel that attacking me was the right way to go about your response. You see, I'm a member at both GitHub, and Stack exchange. So I guess I just assumed that because there is plenty of room for misinterpretation, and at times even errors, so honestly, some of the best ways to further our understanding is when we converse and can learn from one another. In any case, I had noticed that your comment could very easily be misinterpreted, and not everyone is on the same advanced level as you might be. So its best to not just assume, but actually it is encourage to give your answers as if you may be explaining to someone who isn't familiar with the subject at all, and using examples and explaining as clearly as possible are excellent way to do this, and usually can be most appreciated.
As for trying to prove you wrong, I do then appologize, as that was not my intentions. I only wished for it to be acknowledged, that a Chromebook, regardless of the year, then and now, in no way has the ability to utilise any Windows rooting tool. I did not state this to offend any one. It was only to contribute a very descriptive and detailed body of information, ensuring that the difference between windows executable files and that of Androids are to be both known and understood, to avoid anyone's time being wasted on a task or and idea that would get them nowhere.
It is necessary to do this, as for the chance an unknowingly individual may come across this thread, looking for answers similar to the question at hand. As you should know, even "old topics" should be rectified as such. Unless in the event they are to be removed, locked or relocated to a more appropriate forum.
The only thing here I believe to be irrelevant, is that you felt inclined to point out what I had already stated and took into consideration. So again, that way it is clear, I would just like to point out... that regardless of the year, whether it be 4 years ago, 4 months ago, or whether it be today. I amend the information I provided, and consider it to not only be "relevant" but I hope it proves to be useful and potential prevent or deter someone who would have been then proceeding to inquire about how to run "Windows rooting tools" on a chromebook.