yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Android Development] pershoot:
i see no panic in your log.

[ 23.637701] Restarting Linux version 2.6.36.4-cyanogenmod+ (root@pershoot-ubuntu) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 SMP PREEMPT Sun Jul 17 11:34:24 EDT 2011

[ 23.637707]

[ 23.657983] VFS: Close: file count is 0

[ 24.042713] Power down.

No errors detected

so from this perspective your good to go (so far).

this is good test though,

flash to 7.16 (re-download it), and set to 1.4. use it for 24 hours as you normally would. if you get no freezes/panics/hard resets, then your device probably can handle it, and i can look to amend/remove some stuff i've introduced in 7.17. if you do, then you're device cannot do 1.4, with the amount of voltage im giving.

at any rate, report back when you can.
[Galaxy Tab 10.1 Android Development] Grommish:
Pershoot

I don't have recovery, just cwm. What's the best way to do wipe like you commend since cwm factory is different? It got the 7510 and it came unlocked

I used nvflash initially
[Galaxy Tab 10.1 Android Development] pershoot:
you do have the stock recovery file. shep included it in his files. i also have the stock IO recovery. its on droidbasement in sys-backup.

if you just want to wipe, enter nvflash, flash the stock recovery, boot it, factory reset, then reboot.

if you will be doing lot of testing, get fastboot on to your device (mashi's thread), then you will have a relatively painless way to test/boot/recover.
[Galaxy Tab 10.1 Android Development] hoodoomagic:
I flashed the 7.16 kernel and got another hard reset at 1.4. Going to clock down to 1.2 for awhile to see how it holds up.
[Galaxy Tab 10.1 Android Development] RustyNailz:
Pershoot,

No, I'm not overclocked at the moment. I just retried this and locked up again. I can send over the log file if you wish.

Thinking of reverting to the stock kernel and perfoming the same test with it.
[Galaxy Tab 10.1 Android Development] pershoot:
yea, your device cant do it. sorry man.
[Galaxy Tab 10.1 Android Development] pershoot:
i am suspecting something else. no way you should be locking up at all. this is more voltage then the stock kernel is providing.

factory reset through the stock recovery (pull your media off if you have any), and then flash 7/17 (re-download it from droidbasement) via CWM. you must factory reset through the stock recovery, to ensure you are at a pristine spot. you could also flash ota_3.1 update.zip prior to flashing kernel, to ensure you are at a bone stock point.

report back in 24 hrs.

be mindful of the apps your installing and using (some of them will indeed crash you on HC).

dont install setcpu. just use it as is.

post a /proc/last_kmsg if it occurs again. without this, i cant do anything.
[Galaxy Tab 10.1 Android Development] pershoot:
I'm going to rework the cpufreq patches and post an update.

I'm speculating some of these odd ended device crashes at 1ghz and below are attributed to it (barring the dirty system scenario).

Ill see if I can get to this tonight.
[Galaxy Tab 10.1 Android Development] RustyNailz:
Unable to reproduce with the stock kernel (although I did get a FC in android.process.media while rotating the screen back and forth).

Flashed back to the 7.16 kernel, unable to reproduce. Flashed the 7.17 kernel, and so far haven't had another lockup. Perhaps reflashing the stock kernel "fixed" whatever was out of whack. <shrug>
[Galaxy Tab 10.1 Android Development] pershoot:
my advice is to purge your 'dirty' system, as outlined.

please do this, to ensure there are no extraneous variables, then report back, and we can work on it some more, in your specific scenario, if not resolved.

this device is quite finnicky (unfortunately). one bad episode of lockups/resets can start a chain reaction which effect the whole system, and remain.

at any rate, let me know if it persists. i can yank/rework the additions in 7.17, if that is posing an issue for you/devices like yours (i cant reproduce on my end).
[Galaxy Tab 10.1 Android Development] GrkEngineer:
After going back to stock recovery and wiping, I'm now doing much better with the latest kernel. Was getting locks at normal speed every 15 minutes of use. Way better now. Just did the steps I mentioned in my previous post. Thanks!!
[Galaxy Tab 10.1 Android Development] pershoot:
Are you pleased with the performance thus far (given the fact that hc is a dog, hehe)?
[Galaxy Tab 10.1 Android Development] GrkEngineer:
doh...

I spoke too soon. Here are my logs from the last two resets. The 99k file is from an auto reboot. The 13k from a freeze which I had to hold the power button for.
[Galaxy Tab 10.1 Android Development] pershoot:
if you are not overclocking, can you reproduce this on 7.16 refresh?

if you are overclocking, clock down and observe.
[Galaxy Tab 10.1 Android Development] GrkEngineer:
No overclocking. I'll load 7/16 refresh now.
[Galaxy Tab 10.1 Android Development] pershoot:
pm me when your done testing 7.16 refresh, and ill send u a test, so it can be fixed up.
[Galaxy Tab 10.1 Android Development] Zoide_:
pershoot: I see that your blog says the kernel isn't compatible with the Touchwiz ROM. However, some people have posted here saying that they've gotten it to work (e.g. http://xdaforums.com/showpost.php?p=15741833&postcount=799).

What are your thoughts on this?

Thanks
[Galaxy Tab 10.1 Android Development] pershoot:
not supported.

however,

you can use this kernel on that rom, if you flash a release before 7/14 (which will replace your ramdisk).

then you can flash from then on in (7/14 and above).

but, please don't report issues regarding that rom, as i can only support the stock rom, atm.
[Galaxy Tab 10.1 Android Development] Zoide_:
Alright, thanks!
[Galaxy Tab 10.1 Android Development] mazlo:
Using the Samsung USB adapter, my Xbox 360 controller and Logitech Gamepad F510 (direct-input) don't seem to be working. I copied ff-memless.ko and xpad.ko to /data/local/modules and I used insmod to load them (with adb shell). I verified both were loaded using lsmod.

The Xbox 360 controller still gives Unknown device when plugged in (same error that the stock kernel gives).

The Logitech gamepad says Usb device connected and dmesg confirms it recognized it, but it doesn't seem to be set up as an input device (or input event). This gamepad also has an x-input mode (emulates Xbox 360 controller), and in this mode it gives the Unknown device error.
[Galaxy Tab 10.1 Android Development] pershoot:
Ill look in to it. Don't have an adapter on hand or an xbox360 controller to test, atm.
[Galaxy Tab 10.1 Android Development] pershoot:
I need to trim, from the barrage of things brought in to this rls, so probly another update in 2 days or so.

Then ill start spacing the releases out to give you all some peace from flashing too much, hehe.

Enjoy!
[Galaxy Tab 10.1 Android Development] SellswordShev:
That merge was massive, good luck :P
[Galaxy Tab 10.1 Android Development] Jnn1:
Thank you!!
[Galaxy Tab 10.1 Android Development] pershoot:
7.19 working out ok?

do you all want me to bring in the voodoo stuff from supercurio? will it be used?
[Galaxy Tab 10.1 Android Development] goldgrillshinin:
I tried his out.. Not sure what the difference to voodoo is making.. Guess I dont know how to test it out..
[Galaxy Tab 10.1 Android Development] SeanHacker:
Voodoo would be awesome bro.
[Galaxy Tab 10.1 Android Development] njfoses:
Voodoo would be cool but uv would be better!
[Galaxy Tab 10.1 Android Development] pershoot:
yea, i would like to uv (as ive done with the other devices i support), but seems as tho samsung really gimped out the cpus in these devices, and there is quite a wide range of variation here (just from this thread), making it difficult to have a common uv structure without breaking compatibility and stability for the masses (from what i can see thus far in this thread).

i'm not keen on giving the user VC controls at this stage. i want total control without any external variables as more and more devices come online, and can predict their behavior, etc.

i'll keep it on the backburner.

battery life is quite good tho, at idle.
[Galaxy Tab 10.1 Android Development] SellswordShev:
I was looking at frequency % used stats (using CPU Spy on the market), noticed that there is a Deep Sleep mode listed under not being used, any idea what that is and does?

Hope samsung has un-gimped the cpu in touchwiz, the unofficial ROM definitely showed better performance at stock.
[Galaxy Tab 10.1 Android Development] pershoot:
its a hardware variation, not software.

deep sleep is one of the sleep/suspend modes (simple suspend being another) on this platform.

it does go in to a 'suspend'/collapse, but it is not as deep as the early tegra2 models (harmony in particular), where nothing (not even wifi) would hold a proper wakelock.
[Galaxy Tab 10.1 Android Development] GrkEngineer:
Perhaps I have a faulty device. Got another bootloop with 7/19. Just curious, is no one else seeing issues anymore? I might need a new tablet.
[Galaxy Tab 10.1 Android Development] pershoot:
as discussed, not anyone ive spoken to can recreate this crash that you are receiving. anything that i saw in your log (with wifi), i patched up, to the best of my knowledge.

i certainly cannot crash it (ive tried very hard), literally hammering it and waking it up repeatedly and letting it sweat, idle/load.

it is not uncommon to have a defective device and/or a device which cannot do 1GHZ (i've seen one or two in my day on the harmony platform). this may be the case.

try this:

set min: 216, max: 912.

now see if you get any crashes.

you may or may not be able to reproduce this on the stock kernel at a rapid pace, due to the governor being used there (you may never hit max at a constant rate (default is conservative, with it being set to interactive later on, and then it idling at conservative again)).
[Galaxy Tab 10.1 Android Development] tiny4579:
I would love voodoo audio. It's the only thing keeping me from switching back your kernel.
[Galaxy Tab 10.1 Android Development] GrkEngineer:
Yea I totally agree. Was just taking a final survey before returning. Beyond the 30 days so will have to get creative.
[Galaxy Tab 10.1 Android Development] pershoot:
try limiting your max as i advised, so you can rule this out.
[Galaxy Tab 10.1 Android Development] pershoot:
yes, i will include it. but it will be a loadable module (if it can support it).
[Galaxy Tab 10.1 Android Development] cyberleader:
replace

This always works. Buy another one return the old one. Make sure they are the same model tho.
[Galaxy Tab 10.1 Android Development] bballer71418:
Can anyone explain what exactly voodoo audio is?
[Galaxy Tab 10.1 Android Development] scmguru:
This current build is really unstable on my unit...random lockups at stock speeds... tried using cwr to delete caches and reinstall and no improvement.. going to roll back to stock and see if it improves.
[Galaxy Tab 10.1 Android Development] pershoot:
you dont use CWM to reset your system.

you use the stock recovery to reset your system.

flash ota 3.1.zip so you can format your system as well.

do all that, and then report back with a log in hand. do not install setcpu at all.

this kernel is flying. you should not be receiving what you are receiving.
[Galaxy Tab 10.1 Android Development] used2hvatreo:
Agreed, I have been rocking and rolling on this for a long time now and it is rock solid.
[Galaxy Tab 10.1 Android Development] rvrugg90:
I'm a little confused as well....

So we cant just boot into clockwork, clear cache, wipe, and wipe dalvik? I thought this was the only way to do it? We do this, then we can mount the tab up to computer...drag over new rom or kernel, then flash in recovery...Correct me if I'm wrong. Just want to make sure I'm also doing this the right way in the future! Thanks!
[Galaxy Tab 10.1 Android Development] pershoot:
you do not do this before flashing a kernel. you can clear dalvik before flashing a rom. you can also factory reset in CWM.

but, should you end up in a bootloop situation (and /data being unable to be written to) and/or some odd behavior with your tab, reset through stock recovery is the way to go, because it does something extra in the step, which is not done in CWM.

factory reset in CWM preserves media. factory reset through the stock reocvery blows media away.
[Galaxy Tab 10.1 Android Development] pershoot:
wait for the next update (coming soon). your particular device should be good to go then.
[Galaxy Tab 10.1 Android Development] pershoot:
this issue is rectified. grkengineer is on 1.4, stable.

this should now cover all the other devices who had issues before. for the other devices who had no perceived issues, you should enjoy some added peppiness.

performance is very good (still a bit more to do tho).

update coming soon.

this will be it for the next few days (need to head to other devices who have been neglected, hehe).

has voodoo in it as well (couldn't modularise it (it's not finished yet), so the image grew a bit).
[Galaxy Tab 10.1 Android Development] pershoot:
galaxy tab 10.1 - 2.6.36.4 - http://droidbasement.com/db-blog - this will be it for the next few days. enjoy!
[Galaxy Tab 10.1 Android Development] GrkEngineer:
steps to reset

Here are the steps I took to reset when hosed up. I have a retail locked bootloader wifi 16gb device.

1. Boot into "download mode" and flash PDA_SIGNED_P7105 using the Odin tool. This alone won't reset stuff sufficiently. You then need to boot into recovery and do a system wipe. This will do the proper CSC magic and /data/media wiping.

2. I then went back into "download mode" and flashed the recovery-cwn_4.0.0.4-sam-tab-10.1.tar.md5 file.

3. I then booted into CW recovery and installed the hc-3.1_ota-full_sam_tab_10.1.zip. According to Pershoot, this will also do a wipe which is needed.

4. While still in CW recovery, I then installed Pershoot's system tools followed by the kernel. (The system tools installs a kernel, so make sure to flash your desired kernel after the tools are installed.)

(One thing to note, if you want to use ClockworkMod from the app, you'll have to reflash CW recovery from within the app.)

Hope this helps. It seemed that some were confused about the reset steps.
[Galaxy Tab 10.1 Android Development] used2hvatreo:
Its awesomeness thanks for all the hard work
[Galaxy Tab 10.1 Android Development] katlimaal:
Can this be flashed on Bonsai ROM.

My device:

Tab 10.1 (P7510) with Bonsai ROM ver 0.20
[Galaxy Tab 10.1 Android Development] pershoot:
yes.

.......
[Galaxy Tab 10.1 Android Development] pershoot:
im curious....

for those that felt they could not do 1.4 prior (that could do 1.2), please try again.
[Galaxy Tab 10.1 Android Development] Muuhmann:
hi pershoot,

quick question: has this kernel the tun/tap module. i'd love to use autoproxy
[Galaxy Tab 10.1 Android Development] pershoot:
yes, its built-in.
[Galaxy Tab 10.1 Android Development] proengin:
Thank you Pershoot!

This latest kernel has been running beautifully at 1.4/1.4Ghz on my I/O Tab - it wasn't even stable at 216/1.4Ghz in previous kernels. Opening and exit from app is a bit faster than before. Scrolling of web page feels smoother and updates of background tiles seem to be faster as well. Continuation of youtube video on web page from sleep seems more spontaneous than before - this may suggest wifi wakes up faster.

All in all, it's a very good and stable kernel.

Once again, thank you Pershoot for the excellent work.
[Galaxy Tab 10.1 Android Development] dwa012:
Love the newest release. I am running at 1.4/1.4 and having no trouble at all. Everything runs and open so much faster. It really puts my father-in-laws iPad2 to shame.

The Voodoo sound sounds fantastic!!!

Thanks for all your hard work.
[Galaxy Tab 10.1 Android Development] pershoot:
there really is no need to run pinned at 1.4. please use min 216. it will scale and respond as required.
[Galaxy Tab 10.1 Android Development] SellswordShev:
Hey have you given any more thought to the interactive governor? I have been using it constantly with the bonsai ROM (~1.5 weeks) and it noticeably outperforms ondemand while maintaining stability @1.4ghz.
[Galaxy Tab 10.1 Android Development] pershoot:
tell me why you think it outperforms ondemand?
[Galaxy Tab 10.1 Android Development] SellswordShev:
I am judging it purely from a usage scenario, I have seen ondemand lag where the interactive kernel doesnt (mostly when coming off sleep / low use states).

I don't rely much on quadrant either, if anything the new Vellamo benchmark does a much better job, though I have not yet compared results for the two governors with that yet.
[Galaxy Tab 10.1 Android Development] pershoot:
i see no lag at all whatsoever from wake (it literally is ready to go at unlock; barring the pigginess of the launcher). no one else has reported this either.

speak with randy. i don't know what is going in that rom if that is ocurring.
[Galaxy Tab 10.1 Android Development] SellswordShev:
okay, Ill try doing a clean install of everything it might be just me. Also, what base ROM do you use ? just the OTA, or the deodexed version by khasmek ?
[Galaxy Tab 10.1 Android Development] pershoot:
OTA

.....
[Galaxy Tab 10.1 Android Development] used2hvatreo:
I have only ever used the OTA, and i have no lag on wakeup, and no lag in the launcher other than just the usual honeycomb business.

Come play and let me know what you think about the kernel/stock combo
[Galaxy Tab 10.1 Android Development] tiny4579:
Correct me if I'm wrong pershoot but what I understand about the ondemand governor is that it should scale up the CPU speed the quickest for the least lag while still allowing the CPU to downclock when the full speed is not needed.

So in ranking it would be.

1. performance - fastest speed but will drain battery much quicker and also could get hot.

2. ondemand - CPU will scale up to top speed quickest but will still go down to the minimum speed as needed.

3. interactive - like ondemand, i believe it's a newer governor and not available in all android kernels by default. I don't know details but I know it works slightly different than the others.

4. conservative - I think it's better for battery life than the others listed as it scales up speed slower so lag might increase. It might be based on ondemand.

5. smartass - based on interactive but with basically a built in sleep profile. I don't think it's been implemented in our source code.

Hopefully this helps. Pershoot, you want to expand on this summary any?
[Galaxy Tab 10.1 Android Development] pershoot:
read this:

http://www.mjmwired.net/kernel/Documentation/cpu-freq/governors.txt
[Galaxy Tab 10.1 Android Development] GrkEngineer:
This one has more info. https://github.com/CyanogenMod/cm-k...60f39120/Documentation/cpu-freq/governors.txt
[Galaxy Tab 10.1 Android Development] tiny4579:
Yes, I think that is the document I saw previously. The first document was about stock Linux and the interactive governor mentioned in the second link describes the interactive governor added by Cyanogenmod. It's an informative read if you like technical docs.
[Galaxy Tab 10.1 Android Development] pershoot:
Everyone rockin and rollin on 0719b?
[Galaxy Tab 10.1 Android Development] dwa012:
Doing well and very stable at 1.4
[Galaxy Tab 10.1 Android Development] njfoses:
Been busy with work but will install tonight.
[Galaxy Tab 10.1 Android Development] njfoses:
pershoot, it seems when your kernel is updated bonsai kernel is updated as well. Is bonsai developing their own kernel or using yours?
[Galaxy Tab 10.1 Android Development] Infobits:
Hi all, I just installed this latest kernal on a Samsung Galaxy Tab 10.1 Retail Locked version. Being this is my first ever venture into Android Tablet (or smartphone) territory, I had to comb through tons of reading and research of everyone's method of how to go about rooting and installing things. I was able to simply just download pershoot's kernal to my tablets /sdcard/ root directory and then go into CWM's flash mode to install zip file from sdcard. Before I did this I used CWM to make a ROM Backup, and I also wiped cache and all that stuff. After flashing the kernal, it booted up and hung at the "Samsung" logo. I waited for awhile to see if it would continue to boot up. It did not. I then powered it off and rebooted again. This time it booted up just fine. But the wipe apparently deleted all my apps icons and settings. sigh! I had to do a google restore to get them all back and reconfigure my apps.

Anyway, just wanted to say so far it seems to be running without a hitch. I did run that auau app performance tester and at default 1000Mhz max CPU clock, the results came in lower than original Samsung kernal at 1000Mhz clock. That's fyi for pershoot.

I then proceeded to set max clock at 1400Mhz and that did increase the performance measurement. So I am happy for that. I have not had a chance to live with it and run it hard for long periods yet to see if it will lock up or not. But it has been on idling and in and out of sleep and wake states all day with no issues at all.

Great job pershoot! I am very glad there are folks like you around to do this sort of stuff~!

I have a question though. Why is the max clock rate only 1.4Ghz for this Samsung 10.1 when I see other branded Tablet PC's with same hardware being OC'ed to like 1.6Ghz? Is 1.4Ghz max clock chosen by you just for stability sake? Have you tried higher clock rates like 1.6Ghz for this Samsung and it fails? I am curious because it seems like the other tablets like my son's ASUS Transformer is faster with OC of 1.6Ghz and stable.
[Galaxy Tab 10.1 Android Development] pershoot:
they are using my source.
[Galaxy Tab 10.1 Android Development] pershoot:
you dont ever have to clear anything before a kernel flash, otherwise you may run in to odd issues, such as what you are describing. just flash.

remember, those are just benches, which mean very little in real-world. the way the governor is setup in this kernel differs then stock. if you want to bench, you should pin min/max.

1.4GHZ is all that i will provide to the masses for public consumption. its not worth it, IMO, in the amount of voltage it takes to provide a stable 1.6GHZ experience. you can't run that 24/7 without taking a penalty on your battery life and possibly the longevity/safety of your hardware.
[Galaxy Tab 10.1 Android Development] njfoses:
Surprised to hear you don't recommend wiping cache and dalvik cache before flashing. From all the kernel threads in the evo section they always recommended wiping both before flashing a kernel. Anyways 7/19 running good so far.

Sent from my rooted galaxy 10.1
[Galaxy Tab 10.1 Android Development] Infobits:
Thanks for the extra guidance pershoot. Much appreciated! I have another question pertaining to the governor stuff. I just read in another forum (Bonzai forums I think) where someone mentioned that you should not run an app like setcpu which itself apparently has its own CPU governing algorithm(s) and so might (and will) clash with the kernal's governing function. Is this true?

Also I think I noticed that even with this 1.4Ghz OC kernel loaded, if I do not have setcpu app to set the clock to max 1.4Ghz, then the Tablet boots up and max speed is default at 1Ghz.

Is there anyway with your kernal to have it switch to 1.4Ghz clock rate without the need for setting it in an app like setcpu? In the other kernal forum I read them say that they have a config file to edit in the desired clock rates. Can we do that with your kernal implementation? Or is it too risky due to tablet might hang at boot screen due to the max OC rate. Can you make it so that it boots at the default 1Ghz clock rate and once booted it automatically sets itself up to max 1.4Ghz clock rate?
[Galaxy Tab 10.1 Android Development] pershoot:
Correct. The kernel is not oc'd by default.

You must set them yourself, either using gscript, setcpu, or echo'ing the value yourself to cpufreq.

You can use init.d, if your ramdisk is setup to handle it. I don't provide the ramdisk in my kernel package.
[Galaxy Tab 10.1 Android Development] torremitsu:
Does this work with Touchwiz?
[Galaxy Tab 10.1 Android Development] pershoot:
Read the blog post. You will find your answer there.