Related
Hi there!!!
I noticed that there lot's of user's complaining about error in selecting network. So, here i present you the ril files pulled from old an nightly which had a working netwok selection.
This is probably not for FUNNY SIM'S!!!
Patch
http://db.tt/ZOoEGNB5
Undo-Patch
http://db.tt/hWJmfHTY
BEFORE FLASHING, ADD THIS LINE TO YOUR BUILD.PROP..
rild.libpath=/system/lib/libril-qc-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM <-----
ro.telephony.ril_class=lgeqcom <-----
Sent from my LG-P500 using xda premium
Please don't complain about the same files having the same md5. My brain won't let me remove it..
Sent from my LG-P500 using xda premium
Thank U
peter joe said:
Thank U
Click to expand...
Click to collapse
Did it work for you pls put a detail which country and sim..
Edit: and there is always a THANKS BUTTON to begin with..
Sent from my LG-P500 using xda premium
> great buddy this is really helpful +1
neko95 said:
> great buddy this is really helpful +1
Click to expand...
Click to collapse
does it work for you neko?
> This work.. but not all people knows how to set/reconfigure build.prop to add those lines.. I suggest you make an updater script which includes the build.prop lines.. but not to over wright the existing build.prop, it should only add those few lines..
neko95 said:
> This work.. but not all people knows how to set/reconfigure build.prop to add those lines.. I suggest you make an updater script which includes the build.prop lines.. but not to over wright the existing build.prop, it should only add those few lines..
Click to expand...
Click to collapse
Or upload thier build.prop here???? Maybe
Sent from my LG-P500 using xda premium
dnle71 said:
Or upload thier build.prop here???? Maybe
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
> no .. I mean people who had build.prop tweaks like from zeppelinrox 3g boost or v6.. this will break those. if it would be over write with a whole build.prop.. So what needed is a script that only updates build.prop let me try to make you one..
neko95 said:
> no .. I mean people who had build.prop tweaks like from zeppelinrox 3g boost or v6.. this will break those. if it would be over write with a whole build.prop.. So what needed is a script that only updates build.prop let me try to make you one..
Click to expand...
Click to collapse
you mean this?
#!system/bin/sh
setprop ril.subscription.types=NV,RUIM;
setprop ro.telephony.ril_class=lgeqcom;
Sent from my LG-P500 using xda premium
dnle71 said:
you mean this?
#!system/bin/sh
setprop ril.subscription.types NV,RUIM;
setprop ro.telephony.ril_class lgeqcom;
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
> you need init.d just to execute a script to build.prop? coz no use updater script to add this to build.prop
I really want to try it baddly but I have an old baseband with "old baseband" fix and it appears that both fixes/patches overwrite at least one file. I will have to reflash the rom and flash new baseband to try it when I'll find some free time.
Thanks for the fix
-Arturo- said:
I really want to try it baddly but I have an old baseband with "old baseband" fix and it appears that both fixes/patches overwrite at least one file. I will have to reflash the rom and flash new baseband to try it when I'll find some free time.
Thanks for the fix
Click to expand...
Click to collapse
Time to upgrade!!..
Sent from my LG-P500 using xda premium
dnle71 said:
Time to upgrade!!..
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Ok I tried the network selection fix..
After trying to search for networks my phone rebooted.
I'm on Polish "Play" network.
I don't know whether I have a funny sim or not.
My phone bootloops....
Actually I have made similar patch (but without undo patch!).
My contains less files and was meant for mentioning in CM issue 5182 Manual network operator selection fails (those who suffer from this problem, please vote for it!). Warning: My patch doesn't have undo patch and it overwrites build.prop, it is made for CM 7.2 RC3 and is purely experimental.
It was created after asking mik_os why manual network selection works in his unofficial CM port, but doesn't work in official CM 7.2 RCs. Here is mik_os answer:
mik_os said:
DavisNT said:
mik_os said:
DavisNT said:
Hi!
How did you manage to get manual network operator selection working on your Cyanogenmod ports for LG P500?
Can you give me a link to source code and/or a comment for Cyanogenmod official port developers?
Issue on CyanogenMod bugtracker is here: https://code.google.com/p/cyanogenmod/issues/detail?id=5182
Thanks a lot!
Click to expand...
Click to collapse
It's easy. CM has temporary switched to old RIL:
https://github.com/CyanogenMod/andr...mmit/49e0b810423dcf94f458e7cf3c2bb90900a7be9e
The old RIL does not properly supports Network Selection in our device. And CM will not fix this because this is temporary.
Click to expand...
Click to collapse
Can I switch my phone back to new RIL by adding back these lines to /system/build.prop (or other changes are also required)?
Code:
ril.subscription.types=NV,RUIM
ro.telephony.ril_class=lgeqcom
Click to expand...
Click to collapse
You also need change this libraries:
https://github.com/koush/proprietary_vendor_lge/commit/65568a688c73962049b2f28de6d108cf05f90772#p500
Click to expand...
Click to collapse
Also I have a question to everybody, especially mik_os and official CM devs. In my patch all files that were updated during library revert mentioned by mik_os are replaced by versions before revert, /system/lib/libdll.so is deleted, but /system/bin/rild is left, because if I delete it, radio doesn't work at all. Also every file, except /system/bin/rild in CM 7.2 RC3 flashable zip is the same as in library revert checkin mentioned my mik_os, but rild is different. Why so - what other changes in rild have been made?
Update: mik_os gave me this link to changes which fixed Manual Network Operator selection with old RIL (Froyo RIL that is contained within mik_os and official CM 7.2 builds): https://github.com/mik9/android_frameworks_base/compare/88b5c4b8eb...2ae66fc39b
Thanks mik_os!
Warning: Patch is only for official CM 7.2 RC3!
I love you! Really thanks what about cm9 it works also there?
Sent from my LG-P500 using XDA
DavisNT said:
Actually I have made similar patch (but without undo patch!).
My contains less files and was meant for mentioning in CM issue 5182 Manual network operator selection fails (those who suffer from this problem, please vote for it!). Warning: My patch doesn't have undo patch and it overwrites build.prop, it is made for CM 7.2 RC3 and is purely experimental.
It was created after asking mik_os why manual network selection works in his unofficial CM port, but doesn't work in official CM 7.2 RCs. Here is mik_os answer:
Also I have a question to everybody, especially mik_os and official CM devs. In my patch all files that were updated during library revert mentioned by mik_os are replaced by versions before revert, /system/lib/libdll.so is deleted, but /system/bin/rild is left, because if I delete it, radio doesn't work at all. Also every file, except /system/bin/rild in CM 7.2 RC3 flashable zip is the same as in library revert checkin mentioned my mik_os, but rild is different. Why so - what other changes in rild have been made?
Click to expand...
Click to collapse
yes that was the basis of my patch too.. but i did not review all files that is not needed to be replace but my brain don't want to....
DavisNT said:
Actually I have made similar patch (but without undo patch!).
My contains less files and was meant for mentioning in CM issue 5182 Manual network operator selection fails (those who suffer from this problem, please vote for it!). Warning: My patch doesn't have undo patch and it overwrites build.prop, it is made for CM 7.2 RC3 and is purely experimental.
It was created after asking mik_os why manual network selection works in his unofficial CM port, but doesn't work in official CM 7.2 RCs. Here is mik_os answer:
Also I have a question to everybody, especially mik_os and official CM devs. In my patch all files that were updated during library revert mentioned by mik_os are replaced by versions before revert, /system/lib/libdll.so is deleted, but /system/bin/rild is left, because if I delete it, radio doesn't work at all. Also every file, except /system/bin/rild in CM 7.2 RC3 flashable zip is the same as in library revert checkin mentioned my mik_os, but rild is different. Why so - what other changes in rild have been made?
Click to expand...
Click to collapse
Well i'll be damned it works ...thank you
It works also for me
@DavisNT
I have tried your patch on my LGP500 with (CM 7.2 nightly 20120617 + patch NeuDLI http://forum.xda-developers.com/showpost.php?p=27616022&postcount=3314) installed.
It seems to work well, the only drawback is to get a misidentification of my "actual" ROM labelled "CM7.2RC3 and 20120526".
Manual selection works well ... Calls and 3G data also. :fingers-crossed:
Thanks a lot for your work!
If these two patches could be integrated by Adam (adfad666) in the official CM 7.2 next nigthly, it would be a huge progress in the LG-P500 version of CM 7.2.
I took the liberty to slightly improve the RIL fix:
In the improved flashable zip the build.prop is not overwritten, but instead the init script of dnle71 is added. In this manner the build.prop is not touched thus preserving any tweaks made therein and also the CM version etc.
(Until someone can tell me how to use apply_patch in the updater-script to patch the build.prop I believe this is the cleanest way)
Furthermore I also added the "old" rild executable so that all RIL files are from the same stage, although apparently this was not absolutely necessary.
Thanks very much dnle71 and DavisNT for your work that I only combined!
Just the usual word of caution: I did test this on my P500 and it worked. For everyone else, however: Use at your own risk!
[HOWTO] Increase available RAM in ROMs based on "That kernel" and "Those libs"
Most Atrix users using ROMs with "That kernel" and "Those libs" are stuck with 778MB or 784MB of available RAM (even after applying the ramfix for international Atrix users), but a few users are reporting getting around 855MB of RAM available on their phones. After a quick comparison of the /proc/cmdline on these phones (and since having more RAM can't hurt), here's a guide how to increase your available RAM on these ROMs. This guide is intended for people who have 778-784MB available on their phone when using ROMs based on "That kernel" and "Those libs" with the original ramfix. DO NOT USE ON OTHER ROMS!
WARNING: STOP NOW AND DO NOT FLASH IF YOU DON'T KNOW WHAT YOU'RE DOING!!!
PLEASE READ AND UNDERSTAND EVERYTHING BEFORE YOU DO ANYTHING!
I have personally tested this with Somebody's CM10 and AtrICS v2.
It should theoretically work with other ROMs based on "That kernel" and "Those libs", but use it at your own risk!
Now, on to the good part:
1. Get your current /proc/cmdline.
You can do this by using terminal emulator and typing:
su
cat /proc/cmdline
Click to expand...
Click to collapse
or by using a root browser and copy your /proc/cmdline to your sdcard.
A note from NFHimself:
NFHimself said:
Hi,
Please emphasize that the script needs YOUR complete /proc.cmdline in there, from a working phone adb session, not recovery adb session as the recovery has it's own possible /proc/cmdline via a different kernel, etc. You are not just editing the mem=?? stuff.
What would be best is to first create a zip that is plain jane what your /proc/cmdline is or one that uses setcmdline with a blank argument or "". That way you can reset to default in case of errors. Or you can just fastboot flash your boot partition, no need for an sbf.
Cheers!
Click to expand...
Click to collapse
2. Download attached file.
3. Edit the updater-script file in the zip.
Extract the zip and find META-INF\com\google\android\updater-script
Windows users: Edit the file using Notepad. DO NOT USE WORDPAD. WordPad changes the Unix-style CR to Windows style CR-LF, which may cause problems.
Once you open the file, find this in the file:
run_program("/tmp/setcmdline", "[email protected] [email protected] [email protected] vmalloc=256M video=tegrafb console=null usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=mbr:d00:100:800,kpanic:2100:400:800 security=tomoyo mot_prod=1 androidboot.serialno=XXXXX00000");
Click to expand...
Click to collapse
Change the red part with your own cmdline, which you got in step 1. Take care especially on the tegrapart and androidboot.serialno parameters. DO NOT USE A TEGRAPART AND/OR SERIAL NUMBER FROM ANOTHER PHONE!
If your original cmdline that you got in step one was:
[email protected] [email protected] [email protected] vmalloc=320M video=tegrafb console=null usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=mbr:1100:100:800,kpanic:2500:400:800 security=tomoyo mot_prod=1 androidboot.serialno=12345ABCDE
Click to expand...
Click to collapse
then you should modify the part of the updater-script mentioned above to look like this:
run_program("/tmp/setcmdline", "[email protected] [email protected] [email protected] vmalloc=256M video=tegrafb console=null usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=mbr:1100:100:800,kpanic:2500:400:800 security=tomoyo mot_prod=1 androidboot.serialno=12345ABCDE"
Click to expand...
Click to collapse
Only the change the red part in the script with the red part in your original cmdline. DO NOT MODIFY ANYTHING ELSE!
4. Save the file, and repack the zip.
5. Flash zip.
6. You should now have 855MB of RAM available. Enjoy your extra 70+MB of RAM.
WARNING: DO NOT FLASH IF YOU DON'T KNOW WHAT YOU'RE DOING!!!
I AM NOT RESPONSIBLE FOR ANYTHING THAT GOES WRONG BECAUSE OF YOU BORKING YOUR CMDLINE!!!
Thanks to: NFHimself for creating the ramfix binary and Ilkinansr92 for his cmdline.
Thanks!!! I will givi it a try.
Edit: Working just fine....thanks again!
from the (m)ATRIX...
Thanks!
Now i have 855mb of RAM available
I have 815mb of ram available and i am using Nottachtrix Rom, i am going to try this method in 2 mins and i will give feedback..
Edit:
it gives me error which number 6 (my rom is working, no problem). i know nottachtirx is not based on that kernel but i had wanted to try it whether work or not.
ramanujan20 said:
I have 815mb of ram available and i am using Nottachtrix Rom, i am going to try this method in 2 mins and i will give feedback..
Edit:
it gives me error which number 6 (my rom is working, no problem). i know nottachtirx is not based on that kernel but i had wanted to try it whether work or not.
Click to expand...
Click to collapse
I got that error too....on JB...but that was because I was doing something wrong.
But I think this is for JB...
Cocolopes said:
I got that error too....on JB...but that was because I was doing something wrong.
But I think this is for JB...
Click to expand...
Click to collapse
are you using something related to "that rom"? (kernel, libs, rom)
jhonnyx said:
are you using something related to "that rom"? (kernel, libs, rom)
Click to expand...
Click to collapse
No...someones Cm10 here...but now is working...I just replace the update script in the zip...and work perfect
from the (m)ATRIX...
successful
oh yeah~
now i have 855mb ram now!
i found that you can copy the file /proc/cmdline to computer,and select the words you need
in this way,you can do it more simple and more safe!
Well. 855 MB RAM. I am using CM10 with that libs.
Thank a lot.
Cocolopes said:
No...someones Cm10 here...but now is working...I just replace the update script in the zip...and work perfect
from the (m)ATRIX...
Click to expand...
Click to collapse
Well, "Somebody's" CM10 IS using the kernel & libs from "That ROM", so I'd say it's very much related.
Can anybody help me i don't even have 500 mb in manage apps - running apps section
International user and using MRom
Sent from Otterbox Atrix 4G Rockz
ranjithkumar1201 said:
Can anybody help me i don't even have 500 mb in manage apps - running apps section
International user and using MRom
Sent from Otterbox Atrix 4G Rockz
Click to expand...
Click to collapse
Have you applied the ramfix? If not download this and apply it and it will fix that problem:
http://forum.xda-developers.com/attachment.php?attachmentid=710806&d=1315237274
Perfect. Thanks !
I hope the OP doesn't mind...
Here's my take on this. I took the source of the cmdline utility and improved it greatly, now it's almost a full-featured kernel cmdline editor. Then I used this new utility in the update script to dynamically edit the system cmdline.
Bottom line: this ZIP should work on all systems without any modifications.
WARNING: not fully tested, use at your own risk!
(If anything goes wrong, it should be easily revertable simply by reflashing the kernel, either from recovery or via fastboot.)
EDIT: added a couple more options, recompiled the cmdline binary and repackaged the ZIP.
ravilov said:
I hope the OP doesn't mind...
Here's my take on this. I took the source of the cmdline utility and improved it greatly, now it's almost a full-featured kernel cmdline editor. Then I used this new utility in the update script to dynamically edit the system cmdline.
Bottom line: this ZIP should work on all systems without any modifications.
WARNING: not fully tested, use at your own risk!
(If anything goes wrong, it should be easily revertable simply by reflashing the kernel, either from recovery or via fastboot.)
EDIT: added a couple more options, recompiled the cmdline binary and repackaged the ZIP.
Click to expand...
Click to collapse
Works beautifully on someone's cm10! Big thanks.
Sent from my MB860
ravilov said:
I hope the OP doesn't mind...
Here's my take on this. I took the source of the cmdline utility and improved it greatly, now it's almost a full-featured kernel cmdline editor. Then I used this new utility in the update script to dynamically edit the system cmdline.
Bottom line: this ZIP should work on all systems without any modifications.
WARNING: not fully tested, use at your own risk!
(If anything goes wrong, it should be easily revertable simply by reflashing the kernel, either from recovery or via fastboot.)
EDIT: added a couple more options, recompiled the cmdline binary and repackaged the ZIP.
Click to expand...
Click to collapse
sorry for ask but i don't get it this is a script to modify the cmdline or is an auto modify tool for the cmdline?
Maibol said:
sorry for ask but i don't get it this is a script to modify the cmdline or is an auto modify tool for the cmdline?
Click to expand...
Click to collapse
Both actually.
It includes a tool that can modify the cmdline, and a script that does modify the cmdline automatically, by utilizing the tool.
ravilov said:
Both actually.
It includes a tool that can modify the cmdline, and a script that does modify the cmdline automatically, by utilizing the tool.
Click to expand...
Click to collapse
thanks nice tool i gon give it a try
Why so some Atrixes have 815 MB RAM and some others 879 MB ?
And ravilov, does your script work on gingerbread ROMs, too?
Sent from my CM7 powered Atrix using TapaTalk \o/
the.cybot said:
And ravilov, does your script work on gingerbread ROMs, too?
Click to expand...
Click to collapse
Actually, I'm not sure. It doesn't seem to work for me. The boot image gets updated correctly but for some reason the new cmdline is not used when the kernel boots. I'm using MROM, latest release. Maybe it works different on another ROM. Maybe this whole cmdline business is specific to stock kernels only. Needs more research.
OpenPDroid is an awesome mod developed and maintained by CollegeDev, FFU5y, Mateor, Pastime1971, Syvat and Wbedard that allows you to configure for each app separately exactly which permissions it should have and block or spoof everything else. Unfortunately, it can only be used if the core platform is integrated directly into the ROM. (For more details, see http://forum.xda-developers.com/showthread.php?t=2098156)
Since I have completed the integration anyway during my attempts to fix the HDMI rotation bug (without success so far, I'm afraid) and the current version of CM does not seem to contain any more critical bugs, I thought others might like to make use of my ROM as well.
I therefore hereby present: CM 10.1 with OpenPDroid integration. Besides the platform integration I made the following changes:
PDroid Manager app integration.
Standard CM Updates are disabled by default.
CM anonymous stats collection is disabled by default.
Google Analytics integration has been removed from the CM stats collection module.
Updates and anonymous stats collection can simply be enabled again using the menu. (Warning! Applying a normal CM update purges the OpenPDroid integration!)
I will try to at least provide updates to newer versions at critical update moments and will perhaps provide some more in between.
You'll need to have ClockworkMOD installed in order to flash this ROM.
Downloads:
11/07/13: Version based on CM 10.1.1 stable. Steps:
1. Flash the stable version of CM 10.1.1 (10/07/13) for our device.
2. Flash this OpenPDroid patch.
3. Install PDroid Manager either from the Play Store or using the APK attached to this post.
10/07/13: (based on source code 09/07)
10/07/13: https://mega.co.nz/#!uswGGQ6K!Wt9JAFDBElZQ2i74yNxMrkz3y7kO4U8-LWK2dLx_L8s
10/07/13: MD5: 99fc3769c9b2354a844ac1ac92504650
16/05/13: (build with standard CM kernel)
16/05/13: https://mega.co.nz/#!StIyQbzD!GfgNa3Seha74UnSahokwIzvcZ9UVqKaa2P38_LlxuMY
16/05/13: MD5: ad036e4035291bba901ad90826ab0abf
13/05/13: (general source code cleanup)
13/05/13: https://mega.co.nz/#!KoxixajK!Wn91VGj5ooOFYXs-Vt8QJDkU8Bo7VuR40_939hd3YMg
13/05/13: MD5: dffad528804bf830c4b225b0bfff5a76
09/05/13: (WerewolfJB kernel v003 new)
09/05/13: https://mega.co.nz/#!2txwmS4S!aR4bHG6BHMkoTPabi8Z0K0r4hPsUICmKO9ROaaIYOg0
09/05/13: MD5: 4a75829296a167a563ad78ffe26991de
05/05/13: (vibration,memory management)
05/05/13: https://mega.co.nz/#!bsQERDaS!RHB4rHhQsDf9XauyOpeMySAiDt1gtc8Y7gnsckdWOlo
05/05/13: MD5: e05017acf9e50affcba7379050514d63
01/05/13: (merged in the WerewolfJB kernel, fixed headphone button actions)
01/05/13: https://mega.co.nz/#!ig5hCJYY!eHM5vwER9zEEZJRk9_C6vCvclH14rDcKa9CyBcU9kTc
01/05/13: MD5: 3ababb1c0cda47874ed7d688de032638
28/04/13 (adjusted some device references for improved custom recovery compatibility)
28/04/13: https://mega.co.nz/#!71BgVLBY!PEcEHAYxpDZVZcQycpgGJ2QeJZZ0HbgVdjaBkiD72bg
28/04/13: MD5: 7f2616736dd78940e37d1e14ea47084f
24/04/13: (storage, power profiles)
24/04/13: https://mega.co.nz/#!j44XWBDb!UrmGEhCUcjbj8Q3WTj1EkDrImXJXwcNGvEMIHFm-TvE
24/04/13: MD5: 491a500c5bef958d7575a6ce62fae1aa
23/04/13: https://mega.co.nz/#!75IDhCAA!EpwDqHm6W6fG3mk0lNaC0XPWvlsJxi2TjEpjJPEuj6Q
23/04/13: MD5: 609c76958796f19fb04aee217c44ba98
PS. If anyone ever discovers the correct procedure for calling the proprietary nvidia tegra driver api, please let me know.
is the baseband wakelock solved in this rom?
Who can change the other network disk ，thx
xtribas said:
is the baseband wakelock solved in this rom?
Click to expand...
Click to collapse
The main additional problem that this ROM currently fixes compared to standard CM is that of blatant privacy violation.
Since the wakelock issue seems to be related to mobile data use, and I don't have a data subscription, experimentation with this would quickly rack up my phone bill. If someone comes up with a solution I'd be happy to patch it out though.
Hansey said:
Who can change the other network disk ，thx
Click to expand...
Click to collapse
I assume you're referring here to the swapping of disk names when using MTP. I actually only noticed this bug last night and it should be easy to fix. I plan to have it patched out in the next version.
Update 24/04/13 uploaded, involving official CM patches for MTP storage & power profile settings.
Is there a guide how to compile it my self?
DavidXanatos said:
Is there a guide how to compile it my self?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1994860
DavidXanatos said:
Is there a guide how to compile it my self?
Click to expand...
Click to collapse
At the Cyanogenmod website there are instructions for compiling yourself. You can apply the OpenDroid patches using the link I included in the post. Make sure to synchronize the proprietary files with those provided by Cyanogenmod or some aspects will fail to work.
@Wenque - As the original CM on which you based this has the incorrectly labelled hardware platform which means it can only be flashed with the one particular version of CWM, could you possibly modify your version so the coding is for X3, not for P880 - then it could be flashed with any recovery.
SimonTS said:
@Wenque - As the original CM on which you based this has the incorrectly labelled hardware platform which means it can only be flashed with the one particular version of CWM, could you possibly modify your version so the coding is for X3, not for P880 - then it could be flashed with any recovery.
Click to expand...
Click to collapse
Thanks for pointing this out, as I wasn't aware that my ROMs still suffered from this problem. I'll look into it.
Wenque said:
Thanks for pointing this out, as I wasn't aware that my ROMs still suffered from this problem. I'll look into it.
Click to expand...
Click to collapse
No problem. I got the 'Status 7' message when I tried to flash it, due to the P880.
This problem goes away with the latest (v6.0.3.1) version of CWM, so it's not massively important I guess. It would be better if CM modified their builds to reflect the correct hardware identifier.
May be worth you expanding your OP slightly to contain a link to the correct CWM - just to make it easier for people to find.
SimonTS said:
No problem. I got the 'Status 7' message when I tried to flash it, due to the P880.
This problem goes away with the latest (v6.0.3.1) version of CWM, so it's not massively important I guess. It would be better if CM modified their builds to reflect the correct hardware identifier.
May be worth you expanding your OP slightly to contain a link to the correct CWM - just to make it easier for people to find.
Click to expand...
Click to collapse
Good idea. I'll probably just expand the model check in the update script for future uploads so it accepts both references.
Update 28/04/13 uploaded, for some improved custom recovery compatibility. As every update, it also contains all official CM patches.
All patches between this version and the last one are minor, so for people who have installed the previous version of the ROM there is no need to update to this one.
Is anyone else having problems with GPS on this ROM? I am going to try going back to all the old methods I used on my HTC DesireS, but thought I'd ask here as well.
For those who wonder what the old methods were, have a look at derekgordon.com
SimonTS said:
Is anyone else having problems with GPS on this ROM? I am going to try going back to all the old methods I used on my HTC DesireS, but thought I'd ask here as well.
For those who wonder what the old methods were, have a look at derekgordon.com
Click to expand...
Click to collapse
No-body?
I have tried ths both with Derek Gordon's gps.conf modification, and with my own one using just the UK NTP servers and no fancy settings.
If I reboot the phone and run GPS Status & Toolbox it takes between 3 and 5 minutes to get the first lock. This happens whether I do it immediately on reboot or leave the phone alone for an hour first. Once it has established a first good lock, GPS seems to be very good - relocks quickly and stays in the background happily.
The problem is the first lock - it's almost as if the hardware is actually starting off disabled and takes time to warm up or something.
Can someone else using this ROM please test to confirm? I will try this with the standard CM 10.1 build and also with the Stock ROM again, but can't do so for a couple of days.
Update 01/05/13 uploaded. I swapped the default CM kernel with the WerewolfJB kernel (thanks laufersteppenwolf!) and I fixed the headphone button actions (key 248 HEADSETHOOK).
SimonTS said:
Is anyone else having problems with GPS on this ROM? I am going to try going back to all the old methods I used on my HTC DesireS, but thought I'd ask here as well.
For those who wonder what the old methods were, have a look at derekgordon.com
Click to expand...
Click to collapse
Sorry SimonTS, but I don't know whether this version fixes your GPS problems. Perhaps I'll have time to look into it later.
Wenque said:
Update 01/05/13 uploaded. I swapped the default CM kernel with the WerewolfJB kernel (thanks laufersteppenwolf!) and I fixed the headphone button actions (key 248 HEADSETHOOK).
Sorry SimonTS, but I don't know whether this version fixes your GPS problems. Perhaps I'll have time to look into it later.
Click to expand...
Click to collapse
No need to apologise mate. I have tried the WerewolfJB kernel, but it doesn't seem to make any difference. I'm going to look at running the WerewolfJB ROM for a while as GPS seems to work perfectly in that, but hopefully you will get time to build a new version as I really want a ROM with pDroid in it.
SimonTS said:
No need to apologise mate. I have tried the WerewolfJB kernel, but it doesn't seem to make any difference. I'm going to look at running the WerewolfJB ROM for a while as GPS seems to work perfectly in that, but hopefully you will get time to build a new version as I really want a ROM with pDroid in it.
Click to expand...
Click to collapse
All you really need to do is copy the good /system/etc/gps.conf file to the PDroid ROM and make sure that you do not block too many permissions. You are probably using Google's SUPL server to help you obtain an initial location estimation and you don't want to block that if you rely on fast GPS locks.
You can do this by first copying the gps.conf file to a safe location (root of sdcard for instance in /mnt/shell/emulated/) and then performing the following steps:
- Use the terminal emulator with the following commands:
= su
= mount -o remount,rw /system
- Now copy the good gps.config file over the current one (for instance using root-permission File Manager or 'su', 'cp /mnt/shell/emulated/gps.conf /system/etc/' )
- Either reboot now or use the terminal emulator with the following commands:
= su
= mount -o remount,ro /system
Wenque said:
All you really need to do is copy the good /system/etc/gps.conf file to the PDroid ROM and make sure that you do not block too many permissions. You are probably using Google's SUPL server to help you obtain an initial location estimation and you don't want to block that if you rely on fast GPS locks.
You can do this by first copying the gps.conf file to a safe location (root of sdcard for instance in /mnt/shell/emulated/) and then performing the following steps:
- Use the terminal emulator with the following commands:
= su
= mount -o remount,rw /system
- Now copy the good gps.config file over the current one (for instance using root-permission File Manager or 'su', 'cp /mnt/shell/emulated/gps.conf /system/etc/' )
- Either reboot now or use the terminal emulator with the following commands:
= su
= mount -o remount,ro /system
Click to expand...
Click to collapse
It's not that simple mate, but thanks for the reply. I know all about the gps.conf file as we used to have real problems with GPS on my old Desire S. The problem I see with this build and the standard CM is almost as if it doesn't know how to talk to the GPS hardware properly.
With the WerewolfJB build and my own gps.conf file I can get a lock in under 10 seconds sometimes, and always under 20.
A. Why change RIL?
Hey, everyone.
As a user that's been using custom roms since our bootloader was unlocked, I'm aware that some of us have some issue with telephony & mobile data (in short, RIL) - occasionally IMEI wouldn't be read on boot, which would lead to device not being registred on network. Sometimes, the network would "die" in a way - you'd get an error when trying to dial a number, and when someone would call you, they'll hear the ringing tone while your cell phone would not ring at all.
The cause of the problem seems to be some lazy coding by official CM developers/maintainers for our device. This was picked up by a developer named kholk, so he did his best to recode it properly, however it was never included into official CM device tree for reasons unknown to me (more info about the issue can be found here: http://review.cyanogenmod.org/#/c/47980/).
Kholk did include his own custom RIL into his EPRJ roms, but the roms are kinda old and have iffy baseband (which seems to be kernel issue, as he's using his own, 3.4 kernel instead of CM's 3.1 kernel in other custom roms).
So, with the help of Adam77Root, I've learned a way on how to implement EPRJ RIL into other custom roms (since I still had RIL issue with default CM RIL in 4.3 roms even) - so far I've tested it with Vanir 4.3, Carbon 4.3, Carbon 4.3.1, and few 4.2.2 roms, and I havent had ANY issues I had in CM RIL.
So, this is a tutorial to show you how you can import EPRJ RIL to any custom rom you'd like, in case you have issues with cell connection.
-this should work on any kernel and any custom rom (4.2.2+)! Tested so far, as far as kernel goes, are iodak 8/8.5, WWJB8/8b, Optimus Prime several versions, Optimus Play! 2.53.
-KK roms tested are P.A. by @dcos which has eprj ril by default, official CM nightlies and several others
-some KK roms, for some reason, don't have x3ril.smali file in their telephony-common.jar. To implement EPRJ RIL in these roms, follow the tutorial up to point 5, and skip that one, since you don't have anything to delete. After point 13, you need to do one additional thing - you need to edit ROM's build.prop settings, look for this line: "#ro.telephony.ril_class=X3RIL", and delete "#" so this line would be included in build.prop. After that, you're ready to flash. Thanks goes to @gerciolisz for the tip on the build.prop settings.
-/As of 24.01.2014. i've added another zip file which contains x3ril.smali taken from P.A. port by dcos - i'd recommend using this one for 4.4.2 roms/
-as of 11.06.2014., I've added x3ril.smali (it's in omni-v1.rar) made by adam, which is based on omni's RIL but has eprj RIL recovery. if you're on 4.4.3 kitkat rom and have issues, i suggest you give this file a try first before others
B. What's needed?
First off, you'll need a few things:
- Android Multitool from http://forum.xda-developers.com/showthread.php?t=2326604, many thanks to @Flextrick
- Read the linked topic - it's the instruction on how to use it, and in case you encounter any errors, that's the place to search for solutions
- Attached is a RAR with two files in it, X3RIL_old.smali and X3RIL_new.smali. You need only one of those - but more info about them will be in the other steps.
- Custom ROM you want to edit
- Common sense
- WinRAR & JAVA
C. How to change RIL?
Steps:
1. First step is to open the .zip of your custom ROM you want to edit, and search for system/framework/telephony-common.jar
2. Extract it to AndroidMultitool/Files, and after extract is done, delete it from .zip
3. Open Android Multitool, under Decompiling select .jar, then select telephony-common.jar in AndroidMultitool/Files, click "decompile"
4. After you're done, check if there were any errors in the Log, in AndroidMultitool main window
5. Head over to AndroidMultitool/Decompiled_jar/telephony-common/com/android/internal/telephony and look for X3RIL.smali. This is CM's RIL implemented in custom roms, which we dont need anymore, so delete it
6. Now, you need to decide wether to use X3RIL_old.smali, which is RIL from EPRJ CM10.2 built on 20130813, or X3RIL_new.smali which is RIL from EPRJ CM10.2 built on 20131007. I'm using 20131007 atm, and it's working without issues
7. When you've decided, move it back into AndroidMultitool/Decompiled_jar/telephony-common/com/android/internal/telephony and rename it to X3RIL.smali
8. Back in AndroidMultitool, under Compilin, select jar, and for folder select AndroidMultitool/Decompiled_jar/telephony-common, press "compile", and check for errors in Log
9. Output should be classes.dex file under AndroidMultitool/Compiled_jar
10. Open telephony-common.jar in AndroidMultitool/Files with WinRar - you should see META-INF folder, with classes.dex file
11. Delete classes.dex file in WinRAR
12. Move classes.dex file from AndroidMultitool/Compiled_jar to telephony-common.jar opened in WinRAR
13. Paste telephony-common.jar into system/framework inside the custom rom .zip file
14. You now have modified ROM ready to flash on our device!
D. Thank You's
Thank you's go out to @kholk for his RIL programming, @dcos for first implementing EPRJ RIL into a rom (his P.A. unofficial port for our device) different than EPRJCM10.2, @Adam77Root for his tutorial that I basically beutified and made sure is easier to understand & his modification of x3ril.smali from omni, @gerciolisz for the tip about build.prop settings, @Flextrick for his Multitool with neat GUI to extract .jar files, and all the other devs of p880 making our device worth every dime I've spent on it.
Flying_Bear said:
Kholk did include his own custom RIL into his EPRJ roms, but the roms are kinda old and have iffy baseband (which seems to be kernel issue, as he's using his own, 3.4 kernel instead of CM's 3.1 kernel in other custom roms).
Click to expand...
Click to collapse
Dude, i think you missed out the clarification for the users on whether or not they need to use the EPRJ Kernel and if anykernel will still work or normal kernels will work etc. Because your bound to have the first person to ask a question will either be, "How do i declare java paths" and "Will 'kernel name here' work with it", this isnt me asking, more of an fyi post (Y)
I do apologize about it, but saves you the time and effort of answering the question every day
MOD EDIT: watch your language please.
penguin449 said:
Dude, i think you missed out the clarification for the users on whether or not they need to use the EPRJ Kernel and if anykernel will still work or normal kernels will work etc. Because your bound to have the first person to ask a question will either be, "How do i declare java paths" and "Will 'kernel name here' work with it", this isnt me asking, more of an fyi post (Y)
I do apologise about it, but saves you the time and effort of answering the question every day
Click to expand...
Click to collapse
np, thanks for the tip. i'll add in OP that it works with any kernel
MODERATOR EDIT: @penguin449 watch your language
I flashed Vanir nightly 171013 with Optimus Prime 2.70 kernel and telephony was completely disabled. I was not able to find or register to the mobile network. I tried modifying the RIL file as explained in this post; initially with the "new" file which didn't seem to solve the problem (still didn't get signal) but I didn't wait I immediately tried flashing the ROM with the "old" RIL instead. Initially there was no signal although I was able to find networks, but after a reboot the phone finally managed to connect to the mobile network.
I'm not sure whether it would've worked after a reboot with the "new" but I'm guessing if it's working with the "old" RIL I got nothing to worry about right?
Vanir is 4.3.1 while OP is for 4.3, i think thats your problem. Different RIL would not help in that case. Flash Anykernel version of OP, or find a version repacked with 4.3.1 ramdisk. Good luck!
Flying_Bear said:
Vanir is 4.3.1 while OP is for 4.3, i think thats your problem. Different RIL would not help in that case. Flash Anykernel version of OP, or find a version repacked with 4.3.1 ramdisk. Good luck!
Click to expand...
Click to collapse
As far as I understood, the 171013 version did not have the RamDisk issue so I figured the CM10.2 version of Optimus Prime kernel should've worked correctly?
So I get it from you that if I flash the original rom with the AnyKernel version of OP it should work fine? (no need for any RIL modifications?)
Yep, anykernel versions of all our kernels xcept iodaks should work on any android version without any modifications.
Is there a way to do this with Linux?
If not, how about uploading modified telephony-common.jar for CM ROMs?
I tried just replacing the whole telephony-common.jar file but I couldn't send or receive any messages. Everything else seemed to work though.
Sent from my LG-P880 using Tapatalk
MilkyJoePD said:
Is there a way to do this with Linux?
If not, how about uploading modified telephony-common.jar for CM ROMs?
I tried just replacing the whole telephony-common.jar file but I couldn't send or receive any messages. Everything else seemed to work though.
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
not sure really, since i havent worked on linux systems.
and i dont think telephony-common.jar is universal for all roms (i might be mistaken though), so there's no use to upload it. however, if you want, upload your original telephony-common.jar file here and i'll do my best to mod it for you!
Flying_Bear said:
not sure really, since i havent worked on linux systems.
and i dont think telephony-common.jar is universal for all roms (i might be mistaken though), so there's no use to upload it. however, if you want, upload your original telephony-common.jar file here and i'll do my best to mod it for you!
Click to expand...
Click to collapse
I meant it would be a good idea to have a place to download the modified files for specific ROMs.
Here's the (unmodified) file for Vanir.
https://app.box.com/s/embcq9kuemfdkdb1qw63
Thanks.
Sent from my Optimus 4X HD using Tapatalk
MilkyJoePD said:
I meant it would be a good idea to have a place to download the modified files for specific ROMs.
Here's the (unmodified) file for Vanir.
https://app.box.com/s/embcq9kuemfdkdb1qw63
Thanks.
Sent from my Optimus 4X HD using Tapatalk
Click to expand...
Click to collapse
well, we have way too much roms for me to download each one and replace the RIL ^^
anyway, here's your modified telephony-common ^^ enjoy!
Flying_Bear said:
well, we have way too much roms for me to download each one and replace the RIL ^^
anyway, here's your modified telephony-common ^^ enjoy!
Click to expand...
Click to collapse
I suppose there is a lot.
I'll test the Vanir one and report back.
If it works then there's a start. I can send messages so it works so far. The only thing keeping me from staying on a CM ROM is the random signal loss.
Sent from my Optimus 4X HD using Tapatalk
MilkyJoePD said:
I suppose there is a lot.
I'll test the Vanir one and report back.
If it works then there's a start. I can send messages so it works so far. The only thing keeping me from staying on a CM ROM is the random signal loss.
Sent from my Optimus 4X HD using Tapatalk
Click to expand...
Click to collapse
check it out, this should fix that issue completely. and report when you have time ^^
Flying_Bear said:
check it out, this should fix that issue completely. and report when you have time ^^
Click to expand...
Click to collapse
If you want some 4.3.1 repacks done i can do them? or if you want some experience, i have the tools to swap ramdisks on windows in my signature that you could use...
In CM ROMs I get crazy data switches from 3g to E and G. Everything is good so far. Time will tell...
Sent from my Optimus 4X HD using Tapatalk
---------- Post added at 01:22 AM ---------- Previous post was at 01:08 AM ----------
penguin449 said:
If you want some 4.3.1 repacks done i can do them? or if you want some experience, i have the tools to swap ramdisks on windows in my signature that you could use...
Click to expand...
Click to collapse
If you can then that would be great. A download for each CM ROM would open up custom ROMs like never before.
Sort out the SD card/internal memory paths and stock ROMs would be not worth installing.
Sent from my Optimus 4X HD using Tapatalk
penguin449 said:
If you want some 4.3.1 repacks done i can do them? or if you want some experience, i have the tools to swap ramdisks on windows in my signature that you could use...
Click to expand...
Click to collapse
if you've got the time and the will, be my guest - however, i don't think it's quite worth it. Not many people have this issue, and those that do would be better off fixing it by themselves then downloading aged nightlies for the rom they're looking for.
MilkyJoePD said:
In CM ROMs I get crazy data switches from 3g to E and G. Everything is good so far. Time will tell...
Click to expand...
Click to collapse
hm, switches from 3g to 2g seems to show that there is a bad connection where you're at. try enabling 2g only or 3g only in custom rom options or quick tiles, most roms support it these days. that should save your battery for few more %.
Just wanted to say that since replacing the file I haven't had to reboot once to get SMS or network to work.
That's over a month, whereas I was having to reboot about every 2 days.
The G/3G switching has improved, but still more sensitive than stock.
Sent from my Optimus 4X HD using Tapatalk
hey what if.... there is no x3ril.smali?XD there is only ril.smali or many others
edit: its ok there just x3ril was missing
I'm on a odexed ROM (mokee 4.2.2 release) so I don't know what to do with classes.dex file multitool generates.It was meant to be used for deodexed telephony-common.jar files.So I tried these steps:
1_)deodex the ROM (using deodexer 4.3),
2_)implent RIL
3_)odex the ROM(using universal odexer 6.3.1) again which I failed to do as something was wrong with decompiling before odexing.This is probably happening due to deodex process.
I got bootloop after odexing the ROM.So I'm curious if there is a way to do this on an odexed jar file without having to deodex first.
I also tried to simply delete the odex & jar file and replace it with deodexed and eprj RIL implented jar file but the rest of the ROM was odexed so it gave me a bootloop.
I don't know much about these stuff, but I did my best searching for a solution and I'm out of ideas.All I want is to have an odexed rom with EPRJ RIL implented, I'd appreciate any help
ottomanhero said:
I'm on a odexed ROM (mokee 4.2.2 release) so I don't know what to do with classes.dex file multitool generates.It was meant to be used for deodexed telephony-common.jar files.So I tried these steps:
1_)deodex the ROM (using deodexer 4.3),
2_)implent RIL
3_)odex the ROM(using universal odexer 6.3.1) again which I failed to do as something was wrong with decompiling before odexing.This is probably happening due to deodex process.
I got bootloop after odexing the ROM.So I'm curious if there is a way to do this on an odexed jar file without having to deodex first.
I also tried to simply delete the odex & jar file and replace it with deodexed and eprj RIL implented jar file but the rest of the ROM was odexed so it gave me a bootloop.
I don't know much about these stuff, but I did my best searching for a solution and I'm out of ideas.All I want is to have an odexed rom with EPRJ RIL implented, I'd appreciate any help
Click to expand...
Click to collapse
unfortunately, i encountered the same issue, and it's beyond my knowledge on what to do with odexed roms. i bypassed the issue by using a nightly which came after the stable was released (not sure if there are any for mokee though)
I am trying to compile android 2.3 v20s kernel and it is giving me 18 mismatch section ...I sorted out first three.....but I am not expecting the other 15.....has any one faced this.......I have use arm-eabi -4.4.3 and 4.4.0 and also 4.6 ...but no change.....
I know there are dev's who has successfully compiled it.....can any one tell me whether they saw so many mismatches ....because it is original source from lg......
I did not face these many mismatch or i think there were none during 4.0.4 compile.....
I know they can be fixed by putting of adding/removing __init etc but i am not expecting them
I have attached the build log ...
You can´t complete the compile ? Check if its complete, because if you are getting something like:
Code:
"WARNING: modpost: Found X section mismatch(es)."
Thats just a adice/warning and the compelition should be fine.
Duarte777 said:
You can´t complete the compile ? Check if its complete, because if you are getting something like:
Code:
"WARNING: modpost: Found X section mismatch(es)."
Thats just a adice/warning and the compelition should be fine.
Click to expand...
Click to collapse
They are just warnings....The build is complete
...But i think section mismatches are bad...and these are too many....
Sent from my LG-P970 using xda app-developers app
Duarte777 said:
You can´t complete the compile ? Check if its complete, because if you are getting something like:
Code:
"WARNING: modpost: Found X section mismatch(es)."
Thats just a adice/warning and the compelition should be fine.
Click to expand...
Click to collapse
Also the lines where mismatch is coming ...the code is same in 4.0.4 but they don't give warnings ...I used 4.6 for 2.3 also but same ....
Are there any compiler flags to be set in makefile which can take care of these.....
Sent from my LG-P970 using xda app-developers app
Can any more dev's put some light on this....
Sent from my LG-P970 using xda app-developers app
I downloaded arm-linux-androideabi-4.6 from https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/
and then only got one warning which I fixed and no warnings now.....
but if i use arm-eabi-4.6 https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/
or any arm-eabi- version then i get 14 mismatch ,,,,,,
AFAIK arm-eabi- is used to build kernels and androideabi is used to build android layer.......but the later also builds kernel and i don't get any warnings now.......
Also found one reference where arm-linux-androideab- is used to build nexus S kernel.....
http://glandium.org/blog/?p=2214
So is it safe to use kernel built by arm-linux-androideab-
I see there is no response .But that is OK,as I have fixed all the section mismatches .The issue was in LG's code..and now compiled with arm-eabi-4.6 with zero section mismatch errors....I will try the kernel after applying rmcc patch ..maybe this weekend.
got the kernel booting
see below post for info
http://forum.xda-developers.com/showpost.php?p=52409264&postcount=13
https://github.com/rajeshmk2011/lg_p970_gingerbreadkernel.git