yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 8.9 Android Development] nirogu325:
Hey motley, I moved back to Overcome 1.2 with your kernel for it. Zero issues (no distortions). I assume there's an issue with the Samsung's leaked KJ4. Here's hoping Sammy finishes its homework before year's end.
[Galaxy Tab 8.9 Android Development] _motley:
Cool, good to hear! I saved the logs in case we deal with this issue again. It's very strange you were seeing it, but I had no other reports of it. Did you buy your tab in the US? Touchwiz is pretty cool, but it opens up a lot of complexities. The kernel even has special mods to support Touchwiz video processing versus normal Android functionality. Seems a little over the top to me. I have added a kernel config option (thanks pershoot!) to flip this functionality on and off so we can compile for a non-Touchwiz environment once someone has a ROM without it.
[Galaxy Tab 8.9 Android Development] nirogu325:
Yes, at a Best Buy. I really hope we see further progress once we get ICS in some form or another. This Tab has a lot of potential. Yeah, I agree it was a weird issue (one that popped up in a Vibrant kernel once but was later solved -ah, old days-). Let's see what Sammy does with ICS in 2012.
[Galaxy Tab 8.9 Android Development] Hurrian:
I meant the kernel patches, as done by Sammy and Nvidia. Doing this should make it easier for kernel devs who may want to port newer kernels (e.g. for ICS) onto the Tab 8.9. As I understand it, the tarball from opensource.samsung.com is a pre-patched tarball (without files such as (example) 0000-Board-Support-Samsung.patch)?

EDIT: Oh, Touchwiz is patched into the kernel. That's freaky stuff right there, not used to that in regular GNU/Linux. No wonder the Xoom's SystemUI simply FC'd when I pushed it to the device.
[Galaxy Tab 8.9 Android Development] _motley:
If you need a kernel zImage and modules built with the Touchwiz parts taken out, I can provide that for you so you can try to boot some non-touchwiz ROMs. I have followed pershoot's lead in the 10.1 kernel by adding this kernel config option (touchwiz or not). I have not merged this patch out to my public git yet since I haven't released anything to the public built from this source.

Yes, it is pretty messed up. Samsung's source is not a perfect match with Nvidia's and they don't give your their git repo so you can track it back to the source tree. The kernel source has been customized by Samsung to the extent that the many of .patch diffs from Nvidia's git repo can't automatically be applied in all cases. They can however be easily be identified and merged my hand if the automatic merge won't work. I have found that many of the Nvidia patchs have been merged in by Samsung from 3.1 to 3.2. I use many different tools so I can compare and merge code when necessary.

To make it worse, we as custom kernel developers change several of the source files to add overclocking, voltage control, and other enhancements. This further fragments the source between Samsung, Nvidia and the custom kernel source. All the patches that are applied to the original source from Samsung can easily be tracked moving forward, but every kernel tree out there can't share patches in a perfectly seamless manner... there's a lot of fragmentation going out there in the kernel world by the time your get the code from the manufacturers.
[Galaxy Tab 8.9 Android Development] Hurrian:
Perhaps this would work out better:

[BUILD SYSTEM]

<Start> -> {Vanilla 2.6.36} -> [Patch to 2.6.36.4] -> [Patch in Nvidia Tegra 2 Board Support] -> {Linux 2.6.36.4-Tegra2} -> [Patch in Samsung Device Support] -> {Linux 2.6.36.4-Tab89} -> [Patch in Custom ROM Changes e.g. 0000-Prereq-for-overclock.patch then 0001-Overclock-T2.patch] -> {Linux 2.6.36.4-Tab89-motley}

Of course, the above build system will need you to extensively diff everything, and use an entirely new build system. But the end result is, people will be dealing with single patches instead of the entire source tree, then selecting different versions of the patch from git.
[Galaxy Tab 8.9 Android Development] konceptz:
I noticed the same thing, after installing overcome 2.1 its back to being amazingly fast.
[Galaxy Tab 8.9 Android Development] jamesfx01:
Yo ! I'm running on 7300, installed with:

ROM: Overcome 2.1

OC @ 1.5 Ghz

Problems: None, No issues with WIFI either.

Result: My tab is flying !!

Thank you motley! And the rest of the 7300 users. :):)

P.S. Let me know if you require any logs or anything. :)
[Galaxy Tab 8.9 Android Development] termleech:
Anyone want to share their uv settings? I know its different for each device but I'm looking for a starting point.
[Galaxy Tab 8.9 Android Development] bdfull3r:
for undervoltage i am iam -50 across the the board except for the lowest settings. Very stable. For what i do.
[Galaxy Tab 8.9 Android Development] _motley:
Glad to hear everything is working well, thanks for the feedback!
[Galaxy Tab 8.9 Android Development] _motley:
New version 2b released

New version 2b for HC 3.2 has been released (see OP). Added USB charging support and some performance enhancements. It is working great for me on rooted stock 3.2 and should work great on Overcome 2.x. Let me know how it goes!
[Galaxy Tab 8.9 Android Development] darthvonodia:
Hi,

How is the battery life after OC, what is the perfect UV setting?
[Galaxy Tab 8.9 Android Development] netxph:
because of the battery charging feature... I installed this again... :)

Working great... no more X in my battery icon.
[Galaxy Tab 8.9 Android Development] franksud:
Great news!

What differences have you noticed the battery life with OC? tahnks!
[Galaxy Tab 8.9 Android Development] questionmark:
Hi

Advanced routing feature seems to be missing from the kernel and for what I recall overcome kernel has it enabled when I first installed it. I might be wrong but this is what the app reports.

I use vpnc widget to connect easily to my fritzbox and this all works fine since tune is enabled in the kernel. It is only the check prerequisite that complains about this though does not prevent to connect so no big deal.

Thanks again for all the work.
[Galaxy Tab 8.9 Android Development] _motley:
Thanks for the feedback. The kernel option CONFIG_IP_ADVANCED_ROUTER is only turned on for the 3G 7300 kernel currently (mirrors stock config), but I will add it for the WiFi 7310 kernel as well to give better support for Cisco VPN. I did some quick research and found that, "if the advanced routing kernel feature isn't available, the VPN connection is lost if the WiFi hotspot has a short dhcp lease time and the DHCP-Client renew" (PC World). So, this should make your connection more stable in these circumstances.

If anyone else is having any type of VPN issues, please let me know ASAP and I will try to correct in the next release.
[Galaxy Tab 8.9 Android Development] fishton:
Thanks for the update mate !

Using -50mV everywhere as proposed earlier and everything runs smoothly :)

Really good job !
[Galaxy Tab 8.9 Android Development] _motley:
Glad to hear, thanks again for being one of the early 7300 3G adopters;)
[Galaxy Tab 8.9 Android Development] questionmark:
Thanks for the feed Bak!!??? :)

No... Let me thank you for your work and this is time for me to give back with a little donation, I assume papal is OK and somewhere there is the info if not please PM me your papal or point me to the details of donating.

Same for overcome... I thank up both... Always wonder how you people can find time in all this
[Galaxy Tab 8.9 Android Development] ZeroPDA:
I am trying your kernel. After installing it seemed me a little bit sluggish. I use the newest version Overcome on SGT 7300 (3G). After switching in SetCPU from "ondemand" to "interactive". It seems, everything starting to work great.
[Galaxy Tab 8.9 Android Development] jamesfx01:
-----------------------------------------------------

| OC Frequency | Temperature | Battery |

-----------------------------------------------------

| 1.5Ghz | 38.0 - 43.8 | 6-8Hrs (ebook, surfing, trading, music)

-----------------------------------------------------

| 1.4Ghz | 30.0 - 39.0 | 8-10Hrs(ebook, surfing, trading, music)

-----------------------------------------------------

Battery life is way better before i OC/UV. Could also be the fact that, i have a profile in setCPU which sets the frequency to the slowest when screen's turned off.

My personal experience is that i noticed a quick rise in temperature to about 43.8 or more when i'm doing multi-tasking, when on 1.5Ghz. Seems pretty fine on 1.4 though, highest was about 40.

Experimenting on UV though, -50 seems fine so far.

Hope this helps. :):)
[Galaxy Tab 8.9 Android Development] _motley:
Thanks for the kind words. I have sent you a PM with a build that enables advanced routing.

I have also reluctantly enabled my donations button and will give it a try as several folks have asked about it. I definitely don't expect anything in return as I do this for fun and to learn. I do get grief for spending long hours at the PC from my family at times, so I do appreciate the kind gesture!
[Galaxy Tab 8.9 Android Development] Stevennnn:
Im on Overcome 2.1 with the latest release of your kernel, and the tab is flying!

Thanks!
[Galaxy Tab 8.9 Android Development] rosdol:
Hi, I use the Overcome 2.1.1 with the latest motley 2b_3g kernel. Everything is fine except is does not turn from landscape into portrait and back. The screen always stays in landscape.

Am I doing anything wrong ??

Have restored the boot.img and rotating screen is back!

Any idea ?? :confused:

Erik
[Galaxy Tab 8.9 Android Development] Crashdown12:
Hmm UV does't working? I'm using Setcpu and i change voltage setting -150 mV on every frequenci and -275 on 1400 Mhz and everything working, no freeze in stress test
[Galaxy Tab 8.9 Android Development] _motley:
I haven't seen this before. In System\Tools, perhaps try doing a horizontal calibration and let me know if it helps. Also, please make sure you didn't have the rotation lock on...sorry,but I had to ask the obvious question too just in case ;)

First, to ask the obvious (don't mean to insult)...after hitting "Save" for a given frequency UV setting, are you then pressing "Apply" at the top to commit the changes?

If that doesn't clear it up, please let me know the following:

Version of the kernel you are using

3G or WiFI

ROM you are using

There are some nominal voltage requirement checks as well as some other rules core vs rail V etc. At some point, it may not honor your changes, but something doesn't sound right. After I know a little more and if you still have a problem, we can use some echo commands against the /sys/devices/system/cpu tree to figure out if SetCPU is actually doing what we think it is.
[Galaxy Tab 8.9 Android Development] Crashdown12:
Rom Overcome 8.9 Series v2.1.1 and v2b (7310 WiFi) kernel..

and yes, i hit save and apply (Set on Boot) restart, -200 MV are saved but i think that nothing change
[Galaxy Tab 8.9 Android Development] _motley:
Thanks for the info Crashdown12. I am back home now and after testing I can confirm that v1i works, but v2a has an issue honoring and subtracting the UV values even though they are set properly in sysfs. I have identified and fixed the issue and will provide an update after doing some testing.

Edit: new version 2c has been posted with a fix. Please read the note in bold for 2c before installing. The Wifi version also gets a new feature (thanks questionmark!).
[Galaxy Tab 8.9 Android Development] ZeroPDA:
Does your wonderful kernel fully support LUKS? It requires

When I try to create volume with FAT32 File System it says:

Interestingly, that I don't have this error on Samsung Galaxy S2. I am not sure where the problem is: Kernel, Overcome firmware or LUKS Manager itself.
[Galaxy Tab 8.9 Android Development] dedalos1:
Is possible that the "b" version of your kernel is too fast then "c" version with overcome 2.1.1? How I can do to go faster?
[Galaxy Tab 8.9 Android Development] ZeroPDA:
It is highly unlikely. This version also seemed me slower (switching desktops with twitching), but after second reboot it started to work as fast as it was before.
[Galaxy Tab 8.9 Android Development] bdfull3r:
That donate button was too tempting for me. The effort in the kernal and the much more usfulness i got out of my tablet was worth it. Sorry i don't have much to give
[Galaxy Tab 8.9 Android Development] _motley:
Hi, the kernel does support CONFIG_DM_CRYPT. It can support loop devices with CONFIG_BLK_DEV_LOOP, but I noticed that CONFIG_BLK_DEV_CRYPTOLOOP is not currently supported (not sure if this matters or not, but we could enable this in the next build of the kernel to try it out).

I have not used this app before, so I was not sure what to expect. I just installed it to check it out. Here is my experience so far:

The first time I ran the app and tried to create a FAT volume, I received the same error you did.

I went into LUKS Prefs and turned on "enabled extended debug"

I went to create the same exact name FAT volume again, but this time it worked. So much for needing to debug!

I browsed with ES file explorer to \sdcard\test where my volume"test" was mounted and I could go into the folder, but I couldn't create or paste anything into it.

I then used root explorer and was able to create a folder inside called "test" and then copy in a JPG file. However, with root explorer, i can't view the JPG I put in there. It launced the available apps list, but when I select Gallery or any application, I get the "item not found" error. Seems like decryption is not working or something...

I mounted an ext2 volume next in LUKS Manager. Then I could also see and browse the files in ES File Explorer, but I could not view them using either Root Explorer or ES File Explorer. Still got the same errors trying to view the JPG.

I can only browse the files on the ext2 volume using the LUKS explorer. I can see the JPG file, but I can view it from there either.

Let me know what you think. A lot of weirdness going on!
[Galaxy Tab 8.9 Android Development] _motley:
Thanks, I appreciate it! If we all work together, we'll keep making it even better:)
[Galaxy Tab 8.9 Android Development] _motley:
It is kind of finicky sometimes until you get it set right and sometimes after a new version is installed it will get finicky. After you get it set right, then stays put on reboot and you should have any issues from there. I am still wondering if there isn't something I can do about it to force it honor any changes SetCPU requests to sysfs no matter what. This is the reason why I eventually set the default governor to On Demand and then suggest that you configure it to be Interactive in SetCPU (the recommended governor). This seemed to help trigger the proper acceptance from SetCPU on boot. Pershoot (the 10.1 kernel guru) suggested that it might be falling to conservative at the default frequency like when it goes to sleep, but not coming back. However,when it goes to sleep and I turn it back on, it always goes back to my 1.5GHz just fine. And when it's set and happy, it never has this issue on boot either. Maybe a second boot is all that it takes, but I would sure like to pin it down and understand it better. Let me know if anyone has any ideas.
[Galaxy Tab 8.9 Android Development] netxph:
My tablet is flying now... after a lot of crashes... I finally stabled @ -50UV and 1400mhz... I don't know if you have the same setting as mine :)
[Galaxy Tab 8.9 Android Development] dedalos1:
With Set Cpu? What kind of governor? I find a lot of difficulties to use set cpu and I don't know how to do? Thanks for your help.
[Galaxy Tab 8.9 Android Development] thndd:
Just tried version v2c on my p7300. I'm using overcome 2.1.1 and it feels faster with overcome's kernel. Anyone feel the same?

I have tried frequencies @1,4 and 1,5Ghz and UV @-50

I also noticed I only have 741 528 kB of memory. I thoght this device had 1GB?
[Galaxy Tab 8.9 Android Development] _motley:
Setup SetCPU for interactive governor and 1.4GHz and configure to set on boot. Do not set UV on boot yet. Reboot and see how it runs. Bench scores should much higher than stock (Overcome kernel). After you are sure OC is working, then work with UV settings. After they are good, set them to take effect on boot as well.
[Galaxy Tab 8.9 Android Development] nirogu325:
Some memory is reserved for the OS and the rest of the device's components.

Motley, what is your UV setting per frequency if any? I just want some ideas/suggestions for next time.
[Galaxy Tab 8.9 Android Development] thndd:
I did just as you told me to + a couple of reboot extra and now it is very fast :)

It is running @1,5Ghz and UV -50

Thank you! Love your work :D
[Galaxy Tab 8.9 Android Development] _motley:
Thanks nirogu325, I forgot to answer that question!

I typically run @1.5GHz -50mV or -75mV and leave the rest of the frequencies as-is. For my usage, I don't find the CPU spending a lot of time anywhere else besides 216, 312, 1000, and 1504. Every other frequency is typically less than 1% of time in state. If folks can UV further and keep it stable, that is great. I don't worry about battery too much since I am mostly around the house and don't mind charging every 2-3 days.
[Galaxy Tab 8.9 Android Development] _motley:
Glad to hear that. Thanks for the update!
[Galaxy Tab 8.9 Android Development] ZeroPDA:
I asked LUKS Manager developer Nemesis][ for help here. If he is kind he will help to solve some issues.
[Galaxy Tab 8.9 Android Development] tommydroidx:
samsung galaxy tab 8.9 kernel by motley

So, I'm having trouble loading drivers on my pc and odin not working, not even sure how to use odin so i don't have cwm yet but I downloaded motleys kernel with overcome ROM 2.1.1 and went to recovery system and flashed/installed from SD motleys kernel. Am I screwed or can I return complete system to stock if I needed to? seems to be running ok except for a few force closes. Still working on loading drivers part. Samsung has such crappy software I think! One thing i did do, is did a back up, in system recovery. Can someone please point me in the right direction? I'm not a noobie at this but not that skillful either!
[Galaxy Tab 8.9 Android Development] _motley:
You really need to get CWM installed using ODIN before you start flashing things. Once you get CWM installed, then you can backup and flash ROMs and kernels the way they were designed to be flashed. I had to borrow a Windows 7 machine when I first got my tablet, but I don't remember it being too hard to get ODIN 1.85 up and working after installing the USB drivers from Samsung.

After you get CWM installed, wipe cache and then wipe dalvik. Next, install a ROM. Finally, flash my kernel. Use SetCPU to set the governor to interactive and your desired frequency.
[Galaxy Tab 8.9 Android Development] _motley:
Cool, let's see what he says. I won't be surprised if the kernel is missing a feature that is required. There are a couple that I have looked into that may required, but it would be great to have a little input from the dev before I start trying stuff.
[Galaxy Tab 8.9 Android Development] mynewuser:
I notice the stock tablet can be charge using normal PC USB port. The tab say discharging and red x but it basically working. So do I need to perform the usb charging hack?
[Galaxy Tab 8.9 Android Development] _motley:
I grabbed this fix from the 10.1 kernel base. I was wondering the same thing when I went forward with the code change. Here is what I know so far...

The change in the kernel allows the tablet to properly report the charging state properly back to the OS. After the fix, the USB charging seems to be much faster. Before, it would take forever to trickle up 1%. Now it really seems be a viable charging source, but still slower than plugging in to the wall of course. I have not however done any tests to prove this, but I think the mod is definitely worthwhile. Samsung should have done it like this stock, but I think they did not want to deal with support calls to troubleshoot charging via USB as it is not as fast and reliable. Who wants to troubleshoot usb busses on 8 year old PCs?

That said, the option is there and folks have a choice on whether to activate it or not. Others, please report back on your experience on this topic.
[Galaxy Tab 8.9 Android Development] _motley:
Good news ZeroPDA, I now have this working in the upcoming version of the kernel. I have built after enabling CONFIG_KEYS=y and CONFIG_BLK_DEV_CRYPTOLOOP=y and it works perfectly with the ext2 file system created in LUKS. It doesn't work with FAT yet, but I am going to open MSDOS file system support in the kernel to see if that fixes it. The partition created by LUKS is FAT12 not FAT32 I believe. Is FAT support in LUKS important to you? I think I will only enable if you need it. FAT12 will only support 8.3 file naming...that doesn't seem too useful in today's world unless you really need it for backward support for some loop devices you already have, assuming they are portable from device to device.
[Galaxy Tab 8.9 Android Development] nirogu325:
After testing (in KJ5 Stock), I changed back and forth the governors and discovered the screen distortion only happens when the governor is set to Ondemand. It stops doing it when changed to Interactive. Clockspeeds don't matter. This is without UV. I haven't tested UV with Interactive yet.

EDIT: I suggest putting Interactive as the default governor. I noticed some lag with Ondemand (apart from the screen issue).
[Galaxy Tab 8.9 Android Development] _motley:
I will make this clearer in the OP as many have had the same problem. I recommend in the first post under "Install" that you use Interactive...here is an explanation of why the default is still set to OnDemand.

http://xdaforums.com/showpost.php?p=19896804&postcount=160

I would like to get this figured out so I can this is no longer an issue when folks are first setting up. They think something is wrong, but it is because they don't have it setup as recommended. I will probably add an FAQ in the 2nd post and put a note in red in the OP.

Interesting about the video distortion with OnDemand...I never run with it, so that is why I probably have never seen it.

Next version is in the works and it should add some performance improvements.
[Galaxy Tab 8.9 Android Development] ZeroPDA:
Thank you very much for working on it. Really, LUKS manager is a best crypto app and your kernel is the best one in both areas for SGT 8.9 - performance and powersaving. For me it would be a great loss if your kernel doesn't support LUKS Manager. Personally me, I don't need FAT support in kernel. I satisfied with ext2 file system, because I like Linux on my Desktop. But I am sure there are Windows users for whom it is critical to have FAT support. For me it was shocking to get to know that LUKS Manager uses FAT12 file system. Unbelievable! FAT12 doesn't need either for me or for my friends. At least FAT16 is needed. You are the one who really welcomes users requests. With your kernel it is safe to have confidential info on such devices without fear to loose it . You don't even imagine how important your work is for people. I can make safe syncing volumes over dropbox account and use the same confidential data everywhere. We greatly appreciate your hard work! Thanks a lot!!!
[Galaxy Tab 8.9 Android Development] _motley:
Thanks for the kind words ZeroPDA. It is great working with folks all over the world to make this platform better. Not sure what is going on with FAT support, but the ext2 is working for me now. Even after adding MSDOS file system options in the kernel, I couldn't get LUKS to work with FAT. I'll keep poking at it and see if I can figure it out and maybe the dev might have some insight for us.

Version 2d has now been posted with LUKS support (ext2 volumes), auto-group scheduling, and some other bug fixes. Let me know how it goes!
[Galaxy Tab 8.9 Android Development] Hurrian:
Can we loopmount ext4 files now?

On the stock kernel a while back I always got File not found errors using mount -t ext4 -o loop.