Hi this is my first kernel. I'm just doing this to get my feet wet before i go after the big one. This is based of the 2.6.35.14 HTC released source code so its for GB only.
Features:
OC
UV
Tweaked I/O
BFS
SLQB
JRCU
ZCache
Zram
Lot's of tweaking
Downloads:
Here
GPL Compliance
irc is at #TeamNightmareSense at freenode
Changelog
TEST 1
Initial Release
Gingerbread? Hmm, lol
Sent from my HTC_Amaze_4G using Tapatalk 2
EclipzeRemix said:
Gingerbread? Hmm, lol
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
I'm just starting out Eclipze be nice lol well since i am just starting out if anyone has anything that might help me or even if it's something you think i know but not sure just post it here i'm trying to get good at this so i can get us a nice ics kernel but as of know i don't know much so please help
just geting your feet wet... what happens if i push you in?
EDIT: quick question.... couldnt we just patch the gb kernel up to 3.0? so that it work with ics? then use that to make a aosp kernel?
ziggy46 said:
just geting your feet wet... what happens if i push you in?
Click to expand...
Click to collapse
Then i might cry lol
quick question.... couldnt we just patch the gb kernel up to 3.0? so that it work with ics? then use that to make a aosp kernel?
i've seen it happen before and i already know i have someone who could help us do it
ziggy46 said:
quick question.... couldnt we just patch the gb kernel up to 3.0? so that it work with ics? then use that to make a aosp kernel?
i've seen it happen before and i already know i have someone who could help us do it
Click to expand...
Click to collapse
Your asking the wrong guy i guess it's possible but for now i'm working on this https://github.com/Sportsstar89/htc-msm8660-ics i'll check
sportsstar89 said:
Your asking the wrong guy i guess it's possible but for now i'm working on this https://github.com/Sportsstar89/htc-msm8660-ics i'll check
Click to expand...
Click to collapse
i check up with my friend, his username is b_randon14. he is doing the patch up for the motorola triumphs kernel source.
oh and the good old pyramid kernel source you working on porting it?
EDIT: if you want to add governors to the kernel, they go in arch/arm/mach-msm (at least thats what ive been told)
ziggy46 said:
i check up with my friend, his username is b_randon14. he is doing the patch up for the motorola triumphs kernel source.
oh and the good old pyramid kernel source you working on porting it?
EDIT: if you want to add governors to the kernel, they go in arch/arm/mach-msm (at least thats what ive been told)
Click to expand...
Click to collapse
Right now i'm just working on getting it compiled if you could ask your friend why i keep getting
Code:
CC arch/arm/mach-msm/8x60-lte/sdio_al.o
arch/arm/mach-msm/8x60-lte/sdio_al.c:3779: error: expected identifier or '(' before '{' token
make[2]: *** [arch/arm/mach-msm/8x60-lte/sdio_al.o] Error 1
make[1]: *** [arch/arm/mach-msm/8x60-lte] Error 2
make: *** [arch/arm/mach-msm] Error 2
with this file http://pastebin.com/MiLUgXzT that would be great
and another thing http://www.howopensource.com/2011/08/how-to-upgrade-or-patch-latest-kernel-3-0-in-ubuntu-and-fedora/
sportsstar89 said:
Right now i'm just working on getting it compiled if you could ask your friend why i keep getting
Code:
CC arch/arm/mach-msm/8x60-lte/sdio_al.o
arch/arm/mach-msm/8x60-lte/sdio_al.c:3779: error: expected identifier or '(' before '{' token
make[2]: *** [arch/arm/mach-msm/8x60-lte/sdio_al.o] Error 1
make[1]: *** [arch/arm/mach-msm/8x60-lte] Error 2
make: *** [arch/arm/mach-msm] Error 2
with this file http://pastebin.com/MiLUgXzT that would be great
and another thing http://www.howopensource.com/2011/08/how-to-upgrade-or-patch-latest-kernel-3-0-in-ubuntu-and-fedora/
Click to expand...
Click to collapse
ok ill pm him and see what he says. (i will text him to get him to read it quicker lol)
and did you mess with the "sdio_al.c" file at all? the error tells you that the problem happened on line 3779 of that file...
Code:
CC arch/arm/mach-msm/8x60-lte/sdio_al.o
arch/arm/mach-msm/8x60-lte/sdio_al.c:[COLOR="Red"]3779[/COLOR]: error: expected identifier or '(' before '{' token
make[2]: *** [arch/arm/mach-msm/8x60-lte/sdio_al.o] Error 1
make[1]: *** [arch/arm/mach-msm/8x60-lte] Error 2
make: *** [arch/arm/mach-msm] Error 2
try looking at that file
ziggy46 said:
ok ill pm him and see what he says. (i will text him to get him to read it quicker lol)
and did you mess with the "sdio_al.c" file at all? the error tells you that the problem happened on line 3779 of that file...
Code:
CC arch/arm/mach-msm/8x60-lte/sdio_al.o
arch/arm/mach-msm/8x60-lte/sdio_al.c:[COLOR="Red"]3779[/COLOR]: error: expected identifier or '(' before '{' token
make[2]: *** [arch/arm/mach-msm/8x60-lte/sdio_al.o] Error 1
make[1]: *** [arch/arm/mach-msm/8x60-lte] Error 2
make: *** [arch/arm/mach-msm] Error 2
try looking at that file
Click to expand...
Click to collapse
I did because it was calling a function that was there that wasn't used and it caused it to not compile so i removed that line i have to learn more C
ok well i pm'ed him.
do you have the original file before your edit so i can look at it? also, what distro are you using and what are your build commands? imma take a crack at it
one thing i can say is that that line i circled almost looks out of place and could be that unsuspected ")"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ziggy46 said:
ok well i pm'ed him.
do you have the original file before your edit so i can look at it? also, what distro are you using and what are your build commands? imma take a crack at it
one thing i can say is that that line i circled almost looks out of place and could be that unsuspected ")"
Click to expand...
Click to collapse
Possibly yep its on the git before i played with it im using Ubuntu 11.10 and its make sportsstar_ruby_defconfig
then
make -jx (x=How ever many cores you have)
im a semi experienced C/C#/C++ coder. maybe I can be of some help later. ill keep an eye on the thread
sebastimau said:
im a semi experienced C/C#/C++ coder. maybe I can be of some help later. ill keep an eye on the thread
Click to expand...
Click to collapse
Thanks all help aboard just if you have any free time and you don't mind looking at the git and messing around a little all help is appreciated
sportsstar89 said:
Possibly yep its on the git before i played with it im using Ubuntu 11.10 and its make sportsstar_ruby_defconfig
then
make -jx (x=How ever many cores you have)
Click to expand...
Click to collapse
awesome, that is terribly easy.
and the laptop i will be building from is a single core with 512mb of ram. (i know, its a beast lol)
sebastimau said:
im a semi experienced C/C#/C++ coder. maybe I can be of some help later. ill keep an eye on the thread
Click to expand...
Click to collapse
this could possibly help alot
ziggy46 said:
awesome, that is terribly easy.
and the laptop i will be building from is a single core with 512mb of ram. (i know, its a beast lol)
this could possibly help alot
Click to expand...
Click to collapse
Yay cool aid man and it takes about 5 min to compile on my quad with 8gb so it might take you a little bit longer
sportsstar89 said:
Yay cool aid man and it takes about 5 min to compile on my quad with 8gb so it might take you a little bit longer
Click to expand...
Click to collapse
it will probably takes as long as your computer would to build ics... -_- lol
but i will be getting this soon so it doesnt matter check it out!
oh, and do i need to have any toolchain installed? like gnc or gcc (whatever its called...)
sportsstar89 said:
Thanks all help aboard just if you have any free time and you don't mind looking at the git and messing around a little all help is appreciated
Click to expand...
Click to collapse
i gave you your 1001 , and gave you 2 blocks filled
Related
Hey all, I thought I would put together a quick guide on how to port modules built for other devices. Since we share the same CPU as the One X and many other phones it's possible some of the mods for them are compatible with our phones too. In this case I was wanting to give coolbho3000's overclock module a try to see if it would work.
Please keep in mind that this will not always work and it's still better to try and use a module built specifically for your setup. Using a module that's not made for your device can cause all kinds of issues and seriously affect system stability. Always make sure you read the original instructions to make sure you understand how it works and how it's intended to be used.
Neither me, XDA or the module's author are responsible for anything that happens to your device. You and you alone are responsible for your actions.
First thing you'll want to do is try to load it as is, it probably won't work but it'll at least give you a place to start. In this case I'm using the overclock module from the One X so I used:
Code:
adb push krait_oc.ko /data/local/krait_oc.ko
adb shell
su
insmod /data/local/krait_oc.ko
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If it is successful it won't say anything, but there you can see it failed as expected. In order to find out why it failed we'll need to run dmesg and look for where it tried to load it.
Code:
dmesg | grep "krait_oc"
There we can see module_layout is where the issue is. What we can do now is pull one of the already installed modules off of the device and use it as a reference, in this case I used lcd.ko since it has an easy name to type. Grab your two modules and using linux run modprobe to find a value for module_layout. (If you only have Windows available skip to next step)
Code:
modprobe --dump-modversions lcd.ko
Now that we know what to look for open up the module in a hex edit and search for "module_layout." Immediately before it you will see the value that needs to be changed, but, keep in mind that it is little endian so the bytes are read backwards. In the view of lcd.ko on the right you can see the value we previously got of '37 19 bc d3' is saved as 'd3 bc 19 37'.
Change those four bytes to match and then save the module under a new name so it is not confused with the original.
Once you save the edited module its time to push it to the device again and try once more.
And success! Sometimes you'll also need to edit the module to accept the current kernel version you are using, but the process should be similar as to what's here.
So, uhhhh . . . you gonna share that modded kernel?
utnick said:
So, uhhhh . . . you gonna share that modded kernel?
Click to expand...
Click to collapse
Kernel is still the same, this is just for the modules
*sigh* I wish I knew what that meant. Can I ask to you to explain it to me please? And does this mean you have the ability to port the kernel to OC an EVO LTE?
Got overclock working fine. Great thanks Haus
Can anyone make a zip? Pretty please.
You can't make a zip. you have to mod the ko file yourself and launch it yourself.
utnick said:
*sigh* I wish I knew what that meant. Can I ask to you to explain it to me please? And does this mean you have the ability to port the kernel to OC an EVO LTE?
Click to expand...
Click to collapse
Think of modules as sort of like an add-on for kernels, except that they're saved as part of the ROM instead of on boot. I used the one-x overclock module here, but since it's not made for the evo it may not be completely stable. Plus there are other changes that need to be made to the thermal profiles according to his original post.
Ideally coolbho3000 will be willing to create one for us and officially support it. I've already reached out to him about it so hopefully we'll hear something back soon.
Hey I know quadrants don't mean much but do you think you could get us a screenshot of our phones scores when overclocked?
Thanks for the guide by the way I will definitely try this when I have time...
Red.
So glad you're here haus :thumbup:
Sent from my EVO using xda premium
it there a way to remove a module, and replace a new edited ported *.ko?
all of this is done in recovery?
if trying to replace a module should just get to modding the kernel itself?
Great guide, I've been looking for something like this. So could I use this method to get USB hosting working? I know the one x (AT&T), has a custom kernel that supports it.
XDA University is Coming! Can't wait to learn more...
Immediately before it you will see the value that needs to be changed, but, keep in mind that it is little endian so the bytes are read backwards. In the view of lcd.ko on the right you can see the value we previously got of '37 19 bc d3' is saved as 'd3 bc 19 37'.
Click to expand...
Click to collapse
That's not little endian and reading backwards is not little endian when the original is not big endian. Little/big endians are in terms of byte size orders.
Good tutorial.
exSD said:
That's not little endian and reading backwards is not little endian when the original is not big endian. Little/big endians are in terms of byte size orders.
Good tutorial.
Click to expand...
Click to collapse
Thank you, but "byte size orders?"
xHausx said:
Thank you, but "byte size orders?"
Click to expand...
Click to collapse
Byte value order. Hex value.
thanks a lot
thanks a lot for your tutorial, and congrats,
i tried your tutorial and i cant modprob on linux, i atached the screenshot of what happenz,
i try "modprobe --dump-modversions usbhid.ko" and i receive a blank line with nothing, i tried with other modules and it do the same, but for the one who was extracted from my phones modules folder, it works,
and i also have a daught, i search for "module_layout" only or any other values?
hackerse7en said:
thanks a lot for your tutorial, and congrats,
i tried your tutorial and i cant modprob on linux, i atached the screenshot of what happenz,
i try "modprobe --dump-modversions usbhid.ko" and i receive a blank line with nothing, i tried with other modules and it do the same, but for the one who was extracted from my phones modules folder, it works,
and i also have a daught, i search for "module_layout" only or any other values?
Click to expand...
Click to collapse
Make sure you have spaces between your arguments. It also depends on what value it's telling you is incorrect, it may be different depending on which one you're trying to use.
xHausx said:
Make sure you have spaces between your arguments. It also depends on what value it's telling you is incorrect, it may be different depending on which one you're trying to use.
Click to expand...
Click to collapse
i already did that i think itś something wrong with the module because i put them i the same directory and the exact same commands and it just dont work, i atached some screenshots and the modules.
thanks for helping me
hackerse7en said:
i already did that i think itś something wrong with the module because i put them i the same directory and the exact same commands and it just dont work, i atached some screenshots and the modules.
thanks for helping me
Click to expand...
Click to collapse
i just cant undestand, if someone can help me.
CyanogenMod 11 for the LG G2 mini D620r
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
All Credits so far go to Quarx and his project CM11 for LG L90
What i have done so far:
Setup Ubuntu on my Laptop
Installed CM dev environment like described here!
Made a new device folder following THIS guide and build some recoveries.
Took the sources from CM11 for LG L90 and integrated them to my build environment.
CM11 for LG L90 builds fine but i can not test it.
Took the files i thought we need from L90 and put them to my d620 tree.
Trial and error till it compiled for d620.
For the kernel i use original LG sources extracted to kernel/lge/msm8226.
Switched to kernel source from Quarx and tweaked it for d620.
Find sources i use here.
Unfortunately the kernel i have build leads to boot loops. (Yes i have wiped everything)
If i only install the system with the original LG stock kernel i get an security error.
How can i find out why the kernel boot loops?
(had to use the dt.img from stock kernel because mine didn't work, phone gets stuck in fastboot)
Kernel now boots with recovery.
Touch only works if i copy the FW to system folder.
CM11 now works quit well.
Known issues:
- NFC not working at all
- Vibration not working at all
- Back/Main camara has overexposure on bright scenes
- LTE can only be activated by adding quick setting for LTE
Testers welcome.
Video review from simo14
Alpha: Download
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any help appreciated.
Port rom!!
Good job! I think You can port rom l90 for g2 mini. Read it: http://forum.xda-developers.com/showthread.php?t=2545618 (my English is bad, sorry!!)
I think we need a "extract-files.sh" to extract device proprietary files with connected and enabled usb debbuging. I do some research but didnt luck. My English is weak and i don't know how to do this script. I know its necesary for boot and compile with success.
Maybe Quarx can help us.
Probably kernel boot loops because you compile with CM source and that its not compatible with stock rom.
Regards.
this is great progress
im trying like hell to make a custom recovery.
take a look at this zaaap
http://forum.xda-developers.com/android/help/building-kernel-error-lg-g2-mini-t2853390
maybe you could help me out a bit?
I'm extracted a system folder from TWRP backup and try to port by paste>copy method. I need a META-INF folder for our phone. I don't know how to make it.
Ok i found it.
I make four builds with AndroidKitchen but its always a update-binary script error.
Any help?
make -j4 otatools give me that error.
/media/radek/bee9f4ae-71a6-4ed8-9153-7dd674ea803d/CM11/out/target/product/generic/obj/APPS/SignatureTest_intermediates
"ebtables is disabled on this build"
find: `src': Nie ma takiego pliku ani katalogu
grep: /build/target/board/generic/recovery.fstab: Nie ma takiego pliku ani katalogu
No private recovery resources for TARGET_DEVICE generic
build/core/tasks/kernel.mk:91: **********************************************************
build/core/tasks/kernel.mk:92: * Kernel source found, but no configuration was defined *
build/core/tasks/kernel.mk:93: * Please add the TARGET_KERNEL_CONFIG variable to your *
build/core/tasks/kernel.mk:94: * BoardConfig.mk file *
build/core/tasks/kernel.mk:95: **********************************************************
make: Nie ma nic do zrobienia w `otatools'.
/build/target/board/generic/recovery.fstab exists in the directory.
When try to compile kernel:
*** Can't find default configuration "arch/arm/configs/w7ds_open_cis_defconfig"!
***
make[2]: *** [w7ds_open_cis_defconfig] Błąd 1
make[1]: *** [w7ds_open_cis_defconfig] Błąd 2
make: *** [w7ds_open_cis_defconfig] Błąd 2
That's mean the Quarx kernel should work for us?
partyzant_x said:
When try to compile kernel:
*** Can't find default configuration "arch/arm/configs/w7ds_open_cis_defconfig"!
***
make[2]: *** [w7ds_open_cis_defconfig] Błąd 1
make[1]: *** [w7ds_open_cis_defconfig] Błąd 2
make: *** [w7ds_open_cis_defconfig] Błąd 2
That's mean the Quarx kernel should work for us?
Click to expand...
Click to collapse
w7ds is an LG L90 dual sim.
Go to your kernel folder /arch/arm/configs and look for a g2m... ...defconfig where the name fits your device.
Try to compile with the g2m defconfig should work.
You might be missing touch and other hardware if you didn't get all property blobs needed for our device.
This is the point where I got struck at the moment.
/tmp/ccfkEagn.s: Assembler messages:
/tmp/ccfkEagn.s:166: Warning: swp{b} use is deprecated for this architecture
/tmp/ccfkEagn.s:192: Warning: swp{b} use is deprecated for this architecture
CC arch/arm/mach-msm/smd_private.o
CC arch/arm/mach-msm/smem.o
CC arch/arm/mach-msm/smd_init_dt.o
arch/arm/mach-msm/smd_init_dt.c:24:25: fatal error: smd_private.h: No such file or directory
compilation terminated.
make[2]: *** [arch/arm/mach-msm/smd_init_dt.o] Błąd 1
make[1]: *** [arch/arm/mach-msm] Błąd 2
make: *** [zImage] Błąd 2
Click to expand...
Click to collapse
I'm try to compile the LG source with:
Run following scripts to build kernel
a) cd kernel
c) make ARCH=arm CROSS_COMPILE=../prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi- g2m_global_com_defconfig zImage
Zaaap can you share your device tree?
Ok. I fixed the errors. Now I have "zImage" how flash that?
What did you do to fix the errors? And wich toolchain did you use?
The zimage comes with some .ko files? You have to make a .zip file of those and flash it through custom recovery or a flash app from market! Like rashr
I fixed the errors that occurred when compiling. Compile the source cm and lg according to instructions in the readme.txt from lg. Thanks Zaaap changed command from w7ds_open_cis_defconfig on g2m_global_com_defconfig. After compiling I received two files zImage and Image.
partyzant_x said:
I fixed the errors that occurred when compiling. Compile the source cm and lg according to instructions in the readme.txt from lg. Thanks Zaaap changed command from w7ds_open_cis_defconfig on g2m_global_com_defconfig. After compiling I received two files zImage and Image.
Click to expand...
Click to collapse
Don't flash the zImage as it is only a part of the needed boot.img.
There is a command like 'make boot.img'. I'll have to look for it.
I'll explain more later when I get to my laptop.
partyzant_x said:
I fixed the errors that occurred when compiling. Compile the source cm and lg according to instructions in the readme.txt from lg. Thanks Zaaap changed command from w7ds_open_cis_defconfig on g2m_global_com_defconfig. After compiling I received two files zImage and Image.
Click to expand...
Click to collapse
look at the last stages of this how to.
http://playfuldroidz.com/wiki/Compiling_a_Kernel#Making_a_Flashable_Zip
Now I'm trying to create a device tree manually. A bit of getting lost in this. Zaaap can share with your device tree. Rather than create new ones we can work on one and make any fixes.
partyzant_x said:
I fixed the errors that occurred when compiling. Compile the source cm and lg according to instructions in the readme.txt from lg. Thanks Zaaap changed command from w7ds_open_cis_defconfig on g2m_global_com_defconfig. After compiling I received two files zImage and Image.
Click to expand...
Click to collapse
where did you find the readme.txt where it said wich toolchain you should use?
invaderjohn said:
look at the last stages of this how to.
http://playfuldroidz.com/wiki/Compiling_a_Kernel#Making_a_Flashable_Zip
Click to expand...
Click to collapse
Give me: Error executing updater binary in zip.
Downloaded kernel source from lg site. Unpack it and there is two files readme.txt and packed kernel source, unpacked it copy kernel folder to cm source then cd kernel and:
make ARCH=arm CROSS_COMPILE=../prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi- g2m_global_com_defconfig zImage
When I have error for example:
arch/arm/mach-msm/smd_init_dt.c:24:25: fatal error: smd_private.h: No such file or directory
compilation terminated.
make[2]: *** [arch/arm/mach-msm/smd_init_dt.o] Błąd 1
make[1]: *** [arch/arm/mach-msm] Błąd 2
make: *** [zImage] Błąd 2
Click to expand...
Click to collapse
Then open smd_init_dt.c find line with smd_private.sh. Its look include <smd_private.sh> and change it to include "smd_private.sh".
Sorry for my English.
Make boot.img
Here you can find the official doc about making boot.img: HERE
I took the device tree from Quarx found here made a copy in a new folder 'd620' but i think 'g2m' would have been correct for phone.
Find my device folder here.
Find my vendor folder here.
The kernel source is located under kernel/lge/msm8226
I normaly compile a recovery and see if the kernel works with it.
Thus i don't risk a semi brick because if the kernel is bad, then recovery may not start but system will start and i can flash an other recovery with a new kernel.
If recovery boots, i can use adb to get dmesg.log and see what works and what not.
On my last try, touch didn't initialize complete.
Thanks Zaaap.
I broke something in the source of CM. I have to download again. Can someone check zImage which I compiled.
partyzant_x said:
Thanks Zaaap.
I broke something in the source of CM. I have to download again. Can someone check zImage which I compiled.
Click to expand...
Click to collapse
It boot, but takes long to do so and there is no touch.
This is the same problem i have.
We need to get the correct touch firmware + patch.
Find log attached.
Kernel boots with touch
Got touch working.
The firmware doesn't get copied to /system/lib/firmware.
When i copy the firmware in via AIK kernel boots fast and with touch.
Now i will investigate how to include the FW in compile process.
Very good news. I asked for help a member of XDA @ moonbutt74. I hope he will have the time and inclination to help us.
Zaaap72 said:
Got touch working.
The firmware doesn't get copied to /system/lib/firmware.
When i copy the firmware in via AIK kernel boots fast and with touch.
Now i will investigate how to include the FW in compile process.
Click to expand...
Click to collapse
partyzant_x said:
Very good news. I asked for help a member of XDA @ moonbutt74. I hope he will have the time and inclination to help us.
Click to expand...
Click to collapse
okay so root is good
look in /proc for
/proc/config.gz
it might be there it might not. i need the stock boot.img please. looking through source right now and unsure of which defconfig.
your modules also depend on libraries in system/vendor - you need that entire directory for your device tree. you may also need
manufacturer/device specific/proprietary libraries from system/lib
starting in /system/vendor type in terminal
strings [nameoflib].so | grep "\.so"
these will bring up a list of additional libraires needed. the ones you already have in vendor don't worry about. the ones you
will find in system/lib are the additional ones you need to get for your device tree. go to the thread i'm working in with restl3ss and read through the whole thing but please do not post any questions there. post here use the mention function @moonbutt74
or pm me or click reply button below any of my posts in this thread and i will know by email.
m
on defconfig readme suggests w7ds_open_cis_defconfig but will try g2m_global_com_defconfig
So,
the G Pad (v500) comes with in two versions.
One version has the S5K4E5YA as back camera.
Other version hast the OV5693 as back camera.
As we know the S5K4E5YA already has support in AOSP and CM ROMs and kernels.
So I tried to add the missing files and references to the CM kernel.
https://github.com/drbeat/kernel_lge_v500/commit/7c9beb4a27fc65b60786616c5c966e53632dfc5d
These are changes I picked out from the "V50020D" kernel sources.
In compiling I get this error
Code:
drivers/media/video/msm/eeprom/ov5693_eeprom.c:68:2: error: extra brace group at end of initializer
{FALSE, 0, 0, 1},
^
drivers/media/video/msm/eeprom/ov5693_eeprom.c:68:2: error: (near initialization for ‘ov5693_calib_supp_info’)
drivers/media/video/msm/eeprom/ov5693_eeprom.c:68:2: warning: excess elements in struct initializer
drivers/media/video/msm/eeprom/ov5693_eeprom.c:68:2: warning: (near initialization for ‘ov5693_calib_supp_info’)
drivers/media/video/msm/eeprom/ov5693_eeprom.c:82:27: error: invalid application of ‘sizeof’ to incomplete type ‘struct msm_calib_id’
{&ov5693_id_data, sizeof(struct msm_calib_id)}, /* */
^
drivers/media/video/msm/eeprom/ov5693_eeprom.c: In function ‘ov5693_format_iddata’:
drivers/media/video/msm/eeprom/ov5693_eeprom.c:88:2: error: invalid use of undefined type ‘struct msm_calib_id’
ov5693_id_data.sensor_id= (uint16_t)ov5693_idcalib_data;
^
drivers/media/video/msm/eeprom/ov5693_eeprom.c:88:2: warning: statement with no effect [-Wunused-value]
make[5]: *** [drivers/media/video/msm/eeprom/ov5693_eeprom.o] Error 1
make[4]: *** [drivers/media/video/msm/eeprom] Error 2
make[4]: *** Waiting for unfinished jobs....
LD drivers/media/video/msm/gemini/built-in.o
make[3]: *** [drivers/media/video/msm] Error 2
make[2]: *** [drivers/media/video] Error 2
make[1]: *** [drivers/media] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [drivers] Error 2
Am I missing some changes?
Maybe someone know how this can be fixed so everyone gets the same experience.
EDIT:
OK I got it compiling.
https://github.com/drbeat/kernel_lge_v500/commit/7fce6ccd0c82fcdb17c22f4053db4d6703f1c436
Now I need someone with OV5693 to test it out
EDIT 2:
The binaries may be lacking.
I will look into that
EDIT 3:
So I have made a ZIP containing binaries and a kernel with ov5693 drivers
I need someone to test it out
DOWNLOAD: removed!
will upload a new version soon
EDIT 4:
DOWNLOAD: https://www.androidfilehost.com/?fid=95897840722648539
I thought ov5663 was the one that does not work. Here is a log for a ov5693 working with stock AOSP.
http://forum.xda-developers.com/showpost.php?p=57338503&postcount=5
Deltadroid said:
I thought ov5663 was the one that does not work. Here is a log for a ov5693 working with stock AOSP.
http://forum.xda-developers.com/showpost.php?p=57338503&postcount=5
Click to expand...
Click to collapse
there is no "ov5663"
the back camera which is not working is "ov5693"
Then I'm curious why the person who posted that log says his cameras are working.
Deltadroid said:
Then I'm curious why the person who posted that log says his cameras are working.
Click to expand...
Click to collapse
so to clear it up for you
front cam is always "IMX119"
back camera is either "S5K4E5YA" or "OV5693"
there is no "OV5663"
that guy posted dmesg before he flashed AOSP
since his back camera is working he has a "S5K4E5YA" module
just ask him to do another dmesg now. you will see that his results will be IMX119 and S5K4E5YA since AOSP and CM dont support OV5693
Thanks for clearing that up. I'm sure lots of others were/are confused too.
I bet of you changed the title of this thread to something like "fix for back camera" then people would understand the purpose of this thread better and offer to test.
Deltadroid said:
I bet of you changed the title of this thread to something like "fix for back camera" then people would understand the purpose of this thread better and offer to test.
Click to expand...
Click to collapse
i still have to find the right binaries to make a working zip
I have a 50020D, I'll take it for a spin and report back later.
UPDATE: I got stuck at boot logo after flashing, but I managed to restore from my backup.
To tell the truth I'm not using stock CM, but a Team Vanir/Commotio ROM. Although they supposed to be using the same kernel and device tree as CM.
Munszu said:
I have a 50020D, I'll take it for a spin and report back later.
UPDATE: I got stuck at boot logo after flashing, but I managed to restore from my backup.
To tell the truth I'm not using stock CM, but a Team Vanir/Commotio ROM. Although they supposed to be using the same kernel and device tree as CM.
Click to expand...
Click to collapse
thx for reporting
do you have a backcam which is not working?
ckret said:
thx for reporting
do you have a backcam which is not working?
Click to expand...
Click to collapse
Yeah, I do.
It's only working on stock ROMs, so I guess its the same.
If you can tell me how, I can send you a log or something to help you.
uploaded a new zip
this one doesnt give bootloop.
still do a backup and report back please
ckret said:
uploaded a new zip
this one doesnt give bootloop.
still do a backup and report back please
Click to expand...
Click to collapse
I've tried and the tablet booted up well this time, but the fix didn't work unfortunately.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
can some one that has ov5693 please test this zip and see if the cam works
it uses the same kernel that ckret has in his zip file
the only thing I added was more of the camera binaries from 20d
make sure you back up first
https://www.mediafire.com/?gx83ty2ytxdc2wt
I tried it but it got me into a boot loop.
I hope you figure it out \o
PS: Using Mahdi's Kit Kat Rom.
thanks for testing, sorry about the loop
since I dont have this phone, I dont think I will be able to help much more, sorry
hroark13 said:
can some one that has ov5693 please test this zip and see if the cam works
it uses the same kernel that ckret has in his zip file
the only thing I added was more of the camera binaries from 20d
make sure you back up first
https://www.mediafire.com/?gx83ty2ytxdc2wt
Click to expand...
Click to collapse
its not that simple.
i am writing exams right now so i dont have time look into the problem
ckret said:
its not that simple.
i am writing exams right now so i dont have time look into the problem
Click to expand...
Click to collapse
I looked at your kernel commit and that looked to be right
those files I have in that zip are the correct libraries
what it is probably missing is a key in the lib camera client
there is most likely a message in the logcat that says it could not load camera.msm8960.so because it could not find a key
usually these keys could be added to
frameworks/av/camera/CameraParameters.cpp
and
frameworks/av/include/camera/CameraParameters.h
but then you would have to build cm11 again
I am pretty sure the only way you are going to get the back cam to work is with those libraries
if you grep for ov5693 in the original files / libraries it probably will not be found, if you grep the 20d files, you should find it listed in the mm-qcamera-daemon, liboemcamera.so and the 3 chromatix files
hroark13 said:
I looked at your kernel commit and that looked to be right
those files I have in that zip are the correct libraries
what it is probably missing is a key in the lib camera client
there is most likely a message in the logcat that says it could not load camera.msm8960.so because it could not find a key
usually these keys could be added to
frameworks/av/camera/CameraParameters.cpp
and
frameworks/av/include/camera/CameraParameters.h
but then you would have to build cm11 again
I am pretty sure the only way you are going to get the back cam to work is with those libraries
if you grep for ov5693 in the original files / libraries it probably will not be found, if you grep the 20d files, you should find it listed in the mm-qcamera-daemon, liboemcamera.so and the 3 chromatix files
Click to expand...
Click to collapse
its propably selinux and permission related
this most time cause bootloops
ckret said:
its propably selinux and permission related
this most time cause bootloops
Click to expand...
Click to collapse
idk
would need to see a logcat to be sure
Here is an python3 script named AAC that build ROM for you, yes.
How to get this ?
Download it on my Github : AndroidAutoCompiler
How to run it ?
Just type
Code:
python3 aac.py
in your Terminal.
Progress of the Project :
06 Nov 2015 : First script & First Upload
Next build will integrate an graphical interface, powered by TKinter. Here is a tease :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Issues :
\
Don't forget to contribute :
Donate with Paypal
Version Infos
Status : Very very pre-alpha
Created 061115
Last Modif 191115
AndroGeek974 said:
Hi there,
I've just coded a script in Python3 to build ROMs more easily and decided to share it here.
It's very basic but I think it can help people that wants to start ROM development. Also it able you to save a lot of times.
Just put the script at the root of your linux machine and run it with :
Code:
python3 aac.py
...and follow instructions.
That's all !
Don't hesitate to test it.
You can download the script on my Github : https://github.com/AndroGeek974/AndroidAutoCompiler
AndroGeek.
Click to expand...
Click to collapse
I've forked your script and am adding some more ROMs, default statements and also fixing some typos. Will let you know when everything's done and I'm ready to do a commit.
Sent from a Cool Phone stuck with crappy KingUser
MSF Jarvis said:
I've forked your script and am adding some more ROMs, default statements and also fixing some typos. Will let you know when everything's done and I'm ready to do a commit.
Sent from a Cool Phone stuck with crappy KingUser
Click to expand...
Click to collapse
That's cool ! Waiting for your update.
AndroGeek974 said:
That's cool ! Waiting for your update.
Click to expand...
Click to collapse
Just one thing - I can't seem to find the link to AOKP's KitKat branch. Can you just look it up and post it here ???
Sent from a Cool Phone stuck with crappy KingUser
AndroGeek974 said:
That's cool ! Waiting for your update.
Click to expand...
Click to collapse
https://github.com/MSF-Jarvis/AndroidAutoCompiler
I have to leave for a few days so I've made an incomplete commit for you to merge and build upon.
Sent from a Cool Phone stuck with crappy KingUser
MSF Jarvis said:
https://github.com/MSF-Jarvis/AndroidAutoCompiler
I have to leave for a few days so I've made an incomplete commit for you to merge and build upon.
Sent from a Cool Phone stuck with crappy KingUser
Click to expand...
Click to collapse
Thanks man, I've just seen your update, going to work on a graphical interface this night.
Really appreciate your help.
AndroGeek974 said:
Thanks man, I've just seen your update, going to work on a graphical interface this night.
Really appreciate your help.
Click to expand...
Click to collapse
Thanks. Just managed to secure internet but cant code from this phone. Maybe i'll be able to help you out with the graphical ui later.
AndroGeek974 said:
Thanks man, I've just seen your update, going to work on a graphical interface this night.
Really appreciate your help.
Click to expand...
Click to collapse
Please keep pushing changes regularly to the Github repo do that I can stay up to date with your sources and keep working on my contributions as well.
P.S. I just had an idea to upload a index file with names of devices and their code names for noobs of course. We can then proceed to also including which ROMs actually support the device. The devices can first be the popular ones, and if the script gets famous :fingerscrossed: , we can accept requests for device inclusion.
Dont worry about implementation, if you aren't familiar with file handling in Python, I'll do it.
Sent from my HTC Explorer X using Tapatalk
MSF Jarvis said:
Please keep pushing changes regularly to the Github repo do that I can stay up to date with your sources and keep working on my contributions as well.
P.S. I just had an idea to upload a index file with names of devices and their code names for noobs of course. We can then proceed to also including which ROMs actually support the device. The devices can first be the popular ones, and if the script gets famous :fingerscrossed: , we can accept requests for device inclusion.
Dont worry about implementation, if you aren't familiar with file handling in Python, I'll do it.
Sent from my HTC Explorer X using Tapatalk
Click to expand...
Click to collapse
I'm still working on that ui, it takes time, i'd never use Tkinter. I'll push when the script will be usable.
Good ideas, it can be good.
#PrayforParis
Sounds like a really interesting thread just subscribed and will be following closely. I've tried building from source before and anything that helps is great. Thanks for sharing
Sent from my SM-N920C using Tapatalk
I've wanted to build something like this for a very, very long time. Here's my [humble as hell] start to it:
https://quip.com/BO2dAOEvDGXd
https://github.com/superordinate/klouds
sawdoctor said:
Sounds like a really interesting thread just subscribed and will be following closely. I've tried building from source before and anything that helps is great. Thanks for sharing
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
faddat said:
I've wanted to build something like this for a very, very long time. Here's my [humble as hell] start to it:
https://quip.com/BO2dAOEvDGXd
https://github.com/superordinate/klouds
Click to expand...
Click to collapse
I just read through your scripts and documents and I feel its awesome. If we ever feel like it, I think the device specific script can be dynamically grepped in the linux shell to make it work for any device without manual editing by the user.
Sent from my HTC Explorer X using Tapatalk
Some progress...
AndroGeek974 said:
Some progress...
Click to expand...
Click to collapse
Really awesome Damien, you nailed it.
This was so good that I had to WhatsApp it to my computer classmates and teachers at half past eleven (right now) in the night. Hope it's up on the git coz I'm excited to work on it.
Sent from my HTC Explorer X using Tapatalk
AndroGeek974 said:
Some progress...
Click to expand...
Click to collapse
It's high time the updated gui shows up on GitHub.
Sent from my Explorer A310e using Tapatalk
MSF Jarvis said:
It's high time the updated gui shows up on GitHub.
Sent from my Explorer A310e using Tapatalk
Click to expand...
Click to collapse
Not ready at all.
AndroGeek974 said:
Not ready at all.
Click to expand...
Click to collapse
Boohoo....
Makes you look dumb when you say that. If it's not ready just make a new branch on the git repo and push it there. Call that branch beta test or something like gui test. It doesn't hurt to have some help. You keep your work synced, I'll keep mine and together we'll be able to finish it earlier than you alone.
Sent from my Explorer A310e using Tapatalk
Few things, then I am off to sleep:
1) BINGO! The plan is to use env variables, eg:
export VENDOR=asus
export DEVICE=Z00A
2) Shall we Skype sometime? I'm faddat on Skype.
faddat said:
Few things, then I am off to sleep:
1) BINGO! The plan is to use env variables, eg:
export VENDOR=asus
export DEVICE=Z00A
2) Shall we Skype sometime? I'm faddat on Skype.
Click to expand...
Click to collapse
1) The idea's awesome, and since @AndroGeek974 is taking some time in that gui thingy, I'll do a version myself using your concept.
2) I would love to, but here in India... ummm, not that good of an idea. But I'll try to, for sure.
The thread has been cold for a while so here's a quick rundown of what we all have been up to in the mean time.
1. The GUI version of the script went up at https://GitHub.com/AndroGeek974/AndroidAutoCompiler2
2. It turned out that the GUI and CLI, both versions of the script are non-functional and buggy.
3. I made many edits to both versions to attempt to fix those issues and bugs, to no avail.
4. Tired of the constant issues with AAC and AAC2, I created another GUI based repository for AAC, called AAC-Redux, that currently only supports CyanogenMod for now, but works. Link is : https://GitHub.com/MSF-Jarvis/AAC-Redux
Sent from my HTC Desire 616 dual sim customised for Puchki using Tapatalk
Hi all.
Compatibility:
Builds from r1 to r5 are for Android 7.1 Nougat only.
Builds starting with r6 are for Android 7.1.1 Nougat only.
Builds starting with r12 are for Android 7.1.2 Nougat only.
Builds starting with r19 are for Android Pie only.
Download:
https://francokernel.app
Installation:
Flash the zip in your recovery
or
Auto-flash from FK Kernel Manager app, it's magical
Changelog:
https://francokernel.app
Scroll down, choose your device & select the latest release to see the changelog.
Source:
https://github.com/franciscofranco/marlin
Follow me on socials for updates and interesting tidbits
Twitter
FK Kernel Manager video
https://www.youtube.com/watch?v=ARdNqh71D0E
Disclaimer to moderators:
Slight OT is fine, but when users decide to act stupid they should be dealt with with the appropriate means - its really annoying for me when OT turns crazy. Please put the warning/ban hammer anytime any of you think there's lack of respect and/or too much unwanted OT crap - but if it doesn't meet this criteria let the OT posts alone. Thank you.
Cheers!
I think the only thing I haven't merged yet is controls for headphone volume boost. Other standard things are already there. Due to the unfortunate fact that we still don't have a custom recovery I haven't touched the ramdisk, so you're just flashing the actual Kernel binary (plus the device tree files that are bundled to it) through the bootloader. It's really straight forward though.
I wouldn't expect any magical battery improvements yet. Although I've made some custom patches to reduce needlessly cpu idle wakeups (don't confuse this with wakelocks, totally different things), and reducing the load average, I doubt there will be any magical enhancements. Though, I wouldn't be surprised if you get 5-10% better screen on time.
Also merged some upstream patches which gave me roughly 5-10% better Geekbench results on both single and multi threaded tests due to lower lock contention & reduced overhead.
Made sure ZRAM was properly set up too, which didn't seem to be the case by looking through the entire Google's device tree.
There's other things on my patches, but nothing groundbreaking.
Everything is in my github too. You know my approach, no bull****, so don't ask me for merge/add retarded crap.
Runs badass! Can't wait for more
Is there a feature list for this kernel? The change log 404s currently.
Nice!
Can we root with this kernel....thanks for your work
NoValidTitle said:
Is there a feature list for this kernel? The change log 404s currently.
Click to expand...
Click to collapse
Literally in the second post. I haven't added the changelog file yet.
cwalker0906 said:
Can we root with this kernel....thanks for your work
Click to expand...
Click to collapse
Yes... Why couldn't you?
franciscofranco said:
Literally in the second post. I haven't added the changelog file yet.
Click to expand...
Click to collapse
I read the second post. There isn't a feature list just says what you didn't include. I also looked at git hub and didn't see anything there either. Sorry.
franciscofranco said:
Yes... Why couldn't you?
Click to expand...
Click to collapse
Thought there was a patch that had to be made in kernel...wasn't sure
NoValidTitle said:
I read the second post. There isn't a feature list just says what you didn't include. I also looked at git hub and didn't see anything there either. Sorry.
Click to expand...
Click to collapse
I wrote a lot about what I included. I don't usually write feature lists, most of the words are just buzzwords for users to feel amazed but not actually know what they mean, so for a less biased experience I just don't have feature lists.
cwalker0906 said:
Thought there was a patch that had to be made in kernel...wasn't sure
Click to expand...
Click to collapse
Nah, you can root it.
franciscofranco said:
I wrote a lot about what I included. I don't usually write feature lists, most of the words are just buzzwords for users to feel amazed but not actually know what they mean, so for a less biased experience I just don't have feature lists.
Nah, you can root it.
Click to expand...
Click to collapse
Already running and rooted, thanks
cwalker0906 said:
Already running and rooted, thanks
Click to expand...
Click to collapse
Awesome!
Ok, I know... I am a newb! But I got a question for you Franco....
When I download the kernel I try to extract it using 7zip and get an error.
Should I not try to extract? What am I doing wrong here? Never had any issue like this before. Used your kernel on lots of devices and this is the first time I got this issue.
Anyone feel free to chime in...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-Scott
Scott said:
Ok, I know... I am a newb! But I got a question for you Franco....
When I download the kernel I try to extract it using 7zip and get an error.
Should I not try to extract? What am I doing wrong here? Never had any issue like this before. Used your kernel on lots of devices and this is the first time I got this issue.
Anyone feel free to chime in...
-Scott
Click to expand...
Click to collapse
It's not a zip, it's the Kernel binary.
Just seen this came out! Rooted and flashed FK1 Loving it so far Franco can't wait for more features! Any change of getting rid of the screen before the boot logo for it being modified? As always great work Fransisco
xReaper7x said:
Just seen this came out! Rooted and flashed FK1 Loving it so far Franco can't wait for more features! Any change of getting rid of the screen before the boot logo for it being modified? As always great work Fransisco
Click to expand...
Click to collapse
Nope not possible
franciscofranco said:
It's not a zip, it's the Kernel binary.
Click to expand...
Click to collapse
Ahhh, Thank you! I am running it now!
Sorry for being a newb, lol
-Scott
Scott said:
Ahhh, Thank you! I am running it now!
Sorry for being a newb, lol
-Scott
Click to expand...
Click to collapse
It's ok, we don't born knowning it all
The Android subreddit would always rave about your kernel during the Nexus 4 days. Excited to see future development.