galaxy

Samsung Galaxy S4 and Phonegap Issue

喜欢而已 提交于 2019-12-04 13:51:18
问题 I'm writing an app using Phonegap, the app includes using HTML5's canvas. When I run the app on Eclipse's Android Emulator, everything works fine (slow but working). When I connect the Galaxy S4 and run the app, it loads, shows the canvas well, but after few second the whole screen turns blue. I have placed javascript's alert();'s and they seem to work after the screen turns blue, but still the app can't be used anymore.. The Galaxy S4 uses Android 4.2.2. from Eclipse, I run it as version 2.2

How to get the correct window width on orientation change for android devices both tablets and mobiles

天涯浪子 提交于 2019-12-04 08:22:55
I am trying to calculate the window width on orientation change for android devices using jquery function $(window).outerWidth(true); . This calculation gives correct width on orientation change for both iphone and ipad but not in android. If i initially load the page in landscape mode or portrait mode i am getting the correct width but once i change the orientation after loading the page i am getting the width for portrait mode as was in landscape mode and vice versa. Please suggest what is happening and how can i handle this issue so that i get the correct window width on orientation change

Video display is garbled when recording on Galaxy S3

让人想犯罪 __ 提交于 2019-12-04 07:31:01
I'm writing a camera app and am having an issue with the S3. Whenever I start recording, the display goes to garbage (see screenshots below). Then, when I stop recording I get an exception: 10-02 13:36:31.647: E/MediaRecorder(24283): stop failed: -1007 10-02 13:36:31.647: D/AndroidRuntime(24283): Shutting down VM 10-02 13:36:31.647: W/dalvikvm(24283): threadid=1: thread exiting with uncaught exception (group=0x40c49a68) 10-02 13:36:31.647: E/AndroidRuntime(24283): FATAL EXCEPTION: main 10-02 13:36:31.647: E/AndroidRuntime(24283): java.lang.RuntimeException: stop failed. 10-02 13:36:31.647: E

ACTION_IMAGE_CAPTURE orientation problem on Nexus S and Samsung Galaxy S I9000

懵懂的女人 提交于 2019-12-04 05:13:59
I'm trying to shoot picture and store it into internal storage by using the following code: Intent intent = new Intent(android.provider.MediaStore.ACTION_IMAGE_CAPTURE); takenPhoto = new File(uploadsFolder, getNewPicFileName()); intent.putExtra(MediaStore.EXTRA_OUTPUT, Uri.fromFile(takenPhoto)); startActivityForResult(intent, SHOOT_MEDIA_REQUEST_CODE); The problem is that on Nexus S and Galaxy S devices default and the single orientation for ACTION_IMAGE_CAPTURE intent is landscape. If i shoot picture in portrait mode, that picture is stored into "takenPhoto" file rotated. That problem seems

Path of getExternalStoragePublicDirectory on Samsung Galaxy Note

时间秒杀一切 提交于 2019-12-04 01:11:31
问题 In my app, I am creating files which are stored in the devices Downloads directory. All of my users are happy with this mechanism... except the ones using a Samsung Galaxy Note. It's kind of hard to debug without owning such a device. Within my code, I am using File newFile = new File(Environment.getExternalStoragePublicDirectory(Environment.DIRECTORY_DOWNLOADS), "file01"); if (newFile.exists()) { // show error } else { if (!newFile.mkdirs()) { // show error } } to find the path for the

Samsung Galaxy Note III emulator settings

 ̄綄美尐妖づ 提交于 2019-12-03 21:53:25
问题 I am porting my iPhone app over to android and the client uses Samsung Galaxy Note III . I need to create an emulator to help with the debugging, but I am getting problems in starting the emulator with the settings I got from gsmarena. There are similar posts but they are of Samsung Galaxy Note II and also used old AVD. What should be selected in AVD ( Device and Target )? I also did some changes and my final settings came up to be: Emulator AVD- Device: 1080 x 1920:xhdpi Target: Google API's

Issue with Samsung Galaxy SIII - Camera.onPictureTaken() returning interlaced image instead of proper capture image

痴心易碎 提交于 2019-12-03 21:44:19
We have an application that utilizes the rear 'Camera' to capture item image. So far all devices that we have tested are all working correctly in term of capturing image as it should be, until Samsung Galaxy SIII (S3). On Samsung Galaxy SIII only, we are observing that Camera.onPictureTaken() is returning an raw image appears to interlaced instead of proper capture image. Debugging each of camera parameter setting, determine that the following parameter setter is causing the issue. If we don't explicitly setPictureSize() on parameter, then it is working as expected: parameters.setPictureSize

android gridview crashes on Galaxy 3

空扰寡人 提交于 2019-12-03 18:03:32
问题 Ok, I think I have a real question for a change. I implemented a gridView in Android, following step by step the instructions in the Android Developers page, http://developer.android.com/resources/tutorials/views/hello-gridview.html I changed it so that when clicking on a view, the bitmap will be returned. This all works great on advanced phones like Galxy Note and Galaxy S2, and on less advanced ones like Galaxy ace and even some crappy htc from 2 years ago. But for some reason, it crashes

Input error with keyboard on Galaxy S2 using jQuery Mobile and Phonegap

假如想象 提交于 2019-12-03 16:58:26
问题 We are developing a mobile web app in jQuery Mobile 1.0.1 and Phonegap 1.4.1 and have run into issues with the keyboard on the galaxy s2. We have a menu which slides out and contains a search input: <input type="search" placeholder="Search..." name="search" id="menu_search" data-role="none" /> When we tap in the input so that it gains focus, the keyboard opens but does not allow us to type anything in. I guess a clue here is that its giving us a regular text keyboard and not the search

Samsung Galaxy S2 2.3.5+ not calling overScrollBy()

*爱你&永不变心* 提交于 2019-12-03 13:01:05
Seems like Samsung disabled their overscroll (probably due to an Apple suit). I have an implementation of a view that extends ScrollView and overrides protected boolean overScrollBy(int deltaX, int deltaY, int scrollX, int scrollY, int scrollRangeX, int scrollRangeY,int maxOverScrollX, int maxOverScrollY, boolean isTouchEvent) { ... return super.overScrollBy(deltaX, deltaY, scrollX, scrollY, scrollRangeX, scrollRangeY, 0, metrics.widthPixels,isTouchEvent); } On every other device (Gingerbread and up of course), overScrollBy is being called when the scroller reaches it's end, and the user can