Related
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
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
Hello guys,
I'm curious about how to build a Dirty Unicorns rom for our device (ZTE Axon 7), which has not been build yet. I searched before in other threads but did not find any wort solution. I followed kindly this guide: https://raw.githubusercontent.com/nathanchance/Android-Tools/master/Guides/Building_AOSP.txt, but got an error after typing the command: "breakfast axon7".
The error itself:
** Don't have a product spec for: 'du_axon7'
** Do you have the right repo manifest?
ls: cannot access 'device/*/axon7/du.mk': No such file or directory
build/core/product_config.mk:246: *** Can not locate config makefile for product "du_axon7". Stop.
** Don't have a product spec for: 'du_axon7'
** Do you have the right repo manifest?
Click to expand...
Click to collapse
When typing "lunch", my device is also not listed there. And when typing 1 (full-eng) I get this:
Go ahead and pick a number... 1
Trying dependencies-only mode on a non-existing device tree?
============================================
DU_VERSION=
TARGET_BUILD_VARIANT=eng
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a
TARGET_CPU_VARIANT=generic
BUILD_ID=NJH47B
OUT_DIR=/home/mariusfl0rian/DU/out
============================================
[email protected]:~/DU$
Click to expand...
Click to collapse
As I'm a newbie when building roms, I need your help. How can I solve this?
Thanks in advance
Link to the device tree you're using?
osas514 said:
Link to the device tree you're using?
Click to expand...
Click to collapse
The thing is, I followed the guide and there was no need of my device tree. I'm a noob, it's the first time I try to build a rom for my device.
mariusfl0rian said:
The thing is, I followed the guide and there was no need of my device tree. I'm a noob, it's the first time I try to build a rom for my device.
Click to expand...
Click to collapse
Do you have any github link to the tree you're using? And have you made the necessary changes? Can you provide a screenshot or a github link of your device tree
osas514 said:
Do you have any github link to the tree you're using? And have you made the necessary changes? Can you provide a screenshot or a github link of your device tree
Click to expand...
Click to collapse
Brother, i did not make any changes, i just followed that guide. Which changes you mean?
Thanks btw
mariusfl0rian said:
Brother, i did not make any changes, i just followed that guide. Which changes you mean?
Thanks btw
Click to expand...
Click to collapse
Where did you download the device tree from? Can you send d link?
You need to download or clone the git files into it's proper location as mentioned in your error
I am trying to build a crdroid rom for the SM-T350. But i keep running into errors that im not sure how to fix.
steps i'v taken so far
Synced the CrDroid 9 repo
added a local manifest (this one https://github.com/Nubianprince/local_manifests/blob/master/crdroid-pie.xml)
repo synced again
Code:
repo sync -c --no-tags --no-clone-bundle -j2
git cloned this https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/
ran
Code:
export CROSS_COMPILE=/home/lividhen/crdroid/arm-eabi-4.8/bin/arm-eabi- && export ARCH=arm && export SUBARCH=arm
Code:
brunch gt58wifi
Ended with
Code:
(ninja: error: '/home/lividhen/crdroid/out/target/product/gt58wifi/kernel', needed by '/home/lividhen/crdroid/out/target/product/gt58wifi/boot.img', missing and no known rule to make it)
tried to build kernel, is that what i need to do?
Code:
(cd kernel/samsung/msm8916
ran
Code:
make menuconfig
then just saved with all the defaults, then ran
Code:
make msm8916_sec_gt58wifi_eur_defconfig)
ended with
Code:
make[2]: *** [scripts/Makefile.build:309: kernel/irq/irqdesc.o] Error 1
make[1]: *** [scripts/Makefile.build:455: kernel/irq] Error 2
make: *** [Makefile:834: kernel] Error 2
I feel as if I'm probably missing something important, I'm just not sure what. any help is appreciated. Do i need to provide more info? i am on WSL, but from what i'v heard, that shouldent make a difference.
Edit: ran make make VARIANT_CONFIG=msm8916_sec_gt58wifi_eur_defconfig again after running make clean and make mrproper in the kernel directory and got make: *** No rule to make target 'include/config/auto.conf', needed by 'include/config/kernel.release'. Stop
Try this.
Use this https://github.com/Nubianprince/local_manifests/blob/master/crdroid-pie.xml to update your crdroid-pie.xml file.
Delete device/samsung/msm8916-common
repo sync
. build/envsetup.sh && brunch gt58wifi
nubianprince said:
Try this.
Use this https://github.com/Nubianprince/local_manifests/blob/master/crdroid-pie.xml to update your crdroid-pie.xml file.
Delete device/samsung/msm8916-common
repo sync
. build/envsetup.sh && brunch gt58wifi
Click to expand...
Click to collapse
It is still throwing "ninja: error: '/home/lividhen/crdroid/out/target/product/gt58wifi/kernel', needed by '/home/lividhen/crdroid/out/target/product/gt58wifi/boot.img', missing and no known rule to make it
15:08:48 ninja failed with: exit status 1"
lividhen99 said:
It is still throwing "ninja: error: '/home/lividhen/crdroid/out/target/product/gt58wifi/kernel', needed by '/home/lividhen/crdroid/out/target/product/gt58wifi/boot.img', missing and no known rule to make it
15:08:48 ninja failed with: exit status 1"
Click to expand...
Click to collapse
In BoardConfigCommon.mk in msm8916-common folder what path are you using for TARGET_KERNEL_SOURCE and does it exist?
nubianprince said:
In BoardConfigCommon.mk in msm8916-common folder what path are you using for TARGET_KERNEL_SOURCE and does it exist?
Click to expand...
Click to collapse
It pointed twards kernel/samsung/msm8916 which no longer exists, so I changed it too kernel/samsung/evervolv, then I had a bunch of problems with the ncurses libs, but eventually got that sorted out, then FINALLY, it built successfully. Thank you.
Aaaaaand, audio not playing and camera is broken. How was this fixed?
lividhen99 said:
Aaaaaand, audio not playing and camera is broken. How was this fixed?
Click to expand...
Click to collapse
msm8916.mk & boardconfigcommon.mk update your audio config path.. change from TARGET_COPY_OUT_VENDOR to TARGET_COPY_OUT_SYSTEM
make clean && brunch gt58wifi
nubianprince said:
msm8916.mk & boardconfigcommon.mk update your audio config path.. change from TARGET_COPY_OUT_VENDOR to TARGET_COPY_OUT_SYSTEM
make clean && brunch gt58wifi
Click to expand...
Click to collapse
All the lines under audio already say TARGET_COPY_OUT_SYSTEM.
(also, quick off topic question, is the crdroid 6 usable yet? I'd guess not sence it hasn't been uploaded yet uploaded.)
lividhen99 said:
All the lines under audio already say TARGET_COPY_OUT_SYSTEM.
(also, quick off topic question, is the crdroid 6 usable yet? I'd guess not sence it hasn't been uploaded yet uploaded.)
Click to expand...
Click to collapse
How is this coming along?
nubianprince said:
How is this coming along?
Click to expand...
Click to collapse
Um... not. i'm not sure what else to do as i have never done this before . I guess i'll just keep poking around to see if i can do anything.
lividhen99 said:
Um... not. i'm not sure what else to do as i have never done this before . I guess i'll just keep poking around to see if i can do anything.
Click to expand...
Click to collapse
Maybe there is something missing from my git repos, I will update those this weekend.
nubianprince said:
Maybe there is something missing from my git repos, I will update those this weekend.
Click to expand...
Click to collapse
Okay, thanks.
Hey, I tried building with your latest commit, and I am not sure if that was supposed to fix anything,but it is still broken. I keep fiddling with the audio paths and can't seem to fix it ?
lividhen99 said:
Hey, I tried building with your latest commit, and I am not sure if that was supposed to fix anything,but it is still broken. I keep fiddling with the audio paths and can't seem to fix it ?
Click to expand...
Click to collapse
Did you do a clean build?
nubianprince said:
Did you do a clean build?
Click to expand...
Click to collapse
Yeah ? I'm just going to delete my entire android directory and start fresh.
okay, here is what i'm doing, just in case i'v done something terribly wrong. Initalize the crdroid repo, added crdroid-pie.xml to local_manifests, repo sync, then i try to build and it gives a liblights error so i comment out all of hardware/qcom/display-caf/msm8916/liblight/Android.mk and do a clean build.
Edit 1: I forgot to correct the kernel path in BoardConfigCommon.mk so i fixed that.
Edit 2: i am now getting build/make/core/shared_library_internal.mk:17: error: hardware/qcom/display-caf/msm8916/libmemtrack: Illegal use of OVERRIDE_BUILT_MODULE_PATH. which i wasn't getting before, so... potential progress?? i don't know.
lividhen99 said:
okay, here is what i'm doing, just in case i'v done something terribly wrong. Initalize the crdroid repo, added crdroid-pie.xml to local_manifests, repo sync, then i try to build and it gives a liblights error so i comment out all of hardware/qcom/display-caf/msm8916/liblight/Android.mk and do a clean build.
Edit 1: I forgot to correct the kernel path in BoardConfigCommon.mk so i fixed that.
Edit 2: i am now getting build/make/core/shared_library_internal.mk:17: error: hardware/qcom/display-caf/msm8916/libmemtrack: Illegal use of OVERRIDE_BUILT_MODULE_PATH. which i wasn't getting before, so... potential progress?? i don't know.
Click to expand...
Click to collapse
Sound like you messed something out in display-caf when you commented out liblight
okay, i got it to build again, i deleted display-caf and synced again, then commented the other of the two files defining liblights. now i'm back at the same issue again, neither camera nor audio works ?. all the audio paths in BoardConfigCommon.mk and msm8916.mk say TARGET_COPY_OUT_SYSTEM already, and i'm not sure what to do about the camera.
upload your device trees so I can take a look, I will upload my vendor trees and you can try building with those
nubianprince said:
upload your device trees so I can take a look, I will upload my vendor trees and you can try building with those
Click to expand...
Click to collapse
device/samsung
https://drive.google.com/open?id=11V3pcrDgMEId13l0bXG7inpyPUVx7FWp