Database Info

[Patch] Add Arabic Support to any ROM [0.97][Updated 9-5-2012]

IT's NoT My WORK - I've already added the source at the end
There is a lot of new roms which are released every week or two,...
and there is a lot of them which have no support for arabic letters
But it's ok,...
you can add the arabic support [RTL] to any rom in less than 5 Minets
AND IF YOU ARE A DEVELOPER PLEASE ADD IT TO YOUR CUSTOM ROM TOO
What is this patch doing?
framework.jar: takes care of shaping texts in android on all texts except Gmail and the browser
libwebcore.so: takes care of shaping texts in the default Browser and Gmail app.
Click to expand...
Click to collapse
So, This patcher will attempt to get you Arabic support in both of these files.
The coder [madmack]:
"This should work with all Android phones supporting Android Froyo or Gingerbread with the exception of MIUI ROMs as they are closed source and I can’t work with that."
Click to expand...
Click to collapse
Note: Please perform a backup of your system before attempting to use this patch.
Requirements:
Rooted Device
Android 2.1 at least
Your ROM needs to be deodexed.[!]
Java "32-bit" installed
[!] To find out if your installed ROM is deodexed, navigate to /system/framework on your phone. If you see a file called framework.odex then this patch will NOT work for you.
Click to expand...
Click to collapse
Steps to apply the patch:
Download the patch below and extract it to a folder on your computer.
Pull these files to the "input" folder
/system/framework/framework.jar
/system/lib/libwebcore.so
/system/lib/libandroid_runtime.so (If you’re not using a CyanogenMod ROM)
Run "commands.exe". (Do not close the black cmd screens that will pop up. Once the patch is done)
You should get a patched framework.jar, libwebcore.so and libandroid_runtime.so in the subfolder "output"
There is a recovery flashable file in folder output. Place that on your sdcard, reboot into recovery and flash it.[!!] [**]
[!!] It's better to replace the generated .zip "SYSTEM" Folder with The "SYSTEM" folder of any flashable .Zip which worked on your RECOVERY before
Click to expand...
Click to collapse
[**] If the flashing through recovery didn’t work for some reason,
You’ll need to do the following manually:
Put file output/framework.jar in /system/framework/
Put file output/libandroid_runtime.so in /system/lib/ (if this file exists, it shouldn’t if you’re arabizing CM6).
Put file output/libicuuc-arabic.so in /system/lib/
(This is extremely important, failing to place this file will result in a boot loop of your deivce)
If file exists: Place file output/libwebcore.so in /system/lib/
If file exists: Place file output/lib__bcore.so in /system/lib/
Sometimes permissions and xml data doesn’t get updated correctly resulting in corrupted data entries. If you receive a bunch of Force Closes after a reboot, you’ll need to Factory Reset.
Click to expand...
Click to collapse
SOURCE: How To Apply Patch

Change log:
0.907
Updated the webkit patcher to 3.91B (support for more devices).
Click to expand...
Click to collapse
0.906
Updated the webkit patcher to 3.1B (support for more devices).
Reduced size of libicuuc-arabic.so to the bare minimum. This should also help make it have broader device compatibility. (Thank you brightidea)
Click to expand...
Click to collapse
0.904 & 0.905
Updated the webkit patcher to 2.6B (support for more devices).
Fixed errors caused by 0.904 in 0.905. To all who have downloaded 0.904, please download 0.905.
Click to expand...
Click to collapse
0.902
Updated the webkit patcher to 2.3B (support for more devices. e.g. Galaxy I5800).
Click to expand...
Click to collapse
0.901
Updated the webkit patcher to 2.2B.
Reversed the default font to the old one due to its wider compatibility.
Fixed patching JVT rom for the I9000.
Using a cleaned up reworked script and a new libandroid_runtime.so patcher by brightidea.
Click to expand...
Click to collapse
0.813
Updated the webkit patcher to 1.5B.
Updated the default font.
Fixed the “dancing letters” problem in WhatsApp.
Compiled libicuuc-arabic.so with armv5te which should support more devices[/B]
Click to expand...
Click to collapse
0.812
Updated baksmali and smali to version 1.2.8.
Updated the webkit patcher to 0.7B (more devices are supported now)
Click to expand...
Click to collapse
0.811
Updated baksmali and smali to version 1.2.7.
Added the arabic shaping libwebcore patcher by brightidea (v 0.3 Beta)
Renamed folders to facilitate the process for you guys: you only have to pull files and dump them in the input folder. All generated files will be placed in the output folder.
Click to expand...
Click to collapse
0.804
Fixed numbers getting reversed in some cases.
Click to expand...
Click to collapse
0.803
Updated Baksmali and Smali to the latest version.
The clockworkmod recovery file is modified (hopefully will work on more roms now)
Click to expand...
Click to collapse
0.802
Updated the arabization files to include the latest CM7 fixes (Alignment, text width and many more).
Unified Gingerbread and Froyo patches by moving TextUtils.java’s methods into a new class.
Fixed garbled text appearing in Gmail’s titles in some ROMs
Click to expand...
Click to collapse
0.801
Using latest CyanogenMod 7 patch for Arabic. Reference
HTC Gingerbread Sense ROMs will now go through a separate patching process for Layout.smali. This patch has been borrowed from the bright minds that created HebFix_0.91
Click to expand...
Click to collapse
0.800
Space after LAMALEF is fixed.
This is a port of the latest arabic patch for CM7. It should work globally on all devices > 2.1. This is also why support for arabizing CM7 is dropped in this patch.
Scrolling and viewing arabic content should be much faster because the new patch relies on c++ to do this instead of Java
Now patch produces a Clockworkmod recovery file for ease of use
Added an arabic font that facilitates reading Arabic text
Click to expand...
Click to collapse
0.789
Fixed a Force Close in CM7 due to missing Styles.smali
No longer using ICU4J to shape text. This could also possibly fix shaping for Persian text. Instead, we use Aziz Huss’s ArabicShaper class with some modifications of my own.
Click to expand...
Click to collapse
0.788
Fixed a minor Force Close issue in gTalk with Gingerbread Sense UI.
Click to expand...
Click to collapse
0.787
Added patch files for Gingerbread Sense UI.
Removed clockworkmod recovery generated file due to incompatibility with all systems
Click to expand...
Click to collapse
0.786
Added patch files for CyanogenMod 6.
Added patch files for Gingerbread.
Recovery flashable update files are generated alongside the framework.
Click to expand...
Click to collapse
0.785
Added patch files for CyanogenMod 7.
Added libwebcore.so (used to shape text in Browser and Gmail) to subfolder libwebcore. You’ll need to place them in /system/lib on your device.
Click to expand...
Click to collapse
0.784
Space after LAMALEF is back. The previous patch caused problems in some apps.
Fixed the RTL alignment in google talk.
Arabic shaping works correctly in Twitter.
Click to expand...
Click to collapse
0.781
Space after LAMALEF is gone. Strings are resized to accommodate this change.
Change to Y6b’s source code to reflect on these new changes.
ArabicShaper function only shapes requested width instead of the whole string. This should speed things up considerably.
Some corrections to y6b’s source code
Added subfolder “Aljazeera fonts” for those who want to replace their phone’s fonts.
Clicking on commands.exe will not produce all these prompts anymore. Minimized them to save your precious time.
Click to expand...
Click to collapse

Download:
0.907 - http://www.mediafire.com/?ubsh844gjtjcaba
0.906 - http://www.mediafire.com/?4hisiqyjq7n3n1f
0.905 - http://www.multiupload.com/624XH5H7YO
0.902 - http://www.multiupload.com/70TG5L3XIQ
0.901 - http://www.multiupload.com/KZH2N0ASEZ
0.813 - http://www.multiupload.com/2DDS2B35HI
0.812 - http://www.multiupload.com/CULDPEQACA
0.811 - http://www.multiupload.com/Y1EOQYOJ6B
0.804 - http://www.multiupload.com/TUQLR9TQ1M
0.803 - http://www.multiupload.com/JRF6SPOIFS
0.802 - http://www.multiupload.com/OCH233RPK8
0.801 - http://www.multiupload.com/31A9AOAG3A
0.800 - http://www.multiupload.com/ROGWC6G0Q2
0.789 - http://www.multiupload.com/868WFGNER6
0.788 - http://www.multiupload.com/4KXZF81IVB
0.787 - http://www.multiupload.com/P8BYJQEZQ0
0.786 - http://www.multiupload.com/C4J0VJPLX2
0.785 - http://www.multiupload.com/V98TYUHUO1
0.784 - http://www.multiupload.com/BAU681Q6AZ
0.781 - http://www.multiupload.com/RONE05PCE7
0.76 - http://www.multiupload.com/WUUDZK9ITQ
Click to expand...
Click to collapse

Rom's Patches:
Creed's Rom v2.0
Andro-ID 3.3
Chocobread
FITDROID 3.2
FITDROID V3.1
FITDROID V3
Creed's ROM 1.6
Creed's ROM 1.5

hi there
thank you for the patch. it works fine. however the font is err... i don't know, i have difficulties to read it. the markings are a bit off. the space between lines is also too tight so some markings are overlapping
ohh... i'm using MyTouch 4G aka HTC Glacier with EnergyROM

ayamjago said:
hi there
thank you for the patch. it works fine. however the font is err... i don't know, i have difficulties to read it. the markings are a bit off. the space between lines is also too tight so some markings are overlapping
ohh... i'm using MyTouch 4G aka HTC Glacier with EnergyROM
Click to expand...
Click to collapse
there is a sub-folder named fonts,... try to put them on the systems/fonts folder and reboot
backup ur device fonts before replacing them "just in case "

I want to confirm that this method worked on two ROMs for my Samsung Galaxy S2 Epic 4G Touch (for Sprint).
Thanks a lot...

ahmadshawki said:
I want to confirm that this method worked on two ROMs for my Samsung Galaxy S2 Epic 4G Touch (for Sprint).
Thanks a lot...
Click to expand...
Click to collapse
The coder [madmack]:
"This should work with all Android phones supporting Android Froyo or Gingerbread with the exception of MIUI ROMs as they are closed source and I can’t work with that."
Click to expand...
Click to collapse
Enjoy the Arabic Support

Can u make it for Chocobread??

aya.yaya said:
Can u make it for Chocobread??
Click to expand...
Click to collapse
as soon as i go home cuz i have a limited bandwidth here and need to download the rom 1st
or u can just upload the
/system/framework/framework.jar
/system/lib/libwebcore.so
/system/lib/libandroid_runtime.so
and i will make it 4 u

Gendows said:
as soon as i go home cuz i have a limited bandwidth here and need to download the rom 1st
or u can just upload the
/system/framework/framework.jar
/system/lib/libwebcore.so
/system/lib/libandroid_runtime.so
and i will make it 4 u
Click to expand...
Click to collapse
Wow.. very thank you brad...
this is file you need
http://dl.dropbox.com/u/56584844/For_RTL_ChocoBread.rar
waiting 4 it

Thank you! I was searching for this dude..

aya.yaya said:
Wow.. very thank you brad...
this is file you need
http://dl.dropbox.com/u/56584844/For_RTL_ChocoBread.rar
waiting 4 it
Click to expand...
Click to collapse
here is ur patch link,... will add it to the patches list to
sorry for being late
Download

Feras.Rehman said:
Thank you! I was searching for this dude..
Click to expand...
Click to collapse
good to hear that,... now i think that all ur custom roms will support arabic

Thanks 4 patch bro
Sent from my GT-S5670 using xda premium

aya.yaya said:
Thanks 4 patch bro
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
u r welcome,....

I've managed to create the zip file. But, CWM on my HTC (http://forum.xda-developers.com/showthread.php?t=1432259) refused to flash it. It seems there is problem with sign. Would you create signed zip based on my HTC files. Or, would you tell me how to sign the zip?
Actually, the original creator of the custom ROM has created one, but it does not based on the undoscript. His zip is not working after undo script is applied. So the provided files are from custom ROM + undo script.
Thanks

sancho21 said:
I've managed to create the zip file. But, CWM on my HTC (http://forum.xda-developers.com/showthread.php?t=1432259) refused to flash it. It seems there is problem with sign. Would you create signed zip based on my HTC files. Or, would you tell me how to sign the zip?
Actually, the original creator of the custom ROM has created one, but it does not based on the undoscript. His zip is not working after undo script is applied. So the provided files are from custom ROM + undo script.
Thanks
Click to expand...
Click to collapse
ok let's see,... there is a "system" folder in the zip,...
so just open any successful flashing zip that u used an put the folder in that zip
but delete it's content first except the meta inf folder
that all what i do after generating the file

Nice. I'll give a try.
Sent from my HTC Wildfire S A510e using XDA App

Please confirm correctness of these steps:
0. cd /tmp/kerja/ex
1. unzip /tmp/kerja/proven_working.zip
2. rm -Rf system
3. unzip -d /tmp/arabic generated_but_rejected_arabic.zip
4. cp -R /tmp/arabic/system .
5. zip -r result.zip *
Sent from my HTC Wildfire S A510e using XDA App

[GUIDE] How to port Stock/GB/CM7/CM9/ICS/CM10/JB Based ROMs [Update: Sept.25.2012]

Code:
/*
* ~ Please READ ME ~
*
* I do not guarantee any successful porting. I am not responsible
* for bricked devices, dead SD cards, or a broken device. [B]YOU[/B] are
* choosing to make these modifications, and if you point the finger
* at me for messing up your device, I will laugh at you. But I will try
* my best to explain all the necessities, so you won't mess up your Device.
*
* ~ END OF AGREEMENT ~
*/
Before we start, let's read the Title of this Guide. Notice it says: based
This means, if you do not have a GB/ICS/JB already compiled for your device, then this Guide is useless for you.
Android Source | Compile GB | Compile ICS | Compile JB ~ Thanks dastin1015 |- Building/Compiling - Durations
Before you a port a ROM, make sure you asked permission from the Developer!
This Guide applies the same principle for porting the following: Sense, Lewa OS, JoyOs, MIUI, LiGux OS, etc...
What you'll need:
WinRAR/7zip
Notepad++ (When developing, always use this)
Android SDK (For Logcatting & DDMS)
Some basic knowledge about Android
If you are on Linux/Unix/BSD use your favorite Archiving Tool & Text Editor.
Notes:
I will be referring to the following:
BASE = The GB/ICS/JB ROM made for your Device only.
PORTED = The ROM you are trying to port from.
BASE and PORTED must be the same CPU. e.g. ARMv7, ARMv6, ARMv5
You must have the same settings in Notepad++ like mine.
Ignore the procedure, if the file or folder is not present!
BASE & PORTED should be the same Android version.
If you are porting a custom GB ROM, then use a GB BASE, the same goes for ICS and JB
Make sure both BASE & PORTED are deodexed (It's hard to port an odexed ROM)
Final ROM is inside PORTED Folder
(Don't get confused! This is a Major change from the previous Guide because this method is a lot faster and easier)
Inside PORTED:​
Remove kernel:
boot.img | zImage | kernel.sin | etc...
Remove the following inside /system:
cameradata
tts
usr
vendor
firmware
modules
wifi
Now you get 2 options:
Delete bin & xbin & lib folder, but keep libandroid_runtime.so inside /system/lib
Keep bin & xbin & lib folder
Explanation:
If PORTED has no tweaks or addons to those folders.
If PORTED has tweaks and addons.
Remove every folder inside /system/etc except:
init.d
permissions
license
Remove the following inside META-INF:
CERT.RSA
CERT.SF
MANIFEST.MF
Remove: META-INF/com/google/android/update-binary​
Inside BASE:​
Move kernel to PORTED:
boot.img | zImage | kernel.sin | etc...
Delete libandroid_runtime.so inside /system/lib
Move the following inside /system to PORTED:
(If prompted, select YES to copy and Replace all)
cameradata
bin
lib
tts
usr
vendor
firmware
modules
wifi
xbin
(If prompted, select YES to copy and Replace all)
Move everything inside /system/etc
To: PORTED's /system/etc
(If prompted, select YES to copy and Replace all)
Move: META-INF/com/google/android/update-binary
To: PORTED's META-INF/com/google/android/
For ICS & Newer:
Move the following inside /system/media to PORTED's media:
LMprec_508.emd
PFFprec_600.emd
build.prop​
Inside PORTED:​Open /system/build.prop
Copy & Replace the following:
ro.modversion
ro.cm.version
ro.config.ringtone
ro.config.notification_sound
ro.config.alarm_alert
ro.config.sms_received_sound
ro.config.sms_delivered_sound
persist.sys.themeId
persist.sys.themePackageName
and anything similar to that, to: BASE's build.prop
For MIUI:
Add & Make sure the following values are like this:
ro.build.id=MIUI
ro.build.display.id=MIUI x.x.x
ro.build.version.incremental=x.x.x
ro.config.ringtone=MI.ogg
For Lewa OS:
Add & Make sure the following values are like this:
ro.build.display.id=LeWa_ROM_DeviceNickname_xx.xx.xx
ro.lewa.version=LeWa_ROM_DeviceNickname_xx.xx.xx
ro.lewa.device=DeviceNickname
ro.lewa.swapper.part_path=PORTED's_Value
ro.lewa.swapper.flash_swappiness=PORTED's_Value
ro.lewa.swapper.sd_swappiness=PORTED's_Value
ro.error.receiver.system.apps=com.lewa.fc
ro.error.receiver.default=com.lewa.fc
Make sure the following is for your Device:
rild.libpath=
rild.libargs=
Inside BASE:​Open /system/build.prop
Highlight from: ro.build.tags=
to: # ADDITIONAL_BUILD_PROPERTIES
Shown in this picture
Copy & Replace that highlighted part to: PORTED's build.prop's highlighted part
Copy everything from: # ADDITIONAL_BUILD_PROPERTIES
To: the end of the file
Paste it to PORTED's build.prop
Shown in this picture
For XPERIA devices:​The whole build.prop is untidy and filled with tweaks and addons.
To edit an XPERIA build.prop you really just need to use your common sense.
Make sure you follow the above and just decide on your own on what to do
For HTC devices (Sense):​The whole build.prop is filled with tweaks, addons and extra libs values.
To edit an HTC build.prop you really just need to use your common sense.
Make sure you follow the above and just decide on your own on what to do ​
updater-script​
Inside BASE:​Move the following, to PORTED:
(If prompted, select YES to copy and Replace all)
META-INF/com/google/android/update-binary
META-INF/com/android/metadata
META-INF/com/android/otacert
Open: META-INF/com/google/android/updater-script
Replace the following values, to PORTED:
mount("xxxxxx");
format("xxxxxx");
retouch_binary
The installation of the kernel (Something like: assert(package_extract_file("boot.img",)
Take note of the added set_perms & set_perm_recursives that PORTED added. Then replace all set_perm and set_perm_recursive from BASE to PORTED. Put back in the noted set_perms & set_perm_recursive you wrote down, to PORTED's updater-script
For ICS & Newer itself:​
If the updater-script in PORTED is modded to have tweaks & addons do the set_perms procedure above
Now use BASE's entire META-INF Folder. Copy it to PORTED
For MIUI v4:​Add the following values to PORTED:
set_perm(0, 0, 06755, "/system/xbin/invoke-as");
set_perm(0, 0, 0755, "/system/lib/liblbesec.so");
For AROMA Installer:​It's actually too hard & time consuming to explain on how to make the script work on your Device when it came from another.
So it's best to use BASE's META-INF folder, rather than try to make the AROMA Installer work on your Device. (Becuase it will be time consuming)​
Porting from a different Manufacturer​
If you are porting from a different manufacturer like, HTC or Sony, you have to check the kernel from them.
Unpack the kernel from PORTED
Unpack your Device's kernel
Open PORTED's init.rc
Replace the BOOTCLASSPATH from PORTED's init.rc to BASE's init.rc
Compare the two files, and addon to your Kernel's init.rc
Packup/Repack your Kernel
Porting Wallpapers | Lockscreen Wallpapers | bootanimation​
Usually you get a wallpaper/bootanimation that doesn't fit your device. Here's a quick tutorial on how to port it to your device.
Download & Install FreeImageConverter then launch it.
For Wallpapers & Lockscreen Wallpapers:​
Click Add Folder... and add the folder were the wallpapers are
Then click Advanced Convert...
Select Exact Size and set the image quality to 100
Set your Width and Height resolutions for your device.
Uncheck Add "Converted by www.freeimageconverter.com"
Select Leave the same file name and leave the Postfix & Prefix empty. Then set your output in a folder.
For bootanimation:​
Extract /system/media/bootanimation.zip OR /data/local/bootanimation.zip OR /system/customize/resource/bootanimation.zip (For Oxygen ROM, the bootanimation is built into the framework-res)
Do the steps above
Move the new resized folder(s) into your bootanimation workspace
Edit the desc.txt to match your device resolutions
Zip the contents ( folder_name desc.txt )
Set compression method to Store
Delete the extracted bootanimation files
Make sure this new bootanimation.zip is in PORTED
Logging & DDMS​
This is very important if your a developer in the Android world. These tools help you debug your device to search for errors or see which processes are running.
Android Debug Bridge (ADB)​Tutorial - How to Logcat
Dalvik Debug Monitor Server (DDMS)​Tutorial from Android
If you want me to help you, don't give me a Logcat from ADB. Instead, give me a screenshot of your DDMS.​
Review
Make sure you did everything inside PORTED first, then work your way up/down to BASE.
Did you replace Kernel?
Is libandroid_runtime.so from PORTED?
Did you edit the updater-script, format & mount values?
Make sure dalvik.vm.heapsize is BASE's value inside build.prop
Make sure build.prop is mostly for your Device
If the Port doesn't boot, try using your own META-INF folder. But backup the previous
Sources
[GUIDE] How to port MIUI v4 to your Device - proxuser
[GUIDE] How to port Stock/GB/CM7/CM9/ICS/CM10/JB Based ROMs - Peteragent5
Credits & Thanks to
proxuser
nims11
dhk.-
Lens_flare
SpaceCaker
fundoozzz
Delanoister
TeamCooper
Happy porting! :laugh:

Frequently Asked Questions
Q: How do you port a higher CPU ROM to my lower CPU device?
A: P.M me or any big-name developers. You must already know what to do. The person you P.M will give you extra info...
Q: Is it possible to port a lower CPU ROM to my higher CPU device?
A: I think it'll work (But why would you do this). If it doesn't boot try changing the DPI values in the build.prop
Q: How do I make a bigger DPI ROM work on my smaller DPI device?
A: Resize all PNGs in every app & framework-res using Android Resizer Tool
Q: Can I Port a smaller DPI device to my device?
A: Yes. It probably won't run & it wouldn't look good if you did. The icons would be small or if you resized it, the icons would be blurry.​

You say that we can use any ROM as BASE but you don't specify what to use as PORT.
Can you please clarify that?

there is no /data folder in cyanogen mod from galaxy mini.. wat to do now??
i m porting cyano from mini to galaxy y

Peteragent5 your arm7 port rom problem solve from this way?

FeralFire said:
You say that we can use any ROM as BASE but you don't specify what to use as PORT.
Can you please clarify that?
Click to expand...
Click to collapse
You can port any Rom as long as it's based on CM7/GB/Stock Rom, the same CPU (Armv6, Armv7, Armv5) as your BASE, and it's best to port a Rom from the same manufacturer, if not, you can still do it, just change BOOTCLASSPATH
hell_lock said:
there is no /data folder in cyanogen mod from galaxy mini.. wat to do now??
i m porting cyano from mini to galaxy y
Click to expand...
Click to collapse
If there is no data then it's fine to not include it
cips gokhle said:
Peteragent5 your arm7 port rom problem solve from this way?
Click to expand...
Click to collapse
Lol. No not yet

I want to port CM7 from LG O2X to Samsung Galaxy R (They both have the same CPU- Tegra 2).
Can I use the official LG O2X CM7 ROM and the stock Galaxy R ROM?
Or should I use the Galaxy S2 CM7 ROM?

Can we port Sense to Gio using this guide?

I have a galaxy tab p1010. That have ARM8.
This means that wont work?

Peteragent5 said:
Now open Notepad++ and open the build.prop in PORTED
Also open the build.prop in BASE, so now you have them side by side in the tabs
In PORTED, edit the build.prop to match with your device!
NOW This is very important!
Your
ro.build.description=
and
ro.build.fingerprint=
must be the same same as the build.prop in BASE!
If not, your Rom will not boot!
Save the Build.prop in PORTED and close NotePad++
Click to expand...
Click to collapse
Why are we editing the build.prop in the PORT, shouldn't we edit it in BASE?

I finished this and the ROM won't boot.
I tried the Base as a Sense 3.0 (2.3.4 Gingerbread ROM)
porting a Sense 4.0 (4.0.3 IceCreamSandwich ROM)

FeralFire said:
I want to port CM7 from LG O2X to Samsung Galaxy R (They both have the same CPU- Tegra 2).
Can I use the official LG O2X CM7 ROM and the stock Galaxy R ROM?
Or should I use the Galaxy S2 CM7 ROM?
Click to expand...
Click to collapse
They must both be CM7
ulasates said:
Can we port Sense to Gio using this guide?
Click to expand...
Click to collapse
Sense is quite hard, to be honest. I'm still trying to figure out how I should do it
samcortez said:
I have a galaxy tab p1010. That have ARM8.
This means that wont work?
Click to expand...
Click to collapse
As long as both PORTED and BASE is the same CPU, this guide will work.
FeralFire said:
Why are we editing the build.prop in the PORT, shouldn't we edit it in BASE?
Click to expand...
Click to collapse
Because. The build.prop in PORTED has more values than than the one in BASE. So if we use BASE's Build.prop, you'd have to copy over everything that was in the PORTED (The extra values, like tweaks and some more stuff)

Adjust said:
I finished this and the ROM won't boot.
I tried the Base as a Sense 3.0 (2.3.4 Gingerbread ROM)
porting a Sense 4.0 (4.0.3 IceCreamSandwich ROM)
Click to expand...
Click to collapse
Sense is hard to port is you are from a different Manufacturer.
But if you are not, this is what you need to do:
Your BASE needs to be an ICS Base in order to port the Sense 4.0

Peteragent5 said:
Sense is hard to port is you are from a different Manufacturer.
But if you are not, this is what you need to do:
Your BASE needs to be an ICS Base in order to port the Sense 4.0
Click to expand...
Click to collapse
I have a Sense 3.6 4.0.3 Base.
or Should I use a pure 4.0.3 Base?
Which is better?

Adjust said:
I have a Sense 3.6 4.0.3 Base.
or Should I use a pure 4.0.3 Base?
Which is better?
Click to expand...
Click to collapse
Try sense 4.0.3 first then pure
unwritten sentance

spacecaker said:
Try sense 4.0.3 first then pure
unwritten sentance
Click to expand...
Click to collapse
I want a 100% answer if possible don't have time to waste.
Thanks for posting though.

Adjust said:
I want a 100% answer if possible don't have time to waste.
Thanks for posting though.
Click to expand...
Click to collapse
You should use 4.0.3 as base

Peteragent5 said:
You should use 4.0.3 as base
Click to expand...
Click to collapse
Sense 3.6 (4.0.3) base?
or Pure 4.0.3 base.
Woulden't using Sense 3.6 as a base be good since it's Sense and ICS so is Sense 4.0

Peteragent5 said:
Because. The build.prop in PORTED has more values than than the one in BASE. So if we use BASE's Build.prop, you'd have to copy over everything that was in the PORTED (The extra values, like tweaks and some more stuff)
Click to expand...
Click to collapse
Then when you finish your edit on ported you should replace build.prop from PORTED to BASE, isnt¿?
BTW excellent guide!

Adjust said:
Sense 3.6 (4.0.3) base?
or Pure 4.0.3 base.
Woulden't using Sense 3.6 as a base be good since it's Sense and ICS so is Sense 4.0
Click to expand...
Click to collapse
Yup. Sense 3.6. As long as both BASE and PORTED are same (4.0.3)
ocovarr112 said:
Then when you finish your edit on ported you should replace build.prop from PORTED to BASE, isnt¿?
BTW excellent guide!
Click to expand...
Click to collapse
Yup when you finished build.prop in PORTED, you copy that build.prop into BASE
And your final Rom is BASE

[Q] Porting Flyme OS to Sensation, radio not working

Hi,
I'm trying to port Flyme OS to Sensation using http://forum.xda-developers.com/showthread.php?t=1908008 guide. I'm using latest CM9 as base ROM. I tried to port using nexus S and Xperia ray Flyme OS ports. I've to replace libandroid_runtime.so in order to make ported ROM boot.
The ROM boots fine and WiFi works but Radio is not working. I tried updating framework.jar with Ril*.smali and QualcommShared*.smali files. But that did not resolve the issue. (Even replacing com\android\internal\telephony folder completely could not make radio work).
So it looks like replacing libandroid_runtime.so is probably causing Radio to not work .
I'm attaching radio logcat if that could be useful. It will be great if someone can help .

Got it working .

webharsh said:
Got it working .
Click to expand...
Click to collapse
How?
xpirt

xpirt said:
How?
xpirt
Click to expand...
Click to collapse
Its been a while since I posted that. I think following was the solution -
Decompile framework-res.apk
Go to \framework-res\res\values\bools.xml and change change <bool name="skip_restoring_network_selection">true</bool> to false
See: http://forum.xda-developers.com/showthread.php?t=1908008
Btw, I abandoned this because I could not fix graphical glitches for which I need to recompile some libraries. Also it became irrelevant once Jellybean was released.

[XT1033][Trying]One Sim Working On All Roms [Implementing EPRJ RIL]

Was looking around how to make atleast one sim working on all roms and then i saw this thread
http://forum.xda-developers.com/showthread.php?t=2496075
Turns out the problem he mentioned was the same as every rom(except 2 made for xt1033) on xt1033
1.Rom taking time to set up network
2.Not able to receive call even when the ring is going.
Happened with me on every rom except with Paranoid android and Cm11 for xt1033
So what to do?
In the thread mentioned above are the simple steps for doing it
(Now please read the full thread before reading down)
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!
I wanted pacrom to work and there was no
X3RIL.smali so i used RIL.smali from the cm11 made doubleprank's telephony-common.jar
On decompiling there was also an org folder so i pasted that as well
Done all the steps and i got a phone fc
Now what should i do ahead
Anyway i have attached all the telephony.jars of all roms i have for testing

atb !!

@dhacker @Doublepranks
Sent from my MotoG using Tapatalk

What exactly do you want? I mean if PACROM is all you want i will be more than glad to build it for you with the minimal hassle of installing over the en.GB firmware.

not that
Doublepranks said:
What exactly do you want? I mean if PACROM is all you want i will be more than glad to build it for you with the minimal hassle of installing over the en.GB firmware.
Click to expand...
Click to collapse
pacrom was just an example
I was just looking what else could be done instead of building?(because there are so may roms) but i sort of gave up and will build now if i figure it out

rr46000 said:
pacrom was just an example
I was just looking what else could be done instead of building?(because there are so may roms) but i sort of gave up and will build now if i figure it out
Click to expand...
Click to collapse
Take a look at sources on my thread, you'll get exactly what you need.
Commit MessagePermalink
p880: Solve IMEI and mobile data problems. Implement baseband recovery.
I don't like the old RILJ, at all. It is unstable and contains just the
necessary code to make RIL to work.
In the old one, there wasn't any baseband recovery management and no quirks
at all.
EternityProject's version instead, contains baseband recovery, that solves
the ugly and bad problem that happens when the radio goes to UNAVAILABLE
state by restarting it completely, avoiding to lose calls and SMS'es.
Also, it contains rawip insmod/rmmod that, on some modern kernels, like
3.4.37 by EternityProject, isn't working like expected.
It also has a better and proper implementation of
RIL_UNSOL_LGE_SELECTED_SPEECH_CODEC management. The reply has to be
an integer value, so that lge-ril.so will handle that correctly.
Moreover, RIL_UNSOL_LGE_PBREADY was not implemented at all and it was
needed to tell the radio to go into AT READY state.
The reason why we need this is because this will actually allow us to
use modern kernels and to (in future) probably get rid of some proprietary
libraries to switch, instead, to opensource code.
Click to expand...
Click to collapse
That's probably a very good reason to marge this into CM, i wonder why it never happened.

Doublepranks said:
Take a look at sources on my thread, you'll get exactly what you need.
Click to expand...
Click to collapse
check ur pm

Awesome!
rr46000 said:
Was looking around how to make atleast one sim working on all roms and then i saw this thread
http://forum.xda-developers.com/showthread.php?t=2496075
Turns out the problem he mentioned was the same as every rom(except 2 made for xt1033) on xt1033
1.Rom taking time to set up network
2.Not able to receive call even when the ring is going.
Happened with me on every rom except with Paranoid android and Cm11 for xt1033
Click to expand...
Click to collapse
Awesome! LOVE U BRO! YOU RESPONDED VERY QUICKLY!!! I'M REAL HAPPY!:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::highfive::highfive::highfive::laugh::laugh::laugh::laugh:
---------- Post added at 10:35 AM ---------- Previous post was at 10:29 AM ----------
rr46000 said:
Now what should i do ahead
Anyway i have attached all the telephony.jars of all roms i have for testing
Click to expand...
Click to collapse
Bro, I ques, the telephony.jar of pac rom that you attached, is fully gone through all the processes that u mentioned here????
Answer me cause I don't have patience and I know you're online now!

Whoa!
[email protected] said:
Awesome! LOVE U BRO! YOU RESPONDED VERY QUICKLY!!! I'M REAL HAPPY!:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::highfive::highfive::highfive::laugh::laugh::laugh::laugh:
---------- Post added at 10:35 AM ---------- Previous post was at 10:29 AM ----------
Bro, I ques, the telephony.jar of pac rom that you attached, is fully gone through all the processes that u mentioned here????
Answer me cause I don't have patience and I know you're online now!
Click to expand...
Click to collapse
Bro chill out!
See the heading it is saying trying
The attached jars are the original ones(not edited)
Currently the procedure is not working
I thought of sharing it so the people with knowledge in thus could discuss then we could finally make sim available
But that didn't work out as no one know what to do ahead in this procedure
The only solution now is to build the rom with xt1033 which i am trying ans as i earlier told you if i figure it out ,i will share it

Doesn't work
rr46000 said:
Was looking around how to make atleast one sim working on all roms and then i saw this thread
http://forum.xda-developers.com/showthread.php?t=2496075
Turns out the problem he mentioned was the same as every rom(except 2 made for xt1033) on xt1033
1.Rom taking time to set up network
2.Not able to receive call even when the ring is going.
Click to expand...
Click to collapse
Doesn't work on PACman ROM. Neither on others. CM AND PA Both already have it working.
I'm really disappointed today as my excitement is totally shattered.
---------- Post added at 11:00 AM ---------- Previous post was at 10:57 AM ----------
rr46000 said:
Bro chill out!
See the heading it is saying trying
The attached jars are the original ones(not edited)
Currently the procedure is not working
I thought of sharing it so the people with knowledge in thus could discuss then we could finally make sim available
But that didn't work out as no one know what to do ahead in this procedure
The only solution now is to build the rom with xt1033 which i am trying ans as i earlier told you if i figure it out ,i will share it
Click to expand...
Click to collapse
Alright brother!
ALL THE BEST! EVEN I'M WORKING OVER PACman rom. I'm new to develop aosp based roms. Iused todevelop samsung galaxy y stock roms as it only had cm7.2 which was damn old. I'll have to learn a lot.

Oic
[email protected] said:
Doesn't work on PACman ROM. Neither on others. CM AND PA Both already have it working.
I'm really disappointed today as my excitement is totally shattered.
---------- Post added at 11:00 AM ---------- Previous post was at 10:57 AM ----------
Alright brother!
ALL THE BEST! EVEN I'M WORKING OVER PACman rom. I'm new to develop aosp based roms. Iused todevelop samsung galaxy y stock roms as it only had cm7.2 which was damn old. I'll have to learn a lot.
Click to expand...
Click to collapse
lets divide our work
I'll work on mokee open source and u on pac
fine?

Lets see.
rr46000 said:
lets divide our work
I'll work on mokee open source and u on pac
fine?
Click to expand...
Click to collapse
I've recently started ****STUDYING**** on how to develop a PAC ROM. I wrote before that I had only worked on Samsung official ROM modding and stuff. But sounds a good idea. We'll double team this PAC ROM. If doublepranks could help us in this then it would be better. Give me 2 days time or you yourself can help me out on how to start up with this stuff.
It would be better if you could help me in somewhat teaching me this stuff. I've already read some stuff on PAC's official website.
E-Mail me at my username - (Check my profile name)....
Rgds
Yash
By the way, what's mokee? I'm a fast learner especially in dev stuff. I'll surely catch-up with you.It would be good if you could help me out.
Lets open a DEV-DB page on this.:highfive:

bro cybojenix had made a patch for cm11 in moto e development , using it he enabled single sim working in dual sim mobile
have a look at this thread http://forum.xda-developers.com/showpost.php?p=53747040&postcount=3

[CM7 Roms][Tool] Auto Porter

Hey Guys I have A surprise for you all Its Rom Auto Porter Tool For Our Device IT Is a Flashable Zip , It will Port any cm7(tested)-cm9(waiting) rom with same screen Resuliotion
With It You Can forget to ask people to port u why dont u do it ur self
Steps
Code:
1-Flash The rom You Want
2- MAke sure all mounts IS alright
3-Flash The Zip
4-Flash The Kernel U want Mightn't boot if u didnt do so
Credits
bieltv.3 and BroadcomCM
myaservip
Status
Testing - Continusly Updated So Please Keep Up with download link .
-last download link added( 30-march Morninig):
-Added More Libs
-New update script
Download Auto Porter
NOTE: THAT WILL REMOVE SOME TWEAKS FROM THE PORT

SS Please

GSculerlor said:
SS Please
Click to expand...
Click to collapse
Its cwm file

a lil more explaination where cool..

I want some one to help me add aroma for multy device selection
Thread soon updated
Imade it in a hurry

Brb got to study some now;(

-CALIBAN666- said:
a lil more explaination where cool..
Click to expand...
Click to collapse
What u mean!?

myaservip said:
What u mean!?
Click to expand...
Click to collapse
He means explain more about your tool.So others may have good observation at your thread.

make sure you delete boot.img from the rom zip if it has one before flashing any rom for another device - I'll have a look at your updater script later but I assume it just replaces all the lib files and so on
you might have to make build.prop changes too
there are rom porter tools out there that can port any rom from any device (although you do still have to make some manual changes)
I assume this tool will only work if the following condidtions are met although correct me if im wrong
1 - its from the same manufactuer ie samsung
2 - its from the same processor type ie armv6

marcussmith2626 said:
make sure you delete boot.img from the rom zip if it has one before flashing any rom for another device - I'll have a look at your updater script later but I assume it just replaces all the lib files and so on
you might have to make build.prop changes too
Click to expand...
Click to collapse
Build prop Already Got from Base
Will add Boot img in Incoming Update Thanks for Idea

san122 said:
He means explain more about your tool.So others may have good observation at your thread.
Click to expand...
Click to collapse
-CALIBAN666- said:
a lil more explaination where cool..
Click to expand...
Click to collapse
Thread Updated all Info required Added
Next Update I Will merge (tassve-Totoro-copreve )into one zip but iam learning to add aroma Now
Sir Rhevaldo Could u help?

marcussmith2626 said:
make sure you delete boot.img from the rom zip if it has one before flashing any rom for another device - I'll have a look at your updater script later but I assume it just replaces all the lib files and so on
you might have to make build.prop changes too
there are rom porter tools out there that can port any rom from any device (although you do still have to make some manual changes)
I assume this tool will only work if the following condidtions are met although correct me if im wrong
1 - its from the same manufactuer ie samsung
2 - its from the same processor type ie armv6
Click to expand...
Click to collapse
Mine Is 100% Automated

san122 said:
He means explain more about your tool.So others may have good observation at your thread.
Click to expand...
Click to collapse
I still have to say iam not good at talking

Well I prefer manual porting it is simple and not so time taking.Well still a good job! :thumbup::thumbup::thumbup:

aniket.lamba said:
Well I prefer manual porting it is simple and not so time taking.Well still a good job! :thumbup::thumbup::thumbup:
Click to expand...
Click to collapse
All people can port Now

realy?this works?i have never see before,what about sgy duos?

-CALIBAN666- said:
realy?this works?i have never see before,what about sgy duos?
Click to expand...
Click to collapse
Gimme Your Base I will make u zip

So, the main feature of this tool is porting based cm ROM ? What about the bugs ?

GSculerlor said:
So, the main feature of this tool is porting based cm ROM ? What about the bugs ?
Click to expand...
Click to collapse
No Bugs but some tweeks might be removed

myaservip said:
No Bugs but some tweeks might be removed
Click to expand...
Click to collapse
Which CM version support ?
Sent from my GT-S5360 using xda app-developers app