Related
Has anybody tried latest zImage and modules witch allows us to use 384 mb of RAM and 32 mb of Video Memory?
Kernel and modules are located here: http://oe.netripper.com/files/htcleo_autobuild/
zImage download link: http://oe.netripper.com/files/htcleo_autobuild/zImage-htcleo-increased-ram-latest
modules download link: http://oe.netripper.com/files/htcleo_autobuild/modules-htcleo-increased-ram-latest.tgz
To use this kernel we need to modify this line in STARTUP.TXT:
use ramaddr 0x18000000 (instead of 0x20000000)
you have me confused...are you saying we've been using less than 384MB all along (on Android)?
:O
Kev007 said:
you have me confused...are you saying we've been using less than 384MB all along (on Android)?
:O
Click to expand...
Click to collapse
Yes, at the moment we are using 245 mb of RAM (on Android).
Yeah, all actual builds only use 252MB of ram.
But do not be surprised, the kernel with 384MB misses the latest changes by cotulla (battery, lower power consumption ) because they have not been pushed to git yet.
Sent from my HTC Desire using XDA App
I haven't start with new android img, atm just edit the startup.txt and change zImage, change ramaddres itu 0x180000000, cannot boot into android, just stay at jumping to Kernel.
did I do something wrong here? or I should try with fresh android?
Haret freeze at jumping to kernel point. It doesn't work for me...
hendr1k said:
I haven't start with new android img, atm just edit the startup.txt and change zImage, change ramaddres itu 0x180000000, cannot boot into android, just stay at jumping to Kernel.
did I do something wrong here? or I should try with fresh android?
Click to expand...
Click to collapse
You have to copy provided modules in /system/lib
I added the new zimage and the new moddule but when I try to boot just hangs
at haret boot.
I put both files on the root of the sd card. I remate to zimage and modules I did not change. Also changed the startup text as iunstructed but no go.
DID I need to extract the files elsewhere?? Please advice.
Thanks in advance
if i'm not wrong we need copy the provided modules in /system/lib ( whit the old zimage and a working android system)
after this replace the zimage and edit the STARTUP.TXT whit:
use ramaddr 0x18000000 (instead of 0x20000000)
sea_man said:
if i'm not wrong we need copy the provided modules in /system/lib ( whit the old zimage and a working android system)
after this replace the zimage and edit the STARTUP.TXT whit:
use ramaddr 0x18000000 (instead of 0x20000000)
Click to expand...
Click to collapse
I did just that and got no further along.
but in this kernel gps work?
wifi75 said:
but in this kernel gps work?
Click to expand...
Click to collapse
All the changes Cotulla made over the last weeks are not included as he has not pushed all of his changes to git.
Not working
Sent from my HTC Desire using XDA App
With this over 50% increase in ram would be a significant increase/improvement in performance?
grusy said:
All the changes Cotulla made over the last weeks are not included as he has not pushed all of his changes to git.
Click to expand...
Click to collapse
Sorry to ask but what do you mean 'git', i'm learning fast but still unsure on a few things
elgrego4 said:
Sorry to ask but what do you mean 'git', i'm learning fast but still unsure on a few things
Click to expand...
Click to collapse
git is a source code revision control software that the developers use to store changes to the code...
http://en.wikipedia.org/wiki/Git_(software)
Cheers
Jonas
Yep, something's broken. Doesn't work for me either...
I find this very interesting. Will wait for this to be added in cotulla's public zimage package.
Bump?
10char
Well I got it working. I have more RAM, but a lot of things like Battery charging and other things are missing because Cotulla's code is missing in git.
So it's quite useless now.
PS: I have build my own kernel. It does not work with the autobuild kernel, at least for me.
This is a continuation of the "Compiling CM6 for Eris" thread - http://forum.xda-developers.com/showthread.php?t=856215. But since Team ADX has really come together on this, we are releasing it in it's new form.
Thanks to workshed for working to get the Eris on the Official CM list and merged into the main repo. And also, thanks to workshed for most of the v6 --> v7 changes to EasyDev!
This script will grab CM7 source and compile a CM7 ROM for you using the official vendor tree that is built-in to the CM source. You have the option of including Google Apps or not.
Uses:
CM source - https://github.com/CyanogenMod/android.git
Conap's CFS kernel that's built-in to CM source - https://github.com/Conap30/htc_kernel_desirec_cfs
Requirements
-------------
1) 64- bit Linux -tested on Debian, Ubuntu 10.04, Linux Mint (if you have a different flavor of linux and easydev worked for you, please let us know so we can update this list)
2) An existing Eris ROM that the script will pull the proprietary files from.
INSTRUCTIONS
1) Download the script
2) 'chmod a+x easydev-v9.sh'
3) copy it to the directory of your choice or leave it where it is
4) copy an existing ROM to the same directory (tested with GSB, but most should work)
5) run it ('sudo ./easydev-v9.sh')
Possilbe future features:
Done.
Changelog
v1 - initial release
v2 - added squisher, made 'make clean' optional, added installation of dependencies, cleaned up output
v3 - uses existing ROM to pull proprietary files, renamed to 'easydev' for case sensitive linux admins
v4 - fixed file missing from list in unzip-files.sh in vendor tree, fixed move/rename of existing ROM, change 'make clean' option to default to no instead of yes
v5 - added 'apt-get update' to refresh repo list (should install dependencies now), swapped order of extract-files and unzip-files to fix 'chmod akmd' issue, tried not to break anything else
v6 - moved questions to beginning of script, added check to only init repo the first time, added check for existing ROM, modded vendor tree to fix compile issues
v7 - removed CM6 stuff, removed kernel compilation code, removed vendor tree code, changed from CM6 to CM7, fixed path bug, added 32-bit libs to dep list
v8 - added ALL official CM devices (mostly untested), minor update to dependency installer code (4-21-11)
v9 - added an extra check for correct Java version, fixed .zip rename issue
Download links:
v7+ --> https://github.com/gnarlyc/EasyDev-Eris
NOTE: If you have issues with google setup or not being able to pass andy the android at the beginning of setup, please delete Provisions.apk for system/app you shouldn't have a problem, but just incase, this will remedy it. -workshed
I'm all over this sh*t
Oh damn, I'm excited for this. good thing I use ubuntu!
Sent from my ERIS using XDA App
this should be fun once i get my new laptop.
Nice! I will be trying this later.
This is awesome! Thanks alot. What does the 'make clean' option do?
Skrip037 said:
This is awesome! Thanks alot. What does the 'make clean' option do?
Click to expand...
Click to collapse
The make clean removes everything that has been compile so far leaving only the original source.
Skrip037 said:
This is awesome! Thanks alot. What does the 'make clean' option do?
Click to expand...
Click to collapse
It removes any previously built ROMs, etc. It's not needed every time, so I've made it optional in the next version. The problem was that sometimes the script would be broken in some way and wouldn't build a ROM. But, there's so much text displayed to the screen, it's not always easy to notice. So, I was actually flashing the same test ROM over and over instead of getting a new build...
Great work guys. Going to try it out on Arch Linux and if anyone's interested I'll give details about how to get it working there (or just modify the script to detect Arch as opposed to Ubuntu and work accordingly.
<gripe>One complaint: commands (including scripts) should *always* start with a lowercase letter </gripe>
good work gnarlyc & conap.
this sounds great and i will be trying this when i get home. I have just one question. Why would i want to run this instead of conap's rom? Both being pure CM. I see alot of the other cm6 roms have stuff themed, but conap's rom doesn't. I'm assuming this is complete pure cm without little tweaks done by devs of the respective roms. Thanks in advance.
ngc604 said:
this sounds great and i will be trying this when i get home. I have just one question. Why would i want to run this instead of conap's rom? Both being pure CM. I see alot of the other cm6 roms have stuff themed, but conap's rom doesn't. I'm assuming this is complete pure cm without little tweaks done by devs of the respective roms. Thanks in advance.
Click to expand...
Click to collapse
Some people just like to "roll their own", more or less. If you like having someone else make improvements and fix issues for you, then you'll probably want to stick with another ROM.
I would love to make my own fixes and tweaks but i dont have the knowledge nor the time to gain said knowledge. guess i will just stick with the devs roms. thanks
Very very exciting. I am installing Ubunto 10.4 now. So does EasyDev-v2 pull from the CM6 nightlies or the stable version and can we change where it pulls from for the CM6 source. This is great.
Will have to check this out later. Always wanted to understand the compile process, always to busy with other software projects. Thanks for building this resource for the rest of us.
morrisdan said:
Very very exciting. I am installing Ubunto 10.4 now. So does EasyDev-v2 pull from the CM6 nightlies or the stable version and can we change where it pulls from for the CM6 source. This is great.
Click to expand...
Click to collapse
Hmmm. Someone correct me if I'm wrong, but I'm pretty sure that this is currently grabbing 'stable'.
Code:
repo init -u git://github.com/CyanogenMod/android.git -b froyo
I'm thinking that to get the nightly, we'll have to change that to:
Code:
repo init -u git://github.com/CyanogenMod/android.git -b master
I'll try it as soon as I can. You got me to thinking that we could add that as an option, if I understand this correctly.
Nightly vs Stable
Yes, you answered my question regarding nightly and stable. I am having fun so far. I got all the necessary packages installed. That was pretty easy using the Ubunto package manager deal. So where do I find the proprietary.zip now? I am almost there to cook this sucker up.
morrisdan said:
Yes, you answered my question regarding nightly and stable. I am having fun so far. I got all the necessary packages installed. That was pretty easy using the Ubunto package manager deal. So where do I find the proprietary.zip now? I am almost there to cook this sucker up.
Click to expand...
Click to collapse
I was apparently wrong about the "-b master" switch, but I think I mostly got it right...
Right now, you'll have to grab the files listed in the OP and zip them up into a file called 'proprietary.zip'. Then place it in the same directory that you run the script from.
I'm working on a way that you can just place an existing ROM there, and it will extract the proprietary files for you. That should be in v3.
Proprietary.zip Files
Can I download CELB Froyo 3.8 and uncompress it and do searches for those files and pull them out and zip them up?
morrisdan said:
Can I download CELB Froyo 3.8 and uncompress it and do searches for those files and pull them out and zip them up?
Click to expand...
Click to collapse
Yes, that should work fine. Here's a list with the paths -
https://github.com/Conap30/android_device_htc_desirec/blob/master/extract-files.sh
Hi hackers,
i know about the common method described by chulri, to compile custom kernels and it works well.
Anyway for kernel only experiments this way is little too bloated.
EDIT3:
So here's my standalone toolchain for archos (build with modified buildroot system for 32Bit linux OS):
arm-archos GCC4.4.1 for ARM uClinux (uClibc C library 0.9.30 with Archos specific tweaks and bugfixes)
http://dl.dropbox.com/u/8815400/arm-archos.tar.gz
EDIT5:
The toolchain does not work on a 64Bit OS.
I'll post a link for the 64Bit version soon.
Only for reference:
There are a lot of external solutions to be found in the web.
E.g. there are different flavoured toolchains based on gcc 4.4.1 from Mentor Graphics (formerly known as Codesourcery):
Sourcery G++ Lite 2010q1-188 for ARM EABI (Newlib C library 1.17.0)
Sourcery G++ Lite 2010q1-189 for ARM uClinux (uClibc C library 0.9.30)
Sourcery G++ Lite 2010q1-202 for ARM GNU/Linux (GNU C library 2.11)
So if i restrict my activities on kernel compilation all three should do the job.
I made a custom kernel using the above mentioned GNU C toolchain, all compiles fine, but did not test it yet.
This is next... i need to find an easy way to test my tweaked kernels.
So far i would recommend UrukDroid running and use the recovery menu to exchange the kernel & ramdisk.
Any comments are welcome.
Unfortunately our devices use also some binary only kernel modules which are not supported by this method:
hmditx.ko (though marked as GPL, we got no sources)
hdmicec.ko (same here)
UPDATE: Sources had been published by Archos at gitorious.
nwolc.ko (proprietary module from NXP)
BTW, someone should contact the author Andre Lepine to hand out the GPL'ed source code
If i got it right, all custom kernels had been build using the buildroot system because of these.
AFAIK using another toolchain would result in a completely different system map and prevent the modules to load.
Anyway if we exclude HDMI and tweak some start scripts to prevent the modules to get loaded, we'll be fine.
Would be nice to start some discussion up here or leave a comment.
I'd also like to get some tricks form the cracks
EDIT:
Sure there's also Ti's wireless driver package which has to be integrated to compile tiwlan_drv.ko.
Need to do some research to find the correct package.
Any hints are welcome!
EDIT2:
Anyone tried to compile a gen8 kernel using the new gen9 kernel source?
Everything seems to be there...
EDIT4:
See above! The toolchain works very nice.
It had been specially compiled for external use and in the meantime it was tested on many different hosts.
Instructions how to install and use it could be found here:
http://forum.xda-developers.com/showpost.php?p=19134490&postcount=8
Thanks a lot for your attention!
Regards,
scholbert
One question: What's so much better about that toolchain to throw away the Archos-compatible toolchain and deal with the hassle of excluding features to build compatible binaries? I guess I didn't get the point
chulri said:
One question: What's so much better about that toolchain to throw away the Archos-compatible toolchain and deal with the hassle of excluding features to build compatible binaries? I guess I didn't get the point
Click to expand...
Click to collapse
Like i tried to point out:
Anyway for kernel only experiments this way is little too bloated.
Click to expand...
Click to collapse
A neat little cross toolchain environment would be enough for kernel experiments.
I'm working on different platforms e.g. old Debian 4.0 workstation, Netbook with UNR 11 but limited space, other linux machines i don't like to run entire process.
You need a lot of disk space and time (at least first time to build the whole environment).
The other thing is that everything is built into the buildroot structure, you could barely locate the toolchain itself...
Sure your right, if you say everthing works out of the box, but i don't like all these automated procedures, to build my own kernel.
In fact that's just it and i wonder if there's another way.
Just kernel source + cross-toolchain...
Apart from that, the toolchain Sourcery G++ Lite 2010q1-189 for ARM uClinux (uClibc C library 0.9.30) is very close to the Archos one.
BTW, anyone tried to tweak the Archos build script to built the toolchain for external use?
Cheers,
scholbert
scholbert said:
So if i restrict my activities on kernel compilation all three should do the job.
I made a custom kernel using the above mentioned GNU C toolchain, all compiles fine, but did not test it yet.
Click to expand...
Click to collapse
Hi Scholbert!
I've been doing the same for my kernels, it compiles and runs fine, wifi loads without any particular tweak with the original Archos compiled module, but I didn't check hdmi as I don't have cable for it. I'm using a cm7 toolchain to build it (arm-eabi-4.4.3) though.
scholbert said:
This is next... i need to find an easy way to test my tweaked kernels.
So far i would recommend UrukDroid running and use the recovery menu to exchange the kernel & ramdisk.
Click to expand...
Click to collapse
My setup is a bit different since I patched bootloader: I have my "stable" build on normal boot (/rawfs/init) and my dev build on sde (/rawfs/custom), and I flash my kernel directly from my stable build without going through recovery.
I just do adb push kernel and initrd, then directly on device a "kd_flasher -k kernel -i initrd", and I reboot from normal to sde with a "reboot_into sde". It's really quick this way, I just have a script on my linux box to do all this.
I believe you can do the same without patched bootloader with a temproot on secure archos build.
scholbert said:
EDIT2:
Anyone tried to compile a gen8 kernel using the new gen9 kernel source?
Everything seems to be there...
Click to expand...
Click to collapse
Yes, I'm playing with it. I don't know what device you have, but mine (A70S) was not finished in Archos sources: board-archos-a70s is almost empty, panel wasn't finished... I add stuff slowly (still learning Omap, I know Qualcomm better), my kernel boots, I currently have framebuffer, internal mmc and usb working.
Hi letama!
letama said:
I've been doing the same for my kernels, it compiles and runs fine, wifi loads without any particular tweak with the original Archos compiled module, but I didn't check hdmi as I don't have cable for it. I'm using a cm7 toolchain to build it (arm-eabi-4.4.3) though.
Click to expand...
Click to collapse
Cool that's nice information.
Interesting that the tiwlan_drv.ko loads without problems.
Just to start an experiment, i started to shrink down the buildroot setup from Archos and built the gcc 4.4.1 toolchain only.
But it's not finished yet...
letama said:
My setup is a bit different since I patched bootloader: I have my "stable" build on normal boot (/rawfs/init) and my dev build on sde (/rawfs/custom), and I flash my kernel directly from my stable build without going through recovery.
Click to expand...
Click to collapse
O.k. i see, sounds like a clean environment this way.
In fact there's no need for this sqashfs thing anymore...
I already got the SDE's avboot version installed. This version is little bigger in size and obviously got some add-on's.
The same byte signature could be found here, so i guess the hack would match this avboot version as well.
Maybe i give it a try.
letama said:
I just do adb push kernel and initrd, then directly on device a "kd_flasher -k kernel -i initrd", and I reboot from normal to sde with a "reboot_into sde". It's really quick this way, I just have a script on my linux box to do all this.
Click to expand...
Click to collapse
Cool, sounds like a nice development platform this way.
letama said:
I believe you can do the same without patched bootloader with a temproot on secure archos build.
Click to expand...
Click to collapse
Mmmh i thought about using it from UrukDroid...
Anyway, the way you do it sounds more elegant.
letama said:
Yes, I'm playing with it. I don't know what device you have, but mine (A70S) was not finished in Archos sources: board-archos-a70s is almost empty, panel wasn't finished... I add stuff slowly (still learning Omap, I know Qualcomm better), my kernel boots, I currently have framebuffer, internal mmc and usb working.
Click to expand...
Click to collapse
I got an A101... looks little better here, but i did not compile the kernel yet.
Anyway, would be nice to have a complete kernel (incl. wireless and HDMI base code) in the end which compiles fine with latest gcc and runs out of the box
Thanks a lot for your extensive reply!!!
Regards,
scholbert
scholbert said:
I already good the SDE's avboot version installed. This version is little bigger in size and obviously got some add-on's.
The same byte signature could be found here, so i guess the hack would match this avboot version as well.
Maybe i give it a try.
Click to expand...
Click to collapse
Yes, it's the same signature, I verified it with IDA before installing sde, only location differs. You should be fine as long as you don't have multiple matches. If you want my code to patch it, let me know... You'd have to adapt the offsets but it would be probably safer than doing it manually.
Regarding kernel development, I forgot one big advantage to have patched bootloaders: ram_console! I built my "stable" and "dev" kernels with it, so I just have to make my dev kernel to crash to reboot and get the full dmesg with "cat /proc/last_kmsg" even if framebuffer or usb don't work .
scholbert said:
I got an A101... looks little better here, but i did not compile the kernel yet.
Anyway, would be nice to have a complete kernel (incl. wireless and HDMI base code) in the end which compiles fine with latest gcc and runs out of the box
Click to expand...
Click to collapse
Yes, gen9 sources look better for A101, I took them as base for my A70 and it's almost ok. I took away hdmi as it seems a bit too hackish, I'll see later . I also had some issue with gp timers that wouldn't use 32K clock, I'd be curious to see a dmesg on a gen9 tablet.
Right now I'm fighting with usb that kills video driver looonng way to go before having a fully functional kernel.
letama said:
Yes, it's the same signature, I verified it with IDA before installing sde, only location differs. You should be fine as long as you don't have multiple matches. If you want my code to patch it, let me know... You'd have to adapt the offsets but it would be probably safer than doing it manually.
Click to expand...
Click to collapse
Thanks for offering your tool.
Guess it's the same you once posted in that thread about changing bootlogo.
I had a look at the soruces once.
Anyway i already prepared a patched bootblock. Did not re-write it yet
Time is lacking...
letama said:
Regarding kernel development, I forgot one big advantage to have patched bootloaders: ram_console! I built my "stable" and "dev" kernels with it, so I just have to make my dev kernel to crash to reboot and get the full dmesg with "cat /proc/last_kmsg" even if framebuffer or usb don't work .
Click to expand...
Click to collapse
Yupp that's nice... have you seen my UART hack?
letama said:
Yes, gen9 sources look better for A101, I took them as base for my A70 and it's almost ok. I took away hdmi as it seems a bit too hackish, I'll see later . I also had some issue with gp timers that wouldn't use 32K clock, I'd be curious to see a dmesg on a gen9 tablet.
Right now I'm fighting with usb that kills video driver looonng way to go before having a fully functional kernel.
Click to expand...
Click to collapse
Guess i will try to compile this kernel soon.
No time for that right now.
Made some efforts to built special toolchain.
See the upcoming post...
Big thanks for participating!!!
Regards,
scholbert
Ready to use Archos specific toolchain
Hi again,
three simple steps to build UrukDroid custom kernel/modules:
1. Grab my customized toolchain and install it (see first post).
The toolchain is configured to work on mostly any 32Bit linux host (min. libc 2.3.6, should work down to Debian 4.0, Ubuntu 8.04 and similar).
The toolchain must be extracted and placed at /opt on your host machine (x86).
To run it as a user you might change the properties for /opt directory to match the user's rights.
You also could extract the archive as root and run:
chown -R 1000:1000 /opt/arm-archos
To make it more comfortable:
Modify user's .bashrc file to include the path to the toolchain:
export PATH=$PATH:/opt/arm-archos/usr/bin
2. Grab UrukDroid kernel sources and compile.
UrukDroid kernel sources could be found here:
http://sauron.pourix.com/UrukDroid/UrukDroid-1.5/UrukDroid-1.5.1-kernelsrc.tar.bz2
You might extract the sources anywhere you like.
After this has been done, step into the kernel source root directory.
Modify Makefile to use the Archos toolchain (line 199):
Code:
...
# Alternatively CROSS_COMPILE can be set in the environment.
# Default value for CROSS_COMPILE is not to prefix executables
# Note: Some architectures assign CROSS_COMPILE in their arch/*/Makefile
export KBUILD_BUILDHOST := $(SUBARCH)
ARCH ?= $(SUBARCH)
CROSS_COMPILE ?= arm-linux-uclibcgnueabi-
...
cp linux.config .config
make oldconfig
make zImage
make modules
make modules_install INSTALL_MOD_PATH=/my_kernel/modules/
3. Transfer the binaries to your Archos device.
Right now there's no need to exchange the kernel, because we use $auron's base setup for the kernel.
Place your custom modules at /lib/modules
TBC
scholbert
scholbert said:
Thanks for offering your tool.
Guess it's the same you once posted in that thread about changing bootlogo.
I had a look at the soruces once.
Anyway i already prepared a patched bootblock. Did not re-write it yet
Time is lacking...
Click to expand...
Click to collapse
Yes, it's roughly the same code. You did patch both location ?
scholbert said:
Yupp that's nice... have you seen my UART hack?
Click to expand...
Click to collapse
Yes, saw it, it would be very nice to have console on serial, but I don't want to open my A70 yet as it's still has warranty running. I may try that if I can find parts and if I get a gen9 as "main".
scholbert said:
Guess i will try to compile this kernel soon.
No time for that right now.
Click to expand...
Click to collapse
Great! Let me know if you have something, I'd be very interested in a dmesg.
I somehow "fixed" my video driver problem (well, not really fixed, adding traces made it go away ), now I'm trying to get SurfaceFlinger works. Sgx driver doesn't seem to play nice with .29 userspace binaries, I'm not sure I'd be able to go much further without new binaries.
scholbert said:
Made some efforts to built special toolchain.
See the upcoming post...
Click to expand...
Click to collapse
Nice! I'll try to take a look at it when I find some time.
Hey letama,
sorry for the delay...
letama said:
Yes, it's roughly the same code. You did patch both location ?
Click to expand...
Click to collapse
Yepp, both locations are patched.
As we already pointed out, there the rawfs header contains some checksums and avboot is the first file in there.
What do you think, if i manually change some bytes in avboot and leave the checksum untouched, will there be any problems?
letama said:
Yes, saw it, it would be very nice to have console on serial, but I don't want to open my A70 yet as it's still has warranty running. I may try that if I can find parts and if I get a gen9 as "main".
Click to expand...
Click to collapse
O.k. if there's warranty on your device, i totally agree.
letama said:
Great! Let me know if you have something, I'd be very interested in a dmesg.
Click to expand...
Click to collapse
Need more time
letama said:
I somehow "fixed" my video driver problem (well, not really fixed, adding traces made it go away ), now I'm trying to get SurfaceFlinger works. Sgx driver doesn't seem to play nice with .29 userspace binaries, I'm not sure I'd be able to go much further without new binaries.
Click to expand...
Click to collapse
Yeah guess there are some changes in the drivers API.
letama said:
Nice! I'll try to take a look at it when I find some time.
Click to expand...
Click to collapse
So far i tested it, the toolchain works out very nice.
Concerning kernel compilation:
It seems the binaries are quite well optimized in size. No problems so far.
I found out that in stock ROM they used some strip command to make the modules even smaller.
Anyway won't speed things up significantly i guess...
Concerning userland apps:
Though my genereated uClibc is little bigger in size, i noticed no problems so far. A binary comparison between the libaries (stock vs mine), shows little differences though.
Anyway, would be nice if people use it and report...
Have a nice day!
scholbert
Hi Scholbert!
scholbert said:
sorry for the delay...
Click to expand...
Click to collapse
No problem, I'm also busy as hell...
scholbert said:
Yepp, both locations are patched.
As we already pointed out, there the rawfs header contains some checksums and avboot is the first file in there.
What do you think, if i manually change some bytes in avboot and leave the checksum untouched, will there be any problems?
Click to expand...
Click to collapse
Well, I didn't touch checksums either, and it seems they're not checked anywhere else, so you should be good. As long as you patched both location before reboot, you should be ok.
scholbert said:
Yeah guess there are some changes in the drivers API.
Click to expand...
Click to collapse
I made some progress there, I took LG P970 3D binaries with driver source code from their cm7 kernel (they also have a 2.6.35) and I was able to boot up to launcher. I had to fiddle a bit with audio runtime as phone audio won't work, but low level audio driver is working too. Next step is touchscreen... And probably doing a proper cm7 build, I'm running a frankenstein mix of cm7 for nook tablet
scholbert said:
So far i tested it, the toolchain works out very nice.
Click to expand...
Click to collapse
I tried it briefly yesterday as I borked my kernel config at some point and it was crashing my usual toolchain, it doesn't run on my comp: "error while loading shared libraries: libmpfr.so.1: wrong ELF class: ELFCLASS64". Ubuntu 11.10 64 bits...
Best,
LeTama
letama said:
Well, I didn't touch checksums either, and it seems they're not checked anywhere else, so you should be good. As long as you patched both location before reboot, you should be ok.
Click to expand...
Click to collapse
Yeah guessed so... the russian guy who first tried this hack also never mentioned anything like this. So it'll be safe then.
letama said:
I made some progress there, I took LG P970 3D binaries with driver source code from their cm7 kernel (they also have a 2.6.35) and I was able to boot up to launcher. I had to fiddle a bit with audio runtime as phone audio won't work, but low level audio driver is working too. Next step is touchscreen... And probably doing a proper cm7 build, I'm running a frankenstein mix of cm7 for nook tablet
Click to expand...
Click to collapse
Wow sounds pretty like a "frankengenius" software design.
Good work!
Have you seen that Archos released part of the hdmi code as external driver code. So the kernel is even more open now (speaking of 2.6.29).
Sometimes their cooperation is very nice.
About two weeks ago i contact the author at NXP, then last week i wrote to Archos and on thursday they released it. Not bad...
Anyway they ought to release the source, even without mentioning it.
It's just GPL code.
letama said:
I tried it briefly yesterday as I borked my kernel config at some point and it was crashing my usual toolchain, it doesn't run on my comp: "error while loading shared libraries: libmpfr.so.1: wrong ELF class: ELFCLASS64". Ubuntu 11.10 64 bits...
Click to expand...
Click to collapse
Sure the toolchain is compiled for 32Bit systems, forgot to mention this.
So it will never work on a 64Bit system.... sorry
Cheers,
scholbert
scholbert said:
Have you seen that Archos released part of the hdmi code as external driver code. So the kernel is even more open now (speaking of 2.6.29).
Click to expand...
Click to collapse
Didn't see it, very nice! HDMI is a low on my priority list, but it's good to have source code, it will help porting it. Even though my efforts on this kernel will slow a bit as I purchased today a gen9 and ICS source code is out .
At first glance, boot process and layout looks very similar to our gen8, same rawfs, a custom file that would indicate that we should get SDE, so far so good. Need to spend some quality time with hex editor and IDA now .
Damn work, I need 72 hours days!
scholbert said:
Sure the toolchain is compiled for 32Bit systems, forgot to mention this.
So it will never work on a 64Bit system.... sorry
Click to expand...
Click to collapse
No problem, just wanted to give a bit of feedback.
@letama:
Wouldn't it be alot more productive for you and us if you would somehow join your affort with the guys from openaos?
cm7 and then cm9 would be here faster the more experienced devs are helping.
fzelle said:
@letama:
Wouldn't it be alot more productive for you and us if you would somehow join your affort with the guys from openaos?
cm7 and then cm9 would be here faster the more experienced devs are helping.
Click to expand...
Click to collapse
Hi fzelle,
Well, I'm only learning slowly, they're far more experienced than me on Archos. My main goal is to understand omap platform, that's why I'm toying with the 2.6.35 kernel. Cm7 is only a convenient for way me to make sure the kernel behaves well. I don't seek a perfect cm7/archos experience for all devices as they do, but if at some point I learned enough, I may try to help if I can.
LeTama
CM7 for Archos atm is based on the 2.6.29 kernel delivered from Archos, so your kernel is far more advanced.
And if you got 2.6.35 to work properly, the guys over at openaos would probably be happy to use that.
fzelle said:
CM7 for Archos atm is based on the 2.6.29 kernel delivered from Archos, so your kernel is far more advanced.
And if you got 2.6.35 to work properly, the guys over at openaos would probably be happy to use that.
Click to expand...
Click to collapse
Yes, 2.6.35 should match better gingerbread code. If I can go somewhere, I'll share it. Currently, I'm far from that, still having troubles with usb and a big piece will be power management. We'll see, but I'm a bit out of free time.
Hey letama,
i guess fzelle is right.
AFAIK, the openaos developers concentrate on the Android part for gen8. As stated they still use 2.6.29 and this no problem so far.
But a kernel project might run in parallel.
Would be nice to get the new kernel working at least for A70 and A101.
I started a build for A101 (...and still compiling), maybe we could share our .config file
EDIT: Aaaaaargh, still fighting with the kernel config/compile errors.
Wifi/BT framework issue.... RFKILL_STATE_UNBLOCKED etc. seems not to be implemented anymore...
letama said:
I made some progress there, I took LG P970 3D binaries with driver source code from their cm7 kernel (they also have a 2.6.35) and I was able to boot up to launcher. I had to fiddle a bit with audio runtime as phone audio won't work, but low level audio driver is working too. Next step is touchscreen... And probably doing a proper cm7 build, I'm running a frankenstein mix of cm7 for nook tablet
Click to expand...
Click to collapse
The SGX part is an open issue i guess, but there's some support form Ti as well. E.g.: https://gforge.ti.com/gf/project/openmax/frs/
Remember the Beagleboard-XM is very similar to what we got on our devices.
Also Zoom3 platform, so maybe their repository is a good starting point for these addon's as well.
In fact using the OMAP might be a benefit in general, because there are so many opensource projects covering this architecture
Happy hacking!
scholbert
Hi Scholbert,
scholbert said:
i guess fzelle is right.
AFAIK, the openaos developers concentrate on the Android part for gen8. As stated they still use 2.6.29 and this no problem so far.
But a kernel project might run in parallel.
Would be nice to get the new kernel working at least for A70 and A101.
Click to expand...
Click to collapse
Agreed! It would be nice if we could develop both A70 and A101 in parallel, sharing will speed things up.
scholbert said:
I started a build for A101 (...and still compiling), maybe we could share our .config file
Click to expand...
Click to collapse
I attached my current one, I added one config option that you don't have, CONFIG_MUSB_ERRATA_445, you can remove the line. I'm not sure I have the config right, but it boots and has quite a lot of stuff working. You need to re-add A10IT board though.
scholbert said:
The SGX part is an open issue i guess, but there's some support form Ti as well. E.g.: https://gforge.ti.com/gf/project/openmax/frs/
Click to expand...
Click to collapse
Well, for me it's no longer an issue, I think what I did is the best we can do until we can get a hand on Archos binaries for 3630. The issue is that you have to have proprietary binaries, they must match driver version, and the binaries I have from P920 works fine even though maybe not as recent as Archos ones. There is no open source implementation afaik. OpenMax is only for video codec, not 3D.
scholbert said:
Happy hacking!
Click to expand...
Click to collapse
Thanks, you too! You have a mission now! Let's get this kernel running on A101
Hi letama!
letama said:
Agreed! It would be nice if we could develop both A70 and A101 in parallel, sharing will speed things up.
Click to expand...
Click to collapse
To be honest i meant developing openaos and kernel in parallel. Who ever does it
Anyway, as i wrote it... i started to play around with the new kernel.
It's hard for me these days to find some time for hacking and i'm not a genius in modifying kernel drivers and stuff.
So in fact i don't know how far i will get things rollin'
letama said:
I attached my current one, I added one config option that you don't have, CONFIG_MUSB_ERRATA_445, you can remove the line. I'm not sure I have the config right, but it boots and has quite a lot of stuff working. You need to re-add A10IT board though.
Click to expand...
Click to collapse
Thanks a lot. I will compare your config with my setup.
Already found some missing parts in the board file...
letama said:
Well, for me it's no longer an issue, I think what I did is the best we can do until we can get a hand on Archos binaries for 3630. The issue is that you have to have proprietary binaries, they must match driver version, and the binaries I have from P920 works fine even though maybe not as recent as Archos ones. There is no open source implementation afaik. OpenMax is only for video codec, not 3D.
Click to expand...
Click to collapse
Ah i see, so i'll take a look at the binaries.
I guess you meant P970, as stated earlier.
letama said:
Thanks, you too! You have a mission now! Let's get this kernel running on A101
Click to expand...
Click to collapse
Haha, as stated above... nice mission anyway
BTW, did you see there are some nice projects at gitorious.
A 2.6.37 kernel port for A43 and A101 had also been started already.
I had a short look at some parts... don't know about the exact state of the code.
Let's stay in touch!
Best regards,
scholbert
Tool Aces Present
Rom-Porter
Disclaimer
Code:
title disclaimer
echo.
Echo you and you alone are choosing to use this tool. So i am not responsible if anything happens to you or your phone due to it.
Echo.
Click to expand...
Click to collapse
Pre-Requisites1. notepad++
2. Better if you know the manual steps.
Click to expand...
Click to collapse
Steps1. Download the zip and extract it.
2. Read the help and pre requisites first.
3. Run the rom-porter.bat file
4. Start porting and follow instructions.
Click to expand...
Click to collapse
Features• Pause and resume Porting.
• Manufacturer ROM Port.
• Lewa and Joy OS Porting.
• Fully automated.
• Build.prop and init.d tweaks.
• Update feature.
• Readable Log File.
• Many Fail safe's.
Click to expand...
Click to collapse
Faqq. It gives x error
a. Give which step it is(No.), what error it gives. and most importantly attach a log using 'Pull Log File' Option.
q. it says findstr not recognized as an internal or external command
a. just close the tool and restart it.
q. it says xcopy not recognized as an internal or external command
a. just close the tool and restart it.
q. How can i add my own build.prop and init.d tweaks
a. for build.prop, copy the tweak in a txt file, give it a name without space and copy it to essentialsbtweak
for init.d, copy the header "#!/system/bin/sh" and then the tweak, give it a name without space, remove the file extension and copy it to essentialsitweak
Q. I want x feature.
A. Just reply here what you want, if its possible by me, I'll add it asap
Click to expand...
Click to collapse
CreditsRishab.Raj37 for his amazing guide on Porting rom
GalaxyUser for his excellent guide on porting manufacturer ROMS
blindndumb for his great guide on Porting Lewa and Joy OS
po8pimp for new awesome theme and exe packing
Abhinav2 For new coding and testing
PluginSz For testing the tool
Click to expand...
Click to collapse
If you like this tool press the thanks button, and consider giving this thread a five star Rating
Oh and if you upload the rom on xda, do give me credits.
XDA:DevDB Information
Rom Porter, Tool/Utility for the Android General
Contributors
mnishamk
Version Information
Status: Stable
Current Stable Version: 3.6
Stable Release Date: 2013-07-24
Current Beta Version: 3.7
Beta Release Date: 2014-09-18
Created 2014-10-23
Last Updated 2014-10-23
Downloads and Changelogs
Download
Head Over to the download section
changelog
Code:
[19.12.14]
v3.9
-> Created self-extraction tool
-> Added Custom theme options
-> Changed bootup animation
-> Thanks to po8pimp
[06.12.14]
v3.8
->Fixed find and findstr error
->Changed the update tool routine.
[18.09.14]
v3.7
->Now can port Kitkat roms. Added kitkat filesystem changes
[24.7.13]
v3.6
->fixed bug in manufacturer rom port
[2.7.13]
v3.5
-> Automated Changing EOL character.
-> finally FULLY Automated.
[17.6.13]
v3.3
-> Added Lewa and Joy OS Porting.
-> Changed the way the sequence is executed.
-> Extended help menu.
-> Changed the logic in some cases.
[6.4.13]
v3.1
-> HTC network auto select fix
[27.5.13]
v2.9
-> small changes in coding
[26.5.13]
v2.8
-> Supports Manufacturer Roms (Testing phase)
-> Squashed a few Bugs
[20.5.13]
v2.7
-> Hopefully, Patched Find and Findstr error for good.
-> Fixed a logical Error
-> Updated Logs.
[17.5.13]
v2.6
->added Log Feature.
[16.5.13]
v2.5
-> added update option
[16.5.13]
v2.4
-> added option to copy zip to sd card.
[15.5.13]
v2.3
-> added Init.d tweaks
[15.5.13]
v2.2
-> added build.prop tweaks.
[14.5.13]
V2.1
-> Modified coding to make version selection automated. Thanks to abhinav2
v2.0
-> supports 32 bit too.
[13.5..13]
v1.9
-> first release
"1. Download the zip and extract it. ..."
SO, where is the zip ???
Good work
Cheers,
AJ
Abhinav2 said:
Lol u again forgot the dl link
Well anyways awesome work as always.....
Cheers,
AJ
Click to expand...
Click to collapse
No I didn't. I was updating the post.
Regards
N
mnishamk said:
No I didn't. I was updating the post.
Regards
N
Click to expand...
Click to collapse
Sorry opened this page a bit earlier.....though commented late so at that time the link wasn't up Just refreshed the page and saw the link
Keep it up anyways :good:
Cheers,
AJ
version 2.2 released
now you can add build.prop tweaks too.
Your kidding!! Great idea, a porting utility tool..Hats off to you and everyone involved with development..
XT912 CDMA Pac Man 4.2.2
1droidmod said:
Your kidding!! Great idea, a porting utility tool..Hats off to you and everyone involved with development..
XT912 CDMA Pac Man 4.2.2
Click to expand...
Click to collapse
The idea was alread there. And the tool too
We only made it a lil more automated.
Regards
N
hey guys ,can i port a cm10 touchwiz rom to a cm10 rom for LG P700 ? ..
I don't think it can be used, coz when they are from different manufacturers, they'll need heavy framework modding etc which the tool does not do.
So its better to port from the sam manufacturer and a similar specs device.
Regards
N
i understand ,that was the real fun in all this porting thing ,i realy wanted a touchwiz inspired rom ! thanks a lot !
The tool won't help you with it coz each one would be different. There's a guide arounf here for porting manufacturer roms, try that
Regards
N
v2.3 released. supports init.d tweaks
Thanks ,maybe someone wil develope an automatic porter like this one for diferent manufactor devices..until then i'm going to search the manual way to port id! Cheers
Sent from my LG-P700 using xda app-developers app
keemo.rom said:
Thanks ,maybe someone wil develope an automatic porter like this one for diferent manufactor devices..until then i'm going to search the manual way to port id! Cheers
Sent from my LG-P700 using xda app-developers app
Click to expand...
Click to collapse
I'll try it, :thumbup:but if its too hard, I may abandon it.
Regards
N
mnishamk said:
I'll try it, :thumbup:but if its too hard, I may abandon it.
Regards
N
Click to expand...
Click to collapse
Thats great news ,i hope you will have great succes!!
Sent from my LG-P700 using xda app-developers app
keemo.rom said:
Thanks ,maybe someone wil develope an automatic porter like this one for diferent manufactor devices..until then i'm going to search the manual way to port id! Cheers
Sent from my LG-P700 using xda app-developers app
Click to expand...
Click to collapse
An automatic "porter" for different devices roms is kinda impossible as this software would be able to practise magic lol. This means it would download the related kernel sources, edit them and insert correct code, including proprietary device files, configure the kernel and compile it (besides of that it must grab the toolchain and set the PATHs, etc, etc..). Then it would decompile the roms framework (of course including full automatic smali magic ) detecting the correct requirements and edit that stuff before it compiles and signs it with system sign keys.. And last but not least it has to compile board related drivers (for kernel and rom) and bake them into the project. When finished all processes it builds a full working flashable rom zip for your device - and if you are nice it will also download the right Gapps and copy all of it to your SDcard
Sorry for sounding like an a**hole Just joking a bit.
The point is that a software like that would do all the work for devs and we all wouldn't have to work that much.. It would be nice, but it's just too much code, too complex for a software to do this. Porting a rom to another device cannot be done with prebuilt files usually. You need to work with the source and that's a lot of work. Except the devices are using almost the same board, chipset and CPU.
Besides of that: This is a nice tool! Thanks for your work, this will be helpful for beginners to perform some first steps! :good:
im trying to port axiom for the hd to the m im using dhackers pere aosp as the base for the m. everything extracts fine then starts the porting process then at the end it says THE SYSTEM CANNOT FIND THE FILE SPECIFIED THE FILENAME, DIRECTORY NAME, OR VOLUME LABEL SYNTAX IS INCORRECT. that is after desktop\romporter\temp\platform.xml 2 files moved any ideas?
By the end you mean which step? The end of extraction?
Regards
N
Excuse my bad English.
With the Kernel DorimanX b11.0 b012 now BLN have brought to works again.
I use CM12.1 official, while I proceeded as follows:
- Create a backup from the rom first.
- Under "/system/lib/hw" I have the "lights.exynos4.so" swapped from CM11.
- Because the lights.xxxx.so under CM11 have a different file name "lights.msm7x27.so" so it must be renamed in "lights.exynos4.so".
- set file permissions to 644
- reboot the rom
- Install STweaks and activate BLN. Now BLN should be work.
-------------------------------edit 19.10.15
I have the file from my second mobile phone Samsung GTS5830.
On it the phone is the rom "cm-11-20150912-UNOFFICIAL-cooper.zip; CyanogenMod 11 [Linaro]" installed.
http://forum.xda-developers.com/galaxy-ace/s5830-develop/rom-cyanogenmod-11-t3194339
The need file called under CM11 "lights.msm7x27.so"
But I can not upload the file. I don’t have the permission here.
With this file BLN and BLNWW works for me.
--------------------------------edit 20.10.15
With the changed file, the screen brightness can not be changed, unfortunately.
-------------------------------edit 20.10.15
I have found a *.so with the BLN works and the brightness control of the display functions.
The file is from image "decuro_GALAXYS2_4.8.8_4.1.zip Jelly Bean"
I uploaded the file under http://filehorst.de/d/bfwjFnoe
Delete under "/system/ lib/hw" the original file and add the new "lights.exynos4.so".
Set file permissions to 644
So far, I could not detect any error with the file.
charlie8104 said:
Excuse my bad English.
With the Kernel DorimanX b11.0 b012 now BLN have brought to works again.
I use CM12.1 official, while I proceeded as follows:
- Create a backup from the rom first.
- Under "/system/lib/hw" I have the "lights.exynos4.so" swapped from CM11.
- Because the lights.xxxx.so under CM11 have a different file name "lights.msm7x27.so" so it must be renamed in "lights.exynos4.so".
- set file permissions to 644
- reboot the rom
- Install STweaks and activate BLN. Now BLN should be work.
Click to expand...
Click to collapse
@charlie8104 Which "lights.msm7x27.so" you are talking about i just downloaded the cm11 snapshot12 and the file name you specified is same as the file name in cm12.1
If you have that file plz upload here
Have u tested this??
If this is the cause of the problem, it shouldn't be too hard to implement to the kernel. :good:
Thanks, gsstudios
Thanks for edit i will try it out
EDIT: BLN worked but m not able to control screen brightness it always stay high
EDIT: It works now..Thanks Man
charlie8104 said:
Excuse my bad English.
With the Kernel DorimanX b11.0 b012 now BLN have brought to works again.
I use CM12.1 official, ...
-------------------------------edit 20.10.15
I have found a *.so with the BLN works and the brightness control of the display functions.
The file is from image "decuro_GALAXYS2_4.8.8_4.1.zip Jelly Bean"
I uploaded the file under http://filehorst.de/d/bfwjFnoe
Delete under "/system/ lib/hw" the original file and add the new "lights.exynos4.so".
Set file permissions to 644
So far, I could not detect any error with the file.
Click to expand...
Click to collapse
Don't worry about your English!
Thank you for not only providing your solution here once, but for even keeping your OP up to date with improved versions after issues got reported. @gsstudios might cherry-pick here to implement BLN in his DorimanX kernel again, if it proves to work without further issues.
So once more, thank you for investigating on that.
Hi Guys,
I have the two lights.exynos4.so compared. In the * .so that I use an entry for BLN is included.
Line 5 in the lights.exynos4.so with BLN function.
------------------------------
#####################################[############################################################################################################################################################__aeabi_unwind_cpp_pr0#strcmp#pthread_once#malloc#memset#init_globals#free#open#sprintf#write#close#__android_log_print#__errno#__stack_chk_fail#__stack_chk_guard#pthread_mutex_lock#pthread_mutex_unlock#load_settings#fopen#fgetc#fclose#load_module_type#fread#pthread_mutex_init#NOTIFICATION_FILE_BLN#NOTIFICATION_FILE_CM#PANEL_FILE#BUTTON_FILE#HMI#__cxa_finalize#__dso_handle#__INIT_ARRAY__#__FINI_ARRAY__#__exidx_end#__exidx_start#__data_start#_edata#__bss_start#__bss_start__#_bss_end__#__bss_end__#__end__#_end#_stack#liblog.so#libc.so#libstdc++.so#libm.so#lights.exynos4###################################################### #######
------------------------------
The entry "NOTIFICATION_FILE_BLN" is completely missing in the original CM12.1 File.
The BLN entry would probably take place before the decompiled File Android Image is constructed.
Hi all, can't get this to work, is it that I need DorimanX kernel to do it? I thought you could do it with the stock CM12.1 kernel.
You need DorimanX.
Stock doesn't support BLN at all.
can someone attach the .so file? i can't seem to properly access the uploader's site...
:good:
souler456 said:
can someone attach the .so file? i can't seem to properly access the uploader's site...
:good:
Click to expand...
Click to collapse
@souler456
Hope this will help
EDIT: Check if it's working for you or not? Don't know why it's not working for me
sonupm said:
@souler456
Hope this will help
EDIT: Check if it's working for you or not? Don't know why it's not working for me
Click to expand...
Click to collapse
Yep. Working on my side. You changed permissions?
:good:
souler456 said:
Yep. Working on my side. You changed permissions?
:good:
Click to expand...
Click to collapse
Yes It work 1st time then I disabled capacitive buttons light and enabled it again after that BLN stopped working
sonupm said:
Yes It work 1st time then I disabled capacitive buttons light and enabled it again after that BLN stopped working
Click to expand...
Click to collapse
Try deactivate/active your BLN settings in Stweaks/Synapse...
:good:
souler456 said:
Try deactivate/active your BLN settings in Stweaks/Synapse...
:good:
Click to expand...
Click to collapse
Leave it. I don't use it anyways just wanted to help you and its working for you then no probs here:good:
You are on DU 9.8 Right ?? and I am on cm12.1 with Dorimanx by gsstudios. So I think this problem is kernel specific
I can make the updater script for dorimanx kernel to automate this process so we all have working BLN. Although I don't see it as a final solution, it works.
gsstudios
Edit: Got BLN working on kernel install. BLN will be fixed in next build
Edit 2: Now it isn't working
Edit 3: Now it works Seems like kernel reflash did the trick
@gsstudios
Same procedure like back then, when I tested successfully and your tests failed. So nothing much changed.
the.gangster said:
@gsstudios
Same procedure like back then, when I tested successfully and your tests failed. So nothing much changed.
Click to expand...
Click to collapse
Did you mean this method or last time when I 'attempted' to fix it? Because I'm now using this method to make BLN work on DorimanX. Last time I did the wrong thing and nothing would have happened.
gsstudios
Here is my commit which does pretty much the same thing as what the OP said but automated in the script: https://github.com/gsstudios/Dorima...mmit/d9432c3d87e26c09d6bad03ecdc22015ea4a9638
gsstudios said:
Did you mean this method or last time when I 'attempted' to fix it? Because I'm now using this method to make BLN work on DorimanX. Last time I did the wrong thing and nothing would have happened
Click to expand...
Click to collapse
I was referring to post #5 in here followed by these in the DorimanX-thread:
http://forum.xda-developers.com/showthread.php?p=63379702
http://forum.xda-developers.com/showthread.php?p=63438826
http://forum.xda-developers.com/showthread.php?p=63715347
and below. All in October.
the.gangster said:
I was referring to post #5 in here followed by these in the DorimanX-thread:
http://forum.xda-developers.com/showthread.php?p=63379702
http://forum.xda-developers.com/showthread.php?p=63438826
http://forum.xda-developers.com/showthread.php?p=63715347
and below. All in October.
Click to expand...
Click to collapse
Oh, that was my silly mistake. Wasn't clear enough I wasn't trying to use the fix back then, instead I was being a noob and replacing the file included in the kernel when I should have updated the script to replace the original file on the ROM. TL;DR, I replaced the Kernel lights.exynos4.so instead of ROM lights.exynos4.so :laugh: I am certain next build will have BLN fix
LoL
now I finally understand why our tests led to completely different results.