Related
This is driving me nuts! All of a sudden Eclipse won't let me install my app on my I am working on to my unrooted Samsung Vibrant There are no errors in the app and it uploads fine on my Cyanogen Moded G1 running 2.1. I have not changed anything on my phone or in the project and because it uploads just fine to the G1 I figure it has to be a problem with the phone (although some, but not all of my other apps I have in eclipse upload to the phone just fine). I uninstalled the app, restarted my phone, restarted eclipse, restarted the computer a thousand times but every time the console just keeps giving me this message:
[2010-09-13 09:31:35 - Image Viewer] Uploading Image Viewer.apk onto device 'T9591e92523f'
[2010-09-13 09:31:42 - Image Viewer] Failed to upload Image Viewer.apk on device 'T9591e92523f'
[2010-09-13 09:31:42 - Image Viewer] java.io.IOException: Unable to upload file: null
[2010-09-13 09:31:43 - Image Viewer] Launch canceled!
I have restarted a thousand times- I have no idea what to do and it is killing me!!
Help!
OREGONMX said:
This is driving me nuts! All of a sudden Eclipse won't let me install my app on my I am working on to my unrooted Samsung Vibrant There are no errors in the app and it uploads fine on my Cyanogen Moded G1 running 2.1. I have not changed anything on my phone or in the project and because it uploads just fine to the G1 I figure it has to be a problem with the phone (although some, but not all of my other apps I have in eclipse upload to the phone just fine). I uninstalled the app, restarted my phone, restarted eclipse, restarted the computer a thousand times but every time the console just keeps giving me this message:
[2010-09-13 09:31:35 - Image Viewer] Uploading Image Viewer.apk onto device 'T9591e92523f'
[2010-09-13 09:31:42 - Image Viewer] Failed to upload Image Viewer.apk on device 'T9591e92523f'
[2010-09-13 09:31:42 - Image Viewer] java.io.IOException: Unable to upload file: null
[2010-09-13 09:31:43 - Image Viewer] Launch canceled!
I have restarted a thousand times- I have no idea what to do and it is killing me!!
Help!
Click to expand...
Click to collapse
Which version of Eclipse and ADT are you using? The latest SDK update that was just released has problems with Eclipse 3.6. The updated ADT (0.9.8) is reported by Google as only working on 3.5, not 3.6.
Hmmmmm- that's a good question. I did update ADT in the midst of this whole debacle but I can't remember if it was before or after I started having problems. It's weird that it would work with some projects and not others though. I will see if I can downgrade to the old version and see if that fixes it. Thank you!!
I'm getting the same thing on my captivate.
I can install the apk to a magic running 2.2, a Droid X running 2.1, and multiple emulators, but not the samsung.
I can install other projects, just not this specific one. I'm not sure where to look to see what makes it different though.
Any ideas?
I don't have these problems on my vibrant - I can hit run in eclipse and the apk gets transferred and loads automatically. I have no clue what could be causing the issue you guys are seeing. Could something have changed in later revisions of the device?
Sent from my SGH-T959 using XDA App
I had Eugene's hybrid rom installed a while back and the eclipse console would report a successful install of my program; however, it would not only fail to launch but also be nowhere to be seen on my phone. There would literally be no trace of the program on my phone despite the supposedly successful install.
I went back to stock via Odin and the problem disappeared. I don't know whether the rom was the culprit and am too tired laying in bed right now to do an empirical study to find out :O
tremechus said:
I'm getting the same thing on my captivate.
I can install the apk to a magic running 2.2, a Droid X running 2.1, and multiple emulators, but not the samsung.
I can install other projects, just not this specific one. I'm not sure where to look to see what makes it different though.
Any ideas?
Click to expand...
Click to collapse
In my case it turned out that I had two activities with this attribute:
android:label="@string/app_name"
apparently the eclipse plugin doesn't like to push an app with two app labels.
I am having this problem on my Vibrant as well. I think a prior installation of the application failed...
If I recreate the project with a different package namespace and transfer the files from the old project over then I am able to upload the application via eclipse again.
I'm not sure how to clean out the prior install. I too am running an unrooted phone...
Not sure if it is related, but since this started happening, my phone has been dying overnight and won't boot up unless I remove the battery AND sim card. Thankfully I have a good internal clock. I've been using my phone as an alarm clock so this has been quite inconvenient.
I've posted this over at the CM forums, but I'm going to post it here as well...
After dealing with this problem (hxxp://forum.cyanogenmod.com/topic/2132-need-serious-help-cant-flash-any-cm-build-but-cm-6-nightly-tests/page__view__findpost__p__20750) throughout multiple iterations of CM on my myTouch-branded 32B, I think I've come to the realization that my NAND is somehow corrupted or broken. It started off easy enough to fix: /system/framework/core.jar, /system/framework/framework.jar, or one a various libraries (including libskia.so, lib_androidruntime.so, and libdvm.so) would show up in the logcat during my bootloop, and I'd just use adb to push those files manually until I could boot. Unfortunately, I think the problem has worsened, as pushing these files (which would routinely show up, regardless of what version of CM I installed) would usually fix the problem. They still do show up at first, but pushing them only introduces new errors in the logcat that I can't trace to any particular file. Eventually, I get core FCs in the gapps initial setup.
The only thing that's even remotely worked for me has been to manually push the entire system folder extracted from CM6.1 and then to run "chmod -R 777 *" on the /system/ partition. This lets me boot, make calls, use the internet, download apps, etc. Still, I've got issues like /system APKs not installing (including Settings.apk, which is a huge pain in the ass).
Is there anything I can do to verify that my NAND is corrupted and possibly fix it in the event that it is messed up? What really kills me is that these adb push commands appear to work fine, so I feel like it's more the flashing process that is FUBAR rather than the sectors on my NAND.
I've also attached a logcat of a CM6.1 install that does core FCs after manually pushing the entire /system/framework folder and those libs I mentioned earlier.
And here's my SPL/Radio info:
SPL: 1.33.0013d
Radio: 2.22.28.25
And I'm sure that I'm running the 2708+ version of CM6.1. I've also tried multiple other 2708+ kernels (including ezterry's newest nightlies and a few 2708+ compatible pershoot kernels), but like I said, this is a recurring issue that I don't think has anything to do with CM in particular.
I'm at my wit's end. I'm actually considering flashing back to stock everything and trying to reproduce some problems so that I can get T-Mobile to swap it out. The only thing holding me back is the fact that adb push commands continue to work even as the quality of my flashes in recovery worsen.
I've split the logcat into two files (filesize limit).
I just updated my system and now my WIFI just reads error. I did a factory reset two times and still no luck does anybody have any suggestions?
androidA500 said:
I just updated my system and now my WIFI just reads error. I did a factory reset two times and still no luck does anybody have any suggestions?
Click to expand...
Click to collapse
What if anything did you do/load on your tab before you updated?
were you rooted and or applied removed any hacks or programs???
I don't know if I was rooted I didn't do anything to change the system when I bought it. All I did was download some games and use the browser. The update failed the first time, so I tried it again and it succeeded. As soon as the tablet restarted it had no internet access and on the setting menu under WiFi it just said Error.
i had to reset permissions on the wpa_supplicant to rwxr xr x.
How would I do that?
this has also happened to me. i'll try changing the permissions.
i used chmod 755 wpa_supplicant in the /systems/bin/ and my wifi still reads "Error"
did not work for me neither ;(
i think i will just send it to acer
You did reboot after making the permissions change, right?
yep i did. i did a system reset too and still came back as wifi error, and little did I know that when you do that it also wipes the "SD Card" internal storage as well, which had my system backup on it. UGH. Now, alot more troubleshooting
Ok I got wifi back up by restoring a system.img i found for the US to the original 1.04 version. After installing the patch manually, wifi failed to work. again.
After letting impatience get the best of me, I managed to extract the update from a posted link back to acer and successfully updated to 1.141. Now I have the same problem here. Error - No wifi.
Log reports an error loading the wifi driver. Tried to fix the wpa_supplicant permissions, but once I had the system folder set to r/w, the permissions were already at 755.
Anyone else figure this out? perhaps there's an old wifi driver we can use and replace the existing borked driver file?
Update: After searching though the forums, only two "fixes" are available for lack of wifi and neither of them do anything. Permission changes for the wpa_supplicant file does nothing and the two kernel mods also do nothing. In fact both those modules are the exact same size so I'd guess they are the same files. It has to be something else. Looking at attempting to revert back to 1.04 until this can get resolved (once I find the 3 images to do so)
Update2 (RESOLVED): Ok, this is something one would not expect from an update. From what it looks like, the update does NOT update the kernel in any way. The kernel modules were the cause of the error as the 1.141 update will update the modules but not the kernel itself. I found a set for my kernel here and after copying those to the /system/lib/modules folder (and changing the permissions to 755 or rwxr-xr-x) after rebooting I got connected. Hope that helps.
Update2 (RESOLVED): Ok, this is something one would not expect from an update. From what it looks like, the update does NOT update the kernel in any way. The kernel modules were the cause of the error as the 1.141 update will update the modules but not the kernel itself. I found a set for my kernel here and after copying those to the /system/lib/modules folder (and changing the permissions to 755 or rwxr-xr-x) after rebooting I got connected. Hope that helps.
Click to expand...
Click to collapse
Thanks! This worked for me.
Hi Guys, I have been having major issues since upgrading the firmware from the Kies software as a standard firmware upgrade....
Just no wifi or bluetooth as soon as you click on the buttons it reboots sometimes several times....heres a link of whats been done so far from a guy that has been helping me on the Vodafone eforum.....
http://forum.vodafone.co.uk/t5/Sams...nger-update/m-p/761803/highlight/false#M16520
Currently running
I now have Firmware 2.3.4
Baseband I9000XXJVP
Kernel 2.6.35.7. XXJVP
Gingerbread XXJVP
I hope someone can help as I am lost without my phone because thats how I get my work...
Regards Lee
Ok found this how can I put these settings on my phone.
Error initializing Wifi scan
Symptom: trying to enable wifi shows scan initialization error message.
Solution: Requires root. Remove /data/wifi/bcm_supp.conf - the file contains wifi access points definitions and will be regenerated. You'll need to re-enter pin codes for known networks.
[edit] GPS lock problems
Come on guys some one must know the answer to this, you lot can hang bells and whistles on your phones and hack NATO
find 3 file froyo tith your csc flash it via odin with pit and pick desired csc
then flas 2.3.4 from samfirmware - any problems should be gone
That's exactly what I done over the weekend went back to 2.2 and installed 2.2.1 then 2.3 etc..
Its seems to be the same faults, someone has suggested its the Antenna that's at fault
adb logcat c:\logcat.txt
produce the bug and so it restarts
ctrl+c to stop writing logcat and pm it to me
I have sent you the logcat txt as an email as it was far to big to send as a pm and I was unsure what parts were not needed...
The wifi is not mentioned but path to bus for bluetooth is a constant failure
( E/BluetoothEventLoop.cpp(125): get_adapter_path: D-Bus error: org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not provided by any .service files)
06-14 11:27:15.546 E/BluetoothEventLoop.cpp(125): get_adapter_path: D-Bus error: org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not provided by any .service files)
I tried to get the wifi to log but everytime the phone locked up
Thanks for taking a look at this for me...
fast google search revealed two fixes for bt:
- hard reset - *2767*3855# - this will wipe your phone stats but most probably will fix both wifi and bt
- http://blog.pfuender.net/?p=61 - this will fix bt alone
also note that adb logcat c:\logcat.txt will log everything till you stop it or phone shuts off so produce wifi bug let it do its reboot or whatever and then ctr+c
- hard reset - *2767*3855# - this will wipe your phone stats but most probably will fix both wifi and bt
Tried these already before and after I put the new software on and have just tried again no difference at all problems still exactly the same...
so pick option #2 and report
It wont connect to my pc to run catlog.
I had to download via 3G and run it on the phone from there so I can not use Ctrl+C unless you know how to bring up a window with in the samsung.
I only got the log by sending it via 3G as an email....to my desktop then copy and pasting to a notepad doc
why cant connect to pc ?
Mine works fine and the one of a friend of mine works fine too wifi and bt on xxjvp
Dont know just finishing my chores around the house and will get onto it!
as an additional after moving file mentioned in article you might want to do 'fix permissions' in cwm recovery
I am also having the same issue:
E/BluetoothEventLoop.cpp( 469): get_adapter_path: D-Bus error: org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not provided by any .service files)
However, my wifi does work. I have a Bell Samsung Galaxy S I9000M. The XXJVP modem didn't work for me (no HSDPA), so I flashed the UGJK3 modem and my connection was back. I followed the instructions on blog.pfuender.net/?p=61, blog "Android/Milestone bluetooth not working", but my '/data/misc/bluetoothd/' directory is empty, thus cannot perform the following step:
‘mv /data/misc/bluetoothd/XX:XX:XX:XX:XX:XX/sdp /data/misc/bluetoothd/XX:XX:XX:XX:XX:XX/sdp.bak <ENTER>’
I will continue to research this issue. I only realized it this morning as an app I am working on requires Bluetooth, and logcat went nuts with error logs (shown above). I will also keep this thread updated with whatever I find.
Cheers,
vinpa.
huh that was htc desire fix =)
lulz understand this - bt should be working out of the box and is working on stock - i can also confirm that it works on cfroot as i use it flawlesly
if you got bt not working now think about what else can be not workign that you do not notice...
imho best way is to make a PROPER system install
basicly youre misising bt deamon or a start link for it = broken system
i am out of this thread, consider yourselfs helped (install stock+cfroot)
Got it working...
I first made a backup with CWM, then flashed PIT512, CODE_I9000XXJVP..., GT-I9000-CSC..., and my original modem.bin.
After it rebooted, I skipped through the setup and rebooted once more into Download mode, flashed CF-Root and then restored. Bluetooth is now functional.
Cheers,
vinpa.
hi, i have updated to 2.3.4 jvp from js3 telenor
all is fine, battery usage is much much better, no laggs, and no FC/FR..
i have turned on the bluetooth once set the name, and turned it off....
after i rooted and brought backups back,i cant use BT anymore. it just stands and turning on for a min or two, and than goes to TURNED OFF state...
any help? any ideas?
Just got a text to say my phone is ready for collection.....
Bet it's not repaired properly and it has to go away again for the same faults..
i followed the CM instructions, but failed at last, the error msg indicates that the failure may have something to do with lack of some .so files, but i have run extract-all.sh between the compilation process, then why there is still such errors?
what is the error? copy & paste it, give us a clue. you might be missing some dependencies, or maybe cm7 is just temporarily broken & wont build due to a bad patch, that happens sometimes.