Jump to content

Music Player from Honeycomb - APK


Recommended Posts

Guest chocman
Posted

This makes my phone reboot when i try to install using japanese jellyfish.

Guest rayraven
Posted

@zakdablack

I replaced it with Root Explorer, but i guess you could adb it.

@chocman

I didnt get reboots, but the app just force closes all the time for me on Jap. Jellyfish

Guest fishb00n
Posted

short review:

i don't need all those features. player pro does a good job already.

Guest Victor von Zeppelin
Posted

Errm, I managed to push it with ADB... it's in my system/app...but does nothing :(

Guest fonix232
Posted

I'm telling you, this one will never work on our Blade, as the main player library (libjumper.so) is only included as an ARMv7 compilation. This app will ONLY work on ARMv7 based phones (like the Galaxy S and Nexus S) until someone gets the ARMv6 version of libjumper.

Guest Victor von Zeppelin
Posted
I'm telling you, this one will never work on our Blade, as the main player library (libjumper.so) is only included as an ARMv7 compilation. This app will ONLY work on ARMv7 based phones (like the Galaxy S and Nexus S) until someone gets the ARMv6 version of libjumper.

Ah makes sense. But also... We didn't know that. It hasn't been posted here before. So...well...news to us!

Guest fonix232
Posted
Ah makes sense. But also... We didn't know that. It hasn't been posted here before. So...well...news to us!

Checking the APK's lib folder will tell you everything :(

If it has armeabi folder, then it is for our phone, if it has only armeabiv7, then it isn't compatible :S

Posted
Ah makes sense. But also... We didn't know that. It hasn't been posted here before. So...well...news to us!

really..so then it come for other phone then??

Guest fonix232
Posted
really..so then it come for other phone then??

Yep, I guess it is from a Nexus S (or similar device).

Guest Victor von Zeppelin
Posted
Yep, I guess it is from a Nexus S (or similar device).

It start raising some scary questions however...like, why go to the effort of developing an ARMv7 specific edition, when the tools are there to make it universally compatible. Does this mean that 2.3 may be the last version compatible with v6? Does that effectively end fragmentation by phasing out all the non-compatible devices.

Am i just creating unfounded hysterics? Probably, yes. I really don't know. But it is a scary thought, when all's said and done

Guest fonix232
Posted
It start raising some scary questions however...like, why go to the effort of developing an ARMv7 specific edition, when the tools are there to make it universally compatible. Does this mean that 2.3 may be the last version compatible with v6? Does that effectively end fragmentation by phasing out all the non-compatible devices.

Am i just creating unfounded hysterics? Probably, yes. I really don't know. But it is a scary thought, when all's said and done

Look. This APK was created only for the given device to test honeycomb. What, in this case, runs on an ARMv7 device. And why stuff every version into it when you know that only one build will be done for only one device? It is like, making a HTC Sense app's libraries to run on any phone while they know that the given app will only and only run on the Desire HD or something new device. Simply unnecessary.

But as soon as a bit of sources come out, we will get our build :( We only need libjumper's source!

Guest Victor von Zeppelin
Posted
Look. This APK was created only for the given device to test honeycomb. What, in this case, runs on an ARMv7 device. And why stuff every version into it when you know that only one build will be done for only one device? It is like, making a HTC Sense app's libraries to run on any phone while they know that the given app will only and only run on the Desire HD or something new device. Simply unnecessary.

But as soon as a bit of sources come out, we will get our build :( We only need libjumper's source!

Ok, ok. I fully believe you, it was just a hypothetical. And anywau, it's still slightly wierd...cos it still means they'll have to port it back and forth. but yes, I understand, if that's how google does it, then so it gets done.

Guest fonix232
Posted
Ok, ok. I fully believe you, it was just a hypothetical. And anywau, it's still slightly wierd...cos it still means they'll have to port it back and forth. but yes, I understand, if that's how google does it, then so it gets done.

They do not have to port, as if they have the source, a fast compile of the library (what, by looking at the size, even on my computer, wouldn't take longer than 10 minutes), repacking the APK, and done :(

Guest Azurren
Posted
It start raising some scary questions however...like, why go to the effort of developing an ARMv7 specific edition, when the tools are there to make it universally compatible. Does this mean that 2.3 may be the last version compatible with v6? Does that effectively end fragmentation by phasing out all the non-compatible devices.

Am i just creating unfounded hysterics? Probably, yes. I really don't know. But it is a scary thought, when all's said and done

We've known that for a while.. Before the SF even came out :(

Honeycomb is designed with tablets in mind and to look goooooooooooooood (Take Vista / Windows 7 aero for example) the SF may be able to run a stripped down version but quite frankly we already know ZTE isn't going to support this device to 3.0

Guest Victor von Zeppelin
Posted
We've known that for a while.. Before the SF even came out :(

Honeycomb is designed with tablets in mind and to look goooooooooooooood (Take Vista / Windows 7 aero for example) the SF may be able to run a stripped down version but quite frankly we already know ZTE isn't going to support this device to 3.0

That's probably true, It's obviously not the most well supported device, bit it also leaves out some other more well known devices, too. Ah well, thanks for clearing this up guys. And the recompiling makes sense, I even knew that, yet I didn't add proprietor knowledge and android together

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.