yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] bendjlee:
I have a suspicion that the battery heat sensors do not work under the v1.5 kernel version.

I would go as far to suggest that there is an issue with the modaco kernel base which v1.5 shares code from.

Try loading your tab and see whether the temperature meter fluctuates...for this kernel and also the modaco kernel it will stay a constant 30 degrees

The battery sensors definately works under the v2 rom although it alarms us to see the temperature of the tab reach upwards to 40 degrees.

I think the heat sensor is an issue and it gives us a false sense of security - especially here where we are overclocking the device…

Anyone care to disprove my claim?

Cheers
[Galaxy Tab  Android Development] Gpsrisk:
guys,

need help ...my internal sd card not functioning...." damaged internal sd card" ..

HELP!!!!!:confused:
[Galaxy Tab  Android Development] koxudaxi:
@darrenjdoc

sorry,this kernel doesn't support CWM yet.

@bendjlee

thank you for your post about caution.

i will confirm the source of the trouble .
[Galaxy Tab  Android Development] bendjlee:
Hi. Not sure how you did that but I did the same thing two days ago while trying out a bad kernel. So I may be able to help.

the easiest way I found was to reinstall rotos v5 rom (you must repartition your file system)

Hopefully you have a.nanddroid backup which you can then restore after your filesystem has been restored and you have your internal SD card working again...

(you should be able to do a nand backup now. That you can then restore back over)
[Galaxy Tab  Android Development] Justin^Tan:
Experience the same thing

modaco stays 30.0 all the time

i'm on v2 now and its just fine, yes it sometimes reach up to 37 and the part near the power screen gets hot, but at least now the battery sensor works, unlike on modaco kernel

if i leave it as is, it can go down as low as 28

if the battery sensor doesnt work, better i leave it on v2 since i cant be alarmed if the temp gets too hot unless i touch the part near power screen

@benjdlee

is there any relation between battery / temp sensor with the sensor default? if there is, would you mind try pushing it to see if it fix the problem?

@koxudaxi

since v2 even though experimental but mostly it works except sensor and camera, can't you just fix that?

sensor can be fixed easily anyway so that leaves us with the camera problem
[Galaxy Tab  Android Development] willingtonyuan:
Cannot mount SDcard on modaco rom
[Galaxy Tab  Android Development] daniel.weck:
Hello !:)

Could you please explain how you finally managed to make the "Update1" source code boot successfully ?

Could you please share your working .init configuration file, and tell us what initramfs you use to make this work ?

PS: the SD card corruption seems to be a common problem with another overclocked kernel on this forum...careful, make backups !! :eek:
[Galaxy Tab  Android Development] koxudaxi:
@willingtonyuan

i checked that this kernel can mount a sdcard on modaco rom.

external SD and internal SD are ok.

@daniel.weck

I forgot that he said this method.
[Galaxy Tab  Android Development] daniel.weck:
I know :)

Can you please send me your .config and tell me about the initramfs ?

Thank you ;)
[Galaxy Tab  Android Development] Alcibiade:
OK, everything works fine for me on v2 with Roto JMI ROM. Honto ni Arrigato gosaimasu koxudaxi !! Great job :)

Only issue is the camera :( Not that I care much but it can be useful sometimes...

When do we shoot for 1.6Ghz ? (Or say 1.5 ?)
[Galaxy Tab  Android Development] daniel.weck:
Ok, koxudaxi's Euro version (compiled from the "Update1" Samsung source code) boots fine ! :)

However, zImage_p1000-mck-r3-rfs (from MoDaCo) doesn't work on my Tab (infinite boot loop). :confused: :eek:
[Galaxy Tab  Android Development] Alcibiade:
Mmh now that there is 1.5 with working camera, this is tempting

koxudaxi, is it possible to flash v1.5 over v2 ? or I ma going to screw my ROM ?
[Galaxy Tab  Android Development] daniel.weck:
The camera works, nice :)

"sensors.default.so" is still needed to get the gyroscope, accelerometer and temperature sensors to function properly.

koxudaxi, the usual initramfs extraction script doesn't work on your kernel. It looks like your CPIO is not compressed, but the start/end positions are wrong:

"Couldn't match start/end of the initramfs image (start = 14377450, end = 14377364, count = -86)"

Do you use a compression when compiling ? (please send me your working .config and initramfs ramdisc, so we can solve this mystery...MoDaCo kernel is boot-looping on my Tab too !)

Regards, Daniel
[Galaxy Tab  Android Development] koxudaxi:
VZW: zImage_vzw_1_2mirrorNEW!!build from vzw soruce sode

@daniel.weck

nice job.

zImage_p1000-mck-r3-rfs can work on my galaxy tab.

@Alcibiade

thank you for your Japanese!!

ok,Could you please wait a few day !?

i have this roadmap .

1.2 -> 1.4->make from update1 source code

->zimage for VZW&sprint users->install self-build-CWM->1.5or1.6 ?

update1:

config

i used lzma.

update2:

lzma or bz2:D

yes,i put initramfs in the directory.
[Galaxy Tab  Android Development] daniel.weck:
Very strange. I can extract initramfs from MoDaCo's zImage, but not from yours !! :confused: Clearly these 2 "Update1" kernels are built differently, yet they are the same size (5.6MB). Could you please PM me your .config and explain what initramfs you use, and how you integrate it with the kernel during the compile process ? (sources, packaged CPIO ?)

Many thanks, let's solve this problem once and for all, to help the dev community!
[Galaxy Tab  Android Development] daniel.weck:
Many thanks ! I will try now.

Does "/home/koudai/android/SC-01C/initramfs" point to a folder, or to a pre-packaged CPIO ?

Your config says: CONFIG_INITRAMFS_COMPRESSION_BZIP2=y

(not LZMA)

By the way, the light sensor works, but not the temperature (I have a SetCPU profile that check the temperature, so this is not a reliable way to protect the CPU against overzealous overclocking ;) ).
[Galaxy Tab  Android Development] Alcibiade:
Wakarimashita. Matemasu :)

Watashiwa Nihongo chotto wakaru (Tokyo ni sundemashita)

Thanks a lot again for your great work
[Galaxy Tab  Android Development] daniel.weck:
;)

I suppose you are in bed now, but I'll ask again anyway: what initramfs source code do you use ? (the one from CWM, MoDaCo, CMSGS, ... ??)
[Galaxy Tab  Android Development] richardtrip:
It points to a folder.

If you need the MCR initramfs:

https://github.com/richardtrip/galaxytab_initramfs_MCR
[Galaxy Tab  Android Development] jkurl:
Holy crap this is getting confusing. I stopped messing w/ the kernel a while back once I found CWM wasn't in it and the sensor stuff not working. Man there is like 1500 version. Lol
[Galaxy Tab  Android Development] daniel.weck:
Just one thing to keep in mind: this MCR initramfs needs to be configured back to RFS for those who are not interested in EXT4 conversion, because init.rc and recovery.fstab mount /system /data /dbdata and /cache as EXT4.
[Galaxy Tab  Android Development] Alcibiade:
Btw any major difference with the patch in this thread (Except the camera working ehehe)

http://xdaforums.com/showthread.php?t=924654
[Galaxy Tab  Android Development] natious:
flashed

EURO:zImage_euro_2mirror

on modaco JMI r1

booted fine no sensors

replace sensors.so

sensors working fine

booted up nfs shift played for 20mins without a problem

set cpu confirms the overclocked

Excellent work, thanks!
[Galaxy Tab  Android Development] Justin^Tan:
same here

but my problem is the camera

did yours works?
[Galaxy Tab  Android Development] antiochasylum:
Does it have CWM built into it?

Sent from my MoDaCo powered Galaxy Tab.
[Galaxy Tab  Android Development] natious:
:(

just tested, no camera.
[Galaxy Tab  Android Development] natious:
I previously had cwm, and after flashing, its still there.
[Galaxy Tab  Android Development] Basil 123:
So it appears to be stable now? All the bits now working - getting ready to jump in here :-)
[Galaxy Tab  Android Development] bendjlee:
Howdy last I checked there are two versions both with a few limitations.

1.5 overclocked kernel

Temperature sensor.not working

No cwm

Ver2 overclocked kernel

Camera not working

Both versions require you to push the sensors file into system/lib/hw to get the gyros working
[Galaxy Tab  Android Development] Basil 123:
Hmm, maybe I will wait just a little longer for ultimate perfection.. Amazing how fast this kernel has evolved...

Noob question - I have to flash the zimage with Odin or is there a tutorial for the right adb commands for the tab?
[Galaxy Tab  Android Development] bendjlee:
Zimages are flashed via heimidall. For Odin you need to package the file before you can push it through. (I have not tried to repackage the file so can't help you out if you wanted.to.use odin)

Good luck
[Galaxy Tab  Android Development] natious:
Just use heimidall, its the same as odin in terms of difficulty, and you can just copy the .so file via root explorer. I did and it worked fine, i cant get adb push to work as the jdk wont install on my computer :/
[Galaxy Tab  Android Development] Basil 123:
Heimdall was pretty sweet to use - after I messed about with the drivers - nice to see that there is an updated 1.1.1 suite that optimizes Tab flashing.

Flashed the Euro 1.5 - just have to be careful not to use the MoDaCo reboot app - if you try to reboot into recovery, you need to flash the Euro 2 kernel to exit it.

Thanks !!!
[Galaxy Tab  Android Development] natious:
i just flash richardtrip trips v11, works perfect on modacos R1 camera working aswell
[Galaxy Tab  Android Development] biopsin:
Success

Flashed euro-1.5 ontop JMI and all fine, but battery sensor is still defunct. Also stuck in portrait mode..will try another sensor.so..OK worked with other sensor.so.

Clocked back to 1200 since tempsensor is nonresponsive, Voltage-Control wont save settings on reboot..updated from 3.0a to 3.0r1 not rebooted yet to check saved settings..

Good work!
[Galaxy Tab  Android Development] BuglessFan:
I tried the 1_2 version for VZW. It boots and finds the radio, but there's no browser and no market, so there's no way to restore apps or settings. I actually got a bit of a scare this time as after reflashing Koush's kernel I got a bootloop. When I booted into recovery it freaked out about the /data and /cache being in rfs. I went ahead with a nandroid restore, though, and it came back fine (whew!).

I thought about trying again with Titanium backup's apk ready on the SD card to do the restores, but since it gave the warning about the FS being rfs instead of ext4 I'm guessing it'd break Clockwork, and I can't live without nandroid restores.
[Galaxy Tab  Android Development] koxudaxi:
@BuglessFan

thank you for

i will proceed to build this kernel for verizon and sprint.

hi,everyone!!

i tried to break the walls of 1.6GHz.

Galaxy tab need high voltage to run on 1.6GHz.

but,Galaxy tab doesn't get high voltage. if you set high voltage then galaxy tab will hang up.

i can't find good ways....
[Galaxy Tab  Android Development] triplex76:
1.5 ghz should be good? no?

however I noticed that going higher than 1ghz doesn't give you any real advantage ... only benchmarks can tell you the difference... and the battery life of course;).

what I really don't understand how is possible that GT works without hanging even at all lowest (-200mV) voltage settings...are we sure about the voltage app... does it really apply those settings?
[Galaxy Tab  Android Development] koxudaxi:
my new kernel work all sensors without battery's temperature sensor.

this kernel don't need to replace sensors.default.so.

i can't find battery's temperature sensor section in kernel source yet...

i got initramfs on richardtrip's github.thanks richardtrip and Paul Obrien.

EURO:zImage_euro_2_5

this version doesn't have 1.5GHz clock tables.
[Galaxy Tab  Android Development] koxudaxi:
@triplex76

i build 1.5GHz version.this version run linpack and Quadrant.but this clock has very important problem.

it doesn't get appropriate clock.this chip-set has many clock tables.exp.cpu,2D,3D,ram,baseclock,nand,etc...

many clock tables depend CPU_clock.

*main_system_clock must be under 200MHz

*perimetral_devices_cloc must be under 100MHz

exp:1200MHZ

main_system_clock = 1200 / 6 = 200MHz

perimetral_devices_clock = 200 / 2 =100MHz

exp 1400MHZ

main_system_clock = 1400 / 7 = 200MHz

perimetral_devices_cloc =200 / 2 = 100MHz

exp 1500MHZ

main_system_clock = 1500 / 8 = 187MHz <<---very low clock.

perimetral_devices_cloc =187 / 2 = 93MHz <<---very low clock

exp 1500MHZ (Quadrant score is over 3300)

main_system_clock = 1500 / 7 = 214MHz <<---become freeze.

perimetral_devices_cloc =214 / 2 = 107MHz <<---become freeze

it is half truth.

richardtrip know about half truth.he ported it of Galaxy S OC_kernel

under voltage app applies TWO voltage on Galaxy S.these are (VDD ARM voltage) and (VDD INT voltage).

but galaxy tab version applies only (VDD ARM voltage).

(VDD INT voltage) don't go under voltage.

Galaxy S can change (VDD INT voltage) between 750mV and 1500mV.

Galaxy tab can change (VDD INT voltage) between narrow space.

we will meet 1.6GHz Kernel when Galaxy tab's (VDD INT voltage) can go to 1300mV

now,Galaxy tab hang up over 1225mV.
[Galaxy Tab  Android Development] Qsilver2001:
with temperature fix?
[Galaxy Tab  Android Development] Alcibiade:
Alright so 1.5 Ghz is not worth it :( And 1.6 Ghz won't make it until we have the full control over the voltage :(
[Galaxy Tab  Android Development] daniel.weck:
Hi, at the moment I am testing 3 similar kernels from different sources (koxudaxi, richardtrip and my own).

My home-built kernel works very well, it has the usual overclock, undervolt, the "interactive" scheduler, and Voodoo sound (and of course the complete EXT2/3/4 filesystem support, latest busybox and adbd, etc.). But:

The temperature is obtained only from the battery (not from the AK8973 sensor), and DroidWall fails (iptables and modprobe issues). Take a look here (3 posts in a row), and let me know if you experience similar issues.

http://xdaforums.com/showthread.php?p=11400438#post11400438

Cheers, Dan
[Galaxy Tab  Android Development] koxudaxi:
@Qsilver2001

this kernel version can work all sensors also it can get battery temperature.

@Alcibiade

i hope to work on 1.6GHz....:rolleyes:

@daniel.weck

hi,daniel.

i use only battery temperature.i don't know AK8973 sensor.:(

Did you say about compass? google says that AK8973 is compass.:eek:

i install and run DroidWall. it works fine.no problem!!
[Galaxy Tab  Android Development] daniel.weck:
Install Sensor Test or the Elixir app from the market, you will see the actual (shared) name of the hardware sensors ;)
[Galaxy Tab  Android Development] rayldf:
i try to install euro 2.5 under Modaco rom .. but the battery sensor said the battery is about 60 (it's too high) .. i can't to charge my tab .. and get flash back to origin kernel ...

orz...
[Galaxy Tab  Android Development] daniel.weck:
Hello, could you please upload you latest [.config] file for zImage_eur_2_6 at the usual online space:

http://koxudaxi.sakura.ne.jp/android/

I would like to compare with my config, maybe I have something wrong with my kernel build (although I have thoroughly checked already...:( ).

Thank you !! :)
[Galaxy Tab  Android Development] jkurl:
Ok I downloaded the kernel I need, but it does not look like the other zimages I have flashed. Is there anything special I need to do such as compile it. Still learning how to do certain things.
[Galaxy Tab  Android Development] Boushh:
Hey, just wanting to let you know, I didn't run all of your patches, I have already done most of the ones I wanted, but I ran uvcontrol_1_21_4_c and use1_2GHz.patch on my VZW Voodoo kernel and it patched just fine,. Thank you.
[Galaxy Tab  Android Development] koxudaxi:
@rayldf

Did you say about eur_2_6?

ok,I uploaded eur_2_6_1 what i fixed temperature method.

@daniel.weck

i didn't change the config which i already showed .

elixir app says that li-ion battery has temperature sensor.i confirm ak8973 obtain 1.0c in sensor tab.

@jkurl

you should use heimdall to flash nand.

good luck!!

@Boushh

thank you for your work!!

i hope to use OC_kernel by everyone.

you can give OC_kerne to verizon users .

I expect your good work.
[Galaxy Tab  Android Development] koxudaxi:
@daniel.weck

by the way, Is this photo your face?
[Galaxy Tab  Android Development] triplex76:
we can't see 1600mhz not cause of the inability to reach higher voltages ....but cause the cpu is unable to handle voltage higher than 1,3V... it just hangs.

I experienced random locks even at 1400mhz using higher voltage than 1,275V.

probably due to high temperature. the cpu and chipset got passive cooling.... probably it could go even higher than 1600mhz with relative low voltage but it should have an active cooling or at least some sort of heatsink...instead they are just "naked"
[Galaxy Tab  Android Development] daniel.weck:
Can you please share your source code / patch for fixing the temperature sensor ? The battery temperature on my Tab is always 30C, it never changes ! :o

PS: it's me on the avatar, but "inside" the glasses. :D

I'm the one taking the photo of the other guy who wears the glasses:

http://daniel.weck.free.fr/avatar_full.jpg

Easter egg ;)

:p
[Galaxy Tab  Android Development] koxudaxi:
EURO:zImage_euro_2_8

experimental!!

add 600MHz, UV internal voltages.

we can decrease total voltage than previous versions.

@daniel.weck

i don't think that this way is the best.but i could solve temp problem.

He surely know better method than it.

--- a/drivers/power/fuel_gauge.c 2010-12-23 11:25:57.000000000 +0900
+++ b/drivers/power/fuel_gauge.c 2011-02-17 23:53:31.087393250 +0900
@@ -613,7 +613,7 @@
else if(battery_type == ATL_BATTERY_TYPE)
return fg_read_temp3();
else
- return (s32)30000;
+ return fg_read_temp2();
}
[Galaxy Tab  Android Development] knightnz:
I flashed this zimage using Heimdall and it's completely broken my tab to the point where I need to do a full repartition & reflash. Flashing back to the old zImage using either Heimdall or recovery didn't work, flashing the entire Overcome firmware didn't work. Any combo just sticks at the "Galaxy tab" screen. Any idea why it might've caused this?

I _think_ I backed up with Titanium, at least I remember meaning to :) The CWM backup is useless as it ran out of space during the process and if it spat out an error then I neglected to notice.
[Galaxy Tab  Android Development] clubtech:
That's exactly what happened to me too.

I was running Rotto's JMI stock firmware with the 1_5 version of the kernel just fine (i was on EXT 4).

Then i flashed the recent 2.X kernel version and the tab would not boot. got stuck on the galaxy tab logo. tried to factory reset - no go.

Tried to flash 1.5 kernel, no go. still stuck.

I have to completely flash a stock firmware using Odin to get it to boot again.

Something in the latest 2.X kernel is seriously broken.
[Galaxy Tab  Android Development] knightnz:
Out of sheer bloody-mindedness I managed to resurrect my tab without doing a reformat. Got it into recovery, wiped everything (data, cache, dalvik, etc) - flashed the Overcome firmware and richardtrip's kernel and it fired up again.

Now because I'm a glutton for punishment, I'm gonna try this kernel again :)
[Galaxy Tab  Android Development] kay_kiat88:
same thing happened to me. just like what happened when i installed richard's v11. i did what u said here, was able to boot up. but sd cards were unmountable. in the end still had to do a full flash with partition :(
[Galaxy Tab  Android Development] koxudaxi:
@knightnz

@clubtech

@kay_kiat88

i think about the problem.

i pulled richard's initramfs from his github. so these kernel have same problem.

this version's initramfs merged with version 1_5.

EURO:zImage_euro_2_6_3
[Galaxy Tab  Android Development] daniel.weck:
Thank you, this works well-enough for SetCPU to trigger the low-performance profile in case of battery overheating. :)
[Galaxy Tab  Android Development] triplex76:
what are the difference between 2.6.1 and the 2.8 one :

http://koxudaxi.sakura.ne.jp/android/

I flashed the 2.8 ... it works well ... but it hangs sometimes if you try the setcpu autodetection...

i flashed the 2.6.1 and it works good but USB storage doesn't work but to tell you the truth I think the issue is related to CWM itself...cause I've never seen it working in not any revisions.

it hangs just as in 2.8 when you try to change frequency manually in setcpu.

maybe something is broken in voltage table for 600mhz.

however 600mhz ARE A GREAT ADDITION cause you can use almost every app (even 3d apps such as games and other!) without any additional need for power ... they works smooth so you can just save a lot of battery!

400mhz are just too less! 800mhz are a lil too much! 600mhz is the optimal compromise!

I think you added the frequency in the table...so it has a greater value...cause now the tab has one more step to work through and it should save some battery even for that.
[Galaxy Tab  Android Development] cruiserbax:
+1 for cwm I am on sprint tab using the sprint/vzw version, I also use the kernel by Boushh depending on who's current version works better. so far they are both great and I thank you both for such amazing work. once CWM is working on one of these kernels it'll be a nice fast complete kernel.
[Galaxy Tab  Android Development] koxudaxi:
@triplex76

hi triplex76!!

thank you

ok,i check usb storage problem.

zImage_euro_1*_* is pure oc kernel

zImage_euro_2_*_* is oc with cwm.

zImage_euro_*_5_* is build from update1 source code.(work camera) >=5

zImage_euro_2_6_* <--stable branch. change initramfs and sensors for stability.

zImage_euro_2_8_* <-- experimental branch. add 600MHz and UV for int voltage

@cruiserbax

thank you

i hope to distribute stable vzw/sprint version.

version 2 has cwm without converting rfs to ext4.
[Galaxy Tab  Android Development] triplex76:
oh great,

AWESOME JOB!

thanks a lot!
[Galaxy Tab  Android Development] triplex76:
I was a lil confused cause this link goes to 2.8 not to 2.6.3....

that's all.

never mind;)

just one more thing...

the voltage application is unable to read the voltage at 600mhz...I don't know how it works ... does it read the voltages directly from the internal Vtable?

so in 2.8 you finally found the way to change the intV?

great!

600mhz are a great welcome! even more than the OC itself!
[Galaxy Tab  Android Development] koxudaxi:
@triplex76

Could you tell me that which can work USB storage?

i fix usb storage and clock tables.

http://koxudaxi.sakura.ne.jp/android/zImage_eur_8_1

i met freeze when only change scaling type.

also i suppose to change int voltage is a danger .
[Galaxy Tab  Android Development] koxudaxi:
@triplex76

No,OC app don't get the voltages directly from the internal Vtable.

OC app has clocks and voltage tables. because OC app can't show 600MHz voltage to us.

i modified richard's oc_uv_1.2GHz patch.he didn't control int voltage.only did arm voltage.

he probably thought it come freeze and some problem.

but i think we need to change two voltage for battery life.
[Galaxy Tab  Android Development] triplex76:
sorry koxudaxi ... I'm speaking about the voltage app that doesn't show the voltage settings not the OC one (setcpu).

voltage-gt.apk if I remember well.:)

give it a look.... it can't read the current 600mhz voltage....so you can't set (lower or higher) the desidered V one.

I found an issue in both 2.8 and 2.8.1 ... accelerometer no longer works.

I tried 2.6 series and even there the accelerometer doesn't works.

other sensors work good... rotation and battery sensor are ok.

even in 2.8.1 usb storage still doesn't work.

If you could implement 600mhz in the old experimental version eur2 you will make me happy, cause it was the kernel I was using and it's just perfect upon JK5

it seems there is some sort of incompatibility among old JJ/JK firmwares and the kernel_update1 sensors management even if the the updated kernel sure is faster.