Google explains why it stopped Acer's Aliyun smartphone launch


Recommended Posts

Listen..let's make something clear.. Android IS open.. you can go take it and make ANYTHING you want with it. Amazon is proof. So let's stop with this Android is not open malarky.

The reason Google is against this is because the other OS IS using Android and Acer is trying to use that OS and continue using Google's services. That's not gonna happen.

Google's services ARE NOT open. So when OHA was created every member agreed not to branch out with alternate Android OSs and use the official builds because that's the only way it will guarantee a healthy and compatible ecosystem.

Acer can abandon OHA and go use Android and build whatever they want. The downside for them will be no access to official Google services that are supported on Android.

Google made their services that give value. You can use Android and do whatever the hell you want. Amazon did it and nobody is against them but even Amazon can't take Android and branch it out. The license specifically stands that you can use Android for whatever you want but you have to build on top of the foundation making Android apps compatible with your eco-system. If you don't comply you can't use the code.

This seems like a very reasonable thing. It's in the interest of consumers.

Wierd Boz, you being a bit of a hypocrite, if Apple used the fact they develop the OS as a fact they can keep a tight reign on it your the first to complain and smash then for not being OPEN like google.

Pretty sure he's referring to this.

http://www.androidpo...er-pirate-site/

Acer need to step a away from this OS.

Ok - thanks for explaining

To me open means purely open and anything less should be prefixed as such and was why I worded my statement in the manner I did. I've always been angry at Google for distorting the definition of open for users due to them marketing something other than the reality (marketing pure open while practicing a definition of open not that different from Apple with Mac OS, which we don't consider open).

Yeah, I've always been annoyed with Google for that. Maybe some of the truly open OSes like FirefoxOS and Ubuntu will remedy that.

so much being "open" then

When was Android actually open? The OS is useless unless you have apps and you can't get Android apps unless you are in bed with Google. You can't contribute to Android unless you are in bed with Google.

Android has never been Open. This has always been nothing more than a marketing line from Google. This isn't the only time Google has crafted contracts that remove all the "open" features of Android from an OEM. They have always used their Google branded apps to tie the hands of their OEM partners. What I find the most comical about all of this is Google uses this pressure to twist OEM arms when it comes to what devices they release, but they never use it to ensure end users get updates all the while claiming they care about users and updates, among other things.

These contracts came to light in the trial between Google and Skyhook from before Motorola was purchased by Google. Google banned the use of Skyhook WiFi based AGPS system because it wouldn't allow Google to get user WiFi data.

http://searchenginel...-headache-77870

this.

Listen..let's make something clear.. Android IS open.. you can go take it and make ANYTHING you want with it. Amazon is proof. So let's stop with this Android is not open malarky.

The reason Google is against this is because the other OS IS using Android and Acer is trying to use that OS and continue using Google's services. That's not gonna happen.

Google's services ARE NOT open. So when OHA was created every member agreed not to branch out with alternate Android OSs and use the official builds because that's the only way it will guarantee a healthy and compatible ecosystem.

Acer can abandon OHA and go use Android and build whatever they want. The downside for them will be no access to official Google services that are supported on Android.

Google made their services that give value. You can use Android and do whatever the hell you want. Amazon did it and nobody is against them but even Amazon can't take Android and branch it out. The license specifically stands that you can use Android for whatever you want but you have to build on top of the foundation making Android apps compatible with your eco-system. If you don't comply you can't use the code.

This seems like a very reasonable thing. It's in the interest of consumers.

bull****. This is not about consumers. This is about Google.

When was Android actually open? The OS is useless unless you have apps and you can't get Android apps unless you are in bed with Google. You can't contribute to Android unless you are in bed with Google.

If Android wasn't open (to some extent, that is, the AOSP) you wouldn't have stuff like CyanogenMod.

Still, while AOSP is open the whole Android product with Google's services is not, that much is clear. Whether AOSP alone is enough to build your product is another issue, and that's certainly hard if you are buiding smartphones or tablets (although you could try to pull an Amazon or make an arrangement with Amazon to use their services).

If your product was a media center you could do with AOSP and alternative markets like Amazon or GetJar for extra apps, though.

If Android wasn't open (to some extent, that is, the AOSP) you wouldn't have stuff like CyanogenMod.

Still, while AOSP is open the whole Android product with Google's services is not, that much is clear. Whether AOSP alone is enough to build your product is another issue, and that's certainly hard if you are buiding smartphones or tablets (although you could try to pull an Amazon or make an arrangement with Amazon to use their services).

If your product was a media center you could do with AOSP and alternative markets like Amazon or GetJar for extra apps, though.

If Android was really open, Google couldn't have pulled the Honeycomb stunt (for whatever reason). I don't really follow its development but AFAIK there are no outside developers contributing to it (beyond obviously the Linux part of it). It is merely open source to some extent.

If Android was really open, Google couldn't have pulled the Honeycomb stunt (for whatever reason). I don't really follow its development but AFAIK there are no outside developers contributing to it (beyond obviously the Linux part of it). It is merely open source to some extent.

When it comes to source code, being open doesn't necessarily imply that it's also community developed.

It's basically an OSS project with a closed development process, which still falls under OSS even though it's not that usual. What they did with Honeycomb could be done with any other OSS project: you are only required to distribute the source to the recipients of the binaries, which they did.

When it comes to source code, being open doesn't necessarily imply that it's also community developed.

It's basically an OSS project with a closed development process, which still falls under OSS even though it's not that usual. What they did with Honeycomb could be done with any other OSS project: you are only required to distribute the source to the recipients of the binaries, which they did.

It doesn't necessarily mean but that is the general perception* when something is termed open. Google likes to play the Open card with Android and lot of their stuff and never gets called out on it.

The bold part of your post, I am surprised to read that. My impression is that GPL requires you to always release whatever you do (although I think the whole Android is not covered by GPL).

It doesn't necessarily mean but that is the general perception* when something is termed open. Google likes to play the Open card with Android and lot of their stuff and never gets called out on it.

It's the general perception because usually the most obvious benefit of an OSS project is getting contributions, but you might not want contributions and/or third parties questioning your decisions during the development stages.

The bold part of your post, I am surprised to read that. My impression is that GPL requires you to always release whatever you do (although I think the whole Android is not covered by GPL).

Only to the recipients of the software (and hence only if you distribute the software, if I modify a GPL application for my own personal use I'm not required to release anything for anyone).

If, say, I got a contract to develop some OS software for X company, I'd only be required to give the source to X since they'd be the only ones getting the binaries.

You mean the total 15 lines?

They could of gone the Amazon route, took android, did there own independent marketplace and launch it.

yes but Acer wanted the both worlds and being a member of OHA that's not possible; the question in here is that Aliyun is a ripoff of Android (even the Marketplace is) so if Acer released that phone it could be in hot waters.

yes but Acer wanted the both worlds and being a member of OHA that's not possible; the question in here is that Aliyun is a ripoff of Android (even the Marketplace is) so if Acer released that phone it could be in hot waters.

I think they're getting frustrated that they can't release an proper "Google Experience" device in China, so it precipitated them considering this clone. However, the piracy issue on its market is a serious concern, one that Acer needs to keep the hell away from, big time.

If Google sorted out the Chinese market so Google Experience devices can be sold there, this problem wouldn't be near so bad.

Update 2: Andy Rubin minced fewer words in his posting on Google+, where he flatly claims that Aliyun "incorporates the Android runtime and was apparently derived from Android."

Didn't seem to be a issue for Google when they was borrowing from Java

Don't you mean were and not was? adding was instead of were makes your sentence almost non comprehensible.

Anyways, Java is just a programming language and a good one i might add imo.

I think they're getting frustrated that they can't release an proper "Google Experience" device in China, so it precipitated them considering this clone. However, the piracy issue on its market is a serious concern, one that Acer needs to keep the hell away from, big time.

If Google sorted out the Chinese market so Google Experience devices can be sold there, this problem wouldn't be near so bad.

Piracy will always be an issue.

Piracy will always be an issue.

Yes, but this "new" OS is built on it from the very start. It's own built in market carries mostly pirated and illegally modified versions of commercial software without the publishers knowledge. Read the article I posted.

This topic is now closed to further replies.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      593
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!