yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] AndroidGX:
Firstly: thanks for trying helping me out ;) I don't think reflashing the kernel will change anything as I wiped cache+dalvik before flashing kernel first.

Secondly: I never said the contrary about kox, he is one of the most talented developpers I encountered on this board, for sure.

But sometimes (we, the testers), cannot understand some choice a developper can make. I agree anyway he must test anything to check the best choice ever, but maybe, my comment help him aswell, I think we need a stab voltage first and once it's done, don't touch it to see where else we need to ameliorate, no worries if my comment will be ignored, I can understand it totally as it will remain as my only point of view ;) I just wish it may help in a good way.

Did you check about the crispy sound I get when listening to music ?

I'am alone in this case ? :(

I tried yesterday night with back to overcome default kernel 3.1.0, and problem is almost solved but not totally (something around 90%, if we talk in percentage :p), maybe kox can you check the code of it to see about that sound problem please ?

many thanks!
[Galaxy Tab  Android Development] nunggg:
please help me ....

I want to know about 3 sec lightkeys patched.What is version work for overcome hermer 2.0.1 ?

please inform me :)
[Galaxy Tab  Android Development] OsitKP:
I'm testin 3.0.11 kernel. No crispy sound (using TTPod).

It won't work with overcome kernel, 'cause it overwrites the lib on every boot. If you flash koxudaxi's kernel, patched lib will surely work.
[Galaxy Tab  Android Development] nobleskill:
Haha. Yeah I know I get protective of my crew, my bois.... lol

Hmm I had a sound issue on 10 I think it was. Fixed by unistalling voodoo control and reinstalling fresh. Wipe cache, dalvic ect...

No chance you are restoring a ESP control app or anything from previous roms by mistake?

Best thing would be a nand backup, fresh ROM no apps. If the problem is there still its a kernel issue or hardware fault.. if not its a chance to find the little fooker by process of elimination ... start with sound/radio/streaming apps and work through...

B-)

Sent from my GT-P1000
[Galaxy Tab  Android Development] 4exess:
Music works ok no weird sound - check ur voodoo sound settings

Camera and all the apks workin fine no problem at all

If u change the .so file in overcome zip update itll get overwrited with ur patched

.so file everytime u boot up ;-)
[Galaxy Tab  Android Development] OsitKP:
Wrong you are. Read, plz, what I've written: OC kernel OVERWRITES the library on EVERY boot, even if you delete it, kernel will restore its original variant.

P.S. Just try to do it yourself.
[Galaxy Tab  Android Development] 4exess:
Replacing original .so file with the patched one in 001006-Overcome_v2.zip before u update/flash will always overwrite with pat hed one. . . Cause that will be the original one

Sent from my Overcomed Tegrafied Smartass Chainfired 3D Tab
[Galaxy Tab  Android Development] OsitKP:
You are too smart to try your suppose on practice? I suggest this lib inserted into kernel so your punditry has no base. Any way whatever you change the lib, overcome kernel forcely overwrites it on every boot.
[Galaxy Tab  Android Development] 4exess:
Lol

I did try it thats y im tellin ya

No need to be rude thou. . .

Sent from my Overcomed Tegrafied Smartass Chainfired 3D Tab
[Galaxy Tab  Android Development] AndroidGX:
Héhé ;)

Thanks for your you guys answers about my crispy sound question.

I finally found the little "fooker" :D it was my "Equalizer" app, who was in trouble with.

Had to reconfigure something with a bit less bass effects and now everything is ok, finally! ;) so it's not kernel fault!

Many thanks! :)
[Galaxy Tab  Android Development] OsitKP:
No rude. The only way you could have it working - you had no overcome kernel installed.
[Galaxy Tab  Android Development] OsitKP:
Did you try PowerAmp?
[Galaxy Tab  Android Development] koxudaxi:
@AndroidGX

thank you for your good news

i am relieved about your tab :)

@rxprenegade

this problem seems like overcome kernel is not bad which like my kernel on speed.

your tab probably has other problem. however i don't know it.

also your english is not bad. i can't use english well. but a lot of people talk to me. they have a tender heart;)

@OsitKP

i will research on tab why it is hotter .i felt it was warm when froyo.

@AndroidGX

i like to discuss with you. i am not perfect man who should be followed by intelligent parsons.

i usually test many times on a kernel. but Not all case is the best also the result may be the worst.

i can do the best with you and a lot of people.

a lot of thanks.
[Galaxy Tab  Android Development] ezynow:
Alrite k,

seem to have found the cause of my problems with smartass. I converted my sys to ext4 using chainfires tool. Simple one click process. My screen powers straight away and so far a bit more snappy.

Testing batt life rfs vs ext4 will report back.

Cheers
[Galaxy Tab  Android Development] AndroidGX:
I tried it there is few months, very nice app, really, but the equalizer is working only with the player, which is not the case with "Equalizer", who works in any app (YouTube, ringtone, etc..) ;)
[Galaxy Tab  Android Development] AndroidGX:
You are welcome kox, I really enjoy your work and all your release like everybody, you are doing a perfect job and we have chance to get you here!

I agree that I like critic, I guess it's the only way to improve something, hope my comments helps ;)

By the way I'am back to 3.0.12, and actually never encountered any problem with -125 at all levels (max 1000Mhz currently). Battery life is good but I can still confirm a bit less than 3.0.10.

We approach a perfect kernel here thanks to you. Keep the good work mate :cool:
[Galaxy Tab  Android Development] OsitKP:
For now I think I should take my words back. It's warm, but monitor shows temperature 27-32 C. Don't even know whether it's much or not. :)
[Galaxy Tab  Android Development] koxudaxi:
i was impatient ...i didn't understand why i couldn't solve many problem.

i forget to do relax.

i'm tired . i have two jobs that are the day shift for money and night work for galaxy tab.

to produce good idea need relax. i must do it.

tonight, i wouldn't develop to rest... :rolleyes:
[Galaxy Tab  Android Development] greenbat:
Bug report: FC's after bootup and hot back of Gtab

[kernel ver]3_0_11 and possibly 3_0_12

[Rom ver]overcome 2.0.1 Hermes

[up time] < 1 min

[governor]ondedemand

[I/OScheduler]sio

[previous kernel] stock overcome 2.0.1 (and before that oc 2.0 with koxudaxi kernel 3.0.8)

[bad point] after installing kernel 3.0.11 and 3.0.12 after booting immediately forced closures off several programs

Please note: I never had this problem with stock overcome 2.0.1 and overcome 2.0 with koxudaxi kernels up to 3.0.8
[Galaxy Tab  Android Development] 4exess:
Have a great and long one

U deserve it ;)
[Galaxy Tab  Android Development] greenbat:
bug report update

After full wipe and reinstalling OC 2.0 Gold running fine with koxudaxi kernel 3.0.11.

(So koxudaxi kernel 3.0.11 appears to be incompatible with overcome 2.0.1?)

Update 2: reinstalled OC 2.0.1 rom with koxudaxi kernel 3.0.12 up and running excellent with changed voltages!

Update 3: reinstalled 3.0.11 kernel with 2.0.1 rom: no more problems--> cause of upper mentioned FC's must be one of my updates programs!!!
[Galaxy Tab  Android Development] 4exess:
3.0.11 and .12 work fine on 2.0.1 Hermes

its not the kernel , everyone has different setups...apps backups whatever causin different problems for some
[Galaxy Tab  Android Development] triplex76:
cam is broken only for firmware after jk5..

i think that in order to work properly for other firmware the kernel should be taken from JM firmware family and patched.
[Galaxy Tab  Android Development] triplex76:
yes,already flashed and fully working...but if you could remove the NTT boot image is better and the integration of CWM would be great.

EDIT

I flashed your last version and I saw you removed the NTT logo.... great....so only add CWM and that's perfect!
[Galaxy Tab  Android Development] daniel.weck:
I've successfully converted my RFS partitions to EXT4, by flashing Koush's international_zImage using Heimdall (both "kernel" and "recovery" with the same image). The conversion process took place in recovery mode, and took a while.

I have just flashed zImage_eur_1 for kernel only (not recovery), and everything seems ok, except maybe the dictionary crash that happens in infinite loop !! :(

As soon as I figure out how to kill this stupid dictionary, then I will be able to check the EXT4 data (and verify internal SD card, etc.)

I'll be reporting about other problems, if any (looking forward to a camera fix though) ;)

Thanks !!! Dan

-- UPDATE -- Android automatically kills services that crash too often. Good. Now let's move "/data/app/DioDict_EngEng.apk" onto the SD card (for backup). I use SmartKeyboard, which I believe doesn't use the default dictionary.
[Galaxy Tab  Android Development] daniel.weck:
With the EXT4 conversion, the only remaining RFS partition is /efs.

Linpack still shows 19+ MFLOPS (expected), and Quadrant now shows 2111 (which is better than 1250 obtained using RFS :D ). Not bad. Not bad at all. The device feels really snappy, and the SetCPU profiles along with the low voltage means that the battery life doesn't suffer ! :)
[Galaxy Tab  Android Development] antiochasylum:
Push it to 1.6!! If the vibrant can do it why cant the tab??

Ill be all over this with 1.6 and CWM.
[Galaxy Tab  Android Development] jkurl:
Yes Please add ClockWorkMod and this kernel is golden. 1.6Ghz would be nice to see, but I am happy w/ 14Ghz. Please take a look at Modaco Paul O'briens Kernel. He has CWM integrated into it. That might give you some hints on how to do it.
[Galaxy Tab  Android Development] daniel.weck:
Yep. Right now I can't boot into recovery without re-flashing the international_zImage from Koush (for both "kernel" and "recovery", using Heimdall). When I try to reboot into recovery when I have this overclocked kernel loaded in the "kernel" only, or in the "kernel" AND the "recovery", then the Tab gets stuck on the white Samsung logo/text. I can only get back to download mode, which forces me to reflash international_zImage (the CWM ClockWork recovery mode from Koush). It's weird, I don't understand why it doesn't let me reboot normally once I have visited the non-working recovery. I also tried Paul's Modaco ext4+CWM kernel, to no avail (all with Heimdall).
[Galaxy Tab  Android Development] jkurl:
Wow pauls kernel won't allow you to use CWM either. Something is not right. I was able to flash his kernel back and get into CWM w/ no problems.
[Galaxy Tab  Android Development] koxudaxi:
ok,i'll set CWM method. it's true.

there is bad news.

i tried to add camera patch my kernel source(ver.ntt) .

the result is very bad.

i think i spend to apply the patch.

possibly i wouldn't success.

i'm finding that a kernel source is better than my kernel source .

what do you recomend?
[Galaxy Tab  Android Development] jkurl:
I would recommend it. Take a look at modaco kernel. It might give you a clue as to why the camera is broken and what you might need to do to get it working.
[Galaxy Tab  Android Development] koxudaxi:
@jkurl

i understand your messages. i'm watching modaco's initramfs.

i will put camera's problem. i'm thinking how to run cwm....
[Galaxy Tab  Android Development] daniel.weck:
Right, my TAR download was corrupted ! :rolleyes:

I haven't tried but it should work now.

I still have the issue that once this overclocked kernel is flashed, I cannot reboot in recovery (I get stuck on "Samsung" white-on-black screen). :confused: Do any of you run both the overclocked kernel AND the Clockwork Recovery successfully ? (i.e. at the same time, installed concurrently)
[Galaxy Tab  Android Development] darrenjdoc:
I got that earlier Daniel ...
[Galaxy Tab  Android Development] bendjlee:
Can some run the set CPU widget in the background and report back the running temperature when fully overclocked?

when using this kernel (even when undervolted to 1300) my tab runs a constant 37 degrees.. slowing the CPU down to 1200/1000 clocks don't have much impact on the temps.

I switched back over to modaco kernel and I am seeing a stable temp of 30 degrees(granted it is only 1000 clock)

I find this a little odd. Seems to me that my attempts to undervolt your kernel has no physical impact(hence the temperture)

Can anyone check/confirm?
[Galaxy Tab  Android Development] jkurl:
When I had this kernel installed no I could not run CWM as it is not integrated in it. I didn't give koush version a try. I may try it when I get home and see if it works.

@bendjlee

I don't think I ran the kernel long enough to get mine up that high. Once I found out CWM wasn't there and the sensors were not working I switched back. Once CWM is in it I am switching back and will push the sensor.so to fix that and then will fully test. I am not to concerned w/ the camera just yet. I know others are but I don't use it right now. I also dropped mine down to -75mv. give that a try w/ the voltage apk he included in this. mine only got to 30C for the time i used it.

UPDATE: @bendjlee I went to download koush CWM but the link is dead. I had the files at one time but I deleted them off my mac. If you can send me the files in a PM or post them on here I will give it a try.
[Galaxy Tab  Android Development] koxudaxi:
@bendjlee

this kernel don't need high voltage on CORE .but CPU get high voltage .

we can find this method in Galaxy s voodoo kernel.

this kernel can run very stable. if this kernel is tuned vdd valtage then we get low temps

[-----------------|
| |
| |----| |
| |low | <-core |
| |----| | <-cpu
| high |
------------------
[Galaxy Tab  Android Development] bendjlee:
Hi, yes the kernel runs really stable.

I am after suggestions to bring down the operating temperature whilst overclocked.to 1400...

As I mentioned I used voltage control to adjust the current however it had no impact...when running the kernel my tab does get noticeably warm(38-39degrees)

Can I ask what purpose does the Oc.txt and the voltage patch serve on your opening page, I haven't done anything with those files
[Galaxy Tab  Android Development] antiochasylum:
1.6??

10chars

Sent from my MoDaCo powered Galaxy Tab.
[Galaxy Tab  Android Development] abuser0815:
you guys wanna get it fried? :D

i would be happy if cam works and cfw.
[Galaxy Tab  Android Development] daniel.weck:
Capacitive buttons back light doesn't work :(
[Galaxy Tab  Android Development] af974:
Kernel 3.0.12

Rom mine

Previous kernel and rom cm7

1000 mhz

Default I/O

No undervolting

None a force close app

Average temperature 33C on battery
[Galaxy Tab  Android Development] greenbat:
You are right, reinstalled kernel 3.0.12 and 3.0.11 no more problems, so must be one of my yesterday market-updated programs!

Thanx for your comments!
[Galaxy Tab  Android Development] greenbat:
Benchmarks!

Benchmarks comparing Overcome 2.0.1 with stock kernel (Hermes) @1.4 Ghz and OC 2.0.1 with koxudaxi kernel 3.0.11 @ 1.4 Ghz

OC 2.0.1 Hermes @1.4 Ghz

Quandrant 2364-2653

Antutu benchmark 2436

Smartbench 2011 prod 1155 games 2895

OC 2.0.1 with koxudaxi kernel 3.0.11 @ 1.4 Ghz

Quandrant 2737-2507-2908

Antutu benchmark 2402

Smartbench 2011 prod 1266 games 2352

[[kernel ver]3_0_11

[Rom ver]overcome 2.0.1

[up time] almost 24 hours

[governor]ondemand

[I/OScheduler]sio

[previous kernel]overcome 2.0.1 stock kernel

[bad point] none!

[good point] working stable and running upper mentioned programs with 3.0.11 kernel and undervolting with settings:

1400 0

1200 -25

1000 -25

800 -50

600 -50

400 -75

200 -75

100 -100

Thank you, kernel master Koxudaxi!
[Galaxy Tab  Android Development] OsitKP:
Koxudaxi, you are absolutely right! To make smth decent you should have enough energy. So have a rest and get some. :D
[Galaxy Tab  Android Development] AndroidGX:
Hi kox!

I saw a bug on "Tweaks" app once flashed your kernel.

The function "Media: Stagefright" even with enabled and once rebooted is not turned on.

I saw it directly on the file "/system/build.prop" which was "false" at any stagefright levels. I turned them to "true" manually by "Root Explorer" and rebooted. Now Stagefright working really ;) hope this helps and you can do something about it? anyway this is not a major issue ;)
[Galaxy Tab  Android Development] nscosta:
Version 3.0.12 is very unstable, my tab was blockeed in every reboot, back to ab overcome 3.1 kernel...
[Galaxy Tab  Android Development] theerachai:
have you remove undervolt before you patch
[Galaxy Tab  Android Development] koxudaxi:
hi,

i'm troubled with my kernel. it should go to where.

i don't think good is to progress to groundless way.

ummm....:( but i can say only one thing, my kernel should be stable

ok, i will check the file.
[Galaxy Tab  Android Development] 4exess:
pic says it all

ur kernel IS stable!
[Galaxy Tab  Android Development] AndroidGX:
+1

The kernel is stable.

The only thing I can note after few days using it (3.0.12) is that I cannot see any real draining difference between 800Mhz and 1200Mhz for exemple. This is strange.. on my HTC Desire I can see any real gain about it.

I guess all people who get FC or bootloop, etc, did something wrong with rom install or wiping or restoring. If you are familiar with android rom world, you cannot say this kernel is not a bomb :D

Okay thanks kox ;)

*edit* :

btw I found my final stable UV settings via Voltage Control on this kernel :

1400 Mhz : 0

1200 Mhz : -50

1000 Mhz : -100

800 Mhz : - 100

600 Mhz : - 100

400 Mhz : - 100

200 Mhz : -100

100 Mhz :- 100
[Galaxy Tab  Android Development] rangercaptain:
I think you have built a stable kernal! And I am enjoying good battery life too.

People, remember to do cache wipes when you install, and only restore apps, not system data.
[Galaxy Tab  Android Development] AndroidGX:
kox, I saw another bug, which is not the first time I encountered this : when trying to open governor settings with "Voltage Control" app, the list doubled (and the first time I saw it, it was triple !), don't know why :(
[Galaxy Tab  Android Development] Alcibiade:
Happened to me too on Overcome's hermes (Without Kox's kernel). Seems to be a bug not linked to his kernel
[Galaxy Tab  Android Development] OsitKP:
Why so many people in this thread like to write "I've found a bug"?

Make a little effort - check for few times, reflash other kernel, check again. In other case you make koxudaxi waste his precious time finding unexisting bugs. No one gets benefits in such situation. Be careful, please, don't harm the reputation of the developer! What would you think of him if almost on every page careless people write "BUG"?
[Galaxy Tab  Android Development] rainbow ng:
+1

this uppset the developer much.
[Galaxy Tab  Android Development] 4exess:
Bug reporting is good but

neither "tweaks" or "VC" "bugs" u`ve encoutered are kox kernel related

tweaks doest work since Hermes and VC sometime messes up if u use setcpu

use blade buddy instead of tweaks and VC instead of setcpu
[Galaxy Tab  Android Development] AndroidGX:
Ok, thanks for report :) It's a ROM problem I guess then :(

Hello "guardian of the temple" #1, I have a message for you : I think you are a bit rude with me.. I only try to help kox as much as I can about finding bugs etc, to get him a nice kernel in such any way who can be my bug I was talking about. Now I know it's not kernel fault (anybody can make mistake as I'ma not a developper, are you ?) I can remember one thing, the overcome original kernel has been developped to be as stable as possible, and kox one the performances first. I'am agree anyway we are here for looking max performances and small battery drain. My comment can be took on a 2nd plan for futur update (eventually) I can agree.. but why tell me suck things as "Be careful, please, don't harm the reputation of the developer!" ?? I think you are wrong, I never said that. So YOU, please be careful to what you say ;)

And about the little effort you ask, when I write something here, generally It's already tested (ok this time I didn't have the time to flash overcome kernel and back to kox one, and ? sorry to have a life...) why you didn't at my place before posting useless post like yours ?

Moreover, I'am waiting for only kox answer when such a question, not really useless posts like yours, really. If he want to say me it's useless, he can tell me himself, not by a "guardian of the temple" ;).

btw, he told me I'am someone interessant and he likes my reports so if you want to check that, just click few pages back to check by yourself.

Hello "guardian of the temple" #2, I think the answer above is for you too !

thanks for watch'in!

(same for the dude who prefer to hit thanks button on useless posts..)

Ok as I think everything is now clear, we can discuss again about my real question :

You are right, it's Chainfire fault then :p
[Galaxy Tab  Android Development] af974:
I don't think is related to Chainfire error but it's more a system not mounted rw and that's strange though, because ro.secure=0 so it's should be rw.
[Galaxy Tab  Android Development] AndroidGX:
You are right.

I think his CF-Root mainly engender some incompatibilities with 2.0.1 overcome rom or something like that :(
[Galaxy Tab  Android Development] OsitKP:
The only sense of my post was: find a bug, think, write. Evidently you are capable to write only. (Before talking of rude reread your previous message).
[Galaxy Tab  Android Development] ezynow:
Hi koxudaxi,

can confirm a "bug /error / miscreante / guru meditation error" :D similar to above. Changing bladebuddy settings i.e stagefreight on / off does not work. It seems only after explicity mounting /system as rw then changes can take place. (explicit rw mounting in bladebuddy works. So i cant see why this extra step is needed :confused: )

Not sure what is wrong as this was working (the extra step of above was not required) on other kernels but not sure which one (maybe oc rc1 or earlier versions of ur kernel. )

Any thoughts? i am not sure if its related to ur kernel?

Using version.11 kernel.

Cheers
[Galaxy Tab  Android Development] koxudaxi:
hi,

sorry i can't replay to all.

recently, i don't have the time.

i will come back to here .Please wait ....

thanks
[Galaxy Tab  Android Development] kenzie6695:
testing it now benchmark went up to 2k after installation for overcome ... issues with modem though.. great power!!!
[Galaxy Tab  Android Development] Namaless:
Is possible to set 1.6?

Inviato dal mio GT-P1000 usando Tapatalk
[Galaxy Tab  Android Development] Alvin Lai:
There is a froyo kernel in first page. Make sure don't grab the wrong file to flash.
[Galaxy Tab  Android Development] nobleskill:
It doesn't change the build.prop it creates a local.prop in *//system/local* CORRECTION: /data/local.prop. This file hijacks the settings on boot from the build.prop and uses the values in its local.prop file.

Fire up rootexplorer and navigate to the file and you will see this. With blade buddy you also need to reboot too so just a play and you will see.

Hope this clears it up for you

Sent from my GT-P1000
[Galaxy Tab  Android Development] af974:
Correction, location is /Data/local.prop.
[Galaxy Tab  Android Development] ezynow:
This is what i thought but there is settings to apply in ram in bladebuddy. I am not sure if this like an echo 1 or 0 in /sys/value_somewhere.

I can see changes without rebooting for example in video app, you can see thumbnails that are normal resolution, if you enable stagefr player in bladebuddy and apply in ram ( need to mount system rw first but did not have to do this step before), then go into video app you can see the video thumbnails are distorted (looked like the resolutions is scaled up incorrectly). So setting are being changed allbeit tempoararily.

As a a month old newbie to android, i dont know much about stagefright and what seems to be a bug with its thumnails but i think a video app that can change stagefright player on or off based on video being a certain format should would be nice i suppose.

Any thoughts. ..