[Q] [dev] help needed - Optimus One, P500, V General

Hi there!
I am trying to port rom from another device (AOSP GT540 to our phone)
as this is my first try of doing port
I can't say that this port will work
I need some help
I am getting lot's of error
phone is not booted
here is logcat
--------- beginning of /dev/log/main
I/DEBUG ( 1418): debuggerd: Jun 13 2011 00:42:24
E/RPC ( 1426): error opening /dev/oncrpc/3000008c:00040000: No such file or directory
E/RPC ( 1426): ERROR OPENING [/dev/oncrpc/3000008c:00040000]: No such file or directory
E/RPC ( 1426): failed to initialize client (permissions?)!
E/loc_api_rpc_glue( 1426): Error: cannot create RPC client.
D/WiperIface( 1426): WiperIface open : Location handle -1234, pid 1426
D/libloc ( 1426): loc_read_gps_conf: using /etc/gps.conf
D/libloc ( 1426): loc_read_gps_conf: PARAM INTERMEDIATE_POS = 1
D/libloc ( 1426): loc_read_gps_conf: PARAM ACCURACY_THRES = 3000
D/libloc ( 1426): qct_loc_eng_wiper_init: wiper enable = 0
--------- beginning of /dev/log/system
I/Vold ( 1416): Vold 2.1 (the revenge) firing up
D/Vold ( 1416): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 1416): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 1416): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
W/Vold ( 1416): Ignoring unknown switch 'usb_connected'
W/Vold ( 1416): Ignoring unknown switch 'usb_configuration'
W/Vold ( 1416): Ignoring unknown switch 'usb_connected'
W/Vold ( 1416): Ignoring unknown switch 'MSM72K_UDC'
W/Vold ( 1416): Ignoring unknown switch 'MSM72K_UDC'
W/Vold ( 1416): Ignoring unknown switch 'usb_configuration'
Click to expand...
Click to collapse

hi,
first messages are from non working GPS, maybe you have a wrong/missing GPS libraries
other messages are related to USB ("ignoring unknown switch... blah").
both types of messages arent bad, phone have to boot - even with these errors.
did you get some other errors?

ya,first I got audioeq error but then I replaced libaudioeq file
so you mean phone should also boot with those error
or I am doing something wrong ?
after this log phone stuck at LG logo and do nothing not booting and no log

ya,first I got audioeq error but then I replaced libaudioeq file
so you mean phone should also boot with those error
or I am doing something wrong ?
after this log phone stuck at LG logo and do nothing not booting and no log
Click to expand...
Click to collapse
Uhh may we know what rom you are exactly porting?? That may help us more in guiding you...
Sent from my LG-P500 using xda premium

Rockr172 said:
Uhh may we know what rom you are exactly porting?? That may help us more in guiding you...
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
it is GT540 Aosp
want to port for our phone

aspee said:
it is GT540 Aosp
want to port for our phone
Click to expand...
Click to collapse
Hmmm kewl... but you should try doing it from source... now while porting this if you are stuck, its quite tough to get outta it... look at ciaox sense port.. it just cant be completed.. sorry but all the best with it...
Sent from my LG-P500 using xda premium

yup but LG optimus net ROm is first port by GT540 devs and then we port there port to our P500
LG gt540 and LGp500 are from same manufacture so I think it's not so tough for porting
as in ciaox case he is porting HTC rom
and he success but The only problem is with that baseband related things
so htc doesn't gave the source code
that's why he was not able to port it
and I have 2 weeks to work on this port as it is diwali

aspee said:
yup but LG optimus net ROm is first port by GT540 devs and then we port there port to our P500
LG gt540 and LGp500 are from same manufacture so I think it's not so tough for porting
as in ciaox case he is porting HTC rom
and he success but The only problem is with that baseband related things
so htc doesn't gave the source code
that's why he was not able to port it
and I have 2 weeks to work on this port as it is diwali
Click to expand...
Click to collapse
O1 hardware isnt the same as Optimus SX or GT540.
Alle devices have different hardware but the GT540 - there is the same GPU and CPU, but other RIL and some more stuff.
Copy only some libs wouldnt work - some parts have to be compiled from sources or can be used by compiled libs, this needs a lot of luck.
wish you all the best and good luck

andy572 said:
O1 hardware isnt the same as Optimus SX or GT540.
Alle devices have different hardware but the GT540 - there is the same GPU and CPU, but other RIL and some more stuff.
Copy only some libs wouldnt work - some parts have to be compiled from sources or can be used by compiled libs, this needs a lot of luck.
wish you all the best and good luck
Click to expand...
Click to collapse
thank you very much,andy
I will try to learn creating from source
but what's the problem in this port
why there is no log after this
if I don't get what is problem then how could I fixed it?
please help me

you get the log when open adb (android debug bridge) from windows:
Code:
c:\>adb logcat
or just use the "ddms" application, this is the visual live debugger for android.
you can debug all code but the kernel.

andy572 said:
you get the log when open adb (android debug bridge) from windows:
Code:
c:\>adb logcat
or just use the "ddms" application, this is the visual live debugger for android.
you can debug all code but the kernel.
Click to expand...
Click to collapse
Andy i am using same method
I got logcat as listed above
I get it using
Adb logcat >> log.txt
Sent from my LG-P500 using xda premium

Related

[q] help...........[solved]

i am developing a cutom rom for lg p500 everything works execpt wifi can anyone help me please
here is the logcat
E/WifiHW ( 694): wifi_load_driver:idriverType=0
E/WifiHW ( 694): DRIVER_MODULE_ARG=firmware_path=/system/wifi/sdio-g-cdc-full11n-reclaim-roml-wme-aoe-pktfilter-wapi.bin nvram_path=/system/wifi/nvram.txt
W/WifiHW ( 694): Couldn't turn on SDIO polling: /etc/init.qcom.sdio.sh 1
E/CheckinTask( 1222): SSL error, attempting time correction: javax.net.ssl.SSLException: Not trusted server certificate
samrox144 said:
i am developing a cutom rom for lg p500 everything works execpt wifi can anyone help me please
here is the logcat
E/WifiHW ( 694): wifi_load_driver:idriverType=0
E/WifiHW ( 694): DRIVER_MODULE_ARG=firmware_path=/system/wifi/sdio-g-cdc-full11n-reclaim-roml-wme-aoe-pktfilter-wapi.bin nvram_path=/system/wifi/nvram.txt
W/WifiHW ( 694): Couldn't turn on SDIO polling: /etc/init.qcom.sdio.sh 1
E/CheckinTask( 1222): SSL error, attempting time correction: javax.net.ssl.SSLException: Not trusted server certificate
Click to expand...
Click to collapse
Have you tried using the stock driver for the WiFi? Not a developer as you can see BUT I've messed up and FIXED my share of devices and I can tell you from experience that 99.9% of the time is usually something really simple that you might be overlooking......GOOD LUCK dude!
Ok i will try
Sent from my LG Optimus One P500 using XDA App

Need help interpreting what logcat is requesting

Hey guys the title basically says it all, but I'm trying to build an ICS rom for the mytouch 4g. I'm using the DHD build as a base and im receiving this error when booting which of course boot loops it:
Code:
E/SocketListener( 1516): Obtaining file descriptor socket 'dnsproxyd' failed: Protocol not supported
I/Netd ( 1521): Netd 1.0 starting
E/Netd ( 1521): Unable to create netlink socket: Protocol not supported
E/Netd ( 1521): Unable to open quota2 logging socket
E/Netd ( 1521): Unable to start DnsProxyListener (Protocol not supported)
Any help or advice would be greatly appreciated, I'll be checking in on this thread tomorrow morning. Thanks!
Cmon guys I know you're out there
Sent from my HTC myTouch 4G using xda premium
I'm not dev but it probably a network errors,this file is in bin folder,but I'm on x10,
exemple,a fix for data drop for fxp cm7 44 is this file.try to replace it.
;-)
Thanks! I just needed to know where the file was located
Sent from my HTC myTouch 4G using xda premium

[Q] How to fix Streak5 'ARM9 has crashed' reboot problem?

Hi!
I am currently working on a CM 7.2 port for the Dell Streak 5, which I want to share soon (I can't post this in the dev forum because I don't have enough posts written just yet). Currently I am trying to find a fix or a workaround for the following problem:
Sometimes, the Streak immediately reboots and shows the Dell logo. It just shows the following kernel logs (also written to LogCat):
Code:
07-03 19:13:09.348 W/PrintK ( 83): ARM9 has CRASHED
07-03 19:13:09.348 W/PrintK ( 83): smd_diag, smem: DIAG ''
07-03 19:13:09.348 W/PrintK ( 83): ARM9 has CRASHED
07-03 19:13:09.348 W/PrintK ( 83): smd_diag, smem: DIAG ''
07-03 19:13:09.348 W/PrintK ( 83): ARM9 has CRASHED
07-03 19:13:09.348 W/PrintK ( 83): smd_diag, smem: DIAG ''
07-03 19:13:09.348 W/PrintK ( 83): ARM9 has CRASHED
07-03 19:13:09.348 W/PrintK ( 83): smd_diag, smem: DIAG ''
07-03 19:13:10.430 W/PrintK ( 83): ARM9 has CRASHED
07-03 19:13:10.430 W/PrintK ( 83): smd_diag, smem: DIAG ''
07-03 19:13:10.430 W/PrintK ( 83): ARM9 has CRASHED
07-0
When I searched the kernel source, it seems that the following lines in arch/arm/mach-msm/smd.c are responsible for this log output (ommitting the parts that are not compiled):
Code:
#if defined (CONFIG_QSD_ARM9_CRASH_FUNCTION)
void smd_diag(void)
{
char *x;
x = smem_find(ID_DIAG_ERR_MSG, SZ_DIAG_ERR_MSG);
if (x != 0)
{
SMD_CRASH_LOG( "%s, smem: DIAG '%s'\n", __func__, x);
queue_work(crash_work_queue, &smd_crash_worker);
}
}
#else /* CONFIG_QSD_ARM9_CRASH_FUNCTION */
/* ommitted (not compiled) */
#endif /* CONFIG_QSD_ARM9_CRASH_FUNCTION */
static void handle_modem_crash(void)
{
SMD_CRASH_LOG( "ARM9 has CRASHED\n");
smd_diag();
/* hard reboot if possible FIXME
if (msm_reset_hook)
msm_reset_hook();
*/
/* in this case the modem or watchdog should reboot us */
#ifndef CONFIG_QSD_ARM9_CRASH_FUNCTION /* return imediately for kernel to do something */
for (;;)
#endif /* CONFIG_QSD_ARM9_CRASH_FUNCTION */
;
}
It seems that the modem is crashing and forces the device to reboot. The severe problem is that sometimes the device ends up rebooting again and again, suddenly stuck in the Dell logo - so maybe the reboot performed by the modem is not correct. But in the optimal case the device should just reset the modem, and not reboot the entire device.
As the radio drivers are only available in binary form (of course) and the device already is EOL, I really need help to find a good workaround. Does anybody have a solution to this problem?
I discovered that there is a kernel driver available in arch/arm/mach-msm/reset_modem.c that sounds interesting. It should be able to reset the modem by writing the appropriate command to a kernel device, and which is compiled as a kernel module in the default Dell Streak kernel config. Has anybody tried this out yet?
Thanks in advance & regards
Marc
PS: I am using the Phoenix kernel by the DSC Team, added with some patches by _n0p_.
Hi Marc!
How severe this problem is?
Hi _n0p_!
It's very severe to me - I have a couple of these devices here, and it's really critical if they turn off during operation (and some of them don't even come back up again afterwards).
It would be better if the radio was reset on failure - I can afford that the devices do not have a radio connection for a couple of seconds. Or at least this is what I hope.
There's a "System Type -> Reset Modem Driver" module option in kernel.
May sound dumb, but maybe it needs it?
_n0p_ said:
There's a "System Type -> Reset Modem Driver" module option in kernel.
May sound dumb, but maybe it needs it?
Click to expand...
Click to collapse
I recompiled the kernel with this module built-in, but from what I read from the source code it's just providing a device /dev/reset_modem to enable users to reset the modem from userspace (as root). However, this will not be possible entirely if the kernel itself is rebooting already, leaving no chance to any userspace commands. I believe this has to be fixed in the kernel itself. Right now I am looking at the method smsm_reset_modem in the file smd.c which sounds quite interesting. Maybe I can deactivate the code for rebooting the device there and instead run code to reset the modem. Interestingly, setting CONFIG_QSD_ARM9_CRASH_FUNCTION to 'n' in the config leads to kernel compilation errors - so the Streak was never intented to resolve modem problems the better way...
By the way, a few minutes ago I was able to log a modem restart during the reboot loop with LogCat:
pastebin.com/9U3XPxdK (yay, I can not post links yet :/ )
This looks really ugly - but it could help during debugging the problem. It would be much nicer to know what actually forces the modem to restart... (is it possible to get the stack trace during runtime, maybe by using a special macro?)
cant you check on the build based on the cm7.2 that already at the dev section? if it is not all, at least some of it would help...
deysmacro said:
cant you check on the build based on the cm7.2 that already at the dev section? if it is not all, at least some of it would help...
Click to expand...
Click to collapse
I don't know exactly what triggers the problem - maybe the devices run fine for a long time, but crash when using GPS + network in some odd way, or when the network type switched from 2G to 3G or back - I really can't tell.
As for CM 7.2, I had to build from the sources (both Kernel and CM) in order to do fixes to the ROM etc. Maybe I could try out the CM 7.2 build, but even if the problem would (not) exist there, too, I would be back to the start.
At least yesterday I tried out the reset_modem kernel module and tried all commands I could find in the source on the device /dev/reset_modem - it just crashed the modem and the device all the time, instead of one command which was effectively doing nothing. So back to the start... :-(
man... that does sucks... well... i wish you all the best nonetheless... :good:
Where's an interesting module param:
msm_smd_debug_mask
--
Also, according to:
Code:
#define MODEM_CRASH_NOTIFY_USER
extern void qi2ccapkybd_set_led(unsigned int light);
#define MODEM_CRASH_NOTIFY_USER_0 do {qi2ccapkybd_set_led(0x0);} while(0)
#define MODEM_CRASH_NOTIFY_USER_1 do {qi2ccapkybd_set_led(0xFFFFFF);} while(0)
It should blink leds on going to reboot.
--
Marc, thank you! While looking at SMD i found the code that blinks leds on AMSS mismatch (finally!)
_n0p_ said:
Marc, thank you! While looking at SMD i found the code that blinks leds on AMSS mismatch (finally!)
Click to expand...
Click to collapse
wow...! a discovery... ! :victory:
This actually leads me to think that we now free of "Blinking LEDs problem" and maybe, just maybe changing AMSS (BB) might help with modem reset problem.
I'm currently using 366 (manics told that it has good voice quality).
_n0p_ said:
This actually leads me to think that we now free of "Blinking LEDs problem" and maybe, just maybe changing AMSS (BB) might help with modem reset problem.
I'm currently using 366 (manics told that it has good voice quality).
Click to expand...
Click to collapse
last time i downgraded from rom based on 407 to 366 and although the blinking led happens.. but phone continue to work like normal... :laugh:
and yeah... 366 does have a good voice quality... and not mention excellent cell tower reception... it is proven since i have been in the building where reception is pretty much poor.. but with 366... somehow it almost always full...
but since nobody make a custom ROM based on 366, i had to sadly use other ROM...
As it's a bit offtopic, let's continue here:
http://forum.xda-developers.com/showpost.php?p=28318630&postcount=4374
Hey _n0p_!
Yeah, that seems to be the code that leads to blinking LED sensor keys on wrong AMSS!
As for the AMSS/DSP1 partitions, I currently use the newest from the original Streak 407 firmware, which I flashed via 'fastboot flash amss amss.mbn' and 'fastboot flash dsp1 dsp1.mbn'. Maybe that leads to the problems.
So you would recommend downgrading to amss 366? Although it does not match the kernel version and Android version? Isn't this a bad idea in general?
And for the DSP1, which version do you recommend - also from 366? Or the complete 366 update.pkg?
I am currently testing the image I flashed after initially flashing the 407 package the correct way - maybe this fixes the problems. Otherwise I will try 366.
By the way: Is there a good overview available what all the other files do, e.g. fsbl.mbn, osbl.mbn, dbl.mbn and appsboot.mbn?
From what I know, DT.img is the bootloader, amss the baseband software and dsp1 the DSP software for audio. And I know it's dangerous to flash the files individually, as I was able to completely brick a device by just flashing one of these special partitions...
Well, i'm using 366 right now. Too early to tell a conclusion, but it seems like default audio output is lower then in 4062 BB.
So far no glitches.
And i'm using only AMSS.
--
AFAIK DT.mbn is firmware updater, but I might be wrong.
Also DSP also works for video processing as well.
--
Almost forgot: it seems simple to disable bb error reboot.
Maybe it's worth giving a test?
_n0p_ said:
Almost forgot: it seems simple to disable bb error reboot.
Maybe it's worth giving a test?
Click to expand...
Click to collapse
Do you mean disabling CONFIG_QSD_ARM9_CRASH_FUNCTION in the kernel config? I did this, recompiled (had to fix a small include error after that, too) and tried it out - so far it crashed again after some time of usage.
BTW, how did you disable the AMSS version check? I guess you disabled the option CONFIG_QSD_OEM_RPC_VERSION_CHECK - but it's good to know.
I thought of simply trimming that rpc probe proc.
And you are right, that's the conf value plus needs ifdefing undeclared version check (in this case), variable.
Marc, it seems like
#if 0
//#ifdef CONFIG_BUILDTYPE_SHIP
SMD_CRASH_LOG( "%s: restart system\n", __func__);
queue_delayed_work(restart_work_queue, &smd_crash_restart_worker,
MODEM_CRASH_RESTART_TIMEOUT);
#endif /* CONFIG_BUILDTYPE_SHIP */
would reboot device only if modem in reset state and camera button is pressed.
Hey n0p!
_n0p_ said:
Marc, it seems like
#if 0
//#ifdef CONFIG_BUILDTYPE_SHIP
SMD_CRASH_LOG( "%s: restart system\n", __func__);
queue_delayed_work(restart_work_queue, &smd_crash_restart_worker,
MODEM_CRASH_RESTART_TIMEOUT);
#endif /* CONFIG_BUILDTYPE_SHIP */
would reboot device only if modem in reset state and camera button is pressed.
Click to expand...
Click to collapse
I tried your code, as well as some other fixes. It always led to a kernel loop and the modem didn't come back, so in the end I just included a solution to detect the problem and continue to reboot the device.
From what I learned in the last few weeks, it seems the complete ARM processor goes down with the modem. In the end, it seems to be a hardware problem, because I noticed the following facts:
Even if I completely re-flash a device that shows an error, it still occurs - especially when the network is used.
Some devices do not show this problem and can run for a long time. Other devices that had this problem always continue to have this problem. Even after re-flashing and even using different amss/dsp1 versions and on the original software.
What's more: I also had the problem on a new device that never had a custom ROM on it. Yeah, using the original firmware.
So in the end everyone should be better off to throw away his device if this problem occurs.

[Q] How to get Boot2Gecko working on 2ndROM?

Hi all,
First-time poster and fairly new to rooting...
I have a Samsung Galaxy SII (GT-I9100, originally LBP firmware on Orange UK) which I successfully managed to flash with Odin/Heimdall to give:
CF-Root
CyanogenMod 9 RC1
Siyah 3.3.2
I then thought I'd give Boot2Gecko a try so I followed gokhanmoral's post and managed to get a page not found screen booting to the second rom.
So I checked out the B2G source code and performed a
make install-gaia
Click to expand...
Click to collapse
ensuring
adb devices
Click to expand...
Click to collapse
found my phone connected over usb - This gave me a lock screen which wouldn't respond to touch events.
After quite a bit of reading I then decided to attempt pusler new 6th July Build performing:
simg2img userdata.img data.img
heimdall detect
heimdall flash --hidden system.img
(cleared 2ndROM data and cache through CWM)
adb push data.img /sdcard/.secondrom/data.img
Click to expand...
Click to collapse
However, when I booted to the 2ndROM I gott a black screen - I tried looking through the
adb shell logcat
Click to expand...
Click to collapse
output and saw several errors similar to:
I/GeckoDump( 9894): Opened socket on 9999
E/GeckoConsole( 9894): [JavaScript Error: "NS_ERROR_UNEXPECTED: Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getCharPref]" {file: "chrome://browser/content/shell.js" line: 80}]
I/Gecko ( 9894): Logging GL tracing output to /system/b2g/firefox.trace
I/Gecko ( 9894): Attempting load of /data/local/egltrace.so
F/libc ( 9894): Fatal signal 11 (SIGSEGV) at 0x00000068 (code=1)
I/Gecko ( 9894): Attempting load of libEGL.so
D/libEGL ( 9894): egl.cfg not found, using default config
D/libEGL ( 9894): loaded /system/lib/egl/libGLES_android.so
I/Gecko ( 9894): Failed to create EGL config!
F/libc ( 9894): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1)
I/DEBUG ( 9891): debuggerd committing suicide to free the zombie!
F/libc ( 9847): Fatal signal 13 (SIGPIPE) at 0x00002677 (code=0)
I/DEBUG ( 9978): debuggerd: Jul 6 2012 04:08:21
I/ ( 9979): ServiceManager: 0xf958
V/yamaha::media::CManager( 9979): constructor
Click to expand...
Click to collapse
Seems like a Gecko Chrome error but I can't be sure. As a last ditch effort I tried to follow gokhanmoral's method of extracting/mounting pusler's images, creating tar files and placing them into a CWM flashable zip but Siyah wouldn't recognise the 2ndROM after installing so now I'm all out of ideas.
Has anyone managed to successfully install the 6th July build as a 2ndROM? Any help/info would be appreciated.
Cheers

[Q] Help this newbie

ported many roms but this is my first rom which has not stuck in boot animation screen im happy but this logcat is kind of pain.(
E/logwrapper( 111): executing /system/bin/e2fsck failed: No such file or directory
E/ ( 171): coming in huawei_oem_rapi_streaming_function! event=213.
E/mm-camera( 153): qcamsvr_start: old_mode = 3f
E/mm-camera( 153): qcamsvr_load_gesture_lib Error opening gesture library
E/mm-camera( 153): Cannot init Gesture library
E/cutils ( 143): Failed to read /data/.layout_version: No such file or directory
E/ ( 142): Qint android::get_number_of_cameras(): E
W/InterfaceController( 134): Warning (dlopen failed: library "/system/lib/libnetcmdiface.so" not found) while opening the net interface command library
after booting the rom it show com.process.phone.android stopped working , systemui stopped woorking
what is the solution ? i cant locate system/lib/libnetcmdiface.so this file neither in base nor port rom..
for which device did you port we need more info....
Thanks for answering
vovaftw said:
for which device did you port we need more info....
Click to expand...
Click to collapse
i have ported for HUawei y201 Pro
USed rom made for Huawei G300
there are so much builds of Cm which are ported from g300 to y201 pro so i tried to port pac rom but faced this thing..
guide
vovaftw said:
for which device did you port we need more info....
Click to expand...
Click to collapse
please guide me .
Thanks
add me on Skype vova50006
ok
vovaftw said:
add me on Skype vova50006
Click to expand...
Click to collapse
thanks for ans im adding you

Categories

Resources