http://www.pcmag.com/article2/0,2817,2380756,00.asp
Google on Tuesday announced that the full SDK for Android 3.0 is now available to developers.
"The APIs are final, and you can now develop apps targeting this new platform and publish them to Android Market," Xavier Ducrohet, Android SDK tech lead, wrote in a blog post.
Along with the new platform, Google said it is releasing updates to its SDK Tools (r10) and ADT Plugin for Eclipse (10.0.0).
In the ADT Plugin, Google had added: new palette with categories and rendering previews; more accurate rendering of layouts that will more faithfully reflect how layouts look on devices; selection-sensitive action bars to manipulate View properties; zoom improvements, including fit to view, persistent scale, and keyboard access; and improved support for "merge" layouts and layouts with gesture overlays.
Google also added Traceview integration for easier profiling from ADT and tools for using the Renderscript graphics engine.
More details are available on the Android 3.0 Platform Highlights page.
Google released a preview of the Android 3.0 "Honeycomb" SDK in late January to allow developers to start testing their apps on tablets. Earlier this month, Google also held an event in San Francisco to more formally unveil Honeycomb. It also unveiled the Android Market Web Store, a Web-based version of the Android app store.
The first tablet running Android 3.0 Honeycomb, the Motorola Xoom, hits stores on Thursday.
uff
noooooo now that i need to send my folio to the assistance for the soundboard problem.... please you can wait sometime for build a release 3.0 for the folio??? ahahahahhaha
i confirm that on the android sdk is now accessible the platform 3.0 api 11, my best notice of the 2011 for now!
moved to general as not android development
Yeah! I've just readen this good news too on a news website!! So, does this mean dev's can start working on a 3.0 update for our folio's?
How long to get honeycomb on Folio?
I'm starting the count down right now
Now for serious, 2.2 is fine for me as long compatible apps keep coming to it. It will be needed a few months before We see honeycomb in full glory. I guess that there's a huge pression to get it right this time.
need this!
I realy need this for my Folio!
please...port it!
tomasino.blaha said:
I realy need this for my Folio!
please...port it!
Click to expand...
Click to collapse
theres only one person who can do that at the moment and that is dext3r
What google has released is SDK, software development kit.
This is tools to build Honeycomb application, not Honeycomb itself.
For the Folio to get Honeycomb we will need a rom from a machine similar enough.
No such thing exists (yet).
Yes of course! SDK is only for software development, but is one first step toward a possible mod. Some tegra 2 tablets with similiar hardware specs will be launched this week, I don't think Xoom from motorola is that similiar.
One other option is to have source code and a set of compile options, and them try to build it from scratch.
I guess the main obstacle could be the drivers and hardware support. Must of these will have to be built from ground up and will take a considerable amount of time. I guess that it's feasible but to get a rom as polished as 1.4 we will still have to wait...
It's still good news though !
Thanks for explanation,now i'm so sedder but i believe somebody can do it
but how said "bastospn",this is first step to build new rom
well guys...
but any chance to have honeycomb working on folio?
whats the problem to port it to our deveces?
i got nexus one also and im trying the honeycomb release roight now....
davidebeatrice said:
well guys...
but any chance to have honeycomb working on folio?
whats the problem to port it to our deveces?
i got nexus one also and im trying the honeycomb release roight now....
Click to expand...
Click to collapse
1st, you need a full source from Google, not just a SDK like someone has already pointed out. 2nd, porting is not an easy job...especially when the target device has a bunch of difference hardware components than the reference device. If there's no compatible drivers, sometimes you need to spend days/weeks of writing drivers/ debugging...
What you have on your Nexus one I believe is just an emulator port and thus extremely slow
xitrumch said:
1st, you need a full source from Google, not just a SDK like someone has already pointed out. 2nd, porting is not an easy job...especially when the target device has a bunch of difference hardware components than the reference device. If there's no compatible drivers, sometimes you need to spend days/weeks of writing drivers/ debugging...
What you have on your Nexus one I believe is just an emulator port and thus extremely slow
Click to expand...
Click to collapse
no,
on my n1 ive a full sdk porting really fast and stable, obviously with no phone connection at all...
resolution is the native one, so characters are really small on n1...but folio screen is wider...
look here: http://forum.xda-developers.com/showthread.php?t=961994
so guys...how does it look?
i'm so excited and waiting for it!
is possilbe to do it?
now i installed FolioMod but.that isn't Honeycomb!
Hello all,
I'm currently trying to develop an Android app as part of my final year of university (I would have posted this is development but I'm too new ) and I'm using my Dell Streak as the main testing device as, lets be honest, it rocks and I'm too poor to get another device. I'm running DJ_Steves Streakdroid 1.9.1 custom rom as the Android platform.
The app itself requires the usage of some sort of mapping API, and I would prefer to use the Google maps API as it has all the features I require and with it being built into a significant number of Android devices it would reach the widest range of devices whilst retaining the necessary simplicity due to being built into the SDK and ADT plugin. However when attempting to run a basic app prototype that displays a map centred on the last recorded GPS location, I run into a classDefNotFoundError every time I try to run it, indicating that the API does not exist on the device. This leads me on to a selection of questions I'd like to ask if anyone knows the answers to:
Do any of the Streakdroid versions have the maps API?
Do any other custom roms have the maps API?
Is the maps API included in the stock Froyo release?
Hi,
Is there any chance for an Android Wear custom ROM later? Or the HW is not enough strong for Android Wear?
Thanks
Never say never, but I think no, becouse Android Wear is a Google operating system and Samsung Gear Fit doesn't have traditional operating system. It use RTOS (Real Time Operating System) and have very limited size of its own memory.
What we shall wait is Gear Fit SDK. It may give endless new ideas for new apps; stored mainly on your phone and viewed on your Gear Fit screens as notifications.
No, Gear Fit will never have Android Wear.
Yes, it works on Pie too! ™
Requirements
Android 4.0 or higher.
Xposed
A recent version of Google Play Services.
Any ROM (the module hooks into Google Play Services).
You do not have installed and do not want to install Google Play Games.
Description
I don't have Google Play Games installed, and I don't want to install it. Yet more and more games beg for it.
This module makes the begging stop. You won't see a prompt for Google Play Games anymore.
Note that this module has no UI. Just enable and disable it as needed.
Note that if you are an XPrivacyLua user, there is a XPrivacyLua hook named GMS.NoPlayGames that implements the same functionality as this module. You can download the hook directly from XPrivacyLua Pro's hook download pane. If you use the XPrivacyLua hook, do NOT use this module at the same time.
EdXposed users: Note that Google Play Services (com.google.android.gms) must be whitelisted (or not blacklisted) for this module to work. Doing so will enable Xposed for Google Play Services and will prevent passing SafetyNet.
Google Play Services Versions
Works with 8.7.03 (8703436, 8703438), reported by @Fif_
Works with 9.0.81 (9081438), reported by @jaydee77
Works with 20.16.15, reported by @Fif_.
Tested with:
Android 6.0 Marshmallow (omniROM)
Android 7.1 Nougat (OxygenOS, LineageOS)
Android 8.1 Oreo (LineageOS)
Android 9 Pie (OxygenOS)
Issues:
The module is not working on KitKat and earlier. Reported by @mendelgordon and @Ksawery. Version 0.4 and later may now work on KK and earlier, please report success or failure
Changelog
Release 1.1, on May 27, 2020.
This is a minor update for GMS 20 compatibility.
Now blocks Play Games dialogs with GMS version 20.15.16 and later.
Still compatible all other GMS versions.
Android Target SDK updated to 29 (Pie).
Updated build tools.
Release 1.0, on June 4, 2017.
This is a minor update for GMS 11 compatibility.
Now blocks Play Games dialogs with GMS version 11.
Still compatible with GMS version 10 and lower.
Release 0.4, on May 6, 2016.
If this module didn't work for you in the past, please try it again, its core has changed and it will probably work now. That includes pre-Lollipop ROMS and arm64 platforms.
Changed the way No Play Games hooks into GMS, increasing cross-GMS compatibility.
Minor logging changes.
Release 0.3, on April 3, 2016.
Recompiled against Xposed v81.
Release 0.2, on March 9, 2016.
Shrank the APK size to a more reasonable 83kB by nuking the appcompat cruft from Android Studio. RLY.
Release 0.1, on March 9, 2016.
Initial release
Download
https://dl-xda.xposed.info/modules/com.fifsource.android.noplaygames_v7_b3827a.apk (on Xposed Module Repository)
XDA:DevDB Information
No Play Games, Xposed for all devices (see above for details)
Contributors
Fif_
Xposed Package Name: com.fifsource.android.noplaygames
Version Information
Status: Stable
Current Stable Version: 1.1
Stable Release Date: 2020-05-27
Current Beta Version: 1.1
Beta Release Date: 2020-05-27
Created 2016-03-09
Last Updated 2020-05-28
Then dev how can we access login in the game
terroboy k9 said:
Then dev how can we access login in the game
Click to expand...
Click to collapse
That's the whole point: you don't.
This module is for people that do not want the Play Games features.
All the games I know of will run happily without Play Games installed. The module just removes the nagging.
I've clarified the description, thanks for the feedback.
Fif_ said:
That's the whole point: you don't.
This module is for people that do not want the Play Games features.
All the games I know of will run happily without Play Games installed. The module just removes the nagging.
I've clarified the description, thanks for the feedback.
Click to expand...
Click to collapse
Can't it be bypassed ? So we still can log in.
I like this module as indeed some games constantly force you to login but I do play some games which don't nag me to but I play the after login, so can it be possible to make exceptions for some or not possible at all?
@Fif_
awesome mod, works on HTC One M9 (MM)
I was looking for module like this! Thank you!
But.... Do you think you could add possibility to choose wich game can/cannot login g-play?
Thanks in advance!
x_one said:
I was looking for module like this! Thank you!
But.... Do you think you could add possibility to choose wich game can/cannot login g-play?
Thanks in advance!
Click to expand...
Click to collapse
I'm not sure how to do this.
I currently just block the Install/Upgrade dialog (because I'm tired of being asked to install it when I don't want to).
If you have Google Play Games installed, then it's not being interfered with beyond blocking that dialog. Login into Play Games will still work as usually.
Plus technically, I'm not sure how I could extract the game that invoked Google Play Games from the method I hook into.
Sorry, it doesn't sound like it's going to work, but I'm happy to hear any further input you may have.
exodius48 said:
Can't it be bypassed ? So we still can log in.
Click to expand...
Click to collapse
You will still be able to login into Google Play Games from your game, if you have Play Games installed.
Only the install/upgrade dialog is suppressed.
nicesoni_ash said:
I like this module as indeed some games constantly force you to login but I do play some games which don't nag me to but I play the after login, so can it be possible to make exceptions for some or not possible at all?
Click to expand...
Click to collapse
I already replied to a very similar question, but for your benefit:
You will still be able to login into Google Play Games from your game, if you have Play Games installed.
Only the install/upgrade dialog is suppressed.
Then my idea isn't important. I'm happy without nag screen + g-play functionality.
*** Edit
Is not working right way
Nag screen don't appear but game autologin to cloud using default account. I thought that it will block login to cloud if i don't want login.
Tested on Xperia Z3 Compact LP 5.1.1 and No Play Games v0.2
Didn't work for me. I have the Google play services version that you said works. Attached is my xposed log.
x_one said:
Is not working right way
Nag screen don't appear but game autologin to cloud using default account. I thought that it will block login to cloud if i don't want login.
Tested on Xperia Z3 Compact LP 5.1.1 and No Play Games v0.2
Click to expand...
Click to collapse
Sorry to hear it didn't work for you.
Were you logged in for that particular game before you installed and activated No Play Games?
Can you log out from Play Games for that game?
Once logged out, does No Play Games work?
I'm only targeting the "Install Play Games" nag dialog in the module, and did not investigate what would happen in case you had Play Games installed...
mendelgordon said:
Didn't work for me. I have the Google play services version that you said works. Attached is my xposed log.
Click to expand...
Click to collapse
Sorry to hear that it's not working for you.
From the log files, it looks like you have GMS v8703030.
I've only claimed to support v8703436.
Is there any chance you can upgrade GMS?
If you cannot or don't want to upgrade GMS, I'll need a copy of your PrebuildGmsCore.apk.
It generally sits under /system/priv-app/PrebuiltGmsCore/PrebuiltGmsCore.apk.
Didn't work for me. Nag screen still appears
Tested on: Huawei Y635 with KK 4.4.4, Google Play Services 8.7.03 (2645110-034) and No Play Games v0.3.
Ksawery said:
Didn't work for me. Nag screen still appears
Tested on: Huawei Y635 with KK 4.4.4, Google Play Services 8.7.03 (2645110-034) and No Play Games v0.3.
Click to expand...
Click to collapse
Would you mind sending the Xposed log?
I think in my case it's because I have dissabled the resource hooks to work with EMUI.
Ksawery said:
I think in my case it's because I have dissabled the resource hooks to work with EMUI.
Click to expand...
Click to collapse
No, this is not the problem, this module does not use any resource hooks.
You have an older Play Services than what I've test with, from your log you have v 8703034, I only claim to support 8703436 and 8703438.
I have another report of v 8703030 not working (see post #12).
For me to fix that issue, I'd need a copy of your PrebuiltGmsCore.apk.
You should be able to find this file under /system/priv-app/PrebuiltGmsCore/PrebuiltGmsCore.apk.
On a separate note, your Xposed log file contains lots of other errors that are not caused by NoPlayGames.
The AppSettings module seems not to be very happy either...
Fif_ said:
You have an older Play Services than what I've test with, from your log you have v 8703034, I only claim to support 8703436 and 8703438.
I have another report of v 8703030 not working (see post #12).
Click to expand...
Click to collapse
Please note that all these versions (8703034, 8703436, 8703438 and 8703030) are the same (Google Play services 8.7.03). The diferences between all of these versions are the android version and the screen DPI:
Code:
To figure out the right version of Google Play services for your Android device, download Play Services info or go to Settings -> Apps -> Google Play services, and look at the last 3 numbers in the parentheses. You'll see something like -XYZ where:
* X defines Android version:
0 for Android <5.0
2 for Android 5.0 and 5.1 starting with Play Services v8
4 for Android 5.0 and 5.1 before Play Services v8, Android >= 6.0 after
7 for Android 5.0
8 for Android TV
* Y defines CPU architecture:
1 for armeabi
3 for armeabi-v7a
4 for arm64-v8a
7 for x86
* Z defines DPI:
0 for universal
2 for 160
4 for 240
6 for 320
8 for 480
Notes:
It seems that -7YZ builds became -4YZ with Google Play services v6.5. If you were on -7YZ before, you should now install -4YZ.
It seems that -4YZ builds got split into -2YZ for Lollipop and -4YZ for Marshmallow with Google Play services v8. If you were on -4YZ before, you should now install -2YZ in Lollipop and -4YZ in Marshmallow.
Looks like -8YZ builds are for Android TV.
Examples:
-014 for Android <5.0 armeabi CPU 240 DPI device
-438 for Android 6.0+ armeabi-v7a CPU 480 DPI device
-876 for Android TV x86 CPU 320 DPI device
Fif_ said:
On a separate note, your Xposed log file contains lots of other errors that are not caused by NoPlayGames.
The AppSettings module seems not to be very happy either...
Click to expand...
Click to collapse
I know. EMUI is not friendly with Xposed and his modules...
Ksawery said:
Please note that all these versions (8703034, 8703436, 8703438 and 8703030) are the same (Google Play services 8.7.03). The diferences between all of these versions are the android version and the screen DPI:
Code:
To figure out the right version of Google Play services for your Android device, download Play Services info or go to Settings -> Apps -> Google Play services, and look at the last 3 numbers in the parentheses. You'll see something like -XYZ where:
* X defines Android version:
0 for Android <5.0
2 for Android 5.0 and 5.1 starting with Play Services v8
4 for Android 5.0 and 5.1 before Play Services v8, Android >= 6.0 after
7 for Android 5.0
8 for Android TV
* Y defines CPU architecture:
1 for armeabi
3 for armeabi-v7a
4 for arm64-v8a
7 for x86
* Z defines DPI:
0 for universal
2 for 160
4 for 240
6 for 320
8 for 480
Notes:
It seems that -7YZ builds became -4YZ with Google Play services v6.5. If you were on -7YZ before, you should now install -4YZ.
It seems that -4YZ builds got split into -2YZ for Lollipop and -4YZ for Marshmallow with Google Play services v8. If you were on -4YZ before, you should now install -2YZ in Lollipop and -4YZ in Marshmallow.
Looks like -8YZ builds are for Android TV.
Examples:
-014 for Android <5.0 armeabi CPU 240 DPI device
-438 for Android 6.0+ armeabi-v7a CPU 480 DPI device
-876 for Android TV x86 CPU 320 DPI device
I know. EMUI is not friendly with Xposed and his modules...
Click to expand...
Click to collapse
Thanks, that was helpful.
Unfortunately, the KitKat and earlier versions of GMS (so the -0XX versions of GMS) have a very different way of invoking Play Games.
I found a version 8.7.01-0XX version of GMS of the interwebs, and the way to call Play Games is very different. There is no com.google.android.gms.games package, and I cannot find any trace of it anywhere.
So it sounds like this module is only compatible with LP and MM. KK and earlier users are left out in the cold.
I'll update the module description.
If we want to add KK and earlier compatibility, I may need help understanding how apps are calling this dialog.