Hello, I have not found much about this topic anywhere else so I thought I would try here.
I was wondering if Glass supported SVG image files and the display of them. For example if I had an SVG image as XML would glass be able to parse the image and render it like a browser would be able to.
Any help would be appreciated.
Only if the KitKat browser natively renders SVG, otherwise you'd need to sideload an app that does.
Related
Are there any other programs out there that can change the today screen wallpaper aside from the standard image and video viewer provided by Microsoft? I have looked all over and cannot find a single lead to any programs that can do such a task. The standard image viewer is extremely slowwwww! Any help would be appreciated. Thanks.
-Louis
file explorers and photo album viewers work
Hey,
I'm looking to re-skin the Android Spotify app, as the current app looks terrible on high-res devices (like my HTC Desire HD).
It looks like it shouldn't be too hard, as most assets I can see are just images, that I'll just replicate in high-res.
What I'm wondering though is if anyone knows where I can find the current assets (images) so that I can start replacing them, and then release it for anyone else who wants to?
Thanks
All of the images used are in the drawable folders.
No real skins yet?
How do you fix Apps and Games that don't stretch full screen in Landscape Mode on Nook Color? I installed Mini Squadron and Shoot U and when I try to view them in Landscape Mode, they don't stretch full screen like for instance, Angry Birds. Is there a setting I have to change on the Nook Color? Do I have to do the Spare Parts trick like the Samsung Galaxy Tab? Just curious if anyone found the solution to this. Kinda sucks because I like that game Shoot U
UPDATE: I fixed the issue. I researched the Fullscreen Compatibility Mode fix for the Samsung Galaxy Tab on YouTube using Spare Parts and followed the steps to fix my landscape issues for some apps/games. Here is the link to the YouTube video:
http://www.youtube.com/watch?v=zasSIA7sexM
Be sure to follow the steps completely which include the 2 reboots. Do not skip any steps in the video because it won't work if you do. List of games that I got fix:
- Robo Defense - Before fix, the screen would stay in 4:3 aspect ratio mode and I couldn't see my robots to drag on the screen. After fix, the screen loads full screen with robots accessible.
- Shoot U - Before fix, the screen would stay 4:3 aspect ratio. After fix, the screen utilizes the whole screen.
- etc.
Apps can set whether they do automatic stretching or not in the manifest file of the apk.
You could try to use APK manager (http://forum.xda-developers.com/showthread.php?t=695701) play around with the manifest file and repackage.
Fixed the issue
Full Screen Compatibility Mode fix with Spare Parts
http://www.youtube.com/watch?v=zasSIA7sexM
Fixed the issue. Folllow the steps in the YouTube video. Now, I just need to get the button re-mapping configuration setup and the Nook Color will be COMPLETE =)
This fix does not seem to fix the remote control on the xbmc app. Anybody get that to work?
Nevermind -- found it:
I can't seem to find a spare parts with the compatibility tick box. If it's copacetic, would someone post the apk here?
quietglow said:
I can't seem to find a spare parts with the compatibility tick box. If it's copacetic, would someone post the apk here?
Click to expand...
Click to collapse
http://www.freewarelovers.com/android/app/spare-parts
jerrygon,
I haven't used the XBMC app yet. I'll try to install it and see if I get the same issues like you. Again, follow the directions in the YouTube video step-by-step. Don't skip on any of the steps. It won't work if you skip steps. That is what I did first and it did not work until I followed the instructions completely.
califrag said:
http://www.freewarelovers.com/android/app/spare-parts
Click to expand...
Click to collapse
DOH! I wish I would have read this full thread for a link
I ended up pulling the spareparts apk from the 2.1 system image that's included with the Android SDK (2.2 version wouldn't install).
Oh well, whatever works.
still buggy
i did this on my nc but brickbreaker still is a smaill screen not sure what i've done wrong. i followed the procedures correctly, still no go i'll try your apps when i get home maybe its just a doomed app
I've also tried this and still have many games run in a small screen and it doesn't stretch to the edges. Any ideas?
Same here
go0nie said:
I've also tried this and still have many games run in a small screen and it doesn't stretch to the edges. Any ideas?
Click to expand...
Click to collapse
I did this too and my apps (read: games) are stretch, but instead of taking 50% of the screen, they take up 70% of the screen...
Thanks for the tips everyone, seems to do the trick for a few apps.
Worked great for robo defense, thanks!
Did anyone encounter this problem with Droid Comic Viewer (AVZ)? I am not with the nook now to try this solution but it seems like some people say AVZ works great and they didn't mention having to fix it to expand to full screen.
My mint.com app is also tiny.
I'm wondering if I can't get AVZ to work what method of viewing comics as either CBR or EPUB (by way of calibre) is best - I tried aldiko but I can't zoom in on any pages to read the small text.
What about the home screen in portrait mode? The widget icons on the sides are cut off? Is there a thread for resolution?
Just want to say the method in this video fixed the issue! At least for the comic book reader and for mint.com app which were very small. Much better. Well the comic book reader isn't exactly thrilling me, but at least I can try it out now.
I have a large number of my photographs prepared for web viewing and copied to my Nook HD+ micro SD card. These are scaled to a maximum of 900 pixels high or 1350 pixels wide for portability. When using the Quickpic app there is really no problem. In Quickpic, in horizontal screen mode, double taps cycle through three magnifications; 100% viewing (a necessity for me), and fit to height or fit to width. The last two are nice features but most likely one or the other will force the image off the screen. There is no ‘best fit’, which I don’t understand. Any minor inconvenience this poses pales compared to my web browsing experience, which is really where I want to use these and other similar size images.
...To the heart of the problem:
The images I mentioned above are a subset of my 'misterpixel' photos up on Pbase and (almost) all are scaled to this same 900 or 1350 pixel (original) size. The ‘original’ images should easily fit in the Nook HD+ in horizontal mode where the screen is 1280 high and 1920 wide….but that isn’t remotely the case using any of the Android internet browsers I have tried so far. With the Nook HD+ sideways the images typically switch between two different sizes upon double taps and neither of these two sizes fit to the screen in any usable fashion. To be honest, I can’t figure out what the images are scaling to as nothing fits to screen even though most normal web pages behave as expected . My suspicions are that the problem isn’t the browsers but some configuration in the Nook itself or perhaps the Nook’s version of Android. Or perhaps it is that in conjunction with the way the PBase pages are set up. Worst case, do I need to root my Nook to fix this issue?
I should say at this point I expected that when using any of these Android browsers and using ‘desktop mode’ that they would in fact mimic my desktop. On my actual desktop screen these PBase images appear in a proper 1 to 1 (100%) manner. I even tried downloading Android browser add-ons to more closely mimic various desktop browsers and it was no help.
As high resolution tablets and photography mix this will increasingly become a major problem. but for right now I’m at a loss as to how to fix this.
Bruce
bruce164 said:
...As high resolution tablets and photography mix this will increasingly become a major problem. but for right now I’m at a loss as to how to fix this.
Click to expand...
Click to collapse
I'm no expert on displays, but maybe it has something to do with the pixel density that we use on the Nook. It may affect the way the browsers render the image. Are you using the stock rom?
There are some really easy HTML/CSS tricks that you could use to scale the pictures for easy viewing on the web, but you would need to create HTML page(s) and show your images there. Would creating an html page work for your needs? Im happy to show an example if so. Share a link to sample image and I will show you what I mean.
Thanks
srgibbs99 said:
I'm no expert on displays, but maybe it has something to do with the pixel density that we use on the Nook. It may affect the way the browsers render the image. Are you using the stock rom?
There are some really easy HTML/CSS tricks that you could use to scale the pictures for easy viewing on the web, but you would need to create HTML page(s) and show your images there. Would creating an html page work for your needs? Im happy to show an example if so. Share a link to sample image and I will show you what I mean.
Click to expand...
Click to collapse
Thanks for the offer but I have almost 2000 images up on PBase and I like some of the amenities the web site provides. OK…I’m lazy.
The difference between a desktop web viewing experience and the tablet viewing experience is profound. As a photographer I want my images to be seen in their entirety and in critical instances it is nice if they are seen at 100% where one pixel in the image displays as one pixel on the screen. Clearly the Nook HD+ is capable of doing this and clearly PBase is providing the ‘original’ image so that this can be done…I just can’t seem to do it. From my frame of reference as a photographer this is beyond bizarre and very frustrating.
I’m a newbie here so I am not allowed to post URLs but you are welcome to go to PBase and check out my ‘misterpixel’ photos and see if this is happening on your tablet. Its the 'original' images that give me issues even though they are realtivly small.
Bruce
New Samsung Galaxy Tab S2 user . . . question: why does the tablet's OS see a difference between media files that have their file type suffixes in capital letters rather that lower case? My tablet can play self loaded media that has lower case file suffixes, such as filenameX.mp4, but if the same filename has its suffix in caps, I get an error message stating the file type is not supported, i.e., filenameX.MP4 will not play, while filenameX.mp4 will. Same with other file types such as pdf's; filenameY.pdf will work fine; filenameY.PDF produces an error.
I can't say why but I;ve had the same issue - a video with MKV won't play but mkv will (when renamed).
I also not that finding a file manager that doesn't hide the damn extension is hard!
Fluffbutt said:
I can't say why but I;ve had the same issue - a video with MKV won't play but mkv will (when renamed).
I also not that finding a file manager that doesn't hide the damn extension is hard!
Click to expand...
Click to collapse
Fluffbutt I'd like to see the video you posted in your response, however, the popups and ads simply won't allow. Can you perhaps post a shortened ur? Back to my question, it's less a 'why' and more of a validation effort. My background is in Apple's iOs / MacOS and this is a 'forced' migration to Google's Android OS device. So, I guess what I'm looking for is some kind of confirmation that what I'm seeing is just the way it is in Samsung world - no capitalized filename extensions. Thank you for your time.
Umm - I didn't post an url. Honest, nothing... I don't even know if I have the video any more (and, even if I did I doubt XDA would want a link posted.. *cough* "downloaded video".)
If you're on windows you might have virus... if on tablet/phone it's a browser advert?
It might be a function of how the players "see" the files - when they were written the developer set ".mkv" and ".mp4" as playable files but didn't think to do ".MKV" and ".MP4".
Case-sensitivity in filenames (and extensions) is typical of Linux. Since Android is Linux-based, I would guess that's the underlying issue. And yes, it's short-sighted of developers to not account for this. Renaming the files is the quickest/easiest workaround.