Ok, I've already tried regular Kies and it could not detect the Vibrant, so I've browsed around and decided to try Kies Mini. It does recognize the Vibrant but it crashes right afterwards. I read online this happened to some people but I didn't find any solutions. Did anyone fix this?
I keep having the same problem also.
Sent from my SGH-T959 using XDA App
same here on windows 7 64 bit
Kies Mini crashes
I had that issue. Make sure to end all applications and use the TouchWiz launcher. Also, use a 32-bit machine because this worked for me when I switched from a 64-bit one.
I'm having the same problem on Win7 x86. Here's a copy of the actual error Windows gives me:
Problem Event Name: APPCRASH
Application Name: AMiniLauncher.exe
Application Version: 1.0.0.1
Application Timestamp: 4d22b28a
Fault Module Name: WININET.dll
Fault Module Version: 9.0.7930.16406
Fault Module Timestamp: 4c7e044e
Exception Code: c0000005
Exception Offset: 0000e958
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Any ideas????
Oryon007 said:
I'm having the same problem on Win7 x86. Here's a copy of the actual error Windows gives me:
Problem Event Name: APPCRASH
Application Name: AMiniLauncher.exe
Application Version: 1.0.0.1
Application Timestamp: 4d22b28a
Fault Module Name: WININET.dll
Fault Module Version: 9.0.7930.16406
Fault Module Timestamp: 4c7e044e
Exception Code: c0000005
Exception Offset: 0000e958
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Any ideas????
Click to expand...
Click to collapse
uninstall IE9. Worked instantly!!!!!!!!!!!!
the solution i found...
in my searching, i found that it depends on what version of kies you use. anything after 1.5.1, i have had problems with. i presently run version 1.5.1.10074.2.6 and it works great. the only problem is don't ever update it or it won't work, lol!
you can google the version number and download it. hope this helps you out...
ps: make sure you fully uninstall all previous versions of kies and mini kies from your pc, then restart your desktop before installing this version!
Related
i install new version of eclipse and Android sdk , but when i run an android project i get this error
Code:
Could not open Selected VM debug port (8700). Make sure you do not have another instance of DDMS or of the eclipse plugin running. If it's being used by something else, choose a new port number in the preferences.
ADB server didn't ACK
* failed to start daemon *
i try to solve the problem by following this , but i still get the same problem:
Code:
-Window -> Preferences -> Android -> DDMS
-Set Base local debugger port to "8601"
- Check the box that says "Use ADBHOST" and the value should be "127.0.0.1"
i am also tryng to reinstall android pluing for ecipse and even the android sdk , but i still get the same problem , any help !
OS : debian6 x64bit
IDE : eclipse juno
thanks in advance !
Hi guys,
I`m facing the problem since last kies update. When I connect device via wi-fi to PC, kies air message show notification that device is connected and everything is perfect, but when I try to compose message or explore a contacts, I receive an error with "service not responding" -> "check solution online and close program". Tried to install older version of Kies, but it didn`t help.
I`m running W7 and JB 4.1.1 on mobile.
Can anyone suggest something?
Oh almost forgot, here`s log:
Problem signature:
Problem Event Name: BEX
Application Name: KiesAirMessage.exe
Application Version: 1.0.0.0
Application Timestamp: 5091e8cf
Fault Module Name: KiesAirMessageCtl.dll
Fault Module Version: 1.0.0.0
Fault Module Timestamp: 5091e8c9
Exception Offset: 000ea027
Exception Code: c0000417
Exception Data: 00000000
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1063
Additional Information 1: 0702
Additional Information 2: 07026e53635cb069580e8f0fa78513c7
Additional Information 3: ed87
Additional Information 4: ed874063ade0aa215128db54538f175e
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
Hey guys,
This is my first time developing apps for a device, please don't be too callous.
Prior to the release of Android Studio I was having a crack at eclipse with the android SDK and attempting to utilise the AVD simulator rather than the actual Galaxy Nexus I have right beside me. My issue was in fact the same as to when I converted to Android Studio, a rather consistent error:
Code:
Waiting for device.
C:\Android\android-studio\sdk\tools\emulator.exe -avd GalaxyNexus -netspeed full -netdelay none
Device connected: emulator-5554
Device is online: emulator-5554
Target device: emulator-5554 (GalaxyNexus)
Uploading file
local path: C:\Ryan\Android\MyFirstApp\build\apk\MyFirstApp-debug-unaligned.apk
remote path: /data/local/tmp/com.example.myfirstapp
Adb Transfer Protocol Error.
No such file or directory
The AVD Simulator boots up, Android Labels displays then fails after a matter of seconds. i understand the issue is obviously not related to the IDE hence why both eclipse and Android Studio are doing the same thing.
I Created an AVD with the following Properties:
Code:
Name: GalaxyNexus
Device: Galaxy Nexus (4.65"...etc
Target: Android 4.2.2 - API Level 17
CPU/ABI: greyed out as "ARM..."etc
Keyboard enabled
Skin enabled
Front Camera None
Rear Camera None
Memory options
- Ram: 512
- VM Heap: 64
- Internal Storage: 8 GiB
- SD 128MiB
Emulation options both left unchecked
Greyed out button for "Override the extisting AVD with the same name"
The basic default hello world app actually runs fine on my galaxy nexus on 4.2.2.
Not sure of my issue, I would assume configuration, though couldn't be sure.
Thanks ahead.
ryanspacef said:
Not sure of my issue, I would assume configuration, though couldn't be sure.
Thanks ahead.
Click to expand...
Click to collapse
Go to SDK Manager and hit the Install button. Mine still had 5 missing packages, including the ARM ABI, which would also explain why the AVD didn't boot. Hope this helps.
ryanspacef said:
Hey guys,
This is my first time developing apps for a device, please don't be too callous.
Prior to the release of Android Studio I was having a crack at eclipse with the android SDK and attempting to utilise the AVD simulator rather than the actual Galaxy Nexus I have right beside me. My issue was in fact the same as to when I converted to Android Studio, a rather consistent error:
Code:
Waiting for device.
C:\Android\android-studio\sdk\tools\emulator.exe -avd GalaxyNexus -netspeed full -netdelay none
Device connected: emulator-5554
Device is online: emulator-5554
Target device: emulator-5554 (GalaxyNexus)
Uploading file
local path: C:\Ryan\Android\MyFirstApp\build\apk\MyFirstApp-debug-unaligned.apk
remote path: /data/local/tmp/com.example.myfirstapp
Adb Transfer Protocol Error.
No such file or directory
The AVD Simulator boots up, Android Labels displays then fails after a matter of seconds. i understand the issue is obviously not related to the IDE hence why both eclipse and Android Studio are doing the same thing.
I Created an AVD with the following Properties:
Code:
Name: GalaxyNexus
Device: Galaxy Nexus (4.65"...etc
Target: Android 4.2.2 - API Level 17
CPU/ABI: greyed out as "ARM..."etc
Keyboard enabled
Skin enabled
Front Camera None
Rear Camera None
Memory options
- Ram: 512
- VM Heap: 64
- Internal Storage: 8 GiB
- SD 128MiB
Emulation options both left unchecked
Greyed out button for "Override the extisting AVD with the same name"
The basic default hello world app actually runs fine on my galaxy nexus on 4.2.2.
Not sure of my issue, I would assume configuration, though couldn't be sure.
Thanks ahead.
Click to expand...
Click to collapse
Have you tried to push your apps apk manually using the adb push command? If that does not work its probably a driver issue. Also you may try changing the sdcard size to >200mb or removing it altogether and only using internal. I would also use a much smaller internal size unless your app needs it. My AVD has an internal of 256mb and no sdcard and runs fine. The AVDs are very picky and have strange issues sometimes.
I'm trying to install linux (Fedora) ARM packages into chroot environment on Android table (rooted). Everything seems to work fine except all of Qt4 applications. Their GUI windows are not displayed properly being luck of most of elements no matter I use android X server or linux VNC server.
Terminal output shows following error messages
Code:
QNativeImage: Unable to attach to shared memory segment.
X Error: BadPixmap (invalid Pixmap parameter) 4
Major opcode: 56 (X_ChangeGC)
Resource id: 0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62 (X_CopyArea)
Resource id: 0x0
(and so on).
I suppose the problem is shared memory segment. Either android doesn't support request for it or this segment is too small for Qt4. Is there any solution to enable shared memory?
My aims:
- Use Android Studio to develop a basic Android application - should be possible
- Use Android Studio to back up my physical phone (Hisense phone running Nougat 7.0) and create an emulated version of it running on my PC - should be possible, is it?
My PC:
- Windows XP 32-bit
- Pentium Dual Core T2330 processor NOT supporting Intel® Virtualization Technology (VT-x)
- 2 GB RAM
Questions:
- Are the above aims possible to achieve with my PC?
- If yes, what are the recommended Android Studio and Java SE Development Kit versions/settings to use that work for sure?
Story: I have tried to use Android Studio 3.0.1 with various versions of Java SE Development Kit 8 (including 121, 144, and 152) and various settings/hacks constantly running into various bugs/issues, most of which were seemingly resolved by new settings/hacks, yet I ended up with the same error messages after I have tried everything I have found online that nice people suggested on forums.
I am unable to even compile and run a default Android app, I get these error messages:
Gradle build finished with 2 error(s) in 21s 591ms
Error:java.util.concurrent.ExecutionException: java.lang.RuntimeException: No server to serve request. Check logs for details.
Error:Execution failed for task ':app:mergeDebugResources'.
> Error: java.util.concurrent.ExecutionException: java.lang.RuntimeException: No server to serve request. Check logs for details.
I am unable to run a default-loaded Android Virtual Device, I get this error message:
Emulator: Process finished with exit code -1073741511 (0xC0000139)
I am clueless how to continue. If my aims are possible to achieve, could someone tell me the Android Studio and JDK versions and settings that work 100% under 32-bit Win XP?
Thanks in advance!