yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Android Development] alexige:
Alright so I'm a bit freaked out today. I've had my tab 4 days and after making a CWM backup from stock, I flashed starburst rom and this kernel the version that was out earlier in the day yesterday not the most recent version. Woke up this morning to my tab saying it had 31% battery, or the amount of battery left when i went to sleep and put in on the charger. The charge symbol was on this morning. So in extreme worry something was already wrong with my charger I factory reset from CWM and fresh installed Starburst and the version of this kernel i had on my card. Everything came back up fine and the battery was at 96%. Charged it up for a little while longer, unplugged and left it at home with 100% battery.

So my question is is this a known issue with the charge indicator being off like that or a fluke?

Got my tab at Best Buy thinking of returning and getting it at Costco so I have to security of the two year warranty cause that REALLY scared me after various issues I've had with my Captivate.

Any opinions?
[Galaxy Tab 10.1 Android Development] pershoot:
you could not have flashed this kernel for touchwiz in a previous version, because it was only released yesterday for the first time.

its plausible that it could get messed up (rarely). i have yet to experience it.

post full logs if you feel it is a recurring issue.
[Galaxy Tab 10.1 Android Development] alexige:
I flashed StarBurst rom then your kernel cause I wanted voodoo sound. I guess I'm not understanding what you are saying.
[Galaxy Tab 10.1 Android Development] pershoot:
you stated you flashed the first but not the refresh. i never released a refresh for the 10.1 wifi ux version. it was only the one, which was yesterday at 2pm.
[Galaxy Tab 10.1 Android Development] alexige:
How do I get logs out? I'm having a ***** of a time getting ADB on my Win 7 64-bit laptop. If it happends again I'll let you know though.
[Galaxy Tab 10.1 Android Development] alexige:
That was the one I flashed. On a bit of a learning curve here what do you mean refresh?
[Galaxy Tab 10.1 Android Development] pershoot:
osmonitor, dmesg, during the event.
[Galaxy Tab 10.1 Android Development] pershoot:
here is the terminology/flow:

when i 'refresh' something, it is usually an update to the already existing file released. the filename will not change.

when i 'update' or add content to a post, i will change the times of this post, which may not necessarily reflect the initial posting times and initial content.
[Galaxy Tab 10.1 Android Development] Croak:
This. This is why I greatly dislike the trend for almost exclusive CWM usage on this device. :)
[Galaxy Tab 10.1 Android Development] Grommish:
Yah.. I was getting a ums lunfile error when trying to do a usb mount in cwm.. since I cat just pull the card, it drove me nuts.

I also am not a huge fan of the gtab10.1 forum organization. Everyone uses different terms for everything, usually the same thing, in their posts.

Bound to happen I guess, and will correct itself over time. But damn, it makes finding things a bear!
[Galaxy Tab 10.1 Android Development] sixstringsg:
You can unzip the file, and push the kernel with heimdall.
[Galaxy Tab 10.1 Android Development] Entropy512:
What version of heimdall are you using, and what OS? Heimdall consistently fails for me with the Tab 10.1 (Will post the error in a few minutes...). Kinda is frustrating since I use it all the time on my Infuse.

Also, pershoot - On a regular basis I get merge conflicts for files I've never touched when pulling from your repo. I've never had this happen with any other github repo. Are you by any chance rebasing stuff that you've already pushed and force-pushing it?

Heimdall v1.3 (beta), Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG Corp."
Product: "SEC Device"
Serial No: "?"

length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 0100
iMan:iProd:iSer: 1:2:0
nb confs: 1

interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 82
max packet size: 0010
polling interval: 09

interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...

Beginning session...
ERROR: Failed to begin session!
Re-attaching kernel driver...
[Galaxy Tab 10.1 Android Development] sixstringsg:
To be honest, I've never done it on my tab. Just my captivate on CM7.
[Galaxy Tab 10.1 Android Development] RustyNailz:
fwiw, I've seen this also. Actually had the system reboot on me the first time I turned it off after bumping to 1.4 with setcpu. Its been ok since then. I can post the log if desired.
[Galaxy Tab 10.1 Android Development] pershoot:
I rewrite history at times. This is why you are getting conflicts.

Rebase or pull with merge strategy theirs (depending on what you are doing).

Do not push the ux kernel like that without the appropriate init rc change. Failing to do so will cause immediate lockups/bootloops. If you are using a ramdisk forged from one of my ux zips which is on your system already, then your good to go, to do that approach.
[Galaxy Tab 10.1 Android Development] pershoot:
Lower your clock. That's an instability on your specific device when working with that frequency, most likely.

I get no bad behavior at all at 1.4. Which deems my specific device stable, for all intents and purposes, when using that paricular freq. Not every device will be like mine. Listen to your device and build. Don't push it if it doesn't want to go.
[Galaxy Tab 10.1 Android Development] FillTheVoid:
It seems like its charging quite slowly when plugged into outlet. I'm not sure if this is touchwiz or the kernel. I have it clocked to normal 1Ghz when charging via setcpu. Will clear battery stats and report back tmrw.
[Galaxy Tab 10.1 Android Development] K Rich:
everything seems stable at 1.4, we'll see how it holds up over the next few days.

went from 2250 to 3050 in quadrant.
[Galaxy Tab 10.1 Android Development] K Rich:
this may be a stupid question...but what is different between the newest one "080911"

abd "080711"?
[Galaxy Tab 10.1 Android Development] pershoot:
All changelogs are posted on the actual blog post.
[Galaxy Tab 10.1 Android Development] rs125:
This is a new kernel?you fix battery drain?

Your kernel work on my ROM (http://xdaforums.com/showthread.php?t=1200985) and on my porting from p7510, Thanks :)
[Galaxy Tab 10.1 Android Development] pershoot:
im seeing none of that. i lost 2% in 8 hours idle.

flash the latest kernel and mind your BG processes. post full logs if it is an issue.
[Galaxy Tab 10.1 Android Development] EvoXOhio:
Does the new version attempt to fix the static garbage at bootup on touchwiz rims?
[Galaxy Tab 10.1 Android Development] pershoot:
this has nothing to do with this kernel.

cleanse yourself out.

not seeing that at all.

your fix for that has been widely publicised.
[Galaxy Tab 10.1 Android Development] EvoXOhio:
If I flash your kernel I get the issue. If I flash the stock kernel back the issue goes away. I have done that 3 times now and it does the same thing every time. I'd say it is the kernel.

If restoring the stock kernel didn't fix the issue then I would agree with you.
[Galaxy Tab 10.1 Android Development] pershoot:
you need to clear yourself out with the stock recovery via CSC reset, etc.

that is not the fix by just flashing the stock kernel. the stock kernel is widely different then this one. whatever they have in there is not furnished to me. i can't duplicate 100% what all they have in there for these lil wierd tidbits.
[Galaxy Tab 10.1 Android Development] pershoot:
rs,

will roll back in the change i removed for this platform, for your device only. seems as though you all need it.

ill refresh it later today for your device only.
[Galaxy Tab 10.1 Android Development] SellswordShev:
stock recovery reset fixed static screen bug for me, steps I did:

ODIN stock recovery > factory reset (beware this wipes /sdcard) > flash CWM > flash Doc's Slim v6.5 > flash this kernel.
[Galaxy Tab 10.1 Android Development] Grommish:
someone reported removing a .bonsai file on the sdcard fixed the issue after they moved away from it
[Galaxy Tab 10.1 Android Development] pershoot:
for wifi users-

how is 0809?
[Galaxy Tab 10.1 Android Development] K Rich:
Using it today, evertythink seems well. I haven't run into any issues yet on OTA Touchwiz.
[Galaxy Tab 10.1 Android Development] sic_lic1o1:
Is both of the files the same size? I noticed the kernel for the touchwiz has the same file size like the kernel for hc 3.1 (3.46m). And the file names are the same too. Just making sure if im downloading the right kernel. Dont want to make the wrong mistake i made before. Thanks

The touchwiz file name is boot-cm_2636.zip

And the other has the same file name and size too
[Galaxy Tab 10.1 Android Development] Silenus21:
Touchwiz is the UX file.

Guys I already flashed Starburst on my Galaxy Tab 10.1.

I'm going to follow the guide to flash this kernel.

CWM recovery, navigate to either update/instal zip from SDcard.

I already bought SetCpu.

Is there anything else I have to do to flash this kernel.

Would like to hear from people with Starburst on how they installed this.

There are always two files.

boot-cm_2636.4_ux-oc-xtra-vfpv3-d16_fp-080911.zip:

lib-2636.4.tar.gz

Which one should I flash and how.

Thanks.
[Galaxy Tab 10.1 Android Development] pershoot:
Read the blog post carefully, and your answers will be there.
[Galaxy Tab 10.1 Android Development] drae52:
Reading the posts in both threads will tell you what you want to know.

I installed Starburst, then pershoots kernel from CWM; using the .zips.

Easy as pie once you have CWM.
[Galaxy Tab 10.1 Android Development] Vlad_z:
Running 0809 just fine at 1.2Ghz... my Tegra2 is unstable at 1.4. Quadrant score is in 2750ish.
[Galaxy Tab 10.1 Android Development] nakedninja42:
So my issue is not kernel related, samsung determined something is wrong with my battery and now I am in RMA land :(
[Galaxy Tab 10.1 Android Development] WobbleTheHutt:
I want to confirm this solved my static issue, however once you have CWM back on your galaxy tab 10.1 you cant mount as USB and the SD card is wiped clean, so you must use ADB to push your zip files should be somthing like "adb push file.zip /sdcard/file.zip" with out quotes (this is assuming your files are in the same root directory as ADB)
[Galaxy Tab 10.1 Android Development] Silenus21:
Finally flashed this kernel.

2700+ on Quadrant.

Thanks a lot Pershoot.
[Galaxy Tab 10.1 Android Development] K Rich:
Does anyone have setcou to "set on boot" with any issues?
[Galaxy Tab 10.1 Android Development] Grommish:
Set to 1400 on boot, no issues. 2950 quadrant, 5700 on antutu
[Galaxy Tab 10.1 Android Development] K Rich:
Sweet, I haven't had any problems with the kernal thus far, rocks quadrant!!
[Galaxy Tab 10.1 Android Development] wavrunrx:
set to 1400 performance.

great performance.

battery life not so good... :/

cant have everything. :cool:
[Galaxy Tab 10.1 Android Development] pershoot:
U realise what performance is right?

Leave it to ondemand and that wont happen.

Clock down to save juice when u need it.
[Galaxy Tab 10.1 Android Development] gordec:
Installation

Two quick questions for first time kernel flasher.

1. If I flash a ROM with the Kernel, should I boot up into the ROM once then go back to CWM to flash the kernel or is it ok to flash both at one time? If you need to flash the kernel after first boot, should I wipe cache before flashing kernel?

2. Any advantage to flash the different modules? I have never done this before for my phone or tablet. If it's complete optional, I may just flash kernel, overclock and see how it goes.

Thx
[Galaxy Tab 10.1 Android Development] sixstringsg:
1. I've always flashed both without a boot in between.

2. It just depends on if you want what the modules give you. It isn't necessary for the kernel to run, no.
[Galaxy Tab 10.1 Android Development] funky81:
Somehow I've got this battery drain bugs

I dont know which to stop it because I've already reflash my rom back to stock rom many times but still doesnt resolve it.

Anyone know how to stop this?

It's very ignoring, because from start you've got 70% then suddenly drop to 50% then I reboot it and back to 70%
[Galaxy Tab 10.1 Android Development] fransarj:
If possible, can you post a changelog in layman's terms? Because I believe that a lot of us here don't really understand all the technical terms you post in your blog. :) Just a suggestion though. That way, it could also help us discern whether the update is applicable to us or important enough to flash. At the same time, we can better monitor the benefits of the updates that you bring to us, and report bugs at the same time. :)
[Galaxy Tab 10.1 Android Development] texasredrider:
Ok my battey drain is being caused by kernel. On stock everything battery drain is normal. With this kernal i swear i can watch the percentage drop. Like now it dropped 2 percent in the time it took to type this. Doh! 3 now....i bet i will only get 4 hours tops on a full battery on sleep. Dunno what happened. Been using pershoots kernels since day 1. UX doing this? Must do more tests.........
[Galaxy Tab 10.1 Android Development] pershoot:
flash 0809 for wifi.

flash 0807 for p7500/10.1v

there is absolutely no drain whatsoever on my wifi device. its 2% drop in 8 hours.

calibrate your battery properly on the stock kernel prior to flashing upwards.
[Galaxy Tab 10.1 Android Development] Vlad_z:
Last day I flashed latest kernel 0809, rebooted and worked all day for a total run time 9:40. It includes couple movies through WiFi, lots of web, no games... When tab finally hit 1% of charge I put it on charger overnight.

This morning in first 15 min. of web browsing tablet lost 30% of charge. I did reboot it, charge jumps up to 90% but then again goes down very quickly.

I checked top processes and there was nothing unusual consuming CPU on background (3-2% CPU utilization total).

The same time back of the tablet becomes pretty warm. I've turned down WiFi, drainage did not slowed down even when tablet was idle. Brightness was set on manual 10%.

I'll try to flash previous kernel and report back.
[Galaxy Tab 10.1 Android Development] pershoot:
something is running wild.

aren't you on a wifi device? 0809 should work just fine (i yanked the suspected change which was causing the charging issue). post logs if you still have an issue (dmesg).
[Galaxy Tab 10.1 Android Development] pershoot:
im going to rework this source when i get some downtime.

ill pm a few of you tests when i can do that.
[Galaxy Tab 10.1 Android Development] Vlad_z:
Ok, here we go with my dmesg log...
[Galaxy Tab 10.1 Android Development] pershoot:
its mediaserver. i see it constantly trying to free unpinned handles.

you sure you dont have this running in the background?
[Galaxy Tab 10.1 Android Development] Vlad_z:
I have used Advanced Task Killer to send kill signal to BG processes and sometime it's not enough so I go to Application menu and FC some running from there.

I saw no media server here, do you want me to go to terminal and kill it from there?
[Galaxy Tab 10.1 Android Development] pershoot:
dont use that app. this is not the way to do it on gb+.

use settings -> applications to kill stuff. force stop.
[Galaxy Tab 10.1 Android Development] Vlad_z:
I did not find MediaServer in setting -> applications list but force stop anything related to media, like video player, music, etc.

Let see how it goes...
[Galaxy Tab 10.1 Android Development] pershoot:
yes its related to media. its the media subsystem.
[Galaxy Tab 10.1 Android Development] Vlad_z:
Btw, mediaserver process is not apk... it comes from /system/bin/mediaserver

I saw it on previous versions as well and wondering what is the purpose of that daemon?
[Galaxy Tab 10.1 Android Development] pershoot:
i gather to facilitate the execution of the subsystem.
[Galaxy Tab 10.1 Android Development] Vlad_z:
It must be important daemon with parent PID 0...

I'm not sure if killing it from terminal will do us any good, but I can try it for a test if you want me to...
[Galaxy Tab 10.1 Android Development] Vlad_z:
Ok, I'll report in 15 min. how discharge goes.
[Galaxy Tab 10.1 Android Development] pershoot:
ill see if i can scan out any other mediaserver patches in-kernel to tame it.
[Galaxy Tab 10.1 Android Development] pershoot:
this kernel is a lot of work. i've basically put the other devices i support on hold.

UX brought the beast out of this device. i myself may also have gone overzealous with the patches, which work fine on one rom base, but not the next.

it shouldn't be like this really (not to this extent).

sigh. i try my best for you all.
[Galaxy Tab 10.1 Android Development] Vlad_z:
discharge rate stays the same...

I'll flash 0807 then recharge/reset it and will try again.

PS: thanks pershoot for your work, I feel your pain... yup, android might be messy OS.
[Galaxy Tab 10.1 Android Development] pershoot:
ok report back on 0807.

funny i can reproduce none of this.
[Galaxy Tab 10.1 Android Development] pershoot:
as i rework the src, i will need to work with few testers as i gut and make my way through it.

if you are interested, pls pm me, and we'll link up on gtalk.
[Galaxy Tab 10.1 Android Development] Vlad_z:
pm sent...
[Galaxy Tab 10.1 Android Development] texasredrider:
Hmm this I did not do. So I will flash back to stock 3.0, let it OTA update to 3.1, let it OTA google video, charge fully, CWM reset battery stats, unplug then use till shutdown, recharge, flash touchwiz rom (ota doesnt work) then flash kernel.

Should I then repeat battery calibration process?

Or am I totally off?
[Galaxy Tab 10.1 Android Development] pershoot:
no need to OTA.

there are CWM images for everything.

http://droidbasement.com/galaxy/sys-backup

http://droidbasement.com/galaxy/touchwiz-ux

hard reset through the stock recovery for 3.1. backup your media first (/data/media).
[Galaxy Tab 10.1 Android Development] pershoot:
any 10.1 wifi/10.1v/P7500 folks awake, that want to help test, that did receive this battery drain/battery charge issue?

i need stock 3.1 rom testers (10.1 wifi) also (would save me time; then i'd have to switch back/forth on my device).

i've started the process of deconstruction/reconstruction.

lemme know.
[Galaxy Tab 10.1 Android Development] funky81:
You can buzz me on gtalk now..
[Galaxy Tab 10.1 Android Development] dseo80:
This happened to me with the 0807 version of pershoots kernel (10.1-Wifi, Touchwiz UX (OTA, GT-P7510)) on docrambones barebones rom.

it seems the battery calibration becomes severely messed up - for example my tab would get down to 0% and shut itself down. BUT i was able to stay in recovery console for ~5 hours longer (to discharge the battery to 0 on purpose).

meanwhile i upgraded to 0809 (while still having the above issue) and it seems to have persisted.

I have managed to finally drain the battery to 0, and booted into CWM (with charger in) to delete batterystats.

I have turned on device, and started charging (android is on, battery correclt showed 0%, now 5% - have been charging for about an hour)

ill try to charge it up to 100% overnight here (korea gmt+9) then see how it works.

From the size of the battery i think a general rule of thumb is

screen on time should be 8~10 hours (or 10%-15% battery used per "screen on" hour)

and standby should be from 100-200 hours (or an idle drain of ~0.5-1% an hour)

regarding media server issue (i got alot of cpu usage ~23% shown using "top" for android.process.media when i froze drmprovider.apk along with some other apks, once i restored it it seemed to go away.)

regardless.. thank you pershoot for investing your time and abilities into a great kernel for our tabs.

update: tab is charging.. slowwwwly.. charged for 6 hours (is now @40%)
[Galaxy Tab 10.1 Android Development] funky81:
I've test his basic kernel and its workin fine (from samsung opensource + ux patch)

Hopefully after he awake,he will fixed these problems for us.
[Galaxy Tab 10.1 Android Development] gordec:
Anyone feels overclocking the tablet may lower life span? For pc it heats up the cpu more so you just have to get a good fan. But in tablets there are no fans. I'm not sure if tablet manufacturers design big enough heat sinks to tolerate higher speeds.

I am using pershoot latest oc to 1.4gh.
[Galaxy Tab 10.1 Android Development] sixstringsg:
I've run my phone at a %60 overclock (up to 1.6ghz) on a day to day basis for a year and a half if that helps any. In general, it doesn't heat up terribly.
[Galaxy Tab 10.1 Android Development] Kayak83:
Tegra OC'ing hasn't been as successful as other phone's. But, in general, it's been pretty stable up to 1.6Ghz. I run at 1.2-1.4 with no major hit to battery life. Heat hasn't been an issue either. Kinda depends on how well built/layed out the device is. My OG Droid used to get pretty warm at the highest setting and a lot of use. But that's expected from the older stuff.
[Galaxy Tab 10.1 Android Development] rodrigos122:
Are NTFS flash drives supposed to work with this kernel?
[Galaxy Tab 10.1 Android Development] Vlad_z:
you will need ntfs.ko module loaded in order it to work:

insmod /pathwheremoduleis/ntfs.ko

check if it's up and running:

lstmod

then mount your drive to a mount point

mount -o mask=000 -t ntfs /yourblockdevice_i_don'tremember_now /mnt/usbDrive

something like that.
[Galaxy Tab 10.1 Android Development] paratox:
i read p7500 in some posts of this thread, does any pershoot kernel work with the 3g gtabs? would be nice to try one!
[Galaxy Tab 10.1 Android Development] RMXO:
Is there an app that will do this for you automatically. the laziness in me would donate beers if someone could make one & continuously update it.
[Galaxy Tab 10.1 Android Development] Vlad_z:
I only did it once in terminal when checked out if it works, then put all scripts into gscript progy and execute it from it.
[Galaxy Tab 10.1 Android Development] qubanaso:
Does this run for the 4g lte verizon version?
[Galaxy Tab 10.1 Android Development] funky81:
yup, pershoot still workin on it.
[Galaxy Tab 10.1 Android Development] texasredrider:
Im still getting the battery drain issue. Has anyone been able to pinpoint what it is and why its only affecting some machines?
[Galaxy Tab 10.1 Android Development] pershoot:
Calibrate your battery properly, and it will cease.
[Galaxy Tab 10.1 Android Development] Croak:
Media Transport Protocol, perhaps?
[Galaxy Tab 10.1 Android Development] Live2Follow:
I have calibrated it the same way I calibrate my phone. Charge to full wipe battery stats or charge to full while off and then flash.

I do not have a battery drain issue, but a battery reporting issue.

Is there something that I am doing wrong in calibrating? I even wiped with stock recovery before installing again.

Cheers to the good work in any case.!
[Galaxy Tab 10.1 Android Development] SellswordShev:
dont wipe your data after you have calibrated the battery, your stats are stored in /data/system/batterystats.bin. I think best bet for a clean start is: flash 3.1 OTA with CWM, ODIN stock recovery, factory reset with stock recovery, flash CWM, wipe /data , flash the base ROM you want to use (anything with a STOCK kernel, eg. OTA 3.1 or OTA touchwiz), calibrate by draining battery + full recharge, backup with nandroid. Now you should have a properly calibrated battery for your current base ROM.
[Galaxy Tab 10.1 Android Development] Live2Follow:
Okay. Thanks for the response! It's strange i've been flashing non-stop since getting this thing, but only recently have I borked the battery stats :-P I never really thought it was pershoot at all. I know I was just missing a step, which is the case most of the time when someone complains here.