Database Info

[KERNEL][DEV] Kernel 3.0.8 -test only for developer- [15/10/2012]

please respect the rules
WRITE ON THIS THREAD ONLY IF YOU ARE DEVELOPERS
>>otherwise write in this thread<<
Hi guys,
I stop my porting project because Arco and Ivendor are already developing their own porting and they are more advanced than me,
keep my developments to create a custom kernel, based on their developments.​
Before you fill with unnecessary questions, no it is not bootable,
these are the progress i've made in porting the kernel 3.0.8,
the base used is the kernel of Huawei Honor U8860 and with the help of some of the drivers SPH-M950.
The drivers have been included, these are the ones i remember now:
yda165 (audio amplifier) >> updated from SGSII
fsa9485 <fsa9480> >> from SPH-M950
cypress-touchkey >> updated from I9001
touchscreen >> Atmel mXT I2C Touchscreen (updated drivers, to test if work)
gpu adreno >> already included on U8860
audio qdspv2 marimba >> already included on U8860 but fixed the value and config
vibetonz >> updated from SPH-M950
samsung Jack >> ported
samsung battery >> updated from SPH-M950 (do a complete test, when the kernel works)
MAX17043 fuel gauge >> updated by ... i do not remember ... maybe SPH-M950 ?!?
Wifi BCM4329 & bluetooth >> already included on U8860 (maybe need to replace)
Sensors drivers:
gp2a light >> ported
gp2a proximity >> ported
yas bma023 acceleration >> ported
yas529 geomagnetic >> ported
optical gp2a ori orientation sensor >> ported
Camera drivers:
drivers are included.
Board AriesVe:
I re-wrote the board using the one of the U8860, but you may need to make other changes.
Compile errors:
Code:
arm-eabi-ld: warning: unwinding may not work because EXIDX input section 94 of arch/arm/mach-msm/built-in.o is not in EXIDX output section
arm-eabi-ld: warning: unwinding may not work because EXIDX input section 1044 of kernel/built-in.o is not in EXIDX output section
arm-eabi-ld: warning: unwinding may not work because EXIDX input section 455 of mm/built-in.o is not in EXIDX output section
arm-eabi-ld: warning: unwinding may not work because EXIDX input section 205 of fs/built-in.o is not in EXIDX output section
arm-eabi-ld: warning: unwinding may not work because EXIDX input section 53 of crypto/built-in.o is not in EXIDX output section
arm-eabi-ld: warning: unwinding may not work because EXIDX input section 357 of block/built-in.o is not in EXIDX output section
arm-eabi-ld: warning: unwinding may not work because EXIDX input section 274 of lib/built-in.o is not in EXIDX output section
arm-eabi-ld: warning: unwinding may not work because EXIDX input section 67 of drivers/built-in.o is not in EXIDX output section
arm-eabi-ld: warning: unwinding may not work because EXIDX input section 11 of sound/built-in.o is not in EXIDX output section
arm-eabi-ld: warning: unwinding may not work because EXIDX input section 9 of arch/arm/oprofile/built-in.o is not in EXIDX output section
arm-eabi-ld: warning: unwinding may not work because EXIDX input section 963 of net/built-in.o is not in EXIDX output section
STATUS:
14/10/2012:
Updated .config
Correct compilation errors "mdp4_overlay_play_wait", "mdp4_overlay_set", "mdp4_overlay_unset"
Corrected "unmet direct dependencies"
Here are you need to compile:
Toolchain: arm-eabi-4.4.3
Config file: .config [14/10/2012]
My 3.0.8 source: GitHub CastagnaIT
any help is well liked.

Wow! so it's actually booting! that's a very big step. I think getting it to boot is the biggest issue. (although there are probably a ton more issues to solve)

Wow, this is really good news...

As he said its NOT(!) booting. This thread is just for KernelDevs so dont post.

Lets go through the problems one at a time.
Looks like there is a Kconfig issue. Is this seen on other configs of the same architecture at the point you forked from? Kconfig unmet dependencies can cause all sorts of problems.
Code:
warning: (ARM_GIC && PMIC8058) selects MSM_SHOW_RESUME_IRQ which has unmet direct dependencies (ARCH_MSM && (ARCH_MSM8X60 || ARCH_MSM8960 || ARCH_MSMCOPPER))
warning: (MTD_MSM_NAND && MTD_DOC2000 && MTD_DOC2001 && MTD_DOC2001PLUS) selects MTD_NAND_IDS which has unmet direct dependencies (MTD && MTD_NAND)
warning: (ARM_GIC && PMIC8058) selects MSM_SHOW_RESUME_IRQ which has unmet direct dependencies (ARCH_MSM && (ARCH_MSM8X60 || ARCH_MSM8960 || ARCH_MSMCOPPER))
warning: (MTD_MSM_NAND && MTD_DOC2000 && MTD_DOC2001 && MTD_DOC2001PLUS) selects MTD_NAND_IDS which has unmet direct dependencies (MTD && MTD_NAND)

As someone said on the other 3.0.8 post, cyanogen is working on a 3.0.x migration for msm7x30, it could be useful. You can find all the info on this post http://kcy.me/bmr4
Enviado desde mi GT-I9001 usando Tapatalk 2

Here are the unresolved symbols I get when compiling with the CodeSourcery 2009q3 compiler:
Code:
drivers/built-in.o: In function `mdp4_overlay_play_wait':
/home/bryan/i9001/samsung-kernel3-msm7x30/drivers/video/msm/mdp4_overlay.c:2354: undefined reference to `mdp4_overlay_dtv_wait_for_ov'
drivers/built-in.o: In function `mdp4_overlay_unset':
/home/bryan/i9001/samsung-kernel3-msm7x30/drivers/video/msm/mdp4_overlay.c:2272: undefined reference to `mdp4_overlay_dtv_unset'
drivers/built-in.o: In function `mdp4_overlay_set':
/home/bryan/i9001/samsung-kernel3-msm7x30/drivers/video/msm/mdp4_overlay.c:2133: undefined reference to `mdp4_overlay_dtv_set'
make: *** [.tmp_vmlinux1] Error 1
The mdp4_overlay_dtv.c file needs to be linked in, by adding CONFIG_FB_MSM_DTV to the kernel config. This option is only a boolean that is enabled by one of the HDMI PANEL options, like CONFIG_FB_MSM_HDMI_MSM_PANEL. But, once this is enabled, it looks like the board is not defining some memory regions used by the HDMI device.
Which compiler are you using to build with?

I know it's a little bit off, but if you look at arco's github, you'll see he has renamed the kernel branch from ics to ics 2.6.35, so their 3.x kernel is almost ready
Tapatalk 2-vel küldve az én GT-I9001-ről

bhundven said:
Lets go through the problems one at a time.
Looks like there is a Kconfig issue. Is this seen on other configs of the same architecture at the point you forked from? Kconfig unmet dependencies can cause all sorts of problems.
Code:
warning: (ARM_GIC && PMIC8058) selects MSM_SHOW_RESUME_IRQ which has unmet direct dependencies (ARCH_MSM && (ARCH_MSM8X60 || ARCH_MSM8960 || ARCH_MSMCOPPER))
warning: (MTD_MSM_NAND && MTD_DOC2000 && MTD_DOC2001 && MTD_DOC2001PLUS) selects MTD_NAND_IDS which has unmet direct dependencies (MTD && MTD_NAND)
warning: (ARM_GIC && PMIC8058) selects MSM_SHOW_RESUME_IRQ which has unmet direct dependencies (ARCH_MSM && (ARCH_MSM8X60 || ARCH_MSM8960 || ARCH_MSMCOPPER))
warning: (MTD_MSM_NAND && MTD_DOC2000 && MTD_DOC2001 && MTD_DOC2001PLUS) selects MTD_NAND_IDS which has unmet direct dependencies (MTD && MTD_NAND)
Click to expand...
Click to collapse
This looks like you compiled from my repo, right? Because I got the same errors. But I don't think that it is needed that we fix it because I already got it at my first build when I made no changes. And it compiles successfully, I get a ready kernel image.
I'm using the cross-compiler from the cyanogenmod android source tree.

hahnjo said:
This looks like you compiled from my repo, right? Because I got the same errors. But I don't think that it is needed that we fix it because I already got it at my first build when I made no changes. And it compiles successfully, I get a ready kernel image.
I'm using the cross-compiler from the cyanogenmod android source tree.
Click to expand...
Click to collapse
Yup. But if depedences are not met, kernel may not boot, that of course. Meaby try to fix it first?

Harrocan said:
Yup. But if depedences are not met, kernel may not boot, that of course. Meaby try to fix it first?
Click to expand...
Click to collapse
I think there are none of the warned configs selected

hahnjo said:
I think there are none of the warned configs selected
Click to expand...
Click to collapse
It would not hurt to check

Harrocan said:
Yup. But if depedences are not met, kernel may not boot, that of course. Meaby try to fix it first?
Click to expand...
Click to collapse
I've just corrected
now compilation works, it remains to fix unwinding warnings

CastagnaIT said:
I've just corrected
now compilation works, it remains to fix unwinding warnings
Click to expand...
Click to collapse
Great. Any other errors? (i don't have so many pratice, only teoretic, so i can help only in that way)

Harrocan said:
Great. Any other errors? (i don't have so many pratice, only teoretic, so i can help only in that way)
Click to expand...
Click to collapse
no, no other error, but you have to replace the drivers wifi and bluetooth

Rom_Tester said:
Sorry ,I am a noob, but is it now bootabel, because no errors?
Click to expand...
Click to collapse
can we please leave this thread clean from any posts which will not really improve the dev path ?
Only for 1 week discipline, please.

On my github, there is now a branch with the original samsung code. I've also applied the latest changes from codeaurora. Today I will maybe try to fix the error with the "unmet dependencies"
If you want to help / have a pull request or questions that are development related, just PM me

Hi guys,
I stop my porting project because Arco and Ivendor are already developing their own porting and they are more advanced than me,
keep my developments to create a custom kernel, based on their developments.

[Completed] ROM build from source error

Hi there,
I have an error when compiling Android Open Source Bam(AOSB) for Xperia SP(huashan)
target thumb C++: libqdutils <= hardware/qcom/display-caf/libqdutils/profiler.cpp hardware/libhardware_legacy/audio/AudioPolicyManagerBase.cpp:3794:28: error: 'AUDIO_FORMAT_FLAC' was not declared in this scope build/core/binary.mk:432: recipe for target '/home/AndroidNoob69/android/aosb/out/target/product/huashan/obj/STATIC_LIBRARIES/libaudiopolicy_legacy_intermediates/AudioPolicyManagerBase.o' failed make: *** [/home/AndroidNoob69/android/aosb/out/target/product/huashan/obj/STATIC_LIBRARIES/libaudiopolicy_legacy_intermediates/AudioPolicyManagerBase.o] Error 1 make: *** Waiting for unfinished jobs....
I have no idea what causes this. Please advise what I need to do to fix this.
Thanks.
Sent my Paranoid Xperia P

Hi!
2 things.....1, this is your 3rd thread on this subject. XDA assist is not a help desk, we're simply here to give direction to new members. You are not new.
And 2, if Bam is what I think it is....that developer and ROM has been banned from XDA. No threads are allowed on the subject and no ROM postings of it, or ROMs based on it. If your talking about something different... Mt apologies.... But point number one still stands.
Thread closed.

[Q&A] [ROM][UNOFFICIAL] OmniRom Lollipop Unofficial Builds - (23-feb-2015)

Q&A for [ROM][UNOFFICIAL] OmniRom Lollipop Unofficial Builds - (23-feb-2015)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][UNOFFICIAL] OmniRom Lollipop Unofficial Builds - (23-feb-2015). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Well, i'm guess i'm going to need to do this
KSKHH said:
Can you please replace messaging apps to Android L Messaging Apps. It look is like KK Apps.
Can you please check Layers. I believe Layers is working on the ROM already. May be not fully. I have taken Layers application from other ROM (May be from SLIMP) and tried to apply Layers theme. It did apply the theme. Mainly in Settings is not applying properly. I hope the ROM is almost ready for Layers.
Click to expand...
Click to collapse
If you want a "material", "LP" Messaging app you would need to do your own development

Hi. You have had this error?
Code:
frameworks/av/services/soundtrigger/SoundTriggerHwService.cpp:50: error: undefined reference to 'android::MemoryDealer::MemoryDealer(unsigned int, char const*)'
frameworks/av/services/soundtrigger/SoundTriggerHwService.cpp:50: error: undefined reference to 'android::MemoryDealer::MemoryDealer(unsigned int, char const*)'
collect2: error: ld returned 1 exit status
build/core/shared_library_internal.mk:68: ошибка выполнения рецепта для цели «/home/archie/phablet/out/target/product/find7op/obj/SHARED_LIBRARIES/libsoundtriggerservice_intermediates/LINKED/libsoundtriggerservice.so»
make: *** [/home/archie/phablet/out/target/product/find7op/obj/SHARED_LIBRARIES/libsoundtriggerservice_intermediates/LINKED/libsoundtriggerservice.so] Ошибка 1
make: *** Ожидание завершения заданий…
Can help? Thanks in advance.

Where to start to build a new custom ROM?

Hi. I've always been curious to try to build a new aosp based ROM.
I know java but I don't know CPP... Only a bit. Anybody thinks I could start something? Even in a team, of course. Where to start?

enryfantasy said:
Hi. I've always been curious to try to build a new aosp based ROM.
I know java but I don't know CPP... Only a bit. Anybody thinks I could start something? Even in a team, of course. Where to start?
Click to expand...
Click to collapse
First of all, it depends on how much you already know.
There are numerous guides on how to build another existing custom ROM. I'd start with those first to be a little familiar with how a project is handled, but you could always just look for guides for building one from scratch AOSP if you wanted to.
There are plenty of guides on the internet, and if you run into an issue, someone else has likely already asked about it and received an answer.

Elluel said:
First of all, it depends on how much you already know.
There are numerous guides on how to build another existing custom ROM. I'd start with those first to be a little familiar with how a project is handled, but you could always just look for guides for building one from scratch AOSP if you wanted to.
There are plenty of guides on the internet, and if you run into an issue, someone else has likely already asked about it and received an answer.
Click to expand...
Click to collapse
Thanks. I'll try to look for something over AOSP

You interested in teaming?

DOBBY0 said:
You interested in teaming?
Click to expand...
Click to collapse
i am same as the guy who started this thread. and fyi im interested in teaming.

You can hit my up on Hangouts and we can discuss some stuff. My name is Michael Stevens. Hers my G+ page https://plus.google.com/u/0/+MichaelStevens_DOBBY0/about

burakd0gan said:
i am same as the guy who started this thread. and fyi im interested in teaming.
Click to expand...
Click to collapse
^^^^^^^^^^^^^

I'd also be interested in learning how to manage/develop a custom rom. Let's get Team n00b started up

I´m bumping this topic though the last answer is over one month ago
Creating, managing a Custom ROM of any kind is very time consuming and some people will always expect you to release updates as fast as possible and to work for free Even if you´ve set up your developing environment ( I use Linux ), you will need a lot of patience and a hell of a PC to compile stuff without waiting too long.
If I were you I would think twice if I want to a) build a ROM for yourself only or b) also go through the pain of maintaining a thread, webspace and online support.
The Nexus forums are crowded with AOSP based ROMs and I don´t think that one thread more or less would matter. What I build for myself simply needs to be reliable without 1000x different Mods or Themes.
Since I barely have any time for this hobby anymore, I stick to a) only and even by doing so, I will also waste a lot of time since sometimes there are unforeseen consequences

Yes. That's what I ended too. It would take too much time and resources. I just stopped thinking about that (because my linux pc is very old, too) and used a good ROM.
Thanks!

Quick question
I'm trying to build M developer preview from AOSP. I'm currently syncing the repo with the command:
Code:
repo init -u https://android.googlesource.com/platform/manifest.git -b android-m-preview
After this is synced I will add my device to the appropriate folder with the code:
Code:
git clone https://android.googlesource.com/device/lge/hammerhead.git -b android-m-preview hammerhead
After this will I be able to compile and build?
Am I on the right track?

t3al said:
Quick question
I'm trying to build M developer preview from AOSP. I'm currently syncing the repo with the command:
Code:
repo init -u https://android.googlesource.com/platform/manifest.git -b android-m-preview
After this is synced I will add my device to the appropriate folder with the code:
Code:
git clone https://android.googlesource.com/device/lge/hammerhead.git -b android-m-preview hammerhead
After this will I be able to compile and build?
Am I on the right track?
Click to expand...
Click to collapse
Correct me if I'm wrong, but you can just add the device specific code on the manifest (by modifying .repo/manifest/default.xml)

F4uzan said:
Correct me if I'm wrong, but you can just add the device specific code on the manifest (by modifying .repo/manifest/default.xml)
Click to expand...
Click to collapse
I didn't add my device on the manifest. I followed another guide specifically for my phone and AOSP.
Now, I'm stuck at this:
Code:
Header: out/target/product/hammerhead/obj/include/gps.utils//loc_log.h
make: *** No rule to make target `hardware/qcom/gps/utils/log_util.h', needed by `out/target/product/hammerhead/obj/include/gps.utils//log_util.h'. Stop.
make: *** Waiting for unfinished jobs....
Header: out/target/product/hammerhead/obj/include/gps.utils//loc_cfg.h
I used the Preview binaries from Google.
Does this mean the latest blobs do not compile for M?
Edit: Found my answer here

[rom][aospa][unofficial][7.2.2][bacon]

I have almost finished compiling the ROM but need some help with an error then it'll be ready.
Here's what's happening when I build it:
[ 0% 90/18970] Docs droiddoc: out/target/common/docs/api-stubs
DroidDoc took 16 sec. to write docs to out/target/common/docs/api-stubs
[ 0% 91/18970] Compiling SDK Stubs: out/target/common/o...IBRARIES/android_stubs_current_intermediates/classes.jar
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
[ 0% 93/18970] Building with Jack: out/target/common/ob...LIBRARIES/framework_intermediates/with-local/classes.dex
FAILED: /bin/bash out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/with-local/classes.dex.rsp
Out of memory error (version 1.2-rc4 'Carnac' (298900 f95d7bdecfceb327f9d201a1348397ed8a843843 by [email protected])).
GC overhead limit exceeded.
Try increasing heap size with java option '-Xmx<size>'.
Warning: This may have produced partial or corrupted output.
[ 0% 93/18970] Compiling SDK Stubs with Jack: out/targe...BRARIES/android_stubs_current_intermediates/classes.jack
ninja: build stopped: subcommand failed.
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
Build failed!
Total time elapsed: 10 minutes (652.687489167 seconds)
I cannot seem to locate the java heap size parameter file to modify it. A little info will help out. If not I'll figure it out on my own soon and have the latest build ready for flashing. Thanks.

Official? Oh please...

SirSoviet said:
Official? Oh please...
Click to expand...
Click to collapse
I'm building it from https://github.com/AOSPA. So to answer your question, yes it would be official.:good:
Any more questions you could figure out by yourself?

Techie Android said:
I'm building it from https://github.com/AOSPA. So to answer your question, yes it would be official.:good:
Any more questions you could figure out by yourself?
Click to expand...
Click to collapse
There's a difference between that and this. Your builds are unofficial because you aren't an official maintainer (unless you are, in which case I'm sorry), but the builds posted on the site are official, because they were built by a trusted maintainer from the AOSPA team.

SirSoviet said:
There's a difference between that and this. Your builds are unofficial because you aren't an official maintainer (unless you are, in which case I'm sorry), but the builds posted on the site are official, because they were built by a trusted maintainer from the AOSPA team.
Click to expand...
Click to collapse
Okay I was not aware of that being the case. I understood official to mean it was unmodified and built from the source. I'll change it to unofficial since I'm not connected to AOSPA. Thank you for pointing that out.

placeholder threads are not allowed on xda where are the moderators when we need them?
Read the RULES NEXT TIME!!!!

Fine I won't share it then.
Sheesh. Do you people just constantly give everybody this trash talk?

Techie Android said:
Fine I won't share it then.
Sheesh. Do you people just constantly give everybody this trash talk?
Click to expand...
Click to collapse
Rules are rules.. There was no trash talk, the only poor attitude is yours. I hope you'll resolve this here as well as with any future posts you make..
I've already reported this thread, lets keep this respectful until everything gets fixed..
Thanks

Thread moved to Q&A section at this moment, if later the ROM is released, please report it to Mod Team and we will move it back to develop section.
And please be reminded to keep the discussion as civil as you can.