samsung-mobile

I am trying to implement FingerPrint Scanner in my app. I followed below tutorial: http://www.techotopia.com/index.php/An_Android_Fingerprint_Authentication_Tutorial In Samsung Note 4, FingerPrintManager's isHardwareDetected() is returned as false even though I successfully registered two fingerprints from Settings. Does anyone of you know what might be the reason? Thanks. I'm afraid the Note 4 doesn't support the Fingerprint API (just the Samsung Fingerprint). You should try your code with another device if possible. The issue is with the implementation of the Fingerprint scanner in some old

We recently bumped the minSdkVersion of our app from 16 (Jellybean) to 21 (Lollipop). Although we did extensive testing with our app predominantly using debug builds, we are now facing a slew of production crashes at app startup, predominantly on older Samsung devices - (Note3 and S4 are the top crashers) and always on Lollipop. The error is Fatal Exception: java.lang.NoClassDefFoundError: com.retailconvergence.ruelala.delegate.GoogleLoginDelegate at com.retailconvergence.ruelala.delegate.LifecycleDelegateManager.addDelegateOfType(LifecycleDelegateManager.java:48) at com.retailconvergence

I have an web application where mobile phone users see a mobile optimized website. The new Samsung Galaxy SIII user agent provides no clue that the request is coming from a mobile phone. What are the best pratices to detect mobile phones? I'm aware of javascript feature detection (ie. modernizer) but am hoping for something better. Below is the Samsung Galaxy SIII user agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.34 Safari/534.24 EDIT: The SIII has two possible user agents. Above is the 'desktop' version. Fun stuff. See link below for details.

My app needs to show the current bearing of the device using its compass. The code I'm using (below) works perfectly fine on my Galaxy Nexus and Galaxy One, but the compass is spinning around wildly on a Samsung Galaxy S III. I've tried doing a figure-8 to recalibrate the device, but that doesn't change anything. The weird thing is that other compass apps downloaded from Google Play work just fine on the SIII. What could be the issue here? float[] mGravity; float[] mGeomagnetic; public void onSensorChanged( SensorEvent event ) { float azimuth = 0f; if (event.sensor.getType() == Sensor.TYPE

I am having a really odd issue. I have a Phonegap 2.0 app that is basically completed. It is working on iPhone and iPad and I ported it over to Android in a day, testing it on my Galaxy S. Everything worked perfectly. Then I tried to run it on my brand new S3 and none of the touch events worked. Clicks work, but not touch. If I run this code document.addEventListener('touchstart', function (e) { console.log('touch start')}, false); document.addEventListener('click', function (e) { console.log('doc click'); }, false); ... only the click events logs. If I comment out the click I get nothing but

Whenever I open my android app it triggers the game mode/game launcher on samsung galaxy s8. But the app isn't a game. In a previous version the app used opengl and it seems like samsung treats an app as game if it uses opengl. I already removed the opengl code but samsung still treats the app as game. The strange thing is when I change the application-id the app launches normally. So, I think samsung stores the application-id as game somewhere. Anyone ever had a similar problem with samsung game launcher? I was having the same problem and I resolved it by changing app.json package to