Hi, unfortunately, i have problem of not wakeing up after suspend. It's actually very annoying problem and it's not depend on kernel or ROM, i have tried stock ROM, taboonay ROM, stock and moded kernels, i have done all wipes and factory resets - no metter, problem still present.
Now, my ROM is Taboonay 2.0 and kernel [KERNEL] Stock/HV/Taboonay V3.2 for HC 3.2 04-09 - 1.64Ghz/UV control
I have done some logs by this command
Code:
cat /proc/kmsg > /mnt/external_sd/log_name
Can anybody look out, is there any problem in this log?
At this time i reboot tab, put command to collect log and press power button to get tab into suspend mode. In a few minutes, then i pressed power button, it was not responding...
Thanks a lot, and sorry for my great English, but on Russian forums i can't find nobody who can help me to analyze logs
Log:
View attachment debug_log_3.txt
Related
New to working explicitly with the Xperia X10. I guess I should have done some more looking into this, before doing something (apparently) stupid like pressing that big button that says "optimize". I was under the impression it would install JIT. I didn't realize it would instead
1) cause the phone to hang on the splash screen
2) prevent it from booting into recovery (deleted recovery?)
3) prevent it from being flashed from FlashTool. (press back button with phone off, plug in USB, green LED lights up as soon as plugging in, but FlashTool doesn't recognize)
First question is how do I fix it, but the next question is WHAT exactly does the "Optimize" button do? Or shall I perhaps say supposed to have done? [EDIT: sorry, rhetorical question. I believe it is supposed to install JIT for Eclair.]
I can see in the build.prop file that this line has been commented out
Code:
#kernel.log=default
and this line was added
Code:
dalvik.vm.execution-mode=int:jit
**THE PHONE IS NOT BRICKED**
I can adb shell into it. Even though it is stuck on the splash screen, FlashTool sees it. Here is the latest log:
29/045/2011 23:45:40 - INFO - Connected device : X10
29/045/2011 23:45:40 - INFO - Installed version of busybox : BusyBox v1.18.4 (2011-04-04 18:40:20 CDT) multi-call binary.
29/045/2011 23:45:40 - INFO - Running uname -r command
29/045/2011 23:45:41 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29
When opening a shell I get a seg fualt when trying to su to root. So I don't have sufficient privileges to remount /system. so I can't push a the original build.prop to it.
Here's the log from running optimize (aka self destruct ):
29/055/2011 22:55:39 - INFO - Remounting system read-write
29/055/2011 22:55:39 - INFO - Pulling /data/local/tmp/remount.log to .\devices\X10\work\remount.log
29/055/2011 22:55:40 - INFO - Pulling /system/build.prop to .\devices\X10\work\.
29/055/2011 22:55:40 - INFO - Pushing ./devices/X10/optimize.tar to /data/local/tmp/optimize.tar
29/055/2011 22:55:42 - INFO - Pushing .\devices\X10\work\buildnew.prop to /data/local/tmp/build.prop
29/055/2011 22:55:43 - INFO - Running optimize as root thru sysrun
29/055/2011 22:55:44 - INFO - Optimize finished. Rebooting phone ...
Prior to this I rooted it with flash tool, installed xrecovery, did a nandroid, then installed titanium backup and set cpu.
Phone details in sig.
think the optimize was just to install JIT on 2.1 which isnt needed on 2.3
iain26 said:
think the optimize was just to install JIT on 2.1 which isnt needed on 2.3
Click to expand...
Click to collapse
My apologies, I realize that it is supposed to install JIT for 2.1. That was a bit of a rhetorical question.
I'm hoping for suggestions of what to do since I have a locked bootloader.
Finally got it into recovery
I'm not sure how exactly, but after hours of messing with it, I've got it booted into recovery and am restoring.
After trying all sorts of key combinations, I removed the SIM and continued trying key combinations. I powered on the phone while holding the back button. Then I simultaneously pressed the middle button and the power button, and then just the power button, then the middle button, and so on a so forth until BAM! Recovery.
Just restored everything.
Hi ... I have the same problem but I'm unable to bring it to recovery...
I rooted the phone... asked for permission from Flashtool and everything ok ... but then I clicked optimize and mi phone got "semi-bricked" as yours...
I can see the logcat through adb but I can't do anything with it... while Flashtool was still enabled I installed recovery (but the phone was bootlooping so I don't know if it's installed or not)
I found your post and try to do what you did but I don't see any recovery... I removed the sim, and I'm trying power+back, power+home, alternate power and home .. but nothing works... any other idea ?
Cheers!
For me xrecovery was still there. If the USB is plugged in, disconnect it and try getting to booting into recovery.
I subsequently figured out that the reason I couldn't flash anything from flashtool was because I was running XP in a VM using virutalbox - it had nothing to do with clicking the optimize button. So if nothing else works, maybe you can use flashtool to flash new firmware...
Is it possible to unbrick my x10 mini pro?
Sorry for my bad english.
i have clicked on the "optimize" button
Is it possible to unbrick my x10 mini pro?
I've been getting this recently with 3 GB roms and 2 kernels on E22 modem. It happens when I restore my apps+data using Titanium Backup and reboot. This is "user apps" only. I'm working on restoring in batches to troubleshoot, but there are way too many so I got a logcat as well.
Order of events:
Boot -> media scan -> delay of 60-120sec -> restart rom (does NOT show kernel or rom splash screens on restart)
------ loop
I can't seem to pinpoint the offending app. It's also possible that it may be too many of them, or too many on SD. It happens on battery power, on AC, and on USB with airplace mode on/off.
Any ideas how to solve this?
LOGCAT: http://quick99si.home.comcast.net/misc/logcat.txt
Oh, and the log was stopped as soon as I saw the screen turn off. There's definitely data in there from the subsequent restart.
Hi all,
I have to report a problem with 2nd Init installed and camera.
I Found that my camera showed a black screen instead of the preview but I could make pictures without problems, but no video.
After trying everything found on the web, the problem was still there. So I restored all my apps and data and I tried to uninstall 2ndinit....
The camera now is working!!!!
I can't even imagine the reason but seems that 2nd Init has some bugs on defy.
Anyone had this problem?
bye
Davide
The solution is simple, from bootmenu change boot method from bootmenu to normal. The black screen is due to messed up video driver.
Maybe I was not too clear... I'll try to explain better.
The problem at the camera IS DUE to defy 2ndInit not to video driver!
The only way I found to solve it is to remove 2ndInit. (tried 2 times)
I was just wondering about the connection between the problem and 2ndInit.
Thanks
Bye
pbjhon was right in the first place. The 2nd-init is actually causes the camera to stop working properly where you can not see any preview but taking picture is ok.
You need to set the boot menu(in 2nd-init) to normal booting instead of boot into 2nd-init. Installing 2nd-init in default will set the booting direct to 2nd-init menu which you must edit/change it yourself.
I have similar problem, happened just after install of bootmenu (0.6.1, no new ROM yet).
Please clarify - once I've selected the "Normal" boot option, to be the default one, - how could I enter bootmenu again ? - is this done by press on "volume-down" button, once the blue led is lit ?
simon45 said:
I have similar problem, happened just after install of bootmenu (0.6.1, no new ROM yet).
Please clarify - once I've selected the "Normal" boot option, to be the default one, - how could I enter bootmenu again ? - is this done by press on "volume-down" button, once the blue led is lit ?
Click to expand...
Click to collapse
Install latest bootmenu and CWM for better ROM management, http://forum.xda-developers.com/showthread.php?t=1356767.
Some custom roms will ask what kind of boot when you pressed reboot option, like CM7. You can disable/enable that option as well.
However in the ROM you use, if theres no option, then you can simply press Vol-down the moment blue led turns on.
For me, the no-camera issue was resolved by set the default boot, to "Normal".
I have also verified that I can re-select boot menu, using the volume-down press after blue Led lights up.
Thanks for the help.
I am running CM7.2 KANG ROM built by mrg666 on my NC. Sometimes I encountered that the NC stop responding and I have to press the power button key for an interval to force it off then reboot it again. I don't think that's SOD since I am not able to get it connected with USB ADB when it stops responding.
Is there anybody having a clue how does it happen or how to get the previous log to find out the root cause? Thanks.
Three things you can pull - logcat (useless if you have to reboot), kmesg, and dmesg.
Alright guys, I downloaded NC2 kernel and FINALLY flashed alliance rom , at first it was all fine, it flashed quicklly and I got to looking around the rom and noticed when my phone screen times out and I go to turn it back on with the home button it doesnt work AT ALL I can use the home button while my phone is on doing any normal task, but when I go to push it to light my phone up to swipe it , I get nothing
If the mods don't delete this ------ I'll post the fix (which I'm sure the OP found):
Go to Settings --> Custom Settings --> Lockscreen Mods --> Wake with Home Key (make sure that's unchecked) - so it says: Home Wake Enabled.
The rom came with that disabled on a clean flash. I originally thought I broke something when this happened to me, lol.