I can't connect to Kies. It tells me to switch device in PC studio mode ??
Device is in Usb debugging mode, rooted (with another pc).
When connecting in Eclipse, i got some errors.
[2011-06-10 11:31:34 - ] ------------------------------
[2011-06-10 11:31:34 - ] Android Launch!
[2011-06-10 11:31:34 - ] adb is running normally.
[2011-06-10 11:31:34 - ] Performing xxxxxxxxxxxxxxxxxxxxx activity launch
[2011-06-10 11:31:34 - ] Automatic Target Mode: using device '304D19D8533A935E'
[2011-06-10 11:31:34 - ] Uploading xxxx.apk onto device '304D19D8533A935E'
[2011-06-10 11:31:34 - ] Failed to install .apk on device '304D19D8533A935E': Unable to open sync connection!
[2011-06-10 11:31:34 - ] java.io.IOException: Unable to open sync connection!
[2011-06-10 11:31:34 - ] Launch canceled!
In fact it seems that if Eclipse is launched, adb logcat doesn't work anymore. Very strange
[2011-06-10 11:45:05 - ] ------------------------------
[2011-06-10 11:45:05 - ] Android Launch!
[2011-06-10 11:45:05 - ] adb is running normally.
[2011-06-10 11:45:05 - ] Performing xxxxxxxxxxxxxx activity launch
[2011-06-10 11:45:05 - ] Automatic Target Mode: Unable to detect device compatibility. Please select a target device.
[2011-06-10 11:45:07 - ] WARNING: Unknown device API version!
[2011-06-10 11:45:07 - ] Uploading xxxxxxxxxxx.apk onto device '304D19D8533A935E'
[2011-06-10 11:45:07 - ] Failed to install xxxxxxxxxxxxxxx.apk on device '304D19D8533A935E': Unable to open sync connection!
[2011-06-10 11:45:07 - ] java.io.IOException: Unable to open sync connection!
[2011-06-10 11:45:07 - ] Launch canceled!
Someone has any idea ?
I supposed it's a driver problem, but how to update ?
Try turning USB Debugging mode off, you should then connect to Kies. I personally never use Kies so have USB Debugging on so I can mount the phone.
Ok it installed me some drivers more.
Kies IS OK.
But if i switch to usb debugging on, i still got problems in Eclipse.
[2011-06-10 12:25:23 - adb]
[2011-06-10 12:25:23 - adb]This application has requested the Runtime to terminate it in an unusual way.
[2011-06-10 12:25:23 - adb]Please contact the application's support team for more information.
[2011-06-10 12:25:28 - Logcat]null
com.android.ddmlib.TimeoutException
at com.android.ddmlib.AdbHelper.read(AdbHelper.java:648)
at com.android.ddmlib.AdbHelper.read(AdbHelper.java:616)
at com.android.ddmlib.AdbHelper.readAdbResponse(AdbHelper.java:216)
at com.android.ddmlib.AdbHelper.executeRemoteCommand(AdbHelper.java:378)
at com.android.ddmlib.Device.executeShellCommand(Device.java:284)
at com.android.ddmuilib.logcat.LogPanel$3.run(LogPanel.java:527)
when trying to get logcat, and also got problems when trying to pull my app on device. But my device shows in the 'Device' eclipse tab...
So impossible for me to use it for my devs... :/
Nobody has experienced the same problems?
I'm still stuck with this, any ideas ?
TyphZ said:
I'm still stuck with this, any ideas ?
Click to expand...
Click to collapse
Does it show in cmd prompt with -devices ?
What rom? Build date?
What OS and version (Windows 7 i take it?)
I use sgs2 ke7 constantly for testing dev stuff quick so not sure why you should be so special
I use it mainly on OSX and Linux, with the latter I had to add vender USB permissions to the USB module but thats it.
Take it you got it sorted?
Rom v. = XWKE2
C:\Users\gbe>adb devices
List of devices attached
304D19D8533A935E device
(only the SGS2 is connected to my PC)
I'm using WIN 7 PRO.
I don't know why, but now it works, i didn't changed anything, even reboot (just hibernate...)
It will stay a mystery i think....
TyphZ said:
Rom v. = XWKE2
C:\Users\gbe>adb devices
List of devices attached
304D19D8533A935E device
(only the SGS2 is connected to my PC)
I'm using WIN 7 PRO.
I don't know why, but now it works, i didn't changed anything, even reboot (just hibernate...)
It will stay a mystery i think....
Click to expand...
Click to collapse
On win7 I can replicate all sorts of things by using hibernation, usb probs, sound problems, cause sometimes it doesn't sleep resources or wake them up as it should. So could be that
I have the same problem on rooted sgs2 and windows xp. Have you found a solution?
deanwray said:
On win7 I can replicate all sorts of things by using hibernation, usb probs, sound problems, cause sometimes it doesn't sleep resources or wake them up as it should. So could be that
Click to expand...
Click to collapse
yup, I can run the kies on win 7 too,there have not any problem when I root my galaxy S II, maybe is the compatibility problem?!
update ur windows by windows updater in control panel or by clicking right click on my computer u will find additional updates there and thr u can see MTP DRIVERS for S2 after installing it u can reconnect ur device
Related
I've got ADB 1.0.26 running on my Windows 7 x64 and Eclipse SDK 3.6.2 with ADT 10.0.1 SDK tools r10, and I've got all the Android SDK versions installed.
When I connect my phone to the computer in debug mode, and type `adb devices` into the command prompt, my phone shows up. It's an Inspire 4G. I can `adb shell` into the device and `ls`, so I'm assuming that the adb/driver/phone part of the chain is working properly.
Now, if I connect my phone and go into Eclipse, I get:
[2011-03-28 17:46:33 - DeviceMonitor]Adb connection Error:An existing connection was forcibly closed by the remote host
[2011-03-28 17:46:34 - DeviceMonitor]Connection attempts: 1
[2011-03-28 17:46:36 - DeviceMonitor]Connection attempts: 2
Click to expand...
Click to collapse
[...etc...]
[2011-03-28 17:47:53 - DeviceMonitor]Connection attempts: 10
[2011-03-28 17:46:54 - DeviceMonitor]Connection attempts: 11
[2011-03-28 17:47:00 - adb]
[2011-03-28 17:47:00 - adb]This application has requested the Runtime to terminate it in an unusual way.
[2011-03-28 17:47:00 - adb]Please contact the application's support team for more information.
[2011-03-28 17:47:04 - DeviceMonitor]Adb connection Error:An existing connection was forcibly closed by the remote host
[2011-03-28 17:47:05 - DeviceMonitor]Connection attempts: 1
[2011-03-28 17:47:07 - DeviceMonitor]Connection attempts: 2
Click to expand...
Click to collapse
etc, etc... This loops forever.
It doesn't matter if I start Eclipse and then connect the phone, or if I connect the phone and then start Eclipse.
I don't think it should matter, but my phone is an Inspire 4G which is rooted and running Revolution 4G 3.2
As suggested somewhere else, I've tried resetting ADB in DDMS but that has no effect.
i have the same problem... can anyone help me please?
This happens to me too sometimes.
To solve this I have to this:
- close the IDE (in your case Eclipse... )
- open up cmd, and type: adb kill-server
- Start Eclipse and it should work again
http://code.google.com/p/android/issues/detail?id=12141
The Android device in question is a Micromax A87(a relatively unknown brand in global market but I hope that should'nt matter).
In Ubuntu, I have double checked the udev rules. They all look perfect. (I cross checked using another phone too). The USB debug mode doesn't show up no matter what. And I have the adb_usb.ini in the right place. I have tried running all possible combinations of running
adb, adb start-server as root. But
Code:
adb devices
shows no devices at all.
However, with the USB debugging option enabled on phone, it worked on Win7 after windows installed a Common handset driver.
Now the interesting part.
If I go back to Ubuntu without disconnecting the cable and do
Code:
$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[B]1234567890ABCDEF[/B] device
The product id is 1234567890ABCDEF and I am able to see it and everthing works fine!!
But the moment I disconnect the USB cable, its gone.
So I guess it's not the development machine that is at fault. The device seems to be setting a property while in Windows which stays latched till the usb connection goes off.
What could be a way to get this to work? (Besides developing on Windows :silly: )
Btw the
Code:
/data/property/persist.service.adb.enable
is 1 too.
What is your computer setup? Are you using a Windows machine, with Ubuntu in a vm? Dual-boot? Other?
My setup:
Dual boot.
Ubuntu 12.04 and Windows 7.
Ok, how about if you plug in the USB with the computer's power off, then boot into Ubuntu?
i have the clone of this phone. mine is Mito A78.
lsusb command shows it as 1c9e:9e08
so idVendor =1c9e and idProduct = 9e08
for now, what you say (plugin to windows and reboot to ubuntu without unplug the phone) is the solution.
i will see if lsusb output still the same.
okay, have checked on windows pc, it should be switched to idVendor =1c9e and idProduct = 9e18
anyway, what you say is a clue that the solution may be around usb_modeswitch and modem manager
further search on usb_modeswitch 1c9e 9e08 found the solution here: http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=3&t=1351
have tried, but not yet switched to idVendor =1c9e and idProduct = 9e18
have to find the correct rules on /etc/usb_modeswitch.d/1c9e:9e08
Code:
########################################################
# Mito A78
DefaultVendor=0x1c9e
DefaultProduct=0x9e08
TargetVendor=0x1c9e
TargetProduct=0x9e18
SierraMode=1
CheckSuccess=20
NoDriverLoading=1
found it.
after writing the rules, insert
Code:
# Mito A78
ATTR{idVendor}=="1c9e", ATTR{idProduct}=="9e08", RUN+="usb_modeswitch '%b/%k'"
to /lib/udev/rules.d/40-usb_modeswitch.rules
i than have to run
Code:
sudo usb_modeswitch -v 0x1c9e -p 0x9e08 -S -R -W
and then the phone switched to idVendor =1c9e and idProduct = 9e18 and adb can access the phone.
:good: :good: :good:
I-mobile IQ 5.1 has same issue, but adb still can't see device
The usb_modeswitch is exactly the same for this phone (same usb vid/pid). However adb still doesn't find the phone under Windows and Ubuntu. lsusb shows the product id switch did work and it all looks right.
Under windows it spins up a cdrom device from the phone so you can install the windows drivers (this lives as an *.iso file under /system); after the driver install, you get the adb device in device manager and two com ports,with all devices having a pid of 9e18 (original 9e08). However adb does not see the device!
I recon there is something wrong on the phone side. This is a very new phone (only release about 5 days ago), so I suspect this is one of the early release bugs...
Since I don't even have a custom recovery for it (CWM, etc) I can even backup my phone and try and do a factory reset.
Looks like a low level USB issue
Switched on tracing on adbd on the phone side. Looks like a phone/usb low level issue:
Code:
--- adb starting (pid 14270) ---
system/core/adb/adb.c::main():Handling main()
system/core/adb/adb.c::adb_main():Local port disabled
system/core/adb/usb_linux_client.c::usb_init():failed to open /dev/android_adb_enable
system/core/adb/usb_linux_client.c::usb_init():[ usb_init - starting thread ]
system/core/adb/adb.c::adb_main():adb_main(): pre init_jdwp()
system/core/adb/jdwp_service.c::jdwp_control_init():jdwp control socket started (5)
system/core/adb/adb.c::adb_main():adb_main(): post init_jdwp()
system/core/adb/adb.c::adb_main():Event loop starting
system/core/adb/usb_linux_client.c::usb_open_thread():[ usb_thread - opening device ]
system/core/adb/usb_linux_client.c::usb_open_thread():[ opening device succeeded ]
system/core/adb/usb_linux_client.c::usb_open_thread():[ usb_thread - registering device ]
system/core/adb/transport.c::register_usb_transport():transport: 0x11364a0 init'ing for usb_handle 0x1136410 (sn='')
system/core/adb/transport_usb.c::init_usb_transport():transport: usb
system/core/adb/transport.c::register_transport():transport: (null) registered
system/core/adb/transport.c::transport_registration_func():transport: (null) (10,11) starting
system/core/adb/transport.c::output_thread():(null): starting transport output thread on fd 11, SYNC online (2)
system/core/adb/transport.c::dump_packet():fd=11: to remote: [SYNC] arg0=1 arg1=2 (len=0)
system/core/adb/transport.c::transport_socket_events():transport_socket_events(fd=10, events=0001,...)
system/core/adb/transport.c::dump_packet():fd=10: from remote: [SYNC] arg0=1 arg1=2 (len=0)
system/core/adb/adb.c::handle_packet():handle_packet() SYNC
system/core/adb/transport.c::dump_packet():fd=10: to remote: [SYNC] arg0=1 arg1=2 (len=0)
system/core/adb/transport.c::output_thread():(null): data pump started
system/core/adb/usb_linux_client.c::usb_read():about to read (fd=9, len=24)
system/core/adb/transport.c::input_thread():(null): starting transport input thread, reading from fd 11
system/core/adb/transport.c::dump_packet():fd=11: from remote: [SYNC] arg0=1 arg1=2 (len=0)
system/core/adb/transport.c::input_thread():(null): transport SYNC online
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 11279 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 11325 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 11818 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 13994 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 13951 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 13913 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 13856 to jdwp process list
system/core/adb/usb_linux_client.c::usb_read():ERROR: fd = 9, n = -1, errno = 5 (I/O error)
system/core/adb/transport_usb.c::remote_read():remote usb: read terminated (message)
system/core/adb/transport.c::output_thread():(null): remote read failed for transport
system/core/adb/transport.c::output_thread():(null): SYNC offline for transport
system/core/adb/transport.c::dump_packet():fd=11: to remote: [SYNC] arg0=0 arg1=0 (len=0)
system/core/adb/transport.c::output_thread():(null): transport output thread is exiting
system/core/adb/usb_linux_client.c::usb_kick():usb_kick
---------- Post added at 04:31 AM ---------- Previous post was at 04:27 AM ----------
I also tried the Chainfire adbd insecure and its exactly the same in the debugging.
Now working on win7 64!
Followed this link and managed to get it working. The PID value was set to 9e18. In essence the andriod usb driver was missing (install via the andriod.bat andriod package manager).
Also works in virtualbox winxp vm on Linux (ubuntu 12.10; actually Mint 14). Just mapped in my win7 64 partition to get access to the andriod sdk/usb driver.
Now that I know its not a handset issue, can return to trying to get the Linux side working.
Now working under Linux!
You need the vendor id in adb_usb.ini:
Code:
cat ~/.android/adb_usb.ini
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1c9e
If you will run adb as root, make sure you also create the file for root too.
Tip: You will be logged into the phone as the 'shell' user. Try and 'su -' to get root access, and then click on your su dialog on the phone to grant access.
Final issue is that plugging in the device should do the switch automatically; I will update you on that when I have that fixed.
udev sorted on ubuntu
Ok, we are rocking on udev on ubuntu 12.10. Seems like udev doesn't like ATTR keywords, although ATTRS makes everything burst into life (man page says ATTR is useable). Steps that worked for me:
Code:
# cp /lib/udev/rules.d/40-usb_modeswitch.rules /etc/udev/rules.d/usb_modeswitch.rules
# vi /etc/udev/rules.d/usb_modeswitch.rules
Add the following entry near the bottom under the last entry:
Code:
# I-Mobile IQ5.1
ATTRS{idVendor}=="1c9e", ATTRS{idProduct}=="9e08", RUN+="usb_modeswitch '%b/%k'"
Create /etc/usb_modeswitch.d/1c9e:9e08 as described earlier by jurban.
Unplug the phone. Plug it in. Do an lsusb. Firstly shows up as dev 1c9e:9e08. Enter lsusb again. Shows up as 1c9e:9e18. Now adb will show the device as jurban shows above. All good to go!
Hello everyone,
I started to port Tizen on Nexus 7.
Porting state:
- wifi working
- touchscreen working (doesn't yet support multitouch)
- media (pictures, music and videos) doesn't work
- no graphics acceleration (Xorg doesn't use Tegra module)
- USB doesn't work
- GPS / Bluetooth not tested
- Audio not tested
Installation:
To install it, you will need an unlocked Nexus 7 and MultiROMv7. MultiROMv7 is a way to have multi boot on Nexus 7. Once Recovery and MultiROMv7 are installed, you must reboot into recovery. Send image on your Nexus 7:
adb push /path/to/image/Nexus_7_Tizen.zip /sdcard/
After click on install button and select Nexus_7_Tizen.zip. It will install Tizen on your Nexus 7. Now you can reboot. In list of ROM, you will see Tizen_Testing. Select it and enjoy.
Download:
MultiROMv7: http://forum.xda-developers.com/showthread.php?t=2011403
Tizen ROM: http://easymt.org/files/Nexus_7_Tizen.zip
In days, I will publish instruction to build the ROM.
If you get this on par with the factory OS then you're a hair away from every nexus device using this if they want. Thank you for the work.
Sent from awesomeness?
Tizen 2.0?
Sent from my One S using xda app-developers app
Wonderful to see people just using MultiROM to create ports like this, good job
A big thank you for your work!
When USB will be avaible,
we can take screenshot from the Tizen SDK
(sdb_1.0.24_ubuntu-64)
Code:
sdb
Smart Development Bridge version 2.0.2
Usage : sdb [option] <command> [parameters]
options:
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 26101 is used by default if no port number is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 26101 is used by default if no port number is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devices.
commands:
sdb push <local> <remote> [--with-utf8]
- copy file/dir to device
(--with-utf8 means to create the remote file with utf-8 character encoding)
sdb pull <remote> [<local>] - copy file/dir from device
sdb shell - run remote shell interactively
sdb shell <command> - run remote shell
sdb dlog [ <filter-spec> ] - view device log
sdb install <path_to_tpk> - push tpk package file and install it
sdb uninstall <appid> - uninstall this app from the device
sdb forward <local> <remote> - forward socket connections
forward spec is :
tcp:<port>
sdb help - show this help message
sdb version - show version num
sdb start-server - ensure that there is a server running
sdb kill-server - kill the server if it is running
sdb get-state - prints: offline | bootloader | device
sdb get-serialno - prints: <serial-number>
sdb status-window - continuously print device status for a specified device
it reminds me of something, but I do not know what
ikslawlok said:
Code:
sdb
Smart Development Bridge version 2.0.2
Usage : sdb [option] <command> [parameters]
options:
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 26101 is used by default if no port number is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 26101 is used by default if no port number is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devices.
commands:
sdb push <local> <remote> [--with-utf8]
- copy file/dir to device
(--with-utf8 means to create the remote file with utf-8 character encoding)
sdb pull <remote> [<local>] - copy file/dir from device
sdb shell - run remote shell interactively
sdb shell <command> - run remote shell
sdb dlog [ <filter-spec> ] - view device log
sdb install <path_to_tpk> - push tpk package file and install it
sdb uninstall <appid> - uninstall this app from the device
sdb forward <local> <remote> - forward socket connections
forward spec is :
tcp:<port>
sdb help - show this help message
sdb version - show version num
sdb start-server - ensure that there is a server running
sdb kill-server - kill the server if it is running
sdb get-state - prints: offline | bootloader | device
sdb get-serialno - prints: <serial-number>
sdb status-window - continuously print device status for a specified device
Click to expand...
Click to collapse
LOL. adb knockoff.
johnwazhere said:
Tizen 2.0?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Actually, it is Tizen 2.0 alpha. I'm porting 2.0.
Thanks for the port! I have a question though, doesn't Nvidia have a (non-Android) Linux code tree for the Tegra 3? Couldn't the video driver from that tree be used? (even though it's for their development tablet from what I've read the socs are identical)
https://developer.nvidia.com/linux-tegra
Sent from my Nexus 7 using Tapatalk HD
Culex316 said:
Thanks for the port! I have a question though, doesn't Nvidia have a (non-Android) Linux code tree for the Tegra 3? Couldn't the video driver from that tree be used?
Click to expand...
Click to collapse
Yes it can be used. The driver work but it enable mice pointer.
Edit:
In fact I can't use it because xorg server and driver abi missmatch.
I probaly need to buimd another version of xorg than provided.
Thanks for your effort in this, very interested in this project. It's amazing to see the amount of operating systems being ported to Nexus 7.
I am extremely distress about the fact that other dev claimed successfuly port tizen to smartphones, also uploaded his work and nobody believe him (just because thefact that his work is rather complicated and no one smart enough to figure out how to do with his roms), you guys even teasing and disrespect him. Now a few months later, this dev put up with his work and an easier cleaner ways to install, these same non believer ppl comes in and appraise like its not a big deal (or lies?) and pretend nothing happened and they havent done nothing? Seriously you guys should do something about your attitide and mental capacity
Sent from my GT-P6800 using xda app-developers app
You're right man.
Anyone believed in him.
I do not know why all this lies telling about his work.
He got several downloads through internet about his work. And no respect at all.
---------- Post added at 06:42 PM ---------- Previous post was at 06:32 PM ----------
I'm going to quit from here xda.
This was a bad experience.
I've released code.google.com/p/tizen-kernel-s8500
a github.com/vic3t3chn0
a twitter.com/vicetechno
for my it works.
now, i'm going to quit for the bad experience at telling me i'm a liar.
but I had downloads at code.google.com if i'm a liar.
thank you for all.
long6688 said:
I am extremely distress about the fact that other dev claimed successfuly port tizen to smartphones, also uploaded his work and nobody believe him (just because thefact that his work is rather complicated and no one smart enough to figure out how to do with his roms), you guys even teasing and disrespect him. Now a few months later, this dev put up with his work and an easier cleaner ways to install, these same non believer ppl comes in and appraise like its not a big deal (or lies?) and pretend nothing happened and they havent done nothing? Seriously you guys should do something about your attitide and mental capacity
Click to expand...
Click to collapse
I don't know who exactly do you mean, but if it is the author of "Tizen [PORT] Attempt almost" thread then you might have not read that thread (or do not know bada/tizen forums) well enough to know that he claimed that he has so many things up and running without bothering to actually try to run it.
When we wanted to know the details it came out that he used many components developed by badadroid team without proper credit and claiming to have functionality that never existed (like working RIL or even stupid lie that he changed a bootlogo in the component that was not responsible for displaying it - to cover this lie he changed one line and provided only the non-working binary violating GPL, but the component was pure assembly we wrote so seeking truth was not difficult) in these components and were known not to be working with Tizen (kernel init not aligned with Tizen).
Looking at the repositories he pointed to, there is no source code he developed or even modified by himself - everything is public and part of other projects.
You are free to elaborate on my mental capacity, but from where I stand his complicated work appears to be limited to the ability to follow compilation instructions.
I don't claim he wanted that to be a scam from the very beginning - he might have had a will to do something and learn along the way (which would be an adequate way), but he chose to cheat where stuff got unmanageable.
While I still encourage everybody to take up the challenge to see how fun it is, but when such a "dev" is leaving XDA we couldn't be worried less. Bon voyage!
Does it take lot of time to boot up? Its showing [ 915.19111] CP L2->L0 and the process is being continued... Cant use power button.
So where does this stand? This is the one OS I want to use more than any other. I dont know jack about compiling code and such. But if someone has this for a N4 I would be all over it like ants on a peach.
This looks cool, I hope this thread doesn't die, I would really like to try Tizen on my nexus
Ubuntu touch is still unusable, but a tizen port could be quite stable, once properly ported
What is the progress of this project?
SuperBoUDS said:
What is the progress of this project?
Click to expand...
Click to collapse
Looks pretty dead. I keep coming back to check if I can get tizen on my s3
Sent from my GT-I9300 using xda app-developers app
...I keep coming back to check if I can get tizen on my s3
Click to expand...
Click to collapse
This is also my question... if S3 is able to use available Tizen Firmware... from testdevices...
Maybe someone can find solution to use Tizen on S3.
Thanx in advance.
Best Regards
adfree said:
This is also my question... if S3 is able to use available Tizen Firmware... from testdevices...
Maybe someone can find solution to use Tizen on S3.
Thanx in advance.
Best Regards
Click to expand...
Click to collapse
I have asked in s3 thread. My post got deleted after a few comments... I was hoping a port for s3 would be easy and quick but there's no development on this whatsoever
Sent from my GT-I9300 using xda app-developers app
Hello guys, I have a little problem with developing apps in my phone.
I installed Stock Android 4.1.2 v4 for my Xperia U ST25i ( http://forum.xda-developers.com/showthread.php?t=2284394 ) (I wanted to post this issue in this thread but i'm new here and I just can't... anyways, rules are rules), and i'm have some issues when I want test APK's in my phone via ADB or Eclipse-ADT.
When I click excecute ( or do adb install), the process will fail, showing me that:
Code:
[2013-07-23 16:40:48 - AWifiSignal] ------------------------------
[2013-07-23 16:40:48 - AWifiSignal] Android Launch!
[2013-07-23 16:40:48 - AWifiSignal] adb is running normally.
[2013-07-23 16:40:48 - AWifiSignal] Performing net.elsemieni.awifisignal.SplashActivity activity launch
[2013-07-23 16:40:48 - AWifiSignal] Automatic Target Mode: Unable to detect device compatibility. Please select a target device.
[2013-07-23 16:40:51 - AWifiSignal] WARNING: Unknown device API version!
[2013-07-23 16:40:51 - AWifiSignal] Uploading AWifiSignal.apk onto device 'YT9002B59S'
[2013-07-23 16:40:52 - AWifiSignal] Installing AWifiSignal.apk...
[2013-07-23 16:40:53 - AWifiSignal] Installation failed due to invalid APK file!
[2013-07-23 16:40:53 - AWifiSignal] Please check logcat output for more details.
[2013-07-23 16:40:53 - AWifiSignal] Launch canceled!
In simple words, doesn't install beacuse [INSTALL_FAILED_INVALID_APK] error code.
Of course, i have Debugging activated in my phone and install 3rd party applications.
By the way, Logcat gives me that
Code:
07-21 18:05:23.663: W/zipro(25492): Unable to open zip '/data/local/tmp/AWifiSignal.apk': Permission denied
07-21 18:05:23.673: W/PackageParser(25492): Unable to read AndroidManifest.xml of /data/local/tmp/AWifiSignal.apk
That's curious I can't write inside it. I searched the forums and I applied a workaroud solution (http://forum.xda-developers.com/showthread.php?p=40040546&postcount=4), to make a link from tmp to sdcard folder. It worked in this way, but ruined the phone sys after reboot ( crashes randomly, most critical app's frezzes, etc), so doesn't work.
I know that's a firmware bug, but... any ideas about this? There's another workaround to make tmp safely writable, or any way to change the folder who ADB uses to install apps remotely?
Thanks! :laugh:
I am sorry that I know there are so many articles talking about
Drivers need to be installed for connected device.
You can find them in the drivers folder of Flashtool.
I have read so many articles but still cannot find out the problem.
I go to "Devices" of Flashtool and "Check Drivers"
It gave me this
01/004/2014 00:04:31 - INFO - List of connected devices (Device Id) :
01/004/2014 00:04:31 - INFO - - USB\VID_0FCE&PID_51AF\CB5A1YAHWN Driver installed : true
01/004/2014 00:04:31 - INFO - - USB\VID_0FCE&PID_51AF&MI_01\6&E66E0BD&0&0001 Driver installed : true
01/004/2014 00:04:31 - INFO - - USB\VID_0FCE&PID_51AF&MI_00\6&E66E0BD&0&0000 Driver installed : true
01/004/2014 00:04:31 - INFO - List of ADB devices :
01/004/2014 00:04:31 - INFO - - CB5A1YAHWN
01/004/2014 00:04:31 - INFO - List of fastboot devices :
01/004/2014 00:04:31 - INFO - - none
And I could not unlock bootloader.
I have ticked the USB Debug yet my Z2 is not rooted yet.
Do I have to root it first?
May someone guide me how to unlock because I cannot finish it using the official way
It always keeps telling me "Waiting for device"
Thank you so much!
http://www.theandroidsoul.com/unlock-bootloader-on-sony-xperia-z2/
I followed this website.
Using method 1, I could not achieve step 4
Using method 2, when I type fastboot.exe -i 0x0fce getvar version
noting happened, it seemed to be saying "cannot find 0x0fce" or somthing else
I don't know why it keeps telling me no driver installed
I go to Device Manager of Windows and it shows it has the updated driver installed in the PC
I am using Win 8.1
http://forum.xda-developers.com/showthread.php?t=2635830
This thread will help alot
Press windowsKey + R
type/paste
Code:
shutdown -o -r -t 0
into the box, this will restart your machine in the advanced startup menu.
when it restarts choose "disable driver signing" Then install the driver manually using the "have disk" option. when you reboot again the driver should be working.
-------------------
I followed what it said but when is "when it restarts choose "disable driver signing" Then install the driver manually using the "have disk" option. "???
I could not find disable driver signing.
After entering the shutdown command, what button should I press? Thank you for replying! I wish I will be able to flash rom today
Not sure what to do then because i ran into the same issue but i just used a linux OS as a work around
Thanks for answering
I will try using Win Vista
I hope someone could teach me