Database Develop

[FIX][CWM] Incorrect MAC address on ICS ROMs [21 Apr]

Here's a flashable fix if you're getting a different MAC address on ICS when compared to GB.
It is caused by a missing symlink causing it to use a wrong firmware file.
update-ICS-MAC-fix.zip (488 KB)
Only tested on ROMs based on stock firmware.

just a question.... y are there duplicates of wifi firmware in etc/firmware and /ticonnectivity?
I would like to know which is the correct path that wifi will look for the firmware?

Correct path is \system\etc\firmware\ti-connectivity\

All xperia phones got this issue or partial to only arc
which config file defines firmware path I want to check for neo_v

what difference does it make if you have the wrong MAC Version being displayed?

@yacloo all of them, for example to fix it I used Arc file on NeoV
@SS4Serebii if your network checks mac address you will not be able to connect to your network and maybe something more

is this needed on a CM9 ROM ? and will this work on said ROM ?

SS4Serebii said:
what difference does it make if you have the wrong MAC Version being displayed?
Click to expand...
Click to collapse
As Zdune stated. Also, let's say there are 2 arcs with the incorrect MAC address issue (they have the same address), only one of them will be able to connect to a WiFi hotspot.
Punkid said:
is this needed on a CM9 ROM ? and will this work on said ROM ?
Click to expand...
Click to collapse
I cannot guarantee but CM9 should already have correct address.

Thanks Zdune and doomed!

I checked my mac address same as like on GB rom didn't changed
weird all stock roms aren't same
on my stock ics rom wifi firmware files are on \system\etc\firmware\ti-connectivity\
there is no wifi firmware \system\etc\firmware\
on dmesg firmware loading is ok
should I install this fix

If it didn't change then there's no need to use this fix.

I'm currently using ICS CM9, and i didn't see any of said item on the path given..

[Patch] Fix Network Error Network Selection

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!

[GUIDE]How to Port ROMS from same resolutions phones- Easy way

Hi.
If someone have improvement advices for this thread PM me.
This won't work for sense ir smth similar.
I'm not responsible for bricked(or smth similar) devices cause of ROMS ported by this method.
I don't know if this works for non-aosp/cm based ROMS. You may need to do some more things to get it working.
Try to use the same android version for both ROMS For 4.2.2 use Cm For 4.1.2 use Stock ROM.
You won't have a compatible source code. This means you can't update the ROM through syncing and recompiling. But you won't need a Linux distro fot this Method.
Actually its very easy.
firstly follow this tutorial: http://www.fesilo.com/forum/android/guides/113-guide-guide-to-port-roms-fast-and-easy to get a booting ROM
then download this Tool -> http://www.virtuous-ten-studio.com/ it makes de/re-compiling very easy.
now you just have to fix those anoying bugs
to fix Phone.apk FC.
Be sure to put in the submenu smali API level to Android 4.2.2(in VTS) and tick use smali debug output and in the submenu build tick use old signature
Decompile telephony-common.jar from both ROMS.
Copy the X3RIL.smali found in /com/android/internal/telephony from the .jar of your base ROM (cm 10.1,stock rom) to the .jar of the ROM you're trying to port.
Recompile and replace the one within your old one from HOX ROM.
Decompile framework-res.apk from both ROMS.
open /res/values/arrays.xml
press Control+f to use the search function.
enter auto
copy the arrays config_autoBrightnessLevels,config_autoBrightnessLcdBacklightValues,config_autoBrightnessButtonBacklightValues,config_autoBrightnessKeyboardBacklightValues to the .xml off your ROM and overwrite the old ones.
then copy and overwrite power_profile.xml and storage_list from your base ROM to the ROM your trying to port.
Recompile and replace the one within your old one from HOX ROM.
actually this was the magic.
I hope I forgot nothing. Please Excuse me If I did. It's half past 23 here and I had a very exhausting Weekend.
I will update this thread in a few days to make it more userfriendly
You can PM me if you have Questions.
BIG THANKS TO SNXO FOR GIVING ME THE KNOW-HOW TO FIX BIG ISSUES.
and sorry for my English
reagards tobixdev

Thanks..
Very Interesting and useful..
Infact i find some guide simple to try...
Good Job!

Very nice Tobi good job :thumbsup:
Hopefully that gives power to the people for making some good Roms and Programms for us. It isn't that difficult to do just a little bit reading and then learning by doing.
Best regards SnXo
Notice that will work with every rom. The easy way is snap from HOX but you can choose Roms from others too... To keep it iesy you should have the same resolution and Androidversion nothing more... That's it!
Maybe a admin can make this as sticky that would be nice
Sent from my LG-P880 using XDA Premium HD app

SnXo said:
Very nice Tobi good job :thumbsup:
Hopefully that gives power to the people for making some good Roms and Programms for us. It isn't that difficult to do just a little bit reading and then learning by doing.
Best regards SnXo
Notice that will work with every rom. The easy way is snap from HOX but you can choose Roms from others too... To keep it iesy you should have the same resolution and Androidversion nothing more... That's it!
Maybe a admin can make this as sticky that would be nice
Sent from my LG-P880 using XDA Premium HD app
Click to expand...
Click to collapse
thanks
anyone tried yet ?
Sent from my LG-P880 using xda app-developers app

tobixdev said:
thanks
anyone tried yet ?
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
I tried a while ago with this rom: http://forum.xda-developers.com/showthread.php?t=1562603.
The end result was a bootloop. I will maybe try to do it again when I have more time.

this doesn't work with sense without additional work.
Sent from my LG-P880 using xda app-developers app

tobixdev said:
Hi.
If someone have improvement advices for this thread PM me.
This won't work for sense ir smth similar.
I'm not responsible for bricked(or smth similar) devices cause of ROMS ported by this method.
I don't know if this works for non-aosp/cm based ROMS. You may need to do some more things to get it working.
Try to use the same android version for both ROMS For 4.2.2 use Cm For 4.1.2 use Stock ROM.
You won't have a compatible source code. This means you can't update the ROM through syncing and recompiling. But you won't need a Linux distro fot this Method.
Actually its very easy.
firstly follow this tutorial: http://www.fesilo.com/forum/android/guides/113-guide-guide-to-port-roms-fast-and-easy to get a booting ROM
then download this Tool -> http://www.virtuous-ten-studio.com/ it makes de/re-compiling very easy.
now you just have to fix those anoying bugs
to fix Phone.apk FC.
Be sure to put in the submenu smali API level to Android 4.2.2(in VTS) and tick use smali debug output and in the submenu build tick use old signature
Decompile telephony-common.jar from both ROMS.
Copy the X3RIL.smali found in /com/android/internal/telephony from the .jar of your base ROM (cm 10.1,stock rom) to the .jar of the ROM you're trying to port.
Recompile and replace the one within your old one from HOX ROM.
Decompile framework-res.apk from both ROMS.
open /res/values/arrays.xml
press Control+f to use the search function.
enter auto
copy the arrays config_autoBrightnessLevels,config_autoBrightnessLcdBacklightValues,config_autoBrightnessButtonBacklightValues,config_autoBrightnessKeyboardBacklightValues to the .xml off your ROM and overwrite the old ones.
then copy and overwrite power_profile.xml and storage_list from your base ROM to the ROM your trying to port.
Recompile and replace the one within your old one from HOX ROM.
actually this was the magic.
I hope I forgot nothing. Please Excuse me If I did. It's half past 23 here and I had a very exhausting Weekend.
I will update this thread in a few days to make it more userfriendly
You can PM me if you have Questions.
BIG THANKS TO SNXO FOR GIVING ME THE KNOW-HOW TO FIX BIG ISSUES.
and sorry for my English
reagards tobixdev
Click to expand...
Click to collapse
ths very much

section mismatch in android 2.3 v20s kernel

I am trying to compile android 2.3 v20s kernel and it is giving me 18 mismatch section ...I sorted out first three.....but I am not expecting the other 15.....has any one faced this.......I have use arm-eabi -4.4.3 and 4.4.0 and also 4.6 ...but no change.....
I know there are dev's who has successfully compiled it.....can any one tell me whether they saw so many mismatches ....because it is original source from lg......
I did not face these many mismatch or i think there were none during 4.0.4 compile.....
I know they can be fixed by putting of adding/removing __init etc but i am not expecting them
I have attached the build log ...

You can´t complete the compile ? Check if its complete, because if you are getting something like:
Code:
"WARNING: modpost: Found X section mismatch(es)."
Thats just a adice/warning and the compelition should be fine.

Duarte777 said:
You can´t complete the compile ? Check if its complete, because if you are getting something like:
Code:
"WARNING: modpost: Found X section mismatch(es)."
Thats just a adice/warning and the compelition should be fine.
Click to expand...
Click to collapse
They are just warnings....The build is complete
...But i think section mismatches are bad...and these are too many....
Sent from my LG-P970 using xda app-developers app

Duarte777 said:
You can´t complete the compile ? Check if its complete, because if you are getting something like:
Code:
"WARNING: modpost: Found X section mismatch(es)."
Thats just a adice/warning and the compelition should be fine.
Click to expand...
Click to collapse
Also the lines where mismatch is coming ...the code is same in 4.0.4 but they don't give warnings ...I used 4.6 for 2.3 also but same ....
Are there any compiler flags to be set in makefile which can take care of these.....
Sent from my LG-P970 using xda app-developers app

Can any more dev's put some light on this....
Sent from my LG-P970 using xda app-developers app

I downloaded arm-linux-androideabi-4.6 from https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/
and then only got one warning which I fixed and no warnings now.....
but if i use arm-eabi-4.6 https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/
or any arm-eabi- version then i get 14 mismatch ,,,,,,
AFAIK arm-eabi- is used to build kernels and androideabi is used to build android layer.......but the later also builds kernel and i don't get any warnings now.......
Also found one reference where arm-linux-androideab- is used to build nexus S kernel.....
http://glandium.org/blog/?p=2214
So is it safe to use kernel built by arm-linux-androideab-

I see there is no response .But that is OK,as I have fixed all the section mismatches .The issue was in LG's code..and now compiled with arm-eabi-4.6 with zero section mismatch errors....I will try the kernel after applying rmcc patch ..maybe this weekend.

got the kernel booting
see below post for info
http://forum.xda-developers.com/showpost.php?p=52409264&postcount=13
https://github.com/rajeshmk2011/lg_p970_gingerbreadkernel.git

[PATCH][TX][DEV]kexec hardboot port - dual-boot possible

!!!!!! NOT FULLY TESTED !!!!!!!
This patch is based on Tasssadar's hardboot patch for mako. And I borrowed some code (hardboot page address usage) from alvinhochun's Xperia M port. The kernel source is 9.2.A.0.295 from Sony. Thanks all of above!
Here is Tassadar's original thread which explains what is kexec hardboot and what it does. Apply this patch to your kernel source and it will be capable of booting another kernel/system without reflashing.
Note: KEXEC_HB_PAGE_ADDR doesn't need to be a certain value. In my tests, 0x88000000 and 0x88A00000 both work. However, I don't know if there are significant side effects... There is no ram_console entry in /proc/iomem... The default address calcuated by original patch is 0x88CE0000,which doesn't work, so I removed the calculation code and hardcoded the address (thanks alvinhochun)
Click to expand...
Click to collapse
Usage can be seen in the sh file attached. Sh file is modded on Tasssadar's. Kexec binary is also taken from his github. Thanks again!
Parameters:
--load-hardboot : load the kernel with hardboot request
--initrd : ramdisk path (For 2012 line, that's the ".cpio.gz" file)
--mem-min : where the kernel should be loaded to (lowest address). This is not certain,either. 0x82000000, 0x85000000 both work. You can try different values. (Is there any limitation to this? Plz tell me...) Normally 0x82000000 will be okay.
--command-line : command line for the guest kernel. Note that the arguments appended by bootloader (semcandroidboot.babe1324 etc)need to be added here manually.
Click to expand...
Click to collapse
Now I have successfully dual-booted stock 4.3(205) and OmniROM 4.4 (homemade):
1. re-partition external sdcard to 4 parts. 1 for regular data storage(mmcblk1p1), 1 for /system (mmcblk1p4), 1 for /data (p2) and 1 for /cache (p3).
2. mount /dev/block/mmcblk1p4 to USB storage in TWRP and "dd if=(9.2.A.1.205 system.ext4 extracted from FTF) of=(USB storage)" on computer. You can use a card reader also.
3. modify the fstab files in stock 205 ramdisk to change the devices for /system, /data and /cache. If you want to add recovery, edit their fstabs also. (PERMISSIONS FOR THESE FILES ARE REALLY IMPORTANT! All .rc and fstab should be 644, root:root. Otherwise it won't boot)
4. repack the ramdisk. Push the zImage and ramdisk to the phone and execute the sh file. The phone reboots and stock 4.3 loads.
5. rebooting the phone will go back to host ROM.
Click to expand...
Click to collapse
But there is one problem: in stock 4.3, Baseband is shown as "Unknown" and the phone gets no signal. On the host ROM, it works properly. It seems to be related to TA reading, but I can't think of anything wrong with this...Logcat shows three TA units were missing. But in host ROM, they are shown as missing too. Full logcat attached in zip. I didn't touch any file other than fstab, fstab.qcom and init.target.rc in 205 ramdisk. Stock 4.1 works like a charm though.
Anyone knows? Thanks in advance~

You said you had a Omnirom for tx (homebuild)... Could you share it... If it's stable?
Sent from my LT29i using XDA Premium 4 mobile app

alanc.1996 said:
You said you had a Omnirom for tx (homebuild)... Could you share it... If it's stable?
Sent from my LT29i using XDA Premium 4 mobile app
Click to expand...
Click to collapse
New build arrived (2014/05/21). See the separate thread. Following is the old message.
==================
At least it won't reboot ramdomly..but there may be some minor bugs.
Link: http://pan.baidu.com/s/1i3Hq4ip (Password: kpnn)
Internet connection is not very good here so uploading to devhost/mediafire is nearly impossible...
You need to flash the kernel first, then use the recovery to flash the ROM, then flash the kernel again. After system boots, push the modules file to /system/lib/modules
This is based on tital's port. Thanks a lot~
Later I will open a thread to introduce this ROM...

Cool! Will try it out!
Sent from my LT29i using XDA Premium 4 mobile app

Months ago, when I restored an Nandroid backup of 9.2.A.0.295, the same problem appeared. But at that time only mobile service was dead, while WiFi worked. Now mobile service and WiFi are all dead. The screen stops at "Turning on Wi-Fi". However, in dmesg & lsmod, I can see that WLAN driver module has been loaded, with MAC address changed correctly...And in Service Menu(*#*#SERVICE#*#*), Configuration in Service info is dead. Tapping on it will cause the app to stop responding. What is the point?

OK I tried 9.1.B.1.67 firmware. Everything works, including baseband, Wi-Fi and *#*#SERVICE#*#*... However, it's not so attractive as stock 4.3...

Possible to run this way Doomlord custom kernel (based on stock 205) from stock ROM (PureXT etc)?

RpRAUC said:
Possible to run this way Doomlord custom kernel (based on stock 205) from stock ROM (PureXT etc)?
Click to expand...
Click to collapse
As long as the kernel matches the ROM (phone operates normally when you install the custom kernel as usual), it should be okay...

Is it your plan to keep this TX exclusive, or would you be willing to port this to T?
Great work!
Sent from my LT30p using XDA Free mobile app

Galcactus said:
Is it your plan to keep this TX exclusive, or would you be willing to port this to T?
Great work!
Sent from my LT30p using XDA Free mobile app
Click to expand...
Click to collapse
This patch may work on T without any modification, except for the macro name in memory.h

Has there been any further development on this?
Sent from my LT30p using XDA Free mobile app

Galcactus said:
Has there been any further development on this?
Sent from my LT30p using XDA Free mobile app
Click to expand...
Click to collapse
It's already perfectly working...

In which case, is there any chance of having a guide on how to use this? A few brief steps outlining which files need to be used where, would be greatly appreciated.
(On a side note is there any chance of a version built especially for the Xperia T? I know that there aren't many differences, but it's better to be safe than sorry).
Much obliged
Sent from my LT30p using XDA Free mobile app

Galcactus said:
In which case, is there any chance of having a guide on how to use this? A few brief steps outlining which files need to be used where, would be greatly appreciated.
(On a side note is there any chance of a version built especially for the Xperia T? I know that there aren't many differences, but it's better to be safe than sorry).
Much obliged
Sent from my LT30p using XDA Free mobile app
Click to expand...
Click to collapse
This is a little bit complicated... but I'll try to make a post about this in a few days.
The kernel commits should be the same for TX and T :
https://github.com/updateing/androi...mmit/3d4950e7d3a0cc1549e82fda6c1d961f83e04f4a
https://github.com/updateing/androi...mmit/8843e01fb1b6752768056589a510a2f8985c0884