Related
This morning i notice Toshiba has made available PPC 2003 2nd edition, I wonder when we will get ours damnit! See below...
Dear Customers,
Please find attached TOSHIBA CONTACT Australia Newsletter where you will find:
New Tecra A2
New Satellite P20
Sales promotions
PPC 2003 2nd edition download
Value add solutions
Countdown for Queenstown
Latest pricing
What are the new/improved features in WM2003 SE?
Landscape mode.
All the rest is just for micro$oft to brag about their operating system :wink:
Kidding, it´s the following:
- VGA and QVGA that support high-resolution displays,
and a new landscape view.
The following modes are supported.
# Portrait / Landscape QVGA (240x320, 96 dpi)
# Portrait / Landscape VGA (480x640, 192 dpi)
# Square screen (240x240, 96 dpi)
# Square screen VGA (480x480, 192 dpi)
Not all devices will support switching between modes, i.e. landscape-only, portrait-only or square-only devices are possible.
- Phone Edition improvements.
Previously, you were unable to compose a number directly from the Today screen, now with this update, it will be possible. It will now also be possible to send a Short Message Service (SMS) directly from your contacts list. Lastly, there have also been some improvements on Voice Recognition features.
- Other Enhancements
Transcriber will gain the ability to use shortcuts. These will let users write a short code phrase that will be replaced with a much longer piece of commonly used text. Shortcuts can also be used to launch applications.
Much like Windows XP does, the Start Menu will now show the most frequently launched application icons. There is a new section in the Start Menu which will display the most frequently used applications. This is divided from the list of applications that appear because they are stored in the Start folder.
The second edition will also get WPA (WiFi Protected Access), which was developed by the Wi-Fi Alliance in an attempt to make wireless networks more secure.
The new version of Pocket Internet Explorer will also be able to force web pages into a single column, similar to the way NetFront 3.1 and Opera does. This will make reading web sites not formatted for handhelds easier.
That is what i got from reviews and news.
Ive seen other changes to, as a nice improved loading Icon that runs much smoother than the original one. (Maybe to create the illusion of something actually loadin :wink: )
For HTC-built MSM7K-based devices only! All MSM7K are technically capable, but only HTC's may have the correct drivers. Will probably not work on stock ROMs. I suspect the CDMA versions of the older MSM7K devices - pre-diamond - do not have the necessary drivers either. As far as I know, the first device that came with these drivers is the Kaiser, but IIRC they are also included in various Polaris ROMs.
About
Short and simple, GfxBoost activates "QTV" mode for specific surfaces. This makes for example DirectDraw display smoother and: a bit slower or significantly faster, depending on how you look at it. It also seems to have a small effect on Direct3D/OpenGL. Effects differ between different devices, driver sets, and ROMs - some see a lot of impact, some virtually none (it seems the older ROMs/devices see the biggest impact). If your performance degrades there is something going wrong, it does happen for some people.
Err, what?
Right, this is a bit tricky! If you will benchmark it the result will be lower FPS. However, it will actually appear faster. This is because normally, not all frames are actually drawn on-screen, and the timing of the drawing can be so it appears nothing is being actually drawn at all. This does not happen when using GfxBoost - more is actually drawn to the screen, and smoother. So, from the application's point of view, it can do less per second, but from what you actually see on-screen, more happens! If you don't understand what I mean, just take it from me: it definitely looks better
Some good effects
Manila2D is faster/smoother [Chainfire]
PointUI is smoother [Chainfire]
CorePlayer playback in DirectDraw mode is smoother [Chainfire] *depends on version and settings*
Titanium seems to be faster [Mikulec]
Diamond Hologram seems to be much faster [aussiebum]
Opera 9.5 seems to be much faster [undac]
SPB Mobile Shell 3.0 seems to be smoother [TITAN-23]
iGo 8 feels the love [draxredd]
morphgear feels the love [draxredd]
FinalBurn feels the love [FlorentG]
TouchFlo 3D feels the love [babijoee]
XTRAKT feels the love [babijoee]
Some bad effects
GfxBoost breaks WMP MP4 playback [FIXED]
GfxBoost breaks camera [FIXED]
GfxBoost breaks Fullscreen/Streaming Player [FIXED]
GfxBoost breaks YouTube [FIXED]
CorePlayer playback in QTV mode may break GfxBoost (may be fixed)
Devices reported this works with
HTC Touch Cruise / Polaris
HTC TyTN II / Kaiser
HTC Touch Diamond / Victor
HTC Touch Pro / Raphael / Fuze
HTC Touch HD / Blackstone
Sony Ericsson Xperia X1 / Venus
Also works with, but not as much effect as with ^^^:
HTC Touch Diamond 2 / Topaz
HTC Touch Pro 2 / Rhodium
Update: it may still have _some_ effect with the Topaz, but I don't think anyone has seen any improvement with the Rhodium, so don't bother Seems the drivers on those devices are quite a bit faster already than the older MSM7K devices
Quirks
Alright, it took a bit of research, a lot of trial and error, quite a bit of hairpulling, a few hours of IDA, and an entire crate of beer to get this working on the few of my devices I actually bothered to test it on (Kaiser and Touch Pro). I think everything is now properly hooked up with HTC's own software so things like Camera and WMP also still work. If you run into anything, strange, well, first RTFM below, then see if you want to post it here.
TFM (The F*ing Manual, read it!)
Requirements
An HTC-built MSM7K-based device, sporting QTV and some similar nonsense. In general, I would say this this is the entire range between the Vogue and the Touch Pro, though I've only tested it on Kaiser and Touch Pro, and both are GSM.
Installation
- Install the CAB on your device
- Soft-reset (does not seem to be needed on all devices)
- Start GfxBoost and click Enable
Uninstallation
- Start GfxBoost (if not running) and click Disable
- Uninstall CAB as usual
- 1.2: You may have to soft-reset and uninstall it again, for reasons unknown
Upgrading
- Install new CAB
- Soft-reset
"What's this Enabled (Inactive) status?
It means another application is running that needs this chipset feature. For example, Windows Media Player, YouTube, Camera, etc. As soon as you exit all of those, GfxBoost should re-activate itself.
"I see no difference Q_Q"
If there's a visible difference depends completely on the application you are running and what you are doing with it (aside from it possibly just not working for you). The more graphical an application is, the more chance you have this makes a difference. I've seen no differences with normal "GDI" style applications (normal apps), but for example on my Kaiser the difference in Manila 2D is enormous.
"What about this video-running-in-the-background-thing I keep reading about?"
If done properly, that has the same effect as GfxBoost. Just not as easy and it doesn't think about other applications that need this chipset feature.
bla bla Coreplayer bla bla
Exactly!
Changelog
1.2 - 22.09.2009
- Some changes to fix issue of GfxBoost not showing up in control panel for some users
- Slight adjustment to loader code, hopefully works for more peoples now (always a guess, if not you can always use 0.7)
1.1 - 01.05.2009
- Some patches to service code and handling
- Added registry fixes for common issues
- WM6.5 icon adjusted again
1.0 - 29.04.2009
- Fixed service version, hopefully this one works
0.8 - 29.04.2009
- Service version
0.7 - 28.04.2009
- Changed loader mechanism
0.6 - 28.04.2009
- Loading of dependencies is dynamic - with error messages
- All files are now signed
- Added program icons [Thanks to 12aon]
Donate
If everybody who uses this buys me a beer, I will be a very happy and/or drunk Chainfire. Please make this happen. See the link in my signature - it's not there for decoration!
Release
Yarr, it r here!
If you are updating GfxBoost, please first "Disable" and "Exit/OK" GfxBoost! Don't forget to soft-reset after installing the new CAB!
There are multiple downloads here, the GfxBoost.cab is the (now old) 0.7, the other are the new 1.1 and 1.2 service versions. Note that in the service versions, the settings panel is under Settings -> System, not under Programs!
You only need to install ONE of these. Older versions are only still available because they work for some people while the newer does not (and vice versa). Do not forget to soft-reset after installation, waiting a minute or two, then opening the Start -> Settings -> System -> GfxBoost and clicking Enable!
(Downloads < 1.1: 3820, 2043 old 0.7)
great job as always Chainfire!
keep up the good work
OWO ChainFire is developing the Holy Grail of the Qualcomm processors!
Ha ! I found you, you're quick as always... Just got the time to express an idea and you've already done all the theory and the app is on the way...
Glad to see it led somewhere.
I was wondering where have u been so long. Looks like u have done a good job, as always. Thanks.
Nice to see you back, with a boom like always
Insane ! You have a nag for improving our lives a lot with very complex improvements. I don't think I fully understand what this does, the thought creating it hurts my brain, Thanks a lot
Mr Burns: Excellent!
With nueDynamicClock hopefully getting o/clocking and a graphics boost, my Diamond will take to the skies! Hopefully...
Another great project, thanks!
So you're forcing the backbuffer to draw to screen, Is that right?
It are the released!
Wow I think it works on my TP, switching albums in tf3d seems smoother. I made an Icon for the ocasion hope you like it, 12
Doesnt work on Polaris with WM 6.5... Runtime error 216 at $03F9332C $03F9332C
Chainfire said:
For HTC-built MSM7K-based devices only!
Click to expand...
Click to collapse
Petulinek said:
Doesnt work on Polaris with WM 6.5... Runtime error 216 at $03F9332C $03F9332C
Click to expand...
Click to collapse
read 1st post
I too get that "Runtime error 216 at $03F94E04", although I have a Kaiser under WM 6.1
Nice program I will give it a go
kancrutt said:
read 1st post
Click to expand...
Click to collapse
doesn't the polaris have the same hardware as the kaiser?
HTC Touch HD
Works perfect on Touch HD... good work, thanks
sipospeter said:
doesn't the polaris have the same hardware as the kaiser?
Click to expand...
Click to collapse
Of course does...
kancrutt said:
read 1st post
Click to expand...
Click to collapse
I read it... Polaris is the same like a Kaiser... ****qualcomm MSM7200...
SimplePiano V4.3
SimplePiano with the SP_mickesjo WVGA Skin
As the name suggests it's a simple piano application. I took over "CrisRowlands SimplePiano" after Cris decided to give up developing it (Original thread). The main reason I took over is because I wanted to implement multitouch. I own HTC HD2 so my emphasize was on the WVGA format, but the application should also support VGA resolution. It should be pretty easy to create skins for other resolutions as well...
Features:
WVGA, VGA, QVGA, HVGA versions.
It has three octaves.
Record and Playback.
Dualtouch via the PinchToZoom events (not ideal but the best I could find...)
Customizable skins.
Customizable sounds (currently include Piano, Acoustic Guitar & Violin).
Currently in develop:
Continuous sliding of the keyboard view.
Change the skn files to support arbitrary number of keys.
CHANGELOG:
21.06.10(4.3)
Added two single finger chord modes (Major and Minor) - Requires special skin. I don't like this solution so I didn't follow it. If anyone is interested in this please let me know...
Added minimum note sustain length control (in milliseconds). If minimum sustain is not specified the full sample is played.
Added support for looping over the sample (by looping over the sample) Two samples can be specified, one is played once in the beginning, and the second is played over and over until the key is released. If the second sample is not specified the first one is used for the loop. This feature requires appropriate sound samples to be available.
Sounds are controlled via "Sound.lst" file. Different behavior of the notes (those mentioned above) can be controlled via this file.
Added OK/Cancel button to the settings dialog.
Vibration LED index can be now set via the "Device" tab in the settings dialog.
Polyphony can control to the "Device" tab in the settings dialog.
Fixed a problem where SimplePiano closed if an incompatible skin was chosen.
Fixed issue where bitmaps were not always clipped to bounds.
Fixed crash when sound file did not exist.
Changed applications icon (thanks mickesjo)
11.06.10(4.2) Added some exception handling during initialization and a vga skin for the Default skin. Fixed the link to point here.
10.06.10(4.0) Initial release including the new features (dualtouch, recording etc. as desribed in this post).
Screenshots:
Skins: Default WVGA skin, MewSkin WVGA skin, MewSkin VGA skin, SP_mickesjo WVGA skin, Saplorer UI WVGA skin
Settings Dialog
Download:
SimplePiano V4.3 (WVGA/VGA/HVGA/QVGA)
Alternative Download(Uploading) (including mickesjo's skin and Osprey00's alternative piano sounds - thanks to Osprey00)
Additional Skins:
(must be installed in the same location as the main application)
HVGA Rescale of the original skin (thanks to sam-2007 on post #130).
MewSkin (WVGA/VGA)
SP_mickesjo (WVGA/VGA/QVGA), thanks mickesjo. atlaswing created replacements key images, these can be found on post #47. HVGA version (thanks to sam-2007 on post #130).
Saplorer UI (WVGA), thanks xclarinetistx
Additional Sounds (thanks conantroutman):
(must be installed in the same location as the main application)
Violin
Acoustic Guitar
Piano Samples 8bit (lower quality) - these samples replace the default piano samples that comes with SimplePiano.
Alternative piano samples (thanks to Osprey00)
Rectangular QVGA (320x320) patch - extract the files from the zip files into the "Default" skin folder.
Click to expand...
Click to collapse
Previous version:
SimplePiano V4.2 (WVGA/VGA)
For QVGA the modified default skin has to be installed too.
Skins:
Default (WVGA/VGA/QVGA)(CrisRownlands' original skin)
MewSkin (WVGA/VGA)
SP_mickesjo (WVGA/VGA/QVGA), thanks mickesjo
Click to expand...
Click to collapse
Other Notes:
If I may quote Cris:
I hope you folks like it
Feedback is appreciated, improvements can only happen if I know what you folks want.
Click to expand...
Click to collapse
Some documentation
Some useful information about the *.skn files and the Sound.lst file.
The *.skn files
These files define the location of the different items on the screen. For each screen resolution the skin supports there should be one skn file. When a skin is chosen, SimplePiano search the skin directory for a compatible skn file and loads the skin according to its content.
here's an example for a skn file
Code:
Display=0,0,480,800
This line declare the target resolution of the skin. It is given in the following format: 0,0,Width,Height
Code:
Name=mewskin
The name of the skin, currently not used for anything.
Code:
Octave1=360,10,120,120
Octave1Image=OneNormal.png,OnePressed.png
Each key should include those two lines. The first line describe the location and size of the image, using the following format:
KeyName=Left,Top,Width,HeightThe second line points to the images to be used with this key. The following format is used:
KeyNameImage=NormalStateImage, PressedStateImageWhere KeyName is one of the following:
Octave1, Octave2, Octave3
Quit, Settings,
Record, Replay,
NormalKey1, ..., NormalKey8
SharpKey1, ..., SharpKey6All these keys must be specified.
NormalKey# stands for the normal note keys (C,D,E,F,G,A,B & C)
SharpKey# stands for the semitone keys (C#, Eb, F#, Ab, Bb & C#)
In addition the toolbar background has to be specified as well:
Code:
Toolbar=360,0,120,800
ToolbarImage=Background.png
unlike a regular key here only one image is supplied.
In addition the optional chord modifier keys can be specified (using the same logic):
Code:
ChordMajor=-30,0,60,60
ChordMajorImage=MajorNormal.bmp,MajorPressed.bmp
ChordMinor=-30,60,60,60
ChordMinorImage=MinorNormal.bmp,MinorPressed.bmp
The Sounds.lst file
This file defines the sounds to be used with the selected instrument. First of all it binds a note to a wav file. In addition different properties can be set for each note, as I'll explain below:
Code:
[1]
The file is divided into octave, currently there are 4 octaves (since SimplePiano also includes C4 &C#4). Each octave is titled with its number.
Code:
C=Data\C1.wav, Loop=0
Then, the sound files for this octave are given. The following format is used:
Note=FileName, Option1=value1, Option2=value2,...Note is one of the 12 notes in an octave. The following notation is used: C,Cs,D,Eb,E,F,Fs,G,Ab,A,Bb,B.
Then a relative path to the sound file is specified. Followed by a list of parameters and values pairs separated by comas. These parameters are optional. The following parameters can be declared:
Loop=#This specify how many times to loop over the sample (0 - plays the note once, -1 loop infinitely). If a non-zero value is given for a note, the note will be played as long as the key is pressed, once the key is released the playing will cease immediately. By default (if not specified) Loop=0.
MinimumLength=#This specify the minimum length (in milliseconds) a note is to be played. If this value is -1 the sample will be fully played. any other (non-negative number), the note will be played at leas this amount of time. For example, if a value of 500 is specified, every touch on the keyboard will generate a 500ms sound. If the key is held longer than 500ms the sound will stop when the key is released (or the sample reaches its end). The default behavior depends on the "Loop" setting: If Loop=0 MinimumLength=-1. Otherwise MinimumLength=0.
Good job man
Good luck with this
I don't suppose you could maybe send me a copy of the source code etc?
Maybe upload it & give me a link.
The main reason I wasn't able to implement these features is because I don't know how. It would be quite interesting to learn about how you did it
good job on significantly improving chris' already nice work
And dang you've beaten me to first reply
ephestione said:
good job on significantly improving chris' already nice work
And dang you've beaten me to first reply
Click to expand...
Click to collapse
cris_rowlands said:
Good job man
Good luck with this
I don't suppose you could maybe send me a copy of the source code etc?
Maybe upload it & give me a link.
The main reason I wasn't able to implement these features is because I don't know how. It would be quite interesting to learn about how you did it
Click to expand...
Click to collapse
Thanks guys...
Cris... no problems, just let me tidy the project a little...
I love your simple piono 4.1. Now 4.2 should be better than 4.1. Thanks for the updated version...
OP, thanks for the APP. I look forward to future updates once more of the bugs have been knocked out!
Update: added a download link to the mewskin, this is nicer looking especially for the VGA resolutions (but also on the WVGA). Kudos to the author (xxmewstarxx)...
Just install the mewskin.cab after installing SimplePiano (no need to reinstall).
Z.
for now, I vote for default to 0 interval between multitouch keypresses, instead of 300ms
Not much of a big deal as you can change it yourself, yet if you already restarted to register multitouch, and you change that option later, you need to restart again
I am also thinking about spanning through more than 3 octaves, and a different method of changing the octave that lets you do that faster and more easily, will report back when I have a better idea
Nice!
Unfortunately the space on the screen ins't that much but if there was a way to "somehow" squeeze in and create spaces for Chord Symbols/Buttons and when these are being pressed, a chord is being played (a flat chords, an arpeggio). Said chord-sounds could be default-sounds distributed with the application or pre-recorded by the user. Something similar to those Casio-chords (or whatever they are called) which do the fingering for you. Another option could be that it played just the root of the chord so one could create some variety and a little base-line while playing the melody on the normal keyboard.
The problem, I guess, is surely the space on the screen and the limit of two touches simultaneously.
Just some thoughts....
ephestione said:
I am also thinking about spanning through more than 3 octaves, and a different method of changing the octave that lets you do that faster and more easily, will report back when I have a better idea
Click to expand...
Click to collapse
tilleke said:
Nice!
Unfortunately the space on the screen ins't that much but if there was a way to "somehow" squeeze in and create spaces for Chord Symbols/Buttons and when these are being pressed, a chord is being played (a flat chords, an arpeggio). Said chord-sounds could be default-sounds distributed with the application or pre-recorded by the user. Something similar to those Casio-chords (or whatever they are called) which do the fingering for you. Another option could be that it played just the root of the chord so one could create some variety and a little base-line while playing the melody on the normal keyboard.
Click to expand...
Click to collapse
Well, as for the 3 octave limitation, that could be easily broken, just that I don't have the sounds... If someone's willing to generate them I'll include them in the application.
About changing octaves I thought of two possibilities, one would be to just add two buttons at the end of the keyboard that moves one octave up or down. Another possibility is to create a slider above (or below) the keyboard on which you can slide left or right to change octaves. Sliding can also be continuous so that the first note is necessarily C. Such slider can also have some buttons to toggle chords buttons as tilleke suggeted...
tilleke said:
The problem, I guess, is surely the space on the screen and the limit of two touches simultaneously.
Click to expand...
Click to collapse
I really hope HTC will release some proper API that supports real multitouch...
Z.
tilleke said:
Nice!
Unfortunately the space on the screen ins't that much but if there was a way to "somehow" squeeze in and create spaces for Chord Symbols/Buttons and when these are being pressed, a chord is being played (a flat chords, an arpeggio). Said chord-sounds could be default-sounds distributed with the application or pre-recorded by the user. Something similar to those Casio-chords (or whatever they are called) which do the fingering for you. Another option could be that it played just the root of the chord so one could create some variety and a little base-line while playing the melody on the normal keyboard.
The problem, I guess, is surely the space on the screen and the limit of two touches simultaneously.
Just some thoughts....
Click to expand...
Click to collapse
zevele said:
Well, as for the 3 octave limitation, that could be easily broken, just that I don't have the sounds... If someone's willing to generate them I'll include them in the application.
About changing octaves I thought of two possibilities, one would be to just add two buttons at the end of the keyboard that moves one octave up or down. Another possibility is to create a slider above (or below) the keyboard on which you can slide left or right to change octaves. Sliding can also be continuous so that the first note is necessarily C. Such slider can also have some buttons to toggle chords buttons as tilleke suggeted...
I really hope HTC will release some proper API that supports real multitouch...
Z.
Click to expand...
Click to collapse
I was thinking the exact same things regarding octave switching, more like automatic recognition, as in when you press a key near the border, the keyboard gets slided past the border of a X length to accomodate for the "direction" you're taking
And tilleke suggestion is very interesting.
Here's my take: just like you play two sounds together when you do multitouch, you don't need to really record a chord, you only need to play 3 sounds together.
Example, put a swith on top, with three positions:
1) Normal
2) Major chord
3) Minor chord
Then you press, say, C
Cases:
"normal" : the note C is played
"major" : the notes C E and G are played
"minor" : the notes C D# and G are played
THe switch would be a slider onr, because a toggle one (1-2-3-1-2 and so on) would take too long if you need 1 and you're currently on 2.
Glad to see somebody picking up on this where Chris left off.....
If you want more octaves I'd be happy to provide them.
Just out of interest, are the samples in this version the same ones from Chris' original version?
conantroutman said:
Glad to see somebody picking up on this where Chris left off.....
If you want more octaves I'd be happy to provide them.
Just out of interest, are the samples in this version the same ones from Chris' original version?
Click to expand...
Click to collapse
More samples can't hurt, but at the moment I'm trying to solve the chords feature...
The samples are the same ones from the previous version.
Thanks,
Z.
Totally awesome. Poor WM support. it seems like everyone writes off Windows platform as thou its limited, but if you had the support you show with this simple piano, the experience level and communication would be thought on a positive (note) about windows platform... GOOD JOB!!
Thanks zevele for the work!
xda member TWolf has a FlashPiano that he stopped developing. The program itself has a great sample of 4 instruments in mp3 form, but I don't know enough about music to rename them. Maybe somebody here can take a look and rename the files. Here's the link and source code from TWolf:
http://forum.xda-developers.com/showpost.php?p=2806409&postcount=126
Would be nice to include mellotron in this, like the Manetron for iPhone
http://www.youtube.com/watch?v=pcIRG1X0VMs
dio62000 said:
Would be nice to include mellotron in this, like the Manetron for iPhone
http://www.youtube.com/watch?v=pcIRG1X0VMs
Click to expand...
Click to collapse
Seeing these applications on the iphone just depresses me... they run so much better than on the windows mobile...
Specifically to your question... If you mean playing several instruments in parallel, it shouldn't be to complicated to implement...
Okay, here's my idea for a solution for the chords feature, I've added two buttons below the keyboard one toggles a major chord and the other a minor. As all other buttons these can be moved and changed through the skin files. Please try it and let me know what you think...
SimplePiano
http://rapidshare.com/files/398328285/SimplePianoV43beta.CAB
MewSkin
http://rapidshare.com/files/398329265/mewskincabV43beta.CAB
Thanks,
Z.
Can this be hosted somewhere else? Rapidshare gives some of us problems and the the download limitation sucks. I can't download the v43beta after just downloading the v42 version. My suggestion is drop.io or dropbox... You can even use the free Skydrive for this.
Thanks for the good work...
Hello Tablet Z community,
This is my first post in this devices forums since getting mine last week. It's a great device, love it, etc.
I've never owned an Android device with a screen resolution this high so I've yet to encounter this problem - some of my games (specifically the emulator PPSSPP) have relatively low framerates (compared to my less powerful Samsung P6810 @ 800x1280). I know with computers in particular it's trivially easy to change resolutions in games/the OS, especially to increase FPS but I've never seen a method to do this on Android and Google searches turn up people mentioning device resolution without changing them.
Does anyone know if it's possible to, ideally, force a different resolution for a particular application? A less than ideal solution would be a system wide change but I would be willing to endure temporarily to increase FPS.
Any advice and suggestions would be greatly appreciated
I would be interested to know about this, iv just loaded ppsspp however havent been able to play any of the playable games listed, I did see a few videos of the xperia z playing well, however that has the same resolution and specs.
juzza87 said:
Does anyone know if it's possible to, ideally, force a different resolution for a particular application? A less than ideal solution would be a system wide change
Any advice and suggestions would be greatly appreciated
Click to expand...
Click to collapse
That was recently discussed in this thread: LCD Density Changes and Results (With Pics)
Cat McGowan said:
That was recently discussed in this thread: LCD Density Changes and Results (With Pics)
Click to expand...
Click to collapse
This is very different, setting the DPI to a non-stock value just resizes the userspace, the resolution is fixed and unchangeable as the OP is thinking. Compared to a Windows PC where you can change the resolution, in Android you only have the ability to change the dpi, which states how large the pixel-to-screen size is. A smaller number indicates a smaller pixel-to-screen size, meaning the information shown on screen is sized for a laeger screen (making it smaller, since the screen is a fixed size). And a larger number has the reverse effect. Android UI guidelines set the optimal dpi for resolution vs. screen size, to mainain a similar experience across devices (similarly sized icons and fonts, etc). Again, this has nothing to do with adjusting the physical resolution of the device, which (to my knowledge) is not possible in Android.
daveid said:
This is very different, setting the DPI to a non-stock value just resizes the userspace, the resolution is fixed and unchangeable as the OP is thinking. Compared to a Windows PC where you can change the resolution, in Android you only have the ability to change the dpi, which states how large the pixel-to-screen size is. A smaller number indicates a smaller pixel-to-screen size, meaning the information shown on screen is sized for a laeger screen (making it smaller, since the screen is a fixed size). And a larger number has the reverse effect. Android UI guidelines set the optimal dpi for resolution vs. screen size, to mainain a similar experience across devices (similarly sized icons and fonts, etc). Again, this has nothing to do with adjusting the physical resolution of the device, which (to my knowledge) is not possible in Android.
Click to expand...
Click to collapse
Heh. Thanks for the schooling, but it was unnecessary, I didn't just fall off a turnip truck.
Thanks for the replies guys, at least now I know for sure..
I wish I could get some clarification from the experts here.
Sorry if I didn't pick the most suitable forum to raise my question.
With displays resolution increasing on high-end android phones (now FHD) and some tablets too, I'd expect the browsers to take advantage on that.
Although this is some thing where I can't see any progress even with the newest hardware.
The same webpage as seen on a FHD laptop, or on a FHD smartphone, doesn't show the same thing.
The minimum zoom for a smartphone seems to be set in such away that a significant part from pages with most content is cut, in respective to what's seen on a FHD laptop.
Some could argue that once the smartphone screens are much smaller, it doesn't make sense to have same zoom level settings as it won't be readable. Although smartphone screens are getting bigger, and many tablets have big enough displays to show it in a different and still readable way...
Furthermore in many cases if you turn a smartphone in portrait or landscape you can see exactly the same content displayed wide-wise, which doesn't make any sense.
Landscape mode could make better use of the larger horizontal display resolution and show additional content.
I've tried many browsers on Android, but all seem to show the same limitations and no settings to decrease the default zoom level, neither it is possible to manually zoom-out further in any way.
Does anyone knows if this is an Android OS limitation and when this foreseen to improve, or if there is some browser that gives further control on the minimum zoom level?
I should say this has been the main reason why I've not seen a justification to change my device for a new one with better HW and larger screen...
The browsers on my qHD device, show exactly the same thing as the newest FHD ones.
Thanks in advance!