Related
Liberation
"Free yourself from your carrier"
Features:
[ROM Base] HTC Droid Incredible 4.08.605.2
Android 2.3.4
De-bloated
Deodexed
Battery percentage
4-in-1 advanced power menu
Removed E911 location icon
Red scrollbar and overscroll glow to complement the Incredible's looks
Zip-aligned for optimal memory management
CDROM.ISO removed (prevents that annoying Verizon install prompt when connected via USB)
Uses edify script, will flash in Clockwork Recovery 2.x and 3.x.
Removed Apps:
Adobe Flash Player (install from Android Market if you want it)
Adobe Reader (install from Android Market if you want it)
Amazon MP3 (install from Android Market if you want it)
CityID (annoying 3rd party bloatware)
Facebook (install from Android Market if you want it)
Slacker Radio (install from Android Market if you want it)
QuickOffice (for those who want a free Office reader, try Documents to Go from the Android Market)
Verizon Bloatware (My Verizon, VCAST App Store, Verizon Navigator, Verizon Skype, Verizon Backup; most can be installed via Android Market)
Youtube (install from Android Market if you want it)
Downloads:
Liberation v3.0 - 143.08MB
MIRROR (provided by BrettApple)
Changelog:
v3.0 (January 6, 2012)
Based on the latest official RUU - 4.08.605.2 (Android 2.3.4)
Red scrollbar and overscroll glow to complement the Incredible's looks
v2.0 (September 20, 2011)
Based on the latest official RUU - 4.06.605.3 (Android 2.3.4)
System hardware information corrected in about phone (bug with official OTA)
Removed Sprint section/tile from Market, replaced with Verizon (bug with official OTA)
Only 688MB available to user (see explanation in FAQ)
No longer patched to block Android Market malware (Android 2.2.2 and above are immune by default)
v1.1 (June 25, 2011)
Added battery percentage meter.
More efficient compression (smaller file size)
v1.0 (May 19, 2011)
Initial Release based on November OTA (3.21.605.1)
FAQ:Q: What was the difference between the standard and enhanced versions of Liberation?
A: In simple terms, Liberation Enhanced was deodexed, while the standard version was not. However, since the Gingerbread update, HTC has deodexed the /system/app folder, but has left framework odexed. I've decided to just deodex everything instead of having two separate versions with minimal differences in available storage, but vast differences in customization.
Q: Why is the Android Market outdated!?
A: If I insert the latest market, it won't update on its own, meaning more work for you. The version of the market I'm using is outdated, but auto updates. It will update in the background the first time that you run it, and should be updated within 2-5 minutes depending on your connection. You'll need to exit and re-launch the Market for the update to take effect.
Q: Some of my Google Apps (such as Gmail) are an old version, but don't show up on the Market as installed or needing an update. How do I fix this?
A: This is a bug or "feature" of the stock ROM, I'm not sure which. However, it as a very easy fix. Simply open Gmail from the Android Market. From there, scroll down to "Developer Info" and select "View Applications." This will display all of Google's apps in the market. Scroll down and update every app that shows as needing an update (they'll all display correctly from here). You may also want to disable automatic updates from here.
Q: Why isn't <insert app here> removed, I consider it to be bloat!
A: HTC did their best to put together an experience utilizing their Sense software. I left that intact as every user will get something out of it. Some use Friend Stream. Some use only Facebook/Twitter/Flickr. There is no perfect combination as every user wants something different. My goal was to present a stock experience without the carrier bloat. There are ways for you to remove unwanted apps yourself if you'd like.
Q: Why aren't there any screen shots?
A: It's a stock ROM. I've done nothing to differentiate this ROM in appearance from what your carrier/OEM ships.
How to customize Liberation BEFORE you flash:
Materials
Windows - 7-ZIP
Linux - nothing
Mac OS X - nothing (note, I have not done this on Mac OS X, so I cannot support this OS)
Steps
Download the above mentioned file(s) for Windows. You can use a different archive manager if you'd like, but my guide is based on using 7-ZIP.
On your desktop, create a folder named "Test." You can name it whatever you want, but I'll be referring to it as "Test" in this guide. If you are new at this, you need to follow the guide to the letter.
Find your downloaded ROM and extract it to the Test folder. The easiest way to do this on Windows is to open the ROM, highlight all of the folders/files (CTRL-A), copy (CTRL-C), then open the Test folder and paste (CTRL-V). Give it a minute to extract the contents.
Once you complete step three, modify the ROM to your hearts content (see details below). Once complete, proceed to step five.
Open the Test folder and highlight everything (CTRL-A). Right click and select "Add to Archive." This will open 7-ZIP's archive manager. On Linux or Mac OS X, just right-click (or equivalent) and select "Compress."
In the options menu that comes up, leave everything at default except the following. The filename should be Test.zip (change Test to whatever you want). Archive format should be zip. Compression level should be ultra. That's it.
Once done, you can copy this zip to your SD card and flash as normal. Keep in mind that I am not responsible for any changes that you made in this ROM, so make sure you Nandroid BEFORE you flash.
Specific Modifications (using the above instructions):
Ringtones - While the ROM is unzipped, open the test folder and look for /system/media/audio. Within this folder you'll see several more folders (Ringtones, Alarms, Notifications). Any should files you put here will show up in the system when you go to change your ringtone (or whatever corresponds to the folder). The benefits to this modification include; no storage space used up in internal, phone, or SD storage; ringtone works even if SD is USB mounted, no errors when the SD card corrupts or is in use. The ringtones (alarms/notifications) are stored in a partition that does NOT count towards your file storage
Replacement "stock" applications - If you use a differnent web browser (like Dolphin HD or Firefox), or a different SMS/MMS program (like Handcent or Chomp), then it is recommended that you remove the stock applications before flashing. This prevents conflicts, slowdown, memory usage, and the annoying popup where you have to constantly re-choose your default application. In these examples, you are looking for /system/app/browser.apk and mms.apk.
Add/Remove apps you don't want - Navigate to /system/app, and remove any APK files that you don't want. If you don't know what app it is, do NOT remove it
Modify Bootup Animation/Sound - Navigate to the /system/customize/resource/ folder. In there, you will see two files; VZW_bootanimation.zip an VZW_Droid.mp3. These files are the bootup animation and "Droid" noise. Simply delete the MP3 if you want a silent bootup. It really is that easy. Replace the ZIP File with another zipped animation (must give it the same name) to replace the animation with one of your own. NOTE: Make sure you verify compatibility. If unsure, don't do it.
Files needed for UOT Kitchen:
Download - framework-res.apk
Download - com.htc.resource.apk
Download - SystemUI.apk
The above files are needed for the UOT Kitchen. Ask questions in this thread if don't know how to use them. UOT Kitchen allows you to change visual elements of your phone's stock interface in a way that no launcher app ever could.
jaykresge, you gonna get anything going with this gingersense leak?
Why is this based off the November OTA? Use the new gingerbread leak!!
Sent from my ADR6300 using XDA App
josh0426 said:
jaykresge, you gonna get anything going with this gingersense leak?
Click to expand...
Click to collapse
I'll mess with it.
tjrocks91 said:
Why is this based off the November OTA? Use the new gingerbread leak!!
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Need to have the stable release out before the test/beta releases
This seems like a cool idea. Looking forward to the download links.
Sent from my PC36100 using Tapatalk
I agree.
I would love to see a ROM of yours based off of the Gingerbread Leak.
Nothing Special is the fastest and most stable ROM out. Hands Down.
I use it as my Daily Driver in a business setting and its perfect.
rosser725 said:
This seems like a cool idea. Looking forward to the download links.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Liberation is uploading right now, should be available in a few minutes. Enhanced is still cooking, might be another 30 minutes or so. As for the "cool idea," this is actually just a renamed update to an existing ROM. See below.
tincbtrar said:
I agree.
I would love to see a ROM of yours based off of the Gingerbread Leak.
Nothing Special is the fastest and most stable ROM out. Hands Down.
I use it as my Daily Driver in a business setting and its perfect.
Click to expand...
Click to collapse
I'm cooking Liberation Enhanced right now, then I'll immediately start playing with the leak. We've seen a few developers upload flashable versions already. I can't commit that I'll release anything on this leak at this point. Let me play with it some and then I'll comment on it.
Both 1.0 ROMs are up based on the November OTA. Currently toying with the leak, will update.
Re-cooking then uploading the beta for 2.00 based on today's Gingerbread leak. Use at your own risk.
I agree with tincbtrar.
Liberation Enhanced v2.00 BETA, based on today's Gingerbread leak, is now up. Use at your own risk.
jaykresge said:
Liberation Enhanced v2.00 BETA, based on today's Gingerbread leak, is now up. Use at your own risk.
Click to expand...
Click to collapse
Downloading now, Thanks.
I'm liking some of the changes. Reboot time (after initial flash) is insanely fast. HTC Car Panel now works in both portrait/landscape, however, most other apps still don't. Feels smoother than 2.2 (and I just did clean flashes of all of my ROMs, it's definitely smoother).
Let me know what you think, but so far, feels good for a beta. I'll make it my daily driver for the next few days and see what happens.
Downloading the beta now. Already a few out there, but I know you put out good work, and it's the slimmest so far. Fingers crossed, already put the new radio on. This is great! Long live the Incredible!
Will definatly give this a try when I get home.
Only thing that stinks is the cool mods (Pulldown Toggles, EVO Camera, ETC) wont work with the beta correct? Those pulldown toggles are amazing for me (Flashlight, Bluetooth and Sounds - especially)
Once that gets sorted out Ill be using your beta. Until then maybe ill flash Liberation for fun.
Great work sir.
Is 2.0 deodexed?
Sent from my ADR6300 using XDA App
BrettApple said:
Downloading the beta now. Already a few out there, but I know you put out good work, and it's the slimmest so far. Fingers crossed, already put the new radio on. This is great! Long live the Incredible!
Click to expand...
Click to collapse
Just an FYI, it works fine with the existing radio. I won't be pushing users to update radio/hboot/etc. until the official release comes out.
tincbtrar said:
Will definatly give this a try when I get home.
Only thing that stinks is the cool mods (Pulldown Toggles, EVO Camera, ETC) wont work with the beta correct? Those pulldown toggles are amazing for me (Flashlight, Bluetooth and Sounds - especially)
Once that gets sorted out Ill be using your beta. Until then maybe ill flash Liberation for fun.
Great work sir.
Click to expand...
Click to collapse
I'm going to work on getting an Evo camera working for it. As for flashing Liberation, it's just Nothing Special under a new name (and the minor change of Car Home switched for Car Panel). All of the mods you used on NS will work here
cabjmb said:
Is 2.0 deodexed?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Yes.
As featured on the XDA portal Here
Note: I understand that the source is for 2.3.4 right now, but svyat is currently working on an ICS version. Hopefully a talented Dev can figure this first. If not, I will post svyat's ICS source patches when he makes them available.
This thread is really a request/research & development topic. I take absolutely no credit for any of the work done by svyat or any potential/willing ROM dev or chef.
The purpose is to bring to attention a new app created by svyat by the name of PDroid. You can find that thread Here.
PDroid is an app with a capability a lot of you are probably already familiar with; permission control. Permission control is the ability to block which permissions apps have access to on your device. PDroid takes this a step further by allowing you to block or change the information that a requesting app receives.
For example: many of you may be aware of LBE security app or permission control in Cyanogen. A lot of times when you block permissions to an app it will cause the app to break (force close) which requires you to change back your settings allowing the app access to information you would rather deny. What is the purpose of blocking data if it just breaks an app? Well that's why svyat has written Pdroid.
PDroid allows you to block permissions AND if that breaks the app, instead you may provide the app with false information. For example: When an app requests your location, you can have PDroid provide a false location. Or when an app requests your IMEI, you can have PDroid provide a false IMEI that you made up. You are able to do this will many of the permissions.
What I am requesting from a ROM dev or chef:
I am not experienced with programming at all so I will do my best to describe what I understand.
PDroid requires that Roms be patched so that the app can work. Currently svyat is doing the patches at a request basis. This is a slow process (he has many people requesting and is working alone). So I am hoping we can get a willing chef to patch one of his ROMs with this.
You can find the patch source Here
Instructions for patching:
Download: PDroid 2.3.4 source (v1.22) (yes it is based on 2.3.4 but also works with 2.3.3 and 2.3.5 flawlessly)
Get the 2.3.4 source from AOSP (branch: android-2.3.4_r1)
Extract the patches from the above archive to the 2.3.4 tree root
Run:
Code:
patch -p1 -i build.patch
patch -p1 -i frameworks.patch
patch -p1 -i libcore.patch
Building from source:
Make a clean build
Apply the patches (see above)
Run:
Code:
source build/envsetup.sh
make update-api
mmm frameworks/base
mmm frameworks/base/services/java
mmm libcore
make snod
However, for experienced developers the following basic steps for creating a PDroid patch should be enough to get you started:
Make a clean AOSP build (2.3.4, assuming that your ROM is based on 2.3.x)
Make another build with PDroid sources added
Decompile the framework.jar, services.jar and core.jar files inside the system/framework directory (of both above builds) using apktool
Diff the output so that you know, which parts were changed by PDroid
Decompile the above three files from your ROM, you want to patch
Add the missing code to your ROM files based on the above diff
Recompile your patched ROM files using apktool
I really seeing this type of control being the new standard for custom ROMs. To me, this is another BIG reason to be rooted!
disregard 10chars
disregard 10chars
Sent from my Nexus S using xda premium
disregard 10chars.
Sent from my Nexus S using xda premium
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!
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)
Hello there, as you know, building a rom isn't simple, not at least until you get the hang of it. I know that not many people (actually, it seems it's just me) build for this phone anymore, so I thought I'd make a little thread to help you.
Here are a few patches to make your builds stabler:
Deep Sleep Patch-
https://github.com/XePeleato/hisi_f...b5fe589a7cc2223a344e56d84e450041756656a.patch
NFC Patch-
https://github.com/Meticulus/androi...mmit/646011845bedc537c157f490d95e98d5e3f01057
Network Toggles Patch-
https://github.com/Meticulus/androi...mmit/ed6563e6fb5747fd0eedc9258aae37ec06891d05
Bluetooth Patch-
https://github.com/Meticulus/androi...mmit/c4fc752cdd31c0c6b2fa29af080cb6af206d8293
RIL Patch (If it stops working across reboots)-
https://github.com/Meticulus/androi...mmit/447f899531949d4d03769fe7235ca7137af3443b
P.S
Some of these may have to be applied manually rather than using the usual patch command.
GPS Patch is in my AOSiP thread.
I think this is all,
Enjoy!
Is there any way to pass any of those to a .zip file to install it in the ROM instead of doing all the construction? Add it to the system as a simple patch
matamata15c said:
Is there any way to pass any of those to a .zip file to install it in the ROM instead of doing all the construction? Add it to the system as a simple patch
Click to expand...
Click to collapse
Nope. These are patches that are applied to the rom sources, and those are different from one to another.