[Dev] [CM10] Fixing in call audio bug for CM10 - LG Optimus 2x
The call issue of CM10 ROMs is present for some people. There will be a trouble when making a call each other could not hear voice or the other side would only hear big noise.
If you reboot the phone once a day (e.g. at the morning) it usually won't occur during the whole day, sometimes it will not fix the problem by reboot.
I checked the offical V30C and V28G radio logcat , and found it is differnet to the CM10 radio logcat.
you can verify this by
Code:
adb logcat -b radio
when making a call.
The offical V28G logcat radio is something like this:
Code:
D/GSM ( 351): [getVoiceMailNumber] isNetworkRoaming: false
D/PHONE ( 351): VM: PhoneSubInfo.getVoiceMailNUmber:
D/GSM ( 351): isTwoDigitShortCode
D/GSM ( 351): dialing w/ mmi 'null'...
D/GSM ( 351): [GSMConn] acquireWakeLock
D/RILJ ( 351): [0162]> DIAL
D/RILC ( 88): [0162]> DIAL (num=88888888,clir=0)
D/RILC ( 88): [0162]< DIAL
D/RILJ ( 351): [0162]< DIAL
D/RILC ( 88): [UNSL]< RIL_UNSOL_LGE_XCALLSTAT {1,2}
D/RILC ( 88): [UNSL]< UNSOL_RESPONSE_CALL_STATE_CHANGED
D/RILJ ( 351): [UNSL]< LGE_XCALLSTAT
D/RILJ ( 351): [UNSL]< UNSOL_RESPONSE_CALL_STATE_CHANGED
D/RILJ ( 351): [0163]> LGE_SET_CPATH 3
D/RILC ( 88): [0163]> RIL_REQUEST_LGE_SET_CPATH (3)
D/RILJ ( 351): [0164]> LGE_SET_CPATH 1
D/RILC ( 88): [0164]> RIL_REQUEST_LGE_SET_CPATH (1)
D/RILC ( 88): [0163]< RIL_REQUEST_LGE_SET_CPATH
D/RILJ ( 351): [0163]< LGE_SET_CPATH
D/RILC ( 88): [0164]< RIL_REQUEST_LGE_SET_CPATH
D/RILJ ( 351): [0164]< LGE_SET_CPATH
D/RILJ ( 351): [0165]> GET_CURRENT_CALLS
D/RILC ( 88): [0165]> GET_CURRENT_CALLS
D/RILC ( 88): [0166]> GET_CURRENT_CALLS
D/RILC ( 88): [0165]< GET_CURRENT_CALLS {[id=1,DIALING,toa=129,norm,mo,als=0,voc,noevp,88888888,cli=0,name='(null)',0}
D/RILJ ( 351): [0165]< GET_CURRENT_CALLS [id=1,DIALING,toa=129,norm,mo,0,voc,noevp,,cli=1,,0]
D/RILC ( 88): [0166]< GET_CURRENT_CALLS {[id=1,DIALING,toa=129,norm,mo,als=0,voc,noevp,88888888,cli=0,name='(null)',0}
D/RILJ ( 351): [0166]< GET_CURRENT_CALLS [id=1,DIALING,toa=129,norm,mo,0,voc,noevp,,cli=1,,0]
D/RILJ ( 351): [0167]> LGE_SET_CPATH 8
D/RILC ( 88): [0167]> RIL_REQUEST_LGE_SET_CPATH (8)
D/RILJ ( 351): [0168]> LGE_SET_CPATH 8
D/RILC ( 88): [0168]> RIL_REQUEST_LGE_SET_CPATH (8)
D/RILC ( 88): [0167]< RIL_REQUEST_LGE_SET_CPATH
D/RILJ ( 351): [0167]< LGE_SET_CPATH
D/RILJ ( 351): [0168]< LGE_SET_CPATH
D/RILJ ( 351): [0169]> LGE_SET_CPATH 8
D/RILC ( 88): [0169]> RIL_REQUEST_LGE_SET_CPATH (8)
D/RILC ( 88): [0169]< RIL_REQUEST_LGE_SET_CPATH
D/RILC ( 88): [0170]> RIL_REQUEST_LGE_SET_CPATH (8)
D/RILC ( 88): [0170]< RIL_REQUEST_LGE_SET_CPATH
D/RILJ ( 351): [0170]< LGE_SET_CPATH
D/RILC ( 88): [UNSL]< RIL_UNSOL_LGE_XCALLSTAT {1,3}
D/RILJ ( 351): [UNSL]< LGE_XCALLSTAT
D/RILC ( 88): [UNSL]< UNSOL_RESPONSE_CALL_STATE_CHANGED
D/RILJ ( 351): [UNSL]< UNSOL_RESPONSE_CALL_STATE_CHANGED
D/RILC ( 88): [UNSL]< RIL_UNSOL_LGE_XCALLSTAT {1,3}
D/RILC ( 88): [UNSL]< UNSOL_RESPONSE_CALL_STATE_CHANGED
D/RILJ ( 351): [0171]> GET_CURRENT_CALLS
D/RILJ ( 351): [UNSL]< LGE_XCALLSTAT
D/RILC ( 88): [0171]> GET_CURRENT_CALLS
D/RILJ ( 351): [0172]> GET_CURRENT_CALLS
D/RILC ( 88): [0172]> GET_CURRENT_CALLS
D/RILC ( 88): [0171]< GET_CURRENT_CALLS {[id=1,ALERTING,toa=129,norm,mo,als=0,voc,noevp,88888888,cli=0,name='(null)',0}
D/RILJ ( 351): [0171]< GET_CURRENT_CALLS [id=1,ALERTING,toa=129,norm,mo,0,voc,noevp,,cli=1,,0]
D/RILC ( 88): [0172]< GET_CURRENT_CALLS {[id=1,ALERTING,toa=129,norm,mo,als=0,voc,noevp,88888888,cli=0,name='(null)',0}
D/RILJ ( 351): [0172]< GET_CURRENT_CALLS [id=1,ALERTING,toa=129,norm,mo,0,voc,noevp,,cli=1,,0]
D/RILJ ( 351): [0173]> LGE_SET_CPATH 8
D/RILC ( 88): [0173]> RIL_REQUEST_LGE_SET_CPATH (8)
D/RILC ( 88): [0173]< RIL_REQUEST_LGE_SET_CPATH
D/RILJ ( 351): [0173]< LGE_SET_CPATH
D/RILC ( 88): [UNSL]< RIL_UNSOL_LGE_XCALLSTAT {1,7}
D/RILJ ( 351): [UNSL]< LGE_XCALLSTAT
D/RILC ( 88): [UNSL]< RIL_UNSOL_LGE_XCALLSTAT {1,0}
D/RILC ( 88): [UNSL]< RIL_UNSOL_LGE_COLP {88888888,type=129,subaddr=,satype=-1, alpha=}
D/RILC ( 88): [UNSL]< UNSOL_RESPONSE_CALL_STATE_CHANGED
D/RILJ ( 351): [UNSL]< LGE_XCALLSTAT
D/RILJ ( 351): [UNSL]< LGE_COLP COLP { number: 88888888, type: 129, subaddr:, satype: -1, alpha: }
D/RILJ ( 351): [UNSL]< UNSOL_RESPONSE_CALL_STATE_CHANGED
D/RILJ ( 351): [0174]> GET_CURRENT_CALLS
D/RILC ( 88): [0174]> GET_CURRENT_CALLS
D/RILC ( 88): [0174]< GET_CURRENT_CALLS {[id=1,ACTIVE,toa=129,norm,mo,als=0,voc,noevp,88888888,cli=0,name='(null)',0}
D/RILJ ( 351): [0175]> LGE_SET_CPATH 8
D/RILJ ( 351): [0174]< GET_CURRENT_CALLS [id=1,ACTIVE,toa=129,norm,mo,0,voc,noevp,,cli=1,,0]
D/RILC ( 88): [0175]> RIL_REQUEST_LGE_SET_CPATH (8)
D/RILC ( 88): [0175]< RIL_REQUEST_LGE_SET_CPATH
D/RILJ ( 351): [0175]< LGE_SET_CPATH
D/RILJ ( 351): [0176]> LGE_SET_CPATH 8
D/RILC ( 88): [0176]> RIL_REQUEST_LGE_SET_CPATH (8)
D/RILC ( 88): [0176]< RIL_REQUEST_LGE_SET_CPATH
D/RILJ ( 351): [0176]< LGE_SET_CPATH
D/RILC ( 88): [UNSL]< UNSOL_SIGNAL_STRENGTH {[signalStrength=18,bitErrorRate=-1, CDMA_SS.dbm=-1,CDMA_SSecio=-1, EVDO_SS.dbm=-1,EVDO_SS.ecio=-1, EVDO_SS.signalNoiseRatio=-1, LTE_SS.signalStrength=-1,LTE_SS.rsrp=-1,LTE_SS.rsrq=-1, LTE_SS.rssnr=-1,LTE_SS.cqi=-1]}
D/RILJ ( 351): [0177]> LGE_HANG_UP_CALL
D/RILC ( 88): [0177]> RIL_REQUEST_LGE_HANG_UP_CALL
D/RILC ( 88): [0177]< RIL_REQUEST_LGE_HANG_UP_CALL
D/RILJ ( 351): [0177]< LGE_HANG_UP_CALL
D/RILJ ( 351): [0178]> GET_CURRENT_CALLS
D/RILC ( 88): [0178]> GET_CURRENT_CALLS
D/RILC ( 88): [0178]< GET_CURRENT_CALLS {[id=1,ACTIVE,toa=129,norm,mo,als=0,voc,noevp,88888888,cli=0,name='(null)',0}
D/RILJ ( 351): [0178]< GET_CURRENT_CALLS [id=1,ACTIVE,toa=129,norm,mo,0,voc,noevp,,cli=1,,0]
D/RILJ ( 351): [0179]> LGE_SET_CPATH 8
D/RILC ( 88): [0179]> RIL_REQUEST_LGE_SET_CPATH (8)
D/RILC ( 88): [0179]< RIL_REQUEST_LGE_SET_CPATH
D/RILJ ( 351): [0179]< LGE_SET_CPATH
D/RILC ( 88): [UNSL]< UNSOL_RESPONSE_CALL_STATE_CHANGED
D/RILJ ( 351): [UNSL]< UNSOL_RESPONSE_CALL_STATE_CHANGED
D/RILC ( 88): [UNSL]< RIL_UNSOL_LGE_XCALLSTAT {1,6}
D/RILC ( 88): [UNSL]< UNSOL_RESPONSE_CALL_STATE_CHANGED
D/RILJ ( 351): [UNSL]< LGE_XCALLSTAT
D/RILJ ( 351): [UNSL]< UNSOL_RESPONSE_CALL_STATE_CHANGED
D/RILJ ( 351): [0180]> GET_CURRENT_CALLS
D/RILC ( 88): [0180]> GET_CURRENT_CALLS
D/RILJ ( 351): [0181]> GET_CURRENT_CALLS
D/RILC ( 88): [0181]> GET_CURRENT_CALLS
D/RILC ( 88): [0180]< GET_CURRENT_CALLS }
D/RILJ ( 351): [0180]< GET_CURRENT_CALLS
D/RILC ( 88): [0181]< GET_CURRENT_CALLS }
D/RILJ ( 351): [0181]< GET_CURRENT_CALLS
D/RILJ ( 351): [0182]> LGE_SET_CPATH 0
D/RILC ( 88): [0182]> RIL_REQUEST_LGE_SET_CPATH (0)
D/RILC ( 88): [0182]< RIL_REQUEST_LGE_SET_CPATH
D/RILJ ( 351): [0182]< LGE_SET_CPATH
D/RILC ( 88): [UNSL]< UNSOL_SIGNAL_STRENGTH {[signalStrength=19,bitErrorRate=-1, CDMA_SS.dbm=-1,CDMA_SSecio=-1, EVDO_SS.dbm=-1,EVDO_SS.ecio=-1, EVDO_SS.signalNoiseRatio=-1, LTE_SS.signalStrength=-1,LTE_SS.rsrp=-1,LTE_SS.rsrq=-1, LTE_SS.rssnr=-1,LTE_SS.cqi=-1]}
As you can see,
1. when the call start, the ril send
LGE_SET_CPATH 3
LGE_SET_CPATH 1 (if you make the call via headset, it will be LGE_SET_CPATH 2)
2. during the call session, the ril send
LGE_SET_CPATH 8
3. after ending the call , the ril send
LGE_SET_CPATH 0
so, I make a fix for the LGEInfineon.java(thank rmcc provide the original code, if I didn't remenber wrong...), try to simulate this command sequence in it(not very accu, but I think it will be OK).
you can put this file in your source tree “device/lge/star-common/ril/telephony/java/com/android/internal/telephony”, then rebuild the CM10 source.
Hope this can fix the CM10 call bug.
PS: lipisak built a CM10 here: http://forum.xda-developers.com/showpost.php?p=34672614&postcount=47
[WARNING]: I am not sure whether this fix will fix the audio bug or not, so it is a DEV test....
2012/11/27:
Another found : In V30C lge-ril.so, it used /dev/block/mmcblk0p5 as a datastorge for write_nvidia function, which will write IMEI, SWV, SWOV, INFO in it. But as CM partitions definition, /dev/block/mmcblk0p5 is used as boot.img....... I am not sure it will cause problem or not. But a dirty fix of lge-ril.so, which will use a hexeditor modified the binary code, would workaround this.
If in your logcat -b radio found these: write IMEI ok, write IMEI ng. write SWV ok, write SWV ng, write SWOV ok, write SWOV ng, write INFO ok, write INFO ng. then your boot.img would be corrupted.[Thank wkpark pointed out that In V30C, /dev/block/mmcblk0p5 is /misc not /data/ve, /dev/block/mmcblk0p10 is the /data/ve in V30C]
2012/11/29:
Fix MSC partition problem[PLEASE NOTE: THIS ASSUME YOU USE THE OLD GB BOOTLOADER & PARTITION, not OFFICIAL BOOTLOADER & PARTITION]
1. use the attached liblgeril.so, this is a quick fix in binary : mmcblk0p5=>mmcblk0p3
2. modified your kernel source code arch/arm/mach-tegra/lge/star/include/lge/board-star-nv.h
Code:
#ifdef CONFIG_CM_BOOTLOADER_COMPAT
#define LGE_NVDATA_PARTITION "/dev/block/mmcblk0p3"
#else
#define LGE_NVDATA_PARTITION "/dev/block/mmcblk0p5"
#endif
then recompile your kernel.
3. fix init.rc. modify the rild group id:
Code:
group radio cache inet misc audio sdcard_rw log system media_rw
4. fix uevent.tegra.rc, add a line at bottom:
Code:
/dev/block/mmcblk0p3 0660 system radio
2012/12/04:
Found a temp fix for this, when you encounter the call bug, just reboot into recovery, do nothing, reboot. This will fix the phone for a while..
2012/12/07:
By compare linux 3.6.9 kernel source to V30C kernel source code, I found that the V30C kernel source wm8994.c has some bugs in it. There are a copy/paste bug and many "switch" "case" "break" mismatch bugs. I made a patch file to fix this. Goto your kernel source sound/soc/codes, input patch wm8994.c < wm8994.diff
2012/12/25:
Another fix for audio problem:
During the wm8994 suspend/resume , it use a unsafe version of read/write registers. I just modify the code , use a mutex lock protect version of register read/write.
Hope this can make some help.
https://github.com/marsgod/lge-kernel-star/commit/02fab112d1dc63387b4474fbcf99e7bb9d617236
I guess when an incoming call trigger, the wm8994 resume, it will take a long time 'restore' the wm8994 registers(because it use the I2C interface), if this process were interrupted by another read/write wm8994 attemp, it will cause problem.
2012/12/29:
Based on above patch, I built two kernel for P990 & SU660, as the attached files. Please have a try.
Just use CWM flash these zip files. The zip file will only update your kernel & modules, there is NO need make a factory reset or clean your cache/data.
EDIT: for P990 kernel , please check http://forum.xda-developers.com/showpost.php?p=36032539&postcount=661
If this will work, you're my 'effin hero!
EDIT: Can somebody tell me where do I need to put the files more exactly? I searched for the location mentioned in the first post but couldn't find it...
Let the testing begin
this is was I'm talking about let´s see how it is a will five u my thanks just for u tried!
---------- Post added at 04:48 PM ---------- Previous post was at 04:32 PM ----------
wwewwf996 said:
If this will work, you're my 'effin hero!
EDIT: Can somebody tell me where do I need to put the files more exactly? I searched for the location mentioned in the first post but couldn't find it...
Click to expand...
Click to collapse
same question here to put the file?
thought i'm the only one ...lol
anjo88 said:
this is was I'm talking about let´s see how it is a will five u my thanks just for u tried!
---------- Post added at 04:48 PM ---------- Previous post was at 04:32 PM ----------
same question here to put the file?
Click to expand...
Click to collapse
No where. Its source code, need to be built with cm10 stuff.
Marsgod, why don't you write some notes into official repo for arcee?
Sent from my LG-P990 using xda app-developers app
can anyone rebuild cm10 with that?
i hope its work
anjo88 said:
this is was I'm talking about let´s see how it is a will five u my thanks just for u tried!
---------- Post added at 04:48 PM ---------- Previous post was at 04:32 PM ----------
same question here to put the file?
Click to expand...
Click to collapse
As you can see the thread has a [DEV] in the title. Did ever cross your mind that if you don't know what to do with this file you are not addressed?
Building right now with the new LGEInfineon.java. Will test as soon as it's done
Thanks for this one !
Hm the problem will be trying to reproduce the in call bug.. but thanks in advance nevertheless
Sent from my LG-P990 using Tapatalk
pengus77 said:
Building right now with the new LGEInfineon.java. Will test as soon as it's done
Thanks for this one !
Click to expand...
Click to collapse
Can u share it when it´s build?
---------- Post added at 05:46 PM ---------- Previous post was at 05:45 PM ----------
May-C said:
As you can see the thread has a [DEV] in the title. Did ever cross your mind that if you don't know what to do with this file you are not addressed?
Click to expand...
Click to collapse
U said? if i have umbunto a rebuild at my own!
In the first post it is mentioned that the sources came from RC. But if I compare the "fixed" LGEInfineon.java with the ones I find in Github it doesn't seem to be based on one of them.
Is it based on a uncommited Source or something like that?
this is off topic, but ricardo cequeira just uploaded a new screenshot on google plus android version 4.2 https://plus.google.com/photos/115049428938715274412/albums/5815099440000881585/5815099446397047970
omg this is the 5th thread with this screenshots from RC... really guys?!
May-C said:
In the first post it is mentioned that the sources came from RC. But if I compare the "fixed" LGEInfineon.java with the ones I find in Github it doesn't seem to be based on one of them.
Is it based on a uncommited Source or something like that?
Click to expand...
Click to collapse
It seems to be based on this:
https://github.com/CyanogenMod/andr...m/android/internal/telephony/LGEInfineon.java
crazyon3 said:
this is off topic, but ricardo cequeira just uploaded a new screenshot on google plus android version 4.2 https://plus.google.com/photos/115049428938715274412/albums/5815099440000881585/5815099446397047970
Click to expand...
Click to collapse
Why post it here if you know that is is off topic?
May-C said:
In the first post it is mentioned that the sources came from RC. But if I compare the "fixed" LGEInfineon.java with the ones I find in Github it doesn't seem to be based on one of them.
Is it based on a uncommited Source or something like that?
Click to expand...
Click to collapse
Yeah man, according to diff it looks not like "fixed", it more looks like "complete rewrited"
Code:
33a34,36
> /* Headset detect stuffs */
> import android.media.AudioManager;
>
50a54,55
>
> audioManager = (AudioManager)context.getSystemService(Context.AUDIO_SERVICE);
81c86,91
< static final int RIL_UNSOL_LGE_SIM_STATE_CHANGED_NEW = 1061;
---
> static final int RIL_UNSOL_LGE_1X_REG_DONE = 1061;
> static final int RIL_UNSOL_LGE_XCALLSTAT = 1052;
> static final int RIL_UNSOL_LGE_COLP = 1036;
> static final int RIL_UNSOL_LGE_FACTORY_READY = 1080;
>
> static final int RIL_REQUEST_LGE_SET_CPATH=252;
92c102,104
< case 1080: ret = responseVoid(p); break; // RIL_UNSOL_LGE_FACTORY_READY
---
> case RIL_UNSOL_LGE_COLP: ret = responseVoid(p); break;
> case RIL_UNSOL_LGE_XCALLSTAT: ret = responseInts(p); break;
> case RIL_UNSOL_LGE_FACTORY_READY: ret = responseVoid(p); break;
94c106
< case RIL_UNSOL_LGE_SIM_STATE_CHANGED_NEW: ret = responseVoid(p); break;
---
> case RIL_UNSOL_LGE_1X_REG_DONE: ret = responseVoid(p); break;
128c140,155
< case 1080: // RIL_UNSOL_LGE_FACTORY_READY (NG)
---
> case RIL_UNSOL_LGE_XCALLSTAT:
> if (RILJ_LOGD) unsljLogRet(response, ret);
>
> // +XCALLSTAT: 1,2 => LGE_SET_CPATH 3, then send LGE_SET_CPATH 1
> SetupCallCPATH(ret);
> // GET_CURRENT_CALLS [id=1,DIALING,toa=129,norm,mo,0,voc,noevp,,cli=1,,0] => LGE_SET_CPATH 8
> // GET_CURRENT_CALLS [id=1,ALERTING,toa=129,norm,mo,0,voc,noevp,,cli=1,,0] => LGE_SET_CPATH 8
> // GET_CURRENT_CALLS [id=1,ACTIVE,toa=129,norm,mo,0,voc,noevp,,cli=1,,0] => LGE_SET_CPATH 8
> // GET_CURRENT_CALLS } => LGE_SET_CPATH 0
> // +XCALLSTAT: 1,2 => LGE_SET_CPATH 3, then send LGE_SET_CPATH 1
>
> mCallStateRegistrants
> .notifyRegistrants(new AsyncResult(null, null, null));
> break;
>
> case RIL_UNSOL_LGE_FACTORY_READY: // RIL_UNSOL_LGE_FACTORY_READY (NG)
130c157
< RIL_REQUEST_HANG_UP_CALL = 206;
---
> // RIL_REQUEST_HANG_UP_CALL = 206;
133c160
< case RIL_UNSOL_LGE_SIM_STATE_CHANGED_NEW:
---
> case RIL_UNSOL_LGE_1X_REG_DONE:
171a199,255
> @Override
> protected void
> processSolicited (Parcel p) {
> int serial, error;
> int dataPosition = p.dataPosition(); // save off position within the Parcel
>
> serial = p.readInt();
> error = p.readInt();
>
> RILRequest rr;
>
> rr = findAndRemoveRequestFromList(serial);
>
> if (rr == null) {
> riljLog("Unexpected solicited response! sn: " + serial + " error: " + error);
> return;
> }
>
> Object ret = null;
>
> if (error == 0 || p.dataAvail() > 0) {
> // either command succeeds or command fails but with data payload
> switch (rr.mRequest) {
> case RIL_REQUEST_LGE_SET_CPATH: ret = responseVoid(p); break;
> default:
>
> // recovery the removed request
> synchronized (super.mRequestsList) {
> super.mRequestsList.add(rr);
> super.mRequestMessagesWaiting++;
> }
> // Rewind the Parcel
> p.setDataPosition(dataPosition);
>
> // Forward responses that we are not overriding to the super class
> super.processSolicited(p);
> return;
> }
> }
>
> if (error != 0) {
> rr.onError(error, ret);
> rr.release();
> return;
> }
>
> if (RILJ_LOGD) riljLog(rr.serialString() + "< " + requestToString(rr.mRequest)
> + " " + retToString(rr.mRequest, ret));
>
> if (rr.mResult != null) {
> AsyncResult.forMessage(rr.mResult, ret, null);
> rr.mResult.sendToTarget();
> }
>
> rr.release();
> }
>
219a304,395
> private AudioManager audioManager;
>
> private void
> SetupCallCPATH(Object ret) {
> int CPATH=0;
> int CallState = ((int[])ret)[1];
>
> if (RILJ_LOGD) riljLog(" CALLSTATE=[ " + CallState + "]");
> if(CallState == 2) {
> // +XCALLSTAT: 1,2 => LGE_SET_CPATH 3, then send LGE_SET_CPATH 1
> CPATH=3;
> RILRequest rr = RILRequest.obtain(RIL_REQUEST_LGE_SET_CPATH,null);
>
> if (RILJ_LOGD) riljLog(rr.serialString() + "> " + requestToString(rr.mRequest) + " " + CPATH);
>
> rr.mp.writeInt(1);
> rr.mp.writeInt(CPATH);
> send(rr);
>
> // normal call: CPATH=1
> // Headset call: CPATH=2
> // BT call: isBluetoothA2dpOn()??
> if (audioManager.isWiredHeadsetOn()==false && audioManager.isBluetoothA2dpOn()==false)
> CPATH=1;
> else
> CPATH=2;
> RILRequest rr2 = RILRequest.obtain(RIL_REQUEST_LGE_SET_CPATH,null);
>
> if (RILJ_LOGD) riljLog(rr2.serialString() + "> " + requestToString(rr2.mRequest) + " " + CPATH);
>
> rr2.mp.writeInt(1);
> rr2.mp.writeInt(CPATH);
> send(rr2);
> }
> }
>
> @Override
> protected Object
> responseCallList(Parcel p) {
> int num;
> int CPATH=0;
> int dataPosition = p.dataPosition(); // save off position within the Parcel
>
> num = p.readInt();
>
> if (num==0)
> {
> // LGE_SET_CPATH 0
> CPATH=0;
> }
> else
> if (num>0)
> {
> // LGE_SET_CPATH 8
> CPATH=8;
> }
> RILRequest rr = RILRequest.obtain(RIL_REQUEST_LGE_SET_CPATH,null);
>
> if (RILJ_LOGD) riljLog(rr.serialString() + "> " + requestToString(rr.mRequest) + " " + CPATH);
>
> rr.mp.writeInt(1);
> rr.mp.writeInt(CPATH);
> send(rr);
>
> // Rewind the Parcel
> p.setDataPosition(dataPosition);
>
> // Forward responses that we are not overriding to the super class
> return super.responseCallList(p);
> }
>
> static String
> requestToString(int request) {
> switch(request) {
> case RIL_REQUEST_LGE_SET_CPATH: return "LGE_SET_CPATH";
> default: return RIL.requestToString(request);
> }
> }
>
> static String
> responseToString(int request)
> {
> switch(request) {
> case RIL_UNSOL_LGE_COLP: return "LGE_COLP";
> case RIL_UNSOL_LGE_XCALLSTAT: return "LGE_XCALLSTAT";
> case RIL_UNSOL_LGE_FACTORY_READY: return "LGE_FACTORY_READY";
> case RIL_UNSOL_LGE_SIM_STATE_CHANGED: return "LGE_SIM_STATE_CHANGED";
> case RIL_UNSOL_LGE_1X_REG_DONE: return "LGE_1X_REG_DONE";
> default: return RIL.responseToString(request);
> }
> }
>
just sharing i guess lol
ergoen said:
It seems to be based on this:
https://github.com/CyanogenMod/andr...m/android/internal/telephony/LGEInfineon.java
Click to expand...
Click to collapse
Oh I think you are right. Must have been blind
But there are still a lot of changes I didn't except.
Ok, tested a couple calls with this fix and all seems fine so far. Using BB 725 v20I. Quality is good and nothing wrong both when calling and when receiving. Of course phone uptime is 8 minutes... will report back in a few hours.
Related
Porting AOSP*1.6
Hi,
I don't know if it's the right section but..
I'm trying to port AOSP 1.6 on Galaxy. After a few mod on init.rc, the system boot and work. Now, i want to have phone, and perhaps other things working on.
To make phone working, i tried to use the same libsec-ril.so from 1.5, but i got :
I/RILJ ( 2548): Couldn't find 'rild' socket; retrying after timeout
I/RIL ( 8488): Opening tty device /dev/ttyS0
I/RILJ ( 2548): Couldn't find 'rild' socket; retrying after timeout
I/RILJ ( 2548): Couldn't find 'rild' socket; retrying after timeout
I/RILJ ( 2548): Couldn't find 'rild' socket; retrying after timeout
I/RILJ ( 2548): Couldn't find 'rild' socket; retrying after timeout
I/RILJ ( 2548): Couldn't find 'rild' socket; retrying after timeout
I/RILJ ( 2548): Couldn't find 'rild' socket; retrying after timeout
E/RILJ ( 2548): Couldn't find 'rild' socket after 8 times, continuing to retry silently
E/RIL ( 8488): Failed to start RX reader thread
E/RILC ( 8488): RIL_register: RIL_RadioFunctions * null or invalid version (expected 2)
Click to expand...
Click to collapse
i also try with libreference-ril :
E/RILJ ( 2548): Hit EOS reading message length
I/RILJ ( 2548): Disconnected from 'rild' socket
I/RIL ( 8330): Opening tty device /dev/ttyS0
D/RILC ( 8330): startMultiClientSocket() START
D/RILC ( 8330): startMultiClientSocket() fd=8 END
I/RILJ ( 2548): Connected to 'rild' socket
D/RILC ( 8330): removeWatch: fd=11
I/RILC ( 8330): libril: new connection=12
D/RILC ( 8330): [UNSL]< UNSOL_RESPONSE_RADIO_STATE_CHANGED {RADIO_UNAVAILABLE}
D/RILC ( 8330): sendResponseRaw(): fd=12, header=201326592
D/RILC ( 8330): sendResponseRaw(): fd=12, dataSize=12
I/RILC ( 8330): RIL Daemon version: android reference-ril 1.0
D/RILJ ( 2548): [UNSL]< UNSOL_RESPONSE_RADIO_STATE_CHANGED RADIO_UNAVAILABLE
D/RILC ( 8330): processTimeouts: fd=-1
Click to expand...
Click to collapse
Anyone know what happens ? I don"t know if it the right way, or if i simply run into a wall...
[Q] Need Help!
Hi xda, I have a problem with the network sgs. When I turn sgs he does not see SIM card, and radio module completely (slashed circle), does not make an emergency call. But, when I run Root Explorer and mount the system in the RW, sgs begins to see the SIM, but imei is empty! Does not ask for unlock code. When I try to change files in a efs folder - everything goes, but, when I reboot device - efs folder appears empty, well, then I put the system RW and come back again the default files! Please help me! What's the problem? What should I do? I've tried everything that is possible! But nothing helped It's adb radio log HTML: D/RIL ( 3578): check_nv_data_validity: D/RIL ( 3578): check_nv_data_size: E/RIL ( 3578): check_nv_data_size: stat failed on /efs/nv_data.bin. No such file or directory. D/RIL ( 3578): record_nv_log: D/RIL ( 3578): check_md5: D/RIL ( 3578): compute_md5: path /efs/nv_data.bin E/RIL ( 3578): compute_md5: open(/efs/nv_data.bin) fail. No such file or directory. E/RIL ( 3578): NV data tainted! Restoring... D/RIL ( 3578): check_md5: D/RIL ( 3578): compute_md5: path /efs/.nv_data.bak E/RIL ( 3578): compute_md5: open(/efs/.nv_data.bak) fail. No such file or directory. E/RIL ( 3578): No valid backup data. Create default nv data. D/RIL ( 3578): create_default_nv_data: D/RIL ( 3578): compute_md5: path /efs/nv_data.bin E/RIL ( 3578): compute_md5: open(/efs/nv_data.bin) fail. No such file or directory. D/RIL ( 3578): /efs/nv_data.bin md5 : D/RIL ( 3578): make_md5_file: (/efs/nv_data.bin.md5) E/RIL ( 3578): open error: /efs/nv_data.bin.md5 (Read-only file system) D/RIL ( 3578): xmit_nvdata: loading /efs/nv_data.bin... E/RIL ( 3578): nvdata file open failed. No such file or directory. D/RIL ( 3578): create_default_nv_data: E/RIL ( 3578): xmit_nvdata: open default nv data failed. No such file or directory. D/RIL ( 3578): NV data load fail. r -1 D/RIL ( 3578): Boot up process done E/RILClient( 2356): Connect_RILD: Connecting failed. Connection refused(111) E/RIL ( 3578): phone booting failed! restart Rild. D/RIL ( 3578): prv_exit() called E/RILClient( 2356): Connect_RILD: Connecting failed. Connection refused(111) E/RILClient( 2356): Connect_RILD: Connecting failed. Connection refused(111) E/RIL ( 3617): loadOpnameStaticTable(): count(765) E/RIL ( 3617): deactivate_virtual_inet() E/RIL ( 3617): down_network_interface(): failed to down interface pdp0 (errno: 19) E/RIL ( 3617): Net intf down result: -1 E/RIL ( 3617): deactivate_virtual_inet() E/RIL ( 3617): down_network_interface(): failed to down interface pdp1 (errno: 19) E/RIL ( 3617): Net intf down result: -1 E/RIL ( 3617): deactivate_virtual_inet() E/RIL ( 3617): down_network_interface(): failed to down interface pdp2 (errno: 19) E/RIL ( 3617): Net intf down result: -1 E/RIL ( 3617): OemInitGps E/RIL ( 3617): No battery calibration data found. E/RIL ( 3617): [*] RIL initialized: TID(3617) E/RIL ( 3617): isRildInit : 0 D/RIL ( 3617): __boot_6160 E/RIL ( 3617): __boot_6160: connman_inet_ifindex found svnet0. E/RIL ( 3617): __boot_6160:svnet failed to down svnet0 (6). No such file or directory. D/RIL ( 3617): prepare_PSI D/RIL ( 3617): Bootloader IMG Size: 0x00005000 D/RIL ( 3617): send PHONE "off" command D/RIL ( 3617): send PHONE "on" command D/RIL ( 3617): xmit_bootloader D/RIL ( 3617): Sending AT in ASCII D/RIL ( 3617): Got Bootcore version and related info!!! D/RIL ( 3617): - nCoreVer = 0xf0 D/RIL ( 3617): - nInforSize = 0x16 D/RIL ( 3617): Sending PSI data: 20480 bytes E/RILClient( 2356): Connect_RILD: Connecting failed. Connection refused(111) E/RIL ( 3617): PSI ACK read done(try #22) D/RIL ( 3617): PSI sending is done D/RIL ( 3617): __boot_6160: Waiting for 0x12341234 D/RIL ( 3617): Waiting for 12341234 D/RIL ( 3617): read: 12341234 D/RIL ( 3617): wait cmd done D/RIL ( 3617): Mapping addr: 0x40009000 D/RIL ( 3617): Modem image load done D/RIL ( 3617): xmit_nvdata: D/RIL ( 3617): md5_enable: on 1 D/RIL ( 3617): refresh_md5_file: /efs/nv_data.bin D/RIL ( 3617): __refresh_md5_file: md5_path /efs/nv_data.bin.md5 D/RIL ( 3617): compute_md5: path /efs/nv_data.bin E/RIL ( 3617): compute_md5: open(/efs/nv_data.bin) fail. No such file or directory. E/RIL ( 3617): __refresh_md5_file: Can't open /efs/nv_data.bin.md5. Read-only file system. D/RIL ( 3617): record_nv_log: D/RIL ( 3617): refresh_md5_file: done D/RIL ( 3617): record_nv_log: D/RIL ( 3617): backup_nv_data: src /efs/nv_data.bin dst /efs/.nv_data.bak D/RIL ( 3617): record_nv_log: D/RIL ( 3617): __refresh_md5_file: md5_path /efs/.nv_data.bak.md5 D/RIL ( 3617): compute_md5: path /efs/.nv_data.bak E/RIL ( 3617): compute_md5: open(/efs/.nv_data.bak) fail. No such file or directory. E/RIL ( 3617): __refresh_md5_file: Can't open /efs/.nv_data.bak.md5. Read-only file system. D/RIL ( 3617): record_nv_log: D/RIL ( 3617): record_nv_log: D/RIL ( 3617): copy_file: D/RIL ( 3617): (/efs/.nv_data.bak) open failed with No such file or directory D/RIL ( 3617): backup_nv_data: back up done D/RIL ( 3617): record_nv_log: E/RIL ( 3617): md5_enable: Can't save MD5 state. Read-only file system. D/RIL ( 3617): load_md5_state: MD5 state 1
so your IMEI is corrupt ?? what does it say when you dial *#06# ? IMEI issues generally get resolved when flashing back to froyo ROMs
When I dial * # 06 # it says IMEI (all empty) I tried to flash froyo ROMs, it did not help
Surely no man who faced the same problem as me?
Can somebody help me? (
Can somebody help me? ( THE SEARCH BUTTON NOT WORKING ) You need to restore your backed up EFS folder as per the instructions . No backup http://forum.xda-developers.com/showthread.php?t=881162 That fails proof of ownership and original IMEI receipt etc . Contact Samsung . That fails sell as broken phone . jje
I said, I've tried, and these instructions, too! agrozz said: When I try to change files in a efs folder - everything goes, but, when I reboot device - efs folder appears empty, well, then I put the system RW and come back again the default files! Click to expand... Click to collapse
can someone help me?
[Q] Bluetooth logcat...
does anyone understand this? lol im trying to fix bluetooth on senselx rom.. D/MCPMonitorService( 272): starting daemon! D/MCPMonitorService( 272): state of daemon after start: running started: true D/skia ( 272): purging 167K from font cache [18 entries] D/dalvikvm( 272): GC freed 17074 objects / 878752 bytes in 270ms D/JBtlBmg ( 272): destroy: Entered D/ ( 272): NativeJBtlBmg_Destroy: Entered D/ ( 272): NativeJBtlBmg_Destroy: Calling BTL_BMG_Destroy D/ ( 272): NativeJBtlBmg_Destroy: BTL_BMG_Destroy returned 1 D/ ( 272): NativeJBtlBmg_Destroy:Exiting Successfully D/JBtlBmg ( 272): After NativeJBtlBmg_Destroy, status=FAILED D/JBtlBmg ( 272): destroy: Exiting D/JBtlBmg ( 272): create: Entered D/JBtlBmg ( 272): Calling NativeJBtlBmg_Create D/ ( 272): NativeJBtlBmg_Create: Entered D/ ( 272): NativeJBtlBmg_Create: Calling BTL_BMG_Remote_Create D/ ( 272): NativeJBtlBmg_Create: BTL_BMG_Remote_Create returned 0, context: 1 D/ ( 272): NativeJBtlBmg_Create: Calling BTL_BMG_SetEventForwardingMode D/ ( 272): NativeJBtlBmg_Create: BTL_BMG_SetEventForwardingMode returned 0 D/JBtlProfileContext( 272): setValue: setValue called, value:1 D/ ( 272): NativeJBtlBmg_Create:Exiting Successfully D/JBtlBmg ( 272): After NativeJBtlBmg_Create, status=SUCCESS, Context = 1 D/JBtlBmg ( 272): create: Exiting D/JBtlCommon( 272): radioOn: Entered D/JBtlCommonNative( 272): NativeJBtlCommon_RadioOn: Calling BTL_RadioOn D/JBtlCommonNative( 272): NativeJBtlCommon_RadioOn: BTL_RadioOn Returned 2 D/JBtlCommon( 272): radioOn: After NativeJBtlCommon_RadioOn, status=PENDING D/BluetoothService( 272): Bluetooth state 10 -> 11 D/BluetoothService( 272): Sending ACTION_STATE_CHANGED intent, new mBluetoothState = 11 D/BluetoothAvrcpService( 272): Received intent with action: android.bluetooth.adapter.action.STATE_CHANGED D/BluetoothPbapService( 272): Received intent with action: android.bluetooth.adapter.action.STATE_CHANGED D/BluetoothA2dpService( 272): Received intent with action: android.bluetooth.adapter.action.STATE_CHANGED D/JBtlCommonNative( 272): signal_BTL_EVENT_HCI_INIT_ERROR: status = 0 D/JBtlCommon( 272): In hciInitError D/BluetoothService( 272): Callback - hciInitError, status = SUCCESS D/JBtlCommonNative( 272): After the call to HCI Init Error V/BluetoothEventRedirector( 4859): Received android.bluetooth.adapter.action.STATE_CHANGED D/BT HS/HF( 436): gsmAsuToSignal=28 D/dalvikvm( 436): GC freed 1729 objects / 82656 bytes in 128ms D/JBtlCommonNative( 272): signal_BTL_EVENT_HCI_INIT_ERROR: status = 0 D/JBtlCommon( 272): In hciInitError D/BluetoothService( 272): Callback - hciInitError, status = SUCCESS D/JBtlCommonNative( 272): After the call to HCI Init Error D/BT HS/HF( 436): gsmAsuToSignal=27 D/BT HS/HF( 436): gsmAsuToSignal=28 D/dalvikvm( 440): GC freed 219 objects / 7576 bytes in 127ms D/BT HS/HF( 436): gsmAsuToSignal=29 E/BluetoothService( 272): got timeout (or bad status) switching bluetooth state! indicating non-responsiveness to MCPMonitor D/MCPMonitorService( 272): indicateNotResponding: refcount: 1 D/MCPMonitorService( 272): will stop deamon and reset refcount D/MCPMonitorService( 272): stopping daemon. force: true D/MCPMonitorService( 272): calling all onStop callbacks D/BluetoothService( 272): onDeamonStop: forceStop: true D/BluetoothService( 272): onDeamonStop: forceStop - simulating radio off D/BluetoothService( 272): Callback - radioOffComplete, status = SUCCESS D/MCPMonitorService( 272): state of daemon after stop: stopped stopped: true D/MCPMonitorService( 272): shuting down chip... D/BluetoothService( 272): Bluetooth state 11 -> 10 D/BluetoothService( 272): Sending ACTION_STATE_CHANGED intent, new mBluetoothState = 10 D/BluetoothAvrcpService( 272): Received intent with action: android.bluetooth.adapter.action.STATE_CHANGED D/BluetoothPbapService( 272): Received intent with action: android.bluetooth.adapter.action.STATE_CHANGED D/BluetoothA2dpService( 272): Received intent with action: android.bluetooth.adapter.action.STATE_CHANGED V/BluetoothEventRedirector( 4859): Received android.bluetooth.adapter.action.STATE_CHANGED D/BT HS/HF( 436): gsmAsuToSignal=30 D/BT HS/HF( 436): gsmAsuToSignal=29 D/dalvikvm( 433): GC freed 69 objects / 3152 bytes in 102ms D/skia ( 779): purging 93K from font cache [12 entries] D/dalvikvm( 779): GC freed 2455 objects / 120680 bytes in 151ms
[Q] GPS Driver Dead? How to fix?
The GPS is not starting up, tried everything. Flashing new GPS configuration, Cleaning GPS data with angry GPS, Booting, reebooting. i9000 running CM7 7.1.0 Stable It started after following this Post http://forum.xda-developers.com/showthread.php?t=1182735 -GPS Antenna is on -The gps notification used to blink while trying to fix a position, now it doesn't even show up. Please Help Part of a alogcat file where the same error keeps repeating itself while the antenna is on. E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2) I/GPS ( 191): [gps_state_done][line = 293] : successfully called E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2) I/GPS ( 191): [gps_state_done][line = 293] : successfully called E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2) I/GPS ( 191): [gps_state_done][line = 293] : successfully called E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2) I/GPS ( 191): [gps_state_done][line = 293] : successfully called E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2) I/GPS ( 191): [gps_state_done][line = 293] : successfully called E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2) I/GPS ( 191): [gps_state_done][line = 293] : successfully called E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2) I/GPS ( 191): [gps_state_done][line = 293] : successfully called E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2) I/GPS ( 191): [gps_state_done][line = 293] : successfully called E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
Can anyone give me a hint please? biomanuel666 said: The GPS is not starting up, tried everything. Flashing new GPS configuration, Cleaning GPS data with angry GPS, Booting, reebooting. i9000 running CM7 7.1.0 Stable It started after following this Post http://forum.xda-developers.com/showthread.php?t=1182735 -GPS Antenna is on -The gps notification used to blink while trying to fix a position, now it doesn't even show up. Please Help Part of a alogcat file where the same error keeps repeating itself while the antenna is on. E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2) I/GPS ( 191): [gps_state_done][line = 293] : successfully called E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2) I/GPS ( 191): [gps_state_done][line = 293] : successfully called E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2) I/GPS ( 191): [gps_state_done][line = 293] : successfully called E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2) I/GPS ( 191): [gps_state_done][line = 293] : successfully called E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2) I/GPS ( 191): [gps_state_done][line = 293] : successfully called E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2) I/GPS ( 191): [gps_state_done][line = 293] : successfully called E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2) I/GPS ( 191): [gps_state_done][line = 293] : successfully called E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2) I/GPS ( 191): [gps_state_done][line = 293] : successfully called E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2) Click to expand... Click to collapse Please help me out with this!
GPS no longer working You have a GT-I9000, yet you have sought the answer to your problem on a Vibrant thread. Did you, by any chance, install CM7 for the Vibrant onto your GT-I9000, find a problem with the GPS, and look for the answer within the Vibrant thread? If you could supply a little more background information, then this would be helpful.
(HELP) RootBox Rom Build
Trying to compile a rootbox vanilla build for qinara (4.2.2 / host:s2) When I logcat e (error), I get this... Code: Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\John>cd android/sdk/platform-tools C:\Users\John\Android\sdk\platform-tools>adb logcat d - waiting for device - ^C C:\Users\John\Android\sdk\platform-tools>adb logcat e - waiting for device - ^C C:\Users\John\Android\sdk\platform-tools>adb logcat e - waiting for device - --------- beginning of /dev/log/main I/init.qcom.modem_links.sh( 157): modem_fw.mdt: No such file or directory I/init.qcom.modem_links.sh( 157): /system/etc/init.qcom.modem_links.sh[83]: bre ak: can't break I/init.qcom.modem_links.sh( 157): /system/etc/init.qcom.modem_links.sh[170]: br eak: can't break D/ ( 261): MOTO_PUPD: mot_boot_mode D/ ( 261): MOTO_PUPD: mot_boot_mode : normal E/mm-camera( 259): E/mm-camera( 259): Camera Daemon starting D/QSEECOMD: ( 263): qseecom listener services process entry PPID = 1 D/QSEECOMD: ( 263): Parent qseecom daemon process terminated!! D/QSEECOMD: ( 289): qseecom listener service threads starting!!! D/QSEECOMD: ( 289): Total listener services to start = 2 D/QSEECOMD: ( 289): Init dlopen(libdrmfs.so, RTLD_NOW) succeeds D/QSEECOMD: ( 289): Init::Init dlsym(g_FSHandle fs_start) succeeds D/QSEECOMAPI: ( 289): QSEECom_register_listener 10 sb_length = 0x5000 D/DrmLibFs( 289): registering fs service to QSEECom is done! D/DrmLibFs( 289): begin to create a thread! D/DrmLibFs( 289): Creating a pthread in fs_start is done! return 0 D/QSEECOMD: ( 289): Init fs_start ret = 0 D/QSEECOMD: ( 289): file system services: Started D/DrmLibFs( 289): Dispatch starts! D/DrmLibFs( 289): before calling ioctl to read the next cmd D/QDUMPD ( 286): Start polling. D/BHD ( 285): Battery Health Daemon start! I/ATVC ( 283): atvc_pal_production_part: start I/ATVC ( 283): dbval_production_part: determined production part I/ATVC ( 283): atvc_pal_init_factory_state: start I/ATVC ( 283): atvc_pal_init_factory_state: determined out of factory state I/ATVC ( 283): atval_pal_read_datablock: enter I/ATVC ( 283): atval_pal_read_datablock: getting size of datablock D/QDUMPD ( 286): dump polling (/dev/ramdump_smem) D/QDUMPD ( 286): dump polling (/dev/coredump_riva) D/QDUMPD ( 286): dump polling (/dev/ramdump_modem_sw) I/DEBUG ( 273): debuggerd: Apr 21 2013 00:38:24 D/QDUMPD ( 286): dump polling (/dev/ramdump_riva) D/QDUMPD ( 286): dump polling (/dev/ramdump_modem_fw) I/installd( 279): installd firing up D/QDUMPD ( 286): dump polling (/dev/coredump_modem) I/graphicsd( 287): graphicsd - version: 1.0 I/graphicsd( 287): graphicsd - watching [/sys/class/kgsl/kgsl-3d0/snapshot/time stamp][fd: 3] D/BHD ( 285): EEPROM - Battery ID = 898bc7a41c0050b7 I/ATVC ( 283): atval_pal_read_datablock: exit I/ATVC ( 283): atval_enforce_android_policy: validation failed. all disable d. I/ATVC ( 283): read handset resource access flags: I/ATVC ( 283): 0x00000000 I/ATVC ( 283): atval_setup_properties: valid datablock - setting flags D/BHD ( 285): NVM Read - Opened NVM file /pds/batt_health/batt-898bc7a41c00 50b7_0 E/mm-camera( 259): GETTING MCTL INFO I/ATVC ( 283): atval_enforce_android_policy: finalize the properties I/DMM ( 346): DMM available. movable_start_bytes at --------- beginning of /dev/log/system I/Vold ( 266): Vold 2.1 (the revenge) firing up V/XTWiFi ( 354): [MessageQ] creating server socket I/location-mq( 335): [XTWiFi-MessageQ] creating server socket V/XTWiFi ( 354): [MessageQ] binding server socket to name [/data/misc/location /mq/location-mq-s] I/location-mq( 335): [XTWiFi-MessageQ] binding server socket to name [/data/mis c/location/mq/location-mq-s] D/Vold ( 266): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media ) D/Vold ( 266): Volume usbdisk_1.1.1 state changing -1 (Initializing) -> 0 (N o-Media) D/Vold ( 266): Volume usbdisk_1.0 state changing -1 (Initializing) -> 0 (No- Media) D/Vold ( 266): Volume usbdisk_1.1 state changing -1 (Initializing) -> 0 (No- Media) D/Vold ( 266): Volume usbdisk_1.2 state changing -1 (Initializing) -> 0 (No- Media) D/Vold ( 266): Volume usbdisk_1.3 state changing -1 (Initializing) -> 0 (No- Media) D/Vold ( 266): Volume usbdisk_1.4 state changing -1 (Initializing) -> 0 (No- Media) D/Vold ( 266): Volume usbdisk_1.5 state changing -1 (Initializing) -> 0 (No- Media) D/Vold ( 266): Volume usbdisk_1.6 state changing -1 (Initializing) -> 0 (No- Media) D/Vold ( 266): Volume usbdisk_1.7 state changing -1 (Initializing) -> 0 (No- Media) I/cm ( 367): ____ _ _ ____ _ _ ____ ____ ____ _ _ _ _ ____ ___ I/Netd ( 272): Netd 1.0 starting W/InterfaceController( 272): Warning (Cannot load library: load_library(linker. cpp:771): library "/system/lib/libnetcmdiface.so" not found) while opening the n et interface command library I/rmt_storage( 338): Target is APQ8064: 1074105669 D/BHD ( 285): NVM Read - Read header, version = 1, file write count = 190, time = Sun Apr 21 03:18:08 2013 D/BHD ( 285): NVM Read - Opened NVM file /pds/batt_health/batt-898bc7a41c00 50b7_1 D/BHD ( 285): NVM Read - Read header, version = 1, file write count = 189, time = Sat Apr 20 06:34:09 2013 D/BHD ( 285): NVM Load - Found newest file, index to use = 0 D/BHD ( 285): State - EEPROM id = 898bc7a41c0050b7; capacity = 1750 D/BHD ( 285): State - BMS real fcc batt temp = 282, real fcc = 1700 D/BHD ( 285): State - BMS SOC = 100%, OCV = 3682000, rbatt = 241 D/BHD ( 285): State - BMS charge inc = 66, charge cycles = 121 D/BHD ( 285): State - is factory mode = 0 D/BHD ( 285): State - is charging = 0 D/BHD ( 285): State - aged capacity % = 98 D/BHD ( 285): State - aged capacity calculated @ Fri Apr 5 00:04:14 2013 D/BHD ( 285): State - Begin charge % = 0, cc = 972508, ocv = 4011000 D/BHD ( 285): State - End charge % = 100, cc = -468380, ocv = 4011000 I/cm ( 369): | \_/ |__| |\ | | | | __ |___ |\ | |\/| | | | \ D/BHD ( 285): Created socket 7 for uevents D/PPDaemon( 334): isHDMIPrimary: HDMI is not primary display D/PPDaemon( 334): CABL version 1.0.20120512 E/ThermalDaemon( 284): Thermal daemon started D/QC-time-services( 339): Daemon:genoff_pre_init::Base = 0 D/QC-time-services( 339): Daemon:ats_rtc_init: Time read from RTC -- year = 113 , month = 3,day = 3 D/Vold ( 266): Volume sdcard state changing 0 (No-Media) -> 2 (Pending) D/DirectVolume( 266): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 97 , PARTN 1 E/QC-time-services( 339): Daemon:genoff_boot_tod_init: Unable to set TOD at boo t up E/QC-time-services( 339): Daemon: Unable to set TOD at boot up D/QC-time-services( 339): Daemon:genoff_modem_qmi_init: Initiallizing QMI I/cm ( 385): Welcome to Android 4.2.2 / CyanogenMod- I/Atfwd_Daemon( 333): ATFWD --> QMI Port : rmnet1 I/start ( 400): A wise man never plays leapfrog with a unicorn W/libc ( 336): WARNING: generic atexit() called from legacy shared library I/Sensors ( 376): sns_init_la.c(292):initializing sns_memmgr_init I/Sensors ( 376): sns_init_la.c(303):Waiting for sns_memmgr_init... I/Sensors ( 376): sns_init_la.c(307):Done waiting for sns_memmgr_init I/Sensors ( 376): sns_init_la.c(292):initializing sns_debug_test_init1 I/Sensors ( 376): sns_init_la.c(303):Waiting for sns_debug_test_init1... I/Sensors ( 376): sns_init_la.c(307):Done waiting for sns_debug_test_init1 I/Sensors ( 376): sns_init_la.c(292):initializing sns_pwr_init I/sensorsqcomwrapper.sh( 374): Use option "-d" to run as background process. I/sensorsqcomwrapper.sh( 374): Running in foreground... I/run-parts( 342): sysctl: /etc/sysctl.conf: No such file or directory I/SurfaceFlinger( 275): SurfaceFlinger is starting I/SurfaceFlinger( 275): SurfaceFlinger's main thread ready to run. Initializing graphics H/W... I/Sensors ( 376): sns_init_la.c(303):Waiting for sns_pwr_init... I/Sensors ( 376): sns_init_la.c(307):Done waiting for sns_pwr_init I/Sensors ( 376): sns_init_la.c(292):initializing sns_em_init I/Sensors ( 376): sns_init_la.c(303):Waiting for sns_em_init... D/libEGL ( 275): loaded /system/lib/egl/libEGL_adreno200.so I/Sensors ( 376): sns_init_la.c(307):Done waiting for sns_em_init I/Sensors ( 376): sns_init_la.c(292):initializing sns_smr_init I/Sensors ( 376): sns_init_la.c(303):Waiting for sns_smr_init... W/Sensors ( 376): sns_smr_la.c(415):smr_la: smr_apps_la_thread_main is starting , fd=15, sns_smr.en_rx_msg_ptr=400c87e8 I/Sensors ( 376): sns_init_la.c(307):Done waiting for sns_smr_init I/Sensors ( 376): sns_init_la.c(292):initializing sns_reg_init I/Sensors ( 376): sns_init_la.c(303):Waiting for sns_reg_init... D/BHD ( 285): Got a battery uevent,log details D/BHD ( 285): Battery start charging @ 88%! D/libEGL ( 275): loaded /system/lib/egl/libGLESv1_CM_adreno200.so D/libEGL ( 275): loaded /system/lib/egl/libGLESv2_adreno200.so I/Sensors ( 376): sns_init_la.c(307):Done waiting for sns_reg_init I/Sensors ( 376): sns_init_la.c(292):initializing sns_sam_init I/Sensors ( 376): sns_init_la.c(303):Waiting for sns_sam_init... I/Adreno200-EGL( 275): <eglInitialize:269>: EGL 1.4 QUALCOMM build: Nondetermin istic AU_full_mako_PARTNER-ANDROID/JB-MR1-DEV_CL2946718_release_AU (CL2946718) I/Adreno200-EGL( 275): Build Date: 11/04/12 Sun I/Adreno200-EGL( 275): Local Branch: I/Adreno200-EGL( 275): Remote Branch: m/partner-android/jb-mr1-dev I/Adreno200-EGL( 275): Local Patches: NONE I/Adreno200-EGL( 275): Reconstruct Branch: NOTHING I/gralloc ( 275): using (fd=21) I/gralloc ( 275): id = msmfb42_90701 I/gralloc ( 275): xres = 720 px I/gralloc ( 275): yres = 1280 px I/gralloc ( 275): xres_virtual = 720 px I/gralloc ( 275): yres_virtual = 3840 px I/gralloc ( 275): bpp = 32 I/gralloc ( 275): r = 24:8 I/gralloc ( 275): g = 16:8 I/gralloc ( 275): b = 8:8 I/gralloc ( 275): width = 56 mm (326.571442 dpi) I/gralloc ( 275): height = 99 mm (328.404053 dpi) I/gralloc ( 275): refresh rate = 60.00 Hz D/CALCFPS ( 275): DEBUG_CALC_FPS: 0 D/CALCFPS ( 275): period: 10 D/CALCFPS ( 275): ignorethresh_us: 500000 D/CALCFPS ( 275): DEBUG_CALC_FPS: 0 D/CALCFPS ( 275): period: 10 D/CALCFPS ( 275): ignorethresh_us: 500000 D/overlay ( 275): initoverlay:: opening the device:: /dev/graphics/fb0 D/overlay ( 275): initoverlay:: opening the device:: /dev/graphics/fb1 D/overlay ( 275): ndx=6 num=5 z_order=-1 D/AndroidRuntime( 276): D/AndroidRuntime( 276): >>>>>> AndroidRuntime START com.android.internal.os.Zyg oteInit <<<<<< D/AndroidRuntime( 276): CheckJNI is OFF D/overlay ( 275): initoverlay:: opening the device:: /dev/graphics/fb2 I/mediaserver( 278): ServiceManager: 0x414a7ed8 I/AudioFlinger( 278): Using default 3000 mSec as standby time. I/CameraService( 278): CameraService started (pid=278) ^C C:\Users\John\Android\sdk\platform-tools>adb logcat e --------- beginning of /dev/log/system I/Vold ( 266): Vold 2.1 (the revenge) firing up D/Vold ( 266): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media ) D/Vold ( 266): Volume usbdisk_1.1.1 state changing -1 (Initializing) -> 0 (N o-Media) D/Vold ( 266): Volume usbdisk_1.0 state changing -1 (Initializing) -> 0 (No- Media) D/Vold ( 266): Volume usbdisk_1.1 state changing -1 (Initializing) -> 0 (No- Media) D/Vold ( 266): Volume usbdisk_1.2 state changing -1 (Initializing) -> 0 (No- Media) D/Vold ( 266): Volume usbdisk_1.3 state changing -1 (Initializing) -> 0 (No- Media) D/Vold ( 266): Volume usbdisk_1.4 state changing -1 (Initializing) -> 0 (No- Media) D/Vold ( 266): Volume usbdisk_1.5 state changing -1 (Initializing) -> 0 (No- Media) D/Vold ( 266): Volume usbdisk_1.6 state changing -1 (Initializing) -> 0 (No- Media) D/Vold ( 266): Volume usbdisk_1.7 state changing -1 (Initializing) -> 0 (No- Media) D/Vold ( 266): Volume sdcard state changing 0 (No-Media) -> 2 (Pending) D/DirectVolume( 266): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 97 , PARTN 1 Can anyone help me?
Really, no one? Sent from my MB886 using xda app-developers app
Codex01 said: Really, no one? Sent from my MB886 using xda app-developers app Click to expand... Click to collapse Some people (like me) don't even know what to do with that so just be patient friend. Sent from my MB886 using xda app-developers app
worlddominatiin said: Some people (like me) don't even know what to do with that so just be patient friend. Sent from my MB886 using xda app-developers app Click to expand... Click to collapse Yeah, I pretty much know whats going on, I may have the wrong lib_runtime and android policy, also may be a faulty kernel. From the log you can tell it finalises boot, it has all the scripts but there are a few errors, that I know cant be errors.
system/lib/libnetcmdiface.so - look like that lib isn't there camera drivers might be wrong - use the CM10.1 drivers and looks like some of the /etc scripts aren't working properly and some .conf files aren't present. I'd have to flash the rom and have a physical copy to mess with to tell you more.
skeevydude said: system/lib/libnetcmdiface.so - look like that lib isn't there camera drivers might be wrong - use the CM10.1 drivers and looks like some of the /etc scripts aren't working properly and some .conf files aren't present. I'd have to flash the rom and have a physical copy to mess with to tell you more. Click to expand... Click to collapse I will upload this on the new site asap.
Any word on ur progress my friend? Sent from my MB886 using xda premium
sickkside13 said: Any word on ur progress my friend? Sent from my MB886 using xda premium Click to expand... Click to collapse @sickkside13, @skeevydude and I are working on this port, hes helping me alot. He says (I deleted the email, so don't quote me.) that we will have a build from source probably by tomorrow or the day after.
Nice Sent from my MB886 using xda premium
I still gotta tweak our device\vendor repo (if its anything like PA, which it seems to be, should only be a few lines). Hard part will be making a vendor/rootbox repo for us -- just gonna base it on a Nexus and start playing the follow the makefile game . Due to the way our CM10.1 repo is set up -- our only custom repos are for kernel, device, and device vendor -- the very minimal necessary -- roms like this & PACMAN shouldn't be that hard to make for us from source. Atrix HD and GSM Razr HD anyways...don't know much about CDMA roms. Depending on time, I should have the necessary changes and additions done today. I gotta go with the bossman on a bid and to pick up some materials today --- not sure how long that'll take. Gotta go 20 miles one way from town for the bid, 40 miles the other way for materials (60 miles from the bid).
Waiting for this, looks good Sent from my MB886 using xda app-developers app
Just finished everything and starting the first compile. Been going for 10 minutes now. Hopefully it'll finish. :fingers-crossed: If it goes well, sources should be on github this evening and my tweaked vendor and device repo should just work with the PacMan sources. PacMan should just need some qinara vendor/pacman config and make files. Root and Pac both use a modified PA style build system, I've done a bit of PA in the past so, and luckily, doing these tweaks\making the necessary vendor make files is nothing new to me. Plan is to do Unofficial Atrix HD RootBox. If this works, then I'll do the same for Razr HD. Once all that's done I'll move on to PacMan. I'm also going to add, before all you guys start giving me the same BS you've been giving Codex, that all I'm doing is taking the razr-qcom dev team repos and making them compatible with other projects. All the actual development will either be via the dev team's CM10.1 kernel or whatever project's dev team. That's not saying that I won't add in any fixes or whatever myself, just that most of what I'm doing is combining other peoples hard work for our benefit. //20 minutes compiling and goind strong
skeevydude said: Plan is to do Unofficial Atrix HD RootBox. If this works, then I'll do the same for Razr HD. Once all that's done I'll move on to PacMan. Click to expand... Click to collapse Thanks for the Razr HD love!
Didn't compile, had some errors with tcpdump, removing it and trying again. Sources available on git-hub Code: repo init -u [url]https://github.com/skeevy420/platform_manifest.git[/url] -b razrqcom-rootbox repo sync . build_rootbox.sh qinara [B][COLOR="Blue"]X[/COLOR][/B] clean [B][COLOR="Blue"]X[/COLOR][/B] is the number of threads to use, use either number of cores or number of cores +1 -- whichever you find works best. //Why all of a sudden does XDA decide to email me when I post a code box in my own post? You'd think I'd be aware of that one
Once you get a build I'd be more than happy to beta, PM me if you need anything. I was a beta tester for eight months for two devs on the Galaxy Player 5.0 so I have a lot of experience... Sent from my MB886 using xda app-developers app
EcHoFiiVe said: Once you get a build I'd be more than happy to beta, PM me if you need anything. I was a beta tester for eight months for two devs on the Galaxy Player 5.0 so I have a lot of experience... Sent from my MB886 using xda app-developers app Click to expand... Click to collapse Let ya know when I know Was having some defconfig issues with the kernel. Resolved them and starting over. It was crappin out around 35 minutes, so once 10:00 central hits I'll be farther along in the process anyways Day one fun
skeevydude said: Let ya know when I know Was having some defconfig issues with the kernel. Resolved them and starting over. It was crappin out around 35 minutes, so once 10:00 central hits I'll be farther along in the process anyways Day one fun Click to expand... Click to collapse How long do you think it'll take to build? Four, seven hours? Sent from my MB886 using xda app-developers app
EcHoFiiVe said: How long do you think it'll take to build? Four, seven hours? Sent from my MB886 using xda app-developers app Click to expand... Click to collapse From start to finish? Defy CM10.1 takes an hour an a half, so this should be between an hour an a half to two hours...providing it finishes.
i have a nexus 4 and i just flashed rootbox its kinda buggy but there is another build. Il try it out in a bit Sent from my MB886 using xda premium
sickkside13 said: i have a nexus 4 and i just flashed rootbox its kinda buggy but there is another build. Il try it out in a bit Sent from my MB886 using xda premium Click to expand... Click to collapse Even if it is buggy I'd at least like to get it set up and compiling so that when its not buggy all the leg work is already done.