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: )
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...
Hi all,
Well ... I waste some hours trying to make a color profile of our phone screen and ... I did it ! I can say it wasn't easy ...
I was bored to make stuff in photoshop and have a different result on the phone screen, then go back to PS, then push again, PS again ....
Attached files:
-Graphic which shows that the screen color space is smaller than sRGB & Adobe98. We also have a low contrast ratio of 350.
-The color profile that you have to put in C:\windows\system32\spool\drivers\color
-Photoshop screenshot to enable the profile
--> When you make images modd in PS for your phone (don't forget to disable it when you work with normal pictures !), choose : menu>Display>Work format (I don't have the UI in english so I don't know the real name --> look at the screenshot), then choose the profile and tick "Keep RGB numbers".
You're now able to modd images that will appear like on the phone (not perfect but acceptable). If you load a SGS3 screenshot you will see the difference too (CTRL Y to toggle apply profile / no profile).
However, I'm using a high-end monitor which is perfectly calibrated so I can really see the difference (this is named softproofing (simulating the destination display device). Depending on how your monitor is far from the right calibration, the profile may be useless ... Try it ! or search for someone who have a colorimeter and calibrate your screen, the improvment is very great !
I've made this profile with Spyder3 Elite in a very strange way
Enjoy !
/
/
[Edit 1] Screenshot added as example : "Without profile" jpg is the one that is made by the phone (raw). "With Profile" jpg is the same after applying my color profile, and this one is very near what I can see when I look the phone. The difference is not small !
/
[Edit 2]
1) How to convert your screenshots:
In photoshop, choose Menu Edition/Assign a profile, and then choose the phone's profile. Then choose Menu/Edition/Convert to profile and choose the sRGB profile. Then save your image.
Now, posting your screenshots this way, they will appear like there are on the phone. (Depending on how well calibrated is the monitor's member).
2) If you have a photo wallpaper on your computer and want it to appear the same on the phone : choose Menu Edition/Assign a profile, and then choose the phone's profile
- For who can have a profile for its momitor, it's important too to use the Color Management plugin in Firefox ( the only one browser able to manage color profiles )
/
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!! [EDIT 3] !!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
There was a problem with some colors with previous color profiles.
When applying profile in photoshop with this V3 color profile :
- Select profile
- Untick Keep RGB numbers
- Select Relative color
- Tick Black point compensation
Now you will see in PS the colors like they will appear on your SG3 !
/
/
noob question
can u explain it in a simple language and wat is it exactly?
wat changes in phone and how to apply it..
vikraam said:
can u explain it in a simple language and wat is it exactly?
wat changes in phone and how to apply it..
Click to expand...
Click to collapse
Color Management is not an easy thing to understand at all. It can be a sbject of PhD ! And my bad english does not help to explain ...
The profile is usefull for who makes themes (it's not to implement into the phone):
-When you work on android's images in photoshop, what you see is not what you see when it is on the phone.
-With the profile you can :
--> See in photoshop what you will see when the image will be on your phone. It helps a lot ! Before making the pofile I was making changes, pushing them to the phone and then going back to photoshop (it was looking good in photoshop but not on the phone)
--> When you take a screenshot on the phone, the image is raw without any color profile, ugly ! Applying my profile you can visualize the screenshots on your computer like it appears looking at the phone. It's good to apply the profile to the screenshots before posting. At the present time the screenshots available on the forum does not correspond to reality. I will add a small tutorial to do that.
you get it ?
ok now i understood it. Im learning to make themes actually. So this wil help me
vikraam said:
ok now i understood it. Im learning to make themes actually. So this wil help me
Click to expand...
Click to collapse
I hope so ! See if someone or some store can lend/rent you a colorimeter to calibrate your monitor. I can warranty that this will change your editing experience ! You will be surprised visualizing your photos ...
Unfortunately, monitors even high-end, are sold without being calibrated .... The Delta can be very huge !
all i see in the 2 screenshots is that one is brighter than the other
i dont get it
in 1 post u say we can view the images before pushin it in the phone
n the other post u say it improves ur viewing experience like improves the quality??
i m viewing these photos on a netbook i dont if that makes a difference
so if u could please explain me again
AacidD said:
all i see in the 2 screenshots is that one is brighter than the other
i dont get it
in 1 post u say we can view the images before pushin it in the phone
n the other post u say it improves ur viewing experience like improves the quality??
i m viewing these photos on a netbook i dont if that makes a difference
so if u could please explain me again
Click to expand...
Click to collapse
Color management is a headache subject ...
The purpose is to get the same visual result on the phone and on the computer. The fact is that you don't have my phone so you can't see that the second picture looks like the phone and not the first one.
Actually, your case is not surprising : in general (90% ?) netbook's screens are very bad (poor color range and very sensible depending on what angle you are looking it) and of course non calibrated. So it's not a surprise you're not viewing a lot of diference.
Even like that, if you can calibrate your netbook screen there will be a significant improvment to view photos and other stuff.
Thanks!
I've been trying to solve different looking colors problems for a while now.
How did you create the profile?
undsoft said:
Thanks!
I've been trying to solve different looking colors problems for a while now.
How did you create the profile?
Click to expand...
Click to collapse
I'm pleased to know someone is using this profile and finding it usefull !
It was'nt easy to make it :
- 1st, I ran Basiccolor display calibration soft with my Spyder 3 colorimeter, on my computer screen, and make screenshot of each pattern color.
- then I put the images on my sdcard's phone
- then search for an image viewer able to switch picture by clicking a button. I found one where you can configure the button you want to use.
- then, ran calibration soft on computer, holding colorimeter on the screen phone and clickin the button just in time (at each color measure).
I will not do that again !
V3 profile available
UP !
see first post [EDIT 3]
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