Related
Mupen64plus-AE
Hi I just wanted to give some attention to the new open source
n64 emulator for android Mupen64plus-AE which was developed by Paul Lamb.
Its currently in its beta testing phase and it would be awesome if other developers wanted to join in and contribute to the project.
Android market link:
https://market.android.com/developer?pub=Paul+Lamb
Heres a link to the latest build + source code:
http://www.paulscode.com/forum/index.php?board=11.0
[This is currently the only emulator for android with xperia touch pad support]
Here is an overview of the emulator:
Here is a comparison video of banjo-tooie running on n64oid and mupen64plus-ae:
Here is an extra video I made of the xperia play touch pads working with the emulator:
Common questions
The GUI is now finished so most of this information is now irrelevant​
How do I map the gamepad buttons?
First, install and run the "SDL Scancode Finder" linked below. Press the keys you want to map, and write down the Scancodes that are displayed. Then after running Mupen64Plus AE at least once, close the app and edit the file [sdcard]/app-data/paulscode.android.mupen64plus/data/InputAutoCfg.ini. Under the [Keyboard] section, enter the scancodes that you wrote down earlier. For the analog stick, use the scancodes for the left and right buttons for "X Axis", and the scancodes for the up and down buttons for "Y Axis". Finally, save the file and restart the emulator.
SDL Scancode Finder:http://www.paulscode.com/source/AndroidSDLScancodeFinder/ScancodeFinder-debug.apk
Alternatively you use my control config and just paste is over the file. Just replace [sdcard]/app-data/paulscode.android.mupen64plus/data/InputAutoCfg.ini with the custom version of the InputAutoCfg.ini
Heres my config: http://dl.dropbox.com/u/13594612/paulscode/InputAutoCfg.ini (right click and save as)
How do I change games?
Delete or rename the file [sdcard]/app-data/paulscode.android.mupen64plus/roms/mario.n64. Place the ROM you wish to play into that directory, and call it "mario.n64" (it doesn't matter what format the ROM is in, just call it "mario.n64", and the emulator will load it instead of Mario64).
How do I remove the touch control overlay?
Go to [sdcard]/app-data/paulscode.android.mupen64plus/skins and delete everything in there except the folder called touchpads, the touch pads folder it what lets you use the xperia play touch pads.
Click to expand...
Click to collapse
*I take no credit in the creation of this emulator all credit goes to Paul and the people behind the original Mupen64plus source code. Im just a tester nothing more haha*
that'd be cool, but even cooler if N64oid got it
Nhialor said:
that'd be cool, but even cooler if N64oid got it
Click to expand...
Click to collapse
N64oid probably never will though. Adding touch pad support cuts of every android device
that has a firmware lower than 2.3 and thats alot of devices.
With Mupen64plus-ae multiple builds can be made so it doesn't effect other devices.
Thats why I feel so strongly that developers should help support this project,
it means that developers can add whatever they want and can create device specific features.
I would love to see this with touchpad support. Waht do you guess how long will it take?
IE-coRe said:
I would love to see this with touchpad support. Waht do you guess how long will it take?
Click to expand...
Click to collapse
Touch pad support is nearly done, my best guess it will either be finished by tomorrow or in a few days. Also just to clarify I am not the one making this emulator.
This the latest build for non qualcomm devices: http://www.paulscode.com/source/Mupen64Plus-AE/13SEP2011/Mupen64Plus-debug.apk
This is the latest build for qualcomm devices (like the xperia play: http://www.paulscode.com/source/Mupen64Plus-AE/13SEP2011/Mupen64Plus-debug-sortProblem.apk
The xperia play version has very bad graphics at the moment but paul is working on fixing that atm.
You mean Paul as in Paul O'Brien, Modaco's overlord and programmer extraordinaire?
Logseman said:
You mean Paul as in Paul O'Brien, Modaco's overlord and programmer extraordinaire?
Click to expand...
Click to collapse
No the full name of the Paul who is making the emulator is Paul Lamb
Rockin'
Sent from my R800x using xda premium
P.s. I can't wait for this to come to fruition. Finally! A viable way to play Duke Nukem
What are you talking about? Google made it so that multiple versions of the same apk can be uploaded to the market under the same heading, so adding it for our device would therefore NOT rule out other phones, as they could just download the regular version (our version wouldn't be able to be seen by them), also, as a computer science major, it'd be easy to not have this problem if he doesn't want to go down this road, he could do, for arguments sake, if build.prop=="R800i"|"R800x"{control-type="touchpad"}else{control-type="regular"}, or even just a tick box in the option menu...!
therefore avoiding the problem. Obviously it goes a lot deaper than that, but saying that adding support for us would rule out other devices is just not true. It's something else that's stopping him.
Nhialor said:
What are you talking about? Google made it so that multiple versions of the same apk can be uploaded to the market under the same heading, so adding it for our device would therefore NOT rule out other phones, as they could just download the regular version (our version wouldn't be able to be seen by them), also, as a computer science major, it'd be easy to not have this problem if he doesn't want to go down this road, he could do, for arguments sake, if build.prop=="R800i"|"R800x"{control-type="touchpad"}else{control-type="regular"}, or even just a tick box in the option menu...!
therefore avoiding the problem. Obviously it goes a lot deaper than that, but saying that adding support for us would rule out other devices is just not true. It's something else that's stopping him.
Click to expand...
Click to collapse
Well If you actually knew anything about n64oid you would know that its not even on the android market. Its distributed via slideme which does not support uploading of multiple apk's for a single app.
And ive talked to alot of emulator developers and for some reason (Im not entirely sure why) Including touch pad support cuts off support for older versions (lower than 2.3).
bubblegumballon said:
Well If you actually knew anything about n64oid you would know that its not even on the android market. Its distributed via slideme which does not support uploading of multiple apk's for a single app.
And ive talked to alot of emulator developers and for some reason (Im not entirely sure why) Including touch pad support cuts off support for older versions (lower than 2.3).
Click to expand...
Click to collapse
haha ,completly forgot about that, but still, u see my point about the proper implemantation?
EDIT: Wait, I remember something that either Yonghz or Shtruck said something like the classes needed for this are unaccesible for Froyo and before or something, so you may be right. Apologies
Nhialor said:
haha ,completly forgot about that, but still, u see my point about the proper implemantation?
EDIT: Wait, I remember something that either Yonghz or Shtruck said something like the classes needed for this are unaccesible for Froyo and before or something, so you may be right. Apologies
Click to expand...
Click to collapse
No problem and Im sure ive seen Shtruck say something along those lines on the fpsece forums
I would imagine they would be able to add backwards compatibility after adding touch pad support, but that would take extra time - which they may not be willing to give the time.
hairdewx said:
I would imagine they would be able to add backwards compatibility after adding touch pad support, but that would take extra time - which they may not be willing to give the time.
Click to expand...
Click to collapse
Im not sure what you mean by backwards compatibility but in the future arm6 devices will be supported as well.
Also touch pads are in the process of being added, in the newest build the touchpad overlay has been added to the screen and different layouts have been made for different screen sizes (phone, tablet, small screens etc).
bubblegumballon said:
Im not sure what you mean by backwards compatibility but in the future arm6 devices will be supported as well.
Also touch pads are in the process of being added, in the newest build the touchpad overlay has been added to the screen and different layouts have been made for different screen sizes (phone, tablet, small screens etc).
Click to expand...
Click to collapse
I meant having N64oid, FPSE, etc. detect the android version and run version specific code to add touch pad support while avoiding the compatibility issues.
I have done that before in software (I am a software engineer for a living) but it takes a long time to do and adds extra things to support. I certainly would not be motivated enough to do that either
hairdewx said:
I meant having N64oid, FPSE, etc. detect the android version and run version specific code to add touch pad support while avoiding the compatibility issues.
I have done that before in software (I am a software engineer for a living) but it takes a long time to do and adds extra things to support. I certainly would not be motivated enough to do that either
Click to expand...
Click to collapse
Im no emulation programmer but alot of emulator developers have said the same thing that implementing the touch pad controls limits it to 2.3+
Im sure if somebody was brainy enough to create an emulator then they would know how to support more versions if it were possible.
also I would like to point out that Mupen64plus-ae supports arm6, It was already implemented but I forgot to update my post.
bubblegumballon said:
Im no emulation programmer but alot of emulator developers have said the same thing that implementing the touch pad controls limits it to 2.3+
Im sure if somebody was brainy enough to create an emulator then they would know how to support more versions if it were possible.
also I would like to point out that Mupen64plus-ae supports arm6, It was already implemented but I forgot to update my post.
Click to expand...
Click to collapse
Touch pads limit it to 2.3+ because of some of the classes and available system calls it needs are only in 2.3+.
But that doesn't mean it's impossible to make one apk support all android versions, just very impractical implementation-wise and probably not worth it.
hairdewx said:
Touch pads limit it to 2.3+ because of some of the classes and available system calls it needs are only in 2.3+.
But that doesn't mean it's impossible to make one apk support all android versions, just very impractical implementation-wise and probably not worth it.
Click to expand...
Click to collapse
The project is open source so anybody (with the right knowledge) could just go and add touch pad support if they wanted.
Also I would like to point out touch screen controls have now been added but they are still not finished, there are still a few more things to be added like a moving analog stick and lots of optimisations so dont expect it to be perfect just yet.
Mupen64plus-ae now works properly on adreno GPU's (qualcomm chipsets)
It works great on my xperia play! keep in mind that its still not finished yet.
bubblegumballon said:
Mupen64plus-ae now works properly on adreno GPU's (qualcomm chipsets)
It works great on my xperia play! keep in mind that its still not finished yet.
Click to expand...
Click to collapse
did you use the first apk or the "qualcomm" apk?
because Im trying the second apk and its not letting me download the data from paulscode.com...
any help would be appreciated
So I've watched the ICS Motorola Webtop Beta 3.0 video and it may be me but it looks very similar to the Evo Desktop PC in concept and function. Considering that ICS wasn't even available this time last year this would have been the logical progression of the project. I'm not asking for Moto to send me a check but I'm waiting to see how the credits roll out. If the Sun here on Mars has baked my brain then feel free to say so.
Lokifish Marz said:
I'm not asking for Moto to send me a check but I'm waiting to see how the credits roll out.
Click to expand...
Click to collapse
Wow
The check is in the mail.
CCallahan said:
The check is in the mail.
Click to expand...
Click to collapse
So are you going to send it on their behalf?
Actually I've been in contact with Moto since the videos surfaced and am getting the "hot potato" treatment. All I'm looking for is to have a civil dialog with them about it. All I'm getting is being told I need to contact Department A by Department B after just being directly referred to Department B by Department A. I have even gone so far as to include the direct referral and names in my communications. You probably have a good idea as to how well that's working.
The odd thing is that with 200+ views nobody has said I should have my head checked. Is everybody on XDA being nice?
Interesting question, locki. Definitely a fair one. If I understand correctly, from watching the video (I had the volume down - A cold and a headache coming down so I'm trying to minimize the noises). In any case, your version looks to me like phone mirroring with a keyboard and a mouse. Not sure how it's set up (you probably said it in the video). But I don't think the ICS demo is a complete demo. This looks like he just reviewed the phone mirroring version, but didn't do a complete webtop review. Also, webtop on the current system is also pretty limited. From that video, I don't see much difference between the ICS and what we have on our phone, except that this is a proof of concept. In any case, you could say the same thing about a comparable presentation from the webtop experience on the mopho if you only show the the phone window usage. could also say the same thing about your ubuntop if you only show a limited version of the capabilities. I guess my point is I don't think you have a fair comparison at this point. But my head is stuffy and I am on my way to an early bedtime, so maybe I'm missing something...
I replaced the video of webtop 3.0 with one that shows webtop3.0 in use. I also have a copy of the ICS RAZR leak and osh (or anything related to that partition) is nowhere to be found. Neflix is obviously Netflix for tablets. The desktop look of Chrome appears to be a ui switch for the mobile chrome browser. If the ICS leak is anywhere near what the official release is, then the tech/android reports are correct that the new webtop is nothing more than modified tablet mode mirroring.
I'm not saying it's not good work. Had HCL Launcher, Chrome mobile browser and Netflix for tablets been out when I released Evo Desktop you would be hard pressed to tell the difference.
My other concern is if the leak I have and the videos are correct this does not bode well for Webtop becoming a true desktop with ICS like many had hoped.
So If I am understanding things correctly, the new webtop is just tweaked phone mirroring, as opposed to now where there are 2 operating systems running side by side. I guess ubuntop won't work on that system then. very disappointing.
As nice as Evo Desktop was there were tons of drawbacks. So I can tell you from experience that this is going to be a serious step backwards for "Webtop". Open up a mobile browser and visit a page that has flash based chat embedded. You cannot leave that page (view another page in another tab) because as soon as you leave the chat page tab everything gets suspended. When you go back to the chat page tab you have to log back in and start over.
Document editing will also be an issue as you have to use cloud based editors like Google Docs because to my knowledge none of the current office apps have that tablet switch needed change how the ui is rendered. When you combine this with the browser tabs issue and that Google Docs puts a fairly heavy load on the browser, you can say goodbye to any real doc editing.
What it comes down to is that many app devs are going to have to add the needed ui switch and changes to keep the new webtop from being trash. This will not be easy. I fought for months to just get a browser with a "desktop ui" look with no success. Even with thousands of users on the Evo project nobody would touch it. I ended up having to modify an existing browser to give my users a desktop look. Multiply that by how many commonly used apps that would need a ui switch and Moto is just asking for failure.
My other concern is what happens to the, now wasted, 1.3GB osh partition? The leak has no mention of it in the install script. It looks like it will still present but only accessible via vnc which has it's own issues and drawbacks.
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
After a 3 year stint with Windows Phone I've come back to Android with the purchase of a Galaxy S4, however the transition back hasn't been entirely smooth.
One source of quite a bit of this ire, is from how android organizes the photo gallery. Doesn't matter the app, they all seem to organize in a similar way - find all folders with photos in it, list every folder as a separate album. That's great, but I don't want that.
On my Lumia 920 I had my photos organized like this:
And on the device, they show up like this:
I have folders with only subfolders as content:
And they retain this organization in the photo viewer:
For the life of me, I cannot find a single app that does this. I've tried Scalado, QuickPic, Just Pictures, Android ICS Gallery, Samsung Gallery, Customizable Android 3D Gallery - nothing.
Is this just how the mediascanner works? Does anyone know of any way to organize into subfolders within a gallery app? Is there any app that allows me to custom define my own setup? I wouldn't mind having to configure a text file to my setup, I just want it organized.
I've been searching all morning and have found countess threads with no solution. This is how BB, iOS, WP, and almost every other mobile OS organizes photos.
Thank you for your time.
______________________________________________________________________________________________________________________
Solution thanks to GermainZ.
The application F-Stop Media Gallery on the android marketplace allows the construction of custom albums. Although you cannot specify covers for the empty albums containing subalbums, I've found a decent workaround.
Now my album view looks like this:
With subalbums looking like this. In order to get some form of album cover, you need images in the folder. However it will take the top 4 images and use those, so if you want a phone for the whole cover you'll need to split it up into 4 quadrants. Or just do 1 image and deal with it being small. That is what I did because I got lazy.
Also, albums within other albums don't take on covers for some reason. I contacted the dev and he said this was intentional but they were looking to change this in the future.
Albums need to be manually defined, which is a tad irritating but it works alright once you have it set up.
I have not seen any that will do that. To be honest Android is supposed to be different then all the other OS
Wayne Tech Nexus
zelendel said:
I have not seen any that will do that. To be honest Android is supposed to be different then all the other OS
Wayne Tech Nexus
Click to expand...
Click to collapse
That's a particularly silly reason to have a system that lacks features every other system offers.
Scrtcwlvl said:
That's a particularly silly reason to have a system that lacks features every other system offers.
Click to expand...
Click to collapse
TO be honest it is a perfect reason. I mean really think about. Linux is different then every other OS on the planet. So it only makes sense that Android would be to.
zelendel said:
TO be honest it is a perfect reason. I mean really think about. Linux is different then every other OS on the planet. So it only makes sense that Android would be to.
Click to expand...
Click to collapse
It's perfectly possible to make an app that does that. Difference doesn't have to mean inferiority.
GermainZ said:
It's perfectly possible to make an app that does that. Difference doesn't have to mean inferiority.
Click to expand...
Click to collapse
Oh I am sure it can be. But to be honest I have no issues with how Quick pic works. It separates my folders just as they should. So inferiority is in the eye of the beholder.
zelendel said:
TO be honest it is a perfect reason. I mean really think about. Linux is different then every other OS on the planet. So it only makes sense that Android would be to.
Click to expand...
Click to collapse
So your position is ... what?
Android gets a pass on not having a pretty basic feature or any apps with the feature... because it's based on linux?
Well then. We might as well not even expect future version of android... or apps. They've all already gotten as good as they're gonna get, since they're based on linux.
Yoinx said:
So your position is ... what?
Android gets a pass on not having a pretty basic feature or any apps with the feature... because it's based on linux?
Well then. We might as well not even expect future version of android... or apps. They've all already gotten as good as they're gonna get, since they're based on linux.
Click to expand...
Click to collapse
No I point is you should not expect it to act like any other OS. If people want this feature they are more the welcome to make it. That is the great thing about android. Your free to make anything you like
zelendel said:
Oh I am sure it can be. But to be honest I have no issues with how Quick pic works. It separates my folders just as they should. So inferiority is in the eye of the beholder.
Click to expand...
Click to collapse
zelendel said:
No I point is you should not expect it to act like any other OS. If people want this feature they are more the welcome to make it. That is the great thing about android. Your free to make anything you like
Click to expand...
Click to collapse
Unless I'm reading it wrong, that wasn't the impression I got.
He was simply giving us examples to clarify what kind of apps he wants. I still don't understand why you're talking about how different Android is as an OS.
EDIT: To make myself clear - If you don't know about such an app, that's cool. But going back to how the OS is different to explain how a perfectly possible to make application doesn't exist yet doesn't make any sense to me.
GermainZ said:
Unless I'm reading it wrong, that wasn't the impression I got.
He was simply giving us examples to clarify what kind of apps he wants. I still don't understand why you're talking about how different Android is as an OS.
EDIT: To make myself clear - If you don't know about such an app, that's cool. But going back to how the OS is different to explain how a perfectly possible to make application doesn't exist yet doesn't make any sense to me.
Click to expand...
Click to collapse
The point was that you can not expect one OS to act like another. People come here and start asking well why doesnt this app do this or that, when the IOS, WP, WM ect apps do it like this. People should not expect the apps to work the same across different platforms. Can it be made to act like said app? Yeah most likely, just dont expect a stock app to work like other apps on different platforms
zelendel said:
The point was that you can not expect one OS to act like another. People come here and start asking well why doesnt this app do this or that, when the IOS, WP, WM ect apps do it like this. People should not expect the apps to work the same across different platforms. Can it be made to act like said app? Yeah most likely, just dont expect a stock app to work like other apps on different platforms
Click to expand...
Click to collapse
Of course, and I totally agree with this. However, I personally didn't see the OP doing that, but giving us a precise example of what he wants. That's all.
@Scrtcwlvl
I searched around a bit - Check F-Stop Media Gallery, it has nested albums.
Otherwise, I think your best bet would be to get a file manager with media support. FX does that, but I don't think it does it for free.
So, basically, I got the smart dock and, it's pretty damn awesome. But OMFGTHATFREAKINGMOUSECURSORTHATWON'TGOAWAY.
Anyway, I did some searching and found that there's no way to get it to disappear under stock. Grr. But some custom ROMs allow it. Unfortuantely, none of them seem to say whether they do or not, so I need your advice! BUT! There's other things I need too, which are even more important than being able to make the cursor disappear. So... I need:
1) NTFS support, read AND write. If the ROM isn't Android 4.2+, Paragon NTFS & exFAT can take care of that. So; I need a ROM that's either 4.1 based or has built-in NTFS support. (I don't need exFAT.)
2) Works with the smart dock. The one that has the audio out, HDMI, and 3 USB ports, and isn't officially compatible with the S3 but works anyway.
3) Can make the freaking mouse cursor disappear. Even better if this can be set on an app-by-app basis or toggled with a key shortcut on an external keyboard.
4) Decent battery life. Doesn't need to be better than stock, just not one of those ROMs that runs the thing flat in half an hour.
5) Being based on Samsung's rather than AOSP would be a bonus, but I'm not *overly* fussed on this.
(I heard some custom ROMs result in the FM Radio not working. I really couldn't care less about this, I never use it, so it's fine if that doesn't work.)
I don't need to be walked through how to install it etc, I've done all that several times before. Just need a reccomendation on which one to use, to save me trying every one of the millions out there. Even if you can only confirm some of those features and aren't sure about others, that'll at least narrow down the selection to try. Thanks in advance guys. =)
Recommend a ROM threads aren't allowed. You have to read the features in the rom thread.
That said:
1) This is KERNEL related
2) Only Touchwiz support video out
3) The mouse cursor you turn on in developer options? Or you mean when you're using the mouse? Can't imagine using a mouse without a cursor
4) Again, mainly kernel related. But since you narrowed it down to only touchwiz roms in point 2, it's not really relevant anymore.
5) Not really got a choice.
^^^^This^^^^
Thread Closed