Related
Has anyone found or manage to install the "USA TODAY for Tablet" on their NC? I'm trying to track down the APK but can't find it.
https://market.android.com/details?id=com.usatoday.android.tablet.news
Does anyone think updating the build.prop to match the Xoom would allow it to be downloaded from the Market on to a NC?
I use the phone version frequently and would love the tablet version on my NC. I was surprised to not see much mentioned about it on XDA. If anyone has managed to install it can you verify that it works on Honeycomb v4? I'm afraid it's going to use a different sdk version (11, not 10 that the Preview image is).
It wouldn't install because we are using the wrong sdk version but if we could get it to install, I imagine it would work. I don't think it's using anything the preview sdk didn't have. Try asking someone in the xoom forums to post the apk. They'll be the only ones who have it.
Don't forget that Honeycomb has a new UI method which this might use. Pulse now will use this, but you won't see it on anything less than Honeycomb.
Activity Fragments
Honeycomb allows developers to break the Activities of their applications into subcomponents called Fragments, and then combine them in a variety of ways to create a richer, more interactive experience. For the landscape view, Pulse allows you to open the story right there in a new fragment. This allows readers to simultaneously browse and read news stories.
Click to expand...
Click to collapse
I've cross posted in Xoom forum. Maybe someone will post it for me.
http://forum.xda-developers.com/showthread.php?t=978369
khaytsus said:
Don't forget that Honeycomb has a new UI method which this might use. Pulse now will use this, but you won't see it on anything less than Honeycomb.
Click to expand...
Click to collapse
Yeah Fragments look interesting. I don't expect the apps to work on anything below Honeycomb.
RE
Does anybody have the .apk for this? It doesnt show up in the market.
Link for USA Today APK
Here you go... (Attached)
Free version. No piracy involved.
Its one of my favorite news Apps, too. Wonder why they yanked it? When I discovered it was gone, I started keeping back-ups of my Free stuff online for this very reason.
-Kodak
mynookcolor.blogspot.com
The apk worked for me until a little while ago. Now, I get an error that I must download an updated version from the market. Searched in the market and couldnt find it
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
I have a treadmill that uses android tablet to control everything through their app. I was able to gain adb access to the tablet and was wondering where I can start to develop on it. I don't have any kernel sources or rom for it, I just have what is on the device. Is there anything I can do to make the tablet more open to running other applications? For example I would love to get gapps working on it, I was able to copy everything over but the google accounts seems to be disabled so I have to work on that, I would also like to give it root but again dont know how to go about doing this.
Is there much possibilities without the source?
Thanks in advance!
Do you know what model the tablet is? If it's something that's been made specially for the treadmill, you might be out of luck as nobody here will have been able to get their hands on it.
That's not to say you couldn't try using z4root or something similar on it to try to get a root. But if it's a device not supported here, you could be asking for trouble.
Would it be possible to emulate android on an android phone? As in, you could supply an app with an android version (or have the app build it for you) an emulate or run it. Any time it asks for something device specific, it would simply run the request back to the stock OS. Said app would kill all but the essential android processes to improve performance. And to return, it could add a shortcut to the app drawer that would close everything and return to the stock. Using this, could we create universal, or at least wider, distributions of android?
Android in your android so you can android while you android....
I love it! its like watercooling a raspberry pi, because you can.
would be amusing to see
Darkcon said:
Android in your android so you can android while you android....
I love it! its like watercooling a raspberry pi, because you can.
would be amusing to see
Click to expand...
Click to collapse
My main idea was to be able to emulate any android version on any other and have it work as if it was built for that device. So if you had a KitKat device, and there were no Nougat ports available for your device (ahem), you could still run Nougat by emulating it. AKA, universal distributions of android.
But that would be pretty ridiculous. Actually, that could be a new benchmarking method: how many stacked emulators can it handle?
The Original Leppa said:
My main idea was to be able to emulate any android version on any other and have it work as if it was built for that device. So if you had a KitKat device, and there were no Nougat ports available for your device (ahem), you could still run Nougat by emulating it. AKA, universal distributions of android.
But that would be pretty ridiculous. Actually, that could be a new benchmarking method: how many stacked emulators can it handle?
Click to expand...
Click to collapse
I can see a few good reasons you'd want to do that, would require root, and alotta work tho
Darkcon said:
I can see a few good reasons you'd want to do that, would require root, and alotta work tho
Click to expand...
Click to collapse
Well, if no-one supports your phone, what other choice do you have? Also, were this a thing, it would be easier for ROM developers, too, as you could simply update a single package.. As for SU permissions...
SU would only be used for, let's see...
Not Bluetooth (can be accessed by other apps)
Not WiFi
Not calling
Switching off your phone? Holding power would just trigger the default power menu, as some system processes would still run and for the most part the emulator app would be treated as any other.
Killing processes for extra efficiency? Maybe. But it would be optional and likely wouldn't make much of a difference.
The Original Leppa said:
Well, if no-one supports your phone, what other choice do you have? Also, were this a thing, it would be easier for ROM developers, too, as you could simply update a single package.. As for SU permissions...
SU would only be used for, let's see...
Not Bluetooth (can be accessed by other apps)
Not WiFi
Not calling
Switching off your phone? Holding power would just trigger the default power menu, as some system processes would still run and for the most part the emulator app would be treated as any other.
Killing processes for extra efficiency? Maybe. But it would be optional and likely wouldn't make much of a difference.
Click to expand...
Click to collapse
Hmm you've got a point there, this could be used to root a phone thats unrootable effectively, like the android emulated inside an Iphone that some people did in the Iphone 4 days
all depends on implimentation, you'd have to set up the emulator to trigger normal events, like power saving cpu states etc in response to the emulated android os's requirements
I've been thinking.
Let's say you decide to emulate AOSP Nougat. You then installed the official Pixel Launcher. While emulating, it would act as it should, as it would be entirely identical to if you were running Nougat.
Then you close the emulation. You then try to open Pixel Launcher; it's already installed. Would it crash?
Ok then...
Would I just look for adb? Or does adb simply ask something else to emulate?
Hello all,
I love my Touchpad. It got me through College, especially with its completely underrated out-of-the-box office suite. However now it just functions as my Alarm Clock on my bedside table on a Touchstone dock.
When the Amazon Echo Show came out, I think I can saw we all laughed a little. After all, who would would want a tablet with at-a-glance information that they can't carry around with them. Then I realized, that's *exactly* how I use my Touchpad in Exhibition mode. So that got me thinking: how could I transform the hardware I already have and love into a device similar to the Echo Show.
Now, in my mind, there are three ways to do this:
a) Keep webOS and install the somewhat buggy ACL made by Phoenix Communications then install the Alexa handsfree app from the new Fire10 tablet (if I can find the APK). Basing myself on this article: https://techcrunch.com/2017/09/19/a...s-as-a-cheap-echo-show-with-hands-free-alexa/
b) Install Android 6.0+, and make the Google Assistant my Alexa stand-in. I would therefore need to find a way to port-over webOS's Exhibition Mode. Also perhaps the Prelude fonts, as I find Roboto completely unappealing.
c) Install ANY version of Android, and use the same Alexa handsfree app from a), setting it to be constantly on (no screen lock).
Given the Touchpad's aging hardware, any Android ROM would need to be fast, minimal and barebones as I don't intend to use this for much else. It does, however, need to be stable enough to not crash every time I say "Ok Google" or "Alexa".
Any tips on how I should proceed?
Thanks in advance!
Sheik
Sheikboy said:
Hello all,
I love my Touchpad. It got me through College, especially with its completely underrated out-of-the-box office suite. However now it just functions as my Alarm Clock on my bedside table on a Touchstone dock.
When the Amazon Echo Show came out, I think I can saw we all laughed a little. After all, who would would want a tablet with at-a-glance information that they can't carry around with them. Then I realized, that's *exactly* how I use my Touchpad in Exhibition mode. So that got me thinking: how could I transform the hardware I already have and love into a device similar to the Echo Show.
Now, in my mind, there are three ways to do this:
a) Keep webOS and install the somewhat buggy ACL made by Phoenix Communications then install the Alexa handsfree app from the new Fire10 tablet (if I can find the APK). Basing myself on this article: https://techcrunch.com/2017/09/19/a...s-as-a-cheap-echo-show-with-hands-free-alexa/
b) Install Android 6.0+, and make the Google Assistant my Alexa stand-in. I would therefore need to find a way to port-over webOS's Exhibition Mode. Also perhaps the Prelude fonts, as I find Roboto completely unappealing.
c) Install ANY version of Android, and use the same Alexa handsfree app from a), setting it to be constantly on (no screen lock).
Given the Touchpad's aging hardware, any Android ROM would need to be fast, minimal and barebones as I don't intend to use this for much else. It does, however, need to be stable enough to not crash every time I say "Ok Google" or "Alexa".
Any tips on how I should proceed?
Thanks in advance!
Sheik
Click to expand...
Click to collapse
Good idea! I don't use my TouchPad very much anymore away from it being my alarm clock on the Touchstone dock.
I'd definitely try to upgrade it to an Alexa enable tablet if possible.
Will follow this thread with interest!
Sent from my Nexus 5 using Tapatalk
Quick Update:
Option a) does not work. As I suspected, the ACL simply doesn't work well enough to run the Google Assistant and listen for the Ok, Google hotword. I didn't run the Alexa app, but I suspect I'll run into similar issues with it.
This leaves me with options b) and c). I've been installing all sorts of different ROMs for the past day and I keep running into a recurring issue: the WiFi on my tablet doesn't seem to be working. It works fine in webOS, but in every single Android version I've run it gets stuck on "turning WiFi on".
I suspect I have an issue with the ath6kl driver, but I can't find a replacement driver updated for anything past CM9. Can anyone help me? I seem to be having the exact same issue OP is having in this thread: https://forum.xda-developers.com/hp-touchpad/help/wifi-wont-clean-flash-t3612062
Sheikboy said:
Quick Update:
Option a) does not work. As I suspected, the ACL simply doesn't work well enough to run the Google Assistant and listen for the Ok, Google hotword. I didn't run the Alexa app, but I suspect I'll run into similar issues with it.
This leaves me with options b) and c). I've been installing all sorts of different ROMs for the past day and I keep running into a recurring issue: the WiFi on my tablet doesn't seem to be working. It works fine in webOS, but in every single Android version I've run it gets stuck on "turning WiFi on".
I suspect I have an issue with the ath6kl driver, but I can't find a replacement driver updated for anything past CM9. Can anyone help me? I seem to be having the exact same issue OP is having in this thread: https://forum.xda-developers.com/hp-touchpad/help/wifi-wont-clean-flash-t3612062
Click to expand...
Click to collapse
Use the Evervolv ROM.
shumash said:
Use the Evervolv ROM.
Click to expand...
Click to collapse
That's what I'm currently running. I also changed the Kernel to see if that's what was causing the issue but it isn't.
I know for a fact it's not the hardware, because webOS's wifi works perfectly.
Sheikboy said:
That's what I'm currently running. I also changed the Kernel to see if that's what was causing the issue but it isn't.
I know for a fact it's not the hardware, because webOS's wifi works perfectly.
Click to expand...
Click to collapse
All I can tell you is that wifi works perfectly for me (and most others based on the devs-base forum). I have no problem with Google Assistant and "OK, Google" voice recognition.
shumash said:
All I can tell you is that wifi works perfectly for me (and most others based on the devs-base forum). I have no problem with Google Assistant and "OK, Google" voice recognition.
Click to expand...
Click to collapse
Hey !
Thanks to kernel and settings found here, my TouchPad is now usable.
I plan to use it as a control screen for my home automation system, and a echo show / google home like.
You told that the Google Assistant was active, and usable on your TouchPad. Could you please explain me how did you activate it ?
I tried some tricks found on xda dev, but i'm stuck with google now...
Thank you !
thedeathspirit said:
Hey !
Thanks to kernel and settings found here, my TouchPad is now usable.
I plan to use it as a control screen for my home automation system, and a echo show / google home like.
You told that the Google Assistant was active, and usable on your TouchPad. Could you please explain me how did you activate it ?
I tried some tricks found on xda dev, but i'm stuck with google now...
Thank you !
Click to expand...
Click to collapse
Get Assistant - Root works
I still haven't been able to fix the WiFi on my Touchpad. It works perfectly in webOS, but it just remains stuck on "Turning WiFi On" on every single Android ROM iIve tried. I'm not quite sure what to do at this point
shumash said:
Get Assistant - Root works
Click to expand...
Click to collapse
Thank you, I'll try.