Hi all,
Background:
I have rooted my x10 mini and installed generic 2.1 update. then installed launcherPro 0.8.1.1 (version code not sure). I have 8 gb microSD card on my phone with 3.24GB free memory. Installed Handsent SMS latest version.
Problem:
I was trying to send SMS to 12 recepients togather. While doing this operation i gor call and suddenly screen turns off but vibrator was on. I can't restart the phone as still the screen is black but can recognize call via vibrator but can not pick up.
Please provide the solution.
thanks in advance.
Thanks and Regards,
Mayur (Meirales)
X10 mini Owner
Since you have it rooted, use adb shell to connect via command line.
Then:
su (hope that you have done this at least once, since the first time an authorization dialogue pops that you need to allow)
/system/bin/reboot
should reboot your device.
i am a noob to adb shell ...
please provide ..learning site and instruction manual if possible .. above concern
hey, i think that u just need to restart your phone by pressing the middle key+ the power key for 5 seconds ( till it vibrate)
gd luck
hey thanks that was easy
Related
After updating to 2.0.2.A.0.24 the phone crashes\reboots when i wake up the phone and try to swipe the lock screen. It seems like the screen is frozen when waking it up, and if i dont carefully swipe the keylock it will crash.
Anyone know what the problem can be?
mangoman said:
After updating to 2.0.2.A.0.24 the phone crashes\reboots when i wake up the phone and try to swipe the lock screen. It seems like the screen is frozen when waking it up, and if i dont carefully swipe the keylock it will crash.
Anyone know what the problem can be?
Click to expand...
Click to collapse
Yes, it did that that to me.
Solution :
1. wait for black screen just before next reboot(try and error), long press home key (right buttom key), do not release, phone stop reboot. If you release, it will boot again.
2. at your PC, start Sony update program, wait for it ready prompt you to connect USB cable, then connect USB cable while still press (home key).
3. Sony update program should detect your x10 mini, and check version upgrade, after it report that version already uptodate and prompt you reinstall it again, your answer is YES.
4. until you saw you X10mini green light on, then you can release you hand. Sony update will download again from internet and flash your x10mini.
I did this, sucessfully installed again with 2.1 2.0.2.A.0.24 version. But then you have to reinstall all you apps again from the beginning.
yes, i did reinstall the update from seus 3-4 times. I think it crashed 15 times in some hours.
Finally it also crashed and restarted when switching it off, and the popup screen appears to shut it down. Had to remove battery to turn it off.
i was using titanium backup to restore, so now im restoring applications one by one and testing to see if some of them are causing the crash.
The app2sd crash
Sent from my Pulse using XDA App
im not using app2sd, but today it has crashed 4 times so reinstallling with seus again. im soon giving up..
heres what im doing,- On Norwegian phone
1. install from seus again
2. root phone with this guide http://forum.xda-developers.com/showthread.php?t=906231&page=5
3. since im using build.prop with ro.product.name=U20i_1238-8536 im getting for some strange reason keyprint.xml with Keyprint name: QWERTY Swedish/Finnish and <script name="latin" keylayout="qwerty-se-fi"/> when i want norwegian.
Problem here is with 3. party on screen keyboards installed, the hardware keyboard cant write ø and æ. (It becomes ö and ä)
So with root explorer i replace keyprint.xml and mimmi_keypad.kcm.bin found here http://forum.xda-developers.com/showthread.php?t=828558&page=1
I think that can be the problem, but not sure
Edit again..
im 99% sure changing the keymap.xml and mimmi_keypad.kcm.bin from mentioned thread is the cause of the constant crashes.
with build.prop with ro.product.name=U20i_1238-8536 and updating i get Keyprint name: QWERTY Swedish/Finnish. So hardware keyboard cant type ø and æ with third party keyboard installed.
Any advice?
i have a lika problem but my problem is i can't write åäö but i have it on my keyboard it's become the other symbols .',
its lika i have a english keyboard but i dont shold have it. because instad of your .', i have åäö.
I have just rooted my phone and installed xcyanogen v3.4 for the x10mini pro.
Everything worked fine, I have even managed to go into xRecovery after the installation and reinstalled xcyanogen three times.
This morning, I updated my Busybox from busybox installer from Market. Installed V1.19 busybox, I guess the previous one installed with cynogenmod6 was v1.15 then
The phone reboots suddenly, and hence after
*I only have an Unlock screen that works, displaying clock, charging stats, Sound off etc with NO SIGNALS
*If i unlock the screen, it will have a 'DSOmanager stopped Unexpectly force close' window followed by unlimited 'LauncherPro stopped Unexpectly force close' windows
*I am UNABLE to go into xRecovery to reinstall the system, unalbe to do anything now.
and the Phone reboots all the time automatically, but still get back to this unlock screen.
I am a newbie, any pros would help me pls? Thanks so much!
rccr said:
I have just rooted my phone and installed xcyanogen v3.4 for the x10mini pro.
Everything worked fine, I have even managed to go into xRecovery after the installation and reinstalled xcyanogen three times.
This morning, I updated my Busybox from busybox installer from Market. Installed V1.19 busybox, I guess the previous one installed with cynogenmod6 was v1.15 then
The phone reboots suddenly, and hence after
*I only have an Unlock screen that works, displaying clock, charging stats, Sound off etc with NO SIGNALS
*If i unlock the screen, it will have a 'DSOmanager stopped Unexpectly force close' window followed by unlimited 'LauncherPro stopped Unexpectly force close' windows
*I am UNABLE to go into xRecovery to reinstall the system, unalbe to do anything now.
and the Phone reboots all the time automatically, but still get back to this unlock screen.
I am a newbie, any pros would help me pls? Thanks so much!
Click to expand...
Click to collapse
Newbie too, and had the same problem, phone would boot into a low resolution mode (everything looked huge), followed by most applications and widgets crashing, I was lucky enough for the phone to forget the association with ADW Launcher and it allowed me to use the default home screen when launching it.
Now I'm in the process of repairing it using SEUS, need to charge up the phone before, is there's a way to fix this without having to lose everything? (Can't use the backup service)
rccr, try accessing safe mode, hold the menu key while it's booting.
Thanks!
Thanks! I have got to a post from xcyanogen forum, ways of recovering a 'killed device'. I was managed to flash back Sony Ericsson 2.1 using SEUS. Have installed back CyanogenMod6-v3.6, now everything working as before.
Help!!!!
Rccr can you please tell me the exact link?
You should never replace busybox on a custom rom or if ypy have xrec installed because they depend on their specific bysybox version!
Sent from my X10mini running on MiniCM 2.2.1 RC2 / aZuZu ZiG ZaG Alpha 0
Hello, all ROM makers, developers, hackers and advanced users.
I have a problem and hope you can give me some good advice.
Here is my sad story
You can read the full description if you want. Or you can skip it - the main question in the end of this post..
I have bought a new Sony ericsson Live! with walkman (wt19i) phone during my newyear holydays in Prague. It seemd to be working fine.
It is from rev.3, manufacture date 11/49 (mounth/week)
When I came back home and started using it, I saw that after some inactivity period (about couple hours or maybe more) the touch screen, back and menu snsor buttons stops any responsing. Hardware buttons (home, volume, camera, walkman and power) are still working. The system also continues to work as usual, so I can turn it on (but can not slide to unlock), I can hear if somebody calls me (but can not answer). Alarms, notifications and all another functions are still working.
Once or twise it started to work again (by itself, without any actions by me) but after few time the problem repeated. I was very unhappy and sure it was a hardware problem (and of course the Czech warranty does not work in Russia), but now i'm not so sure.
The phone had 4.0.2.A.0.58 firmware (android 2.3.4) from the box. First of all I tried to install SE PC Companion software, connect phone with usb and make factory reset... touchscreen started to work! But soon I saw this problem again.
The next day a new update was released and installed it (firmware .62). My phone was working again, but with the same result after some time.
You shoud know, that simple softreset (or ejecting and inserting battery) has absolutesy no effect on problem. After system starts I can not even unlock it. But flashing a new (or even the same) firmware (with flash tool or SE PCC) makes touchscreen and buttons working for some time. Have no idea why, but installing ROM with CWM (even with full wipe) does not make touch working.
Then I tried to use another custom kernels and ROMs. I unlocked the bootloader with fastboot tool, flashed one of custom ROMs from this forum (pre-rooted and with CWM). Then tried to use CM7.2 ROM... then another kernel and another ROM. Official, official-based, totally unofficial. The problem was with me each time after couple hours
I thought it is because some troubles in lock screen. Tried to install "no lock" app, so my phone did not use lock... but after some time touch freezes in home screen.
I disabled screen off while charging in settings and tried to leave the phone "wired" for some time... actually it worked fine all the time, and when I dicsonnected it it was still working... for couple hours.
I tried to install "no sleep" applications that does not allow CPU and screen to suspend. But it have no influense.
I even flashed CM9.0 ICS (very) beta ROM with the same result.
If it is just hardware problem - why it solves (for some time, but solves) with flashing? If it is a software problem - why it doesnt solve with new kernels and ROMs? My brain is ready to explode.
Now I have only one last idea and ask you to help me.
The question is:
How can I use adb or adb shell comands to get more information about the problem with touch?
I saw there is some log (logcat, stderr) tools, debug tools. I saw working lsmod, dmesg and mount commands in shell.
I think I shoud get all this information when all is ok. And then get it again when touch stops working and then compare, is it a good idea?
Where exactly shoud I see? How to test or get some touch input device info with adb? Is there any item in /dev that i can explore? Or something in dmesg? Where are touch driver located and how can I check if it is working?
I have some basic linux and andriond skills, but have not enought expierence.
I very (VERY) hope somebody can give me any useful advice to continue solving the problem. Where to see, what to do?
Thank you
P.S.: and sorry for mistakes, of course. English is not my native language.
P.P.S.: i am not sure where is the best place for this question: here or in xperia subforums. But I decided that this question is not xperia-specific and can be useful for other people in future.
Anybody? I have Lenovo Yoga B6000 with touchscreen problem and will be good if anyone know how can i test TS through ADB or shell.
Hi,
I'm not sure if this is the correct place to post this issue..!
I use Sony Ericsson Xperia Pro MK16I. (Rooted, Bootloader unlocked).
Recently I had issues syncing contacts with Google, Fb etc and I had to do a factory reset of the phone. Since then I've following issues so far. :crying:
1. Incoming calls are getting rejected automatically
2. Silent, Flight mode are missing when I press the power button
3. When I'm in some application and if I press the Menu/Home button, it does not take me to the home screen and nothing happens
4. Windows can't detect or install the drivers for the phone, even if I do it through the 3rd party sources windows still doesn't show it.
Anyhelp would be appreciated, thanks
Ferrard said:
Hi,
I'm not sure if this is the correct place to post this issue..!
I use Sony Ericsson Xperia Pro MK16I. (Rooted, Bootloader unlocked).
Recently I had issues syncing contacts with Google, Fb etc and I had to do a factory reset of the phone. Since then I've following issues so far. :crying:
1. Incoming calls are getting rejected automatically
2. Silent, Flight mode are missing when I press the power button
3. When I'm in some application and if I press the Menu/Home button, it does not take me to the home screen and nothing happens
4. Windows can't detect or install the drivers for the phone, even if I do it through the 3rd party sources windows still doesn't show it.
Anyhelp would be appreciated, thanks
Click to expand...
Click to collapse
did u fash any rom ? if yes then it is problem related to rom ....u have to contact ur rom developer for help......if u havent flashed any rom then try un rooting ur phone
CHEERS
I did flash the ROM and root the phone initially, after I reset my phone to factory defaults my PC couldn't recognize it.
Anyways, I installed the drivers for all Xperia phone and finally I was able to flash using ICS firmware. Now in a process of rooting it.
Appreciate your reply!
Sent from my MK16a using xda app-developers app
Hello everyone,
I searched for a similar topic but I could not find it. If there is a topic like that I would appreciate if somebody could transfer this to the correct place.
I have an Xperia X10 with Wolfbreak 7 Stock (2.3.3) installed and from time to time I am experiencing the same problem. My wife, with the same hardware and software has the same:
The phone, after some time working perfectly, suddenly loses the screen lock and the options “silence mode” and “plane mode” when the start button is pressed and held (only “shutdown” and “restart” are available).
The only way I found to correct that is the factory reset. The problem is I have to configure my accounts again and reinstall all the downloadable apps I use.
Can anybody help me? Is there any correction I could install on my phone or could I use a recovery function to make this process easier?
Thank you in advance.