yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 8.9 Android Development] _motley:
Good news! I have a fix for the lock screen! Doing some testing now. It was the touchscreen driver like I thought. The Melfas driver automatically was downgrading the firmware on every boot with built-in firmware compiled into the kernel (not a .bin file on disk). I have now eliminated the firmware downgrade by toggling some available switches they had available and just allow the firmware to be whatever it is already on your tablet. The firmware seems to only stay resident until you reboot and then it reverts back to the firmware that was already on the tablet. This may explain the wacky differences between tablets if they were on different firmwares.

Edit: new release see OP

Version 1.0h changes (beta 1):

-Touchscreen lag appears to be fixed! Let me know how it works for you.

-UV bug fix (experimental, still in testing)

-Governor fixes, SetCPU seems to set properly on boot now.
[Galaxy Tab 8.9 Android Development] SGSChris:
wow - you rock!! lag is gone. congrats and thanks a lot!
[Galaxy Tab 8.9 Android Development] kevinchg:
v1h does fix the lock screen lag for me, well done ,thank you !

for setcpu function, i still cannot get interactive scaling work when boot,

i set cpu at 1.4ghz interactive mode before reboot, it works normally,

however, after reboot, i check the clock in setcpu, it locks at 1.0ghz, not well scaling, and i do check "set on boot" option in setcpu.

but if i set to ondemand mode, it works well even after reboot...
[Galaxy Tab 8.9 Android Development] tgallant21:
Lock screen issue solved here, overcome rom 1.2. Thank you for your hard work on this.
[Galaxy Tab 8.9 Android Development] konceptz:
Thanks for the lessons and the fix!

This was really the only thing keeping me from full timing this rom.

You just revitalized this community! And probably helped Samsung sell ozens more 8.9s
[Galaxy Tab 8.9 Android Development] Hurrian:
Sweet, UV control. Time to test things out, and how far you can UV a Tegra 2.

EDIT: Apparently, UV control works now. I set a -200mV UV on the device at 1000MHz, and it hung up after ~10 seconds.

EDIT2: My Tab is happy at 1000MHz@-175mV. Thanks motley!
[Galaxy Tab 8.9 Android Development] weltwon:
V1.0h fixed my lag

I'm running stock, used CPU Master Free to set Conservative 1504 Max, 216 Min, ZERO lag here. Great job!

I'll be adding & recommending your work in my epinions.com review of the Galaxy Tab 8.9

Glenn :)

P.S. With all these settings, battery drain in standby is less than 1%/hr.
[Galaxy Tab 8.9 Android Development] bdfull3r:
I am a completely noob for ROMs

What do you have to wipe when you flash. I read it was different when going from stock to a versus aROM update. Can someone help?
[Galaxy Tab 8.9 Android Development] _motley:
New version v1i released

Please see OP for download and details. Thanks again for all the testing, feedback and support!
[Galaxy Tab 8.9 Android Development] _motley:
This thread is for a custom kernel only, not a complete ROM per se. In order to use it, you first need to be on a rooted ROM based on Android stock HC 3.1 and then you need to install CWM (see that thread on this forum).

For kernel only flashes, like this one, you don't have to wipe anything, it will replace your entire boot partition on your device and won't touch any of your data or your Android OS partitions.

Make sure you have a backup in CWM before flashing anything to your device. For OS ROMs (sometimes they also include kernels), follow the ROM developers instructions on what to wipe. I suggest you do some reading first in order to become a little more comfortable.
[Galaxy Tab 8.9 Android Development] JeffSmith215:
Accelerometer not working on 3.2?

I know the kernel is designated for the 3.1 Kernel but I though I would test on the 3.2 (HTJ85B.XXKJ4 P7310XXKJ4) since my device had already upgraded.

Tab works really well and stable all the up to 1.5 - speed increase really noticeable.

However, the accelerometer does not seem to be working. Screen stays in landscape no matter which way you hold the device. Used software to manually flip it to portrait and back and this works ok - maybe a small kernel difference for accel between 3.1 and 3.2?

Great work by the way - Hope this helps.....
[Galaxy Tab 8.9 Android Development] _motley:
Appreciate that Jeff! This is where I am going to go next. Hopefully Samsung provides the source for the 3.2 kernel...I need to check to see if it is out there yet....their download site is a bit confusing with labels...

Can you confirm that video playback, YouTube, cameras, WiFi, sound, GPS, Bluetooth etc. are working? Any info you can provide about what you tested would be great. We have the Kionix KXTF9 accelerometer and the MPU3050 (Digital Triple Axis (X/Y/Z) MEMS Gyroscope), so I am guessing this will be easy to fix once I can identify what changed.

Thanks again.

Edit: so it sounds like stock HC3.2 is able to be rooted just like 3.1...that is great news. I came from the Iconia world where things were locked down more and the official 3.2 was not able to be rooted easily in stock form as Acer eliminated our itsmagic word-around to rewrite the checksums into a partition.
[Galaxy Tab 8.9 Android Development] poisike:
The root_original.zip (from http://xdaforums.com/showthread.php?t=1287205) worked just fine on P7300BVKJ5 rom.
[Galaxy Tab 8.9 Android Development] JeffSmith215:
You're right - much more broken

Ok - so I went back and did a slightly more thorough test and it does seem that a bit more is broken.

Working:

* GPS

* Wi-Fi

* Bluetooth (keyboard and mouse tested)

* Music

* Brightness detector

Not Working (so far):

* Camera (app opens in a forced portrait mode, then FC's)

* Video Playback (eventually force closes)

* You Tube: Force closes after trying to open a stream

Looks like this is all related to accelerometer in some way as the basic component is working (you can use the motion zoom for example or play accelerometer based games and that all works fine).

Perhaps something to do with the new screen handling code they put in 3.2?

Hopefully simple to fix - good luck!
[Galaxy Tab 8.9 Android Development] bwagner:
Undervolting

I have been playing with the undervolting features of the kernel. Running Overcome 1.2 and v1h.

1504 MHz - 1050 mV

1400 MHz - 1050 mV

1200 MHz - 1000mV

1000 MHz - 950 mV

912 MHz - 950 mV

816 MHz - 900 mV

760 MHz - 900 mV

608 MHz - 725 mV

456 MHz - 725 mV

312 MHz - 725 mV

216 MHz - 725 mV

Pretty good undervolts, but honestly the battery life was fantastic beforehand.

B
[Galaxy Tab 8.9 Android Development] konceptz:
I am using h and have no side effects at 1504. Camera, wifi, GPS etc are all working. Battery life is not noticably lower than stock Samsung, probably in part due to overcome.

Haven't done anything that pegs the CPU max for long periods of time, but as we all know different chips have different tolerances.

I was getting some heating at 1.5 before while charging, but it has gone away, possibly due to thermal paste settling in (does the chip even have paste and attach to a heatsink?)

Landscape mode (homescreen) is still noticably jittery, though large PDF (ezpdf) viewing has greatly improved.

Thanks again! At this point its hard to justify moving to 1.0i or changing even to 3.2 until ICS. I have 3.2 on transformer and its not overtly better than overcome especially with 1.5oc.

Sunspider 9.1: 1511.6 ms

Rightware browsermark: 128395
[Galaxy Tab 8.9 Android Development] Loccy:
I couldn't get anywhere near these, unfortunately. Started what I thought was conservatively by using your values plus 50mV. Hit apply - Kaboom. Clearly my Tab wears pink underwear.

I will have a play and see where the sweet spot is for me when I get a few spare hours to play, but to be honest I've never really got in to undervolting. Does it really make that much difference to battery life? My perception has always been that the screen is the major consumer of juice.
[Galaxy Tab 8.9 Android Development] _motley:
Hi guys, not sure about those voltages, they seem way too low for me. I am familiar with Tegra platform on other devices and they don't make sense to me. I think I know why you may have been able to do this....Loccy I think your underwear may be ok this time:)

With 1.0h, sometimes SetCPU would say that it was setting the CPU at a certain clock speed, but it really was not. This is why I set the default

in the kernel

to be the OnDemand governor for v1.0i. If you have SetCPU set to the recommended interactive governor, it will then be able to properly set correctly on boot (or after boot if you set manually). Not sure why this is, but it is at least a workaround for now since it seems to set correctly when it changes from the stock speed with ondemand over to the interactive governor. There is still some problem here because after the first set of the clock speed, it appears to be hindering further changes with SetCPU it seems.

For 1.4-1.5GHz using the interactive governor, you should be able to see a Linpack score between 70-87 depending on what else is running on the tablet. The ad-free version is better because the ads can lower your scores unless you hit test at the right time when the ad is already loaded. If you keep hitting test at 1.5Ghz, your consistent higher scores should be around 76-83.

So, what I am saying is that you need to make sure the clock speed is what you think it is. Verify the clock speed by using Linpack scores and verify in SetCPU that the different clock speeds are being used periodically, most particularly the highest clock speed. If your clock speeds are not what you think they are, then your aggressive UV values are not even being used for the higher clock speeds.

I recommend that you:

Uncheck the SetCPU setting to "set on boot" and then upgrade to kernel 1.0i. Don't set this back until you are sure you are good to go with your clock speed and UV settings.

Boot up for the first time and use SetCPU to set your desired clock speed and to use the interactive governor.

Verify your linpack scores to make sure they are higher than stock (~50).

Once the clock speed is verified, run some bench marks (AnTuTu is good) and do some heavy multiple-tab browsing sessions to make sure your tablet is stable. Watch some vids or whatever you like to do, this is the key.

If you are safe, step down your voltage at the highest clock speed by -25mV. Repeat the benchmarks and usage scenarios.

If it fails (locks the tab), reboot and step back up +10mV and try again until it is stable.

Repeat the UV calibration for the next lower clock speed and so forth. I don't typically mess with anything below GHz since those are stock values.

OC'ing will use more battery and this is why UV is so valuable for folks that want to OC, but still get the lowest battery drain possible when the governor kicks up to the higher speeds.
[Galaxy Tab 8.9 Android Development] poolguy:
I'm stable and content at -100 across the board except 216 (unchanged@750). 1.0i w/Overcome 1.2.

Antutu: 6600

Lockups @ -125. Not patient enough to go any further.
[Galaxy Tab 8.9 Android Development] bdfull3r:
Running stable at 1.4

Linpack around 72 average

I haven't doone any undervolting, for a device with close to 10 hours of battery, i don't see much of a point if i lose half an hur, i haven't noticed a large difference in battery life

*off topic

HOw do i edit my signature? I can't find it in my control panel

EDIT

Still got lockscreen lag here. Stock ROM, Wifi version
[Galaxy Tab 8.9 Android Development] chadti99:
I'm stable at 1.5, could we try just a hair more voltage at 1.6?

Consistently benching over 3400 at 1.6 although I imagine it would be higher if all the gpu tests weren't capped at 30fps.
[Galaxy Tab 8.9 Android Development] the-bink:
I also have been running this Kernel at 1.2GHz on Overcome V.1.2 for about 1 week, and have jet to encounter a problem. Keep up the good work!

I use the app "No lock" so I do not have a lockscreen. However, when I switch the screen on, it takes about 1 second to start responding to touch.

With Version 1.0i the screen issue is solved. Will be testing 1.4GHz the coming week. Thanks again for this great kernel.

PS I'm using the free app "CPU tuner" to set the Tegra 2 SoC to 1.4GHz
[Galaxy Tab 8.9 Android Development] _motley:
Please make sure you are running v1i as everyone else has reported that it is fixed after this update.

Sure, I will bump up by 25mV in the next release.
[Galaxy Tab 8.9 Android Development] bdfull3r:
I think it is the latest, got it from the front page. Still get the occassional lockscreen lag. From a black screen, press the power button and it waits 3 to 5 seconds before responding
[Galaxy Tab 8.9 Android Development] chadti99:
Try reflashing, the latest kernel fixed the lag for me.
[Galaxy Tab 8.9 Android Development] ajaffarali:
Will you be porting this for the 3G/7300 version? Would love to try it out on that.
[Galaxy Tab 8.9 Android Development] _motley:
As soon as I have the HC 3.2 support released, I'll do a build for the 7300 guys to try out. It's most likely going to also be on new HC 3.2 base moving forward, but I am not 100% sure yet.
[Galaxy Tab 8.9 Android Development] SGSChris:
deleted, posted in wrong section, sorry
[Galaxy Tab 8.9 Android Development] ajaffarali:
Thanks! I think using the HC 3.2 base is a good idea.
[Galaxy Tab 8.9 Android Development] xblade96:
does this kernel work with the most recent Overcome rom?
[Galaxy Tab 8.9 Android Development] _motley:
I will be uploading a new version in a couple hours that will support HC3.2 and thus the new Overcome rom:)
[Galaxy Tab 8.9 Android Development] xblade96:
Nice! Thanks!
[Galaxy Tab 8.9 Android Development] _motley:
New version posted for HC 3.2 support, please see OP. Let me know how it works. It still doesn't work for 3G models, but I will work on adding support in the v2 lineage.
[Galaxy Tab 8.9 Android Development] nirogu325:
Took the plunge and installed your v2a kernel. Currently testing with all freqs (up to 1Ghz) UV'ed -50 except for the lowest freq which SetCPU only lets me UV -25, weird. I will let you know how it goes. By the way, do you know if USB charging might be possible? I think I saw something related to it at 10.1 forums, but don't know if it's kernel or ROM bound.
[Galaxy Tab 8.9 Android Development] SGSChris:
just installed on overcome 2.0 rom. no fcs except once gmail fc.

the homscreen seems noticably more laggy than on overcome rom. i am using adw launcher ex and oc to 1.4GHz.

thanks a lot for the update.
[Galaxy Tab 8.9 Android Development] nirogu325:
So far I've noticed some distorted lines when you turn off the screen. It doesn't do it all the time, but turn on/off the screen several times and you'll see. I only am UVing mildly (-50mV across). The rest is untouched.

Sent from my GT-P7310
[Galaxy Tab 8.9 Android Development] Hurrian:
Only got this once on my Tab 8.9, flashed with Overcome 2.0, not flashed with the new Motley kernel, and definitely not UV'd.
[Galaxy Tab 8.9 Android Development] _motley:
Thanks for the feedback guys. Gotta go to work, but here is some quick input for now.

AFAIK, I should have changed anything that would affect the UV at the lower freq. We you able to go lower on HC 3.1 and v1 of the kernel. I'll check into the USB charging.

I have been doing all my testing on the stock 3.2 ROM thus far just so I can rule out anything in a customized ROM. I'll have to check out the overcome 2.0. Make sure you reset your default gov to interactive and that OC is actually working. On stock, it feels somewhat laggy without the overclock, but this is normal I think.

Not seeing this on the stock 3.2 ROM so far...just turned the screen on and off 30 times, but can't seem to duplicate it.

Thanks for the input.
[Galaxy Tab 8.9 Android Development] xblade96:
how do i get stock 3.2? the one that you use? also where can i find the root for it as well?
[Galaxy Tab 8.9 Android Development] fishton:
Hi mate

Any chance to get a P7300 version of your amazing kernel anytime soon :D :D :D
[Galaxy Tab 8.9 Android Development] the-bink:
Will give the V.2.0 kernel a go on my 7310 with Overcome V.2.0. Again thanks!

---------- Post added at 09:00 PM ---------- Previous post was at 08:57 PM ----------

Also had this ones with Overcome, before I installed the new Kernel. So definitely not a Motley Kernel issue.
[Galaxy Tab 8.9 Android Development] goenieg:
Thanks! Works like a charm with overcome 2 here.
[Galaxy Tab 8.9 Android Development] _motley:
I created a CWM-flashable and pre-rooted stock 3.2 ROM that I can share when I get a chance to upload somewhere. There is also an ODIN-flashable version, but it blasts away the all the partitions including boot and recovery (not sure about data). You can use the normal root and install CWM methods just like 3.1 once the ODIN flash is done.

I will be looking into this soon, just can't promise an exact ETA. Are you willing to test when it is ready?
[Galaxy Tab 8.9 Android Development] nirogu325:
No, this is the first time I install your kernel. Gonna remove UV as I am noticing lag after long hours.

Sent from my GT-P7310
[Galaxy Tab 8.9 Android Development] fishton:
Hummm, let me think ..... ..... .... YEAHHHHHHHHHHHHHHHH !!!!
[Galaxy Tab 8.9 Android Development] choatb:
Ready

I was ready as well.

:)
[Galaxy Tab 8.9 Android Development] _motley:
Sent you a PM earlier today to see if you wanted to give it a test. I sent a request to 5 members last night to see if they wanted to test 3G out, but nobody has responded with any feedback yet:( I would like to have a couple users provide feedback before I release to the masses since I don't have 3G.
[Galaxy Tab 8.9 Android Development] _motley:
Kernel now available for 7300 3G model

Update: I have received feedback from two beta testers and it appears that the 7300 3G kernel for Android 3.2 is performing well and 3G is working fine. I have added the info to the OP, but I have left the "beta" tag on it for now until we get more feedback. Let me know how it goes:D
[Galaxy Tab 8.9 Android Development] nirogu325:
EDIT: Wait wait....the screen turned on with nothing onscreen and turned off just now. I am puzzled. :confused:

EDIT 2: Issue reappeared in KJ4. Kernel related perhaps?
[Galaxy Tab 8.9 Android Development] _motley:
Not sure, I am running KJ4 too and I haven't seen the issue. I'll let you know if I do.
[Galaxy Tab 8.9 Android Development] nirogu325:
Motley, I've just sent you via PM a link to download a video I made just right now about the issue I wrote above. You will see the distortion and the screen weirdly turning on (by itself) after pressing the button and then it turns off. Feel free to ask if necessary.
[Galaxy Tab 8.9 Android Development] _motley:
Thanks, just watched the vid. That is pretty strange. Does it go away using the stock kernel that comes with the KJ4 3.2 build?

Grab the dmesg output to your sdcard and then analyze it to see what is going on.

From a terminal session:

dmesg -> /sdcard/dmesg_offon.txt
[Galaxy Tab 8.9 Android Development] ehcan:
I got the screen corruption at first boot for about 2 seconds after the dalvik and cache wipe. However, then the lock screen showed up and everything was fine from then on. The home screen swipe is definitely slower than the Orange 3.2 stock but with the 1.4GHz+, they are about the same. There is a little lag from time to time but the Orange exhibit the same symptoms when I first flashed it. After a few days, the ROM become much smoother so I am going to do the same and wait for a few days before render my final verdict.

My little 8.9 3G at 1.5GHz just gave its big brother 10.1 the finger while zooming past it on benchmarks.

Thank you so much _motley!

Orange Stock ROM with Motley 3G 2.0a kernel
[Galaxy Tab 8.9 Android Development] nirogu325:
EDIT: Coming right up.
[Galaxy Tab 8.9 Android Development] phonic:
Thanks Motley. Installed the latest kernel on my 7310. OC'd to 1.4 using the standard settings. Much more responsive overall. Will play around with it for a while then maybe test out 1.5.
[Galaxy Tab 8.9 Android Development] nirogu325:
EDIT2: Motley, the issues popped up even after formatting back to KJ4 stock. They didn't show up until I installed the kernel. Here is another log.
[Galaxy Tab 8.9 Android Development] netxph:
Has anyone tested this already in OC 2.0 3G? I'm willing to test this but, can you teach me how to backup boot.img and how to restore it?

Thanks :)
[Galaxy Tab 8.9 Android Development] phonic:
One of the prerequisites is to install CWM. This is what you use to install the new kernel. Once CWM is installed, before installing the kernel, chose the backup option and make a backup of your device. This will back everything up, including the boot image.

If you ever need to restore it back, you will do a selective restore and only restore the boot image.

It's a fairly straighforward and easy procedure.
[Galaxy Tab 8.9 Android Development] alishankiti:
I am using the OC 3g version and its working like a charm at 1.5ghz. First you need to root, then install clockwork recovery. Download the appropriate kernel, boot into recovery and flash the kernel.
[Galaxy Tab 8.9 Android Development] Jade Eyed Wolf:
I have the 3G too, but I'm not on HC 3.2 yet. Will that matter (much)?
[Galaxy Tab 8.9 Android Development] chriscsh:
i have 7300(3G) with overcome 2.0 rom

after flash this kernel, i feel this a little bit slow then the ori kernel

any advise or i miss something :confused:
[Galaxy Tab 8.9 Android Development] netxph:
Felt that too, specially in Apps transition... :(
[Galaxy Tab 8.9 Android Development] _motley:
The 3G kernel is only for HC 3.2 ROMs at the moment. It will cause rotation issues etc. if you use it against a 3.1 ROM. Read on below with my additional comments, I would sit tight for now.

Make sure you use SetCPU or equivalent to switch to the "interactive" governor. At 1.4 or 1.5Ghz, you should be able to demonstrate much better benchmarks with Linpack and Quadrant etc.

Additional comments for today:

Please also see my and the other gentlemen's comments in the following thread as well as in the Overcome thread referenced. Many of us are of the feeling that the HC 3.2 early release might not be a good option yet. While the 3.2 with OC kernel benchmarks show the same raw performance improvements as in 3.1, the HC 3.2 base from Samsung isn't as smooth as the 3.1 official release. I am speaking for the WiFi only models as I don't have a 3G model.

http://xdaforums.com/showpost.php?p=19660121&postcount=4
[Galaxy Tab 8.9 Android Development] chriscsh:
thanks, will try it tonight :D
[Galaxy Tab 8.9 Android Development] chriscsh:
after the setcpu enable, i feel my tablet can fly :D

thanks
[Galaxy Tab 8.9 Android Development] _motley:
Glad to hear, which rom are you on?
[Galaxy Tab 8.9 Android Development] chriscsh:
Overcome 2.0:)
[Galaxy Tab 8.9 Android Development] goenieg:
Using your kernel and the 3.2 image here, no major problems. Setcpu @ 1.4 interactive, and all feels quite smooth for me. I wonder what might be up with your setup what makes you go back to 3.1. I do have the occasional market crash, and some wifi connection instability though.

(Juice Defender Ultimate

Adblock

Auto Memory Killer

also in use.)
[Galaxy Tab 8.9 Android Development] ZBoater:
Same here. Although my wifi was just as flaky coming out of sleep in 3.1.
[Galaxy Tab 8.9 Android Development] Hurrian:
Is it possible to split the patches from the source files? Should make it easier in the future to port newer kernels to the device, although this is time consuming.
[Galaxy Tab 8.9 Android Development] _motley:
I didn't have any major issues, I just feel 3.2 on kernel 2a is less fluent than 3.1 on kernel v1i. It is very subtle. I haven't had any WiFi issues on 3.1 or 3.2 with with my kernel or the stock kernel.

Are you talking about the code that you see in my git repo or the kernel patches themselves? Not sure exactly what you mean, but with source control it is pretty easy to roll back stuff if necessary. The kernel itself is built into one zImage binary file, in case you were wondering about that.