yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace S5830 Original Android Development] tossan:
Nice to see a genuine kernel hacker actively around here! :)

Can you give us a good tip how to debug kernels on the Ace at the early stage of the boot process while the default logging system (logcat, dmesg) still isn't in place yet?

I think the main problem is, that he is trying to boot coolya's kernel on a stock rom, no?

@Prawesome

... nah ... see you in the Official Off-Topic thread at high-noon GMT! ... :D
[Galaxy Ace S5830 Original Android Development] Prawesome:
Lol,ok :p

Sent from my fingers to your face,take it or leave it.
[Galaxy Ace S5830 Original Android Development] LibiSC:
There is a post where coolya just added ext4 and something else but it's stock...i'm using that one and also tried the one from samsung server upd3 but same result. I think is something about with the config. I withdrew mine from my phone with adb too. But same result. I'll check again later
[Galaxy Ace S5830 Original Android Development] mdfzhi:
well, obviously dont turn off default kernel debugging option in defconfig :p

i dont know i we can see logs before dmesg and logcat kicks in, but i know that qtadb can show logs even if kernel fails to mount /system, in other words even before androids itself kicks in.

booting cm kernel in stock rom or the other way around wont give any serious problem like stuck on boot etc, it'll boot eventually but will got error in bluetooth, wifi etc. the difference between cm/aosp kernel with stock kernel is just in the ramdisk. use the same zImage produced from compiling, repack with cm ramdisk and repack another one with stock ramdisk and both will boot and works the same in their intended roms :)

---------- Post added at 05:52 PM ---------- Previous post was at 05:36 PM ----------

btw i just remember this, the kernel need to have the same localversion as the proprietary samsung's module in the ramdisk. if its missmatched kernel would fail to mount /system.

cd into ramdisk extracted directory containing the samsung's module and do

strings fsr.ko | grep vermagic

it'll throw some result and in it will have something like this

2.6.35.7-perf-CL514579

the localversion is the

-perf-CL514579

so edit the kernel defconfig to include the localversion same as the samsung's proprietary module localversion eg

CONFIG_LOCALVERSION="-perf-CL514579"
[Galaxy Ace S5830 Original Android Development] tossan:
Where did you find upd3?

The most recently released update I can get hold of is:

GT-S5830_GB_Opensource_Update1.zip
​

Nice, thanks for the infos. I'll give this one a try on the next kernel reflashing.

---------- Post added at 12:01 PM ---------- Previous post was at 11:55 AM ----------

I think you hit the bull's-eye right there! They definitely should differ because the new zImage only is packaged with a pre-made boot.img. Can't thank you for an useful post twice though. ... :D

---------- Post added at 12:08 PM ---------- Previous post was at 12:01 PM ----------

That said: AnyKernel is a myth after all?! ... :p
[Galaxy Ace S5830 Original Android Development] mdfzhi:
its the common problem with first time kernel modder. earlier when i first compiling kernel i'm stuck there too. ketut gave me this solution so he deserve the credit, not me. go thank him :D
[Galaxy Ace S5830 Original Android Development] dragonnn:
It;s widgetsoid (add the temperature indicator), but you can access this menu by typing an service code into the dialler (seach on google for it).
[Galaxy Ace S5830 Original Android Development] biswatmak:
Ok I used the last updated

kernel with the v1.1 battery patch

on LEWA Rom and the following anomaly happened

1) While discharging the battery value jumped directly to 92% from 100%.....I was using CONSERVATIVE governor : 120 mhz( min ) to 800 mhz ( max )

I am now back to pure ZIMAGE mod
[Galaxy Ace S5830 Original Android Development] dragonnn:
Are you charging to 100% or wait a bit longer, install https://play.google.com/store/apps/...95YWRqaWV2LmJhdHRlcnlmdWxsbm90aWZpY2F0aW9uIl0. or go to the service menu that I posted some posts ago, and charge you phone until it shows full.
[Galaxy Ace S5830 Original Android Development] LibiSC:
When i used the config that i extracted from my phone the value was there.

I tried with cooper03 and change the value but same result.

Maybe it's the arm. What arm compiler do you use?
[Galaxy Ace S5830 Original Android Development] LibiSC:
my mistake, update1
[Galaxy Ace S5830 Original Android Development] madman:
well that change has to be done by applying the method to ramdisk modules and not one got from phone config as you may be ultimately repacking it with other ramdisk which have different module numbers..

and about compiler use latest version of Sourcery G++ Lite from official site..
[Galaxy Ace S5830 Original Android Development] biswatmak:
I charge upto the point when the

charging sign on battery icon

in the status bar is replaced by the no

100

I also checked Settings > About Phone > Status and it showed "

FULL

" and not "

CHARGING

".
[Galaxy Ace S5830 Original Android Development] LibiSC:
I use a boot.img from a backup from my actual rom so are the same, i even checked in settings in phone info the code is shown too.

I'll try that compiler

edit: i'm already using 2011.03
[Galaxy Ace S5830 Original Android Development] tossan:
Managed to compile Samsung kernel from source.

Nothing fancy in here. Just trying to help LibiSC to get the selfmade kernel to boot. So, this is NOT for others to use at all! ... :D

@LibiSC

Maybe you can get the recompiled samsung kernel to boot, if you follow the procedure below.

Prerequisites:

stock and vanilla Samsung rom: DDKQ8 (flash it with Odin; if you use cf-root, then maybe some changes to .config have to be done to make it work)

source: GT-S5830_GB_Opensource_Update1.zip

compiler: arm-none-linux-gnueabi-gcc -v => gcc version 4.5.2 (Sourcery G++ Lite 2011.03-41)

Attachement

: ddkq8_kernel_recompiled.tar.gz

EDIT_01: The original attachement with the boot.img got deleted by some moderator? Anyway it was only there as a proof of concept. You don't need it to follow the instructions. Only the configuration files are now zipped. See attachement below.

EDIT_02: reuploaded ddkq8_kernel_recompiled_v2.zip

Procedure:

cp [COLOR=Red].config[/COLOR] "your_path_to_GT-S5830_GB_Opensource_Update1"/kernel
#[I] edit Makefile: search for [/I][COLOR=SeaGreen][I]CROSS_COMPILE[/I][/COLOR]
export PATH="your_path_to"/arm-2011.03/bin/:$PATH
cd "your_path_to_GT-S5830_GB_Opensource_Update1"/kernel
make
# repack new zImage with the boot.img from the rom as base, which config.gz was extracted from

[xXx]
​
[Galaxy Ace S5830 Original Android Development] LibiSC:
file is corrupted :S.
[Galaxy Ace S5830 Original Android Development] mdfzhi:
the latest Sourcery CodeBench Lite 2011.09-69, but it'll throw some error of unused-but-set-variable.

edit the Makefile to overcome that error, from

KBUILD_CFLAGS := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \
-fno-strict-aliasing -fno-common \
-Werror-implicit-function-declaration \
-Wno-format-security \
-fno-delete-null-pointer-checks

to

KBUILD_CFLAGS := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \
-w \
-fno-strict-aliasing -fno-common \
-Werror-implicit-function-declaration \
-Wno-error=unused-but-set-variable \
-Wno-format-security \
-fno-delete-null-pointer-checks

btw u dont need to pull config from phone, fully working defconfig already there in the kernel source. look in the automatic build script the make_kernel_GT-S5830.sh

make cooper_rev03_defconfig
make

its pointing to cooper_rev03_defconfig. it can be found in /arch/arm/config directory. just edit that defconfig

so just run the automatic build script when u want to start compiling

./make_kernel_GT-S5830.sh

or manually, like in the content of the script

make cooper_rev03_defconfig
make
[Galaxy Ace S5830 Original Android Development] ssDen_lol:
I am testing this kernel...

4 hours 3g surf on CyanogenMod by FAT... Good work :)
[Galaxy Ace S5830 Original Android Development] LibiSC:
i tried that config too and just changed the LOCAL but still didn't work and didnt touch anything else. It's really weird

One thing that may be the error is this one in compiler output

MODPOST vmlinux.o
ERROR: modpost: Found 3 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
GEN .version
CHK include/generated/compile.h
UPD include/generated/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
KSYM .tmp_kallsyms1.S
AS .tmp_kallsyms1.o
LD .tmp_vmlinux2
KSYM .tmp_kallsyms2.S
AS .tmp_kallsyms2.o
LD vmlinux
SYSMAP System.map
SYSMAP .tmp_System.map
OBJCOPY arch/arm/boot/Image

got this mistake too when cleaning

CLEAN arch/arm/boot/compressed
CLEAN arch/arm/boot
CLEAN /home/carlos/android/kernelSamsung
CLEAN arch/arm/kernel
CLEAN drivers/char
scripts/Makefile.clean:17: /home/carlos/android/kernelSamsung/drivers/fsr/Makefile: No existe el fichero o el directorio
make[2]: *** No hay ninguna regla para construir el objetivo «/home/carlos/android/kernelSamsung/drivers/fsr/Makefile». Alto.
make[1]: *** [drivers/fsr] Error 2
make: *** [_clean_drivers] Error 2
[Galaxy Ace S5830 Original Android Development] tossan:
file reuploaded;

Please give it a try.

You forgot about CONFIG_LOCALVERSION ? ... :D
[Galaxy Ace S5830 Original Android Development] madman:
newer stock kernel of ddkq8 has 5-6 or more changes in config but as we don't have updated kernel sources till date that config is mostly not gonna help..

even update1 don't have that config in it..
[Galaxy Ace S5830 Original Android Development] tossan:
Does not help to do what?

It is not about getting the new features into the Samsung stock kernel source but rather to get it compiled and booting here.

The reason why the config.gz is extracted from the DDKQ8 running rom is, that we want to ensure the new compiled kernel from the source is compatible with the stock DDKQ8 boot.img and base /system.

Btw, here is the diff of the provided .config with the default one.

As you can see, the default config has among other things the RFS modules enabled. But RFS is property source code from Samsung, so they don't bundle it with the opensource kernel code. This pose no big problem, because we're gonna use the modules packaged with the stock boot.img and /system anyway by editing the CONFIG_LOCALVERSION option accordingly. In this respect, it helps me a lot to boot the self compiled Samsung kernel pretty much. Once again thanks an0nym0us_ & ketut for the very useful hint. ... :D

diff -y --suppress-common-lines .config arch/arm/configs/cooper_rev03_defconfig |grep -v \#

[COLOR=SeaGreen][I]CONFIG_LOCALVERSION[/I][/COLOR]="-perf[COLOR=Red]-CL972857[/COLOR]" | CONFIG_LOCALVERSION="-perf"
> CONFIG_PACKET_MMAP=y
CONFIG_ASK_IP_FIB_HASH=y <
CONFIG_IP_MULTIPLE_TABLES=y <
> CONFIG_IPV6_ROUTER_PREF=y
<
<
CONFIG_NET_SCH_FIFO=y <
> CONFIG_RFS_FSR[COLOR=Red]=m[/COLOR]
> CONFIG_RFS_FSR_STL[COLOR=Red]=m[/COLOR]
> CONFIG_RFS_STL_DELETE=y
> CONFIG_FSR_FLASH_PHYS_ADDR=0xA0A00000
> CONFIG_LINUSTOREIII_DEBUG_VERBOSE=0
> CONFIG_LINUSTOREIII_DEBUG=y
>
>
> CONFIG_PPPOL2TP=y
> CONFIG_HS_SERIAL_MSM_CONSOLE=y
<
> CONFIG_MSM_KGSL_CONTEXTS=32
CONFIG_FB_MSM_DEFAULT_DEPTH_RGBA8888=y <
>
> CONFIG_MSM_PARAM[COLOR=Red]=m[/COLOR]
>
> CONFIG_RFS_FS[COLOR=Red]=m[/COLOR]
> CONFIG_RFS_DEFAULT_IOCHARSET="utf8"
> CONFIG_RFS_FS_PERMISSION=y
> CONFIG_RFS_FS_SYNC_ON_CLOSE=y
> CONFIG_RFS_FS_ERASE_SECTOR=y
> CONFIG_RFS_FS_SPECIAL=y
>
>
> CONFIG_RFS_FS_CORE_FAT=m
> CONFIG_RFS_FS_FAT_VFAT=y
CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0 <
[COLOR=Red]CONFIG_EARLY_PRINTK=y[/COLOR] <
CONFIG_TEXTSEARCH=y <
CONFIG_TEXTSEARCH_KMP=y <
CONFIG_TEXTSEARCH_BM=y <
CONFIG_TEXTSEARCH_FSM=y <
> CONFIG_SAMSUNG_LTN_COMMON=n
> CONFIG_SAMSUNG_TASS_LTN_L=n
> CONFIG_SAMSUNG_TASS_LTN_B=n
> CONFIG_SAMSUNG_BENI_LTN_L=n
> CONFIG_SAMSUNG_BENI_LTN_B=n
> CONFIG_SAMSUNG_COOPER_LTN_L=n
> CONFIG_SAMSUNG_COOPER_LTN_B=n
> CONFIG_SAMSUNG_BENNETT_LTN_L=n
> CONFIG_SAMSUNG_BENNETT_LTN_B=n
CONFIG_HAVE_SCHED_CLOCK=y <

[xXx]
[Galaxy Ace S5830 Original Android Development] madman:
as i said there are some changes ..

and default kernel config in sources will boot anyway on any boot.img unpacked with proper module version..

i was only pointing out that stock config is enough as config.gz from rom have different config and no entries to those are made in makefile and kconfig files in sources by sammy..

anyway that version number is the only change needed to get booting kernel
[Galaxy Ace S5830 Original Android Development] LibiSC:
Still nothing... So strange :-\
[Galaxy Ace S5830 Original Android Development] tossan:
Please upload your last boot.img attempt . Many eyes may see things which two never will --> an0n ... :D

---------- Post added at 03:31 PM ---------- Previous post was at 03:28 PM ----------

... also add your kernel/.config and kernel/Makefile!
[Galaxy Ace S5830 Original Android Development] LibiSC:
test flashable zip

config

MakeFile
[Galaxy Ace S5830 Original Android Development] tossan:
​

Strange indeed. Your extracted libisc_boot.img (renamed) boots fine on my system. What I did was

1. boot into recovery
2. ./flash_image boot ../libisc_boot.img
3. reboot

My system

Please do

adb shell mount >libisc.log
echo "~~~~~~~~~~" >>libisc.log
adb shell busybox ls -lR / >>libisc.log #will only work, if you're rooted or have busybox manually installed

and attach libisc.log.
[Galaxy Ace S5830 Original Android Development] tossan:
Obviously not.

We would all be thankful, if you could share some insights and help LibiSC to make it work. ... :D
[Galaxy Ace S5830 Original Android Development] madman:
@LibiSC

what package you downloaded for arm compiler ? tell complete name of that package

as i see from makefile its huge difference from the one from mine [ofc not username]
[Galaxy Ace S5830 Original Android Development] tossan:
The Makefile is from GT-S5830_GB_Opensource_Update1.zip ... the Samsung kernel source code.
[Galaxy Ace S5830 Original Android Development] LibiSC:
2011.03 for linux

p.s= I will be busy cause i have a new job...i'll be trying again friday
[Galaxy Ace S5830 Original Android Development] LibiSC:
u flash it with a zip with cwm right??? I cant make it work
[Galaxy Ace S5830 Original Android Development] tossan:
No, I did it manually via the adb shell while booting into CWM 4 (recovery mode). But the commands involved are the same as seen in the updater-script.

It have to be your rom setup, which pose problems esspecially on your device only.

Please create the libisc.log as suggested in my previous post.

Try to do it manually like I did and let's see, if you get some error report back from the shell.

Attach recovery.log and adb logcat, if you gonna flash the last zip again, which you gave me lately.

Without any log it is kind of hard to guess, what exactly is going wrong with your setup.

[xXx]
[Galaxy Ace S5830 Original Android Development] LibiSC:
Those commands are after flashing it right?
[Galaxy Ace S5830 Original Android Development] tossan:
The flash_image command is an alternative way to flash boot.img instead installing it via CWM zip archive.

The commands with redirection (> and >>) to libisc.log are there, to let me see which configuration you're currently running. Run them on your stock rom before flashing your custom kernel. And while you're at it, you can also append the whole logcat to the log with: "adb shell logcat >>libisc.log".

The recovery.log and adb_log_after_flash.log ("adb shell logcat >adb_log_after_flash.log") are nice to have to get some hints, why your CWM flashing attempt didn't went through.

To avoid typos, please cut and paste the commands into your terminal (the device is either in the normal running mode or recovery mode -> needed, if you want to do the flashing manually or grab the recovery.log).

[xXx]
[Galaxy Ace S5830 Original Android Development] LibiSC:
I did eeverything i always do but this time i update superuser binaries and the test kernel worked... then i compiled another one but didnt work T_T

adb log in attachments

Edit:

I think i found the reason why it wasnt booting....

In the makefile in extraversion i was putting 7-test

But apparently perf is concatened there so would end like 7-test-perf-....

So it wouldn't match with the source boot.img T_T

Problem solved. Now i can start with the modifications on the source. thanks man
[Galaxy Ace S5830 Original Android Development] tossan:
Nice to see you beeing able to resolve the custom kernel boot issue!

We now all expecting great things coming. ... :)

It is strange though that an update of the su-apk did the trick for you. I'm still using the su-apk bundled in the original AceGingerRoot.zip.

Regarding the typo in the Makefile:

That's why I always make a back up of the files I'm going to change, if I'm working locally on some source code with no repository like github, svn or cvs. A diff (btw, kdiff3 is a must have asset for any serious linux dev ... :D ) and code review would reveal the mistakes or coding errors.

[xXx]
[Galaxy Ace S5830 Original Android Development] side_effect:
Alpha 3:-Cant get past galaxy ace screen.

ROM-DDKQ8
[Galaxy Ace S5830 Original Android Development] LibiSC:
mmmm is your rom deodexed or with cf root??
[Galaxy Ace S5830 Original Android Development] side_effect:
Yes..!!

both deodexed and using cf root b83..

No scripts except A2SD,if it makes any difference..
[Galaxy Ace S5830 Original Android Development] LibiSC:
I have not tested it with a rom that already have cf root. Cf root changes the filesystem type to ext 4 so maybe is giving trouble
[Galaxy Ace S5830 Original Android Development] side_effect:
Hmmm..so should i revert back to rfs and try?

Or may be you can compile one that supports multiple filesystems if it is convenient and doesnt bothers u much?

Anyways I am up for testing anytime!!

keep on your good work buddy..!!
[Galaxy Ace S5830 Original Android Development] LibiSC:
I tested it in a clean ddkq8... The most important difference is that i think between cf root and this kernel... I will try it and let you know
[Galaxy Ace S5830 Original Android Development] side_effect:
Alright..!
[Galaxy Ace S5830 Original Android Development] jumbobombo:
I get reboots but that's fine coz I was heavily multitasking :p

Battery life is amazing last for a day and 1/4 with 2g, wifi and some games perfect :D

Thanks a lot :)

----------------

Sent from my Ace. Galaxy Ace
[Galaxy Ace S5830 Original Android Development] AndroidGadgetCyprus:
How to install? Installed it but no wifi, no bluetooth. (installed only zImage, coz if I install the other things, it wont boot)
[Galaxy Ace S5830 Original Android Development] LibiSC:
You need a clean stock. By zImage you meant boot.img renamed. Use the flashable zip if doesnt work then use a clean stock rom.
[Galaxy Ace S5830 Original Android Development] skynet28:
The wifi module will work only if it matches the kernel vermagic.So please repack your wifi module with your kernel for wifi to work across all basebands.
[Galaxy Ace S5830 Original Android Development] LibiSC:
Didnt know tht...i'll do it tomorrow right now im sleepy
[Galaxy Ace S5830 Original Android Development] LibiSC:
New version... please test it
[Galaxy Ace S5830 Original Android Development] Farooq95:
ChangeLog?
[Galaxy Ace S5830 Original Android Development] LibiSC:
First page
[Galaxy Ace S5830 Original Android Development] dragonnn:
Can you post the source

Wysłane z mojego GT-S5830 za pomocą Tapatalk
[Galaxy Ace S5830 Original Android Development] wizarcl:
Hi friend...

In some custons kernels i found one small "BUG".... i reported it to Skynet about The Ace Kernel beta 3.1 and your kernel also have this bug, but it is on tension level higher...

By wizarcl at 2012-04-23

http://xdaforums.com/showpost.php?p=25268836&postcount=178

Can u correct this? or someone?
[Galaxy Ace S5830 Original Android Development] LibiSC:
If it was during chargin it's normal, if it is not then ur phone is damaged xD.

There is a recharge value where the power is cut but 100% is still shown... where the value is lower of recharge value it starts giving power again.

The battery cant be in the 100% always cause it will damage it.

Solution...well disconnect as soon as the full charge notification is shown
[Galaxy Ace S5830 Original Android Development] LibiSC:
Second post.
[Galaxy Ace S5830 Original Android Development] LibiSC:
I have compiled one for custom roms... I tested it in Cheetah 2.0 and worked so can work in stocklite 6.0 too.

Download it in OP
[Galaxy Ace S5830 Original Android Development] side_effect:
Thanx a lot sir..!!

Works good and well.

Small request-can you add OC and interactivex?

Do at your own convenience..!!
[Galaxy Ace S5830 Original Android Development] consegregate:
I wanna ask, what will happen if you don't just EDIT values, but you ADD more values defining more levels. Will it make the battery reading more accurate? Maybe it's not about the checking frequency but actually the levels never being accurate enough anyway.

Someone on stock rom will realise there is no way to tell the battery percentage through settings on the Ace but you can on other phones. It is excluded purposely for some reason and I think it may be lazy engineering when developing for the phone.
[Galaxy Ace S5830 Original Android Development] encik_racun:
gonna try it i guess...
[T-Mobile Samsung Galaxy S II SGH-T989] nabilbek:
is there a way to get voice command working without using internet connection ?? so stupid ... why does it require that :confused:
[LG Optimus Black] andreas0013:
guys i was wondering, whats the best option to set in the script for our phone??

Im only using it for a day and i dont know whats the best setting for the black
[LG Optimus Black] re4lsk:
Any of the big ram setting will be ok.

Trolling in the deep
[Huawei Ideos X5 U8800] Odinforce:
I have the resources to lay my hands on the upcoming ICS 4.0.3 rom for the Honor, the version B978 it is the final beta version before the official launch.

Can anyone work on that rom to port it for the Pro? I don't want to waste resources, it would be pointless to upload it if anyone is going to work on it.

Dev's please confirm me so i can post it.
[Huawei Ideos X5 U8800] Odinforce:
Come on, not interested in ICS for the Pro's?
[Huawei Ideos X5 U8800] Filatov.p:
You answered your question yourself. Who would waste his time on beta version if there is comming official one? Sensless...
[Huawei Ideos X5 U8800] Odinforce:
Not senseless clearly you are not a developer, this is a stable version without Huawei UI, the only change is going to suffer is that before it's launch as the official one.

By working on this you are going to save TIME which clearly doesn't mean anything to you because you are a user not a provider/developer.

So go troll to another post smartass.
[Huawei Ideos X5 U8800] atmsv:
I would love to help. But I have the skills
[Huawei Ideos X5 U8800] husen4u:
Ask DZO he is the great developer for u8800
[Huawei Ideos X5 U8800] masiushc:
as i know dzo doesnt have pro,only standard u8800 and working with it like we see already released with 3kernel..with pro version devs are rare thing...geno? geno working with miui i think.
[Huawei Ideos X5 U8800] pikachukaki:
If honor port is stable dzo will take it and make it working...but maybe he is waiting final version....then port is easy from non pro to x5pro!!
[Huawei Ideos X5 U8800] Filatov.p:
the one is trolling here is you! Are you a developer, saying such things to me?! people like you only annoying real developers posting such posts!

as*hole!

I heard porting rom from Honor to 8800pro is easier than porting 8800 to 8800pro...
[Huawei Ideos X5 U8800] Odinforce:
Dude no need to insult now i see you are bleeding from the wound, i don't disturb developers, i don't sent PM's, just post what i think may be of their interest smartass.

The porting from Honor to Pro is easier because of the chipset resemblance MSM8255 Pro vs. MSM8255T Honor.

The U8800 MSM7230 resemblance to Pro is only cosmetic, even the Wifi and bluetooth chip are different hence the work to make the porting is harder.
[Huawei Ideos X5 U8800] linomaniac:
stop rambling, chicks, and start the work.