Related
I was looking for Emulator(GameBoy/GameBoy Color/Gameboy Advance) for Smartphone and i found a lot of others that does not work or there is no option for me to change the resolution because it is too small.
Finally i found a post from modaco that work on my cingular 3125 wm5/wm6/wm6.1
I believe it also work on older OS like wm2003
Hi everybody,
I've been hunting on the net for good console emulators for the smartphone and came across PicoDrive and PocketSNES. Unfortunately neither of these emulators worked properly on my C550. So I decided to try and fix it so I could play my favourite games on my phone.
The biggest change is probably getting it to work at QVGA resolution, which was a definite improvement to the postage stamp size window. After much tinkering, I think I've reached a milestone and am happy to share it with the rest of the community.
Disclaimer: These programs have been tested on my C550. I hold no responsibility for any damage caused by running them on your own devices.
Credits:
Full credit should go to the following people for original conversion to smartphone. Please provide donations to the relevant developers for their efforts, so that more projects like these remain open source and free to everyone.
FileDialogSP.dll by STomski
PicoDrive (original source) by Dave @ finalburn.com
PocketSNES (original source) by SpaceMonkey
PocketGNUboy (original source) by ???
MameCE3 (original source) by Techmaster
PocketNester (original source) by Rick Lei
Fixes/Tweaks:
Update: Now works on all smartphones including QVGA screens
PicoDrive (Genesis) Attached File PicoDrive_QVGA_19_01_06.zip
-QVGA compatible in all screen modes. (Portrait/Landscape)
-Integrated FileDialogSP.dll by STomski for ROM file selection.
-Game save/restore options
-Added key configuration screen
-Portait mode now uses full width of QVGA screen
- No sound
PocketSNES (Super Nintendo) Attached File PocketSNES_QVGA_04_01_06.zip
- QVGA compatible in all screen modes. (Portrait/Landscape)
- CPU cycle adjustment to increase game speed (lower value equals faster emulation)
- Game save/restore options
- Integrated FileDialogSP.dll by STomski for ROM file selection.
- Fixed screen freeze on startup.
- I have provided two version of the app in this archive. Version 1.43 core app will have better compatibility but will only work on QVGA phones. If you have trouble running this please refer to 1.39 version.
- No sound
PocketGnuboy (Gameboy Color) Attached File PocketGnuboy_QVGA_08_01_06.zip
- QVGA compatible in all screen modes. (Portrait/Landscape)
- Integrated FileDialogSP.dll by STomski for ROM file selection.
- Game save/restore options
- Added Extended Config Key option to redefine directional and game keys
- Fixed low res screen position offset
- Enabled GAPI draw mode by default and disabled option in Preferences screen.
- Sound enabled
MameCE3 (M.A.M.E) Attached File MameCE3_QVGA_25_01_06.zip
- This is a fairly cut down version of the full Mame32. It supports 200+ games but can be enabled for more depending on hardware emulated.
- To "OK" the legal notice screen use LEFT->RIGHT directional keys
- Added key configuration screen
- Fix default mame key quirks
- Game screen now shrinks to display size. Some games may be difficult to view on low-res phones.
- Menu option to turn auto scaling on/off
- Improved screen scaling but still a bit slow.
- Use * and # to adjust frameskip rate.
- Added option to refresh game list
- Sound enabled - but nothing to get too excited about.
PocketNester (NES) Attached File PocketNester_QVGA_14_01_06.zip ( 138.47K )
- QVGA compatible in all screen modes. (Portrait/Landscape)
- Integrated FileDialogSP.dll by STomski for ROM file selection.
- Game save/restore options
- Added key configuration screen
- Extended Sound options
- Sound enabled
There have been changes to the HTC hardware to disallow volume/record/camera keys to be used as game buttons, please stick to the keypad when redefining your own to avoid problems.
I would appreciate some feedback on your experiences with these emus, whether good or bad.
Please send enhancement requests to the original developers as I have no plans for doing any more updates to these programs.
Enjoy!
Kien Phan (Parallax).
Click to expand...
Click to collapse
All credits goes to modaco Kien Phan (Parallax).
The best emulator I've seen is SmartGear. It has support for NES, GBC, GameGear, Genesis and a couple others I think. It's going to have SNES support really soon apparently too.
The only problem is it's not free, but it works so well and with unlimited free upgrades, I think it's worth it.
bitbanksoftware.com (there's a dev discussion at modaco)
Wicked. Just what i needed. Thanks for posting this (..and thanks to Parallax for the changes!)
What are game emulators? The name implies a peice of software which enables running various formatted console games. Or is it a console game that has be rendered to play on a multitude of devices. In which case, a more appropriate name would be game emulation.
is this worked for 6.1 pro erofich ?
The PicoDrive is an interesting app.
But isn't it possible to load ROMs from a SD card?
I can't select the card in the menu and with my 64 MB ROM there's enough memory for just 1 ROM.
are there any GB/GBC/GBA emulators for HTC diamond? i tried "PocketGnuboy_QVGA_08_01_06.zip" and i was able to config the keyboard for directional keys and game keys but every time i tap the screen (to launch keyboard), it always pause so i cannot play it anyway.
any other alternatives or solutions please....
i appreciate it thanks...
hahaha... i just found a keygen for smart gear...it's funny coz the keys are dependent to owner ID.
I have an image I wish to use as a wallpaper background on my home screen.
I have cropped the image in photoshop to the exact screen size, I have successfully blue-toothed it from my mac to my Hero, when I go to set it as my background it only takes a section of it and not the whole image itself.
When looking at the standard wallpapers they are all landscape and selecting one also only takes the middle section to use.
Any ideas?
Whenever I have set my own picture as a Home wallpaper, the Hero shows a green cropping rectangle that sets the correct aspect ratio.
Do you not get this ? If so make sure the green box is resized correctly to display your image.
Also... in case I read you wrong... the wallpaper covers all 7 Home screen's and is not supposed to be enclosed in just one. ie you will see a section of it and this will move slightly as you swipe between Home's.
BTW, what did you use to Bluetooth the file from your Mac ? My Mac won't see it in Bluetooth File Exchange.
Of course forgot that it was one giant screen...
Just using the regular built in bluetooth, (have a dual 2.8 imac, OSX 10.6 snow leopard)
On another note - do you know what size the image would have to be made to fit the entire 7 screens (pixels or mm)
Snow Leopard How's that going ??
Maybe 10.6 adds more functionality ?
Did you just pair it with Bluetooth setup ? I did try that but it failed to find any services.
I believe its 640 x 480 or any other size to that aspect ratio.
Snow Leopard is the mutts..... Little bit quicker and I gained approx 15gb on my HD (not really noticeable when you have 1tb internal and 1tb external though )
Various little tweaks and a few old things improved.
Could well be that Snow Leopard has improved functionality, I know my friend had probs running OSX 10.5 and it wasn't seeing his Hero but mine is fine
Sounds good... being ex-Apple its great when the company do things right
mrdavie, I've just installed 10.6 (finally arrived this morning), but the Hero is still not seen as having the necessary services for file transfer - how are you doing it ??
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...
I mentioned it briefly in another post and searched the forum - but found nothing.
I am talking about the Sweep Panorama mode of the Xperia-S camera. Not the '3D' versions, the 'normal' (2D) sweep panorama - the last icon in the first ('Shooting mode') menu. I tend to experience problems with it and am not sure if everyone has observed the same.
In Sweep Panorama mode, whatever direction of sweeping I choose, I tend to get error messages that either:
- I am sweeping too fast, or
- I am sweeping too slow, or
- just 'Picture could not be taken' with no explanation why.
I need to mention that I have plenty of sweeping experience on my previous Xperia X10 and on a Sony Nex camera - so I am sweeping really smoothly and at medium speed. Are the phone position sensors and accelerometers too sensitive? (And the camera software inadequately set to interpret them?).
This is happening in roughly 3 out of 4 attempts (or even 4 out of 5) making the function hardly usable and very annoying.
Ironically, while the X10 had no such function, I was using a 'beta' version (called Panorama Beta) as a standalone app, offered by Sony Ericsson on the Android Market (now Play Shop). Despite being a beta, that app worked flawlessly and never gave me such problems. I have many excellent panoramas from that, and some have even won photographic awards. I particularly like the 'vertorama' mode, i.e. vertical sweeping. With the camera in 'landscape' mode, this captures a square-ish rectangle - with a wider field of view and more scene detail, at highest possible resolution. To capture a square (or 4:3 'portrait') vertorama, you need to stop sweeping early - and the Beta app had a 'Stop' button.
The new version integrated within the Xperia camera has no 'Stop' and expects you to make very long sweeps. I tried to stop by pressing the on-screen or physical shutter button, but that produces the above errors - or a very long and narrow rectangle, half of it greyed and the other half a blurry, low resolution panorama.
Disappointed with the function, I wanted to use the standalone Panorama Beta app, but it doesn't appear in the Market. Is it withdrawn by Sony? (As no longer beta and included with newer firmware)? Or is it only not appearing for the Xperia-S - presuming you already have it?
I tried taking a backed-up .APK from the X10 and 'restoring' (installing) it on the X-S, but it does not install. The install process starts normally, but when the blue 'thermometer' finishes, the message is: 'The app did not install' - with no further explanation. I imagine it discovers the newer version already installed and avoids a conflict with it?
All other 'panorama' apps on the market are much worse, from primitive to utter rubbish. They are either not 'sweep' and ask you to take multiple separate shots, asking you to manually align them to on-screen guide marks, before running a 'stitch' operation (resulting in very poor blends with obvious fault lines). Or they shoot relatively smoothly, but the end image is very lo-res, small in size and out of focus. Among all of them the Photaf app was closest to 'working' but it's only horizontal and stitches are a hit-and-miss (most of the time a miss - too obvious).
Can others, please, share experiences with the Sweep Panorama mode in the Xperia-S camera? Does it work for you or have you got similar problems? Has anyone found solutions?
Any suggestions how to make the Beta standalone app install and work? (The new one isn't standalone, so I am not sure I'll be able to uninstall it, even when I root the phone).
Thanks for any info!
The new Sweep Panorama sucks big time indeed. There's a modified APK of the beta floating around, I've been using it on my Arc S/Neo for ages, works just fine!
Don't have my S yet, so can't try it, but you can give it a go:
http://www.box.com/s/182e205dc19cbba235f7
Ambroos said:
The new Sweep Panorama sucks big time indeed. There's a modified APK of the beta floating around, I've been using it on my Arc S/Neo for ages, works just fine!
Don't have my S yet, so can't try it, but you can give it a go:
http://www.box.com/s/182e205dc19cbba235f7
Click to expand...
Click to collapse
Thanks a lot - this is the same Panorama 'Beta' I loved on my X10, works well on the X-S. I'll now use it as main pano tool and hope Sony will fix their in-camera version with one of the firmware updates.
Not sure if they read (or at least scour with spider-bots) this and similar sites for insight what needs fixing - if I knew a contact point I'd write to them but won't spend time researching their feedback channels...
The S camera rocks otherwise, wish you to get yours soon!
I'll let them know whenever I get the chance
@duraaraa any info or direction that you can provide on this?
I upped the resolution from stock 1080x2160 to 2160x4320 and left dpi at stock so I can have more screen real estate and still have a comfortable viewing experience. The issue I'm facing now is, I cannot capture a screenshot I get an error.
System UI
Couldn't Capture Screenshot
Screenshots are not allowed by this app or your organization.
steps to reproduce:
up your resolution to 2160x4320 and take a screenshot
Any guidance would be appreciated.
webleeper said:
@duraaraa any info or direction that you can provide on this?
I upped the resolution from stock 1080x2160 to 2160x4320 and left dpi at stock so I can have more screen real estate and still have a comfortable viewing experience. The issue I'm facing now is, I cannot capture a screenshot I get an error.
System UI
Couldn't Capture Screenshot
Screenshots are not allowed by this app or your organization.
steps to reproduce:
up your resolution to 2160x4320 and take a screenshot
Any guidance would be appreciated.
Click to expand...
Click to collapse
Sorry, don't know. Probably issue related to rooting and the settings you changed.
Thanks for the quick reply but I'm not rooted.
webleeper said:
@duraaraa any info or direction that you can provide on this?
I upped the resolution from stock 1080x2160 to 2160x4320 and left dpi at stock so I can have more screen real estate and still have a comfortable viewing experience. The issue I'm facing now is, I cannot capture a screenshot I get an error.
System UI
Couldn't Capture Screenshot
Screenshots are not allowed by this app or your organization.
steps to reproduce:
up your resolution to 2160x4320 and take a screenshot
Any guidance would be appreciated.
Click to expand...
Click to collapse
Mate 10 pro panel is only 1080p to begin with,
In what way did you upped the resolution ?? The setting wont give you that resolution option.
otonieru said:
Mate 10 pro panel is only 1080p to begin with,
In what way did you upped the resolution ?? The setting wont give you that resolution option.
Click to expand...
Click to collapse
no need for root or settings to change DPI or Resolution
adb shell wm size 2160x4320
adb shell wm overscan reset
webleeper said:
no need for root or settings to change DPI or Resolution
adb shell wm size 2160x4320
adb shell wm overscan reset
Click to expand...
Click to collapse
uh... well... you already understand that this method is "only faking" the number for the app to think that it run on that size of screen right ? Hardware & stock OS wise, the limitation is still on 1080p
I dont think the system UI app of EMUI 8 itself was made to handle that number
Normal 4K itself is only 3840 x 2160, and i dont think i ever found any phone running 4K+ (18:9)
This is just like asking why sometimes the play store act weird when we change our DPI
So answer is that : because it simply didn't support it
I've done #wm size 720x1280 & wm density 320 to 720p screen for long battery life. and I found the system's screenshot can not take whole screen(720p one).
It looks like the screenshot component take a 480p screen and the same 720p adjusting on AEX 5.x is fine.
so I thought maybe the screenshot on pie still mistake 720p screen for 1080p screen and take a 480p picture（expect: 1080p x 720/1080 = 720p, but now: 1080p x 720/1080 x 720x1080 = 480p）
But I notice that keep wm size 1080x1920, whatever which density（320 480 240）I've set, the screenshot could take a complete screen picture. while I change density, whatever resolution (720x1280, 480x800, 1080x1920), screenshot just take the top left part of screen...
partial screenshot is same condition , take a top left part of what I selected .
the screenshot on different resolution is the last issue I can found on AEX 6.0, which not contain on AEX5.x（maybe this is pie issue but still expect you can fix it） if I don't need change the resolution, the ROM is PERFECT?
can you fix this ?? thxxxxx a lot
XDrz said:
I've done #wm size 720x1280 & wm density 320 to 720p screen for long battery life. and I found the system's screenshot can not take whole screen(720p one).
It looks like the screenshot component take a 480p screen and the same 720p adjusting on AEX 5.x is fine.
so I thought maybe the screenshot on pie still mistake 720p screen for 1080p screen and take a 480p picture（expect: 1080p x 720/1080 = 720p, but now: 1080p x 720/1080 x 720x1080 = 480p）
But I notice that keep wm size 1080x1920, whatever which density（320 480 240）I've set, the screenshot could take a complete screen picture. while I change density, whatever resolution (720x1280, 480x800, 1080x1920), screenshot just take the top left part of screen...
partial screenshot is same condition , take a top left part of what I selected .
the screenshot on different resolution is the last issue I can found on AEX 6.0, which not contain on AEX5.x（maybe this is pie issue but still expect you can fix it） if I don't need change the resolution, the ROM is PERFECT
can you fix this ?? thxxxxx a lot
Click to expand...
Click to collapse
Who is gonna fix what? Just use the phone the way its supposed to be used i dont understand what you are doing and why. If anyone, huawei can fix your issue i guess.... good luck talking to them.
You should read this, particularly the long answer near the top which explains the size vs density changes.
https://stackoverflow.com/questions...to-use-adb-shell-wm-to-simulate-other-devices
I think this is actually a bug in android pie. My phone has a 4k display, but normally uses HD res unless in gallery app. So I changed wm size and density to match the display (and despite what some other say, this actually changes the visible resolution, IF your display has this many physical pixels).
Screenshots worked worked fine in oreo, but after updating to pie, there are black borders on the picture.
Display
Spodi2290 said:
I think this is actually a bug in android pie. My phone has a 4k display, but normally uses HD res unless in gallery app. So I changed wm size and density to match the display (and despite what some other say, this actually changes the visible resolution, IF your display has this many physical pixels).
Screenshots worked worked fine in oreo, but after updating to pie, there are black borders on the picture.
Click to expand...
Click to collapse
No Huawei phone has a 4k display, this whole thread is a waste of space really, guy setting his phone display to something that is not supported and wondering why his screenshot won't work, damn mate 10 pro is 2160x1080 and can't be any more than that, if the problem was the screenshots not working in a supported mode there might be a reasonable and were but as it stands this thread should be closed and deleted
revjamescarver said:
No Huawei phone has a 4k display, this whole thread is a waste of space really, guy setting his phone display to something that is not supported and wondering why his screenshot won't work, damn mate 10 pro is 2160x1080 and can't be any more than that, if the problem was the screenshots not working in a supported mode there might be a reasonable and were but as it stands this thread should be closed and deleted
Click to expand...
Click to collapse
The whole point of my post was more like: its not a Huawei only "bug", but effects all (or at least most) pi phones with a custom wm size set. Maybe I was beating around the bush too much... :angel:
Spodi2290 said:
The whole point of my post was more like: its not a Huawei only "bug", but effects all (or at least most) pi phones with a custom wm size set. Maybe I was beating around the bush too much... :angel:
Click to expand...
Click to collapse
Hi, have you found any solution for the screenshots when you change the screen resolution? You're right it happens only in pie and with different phones, in oreo the multitasking previews resize when you enter to the app but the screenshots are ok, in oreo the previews in multitask are ok but the screenshot miss a part of the screen.