yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] TheGrammarFreak:
All seems to be fine. I use the conservative governor.
[Galaxy Tab  Android Development] bendjlee:
Anyone care to try Bluetooth? I've tried it on both the v12 and v13 kernels with no success... I am currently on overcome1.1.3
[Galaxy Tab  Android Development] KChauJen:
Glad to see your Tab's working as you want.

Take care,

KC
[Galaxy Tab  Android Development] natious:
Hit 46* today using GPS and full brightness for 30mins, kinda scared me lol

Sent from my Galaxy Tab of awsomeness
[Galaxy Tab  Android Development] daniel.weck:
Is that the battery temperature, or the temperature readout from the AK8973 sensor ?
[Galaxy Tab  Android Development] :
is that with 1.4 or 1.2 mhz setcpu max ?
[Galaxy Tab  Android Development] natious:
Battery via elixer, AK sensor says 1* for me all the time

Sent from my Galaxy Tab of awsomeness
[Galaxy Tab  Android Development] natious:
1.4 -200 voltage

Sent from my Galaxy Tab of awsomeness
[Galaxy Tab  Android Development] :
hmmm!

it seems to me that this temperature is not good for the battery life...
[Galaxy Tab  Android Development] fastcx:
No issue here pairing on overcome 1.1.3, v13 kernel, i believe you use TB to backup apps? Do not bring forward system apps and their data..
[Galaxy Tab  Android Development] natious:
which function in voltage control are you guys using , noop, qcb, ect...
[Galaxy Tab  Android Development] fastcx:
Er, obviously just to set each clock speed's voltage..u can choose to reduce or increase how many mV you wants, then apply..when you feel it's stable enough, save it for boot up
[Galaxy Tab  Android Development] kay_kiat88:
i think he's talking about the scheduler lol. bfq or noop
[Galaxy Tab  Android Development] triplex76:
on demand governor and conservative will lock the tab when in idle with screen off.the best way to go after several tests is to set 100mhz with fixed clock ...that is performance, it will fix the clock to that frequency avoiding any sudden change that generally locks the tab.I use it at -200mV all settings and no problem at all....only remember to create a profile for USB CHARGING and to set that with an higher priority than the screen off one.this will prevent the tablet to work at 100mhz when connected to the pc even when the screen is off avoiding poor performance during usb data transferring.;)

AC charging profile is ok to work with the screen off 100mhz profile.it even greatly decreases the time needed to charge the tablet ...that's great.
[Galaxy Tab  Android Development] fastcx:
that's not function..it's scheduler..just keep bfq, or you can test on others, noop n bfq shouldnt have too much difference in performance
[Galaxy Tab  Android Development] MaxiJavi:
Bluetooth seems to work better for me with this kernel and Modaco's ROM.

I am fully undervolted and Bluetooth works perfectly, even when Wifi is turned on (before I had problems).
[Galaxy Tab  Android Development] knightnz:
Try using the Conservative governer, On-Demand seems to be flaky.
[Galaxy Tab  Android Development] knightnz:
For some reason Samsung apparently already had voltage tables in place supporting 1.2 and 1.4Ghz.
[Galaxy Tab  Android Development] daniel.weck:
The Galaxy Tab in latin america is clocked at 1.2GHz, probably to cope with the digital television tuner.
[Galaxy Tab  Android Development] antiochasylum:
And the new Verizon tab being released supports LTE and is running at 1.2!
[Galaxy Tab  Android Development] natious:
Damn, I want digital tuner on my tab lol

Sent from my Galaxy Tab of awsomeness
[Galaxy Tab  Android Development] shmigao:
Ok, I got my music/video lag figured out

I checked logcat and every lag event was preceded by a wifi lock (while moving about on highways with ever changing wifi APs)

While this should still not result in lag, simply deactivating wifi while moving about will do for now.

I blame it on a sub optimal backup recovery. Will factory reset on next ROM update

Happy camper with setCPU and UV now :-)
[Galaxy Tab  Android Development] shmigao:
100mhz with screen off does still quasi-lock tab when playing music. I am trying with 400mhz
[Galaxy Tab  Android Development] halftonehero:
Thank you again, Mr. Trip. Your kernel keeps getting better.
[Galaxy Tab  Android Development] fastcx:
min 100, max 400, works for me with on-demand, i tend to not mixing(different profile different governor) governor just to avoid freeze.

Conservative works better on stock kernel, on-demand is more stable(don't cause freeze ezily) now on custom kernel, so on-demand is recommended to avoid freezing.
[Galaxy Tab  Android Development] shmigao:
Your statement is exactly opposite to what triplex76 said...

Who is right?
[Galaxy Tab  Android Development] MaxiJavi:
For me "conservative" is the only reliable option.
[Galaxy Tab  Android Development] fastcx:
Perhaps it's due to different revision on hardware? Mine is SEA tab, running on-demand well enough, all well but there were twice if I do screen lock and unplug charger in consecutive, it will freeze cause I use performance for charging AC while screen off is on-demand priority 100, charging AC priority 97.

My profile is as following,

Screen Off - 400 max, 100 min, ondemand, Priority 100.

Charging AC - 1400 max, performance, Priority 97.

Temp > 50.1c - 400 max, 100 min, ondemand, Priority 94.

Battery < 16% - 400 max, 100 min, ondemand, Priority 88.

Battery < 51% - 800 max, 100 min, ondemand, Priority 86.

Battery < 86% - 1000 max, 100 min, ondemand, Priority 82.

Battery < 101% - 1400 max, 100 min, ondemand, Priority 80.

With this setting, I did get freeze twice on the situation I mentioned above, no issue for the rest of the situation. For weather condition in Malaysia which is lowest around 25c at night, 29~32c in day time outside, consider quite good with temperature not over 40c in 1400 performance + charging.
[Galaxy Tab  Android Development] daniel.weck:
Have you tried the "interactive" mode ? This is essentially like the "on demand", only without polling (based on idle status).
[Galaxy Tab  Android Development] fastcx:
Tried it, because it gets too "responsive" in terms of rising mhz steppings, it makes battery temperature rise too fast and worse battery live.
[Galaxy Tab  Android Development] fastcx:
1 thing I'm not so sure is swap support in this kernel, but I suspect this kernel supports it
[Galaxy Tab  Android Development] daniel.weck:
Android doesn't use RAM <--> disc swap.

Coincidentally, this startup script disables swap explicitly, just to make sure :)

http://xdaforums.com/showthread.php?p=11448321#post11448321
[Galaxy Tab  Android Development] antiochasylum:
Only profile I have set is 200 200 with on demand while screen off. Its set as interactive with Max of 1000 everyday use.

No freezing no lag.

I think to many profiles will cause lags and freezing honestly.

Edit: that's not undervolted at all. All stock voltages.
[Galaxy Tab  Android Development] :
where are the benefict between this kernel (set max clock to 1mhz) or standard modaco kernel?
[Galaxy Tab  Android Development] antiochasylum:
Nothing honestly both are similiar on speed at 1000 however this kernel can be clocked at 1.4 to show off. Lol.
[Galaxy Tab  Android Development] natious:
anyone else have a problem with the accuracy of the battery monitor in the status bar, mine will say 50%, yet in reality it has 5% left.

Also, underclocked it seems to be draining the battery faster, i barely get a day out of a full charge. ( everything is off, and screen is usualy on auto)

:/
[Galaxy Tab  Android Development] lambstone:
Nope, no problems here. My battery discharge rate is even less when I was running stock.
[Galaxy Tab  Android Development] JanovPelorat:
I'm running P1000XWJMI (flashed with heimdall 1.1.1 but without the signed boot loaders). Now I flashed this kernel with Heimdall as well and the kernel boots, but gets stuck on the SGT screen. Looking at dmesg I see that the system partition is not mounted and neither is /etc. There's an error saying that init cannot find 'dd' and '/system/bin/sh'

Anyone know what might be wrong here?

EDIT: I flashed the latest v13

EDIT2: This is a rooted JMI with cifs.ko and slow-work.ko already installed.

Flashing back the old P1000XWJMI kernel works fine and then it boots up properly.
[Galaxy Tab  Android Development] richardtrip:
You can undervolt this kernel (voltage control app) at all frequencies.
[Galaxy Tab  Android Development] triplex76:
ah ok, if you use some service when the screen is off you need more mhz than 100...of course, it could be usefull for you the koxudaxi kernel that has implemented the 600mhz step.awesome stuff...I'm sure richardtrip will follow the route.
[Galaxy Tab  Android Development] shollywood:
Forgive the dumb question but...If I flash a new ROM do I have to reflash this kernel again and redo my ext 4 file system? TIA!!
[Galaxy Tab  Android Development] natious:
Nope

Sent from my Galaxy Tab of awsomeness
[Galaxy Tab  Android Development] TheGrammarFreak:
You will need to flash the kernel again if you want to keep using the OC, but the ext4 filesystem should stay. :D
[Galaxy Tab  Android Development] shollywood:
Thanks for the response(s). Has anybody else had troubles pairing thir bluetooth devices after flashing this?? I cannot pair for the life of me. Finds the device asks me if I accept then quits???
[Galaxy Tab  Android Development] shmigao:
Several had this. Try delete bluetooth cache / data in app settings

Otherwise a factory reset will fix this problem
[Galaxy Tab  Android Development] rangercaptain:
Clearing the cache ( I used the CWM3 menu option) clears up the pairing issue and stopped all the studdering I was getting when I was listening to music.
[Galaxy Tab  Android Development] natious:
i just flashed overcome over modaco, oc kernel is still in place.
[Galaxy Tab  Android Development] shollywood:
Can you explain this a little more? I can't find where to clear this??
[Galaxy Tab  Android Development] captain134:
Yes, I have noticed that I have this problem. I have a Bell GT-P1000M. On v13. Modaco rom.
[Galaxy Tab  Android Development] kay_kiat88:
it really depends on the rom itself. like for modaco, paul indicated that kernel is included. so when u flash his r1, it includes the kernel. for overcome kernel it is not included.
[Galaxy Tab  Android Development] kay_kiat88:
off your tab first.

switch it on again by holding up and power button. you will get into cwm recovery.

choose the appropriate option to clear cache.

reboot tab.
[Galaxy Tab  Android Development] natious:
i just flashed overcomes rom to see how things go

speed wise its the same i think, but it seems to be running cooler, and the battery looks like its working correctly
[Galaxy Tab  Android Development] captain134:
Awesome thanks for your reply.
[Galaxy Tab  Android Development] ayman07:
Just wanted to post my results. I'm a bit surprised that it worked this time since all by other attempts failed miserably. I'm on a tmobile with Overcome 1.1.3 & MCR kernel. Flashed with recovery and booted right up. Sdcard content still there.

From the Tab.

www.twitter.com/ayman07
[Galaxy Tab  Android Development] shollywood:
Much appreciated
[Galaxy Tab  Android Development] ayman07:
Camera crashes for me. Maybe because my LCD density is 180. I heard it causes issues.

From the Tab.

www.twitter.com/ayman07
[Galaxy Tab  Android Development] lxxxxxr:
Change it to 182;-)
[Galaxy Tab  Android Development] carlsbad0331:
Installed on T-Mo with overcome. I havent found anything that isnt working properly and it seems much quicker.

Thank you!
[Galaxy Tab  Android Development] antiochasylum:
Plus one. The camera will not work with LCDD below 182.

Sent from my MoDaCo powered Galaxy Tab.
[Galaxy Tab  Android Development] ahahha:
Dear all,

I just download the GalaxyTab_1400_MCR_ext_V13

using heimdall frontend to start the zImage file.

but after reboot. it stuck at SGT logo.any solution and why does it occur?

original rom, with root and SGT BOOTLOADER PATCH
[Galaxy Tab  Android Development] celestar32:
Hv you convert it to ext4. This is an kernel not rom.
[Galaxy Tab  Android Development] ahahha:
nope.any solution to make it normal again?
[Galaxy Tab  Android Development] jeebspawnshop:
Man, all you gotta do is read a bit (there aren't THAT many posts here) and perhaps even use the "Search".

It has been covered, and repeatedly extensively, that this kernel will only properly work on Overcome ROM or Modaco ROM.

If you flash this kernel over stock-ish ROMs, then it likely won't work. And if it does, it causes some pretty weird problems.

EDIT: The only way to fix it is to reflash stock ROM (with Re-Partition) in Odin. Or Heimdall I guess, but I don't use that one.
[Galaxy Tab  Android Development] rangercaptain:
I'm going to suggest you go to the Roto JME rom thread, and do a complete install using the full rom and the pit file to reparitition your internal memory. It will take only about 5 minutes to do that and should repair any possible damage.
[Galaxy Tab  Android Development] Jeepsdaddy:
I keep freezing up on an ATT Galaxy Tab Running Overcome ...

Anyone have recommendations for VOLTAGE setting using this kernel on an ATT Tab?

Thanks

I don't think it is ATT Compatible
[Galaxy Tab  Android Development] rangercaptain:
I had lots of lag, but not a complete freeze on my at&t tab. I reflashed the mocado rom, and the lags stopped.
[Galaxy Tab  Android Development] -Mr. X-:
I had lag after flashing, clearing the cache from CWM fixed it for me.
[Galaxy Tab  Android Development] ahahha:
thanks all...

i manage to make in flash roto rom and it function again.

let said if i need to flash modacco rom or overcome rom...

is that i am supposed to flash modacco custom kernel EXT4 version with micro sd card insert?
[Galaxy Tab  Android Development] bpt888:
My LCDD is set to 200 and the camera is NOT working as well. Has anyone found a solution for this yet?

I have v13 kernel on MoDaCo R1 ROM on a Bell Galaxy Tab.
[Galaxy Tab  Android Development] rangercaptain:
Yes, you need to have an external sd card inserted to give the rom room to expand files, move your old system, then reformat the internal sd card.
[Galaxy Tab  Android Development] ahahha:
thanks for informing. then is that i am supposed to flash modacco kernel first.follow by modacco rom. then last only update the kernel in this thread
[Galaxy Tab  Android Development] antiochasylum:
I beg to differ. I have the ATT tab and mine works like a champ. No issues, no lag nothing.
[Galaxy Tab  Android Development] rangercaptain:
Be sure to reboot between each install and let the tab run for a few minutes before going on.
[Galaxy Tab  Android Development] bpt888:
Antiochasylum, how did you fix the "camera failed" problem? I've tried changing the LCDD to different values (182, 180, 220, 200 etc.) through build.prop several times already and it's still not working. I have it currently set at 200 which is what I use.

Any suggestions guys of what else I can try? I've got the v13 on MoDaCo R1 rom.

Cheers
[Galaxy Tab  Android Development] chetermaat:
Big Biiig Biiiig problem ?!

After flashing all works just Fine. After a litle while i pluged in to charge. And I got a constant warning charging not possible deu to, to high or low temps of battery.

I left it alone for the night, plugged it in again. And it still warns about the temp, and stops charging.

Its 30% Charged. should I do a bat stat reset. ???
[Galaxy Tab  Android Development] fastcx:
Give wipe batt stat a try, and in the process, wipe cache as well
[Galaxy Tab  Android Development] ahahha:
i faced the same problem with it.

modacco custom rom.

any idea or solution?

thanks
[Galaxy Tab  Android Development] chetermaat:
NO succes!!!

Tried wipa bat stat and cache. Still no succes.

I think it is the sensor problem mentioned.

I can not find a way to ADB push a zImage_eur_2_8 or 2_6_1. this image seems to resolve the sensor issieu.

Does some know what ap (besides google SDK) pushes ADB
[Galaxy Tab  Android Development] chetermaat:
please litle help

please help

!
[Galaxy Tab  Android Development] fastcx:
Why not using adb? I have no idea whether root explorer is safe for this procedure.
[Galaxy Tab  Android Development] -Mr. X-:
I wasn't even aware adb would push and write a zimage....??
[Galaxy Tab  Android Development] richardtrip:
Already limited the cpu-speed to 1Ghz using setcpu or something?
[Galaxy Tab  Android Development] chetermaat:
Solved THO !!!

It was a battery temp sensor bug in a 1,4 ghz kernel.

So I had to re-flash with other firmware.

RESULTING in problem described in this thread.http://xdaforums.com/showthread.php?p=11527212#post11527212

So now MY TAB is dead tho brand new. Or has to go to Samsung i,m afraid of.
[Galaxy Tab  Android Development] rangercaptain:
You use Heimdall to push a zimage.
[Galaxy Tab  Android Development] jayavinash:
can someone teach me how to reset the batt stat and wipe the cache.tq
[Galaxy Tab  Android Development] mobile88:
Just boot into recovery mode - the choices are there for you to select
[Galaxy Tab  Android Development] fastcx:
LOL I thought he was asking about pushing sensor's so file, for kernel, it's either heimdal or odin
[Galaxy Tab  Android Development] fastcx:
I've got confirmation on conservative works better on tab n score higher in quadrant
[Galaxy Tab  Android Development] jayavinash:
my quadrant was 2300 after this update with overcome rom.
[Galaxy Tab  Android Development] Qsilver2001:
Under powersave mode running 1.2 tab becomes retard. Previous running conservation mode, smooth as silk. Still testing out in 1.2, presently running interactive mode.

Have not clock to 1.4 yet.
[Galaxy Tab  Android Development] fastcx:
Powersave mode takes the min clock and stays there, so no matter how much u set for max, it doesnt matters
[Galaxy Tab  Android Development] crazylemon:
last night I turned off my tab with 53% battery remaining. this morning, 8h later, the battery was fully drained! could this issue be kernel related?

this was the first time this happened, after over a week of usage.

I'm using V13 and overcome 1.1.3 rom.
[Galaxy Tab  Android Development] fastcx:
Do you have alarm on? I noticed this issue last week, from juiceplotter, it seems like a straight off to nill after 51% cause it straight away off, no logging info on that past 1 hour time
[Galaxy Tab  Android Development] crazylemon:
no, no alarms.

i did nothing fancy with my tab, just surfing.
[Galaxy Tab  Android Development] fastcx:
hmm weird, i had such issue once, but after play around with uv app, it didnt happens again..
[Galaxy Tab  Android Development] jonidroid:
Heelp i flashed to this and now im stuck at galaxy tab booting screen ??
[Galaxy Tab  Android Development] shmigao:
By any chance do you have a locked bootloader?

If so, look for rotohammer's bootloader patch
[Galaxy Tab  Android Development] -Mr. X-:
Two things i have noticed, Firstly am i the only one who does not have a correct current reading in the voltage adjustment app for 1400mHz? Secondly, has any one else noticed the interactive scheduler keeping the cpu maxed out at its highest clock even when its under little or no load? I have not experienced this with this scheduler on any of my other devices.
[Galaxy Tab  Android Development] richardtrip:
Update:

Version 14:

*Add int voltage UV (thanks to Koxudaxi)

*Add 600Mhz (thanks to Koxudaxi)

Flash with recovery:

http://xda.richardtrip.org/tab/GalaxyTab_1400_MCR_ext_V14.zip
[Galaxy Tab  Android Development] warm.shine:
Excuse me. How can I push sensors.default.so by adb ?

Here is my process :

copy sensors.default.so to adb folder

adb devices

adb shell

su

adb push sensors.default.so /system/lib/hw

I've try all night but adb just say "adb not found"

Is there anything wrong?
[Galaxy Tab  Android Development] fastcx:
Great! Will update in a moment.

UPDATE: Ok, done! 600mhz is in! It's my new 800mhz now :D What's int voltage uv?
[Galaxy Tab  Android Development] lambstone:
Check the directory bible.
[Galaxy Tab  Android Development] warm.shine:
I'm sorry for my stupid problem.

I've try all night to do this but still fail.

So that I ask for help here...
[Galaxy Tab  Android Development] fastcx:
Obviously you need android sdk, or if you do not have it, adb from superoneclick root can be used as well.

Once you have it, run terminal(cmd.exe), go into the directory that contains adb.exe, only then you starts..
[Galaxy Tab  Android Development] GOF007:
Can I just use Root Explorer to copy sensors.default.so to /system/lib/hw ?
[Galaxy Tab  Android Development] warm.shine:
Sorry .

I've download adb by superoneclick root and put it in C:\

and all of the process was on adb

Let me show all of my step by photo
[Galaxy Tab  Android Development] fastcx:
when u r in adb shell, dnt need to put "adb" in the command anymore
[Galaxy Tab  Android Development] fastcx:
Why do that when new v14 is out? and it push the sensor and app thru cwm for you
[Galaxy Tab  Android Development] warm.shine:
Big thanks for your answer .

but it doesn't work
[Galaxy Tab  Android Development] fastcx:
ok, now you nees to remount your /system to read&write,

run "mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system" after you done su in adb shell, after that is done without error code, try pushing again.
[Galaxy Tab  Android Development] warm.shine:
Really preciate for your help !

But...still not working...
[Galaxy Tab  Android Development] -Mr. X-:
That command is not going to work

Command was incorrect use this to remount your system partition

mount -o rw,remount -t ext4 /dev/block/mtdblock4 /system
[Galaxy Tab  Android Development] fastcx:
LOL okok, which kernel are you using now?
[Galaxy Tab  Android Development] fastcx:
LOL thanks for correction :P forgotten we are in ext4 now, not rfs
[Galaxy Tab  Android Development] -Mr. X-:
I'll assume he is using this one since he is in here, which is why your remount command didnt work. infact even if he wasnt using this kernel your remount command stil lwould not work as i do not think samsung devices use yaffs2 they use rfs
[Galaxy Tab  Android Development] warm.shine:
Galaxy Tab 1.4Ghz V14

I've convert to ext4
[Galaxy Tab  Android Development] fastcx:
It did work b4 i converted to ext4 on rfs
[Galaxy Tab  Android Development] fastcx:
y you still wants to push sensor? orientation sensor still not working?
[Galaxy Tab  Android Development] -Mr. X-:
mount -o rw,remount -t ext4 /dev/block/mtdblock4 /system
[Galaxy Tab  Android Development] fastcx:
no, mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system
[Galaxy Tab  Android Development] warm.shine:
The battery sensor is strange.

I cannot charge tab...
[Galaxy Tab  Android Development] -Mr. X-:
dude, seriously.

He is ext4. the correct command is the one i gave him.
[Galaxy Tab  Android Development] fastcx:
dude, i know, i'm telling you yaffs2 is working on stock rfs. and i'm sure he gets your command in previous post, chill
[Galaxy Tab  Android Development] -Mr. X-:
He needs to use my command to push the sensors to his device.

so when i said

mount -o rw,remount -t ext4 /dev/block/mtdblock4 /system

you should not say

"no, mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system"

as he is not running yaffst or rfs he is running ext4 as he stated.
[Galaxy Tab  Android Development] warm.shine:
I've try all the command you two given to me

I'm shame of my stupid and you guys helping me...
[Galaxy Tab  Android Development] fastcx:
dont mind the argument, it's clear that u need to run ext4, ignore the yaffs2 obviously.

Anyway, have you cleared cache? Through cwm
[Galaxy Tab  Android Development] warm.shine:
Sure i did

and I've try clean baterry status , but it seem not work , nothing appearance after I clean baterry status
[Galaxy Tab  Android Development] -Mr. X-:
alright,

do these commands in order

"

adb shell

mount -o rw,remount -t ext4 /dev/block/mtdblock4 /system

exit "

don't put in the quotes

then you are going to want to run this command

adb push /path/to/sensors.default.so /system/lib/hw/sensors.default.so

alternatively there is no harm in using root explorer to copy it over and then rebooting

where "/path/to/sensors.default.so" is the actual path where the file you want to push is.