yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] jeff29:
Hi, Would it be possible to know what is the best configuration for voltage control, because my battery does not even have a very long day ... Thank you in advance!
[Galaxy Tab  Android Development] fastcx:
Sound familiar, perhaps can search the forum awhile? I have no solution to this other than asking you to redownload the file and install zip from sd
[Galaxy Tab  Android Development] gwbard:
not for nothing... but I've always used:

1) adb remount

2) adb push ... ...

no need for adb shell or complex mount commands ;)
[Galaxy Tab  Android Development] -Mr. X-:
this will also work, forgot about the simple things ;)
[Galaxy Tab  Android Development] warm.shine:
All right guys .

The commend finally work !

Really appreciate that you guys spending time for helping me !

But the battery sensor still show "overheat,stop charging"...

Nomatter how I wipe data、cache or baterry statuse...

What's wrong with my tab ???!!!
[Galaxy Tab  Android Development] -Mr. X-:
Probably a no brainer, but you have verified its not in fact just too hot?

After pushing the correct sensors file i would clear the cache and battery stats in recovery.

Cross fingers
[Galaxy Tab  Android Development] warm.shine:
Sure not overheat...

It show 68'C

If the temper was right , I cannot even hold by my hands....

Sorry for you guys wasting time of helping me.

Maybe I shound try a custom ROM...

Damn ! Shame of me !
[Galaxy Tab  Android Development] fastcx:
LOL probably you should, cause this kernel work best on new custom ROM, not stock rom
[Galaxy Tab  Android Development] warm.shine:
I've try a custom rom earlier , was made by a chinese(Hong-Kong)

And flash this kernel.

The battery still overheat...0.0

So I think I'll stock on V12.

Nomatter what.This is a really great kernel.

Maybe it's a single case of me.

Big thanks again for you guys helping~

You guys are my warm shine. LOL
[Galaxy Tab  Android Development] richardtrip:
Can create a kernel with a patched temp so you can use it (koxudaxi made a patch for it):

Test this one if you have temp problems: http://xda.richardtrip.org/tab/GalaxyTab_1400_MCR_ext_V14_patched_temp.zip
[Galaxy Tab  Android Development] richardtrip:
Update:

Version 15:

*changed recovery keys (extra keys, previous keys still working):

up = menu

down = search

ok = home

back = back

http://xda.richardtrip.org/tab/GalaxyTab_1400_MCR_ext_V15.zip

if you have temp problems try this one (only for older roms):

http://xda.richardtrip.org/tab/GalaxyTab_1400_MCR_ext_V15_patched_temp.zip
[Galaxy Tab  Android Development] TheGrammarFreak:
I got it, and manged to recover my data. Could we possible overvolt it? For stability like. :D
[Galaxy Tab  Android Development] acolwill:
http://xdaforums.com/showthread.php?t=829731
[Galaxy Tab  Android Development] TheGrammarFreak:
Will that allow me to overvolt too?

EDIT:

No, it won't :(
[Galaxy Tab  Android Development] crisvillani:
So does this kernel mess up the sensors on Att tab or is that just one person ?
[Galaxy Tab  Android Development] bpt888:
I tried flashing with this kernel via Phone option on Odin and the sensors were working. Problems is I lose my modem firmware and have no service. I'm using a Bell tab GT-P1000 with the bell_i9000.bin modem file.

Does it work for you on Rogers?
[Galaxy Tab  Android Development] crisvillani:
Im doin a backup now then im going to flash it will post later to see how it goes:D
[Galaxy Tab  Android Development] bpt888:
richardtrip, does the zimage in the TAR file contain a modem file?

Coz I think it flashes over our modem files for US/Canada that s why I'm getting "No Service" message and an unknown Phone version in system information.

This should work for all GSM tab right? If we can just remove the modem part of zimage so it does not overwrite other (countries) modem files.
[Galaxy Tab  Android Development] crisvillani:
Hey try flashing with pda button, not phone flashed it , everything seems to work good only thing is it deleted all apps and android market, but i then jjust did a advanced restore with CWM , and all apps are back, also all sensors seem to work:D
[Galaxy Tab  Android Development] rmanaudio:
Kernals have nothing to do with Modem or CSC or wiping any SD cards.

Stop blaming kernals for that.

Something went wrong during flashing for you guys!

I have flashed this kernal many times and other kernals and back and forth with ROTO KM2 and JME roms and have never lost my SD, apps, modem or any settings. All have stayed in tack....even when my TAB got bricked I brought it back to life with everything still there just by flashing a update ROM that did not repartition!

This Kernal is not optimized for NA GSM tabs for AT&T/ROGERS/BELL/FIDO! They Gyro sensor is the only thing I cannot get to work properly because of KM2 rom As soon as you flash a stock kernal it works. Everything else works perfectly.
[Galaxy Tab  Android Development] doloop:
failed on euro tab with CWM beta

Had my tab under roto V4 jme

CWM beta installed, ext4 system files.

flashed Zimage using heimdall

device filed it's screen with random pixels (from left to right)

display a t-mobile logo.

then seem to auto reboot,

filed it's screen with random pixels again

display a t-mobile logo again, and stuck there.

I stopped the device, flash back the international zimage for euro tab from CWM thread, the device autoreboot again around the glowing samsung logo.

I entered CWM under your zimage and saw that my ext4 partitions are still all there. Why my tab can't boot when i restore my old zimage, then ?

I entered CWM uner CWM beta zimage, it said it can't mount /data (invalid argument)

installed roto V4 jme full (no repartition) using heimdall

wipe data/cache through samsung recovery

device boots ok.

My sdcard is wiped !!! System says "your sdcard is blank or using an usnsupported file system"

Damn.
[Galaxy Tab  Android Development] bpt888:
ramanaudio, no one is blaming the kernel or said it was wonky. We are trying to figure out how to get it to work. Obviously others did it that's why its posted. Cool your jets and be helpful instead. All your ranting and you did not even mention what you did to get it to work. ;)

FYI, from previous posts, people were trying to flash this via Odin using the PDA option which wiped their internal SD (which people did not expect). Secondly, the following post from acolwill indicated to flash it with the Phone option, which he later edited but not after I tried it. Luckily I knew how to get my modem file back and I did not complain about it.

Now, crisvillani confirmed for me to use the PDA option and an internal SD wipe is inevitable or possible, which means I need to back things up. I didn't want to try with a wipe because I didn't have CW3 installed and can't do a nandroid backup. But I guess now I have to do that first to get this work.

Thanks crisvillani for confirming back.

Relax...breathe...and be happy we have OC now :D
[Galaxy Tab  Android Development] rotohammer:
I never heard of a kernel wiping apps or /sdcard, so I downloaded it to take a peek inside but accidentally triggered my Odin simulator in Linux and it got flashed. Yep, it wiped my apps and sdcard. WTF?

FYI, my Odin simulator flashes Odin tar files using Heimdall, so this isn't an Odin issue at all.
[Galaxy Tab  Android Development] roy8846:
Noob Alert...

Need some info please

Cant get Heimdall to work (missing .dlls) so which Odin is best to download??

And is there anything else needed??

Do I extract the zImage and flash that using pda option and uncheck repartition?

Is a Titanium Backup enough so I dont lose anything? I do not have CW on my Tab

I am on JJ7 Euro Tab by the way :)

Thanks in advance
[Galaxy Tab  Android Development] MaxiJavi:
You need the vcredist_x86.exe for VS 2010 ... Installs the runtime DLLs

I think it is this one :

http://www.microsoft.com/downloads/...5E-6DE6-4D3A-A423-37BF0912DB84&displaylang=en

I found it along with Heimdall, but I don't remember where I got it from :-)
[Galaxy Tab  Android Development] Nype:
Thanks richardtrip,

this is really good work. The kernel is snappy und quite stable.

But there are some little bugs:

1) As mentioned before the t-mobile logo looks weird (can't you just delete or replace it)

2) The display adjustment does not work. If I change for example the saturation the tab restarts.

3) There is another problem that causes a restart that I can not reconstruct. It happened while installing an app. After restart the installation worked fine.
[Galaxy Tab  Android Development] roy8846:
got Heimdall working..

Do I extract the zImage for the .tar and flash PDA????

And Titanium backup will be able to restore all my stuff??

thanks
[Galaxy Tab  Android Development] natious:
For the guys that have flashed, any notice in battery life dropping? I guess it only scales up when need be.
[Galaxy Tab  Android Development] richardtrip:
you can undervolt with the app (see first post).
[Galaxy Tab  Android Development] TheGrammarFreak:
I've undervolted by 200mV and it *seems* to be fine. At the moment.
[Galaxy Tab  Android Development] richardtrip:
1. The logo will be changed in future versions.

2. The display adjustment is working fine on JME V4

3. Never seen that on my device. Can you post a logcat when you uninstall/install and the problem is there again?
[Galaxy Tab  Android Development] -Mr. X-:
Thank you sir, if you could, can you enable 1.5gHz as well so we can try and see if some of our devices can achieve this?

Thanks a lot for the kernel by the way im enjoying it so far!
[Galaxy Tab  Android Development] warm.shine:
Sorry Sir.

Both two new patch cannot solve this problem....

It's OK,sir.

I'll use V12 even it cannot show the right temp but still can charge~
[Galaxy Tab  Android Development] antiochasylum:
+1 please give us 1.5 or 1.6! Lol
[Galaxy Tab  Android Development] jayavinash:
Is it normal my battery temp. shows 42c while charging and 38c when it is not charging.tq
[Galaxy Tab  Android Development] thenashy:
On booting, when the tab displays the Galaxy Tab splash, I get a heap of distored colours on the left (portrait) which flash for a second or two, then go away.

It boots normal.
[Galaxy Tab  Android Development] richzzp:
Does it works normally now with this kernel?

I've the same situation while flash V14 with recovery, I'm a HK P1000 with official ROM.

or it just can't support HK P1000?

Thinks!
[Galaxy Tab  Android Development] -Mr. X-:
mine does the same and this seems to be normal for some SGT's, so no need to worry about it.
[Galaxy Tab  Android Development] richzzp:
Thanks for your kindly reply.

Does my tab can still boot normally after that? and I just need to wait for a longer time?

I've already ext4 converted with CWM, after flashing V14 and rebooting, the distored colours appears quickly, then i wait about two or three minute again, it just show Galaxy Tab splash and not going on。

Worrying about whether it can support my tab or not, I recover to my previous kernel.
[Galaxy Tab  Android Development] spirit32:
same here.
[Galaxy Tab  Android Development] shmigao:
Known issue to all these kernels (modaco and this uv/oc)
[Galaxy Tab  Android Development] fastcx:
Can you get into recovery? Anyway, which rom are you running now on?
[Galaxy Tab  Android Development] richzzp:
I can enter recovery normally.

I'm using HongKong P1000 with official ROM, newlly installed the OC CWM kernel from here http://xdaforums.com/showthread.php?t=943669.
[Galaxy Tab  Android Development] fastcx:
But still unable to get past boot logo? Did you cleared cache in cwm? Or perhaps install custom rom and do dalvik-cache wipe?
[Galaxy Tab  Android Development] shmigao:
P1000 no problem

Locked bootloader maybe?
[Galaxy Tab  Android Development] warm.shine:
I got it . Sir !!!!

I've flash koxudaxi's kernel of

HKTW:zImage_hktw_2_3 mirror NEW!! with cwm,ext4,+600MHz,UV+int-voltage

And all of the sensor works perfectly!!

But it doesn't incloud voodoo sound . Could you please check this kernel where's deffirence btween your kernel ?
[Galaxy Tab  Android Development] turruso:
I get the following message with clockwork

install from package. . .

Finding update package. . .

Opening update package. . .

Verifying update package. . .

E: failed to seek in /cache/update.zip invalid argument

E: Signature verification failed

any help is greatly appreciated thanks
[Galaxy Tab  Android Development] antiochasylum:
Maybe try a redownload? Or try and toggle signature verification off in CWM
[Galaxy Tab  Android Development] Qsilver2001:
Why are you flashing it as package Update.zip?

Under Cwm, select flash from zip in sdcard. Then select from your sdcard the kernel zip file.

Thats what i did. Thot i could be wrong, hope some experts can chime in.
[Galaxy Tab  Android Development] jkurl:
No you are right. They should be using flash from zip on sd card.
[Galaxy Tab  Android Development] -Mr. X-:
What sensors are we talking here, the only one i notice that may or may not be legit. Is in my system panel app i have battery temp and then AK8973 Temp. which is not registering. I'm also thinking the light sensor is not working with v16 and the included sensors.default.so because any app i use to try and pole the light sensor data comes back empty and it does not appear to me reacting when i cover the sensor.

Can any one else confirm the validity of my above claims?
[Galaxy Tab  Android Development] jeebspawnshop:
Hi Richard.

Just wondering if this post from daniel.weck would be of any use to you and your kernel;

http://xdaforums.com/showthread.php?p=11456176

But if this is not really something Richard can use, don't suppose anyone out there smarter than me knows if this is of any use to us at all?

If we're running this kernel (which is awesome, by the way) then we're here to get as much speed as we can ;) I also would like to know if these tweaked settings are "compatible" with this kernel, or would they potentially break something?

Thanks for looking guys.
[Galaxy Tab  Android Development] richzzp:
I do nothing after flash, just reboot. I will try clearing or wiping at first boot to see if it will be ok.

Thank you very much!
[Galaxy Tab  Android Development] cx5:
Hi richardtrip

Hope you can help me identify my mistake ...... appreciate your help very much....

original baseZHJJ1/buildZHJK1

then kernel to koxudaxi_hktw_2_6_3

then kernel to hktw_2 CWM EXT4 conversion ->boot loop

then kernel to hktw_2_6_3 -> boot loop

then Heimdall factoryfs.rfs from rotobackup the original unit

OK

Itchy wanna WIPE/factory reset -> process complete -> no effect :(

then to rotohammer_JMIv2 lost 1.4Ghz,

then re-kernel_koxudaxi hktw_2_3 boot-loop :(

then kernel_xda_richardtrip boot-loop :(

reboot into recovery-mode shows EXT4 CHECK intact

-select install from zip by Overcome1.1.3.zip rename into update.zip also failed

--Finding update package

--E:failed to mount /sdcard(Invalid argument)

--E:can't mount /sdcard/update.zip

--Installation aborted

-select WIPE

--Formating /data.. /cache.. /datadata. /se-ext.. /sdcard/.android.secure

--E:failed to mount /sdcard(Invalid argument)

--E:can't mount /sdcard/update.zip

--Skipping formating

--Data wipe complete

Reboot 1 OK hang

Reboot 2 OK OK hang

Reboot 3 OK OK OK hang

Reboot 4 OK OK OK OK hang

give up

Reflash kernel by koxudaxi hktw_2_3 reboot OK

-sdcard can't mount within android. empty empty, not even the usual data folder

apk Temp+CPU V2 shows 1GHz only

apk CPU Tuner shows 1GHz only

still looking for other solutions ..............
[Galaxy Tab  Android Development] shmigao:
1) flash rotohammer jmi v2 with pit and repartition enabled

2) flash modaco custom kernel r3 (on reboot long press power to shut down and restart into recovery then ext conversion will start)

3) flash kernel in this thread

4) flash modaco custom rom r1

Then should work

If you have locked bootloader, check rotohammer bootloader patch
[Galaxy Tab  Android Development] fastcx:
I suggest you redo from ground up.

Flash roto rom with pit file and repartition.

Once done, check for locked bootloader with apk file from here.

If not locked, then proceed to flashing modaco custom kernel from here and do ext4 conversion.

Once that done, flash overcome or modaco rom, whichever you like.

Once all that done, install kernel of your choice through clockwork ;) enjoy!
[Galaxy Tab  Android Development] knightnz:
I've had the same problem, the Koxudaxi kernel fries something somewhere necessitating a complete ground-up reflash. I managed to reinstate mine by reflashing Roto's JMI, then MCR's ext4 kernel, doing the conversion, then flash back to the Overcome firmware, this Voodoo kernel and running a nandroid restore. Pain in the arse but got all my stuff back.
[Galaxy Tab  Android Development] richzzp:
Flashed again V15 with cwm this morning

Wiped cache and reboot, stopped at Galaxy Tab splash...

Reset to factory settigs and reboot, still stopped at Galaxy Tab splash...

Checked bootloader, it's unlocked!

Should i must flash a custom rom to get this kernel work on my tab?
[Galaxy Tab  Android Development] fastcx:
:) most probably, cause i believe none of us us stock rom after we converted to ext4
[Galaxy Tab  Android Development] jeff29:
Hello, I need your help. My battery does not last a day install this kernel. I put voltage as:

1400MHz -200

1200MHz -200

1000MHz -200

800mhz -200

600MHz -100

400mhz -100

200mhz -100

100mhz -0

I'm BFQ. Can you please come to my rescue. :(

Thank you
[Galaxy Tab  Android Development] Qsilver2001:
You are not alone. I set my UV all to -200. Batt drains like 1% per 10mins. I also encounter the tab not waking up after screen is off for quite awhile. Have to push and hold 10sec for it to boot to boot screen again. Thot this happens when i install SetCPU. Uninstall tht will not happen. I also notice my display is using hell lot of batt, at abt 70%.

Not sure about the rest who had this kernel installed having turbo batt drain :-P
[Galaxy Tab  Android Development] -Mr. X-:
Lowering your voltage too low cause your cpu to spend more time on max load as its working hard because its starved.

i seem to get a day out of this but maybe im not using it as heavy as you guys.
[Galaxy Tab  Android Development] shmigao:
Screen not waking up probably not related to uv setting but rather setcpu screen off profile. What are your settings there?

I found less than 400 and on demand freezes the phone.

My screen off profile is 400 min/max performance
[Galaxy Tab  Android Development] JanovPelorat:
I'm stuck on the Samsung boot logo screen with the blue glow. Here's what I'm running:

Stock P1000XWJMI firmware without signed boot loaders (flashed with Heimdall). Updated to EXT4 Using p1000-mck-r3-ext4-cwm. GalaxyTab_1400_MCR_ext_V15.zip flashed using recovery directly from SD card.

The issue seems to be the sensors lib. I've tried the stock one from P1000XWJMI and the one in the first post, but neither works. The issue is that system_server crashes with SIGBUS (7)

logcat attached.

EDIT: Correction; I've only tried sensors from the .zip and the loose one. I've not tried the stock sensors, I have to extract it from the backup and try it i guess.

EDIT2: Works!

I managed to get it working by restoring the clockworkmod backup that was created during EXT4 conversion, this restored the original sensors library. Next I reflashed p1000-mck-r3-ext4-cwm followed by the GalaxyTab_1400_MCR_ext_V15.zip zImage _ONLY_! (using heimdall)

Now for my next problem; while I get better quadrant scores due to EXT4, the device in general feels more sluggish than when I'm running P1000XWJMI with stock kernel.
[Galaxy Tab  Android Development] Qsilver2001:
Thanks for your tips, will try it out. As mine was set at min 100 - max 400, conservarive/on demand. Both was have that problem.
[Galaxy Tab  Android Development] Qsilver2001:
Guess i will try to lower bit by bit till i find my tab's sweet spot
[Galaxy Tab  Android Development] JanovPelorat:
Which SetCPU and voltage value settings matches what the stock JMI kernel is using? I am unable to find a profile that works satisfactory without lag. Even on performance with 1Ghz the lag is worse than on the stock kernel with all partitions on RFS :confused:

I've wiped cache and dalvik cache too so that's not the problem.
[Galaxy Tab  Android Development] fastcx:
For screen off, i'm running 200/200 performance without issue with waking up my phone and dnt get much issue with waking up for incoming calls :cool:

@richardtrip,

Perhaps you can consider adding some init script tweaks suggested in here?

Maybe even putting such options in recovery menu like here.

Personally thinks that similar tweaks should be included in custom kernels for our Tab so that those who wish to do more extreme settings can go with it while those who just wants increased performance as it is can still have the boost provided by such init script.
[Galaxy Tab  Android Development] shmigao:
Yeah, I am mostly playing music via bluetooth when screen off, and get freeze when under 400/400 performance

There may be the difference
[Galaxy Tab  Android Development] richzzp:
Thank you for your reply.

I'll try flash zImage only just like JanovPelorat does....
[Galaxy Tab  Android Development] fastcx:
Probably, did u do uv for 400mhz?
[Galaxy Tab  Android Development] shmigao:
yep I did, changed to no UV now, and down to 200/200 - let's see how that works
[Galaxy Tab  Android Development] monyozt:
after installing lastest kernel, i can't charge my tab as it said "charge paused, batree temp too high or too low" so when i flash the temp patch it will slove my problem?
[Galaxy Tab  Android Development] fastcx:
hmm hope it works, but my condition was without music player, hvnt tried with music player on tho
[Galaxy Tab  Android Development] triplex76:
sorry but this is not true ... voltage and speed got no relation at all..if the voltage is too low it may lock ... sure not increase its speed.
[Galaxy Tab  Android Development] jeff29:
Can a kind soul can give us his setup? So that finally our batteries last longer??

Voltage and SetCPU ...
[Galaxy Tab  Android Development] h_shakil:
Setting the CPU Clock to 1200Mhz or 1400Mhz and saving the setting for boot is causing my JPJM4 ROM to hang on startup (on the Galaxy Tab screen), re-flashing MCK kernel or even restoring Full backup from recovery doesn't fix it and the only way is to re-partition and re-flash stock/Roto ROM

Does the "Save as boot settings" in Voltage Control change anything other than adding the init.d/S_* file? I tried removing the file and booting and it still hangs.

All works well (even at 1400Mhz) if I just "Apply for now" in Voltage Control.

The same problem existed in V13 and upgrading to V15 didn't help.
[Galaxy Tab  Android Development] melodicstealer:
does anyone asked this before?? after i flash this kernel, my ap*lan*t market stop working, its said parse error...what should i do?? thanks for ur help
[Galaxy Tab  Android Development] kay_kiat88:
you should not use applanet at all.
[Galaxy Tab  Android Development] melodicstealer:
phew...sorry, i shouldnt asked that here
[Galaxy Tab  Android Development] cx5:
Thanks shmigao, fastcx, saved the deviced back to normal operation. Conclusion link http://xdaforums.com/showpost.php?p=11684727&postcount=495
[Galaxy Tab  Android Development] fastcx:
#SOLVED#

Using UV script to run other init script settings, putting another init script in init.d obviously doesn't run
[Galaxy Tab  Android Development] @gung:
similar here, after the temp patch. still getting the same result. Could anybody help please? :(:(:(
[Galaxy Tab  Android Development] Asure:
Hi Richard,

Looking at a teardown, i noticed the cpu is actually 110, instead of 210.

But, for example, the OC patch is done on 210 machine. I know they're 99.9% similar except for some ddr/onenand driver..

Did Samsung mix this up already on their side when they released the source?
[Galaxy Tab  Android Development] JanovPelorat:
Should I have an init.d folder with some scripts in it after flashing the kernel? I don't have the init.d folder so I created one manually and put a custom script in it but the device no longer boots after that.

EDIT:

Works now! I had forgotten to chmod the script to have +x. And I had to add "setprop mcr.filesystem.ready 1" at the end as well.