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!
Related
Hi all,
I just got tap tap revenge 4 that is free in the market and I need three point multitouch at least to play majority of the songs on extreme. Could someone please send me a script or what exact file to edit in build.prop? Thanks, and any help is appreciated
Editing build.prop will not get you 4 point multitouch.It needs to be supported by the kernel. I don't think any of the latest 2.2.1 kernels support that.
sileshn said:
Editing build.prop will not get you 4 point multitouch.It needs to be supported by the kernel. I don't think any of the latest 2.2.1 kernels support that.
Click to expand...
Click to collapse
Oh really? Sorry then, I guess I was misinformed. Does anyone know how to get 4 point multitouch on cm6 without wiping data, cache etc?
As sileshn stated 4 point multi-touch is currently NOT supported by ANY of the LATEST KERNELS!
sileshn said:
Editing build.prop will not get you 4 point multitouch.It needs to be supported by the kernel. I don't think any of the latest 2.2.1 kernels support that.
Click to expand...
Click to collapse
the older version which was in CM works with 4point multitouch and can be found http://code.google.com/p/cyanogenmod4milestone/downloads/detail?name=bootimg0.04.zip there, afair this one still had to issues that you had to reboot each time you plugin your phone to usb/charger
sileshn said:
Editing build.prop will not get you 4 point multitouch.It needs to be supported by the kernel. I don't think any of the latest 2.2.1 kernels support that.
Click to expand...
Click to collapse
Daer Sileshn
In the first post of this linked thread, IcenFire says he have >>> 4 POINT MULTITOUCH SUPPORT FOR MILESTONE- abilited by a little hack in build.prop
This is exactly what this thread is questioning about that little hack in build.prop
Please recheck and reply your views.
indiacam said:
Daer Sileshn
In the first post of this linked thread, IcenFire says he have >>> 4 POINT MULTITOUCH SUPPORT FOR MILESTONE- abilited by a little hack in build.prop
This is exactly what this thread is questioning about that little hack in build.prop
Please recheck and reply your views.
Click to expand...
Click to collapse
All latest kernels do not have 4point MT. You need to flash a older kernel if you need 4point MT. No it is definetely not possible just by changing a few lines in the build.prop file.
Sent from my MILESTONE using Tapatalk
well, i flashed the older kernel that's free of DSI errors, but still even after editing the build.prop it still has no 4-pt multitouch after rebooting.
Hello!
Ok so this is an attempt to port MIUI to LGP500. We are trying this because porting on the Galaxy 3 (LDPI armv6) was a success and i'm sure it will work on our device too.
This is what we're using so far: MIUI for Desire & Overflow ROM
So far this has been done:
ADB now working
Merged framework.jar from base rom with MIUI one
Replaced all apks with miui except LatinIME.apk which seems to give an error on boot
Use libs, bin and xbin from base rom
Merged permissions
[Update 9.07.2011 - 17:48 GMT+3 DST]
Now using framework from CM7
Libs, and bins from CM7
Boot.img still from Overflow (CM7 Boot.img stops adb on boot after a while - so using Overflow for developing for now)
Replaced many smali files in framework but errors keep popping up - I think framework is pretty screwed up now and must be redone (again)
No more nasty error on boot (with stack dump and stuff...)
No need for logcat now because errors come from framework
[Update 11.07.2011 - 15:32 GMT+3 DST]
MIUI boots up and we have graphics BUT
It only boots up to some error dialogs that say some processes force closed with "Close" and "Report to MIUI"
Gapps, Provision, and StatusBar force close so they need work
Removed ContactsProvider.apk and CalendarProvider.apk
[Update 14.07.2011 - 10:58 GMT+3 DST]
Fixed framework.jar - no more errors seem to come from it
New zip not made on mac so no low memory errors
New problem that might fix the apps: All apps look for their classes.dex in /cache/dalvik-cache but only system classes are there. The app classes are created in /data/cache/dalvik-cache
All apps are back because the errors don't come from them
[Update 28.07.2011 - 18:53 GMT+3 DST]
Added dalvik-cache to /cache script
New zip with init.d script and updated framework
Need to fix dead code in framework
Need new kernel
Need MDPI apks
Need libs that don't make the apks crash
Latest flashable zip:
http://www.multiupload.com/VNM8QTDBZ3 [Updated 28.07.2011] Thank you 4silvertooth
(DOES NOT BOOT! DON'T FLASH IF YOU DON'T KNOW WHAT YOU'RE DOING!) Sorry... i had to put this in big red letters because apparently people didn't see it well...
If you would like to help go ahead. Download the rom or make your own one if you don't like our development and give input. But most of all don't try to bring us down with "this can't be done" stuff. It can be done and it was done for another armv6 device. We need to get apps and framework to work and rom to boot. Libs and bins will come after...
This being said i would like to thank these people for their work so far and for making me get off my ass and do something useful:
4silvertooth
jazux
DJoptimus-One
Also i would like to thank overflow for his rom. It's the base for our miui so far.
Fantastic news! I can't wait too see how this works out. Good luck, you're gonna need it!
look forward to.
Thanks popdog
Will get into works as soon as i get my laptop back
Great news!
Waiting for testing release!
wow ! MIUI for o1 ?
oh sh*t this is what i've been waiting for so long !
looks good ill be happy to help, just ask for now im looking the motorola dump... maybe theres something that will help my team on galaxy 3 but anyway i subscribed tol this thread
EDIT: damn that motorola dump is useful, already found many, many tweaks thanks a million times for 4silvertooth
Hey can we use pastebin.com for all the logs.. it will be convenient and easy.
Sent from my LG-P500 using XDA Premium App
good point... also do you know a way to upload the files like in a git source (only the ones that changed) because multiuplad is painfully slow for me...
popdog123 said:
good point... also do you know a way to upload the files like in a git source (only the ones that changed) because multiuplad is painfully slow for me...
Click to expand...
Click to collapse
No but make a base rom and update.zip which will have all changes and will be small in size.
Sent from my LG-P500 using XDA Premium App
About the log.
The error so.lcddensity(something) is in build.prop you have to add it, it's using 160 by default.
All the missing class will have to be taken from the decompiled framework.
Sent from my LG-P500 using XDA Premium App
I'm redoing framework.jar... See what i missed... Then i'll get to build.prop
Also using boot.img from mik's cm port now
Breaking news of the day! I'll one of the first tester Keep going, heroes!
popdog123 said:
I'm redoing framework.jar... See what i missed... Then i'll get to build.prop
Also using boot.img from mik's cm port now
Click to expand...
Click to collapse
Will have to replace some smali. Merge the missing wont do.
@jazuk which one mainly.
Sent from my LG-P500 using XDA Premium App
Great news!
4silvertooth said:
No but make a base rom and update.zip which will have all changes and will be small in size.
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
+1 for this, it would be easier to download for people with a slow connection like me.
ok ok... will do that... but for now we have to make a good base to start off of...
4silvertooth said:
Will have to replace some smali. Merge the missing wont do.
@jazuk which one mainly.
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
Whaaat???
Nice to see another dev porting some other firmwares to our phone if you want help then I'm in
Sent from my LG Optimus One P500 using XDA Premium App
jazux said:
Whaaat???
Click to expand...
Click to collapse
Never mind back to that later.
Sent from my LG-P500 using XDA Premium App
It's important for everyone to know that since this is a development thread, most, if not all conversation should be dedicated to helping us boot the ROM. All questions related to and including "will our device be able to handle Jellybean?" should be moved to the following thread: http://forum.xda-developers.com/showthread.php?t=1736089
Our biggest problem so far: There are incompatibilities with Jellybean and the Adreno drivers, which our phone needs to function. We can't just remove the Adreno drivers and boot the ROM (I tested this, by removing them from our latest CM9 nightly, which wouldn't boot as a result. I also removed the Adreno drivers and used the Jellybean ramdisk, framework, libs, and bin files but still no boot.).
PureMotive's port
I booted my source-built Jellybean.
Status: ALPHA
Working
Root
ADB
3G
WiFi
Calls (outgoing and incoming)
Signal
UI
Soft keys + lights
RIL
GPS
Brightness settings
Sync
SMS
MMS
Gmail
Gtalk
Twitter
Facebook
Audio
Downloads
Native screenshot (should work now)
Google Now
Untested
Video
Bluetooth
Camera
Broken
Butter
Browser (default)
HWA
Click to expand...
Click to collapse
Albinoman's port
Check his thread located here
Click to expand...
Click to collapse
PORTING FILES:
Code:
Jellybean SDK: [URL]http://d-h.st/EUH[/URL]
Jellybean Ramdisk: [URL]http://d-h.st/XhF[/URL]
Boot.img used in Tiny's port: [URL]http://d-h.st/a0C[/URL]
Vicious Jellybean (VZW GNex port): [URL="http://rootzwiki.com/topic/28486-rom-vicious-toro-jellybean-v3-100-functional-franco-kernel-beats-audio-mods-optimized-link-in-op-for-stock-kernel-added-112am-06302012/"]Vicious Jellybean[/URL]
On vacation. When I get back next week I'll check it out
Sent from my unrootable DROID2
where the hell is the ramdisk
Just wanted to mention my scan of the ramdisk the other night didn't lead to anything conclusive. I checked real quick yesterday I think but didn't really have time to look in depth. I didn't see a problem with the way the system mounted so something else is causing it. I'm trying to port it right now. We'll see what happens.
Maybe I should give it a try.
How about paste bin a logcat?
Here is my current logcat
http://paste.ubuntu.com/1074131/
Sent from my Droid Incredible using xda premium
Shano56 said:
where the hell is the ramdisk
Click to expand...
Click to collapse
Posted in the OP.
PonsAsinorem said:
How about paste bin a logcat?
Click to expand...
Click to collapse
We cannot get a logcat with the Jellybean ramdisk, even with these edits to default.prop:
Code:
persist.sys.usb.config=mass_storage,adb
persist.service.adb.enable=1
persist.sys.strictmode.disable=true
persist.service.adb.root=1
ro.secure=0
ro.allow.mock_location=1
ro.debuggable=1
service.adb.root=1
The error that follows is this:
Code:
'system/bin/sh' failed no such file or directory
Adding a "sh" file to /bin results in other errors (don't have them right now)
The only way a logcat will work is if we use the ramdisk from a CM9 ROM in addition to the CM9 libs.
PureMotive said:
Posted in the OP.
Click to expand...
Click to collapse
hehe now u post it. ty
edit: i thought you needed it extracted
PureMotive said:
Posted in the OP.
We cannot get a logcat with the Jellybean ramdisk, even with these edits to default.prop:
Code:
persist.sys.usb.config=mass_storage,adb
persist.service.adb.enable=1
persist.sys.strictmode.disable=true
persist.service.adb.root=1
ro.secure=0
ro.allow.mock_location=1
ro.debuggable=1
service.adb.root=1
The error that follows is this:
Code:
'system/bin/sh' failed no such file or directory
Adding a "sh" file to /bin results in other errors (don't have them right now)
The only way a logcat will work is if we use the ramdisk from a CM9 ROM in addition to the CM9 libs.
Click to expand...
Click to collapse
I got a port booting with your jellybean ramdisk. It won't go far but I'm about to provide a logcat after testing some changes. Toolbox and busybox work. I ported from the gnex. No boot screen but it does start to load files. Maybe you guys can figure it out from here. I'll upload it and my logcat after I test my zip.
Logcat linked below:
http://paste.ubuntu.com/1075642/
Initial Port Below:
http://d-h.st/shx
Upload!!!! Lol
Sent from my Droid Incredible using xda premium
tiny4579 said:
I got a port booting with your jellybean ramdisk. It won't go far but I'm about to provide a logcat after testing some changes. Toolbox and busybox work. I ported from the gnex. No boot screen but it does start to load files. Maybe you guys can figure it out from here. I'll upload it and my logcat after I test my zip.
Logcat linked below:
http://paste.ubuntu.com/1075642/
zip file coming next.
Click to expand...
Click to collapse
Did you use the ramdisk from the OP or the boot.img I sent you? I got it to the point where it would load the framework .jar files, but haven't encountered what you did in your logcat so I'd consider it progress lol. Seems to be an issue with EGL...
EDIT: Nevermind lol
The error that follows is this:
Code:
'system/bin/sh' failed no such file or directory
Adding a "sh" file to /bin results in other errors (don't have them right now)
Sounds to me like you are missing /bin/mksh either in ROM or in symlink in updater
Sent from my PG06100 using xda premium
Just wanted to first of all say thanks for this - it's awesome that this is even being worked on. We have such an awesome dev community. Secondly, just wanted to offer my support in any way possible. I don't have a lot of experience with porting Android, but I do have pretty good Linux system knowledge and a willingness to experiment. Downloading tiny's build now, going to mess around with some system files and see what happens. Thanks again guys!
Cm is going to working on cm10.
http://briefmobile.com/cyanogenmod-cm10-coming-with-jelly-bean-source-code-release
Sent from my ADR6300 using xda app-developers app
tiny4579 said:
I got a port booting with your jellybean ramdisk. It won't go far but I'm about to provide a logcat after testing some changes. Toolbox and busybox work. I ported from the gnex. No boot screen but it does start to load files. Maybe you guys can figure it out from here. I'll upload it and my logcat after I test my zip.
Logcat linked below:
http://paste.ubuntu.com/1075642/
Initial Port Below:
http://d-h.st/shx
Click to expand...
Click to collapse
Hey tiny4579 could you post what you changed/added in your build?
Albinoman said:
Hey tiny4579 could you post what you changed/added in your build?
Click to expand...
Click to collapse
I don't remember quite what I did and I'm not in a position to test but what if you take evervolv as a base and replace the app and framework folders with the ones from my port and the boot.img with the one from the port. It probably won't work by a long shot but at least it's worth a try.
Sent from my Galaxy Nexus using Tapatalk 2
I see progress! I will download your port right now and see what I can help you with.
tiny4579 said:
I don't remember quite what I did and I'm not in a position to test but what if you take evervolv as a base and replace the app and framework folders with the ones from my port and the boot.img with the one from the port. It probably won't work by a long shot but at least it's worth a try.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'll try that later today. What version of evervolv are you using?
Sent from my Droid Incredible using xda premium
Albinoman said:
I'll try that later today. What version of evervolv are you using?
Sent from my Droid Incredible using xda premium
Click to expand...
Click to collapse
I was testing with 2.2.0a1.
Sent from my Galaxy Nexus using Tapatalk 2
Hi guys,
i'm a new member and i've read forum rules, this is my first post, i hope i'm posting to the right section. I'm trying to build ChameleonOS from source for our device, after 7 hours everytime i get two errors saying "vibrator.c:76: error: undefined reference to "sendit"" and "vibrator.c:81: error: undefined reference to "sendit"", then the build stops with Error 1. I'm using Lubuntu 13.04 with ChaOS repo and Team Canjica's repos: device, vendor, kernel, libhardware and libhardware_legacy, i followed this guide: http://forum.xda-developers.com/showthread.php?t=2351504. Seems that these errors are related to libhardware_legacy's vibrator.c, i attach the image of the error in this post. Thanks
P.S. Sorry for my bad english, i'm Italian
EDIT: For error I made post #5 instead of edit this, sorry! :angel:
No one can help me? Also only to ignore the errors and continue the build, if there's a way, instead of automatically stop it. In this case I can extract libhardware_legacy.so from CM10.1's flashable zip and put it in builded ChaOS's flashable zip.
Add ifdef to the original vibrator c file
Sent from my GT-I9070 using Tapatalk 4
Shaaan said:
Add ifdef to the original vibrator c file
Sent from my GT-I9070 using Tapatalk 4
Click to expand...
Click to collapse
In which part of file I have to add it?
[HELP] ChameleonOS-janice compiled, but wifi issue!
Now I have compiled ChameleonOS for janice, everything works fine but low incall volume bug, same as CM, and wifi doesn't turn on with compiled boot.img... I've tested it with CM10.1 build 20130923's boot.img and wifi works, but in this way loses the customizations and possibility to use integrated theme manager, which are the strong point of this rom. When this problem will be resolved I share the rom in devs section. Any help will be appreciated
Tesla-MADAL93 said:
Now I have compiled ChameleonOS for janice, everything works fine but low incall volume bug, same as CM, and wifi doesn't turn on with compiled boot.img... I've tested it with CM10.1 build 20130923's boot.img and wifi works, but in this way loses the customizations and possibility to use integrated theme manager, which are the strong point of this rom. When this problem will be resolved I share the rom in devs section. Any help will be appreciated
Click to expand...
Click to collapse
compile again with our updated sources
Sent from my GT-S5367 using xda app-developers app
frapeti said:
compile again with our updated sources
Sent from my GT-S5367 using xda app-developers app
Click to expand...
Click to collapse
Okay, sources updated, now I'm rebuilding
EDIT: Recompiled, now wifi works
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)