Guest Dario93 Posted October 27, 2010 Report Posted October 27, 2010 (edited) Hi everyone, since i need to test Sense roms on my liquid E,for developing purposes (i'm in a team that ports sense roms),i have a question for you! :P Unfortunately,Sense roms don't work on my device :D i manage to install them,to boot them,but sense interface doesn't run,so i have to release roms without the possibility to test them. I'm using latest leak... Do my problems derive from this? Thanks in advance, Dario93 LOGCAT : http://pastebin.com/sXjDxuK7 Edited October 27, 2010 by Dario93
Guest Chewy11 Posted October 27, 2010 Report Posted October 27, 2010 Hi everyone, since i need to test Sense roms on my liquid E,for developing purposes (i'm in a team that ports sense roms),i have a question for you! :P Unfortunately,Sense roms don't work on my device :D i manage to install them,to boot them,but sense interface doesn't run,so i have to release roms without the possibility to test them. I'm using latest leak... Do my problems derive from this? Thanks in advance, Dario93 my Liquid E did the same thing last night with the desire and desire hd rom ports... i manage to install them,to boot them,but sense interface doesn't run(VERY slow,could not get any apps or widgets going) screen lock works great (over 15 minutes first boot)no FC.
Guest vache Posted October 27, 2010 Report Posted October 27, 2010 Can you share a logcat of the full boot sequence ? (until you're stuck)
Guest Chewy11 Posted October 27, 2010 Report Posted October 27, 2010 Can you share a logcat of the full boot sequence ? (until you're stuck) yes later...sorry will be my first logcat so patience please will post back if i need you to help hold my hand to get it to you :P
Guest Dario93 Posted October 27, 2010 Report Posted October 27, 2010 Can you share a logcat of the full boot sequence ? (until you're stuck) Logcat ASAP! :P
Guest Dario93 Posted October 27, 2010 Report Posted October 27, 2010 (edited) Logcat ASAP! :P Ok,logcat up. The phone shows up the endless "Loading...it may take several minutes" and only if i reboot twice or more times this message disappears.. howewer,also without this message sense is unusable,apps don't start.. etc.. Edited October 27, 2010 by Dario93
Guest vache Posted October 27, 2010 Report Posted October 27, 2010 (edited) Ok,logcat up. It shows up the endless "Loading...it may take several minutes" and only if i reboot twice or more times this message disappears.. howewer,also without this message sense is unusable,apps don't start.. etc.. Power off the screen when you have this message. Wait 2min, and power on. P.S : the logcat does not contain the boot, only when you have the message. Edited October 27, 2010 by vache
Guest Dario93 Posted October 27, 2010 Report Posted October 27, 2010 (edited) Power off the screen when you have this message. Wait 2min, and power on. Many thanks! :P I'm trying.. Uh, and for apps that don't want to start? EDIT: Ok,tried to turn off the screen for 5 minutes,then on again,but still loading...should i try another bin?? Edited October 27, 2010 by Dario93
Guest MirkoNEO Posted October 27, 2010 Report Posted October 27, 2010 How nice to see you working together ... :P :D :D :P :D :lol: :lol:
Guest vache Posted October 27, 2010 Report Posted October 27, 2010 Many thanks! :P I'm trying.. Uh, and for apps that don't want to start? EDIT: Ok,tried to turn off the screen for 5 minutes,then on again,but still loading...should i try another bin?? Make a logcat from the begining, you can launch it when the phone reboot.
Guest Borkata Posted October 27, 2010 Report Posted October 27, 2010 Try clear logcat buffer before starting it: adb logcat -c
Guest Dario93 Posted October 27, 2010 Report Posted October 27, 2010 (edited) Make a logcat from the begining, you can launch it when the phone reboot. Strange.. windows cmd doesn't report all the log,it cuts the older lines... Edited October 27, 2010 by Dario93
Guest thepasto Posted October 27, 2010 Report Posted October 27, 2010 This is desire sense's rom logcat. With others senses port same behaviour. I stop logcat so quickly, because it goes in a loop (i think), nothing more happend for minutes. If you need more, just ask!! Thanks again vache!!
Guest vache Posted October 27, 2010 Report Posted October 27, 2010 This is desire sense's rom logcat. With others senses port same behaviour. I stop logcat so quickly, because it goes in a loop (i think), nothing more happend for minutes. If you need more, just ask!! Thanks again vache!! It seems to stop here E/ProcessState( 443): Using /dev/binder failed: unable to mmap transaction memory. D/AndroidRuntime( 443): Shutting down VM but i dunno why.
Guest thepasto Posted October 27, 2010 Report Posted October 27, 2010 (edited) It seems to stop here E/ProcessState( 443): Using /dev/binder failed: unable to mmap transaction memory. D/AndroidRuntime( 443): Shutting down VM but i dunno why. If you say that!! i don't understand why sometimes first run conf starts, i can select language ecc.. and application starts regularly, other times home becomes black, instead and nothing works. Could be missing high-mem patch on kernel? The only difference between a1/s100 is ram... Edited October 27, 2010 by thepasto
Guest vache Posted October 27, 2010 Report Posted October 27, 2010 If you say that!! i don't understand why sometimes first run conf starts, i can select language ecc.. and application starts regularly, other times home becomes black, instead and nothing works. Could be missing high-mem patch on kernel? The only difference between a1/s100 is ram... On wich rom you were when you made the logcat ?
Guest thepasto Posted October 27, 2010 Report Posted October 27, 2010 On wich rom you were when you made the logcat ? Desire (LCR-D)
Guest Dario93 Posted October 28, 2010 Report Posted October 28, 2010 If you say that!! i don't understand why sometimes first run conf starts, i can select language ecc.. and application starts regularly, other times home becomes black, instead and nothing works. Could be missing high-mem patch on kernel? The only difference between a1/s100 is ram... Same problem here :P :D waiting for news...
Guest vache Posted October 28, 2010 Report Posted October 28, 2010 Desire (LCR-D) Can you share the output of "adb shell dmesg" too please ?
Guest thepasto Posted October 28, 2010 Report Posted October 28, 2010 Can you share the output of "adb shell dmesg" too please ? Now i'm not at home and i need my phone working!! This evening i will reflash the desire's port and i write kernel log output..
Guest thepasto Posted October 28, 2010 Report Posted October 28, 2010 (edited) Now i'm not at home and i need my phone working!! This evening i will reflash the desire's port and i write kernel log output.. Here the dmesg output.. I don't see any error, but maybe you can find something.. Ram is recongnized (about 384mb).. Hope you understand what's wrong!! After some operations, (try to launch some apps, navigating settings menu) this is the new dmesg output. I think it's ram allocation issue.. But i don't know how to solve.. Edited October 28, 2010 by thepasto
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now