So someone I know surprised me today by saying he's thinking of purchasing the Hero. See, the thing is that he's not the most tech savvy person in the world, and he admitted that he had hoped I would offer him help in using it and generally improve its usability.
Problem is that I'm a Windows Mobile guy. I really don't know anything more about Android than that it's Google's mobile OS. That's it.
So I was hoping some people here could answer the question I had of whether Android apps work across builds? For example, do the apps made for the HTC Dream work on the Hero?
As of currently, I know Google is making a hell of a lot of builds (Original, Cupcake, Donut, Eclair, and so on), and they seem to be making it at a hyperpace. I also imagine that this might continue for quite a while, so this is an important question to me.
Thank you to all for reading!
Currently all Android phones run the same OS and alle apps works cross-phones. There has been some conflict with apps running on the Hero because of the Sense UI but this can be fixed by turning Sense of or use an application called Bar control wich allows for use of the original UI with ease.
You should tell your friend not to worry, Android is pretty easy and basic in general use.
Dont take my word for gospel but this is my perspective and my experience as a Hero user. I love it and your friend is gonna love it to.
R. Duke, thank you for your answer and reassurance.
I had not realize that all of the Android phones were currently using the same build (I thought the Dream was using the original Android build and Hero was using the newer Cupcake), so I'm glad to hear there will be complete app compatibility.
8525Smart said:
I had not realize that all of the Android phones were currently using the same build (I thought the Dream was using the original Android build and Hero was using the newer Cupcake), so I'm glad to hear there will be complete app compatibility.
Click to expand...
Click to collapse
Most Dreams would have either received an OTA update to 1.5 (Cupcake) or its owners have likely rooted their devices and applied a custom rom, but again these are all likely to be based on Cupcake.
Regards,
Dave
R.Duke said:
Currently all Android phones run the same OS and alle apps works cross-phones. There has been some conflict with apps running on the Hero because of the Sense UI but this can be fixed by turning Sense of or use an application called Bar control wich allows for use of the original UI with ease.
You should tell your friend not to worry, Android is pretty easy and basic in general use.
Dont take my word for gospel but this is my perspective and my experience as a Hero user. I love it and your friend is gonna love it to.
Click to expand...
Click to collapse
I'm planning on getting the Sprint HTC Hero in October. Do you know of any conflicts with the following applications:
Astrid
PDANet
Where
Evernote(Web version)
Documents To Go
Sprite Backup
My Backup Pro
Last.fm
GPhone Manager Pro
Astro File Manger
AndExplorer
TasKiller
ReedR News Reader
Flixster
I doubt that any one can tell you definitively as the phone is not out, and even then I doubt someone is going to download and test such a specific list of apps. However, I moved from a G1 to a Hero, and not found a single compatibility problem yet. When the firmware on the G1 went to Cupcake, some apps did break, but in general they were fixed by their devs very quickly.
Regards,
Dave
Well... there are actually some difference between the HTC Dream and all the other Android phones currently; the Dream have a physical keyboard. Imagine a game that uses the physical keyboard running on a phone with only the virtual keyboard (ScummVM to name one such app). How the hell are you supposed to use a function mapped to the "U" button without a keyboard?
The game Cestos for example have a chat function. The players can chat with each other during matches. Those with a Dream can easily chat while those witrh non-physical keyboards will have to press Menu and then press up the keyboard to start typing (it works but it isn't fluid).
Hey guys, so me and my best friend bought Nook Tablets yesterday after seeing all the cool things that the rooted Color could do. Weve been playing around with it, and with the help of some threads here have gotten Go Launcher and all those basic apps to work like the Amazon Store and file managers and such.
Ive also got a fun game called Zombieville USA working after many attempts. However, for some reason not every apk i try installing works, and i was wondering why that is. For example, i tried for a while to get GameBoid working so i could play GBA games. It would install, then ask me to locate a bios file, which i then downloaded and got it to recognize, but after i open the actual Rom, it would run for a second and then stop.
Other apks give parsing errors, others just dont work. My friend just successfully got Fruit Ninja to work, and thats pretty much been our achievement of the hour. Were new to android and the tablet scene for that matter, but very well acquainted with jailbroken iPod Touches.
tl;dr why cant i get every app to work? Thanks for taking the time to help
Apps that don't work
One of the reasons might be that the Nook Tablet has only a subset of the hardware the typical Android Smartphone has.
No GPS, no accelerometer, etc.
Even some of the hardware it does have, like blue tooth, has no software drivers in the stock Nook operating system.
If the application you are trying to run is dependent on one of those missing resources, it may well fail. Missing libraries might be downloadable.
Your best bet will be applications known to run on the Amazon Fire, which has a comparable feature set. Rest will be try it and see.
Alright that makes sense, thanks. Ill go look around that forum then and see what i can dig up
Am I missing something here? App is not compatible with some of your devices.
Htc Evo- check
Transformer Tablet- no check
I need to understand the developer side of this coin. I have been trying to persuade Jawbone to update their android app "Jawbone Companion" to support my tablet. I don't know, but I assume their would be a publisher option in Google Play to add or delete supported devices so that they cannot be installed on those from the Play store. For example, I had to go to the website to find the app because search shows no results on the tablet.
It's a bluetooth headset. It supports 2.1+edr. App supported on Android OS 4.0, OS 2.3 and select OS 2.2 phones. Transformer tf300 has bluetooth. It supports 3.0+edr. It has ICS and is certainly more capable than a 2.2 phone.
Sooo the only difference I see from this side is a bigger screen. I have emailed at least 3 app makers that I use frequently and they just keep saying it's not tablet supported. So do they just have to add devices to some file that cross checks with Google Play or is the code for my tablet so drastically different that they would have to write a whole new app for tablets?
A technical explanation link of the whole developer process regarding this would be nice.
Update to OP
I have found a method of downloading apk files in the Chrome browser with the APK Downloader extension. It only works with Chrome and I logged into my wife's account, did a quick search for my apps in question, then proceeded to download them to pc by making play think it was sending the apk to my wife's "supported" phone. Then I manually transferred the apks to my "unsupported" tablet where they are now running fine, no errors and no resolution problems.
I have emailed the developers of these apps and they have blown me off by saying that tablets in general are not supported, I emailed them all back telling them their apps were working fine and I didn't understand why they couldn't have allowed me to just download it the easy way.
So are they just being lazy? This just reinforces my reasoning that the phone and tablet are about the same and don't require any more coding than any other app that has problems on certain phones. Seems to me as long as the resolution is high enough and it allows auto rotation that any phone app should run on a tablet, and I don't see why they all keep telling me apps are not supported.
Until then I guess I'll just get my apps the way I described.
yap the apkdownloader would be the way i recomended to you =)
dunno why they dont support tablets
in some cases u dont have to understand them
feel lucky u find a way to make it work
Sorry Guys,
As there doesn't seem to be a whole lot of interest in this project and as no one stepped forward to assist, I'm afraid I'm going to have to abandon this project.
Thanks for following.
___________________________________
OK Guys,
I've run into a bit of a brick wall and need some input from other developers. One of the required APKs from the Q needs a class not included along with my CM9 or Samsung stock roms. The class appears to be called "android.os.UpdateLock". So how do I go about ripping the class out of the Nexus Q rom and injecting it into CM9? Any help would be very appreciated!$!
--------------------------------------------------------------------
Hello All,
The Project
I'm looking to embark on a project to rip out the cloud function from the Q and install it on any android device. I want the cloud streaming of "Google" music and movies without the $300 expense.
The Progress
As of today I have the Nexus Q Deodexed, ripped out several apk files including the Nexus Q "Launcher" HubBroker.apk. I've merged the apks along with the fonts and lib folders of /system and my Galaxy Tab now boots up and runs like a Q. Primary issue outstanding is, the Nexus Q app won't detect the "galaxy Q" through bluetooth. I assume that some functions of the Q are sitting either within the bluetooth libs or that the Nexus Q has a specific bluetooth address that the app needs to see before detection.
My next attempt will be to try taking apart the Nexus Q apk and either changing its bluetooth search criteria or removing it completely. Second to that if anyone out there has a Q and has it setup on their phone, I could use the /data/data folder to extract more information about how it works. Or even better if someone knows what config file is generated on the actual nexus Q when it's set up for that first time.
You can already do that on most android devices. The Q just takes it to the big screen conveniently.
The function of being able to control the Google queue of device A from device B, C, D etc does not exist. Or at least I'm not aware of an app that does that.
I believe that I've tracked down the apk that does it on the nexus but I need to deodex the apps and can't seem to find a tool that works. Anyone out there deodex this rom yet?
JoeJonnyBoy75 said:
Hello All,
The Project
I'm looking to embark on a project to rip out the cloud function from the Q and install it on any android device. I want the cloud streaming of "Google" music and movies without the $300 expense.
The Progress
As of today I have the Nexus Q Deodexed, ripped out several apk files including the Nexus Q "Launcher" HubBroker.apk. I've merged the apks along with the fonts and lib folders of /system and my Galaxy Tab now boots up and runs like a Q. Primary issue outstanding is, the Nexus Q app won't detect the "galaxy Q" through bluetooth. I assume that some functions of the Q are sitting either within the bluetooth libs or that the Nexus Q has a specific bluetooth address that the app needs to see before detection.
My next attempt will be to try taking apart the Nexus Q apk and either changing its bluetooth search criteria or removing it completely. Second to that if anyone out there has a Q and has it setup on their phone, I could use the /data/data folder to extract more information about how it works. Or even better if someone knows what config file is generated on the actual nexus Q when it's set up for that first time.
Click to expand...
Click to collapse
This is a pretty nice project and there is nothing like this happening in Android now, besides the nexus Q. I'd like to see a future port of it to Google TV devices
auad said:
I'd like to see a future port of it to Google TV devices
Click to expand...
Click to collapse
Would love to have this functionality in an APK for me Google TV. Don't see why it wouldn't work, well other then no bluetooth on the Revue....
Still very interested in this thread regardless of GTV. I will be following your progress. Thanks!
.
I'm looking for this as well.
I have 3 spare HTC EVO's, and they all have HDMI out. I would like to be able to just plug them into the TV and use my other phones to control them / play music / etc. Maybe even throw XBMC on them with the ability to control from another phone..
They're slower, and less memory..but it may be doable.
Did anyone dig into this? I'd like this for the latest port of Android for a Raspberry Pi and willing to do some of the (noob)stuff myself.
That would be awesome to use any HDMI equipped phone along with the Nexus Q functionalities. I'm really interested.
I guess the problem with the missing API is that the Nexus Q runs android JB and he tried with a cm9.
Vettekult said:
I guess the problem with the missing API is that the Nexus Q runs android JB and he tried with a cm9.
Click to expand...
Click to collapse
Not true, Q runs ICS...
Let me know...
what I can do to help. If you give me a run down on what you would like me to try as far as pulling files from the q or my connected devices just shoot me a PM and i'll give it a shot. I too would love to add this functionality to my spare devices laying around.
I've been interested in this since day one as well. IT is what has me almost ready to fork out the money on more then one occasion. I have a party coming up and it would be fun to have my N7 as the Jukebox.
The Class issue, I'm not sure about. Here is some info that might get it started.: http://www.itcsolutions.eu/2011/08/...te-a-new-activity-class-with-manifest-editor/
AND:
http://stackoverflow.com/questions/5012004/adding-a-new-class-to-android-project
It looks like it is something created with the app. Since you cut/pasted the apk into system it may not have been installed. But I'm thinking that it is something else. Some where in the android system lib's it is probably installed. Since this was a device dedicated to this purpose, they were able to install it into the system and the app calls it. I'm slowly learning to write apps (very slowly) so I am not sure beyond this, or even about this for that matter.
I do have a question. It looks like you pulled some system apps and put them in your galaxy tablet. I think a better test would be to basically replace all the /system contents of say a N7 (galaxy tab may work) with those from the Q. Then once it works, cut down the files until it stops. Then with a list of what is needed to make it work we could get down to the nitty gritty.
My guess is some more knowledgeable devs, like those who got Google Now working, would have a better idea.
I'd love to see a third party app do the jukebox function, I think a issue is license certificate (DRM) for the multiple users. I don't understand how the user is associated/authenticated for the music. One Question is if a user Ques up music then leaves does it cause that music to not be able to be played or will it still play once it's been que'd? My guess is the app just organizes the music/user who is next then when it's their turn it streams from their device in real time... but I'm really not sure about this.
joeavery2 said:
I've been interested in this since day one as well. IT is what has me almost ready to fork out the money on more then one occasion. I have a party coming up and it would be fun to have my N7 as the Jukebox.
The Class issue, I'm not sure about. Here is some info that might get it started.: http://www.itcsolutions.eu/2011/08/...te-a-new-activity-class-with-manifest-editor/
AND:
http://stackoverflow.com/questions/5012004/adding-a-new-class-to-android-project
It looks like it is something created with the app. Since you cut/pasted the apk into system it may not have been installed. But I'm thinking that it is something else. Some where in the android system lib's it is probably installed. Since this was a device dedicated to this purpose, they were able to install it into the system and the app calls it. I'm slowly learning to write apps (very slowly) so I am not sure beyond this, or even about this for that matter.
I do have a question. It looks like you pulled some system apps and put them in your galaxy tablet. I think a better test would be to basically replace all the /system contents of say a N7 (galaxy tab may work) with those from the Q. Then once it works, cut down the files until it stops. Then with a list of what is needed to make it work we could get down to the nitty gritty.
My guess is some more knowledgeable devs, like those who got Google Now working, would have a better idea.
I'd love to see a third party app do the jukebox function, I think a issue is license certificate (DRM) for the multiple users. I don't understand how the user is associated/authenticated for the music. One Question is if a user Ques up music then leaves does it cause that music to not be able to be played or will it still play once it's been que'd? My guess is the app just organizes the music/user who is next then when it's their turn it streams from their device in real time... but I'm really not sure about this.
Click to expand...
Click to collapse
Ok so here is some more detailed info for those of you still following the project.
HubBroker.apk is the app that is for all intents and purposes the "launcher" for the nexus Q. It will install on the Galaxy Tab and Nexus 7. It takes over your "home" and replaces it with a picture of the Nexus Q and a welcome sign. This app looks to be only the launcher as it doesn't do anything if you tap on it. Also having the app running doesn't allow the Nexus Q app (from your phone) to find the device.
So I assume that that the Q is controlled via bluetooth to get it setup and running. Including configuring the Wifi, network settings, etc. Oddly enough the app does send a request to android system to turn on the bluetooth and changes the bluetooth device name to Nexus Q.... The ... part is a odd string of characters that I assume is used in case you happen to have multiple Nexus Q's.
Now as just having the app doesn't seem to work (Phone finding the Q). I've replaced all the bluetooth libs with the ones from the Q. Still nothing. I've migrated all the other APK files and then I get FCs all over, and still no connection. I haven't tried replacing the whole system yet, but I assume the hardware differences would be to great. The only other piece of the puzzle I have yet to attempt it merging the kernels or at least the init parts of the kernel relating to bluetooth.
If you have any questions though let me know. I've been up and down this thing.
Why don't we just flash the img on an old phone and see if that works?
zAo_ said:
Why don't we just flash the img on an old phone and see if that works?
Click to expand...
Click to collapse
For that to work we'd need to get a device with similar hardware (CPU, Chipset, etc.) Not only that but it would need to have the same MTD setup unless I'm mistaken.
Actually I'm going to give that a try with the nexus 7. I'll let you know what happens, won't be till tonight though.
JoeJonnyBoy75 said:
For that to work we'd need to get a device with similar hardware (CPU, Chipset, etc.) Not only that but it would need to have the same MTD setup unless I'm mistaken.
Actually I'm going to give that a try with the nexus 7. I'll let you know what happens, won't be till tonight though.
Click to expand...
Click to collapse
Cool, Thanks.
Sent from my Galaxy Nexus using xda premium
JoeJonnyBoy75 said:
For that to work we'd need to get a device with similar hardware (CPU, Chipset, etc.) Not only that but it would need to have the same MTD setup unless I'm mistaken.
Actually I'm going to give that a try with the nexus 7. I'll let you know what happens, won't be till tonight though.
Click to expand...
Click to collapse
Galaxy nexus has very similar hardware. Someone should try porting it.
Sent from my Nexus 7 using xda premium
If someone still interested in the project, i'm very interested in it, i have a galaxy nexus (almost same hardware) so we can give it a try, im also a android developer, so if it need to build some apk for it to work, i could give a shot.
Anyway, if there is someone interested just post here and we do all we can to make that work.
edit: Only one problem, as I'm out of USA, i need the q apk to test if it will connect or not. I cant download from play store.
I'm sure there will be so many people interested in it. I just think that not to many of them enter this category on forum
I also need the nexus q image so I can flash it. I tried searching it but didnt find
So, I've switched back to a stock-based version of ICS after bit rot got the better of my CM10 runs. Simply puterformance worsened after the installation of my hundreds of apps and games.
Specifically, I'm running black star. What I know is as follows:
Games that were available--as well as apps that were available....games that I know are compatible with our device-monster Life, to name one--give us the "this app is incompatible with your device" tag on the play store when in a UCLF6 ROM, but are perfectly compatible. The apps and games install and run perfectly when side loaded, or when running a CM or other AOSP based build, and I'm able to install them from the Play Store, and update them without error.
Apps which require a up-to-date client, are virtually impossible o play with consistency, which is a issue worthy of research and fixing on its own. But it also means that I have to find APKs through many sites which may, or may not be unscrupulous.
So...why is this? I've searched the build.prop, looking for a case where the dev might have miss typed something, but I see no errors. I also remember a thread from way-back-when ago, that proved worthy of a sticky....the "change your XXX to XXX and be able to install many more apps and games" deal. I'm not sure, but I think it was a build.prop edit.
Does anyone have/remember a solution to/for this? Being as it is, XDA search either didn't like my truncated searches and methods, or read them too literally. Either way, the results either weren't there, or they were, buried on page three-thousand-two-hundred-and-forty-six-point-three-one-four, or the were invisible results under page 4 of 4 in my more specific searches, which applied a more fine-toothed comb.
I apologize for the format, as I'm typing this on my tablet, from the XDA HD app.
Sent from my Transformer Pad using XDA Premium HD app