when remix os will support AMD chipset?
Maybe they're bought by Intel. Can't imagine/remember any software on this planet not functioning on only one of those two without the interference of the programmer.
Yeah, I wanted to try it today and was super dissapointed because it doesnt work on my PC. Im wondering if they will add AMD support in the future.
I am also a little put off by this. Does not make much sense to support only one chipset... especially when you are cutting out a major chunk of the market
AFAIK The player requires Intel HAXM because it is based on the Android SDK emulator, which also requires HAXM.
Related
On the featured demo you will see the Android OS running on a reference device based on the Qualcomm MSM7200 with a 300Mhz processor.
The chipset is gaining popularity with PocketPC manufacturers - it was also in the root of the HTC user upheaval for some reportedly missing video drivers. The Android OS however benefits from the Qualcomm integrated 2D/3D accelerator in a way that the disgruntled HTC users could only wish for - it's playing a Quake demo at 30 fps.
it would be possible to ripp off the drivers from the new devices and somehow put them on htc's that lack such drivers?
Isn't android linux based?
Yes; I doubt such portability of drivers is feasible.
If you google android gpu acceleration, you'll see numerous threads on other sites of people asking for it and others saying there hardware is smooth enough.
I don't want to discuss the merit of gpu acceleration as I think it's a given. What I'd like to know is a list of apps that do. But also, if these apps can, why isn't it utilized system-wide? Other threads mentioned older hardware could only have one opengl layer, so if your launcher was gpu accelerated, then a game wouldn't launch. I doubt this is the issue now with more recent hardware.
Is there any side project trying to add this to say cyanogen?
Anyway, I know launcher pro is accelerated. The scrolling through applications is like night and day with other launchers. Also the latest Opera is accelerated. It seems like the built-in gallery app is accelerated. I'm not sure about any of the pdf viewers. ezpdf seems the smoothest, but again, it might be just more optimized over other pdf readers.
So is there a list of apps that utilize the gpu? (besides games obviously)
I'm not sure if it's a video driver issue from device to device, but if that's so, how can a small app like launcher pro work accelerated on numerous devices?
sark666 said:
But also, if these apps can, why isn't it utilized system-wide?
Click to expand...
Click to collapse
Because a lot of Android phones can't take it.
Other threads mentioned older hardware could only have one opengl layer, so if your launcher was gpu accelerated, then a game wouldn't launch. I doubt this is the issue now with more recent hardware.
Click to expand...
Click to collapse
Yeah, but Android's target is a huge range of hardware- some very crappy. Read up on Android's "fragmentation problem."
Is there any side project trying to add this to say cyanogen?
Click to expand...
Click to collapse
A composite based GUI is a HUGE project. It is WAY beyond the scope of this community. It is what delayed Windows Vista for so long, and was a huge reason why many people didn't like Vista (as hardware around its launch couldn't handle the interface).
It took the Linux desktop over three years to add a decent composite GUI, and that was with MANY large companies working on it.
Composite based GUIs are VERY VERY difficult to get right. The only reason Apple has it right is from the get go that was the best part of OSX. Apple's engineers somehow got its composite GUI (called Quartz) on old low-MHz PowerPC machines, and that miracle of technology has not been duplicated anywhere else. In fact, that was the competitive advantage that Apple took with it to the phone market once phones were as powerful as old PowerPC machines.
Other OS's that use a GPU accelerated GUI just have to have very strict minimums for hardware. For example, look at the minimums for Window's phones. Any one of those would be high-end in the Android market.
I'm not sure if it's a video driver issue from device to device, but if that's so, how can a small app like launcher pro work accelerated on numerous devices?
Click to expand...
Click to collapse
Run Launcher Pro on an older Android device like a Droid 1 and you would be singing a different tune as to how smooth it is. The fact of the matter is that the Android eco-system isn't ready yet....
Hmm, compiz made huge improvements quite rapidly so I don't know about 3 years to get it right. The benefits were immediate; maybe refinements as it went along.
Regardless if it is huge undertaking, google has to address this. I've read articles where they say it's more garbage collecting vs an accelerated gui. Here's a brief but good article on it: http://www.satine.org/archives/2011/01/01/the-care-and-feeding-of-the-android-gpu/
And linux is a good example, the initial beginnings of compiz were a very small group of developers and features were being added very rapidly.
It turns a lot of people off android when they see a sluggish OS, or the appearance of a sluggish OS.
At any rate, my question still stands. you mention older devices needed to being supported. Then how does an app like launcher pro do it? I'm sure it doesn't have custom drivers for all the various gpu's out there? Same with Opera.
And I'd still like a list of (if there is one) of gpu accelerated apps. If the OS doesn't have it, then it would be nice to have it at the app level. Although I see that causing more headaches down the road instead of the OS doing it.
Anyway, google doesn't sound like they are taking this issue seriously. Or dismissing it as not necessary, but I think that's a mistake. On a traditional desktop OS, it's a nice to have but not really necessary, as most things are static. But given the size of the these devices, menus/icons etc are usually moved about cascade and expand etc. Items are dragged and moved etc. All this calls for an interface that maintains a high fps or otherwise it gives the perception of feeling laggy.
Trust me...rewriting Android to do automatic compositing is a huge undertaking. This would be very difficult to do while maintaining compatibility which existing applications. Honeycomb has compositing but it isn't enabled in applications by default because it can break applications with custom drawing. I don't see any reason for us to attempt to implement composting when its already done about as well as anyone can do it in Honeycomb.
sark666 said:
Hmm, compiz made huge improvements quite rapidly so I don't know about 3 years to get it right. The benefits were immediate; maybe refinements as it went along.
Click to expand...
Click to collapse
GPU GUI acceleration on the Linux desktop didn't start with Compiz. GPU GUI acceleration started in 2004 when Keith Packard added the composite patch to Xorg. David Reveman began working on XGL and Compiz around that time, and didn't release a workable beta version until 2006.
Yet that beta version relied on XGL, which was basically running the Linux desktop like you would a video game. It wasn't until AIGLX became stabilized in open source and closed source drivers in 2007 that GPU GUI acceleration on the Linux desktop was finished (I am huge Xorg junkie, that is why I know these random facts).
Regardless if it is huge undertaking, google has to address this. I've read articles where they say it's more garbage collecting vs an accelerated gui.
Click to expand...
Click to collapse
From what I have heard, Honeycomb supposedly has a GPU accelerated GUI. But we don't know till we can see the code.
It turns a lot of people off android when they see a sluggish OS, or the appearance of a sluggish OS.
Click to expand...
Click to collapse
I would say that the sluggishness is only obvious next to iOS- other mobile OSes also lack such abilities. Compared to iOS Android has mostly targeted the lower-end user segment where quality of experience is less important than raw price (hence the many underpowered Android phones).
Eventually due to attrition the baseline will increase in power and old phones will be cut off for new features such as this. I have already heard that Gingerbread runs terrible on a Droid 1, which is barely a two year old phone.
Then how does an app like launcher pro do it?
Click to expand...
Click to collapse
Same way games do it- they just run like crap on older phones. Google can't afford to take that approach with the entire OS.
And I'd still like a list of (if there is one) of gpu accelerated apps. If the OS doesn't have it, then it would be nice to have it at the app level.
Click to expand...
Click to collapse
Me too.
Anyway, google doesn't sound like they are taking this issue seriously.
Click to expand...
Click to collapse
I think that is an accurate assessment. I think Google believes that in time the hardware itself wil cover this inadequacy- it matters less on dual core phones. Its all those poor people that bought early Android phones that have had to suffer the most...
I'm sure it's not trivial, but again standalone apps seemed to have done it. I know OS wide is another issue. But really, honeycomb is really late when it comes to this. It really should have been a 2.x feature. I"m the exact opposite of an apple fan boy, but the first iphone in 2007 had this. That set the bar right there. What 4 years later and google is almost on it? And yes iphone is a fixed device, but still. An abstraction layer should have been worked on so if a device has a gpu it's used, otherwise fallback to software.
And on a side note, It would still be nice to know apps that do implement this now.
sark666 said:
An abstraction layer should have been worked on so if a device has a gpu it's used, otherwise fallback to software.
Click to expand...
Click to collapse
I am a huge fan of this stuff (I actually had a blog about composite back in the day) and I can tell you after hacking on many devices and OSes, only ONCE have I seen a decent software-based compositor. OSX. That is it, in the whole world.
In fact, Apple's entire "magic" empire of devices is built on that unique competitive advantage. Part of what has made it work is that composite was there from day one- unlike a Linux, Windows or Android, OSX/iOS has ALWAYS had composite so applications had to work with it.
And it wasn't a painless process. Early OSX versions (until Tiger I think) all had major composite bugs (to the point I am good at spotting them). Part of Apple's advantage is that initially the OSX base was so small that it didn't matter what broke and what didn't.
So essentially it is not a 4 year gap, but is more like a 10 year advantage. All those old PowerPC Mac users paid out the nose to make modern Apple phones the pleasant experience they are.
To me the saving grace of Android is that Google allows developers to replace major parts. So maybe the entire OS will never have real GPU acceleration, but Google doesn't stop the Operas and Launcher Pros of the world to replace essential functions with apps that CAN leverage that ability. That way different parts of the OS get fixed up by those who are best at that part, and those with weaker hardware can do without.
So yeah, a list would be nice.
Well even Windows XP seems to dust Android's best. For example, browsing these very forums on my pathetic netbook is smooth but on NC it is extremely slow unless Opera Mobile is used. Even Honeycomb's browser is slow scrolling these forums. It is pretty mind blowing that in 2011 there would be 2D GUI inadequacies like this.
But the reason is as has been said: there are phones with really poor GPUs running Android. So Google basically set the bar too low in order to probably lower the cost to develop an Android device and now they don't want to break compatibility. Although I don't see why 3.0 couldn't have been more ambitious.
Not Quite A List of Android GPU Apps
GPU Acceleration will be system wide when Ice Cream Sandwich is released. I stumbled upon this thread hoping to find specific apps. I am of the Nvidia Bootcamp, so that influenced me to get a Droid X2. There are some killer apps that work perfect with GPU acceleration. I am rather surprised to find that this thread became a history lesson, much which I knew and Wikipedia could tell me.
I am using a Movie Player on Android called MX Video Player (FREE and Free Codec Download Required). It works extremely well. This app is an excellent example of quality software taking advantage of GPU acceleration, before a system wide implementation. I doubt "MX" will get better when ICS is here.
As for CyanogenMod none that I know of other than the ICS port they are cooking up. Has to do with ICS SDK API 14, that is the framework for it?
When I find more I will add to the list here, that is if I dont forget.
Oh and that snyde XP comment.... Let me know how the android gui and os is when it has had ten years in the limelight, with patches and bug fixes!
Just wondering if there will be support for AMD processors in the near future?
Has anyone had any success with an AMD CPU/APU?
moman2000 said:
Just wondering if there will be support for AMD processors in the near future?
Has anyone had any success with an AMD CPU/APU?
Click to expand...
Click to collapse
Well...short answer....no.
It use Intel dev tools for android.
And amd does not build android devices unlike Intel.
They need to switch to virtualbox like other emulators.
But it will have slower video support.
To add to what @tailslol said, Android Studio (which is what Remix OS Player is based on) requires HAXM to run. AMD doesn't support HAXM. Sorry to be the bearer of bad news...
With a lot of new phones coming with ARMv8, why do the arm emulators suck so bad....it makes testing for these a nightmare. Let's get some more Arm support in Android Studio
I've given up on the arm emulator. Have you tried Genymotion? It's a great emulator, free for personal use and really fast. I recommend it.
works for android studio and eclipse
Genymotion is an excellent recommendation, and as a side note its a plugin that works for both Android Studio and Eclipse.
BlueStacks and Andy are decent but you can't beat free!
Why do the ARM emulator suck..?
With a considerable measure of new telephones accompanying ARMv8, why do the arm emulators suck so bad....it makes testing for these a bad dream. How about we get some more Arm support in Android Studio.
no updates
diehard2013 said:
no updates
Click to expand...
Click to collapse
Becauase JIDE was dead.
come again
Totally dead. They already give official statement in their Facebook Page
Requiem aeternam dona eis, Domine,
et lux perpetua luceat eis.
JIDE is NOT dead - just targeting enterprises (not ordinary users)
diehard2013 said:
Requiem aeternam dona eis, Domine,
et lux perpetua luceat eis.
Click to expand...
Click to collapse
JIDE is moving FROM ordinary users to enterprises; and I don't exactly blame them.
Let's be honest with ourselves - the two biggest problems RemixOS products face (all of them) is that they aim (literally) too high in the Android-on-PC subspace (two ways they aim too high - they are based on MM - not KK or L, which is where all the action is, and the reality is that - for precisely that reason - RemixOS is STILL too "hefty" for the Android-emulator space (which is still where the action remains, as opposed to the replacement-for-Windows space). If you have 16 GB of RAM, you CAN run RemixOS alongside Windows - however, why would you, unless there is a specific app/game that you want to run that requires MM or N - and even then, it's STILL easier to run that game or app on a device. The only folks that are going to be looking at that niche use (and the reality is that it IS a niche use) are enterprises and corporate users - not the everyday user. And, if anything, the availability of cheaper N devices (such as the launch of Lnovo's Tab 3 Essential line - which is now based on a commodity-designed Qualcomm SoC - as opposed to the original Mediatek SoC that Lenovo started with) has created a reliable easier-to-target SoC without the problems of Mediatek (at least for now, Qualcomm is NOT repeating the errors that got them in hot water in the networking space - the same errors that got Mediatek in hot water in the SoC space); basically, Qualcomm learned from the mistake they made in networking - the same mistake that the competition did NOT learn (and instead repeated). Result - the complaint that folks are making about Qualcomm is that they are a quasi-monopoly; however, how is it Qualcomm's fault that it learned from the mistakes that IT made elsewhere - and their competition largely didn't? Unless Qualcomm makes a similar egregious error to the one that Mediatek made (or that Qualcomm itself made in networking) I don't see them going anywhere - especially with other ARM licensees and competitors shooting themselves in one or both feet.
If you are in the emulation space (running alongside Windows), there is next to zero reason you would want an MM-based emulator - and especially if you have less than 16GB of system RAM. (I found myself replacing RemixOS Player with MEMu Player (which is still based on KitKat) after I added a second N-based Android device (ex-VZW Galaxy S7 running in SIMless/tablet mode) to my daily-driver Samsung GNex. Let's be honest - even as a TABLET, the two-year-old Snapdragon-driven S7 is far from a slouch; it's plenty speedy - and without the heavy lifting that phones typically have to do, if anything, it's even faster. Then there is the reality that there aren't many tablets (or phablets, for that matter) that can run N reliably without causing wallet rape (all of seven prior to the return of the Note7 - now the Note7 FE) - and three of those are not only Nexus devices, but are no longer manufactured - Nexus 6 (Motorola), Nexus 7 (ASUS) and Nexus 9 (HTC). The other four? Shield K1 (nVidia), Shield Original tablet (also nVidia), Galaxy Tab S2 (Samsung) and Pixel C. The vote in terms of emulators of the Android sort remains low-end/cheap - not the higher end stuff that JIDE built.
PGHammer said:
JIDE is moving FROM ordinary users to enterprises; and I don't exactly blame them.
Let's be honest with ourselves - the two biggest problems RemixOS products face (all of them) is that they aim (literally) too high in the Android-on-PC subspace (two ways they aim too high - they are based on MM - not KK or L, which is where all the action is, and the reality is that - for precisely that reason - RemixOS is STILL too "hefty" for the Android-emulator space (which is still where the action remains, as opposed to the replacement-for-Windows space). If you have 16 GB of RAM, you CAN run RemixOS alongside Windows - however, why would you, unless there is a specific app/game that you want to run that requires MM or N - and even then, it's STILL easier to run that game or app on a device. The only folks that are going to be looking at that niche use (and the reality is that it IS a niche use) are enterprises and corporate users - not the everyday user. And, if anything, the availability of cheaper N devices (such as the launch of Lnovo's Tab 3 Essential line - which is now based on a commodity-designed Qualcomm SoC - as opposed to the original Mediatek SoC that Lenovo started with) has created a reliable easier-to-target SoC without the problems of Mediatek (at least for now, Qualcomm is NOT repeating the errors that got them in hot water in the networking space - the same errors that got Mediatek in hot water in the SoC space); basically, Qualcomm learned from the mistake they made in networking - the same mistake that the competition did NOT learn (and instead repeated). Result - the complaint that folks are making about Qualcomm is that they are a quasi-monopoly; however, how is it Qualcomm's fault that it learned from the mistakes that IT made elsewhere - and their competition largely didn't? Unless Qualcomm makes a similar egregious error to the one that Mediatek made (or that Qualcomm itself made in networking) I don't see them going anywhere - especially with other ARM licensees and competitors shooting themselves in one or both feet.
If you are in the emulation space (running alongside Windows), there is next to zero reason you would want an MM-based emulator - and especially if you have less than 16GB of system RAM. (I found myself replacing RemixOS Player with MEMu Player (which is still based on KitKat) after I added a second N-based Android device (ex-VZW Galaxy S7 running in SIMless/tablet mode) to my daily-driver Samsung GNex. Let's be honest - even as a TABLET, the two-year-old Snapdragon-driven S7 is far from a slouch; it's plenty speedy - and without the heavy lifting that phones typically have to do, if anything, it's even faster. Then there is the reality that there aren't many tablets (or phablets, for that matter) that can run N reliably without causing wallet rape (all of seven prior to the return of the Note7 - now the Note7 FE) - and three of those are not only Nexus devices, but are no longer manufactured - Nexus 6 (Motorola), Nexus 7 (ASUS) and Nexus 9 (HTC). The other four? Shield K1 (nVidia), Shield Original tablet (also nVidia), Galaxy Tab S2 (Samsung) and Pixel C. The vote in terms of emulators of the Android sort remains low-end/cheap - not the higher end stuff that JIDE built.
Click to expand...
Click to collapse
in vino veritas, acta non verba..
diehard2013 said:
in vino veritas, acta non verba..
Click to expand...
Click to collapse
Just a thought here: If Jide had any thoughts about not being committed to this project, why did they even bother collaborating with the Android-x86 project in the first place? And why did they wait so long, between the latest releases of Remix OS (mid-November) and the official announcement?
With Remix OS for PC/Windows out of the picture (and with it, gone is perhaps one of the best--if not THE best--graphic environments for an Android-based OS), which of the remaining Android-based operating systems would you recommend? Right now, I'm giving consideration to either Phoenix or BlueStacks. If I had to choose, I'd be tempted to go with BlueStacks, because it has its own front end (or whatever it is called, which Remix OS had in Remix OS Player) which runs inside Win7/10; while for Phoenix (which has the better-looking graphic environment), I'd probably have to use VirtualBox or VMware, since as of now I don't know if they (or anyone else) developed a front end for this OS to run in a window inside Win7/10.
CookyMonzta said:
Just a thought here: If Jide had any thoughts about not being committed to this project, why did they even bother collaborating with the Android-x86 project in the first place? And why did they wait so long, between the latest releases of Remix OS (mid-November) and the official announcement?
With Remix OS for PC/Windows out of the picture (and with it, gone is perhaps one of the best--if not THE best--graphic environments for an Android-based OS), which of the remaining Android-based operating systems would you recommend? Right now, I'm giving consideration to either Phoenix or BlueStacks. If I had to choose, I'd be tempted to go with BlueStacks, because it has its own front end (or whatever it is called, which Remix OS had in Remix OS Player) which runs inside Win7/10; while for Phoenix (which has the better-looking graphic environment), I'd probably have to use VirtualBox or VMware, since as of now I don't know if they (or anyone else) developed a front end for this OS to run in a window inside Win7/10.
Click to expand...
Click to collapse
It's not that anything necessarily is WRONG with RemixOS - nobody has said that (not me - or anyone else, for that matter) - it's simply overkill for what most users want. It's like the market for high-end GPUs (without the price factor); it's still a niche market. As good a graphical environment as RemixOS - and Marshmallow itself, for that matter - is, why have things moved north (on actual Android devices) and stayed south (on Windows-based Android emulators)?
As the default OS (as is the case with devices), unless you are talking the low and cheap end, N is the new JellyBean - not MM. (Note that instead of doing OTAs for the existing J3 - which is running MM - Samsung chose a hardware refresh instead; this is despite the J3 pre-refresh being barely two years old - and not even that in North America,) As an emulator core (alongside or within Windows), the tendency is STILL to prefer lightweight emulators - which still means KitKat or JellyBean - primarily so Windows (the core OS) can keep most of the resources itself. RemixOS Player didn't require vmWare OR Oracle VirtualBox - just like most of the KK or JB-based emulators; hence none of them are shackled to HAXM. I RAN RemixOS Player because I could take higher-end Android games to it - which wasn't - and still isn't - the case for most emulators - with OR without HAXM. However, gaining that S7 did away with my own need for a high-end emulator. (Remember, the S7 - while not shipping with N - instead, it shipped with MM - now can be blanked and factory-type N-ified using nothing more complicated than either Odin or Heimdall.)
What is further trouble for JIDE is that N is expanding at the low-end. I mentioned earlier Samsung's J3 refresh (which is now N-based - not the MM of the previous version); the same is true of Lenovo's Tab 3 Essential - a refresh of the earlier Tab 2 series of tablets and phablets. Unlike the Tab 2 (which started at KK and went only to L - with only the phablets going beyond L with community ROMs, and typically in languages OTHER than English), the Tab 3 Essential has changed SoCs from MediaTek (MTK) to Qualcomm - they also ship with N out of the box. Amazingly, the price tags went nowhere compared to the MTK predecessors - even the largest of the new line is BARELY $100 from Amazon - including shipping for non-Prime customers. With N for cheap, whither RemixOS? (Basically, RemixOS is being made moot by N on devices - not nice, but there it is.)
What are you guys transitioning to? Any suggestion for someone who was looking into purchasing another Jide solution?
KingdomMan3 said:
What are you guys transitioning to? Any suggestion for someone who was looking into purchasing another Jide solution?
Click to expand...
Click to collapse
You mean SW or HE'S?
anyone still usinng it?
hi guys. anyone still using it? is it stable enough? im thinking to install it on my pixel c tablet
These are project for which
---------- Post added at 02:56 AM ---------- Previous post was at 02:54 AM ----------
Give me a link pixel experience Android p for resume 4x
Hey guys,
I'm planning going back to Remix OS 3.0 (MM) on my Pixel C since AOSP really sucks for a lapotp like tablet like the Pixel C.
But I am worried about Security... Is it possible to use Antivir software like Avast to compensate the missing security updates?
If yes, can you recommend me an antivir app?