galaxy

I am trying to test my Android apps in my Samsung Galaxy S i9000 but I dont know why, I cant. It doesn't appear in the Devices tab on Eclipse. I've downloaded the Google Drivers via SDK Manager, I've got the Samsung Drivers for Windows x64, I've put it in debugging mode, and still nothing. This is weird, because some time ago, but in another computer, I was able to do this with my old Xperia X8 and Nexus S, with no problem. This phone is rooted and has a MIUI Rom on it, but my old phones were rooted and had cooked rooms too, and worked perfectly. Am I missing something? Thanks a lot! On your

I'm currently working on the web app which use medium-dpi in viewport meta tag like the below. <meta name="viewport" content="initial-scale=1.0, maximum-scale=1.0, minimum-scale=1.0, width=device-width, user-scalable=no, target-densitydpi=medium-dpi" /> When I test it on a galaxy S3 device, viewport seems not work correctly. I saw this kind of thing in Android 4.0.2. In android 4.0.2, i heard android OS itself has bug that can't apply the viewport correctly. Anybody has any idea?? I actually found an important clue. http://developer.android.com/guide/webapps/targeting.html " values less than

I reinstalled Windows 7 last week and unzipped Eclipse and reinstalled the SDK again, but I didn't run the program in Eclipse. When I connect the Galaxy phone to my computer, Eclipse shows an error and frequently writes in the console tab Failed to start monitoring 0A3C202B1601A00A . After a while, Eclipse qill show an Android Device Chooser window. I can't select 0A3C202B1601A00A . I use ADB and i write adb address and adb devices in cmd, cmd writes deamon not running. When I disconnect the phone from my computer and I want to run the program with an emulator, the program won't run and when I

I have a custom camera in the app and the images that are taken on most of the devices look good but on galaxy nexus the story is different. Images are blurry in Galaxy nexus. I see grainy lines on Motorola Atrix as well. But Droid X, Droid Razr, HTC Evo, HTC incredible are showing good results. Any idea why it would happpen? This is what I have so far. P.S.: I am using Auto focus in the activity. public class CameraPreview extends SurfaceView implements SurfaceHolder.Callback { private SurfaceHolder mHolder; private Camera mCamera; public CameraPreview(Context context, Camera camera) { super

The Samsung Galaxy S4 shows a very weird behavior when going into ACtionMode on my app which is using SupportActionBar from Support-v7. Has anyone an idea how to fix this? I guess the issue comes from Samsung custom Android-Rom. I solved this changing the parent of my custom actionmode theme from: <style name="MyApp.Widget.ActionMode" parent="@style/Widget.AppCompat.ActionMode"> to: <style name="Apo.Widget.ActionMode" parent="@style/Widget.AppCompat.Light.ActionMode.Inverse"> For some reason those themes don't seem valid in the latest AppCompat libraries (I tried Widget.AppCompat.ActionMode

Galaxy s4 Screen: 4.99", 1920x1080 (FullHD). Which the res folder would be used in FHD and what's the dpi value should be set? xhdpi or xxhdpi? And how can I calculate it? I didn't find any info in the developer docs and in the screens_support article It's 441 dpi, isn't it? So almost certainly xxhdpi, which is already supported in the Android framework. But why worry about it at this time? Assuming you're already supporting xhdpi, the likelihood that the average user can detect the different between xhdpi and xxhdpi assets is becoming increasingly small. -- Edit -- Actually, I'd say it's

Android源代码为Galaxy nexus 编译 作者：JAROD 发布时间：JULY 29, 2012 分类： 原创技术 google发布了Android 4.1的代码，但是不包含蓝牙、wifi、显卡等驱动，google将这些驱动单独提供下载，并未集成到源码中，所以需要将其编译进rom中，步骤如下： 编译完成后会在android_souce/out/target/product/maguro/中生成一大堆img文件，这就是编译生成的刷机rom了 然后打开https://developers.google.com/android/nexus/drivers，下载Galaxy Nexus对应的4个文件并解压到源代码的目录，解压出来的4个文件是4个shell脚本，分别为extract-broadcom-maguro.sh，extract-imgtec-maguro.sh，extract-invensense-maguro.sh，extract-samsung-maguro.sh 分别执行这4个脚本，执行期间会要求输入“I ACCEPT” 重新执行make -j4进行编译，这次编译过程时间很短 完成上面的驱动集成后，可以把编译好的img拿到windows下面去刷机，也可以参照下面的方法在linux下刷： 输入 cd android_source/out/host/linux-x86