Develop Bugs

[Help] A Myriad of Problems

Disclaimer: I am extremely illiterate when it comes to Android terminology, so you will most likely have to talk to me like I'm a child. I will try to explain my problems as best as I can, and will of course answer any questions. I also might over-explain, so I apologize for any length/redundancy issues.
Phone: XPERIA Play R800at, Android 2.3.3, Rooted with su and rom manager
My previous Play's touch screen stopped working, so the warranty granted me this new one. It's only two or three weeks old. The first problem I noticed was that I tried and could not delete anything off of my SD card. I tried formatting it a number of times, both in-phone (In Settings, as well as ES File Manager) and on Windows (both default formatter and a specific SD card formatter), but it would always revert back to what it's previous state would be. After researching a bit, I concluded it's probably faulty or failing, so I've ordered a new one that should get here within the week.
The second problem rose out of the first, I'm sure: My computer now doesn't recognize the sd card anymore. In SMC or MTP mode, it will not pop up on my computer and could not be recognized in PC Companion. On phone, the usual options you get in the notification bar (*dis*connect phone, etc.) do not show up. When connecting, the MTP USB Device driver attempts to install, but never succeeds. This is with USB debugging off and on, and every permutation I could think of.
Now, the most recent problem has been that the Home button doesn't work and there is no lock screen. Using the Terminal Emulator, I've attempted the popular fix (su -> echo -n ON > /efs/imei/keystr -> sync -> reboot) but I get the message /efs/imei/keystr directory nonexistent. I've factory reset my phone a number of times, reset settings, gone into recovery mode and reset things there, as well as caches, but all to no avail.
This could probably easily be remedied by just reflashing Android, or an older version or something, I'm sure, but given that my SD card is currently unreachable, I was wondering if anyone would know of a way I can fix these problems, or at least one of them. Thanks in advance.
If I've left anything out, please tell me and I will expound as best I can.
Other notes that might be of importance:
- It seems my *system* or whatever it would be is read-only, which seems like it could definitely be a problem. How do I fix this or do I even need to?
- I don't have the Setup Guide on my phone; I saw a thread that posited that this was a cause of the no lock screen problem.
Thanks again.

Driver install issue
Hello!
I'm not sure how to fix all of your problems. However, I have the same issue with my MTP drivers not installing when I connect the device. I've tried installing with various tools and the standard sony ericsson software. I believe I have the problem with the driver sorted out. I noticed that the drivers are, for some unknown reason, attempting to install to a TEMP folder. I would assume they are then being dumped from the TEMP folder after only a few seconds because when I install the driver it continues to ask me to install even when I click "finished."
You might try making sure the drivers are installing to the proper location if you haven't already. That might help with some of the issues.
On the same topic, do you know where the drivers are SUPPOSED to go in Windows XP? I'm fairly new to all of this stuff so I'm not sure exactly which folder in C:/WINDOWS the MTP driver for the Experia Play is supposed to go.
I hope this helps!
-Zot-

[Q] Phone keeps restarting by itself

My phone (rooted, but stock running 4.1.1) keeps restarting by itself. I have seen other folks with the same problem on the S3 and other devices. And it seems the only thing that fixed it was changing the SD Card (tried it) or resetting the phone. It takes me ages to set up my phone and I'd like to avoid doing the latter if possible. Is there some kind of a panic log file that gets written that I could look at? I believe that the logcat file gets cleared at every reboot which, if true, explains why I can't spot anything in there. Since this happens erratically, I can't connect from my PC and redirect the logcat to a file on my PC. I believe Linux stores crash logs. Is there something similar on Android?
Oh, and it's not rebooting because it's getting hot or anything. And I haven't done any overclocking or any messing around with the phone.

Found a couple of options after googling. I had tried earlier, but "logcat across reboots" was a better search phrase.
Anyway, I can hook up my phone to the PC and run
adb -d logcat > mylogfile.txt
which should save a log file to my PC and when I'm not near a PC, I can use something like alogrec which saves logcat files to an SD card
https://play.google.com/store/apps/details?id=org.jtb.alogrec
Another option is to use adb bugreport
http://developer.sonymobile.com/2012/01/25/new-bugreport-analysis-tool-released-as-open-source/
Hopefully it will provide a useful clue.

If not....you can always make a Nandroid, reset your phone, and then restore.
Sent from my PG06100

You can use terminal emulator from your phone and dump a logcat to sd as a .txt if you search around you'll find the proper command which I can't remember at the moment but its something like
Su > enter
Logcat -d /sdcard/filename.txt
Filename being whatever you choose
I like to break stuff!

[Q] Logcat any way preferred over another?

Well I have a question to our devs. Is there any one way to logcat that is preferred over another? I never have done logcat to determine issues for our device and I would like to start. I know there are a couple apps on the play store that are useful like aLogcat or Catlog. I know its best to use adb and even run the command in terminal emulator.
There is a great guide here that I've been referring to http://forum.xda-developers.com/showthread.php?t=1726238
And DONT forget to thank paxChristos for the guide.
In short I want to logcat to help out our devs as much as possible so is there any requirements that you like to see for a logcat? Should I/we try and duplicate the issue a certain amount of times while doing the logcat? Any feedback would be useful.
Thanks to everyone who makes these devices we have just that much better. And keep up the great work.:thumbup::thumbup:

Adb is always the best and easiest way. Always be sure to use -v long when logcatting as it's makes our lives 10 times more easier. Personal favorite log cat guide is this
http://forum.xda-developers.com/showthread.php?t=1378491
Sent from my Nexus 7 using xda app-developers app

sinfulgray said:
Well I have a question to our devs. Is there any one way to logcat that is preferred over another? I never have done logcat to determine issues for our device and I would like to start. I know there are a couple apps on the play store that are useful like aLogcat or Catlog. I know its best to use adb and even run the command in terminal emulator.
There is a great guide here that I've been referring to http://forum.xda-developers.com/showthread.php?t=1726238
And DONT forget to thank paxChristos for the guide.
In short I want to logcat to help out our devs as much as possible so is there any requirements that you like to see for a logcat? Should I/we try and duplicate the issue a certain amount of times while doing the logcat? Any feedback would be useful.
Thanks to everyone who makes these devices we have just that much better. And keep up the great work.:thumbup::thumbup:
Click to expand...
Click to collapse
I think this will work for you
http://forum.xda-developers.com/showthread.php?p=37825398
sent from my htc pico

ADB is a great way to do it. The two guides stated above should help teach you how to logat.
Sent from my Nexus 4 using xda premium

For some reason i can not get my device to connect to adb, Ive never had this problem before and my my old G2x connects just fine. Ive uninstalled the drivers and reinstalled with no luck. Also went as far back as uninstalling the drivers and odin back to stock to try and have them reinstalledwith no luck. Any ideas?

sinfulgray said:
For some reason i can not get my device to connect to adb, Ive never had this problem before and my my old G2x connects just fine. Ive uninstalled the drivers and reinstalled with no luck. Also went as far back as uninstalling the drivers and odin back to stock to try and have them reinstalledwith no luck. Any ideas?
Click to expand...
Click to collapse
Try installing the regular ADB drivers then. I linked a Google search for "Samsung adb drivers".

Damn still can not connect, I've tried to uninstall Google USB driver and Samsung USB drivers and they uninstall and install just fine witj a reboot in between of course but phone is still not connected. I'm my device manager on the PC under other devices it shows 4 android devices all with yellow caution signs.
Now my G2x won't show either lol Going to try and completely remove ADB and reinstall and see what happens.
Sent from my SGH-T989 using xda premium

sinfulgray said:
Damn still can not connect, I've tried to uninstall Google USB driver and Samsung USB drivers and they uninstall and install just fine witj a reboot in between of course but phone is still not connected. I'm my device manager on the PC under other devices it shows 4 android devices all with yellow caution signs.
Now my G2x won't show either lol Going to try and completely remove ADB and reinstall and see what happens.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
If using Windows you must run the command prompt [cmd] as an admin be sure to do the following in Win 7:
click start type cmd in the white box and wait as it searches. When it lists cmd in that list now right click and choose run as admin.
Also you need to enable developer options [go to settings about device and tap the build ID like 7 times [as you tap it, it should count down after the first couple taps once you hit it enough it will say you have enabled developer options if you don't see them in settings already]
Be sure to hit the on off switch in upper right of window when you first tap developer options if the options are greyed out and don't let you change anything
Now in developer options be sure to go to the option where it says enable root access and be sure it says apps AND ADB if it says apps only tap that and change it to Apps and ADB.
Now try again
BTW I love CatLog it has a home screen widget that can start / stop recording for you] so if you know how to produce the problem go to home screen tap the widget go through the steps until the error occurs go back to home screen tap widget again and it stops then look in /sdcard/catlog/ and it will have text files named with the date and time and that will be the entire log cat that happened between the time you started and stopped the recording of your actions.

Wanamlite and Eclipse

Hey,
I'm not sure that this is the right place to ask, but I'll give it a shot anyway.
I am trying to use Eclipse to see my device logs & to run projects on my device.
I enabled usb debugging and I did all the necessary adjustments on Eclipse. Eclipse does detect my devices and shows all the apps that run in it, but I can't seem to see any logs or install anything. I tried to plug in my S2 and it did showed all the logs.
Can someone tell me what's the problem and how can I fix it?
Maybe the rom I'm using is blocking the connection?
thanks alot.

Anyone?

[Q] Rooting problem

HI All,
Apologies if subject is already in place (I wasn't able to locate it)
I was following root of
http://forum.xda-developers.com/showthread.php?t=1644167
however not able to install anything via script due to "permission denied". Any ideas what could be causing it?
One of users mentioned something about opening port. Which port would it be and how to open it? On top of that edb.exe keeps reopening though I keep killing it in services.
I would be grateful for any advises
Kind regards,
Ryath23

Ryath23 said:
HI All,
Apologies if subject is already in place (I wasn't able to locate it)
I was following root of
http://forum.xda-developers.com/showthread.php?t=1644167
however not able to install anything via script due to "permission denied". Any ideas what could be causing it?
One of users mentioned something about opening port. Which port would it be and how to open it? On top of that edb.exe keeps reopening though I keep killing it in services.
I would be grateful for any advises
Kind regards,
Ryath23
Click to expand...
Click to collapse
try this one http://forum.xda-developers.com/showthread.php?t=1604439 it worked for me like a charm and make sure that your usb debugging mode is enabled in your developers mode