yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Android Development] lwkoon:
Can AAccount apply Screen-On mode on kernel so that it will benefits those who apply "make-call-mod" on SGT 10.1 3G/LTE
[Galaxy Tab 10.1 Android Development] jaswinky:
For testing proposes, if you try with a different charger, you need it to be also a samsung charger, if don't, same will happen, usb charging will be activated instead of ac charging.

Enviado desde mi GT-P7510 usando Tapatalk 2
[Galaxy Tab 10.1 Android Development] AAccount:
But usb charging should work so no need for any kind of ac mod.

Sent from my GT-I9300
[Galaxy Tab 10.1 Android Development] AAccount:
Can I get some kind of reference to that?
[Galaxy Tab 10.1 Android Development] danielsf:
AAcount, thanks for the cm10 support, it is working well although would it be possible to include pershoots touch boost interactive governor parameter please? As from what I have been it can help with more constant ui interaction framerates. Thanks again, got to say I love the GPU overclock. Thanks :)
[Galaxy Tab 10.1 Android Development] decatf:
How does Samsung's powersaving governor work?
[Galaxy Tab 10.1 Android Development] AAccount:
To be honest I'm not sure. I just saw it in the config file and enabled it. I was trying to figure out why the tablet went into a 450MHz cap, messed around with the compile options (y vs m) and saw that in there. Thought I would just enable it. I have found a correlation between using system tuner and the 450MHz cap but didn't do very many replications to nail down the cause. However, since uninstalling, I haven't ran into that problem.
[Galaxy Tab 10.1 Android Development] AAccount:
Warning. Jus discovered that even after uninstalling system tuner the tablet goes into a 450MHz. If you notice inexplicable lag, check performance settings and see max speed and governor. You MUST change the governor before max speed or max will nt be changed.
[Galaxy Tab 10.1 Android Development] angiotell:
Where can I find your kernel settings please?
[Galaxy Tab 10.1 Android Development] AAccount:
Settings --> Performance --> Processor. Ignore the warning.
[Galaxy Tab 10.1 Android Development] AAccount:
Hey everyone,

New 1.7.4b uploaded to try and fix weird 450MHz cap issue. Did one of pershoot's changes. You'll know you're experiencing the 450MHz when AFTER coming out the sleep, the tablet is inexplicably laggy/unreasonably slow.
[Galaxy Tab 10.1 Android Development] angiotell:
I cannot find it..

could you tell me settings in ITALIAN, please? :o
[Galaxy Tab 10.1 Android Development] xdapao3:
Are you for real..?

Anyway, which ROM are you running? You probably do not have those settings...

And if you did they would be something like "Settaggi/Impostazioni/Configurazione --> Prestazioni --> Processore". What could be more easy?

---------- Post added at 12:49 PM ---------- Previous post was at 12:04 PM ----------

BUG REPORT: running stock ICS LQ8 (rooted and CWM'ed) and 1.7.4b OC @ 1400Mhz, if I start charging the tab while it's turned off it starts up and the touchscreen is unresponsive (no touch is registered). Rebooting the tab while it's still charging the screen is still unresponsive. The only way to charge without issues is to start charging the tab while it's turned on. I hadn't this issue with 1.6.4 (which I run for a long time) and with 1.7.4 (but run it only a few days so can't be 100% sure) so I think it's a 1.7.4b's thing.
[Galaxy Tab 10.1 Android Development] AAccount:
Thats because it's CM10 compatible. Making it cyanogenmod compatible introduces that bug into stock firmware. It's one or the other...

Sent from my GT-I9300
[Galaxy Tab 10.1 Android Development] xdapao3:
Oh.. OK :)

Which kernel would you advise for stock ROM, 1.6.4 or 1.7.4b?

I can live with this bug if 1.7.4 is a "better kernel" :)

P.S. I apologize to everybody, my "bug" had already been reported and addressed... I am catching up now reading all of the older posts... I usually do so before posting but I've had so little spare time lately.. so I am wasting everybody else's time instead :p Sorry :)
[Galaxy Tab 10.1 Android Development] AAccount:
No need to apologize. I perfectly understand not having time to read posts. To be honest V1.7 was the last major edition. Everything else is compatibility fixes. V1.7 is the last for stock rom. 1.7.2 is a cm9 compatibility fix, 1.7.4 is for cm10 compatibility. You wont be missing anything.

Sent from my GT-I9300
[Galaxy Tab 10.1 Android Development] angiotell:
.

I've not those ones settings

I'm running jellybeans ics by Toldo v7...
[Galaxy Tab 10.1 Android Development] AAccount:
Thats a stock samsung ics rom. It's not really jellybean. This setting is only available on cyanogebmos.

Sent from my GT-I9300
[Galaxy Tab 10.1 Android Development] rommelrommel:
Just upgraded (fresh install after wipe, the whole lot) from previous CM10 (August); I'm now on latest october CM10,

with the V1.74b-kernel on 1.6GHz. (I'm from Holland but bought a P7510 at Best Buy in the US).

All works, seems stable so far. Just wondering: were can I see/find details on faster GPU ??
[Galaxy Tab 10.1 Android Development] AAccount:
Gpu overclock is included. Theres a sysfs variable somewhere that will tell you. Ill put the exact path later when i have time. Also, you could just run glbenchmark on stock pershoot and compare that with my kernel. The score increase is proportional to 400/333.

Sent from my GT-I9300
[Galaxy Tab 10.1 Android Development] rob2011:
Works great with A1Kernel1.5.9XE + Stock ICS
[Galaxy Tab 10.1 Android Development] AAccount:
Do not use any version before 1.6.3. The mmc brick bug hasn't been fixed yet. That bug causes a super HARD brick. All versions after and including v1.6.3 have tne fix.
[Galaxy Tab 10.1 Android Development] rob2011:
hmm im using A1Kernel1.5.9XE without any problems though

---------- Post added at 03:49 AM ---------- Previous post was at 03:31 AM ----------

Used this page to overclock

http://galaxytabhacks.com/galaxy-tab-hacks/how-to-overclock-ics-on-galaxy-tab-10-1-with-a1-kernel/
[Galaxy Tab 10.1 Android Development] AAccount:
I highly recommend you download a newer version. The brick bug is rather unpredictable and can strike when you least expect it. It will produce a super hard bricked tab that is impossible to recover using ALL known methods.

----------------------------Status update-------------------

I tried once again to oc the gpu to 450MHz by referencing this iconia kernel

http://xdaforums.com/showthread.php?t=1839873

Unfortunately that didn't work as well as variants based on that idea :(
[Galaxy Tab 10.1 Android Development] danielsf:
Hi, thanks for trying :) Also clemsyn is an extremely talented developer with lots of experience with pushing the t20 tegra 2, I know he made an appearance in this thread. On the nexus 7 thread he is very approachable, maybe it is worth sending him a message saying what you have tried and where is seems to be failing? Also do you think it would be possible to have a build of your kernel with pershoots cm10 variant of the interactive Governor please, as the touch boosts option is supposed to help give a more consistently smooth ui? Thank you for all your work :)
[Galaxy Tab 10.1 Android Development] rob2011:
Can i just install the updated version over the old one or do i have to remove the kernel and go back to stock first?
[Galaxy Tab 10.1 Android Development] AAccount:
Just install over the old one. No need to go back to stock.
[Galaxy Tab 10.1 Android Development] rob2011:
Thanks. Ill be using 1.7 as im running stock

---------- Post added at 04:22 PM ---------- Previous post was at 03:56 PM ----------

Just updated now, no problems what so ever thanks AA :cowboy:
[Galaxy Tab 10.1 Android Development] AAccount:
I know he's good but unfortunately he couldn't force the tablet into submission. I've tried his suggestion but the tablet refuses to give. I'll look at pershoot's interactive next week but should be doable. I got the smartassv2 governor working as part of a few trials.
[Galaxy Tab 10.1 Android Development] Trex07:
Has anyone try V1.7.4b with latest CM-10-20121030?
[Galaxy Tab 10.1 Android Development] AAccount:
Using it on that build right now. So far everything seems to be working.
[Galaxy Tab 10.1 Android Development] Trex07:
Tq, by the way how to use the voltage control?
[Galaxy Tab 10.1 Android Development] jayceebee23:
I can confirm that it works on the latest 1030 p4wifi build. Been using it for couple of days now.
[Galaxy Tab 10.1 Android Development] Martini3001:
Does anybody know if the Kernel is working with AOKP (Unofficial) Jelly Bean? This ROM is based on CM10... so 1.7.4 should work, isnt it?

Thanks a lot!

Greetings

Martini
[Galaxy Tab 10.1 Android Development] AAccount:
You may need 1.7.2 or 1.7.4b. I remember there was an early "secret" CM10 build that ran V1.7.2 just fine. Then, there was a small change in between that secret CM10 build and the experimental ones that are now available. That small change is addressed in V1.7.4b. I would love to try it myself but I have 2 midterms this week. If you do try it, please report back.
[Galaxy Tab 10.1 Android Development] Martini3001:
Thank you for answering so fast.

I will try your kernel in a few minutes, than I will tell you about my experiance with your work.

Thanks a lot, so far! ;)

NOTE:

1.7.4b is running fine @ my device (AOKP - Unofficial) -> smooth & nice!

PERFECT WORK!! :D
[Galaxy Tab 10.1 Android Development] impulse101:
Anyone try running this on AOKP?

Edit: i see martini. Got it runnung
[Galaxy Tab 10.1 Android Development] jayceebee23:
Anyone can confirm skype video call works with this kernel when used with pershoot's 10/30 CM10 build? I've been trying earlier but all I can see is a black screen with audio still working though.
[Galaxy Tab 10.1 Android Development] bL33d:
So is the latest kernel for stock safe? Seen something about Mmc brick a few pages back.
[Galaxy Tab 10.1 Android Development] hanspampel:
It is safe, read the changelog in OP.;)
[Galaxy Tab 10.1 Android Development] AAccount:
Just a random fact: I actually planned to do the mmc_cap_erase patch in V1. (Back when it only had voodoo sound). I already found the patch and was ready to make the changes. However, the steep learning curve associated with just getting the kernel to compile right made me forget about the patch until much later.
[Galaxy Tab 10.1 Android Development] jayceebee23:
I can now confirm that skype video call does not work with the combination of CM10 10/30 build and A1 1.7.4b kernel. When I reflashed 10/30 build, skype video worked as expected. Hope you'll have the time to look at this AA. I'm willing to test if need be. No pressure though. School should always take precedence.
[Galaxy Tab 10.1 Android Development] AAccount:
I just tried using this skype mod http://xdaforums.com/showthread.php?t=1148708 and it works fine. The desktop i connected to was using the latest skype linux in fedora 17 x64. I did get the black screen but only for a second and then the video came. I always use that skpe mod to disable the very annoying startup sound.
[Galaxy Tab 10.1 Android Development] vibecatalin:
Has anyone used the tab for a long time overclocked at 1.6 Ghz? Mine currently is for a year now at 1.4, is it safe if I use it at 1.6?
[Galaxy Tab 10.1 Android Development] AAccount:
That's something you'll have to try for yourself. Just keep an eye on the temperature. I use current widget to do that. At 60% of the "box speed" I think it becomes a person to person case. You can also try 1.5GHz.

Just as a side note: the tablet is also very capable at 816MHz. I underclocked mine to 816MHz during a power outage to extend the battery life and it handled Angry Birds Bad Piggies just fine.

This kernel should be fine on the new CM10 nightly. I was so bored yesterday I actually had my laptop make the 11/09 nightly for me and the current 1.7.4b kernel works fine for me.
[Galaxy Tab 10.1 Android Development] jayceebee23:
Also downloaded the latest 1109 build but hasnt flashed it yet. Did you try skype video call with your 1.7.4b and pershoot's latest? I know there was a reply a couple of messages back bout using a modified skype. Not sure though if i should try that instead.
[Galaxy Tab 10.1 Android Development] pathuri97:
experience with CM10(10/30) build?

I tried on CM10(10/30 - JB 4.1.2 build) and I'm experiencing some lag in menus,swiping etc.

Also TAB won't boot if it is connected to power.

You have to disconnect the plug to boot.

Has anyone has similar experience?
[Galaxy Tab 10.1 Android Development] AAccount:
I did try the skype video call on MY 11/09 nightly. I just downloaded the pershoot device configuration files from his git and had my laptop compile a build yesterday evening which my laptop also called 11/09. I had no idea an official pershoot build would come out. I was just bored and wanted to see if I could apply the Galaxy S1 instructions to my tablet. Yes, it did work. I think the official one has to be nearly identical to the one I had my laptop make. I made

zero

changes to any of the configuration files or CM source code.

I know at one point mine wouldn't boot when connected to the power but I haven't seen that recently. I usually let my tablet charge overnight and boot it while I watch TV and eat breakfast with it still plugged in. In terms of lag, I think it does lag for a few seconds after boot since it's initializing everything but after those few seconds it should be very smooth.
[Galaxy Tab 10.1 Android Development] AAccount:
Hey everyone,

I compiled TWRP V2.3.1.1 for the wifi only tablet. I tried making a 3G but either adb wouldn't work or the recovery wouldn't boot. It's on the first post. Source is included so if somebody else knows how to make it work on 3G go ahead and do it. I've also compiled V2.3.1.1 for my Galaxy S1 but it's not posted. If anybody wants it, just say so.
[Galaxy Tab 10.1 Android Development] AudiTuner:
Hi AAccount,

I really appreciate you taking the time to maintain and update this kernel. Compiling TWRP v2.3.1.1 is a big help too. :)

Thanks again!
[Galaxy Tab 10.1 Android Development] AAccount:
Does anybody know what exactly the missing 279mb is doing? I got 279mb from 1000-721. The tablet shows 721mb total memory. As far as I know it has something to do with the graphics card? Has something to do with 720p recording, hd hardware video playback? **Hint hint, i'm not asking this for no reason... :cool: **
[Galaxy Tab 10.1 Android Development] Ostrich Egg:
Does this include Pershoot's tweaked interactive governor? I think he's made a lot of device specific tweaks to it. Would it even be helpful?
[Galaxy Tab 10.1 Android Development] AAccount:
Not yet. I totally forgot actually. I'm testing another change right now... :cool:

------------------------------------------------Edit----------------------------------------------------

I added the new interactive governor to the other change that I'm testing in V1.8 right now.

-------------------------------------------------Edit2------------------------------------------------------

Look at the screenshot.

If anybody knows where I'm pulling the extra 80MB of ram from then please say so. I'm assuming it's from the graphics card/camera. My SGS3 also has 1GB of ram but shows 832MB available for me. I figured the SGS3 has a better graphics card and certainly far superior camera and it can deal with a smaller graphics/camera reserve so the GT10.1 should be ok with it? If anybody can suggest tests to check for ill effects do suggest. I did try 720p recording, watching 720p video, playing Angry Birds Bad Piggies, GLBenchmark all to no ill effect so far. Still testing.
[Galaxy Tab 10.1 Android Development] Bigandrewgold:
does your twrp build include the eMMC bug fix
[Galaxy Tab 10.1 Android Development] AAccount:
That twrp comes with pershoot's latest kernel as of November 8. I think it does.
[Galaxy Tab 10.1 Android Development] logic5:
I found a bug in this kernel, wifi direct doesn't work .. or can't be discovered with other devices.
[Galaxy Tab 10.1 Android Development] CazeW:
Hard to tell where you're pulling it from unless you show what you're editing. :)
[Galaxy Tab 10.1 Android Development] AAccount:
The screenshot comes from the antutu system info. I did put up the whole screenshot but for some reason xda automatically shrinks it down and it gets hard to read. The point of the screenshot is to prove 801mb is possible.

I just want suggestions for how to test for unforseen side effects.

Sent from my GT-I9300
[Galaxy Tab 10.1 Android Development] logic5:
any word on the wifi direct bug !!
[Galaxy Tab 10.1 Android Development] AAccount:
No time to check yet. Still at school right now waiting for a lab :(. What rom are you on? Did it work before?

Sent from my GT-I9300
[Galaxy Tab 10.1 Android Development] CazeW:
I could see the screenshot just fine. What I meant was, unless I know what and where you're editing (the code), there's no way for me to say from where exactly you're taking the memory. But like you said it yourself, you're most likely taking it from the camera/GPU. To test it, you would probably need something that loads a big chunk of data to the memory allocated for the GPU to be able to see the difference. I guess you could try playing some 1080p videos but remember that the tab has always been picky on how H264 videos are encoded.
[Galaxy Tab 10.1 Android Development] AAccount:
Sorry, I misunderstood the question. The change is made in /arch/arm/mach-tegra/board-p4wifi.c or board-p4.c if you're using the 3G version. I edited this function with my changes in red:

void __init tegra_p3_reserve(void)
{
if (memblock_reserve(0x0, 4096) < 0)
pr_warn("Cannot reserve first 4K of memory for safety\n");
[COLOR="Red"] //I'm assuming the first 256MB chunk comes from the graphics card/camera memory
//It appears that all "math manipulation" must be done using the constants 256 16 8 1 in either addition/subtraction/multiplication combos
// The current change will free up 80MB (5*16) from the assumed graphics card/camera to main memory.[/COLOR]
tegra_reserve(SZ_256M[COLOR="Red"] - 5 * SZ_16M[/COLOR], SZ_8M + SZ_1M, SZ_16M);
tegra_ram_console_debug_reserve(SZ_1M);
}

-----------------------------------------------------------Added---------------------------------------------------------------------

Any insight on what the other reserves are for would be appreciated. I'm not sure what they go to so I haven't messed with them.

-----------------------------------------------------------Added-----------------------------------------------------------------------

Unfortunately I can't test wifi direct because by SGS3 I9300 doesn't have wifi direct in CM10 currently.
[Galaxy Tab 10.1 Android Development] jayceebee23:
Thanks for the update AA. Haven't tested 1109 build and a good thing I didn't. Pershoot just postes 1112 today. Probably will test there your new build. Hopefully skype mores off that build too. Cheers man. Appreciate you keeping this kernel up and running.
[Galaxy Tab 10.1 Android Development] logic5:
Hi,

I use stock 4.0.4 rooted, and if you flash yoda kernel the wifi direct works.. but your kernel is the best so I will wait for the fix ..

thank you for your hard work.
[Galaxy Tab 10.1 Android Development] AAccount:
Well thank you for the compliment but my kernel doesn't really support stock anymore. The last version that ran on stock was V1.7. However, there are almost no differences between V1.7 and V1.7.x. V1.7.2 V1.7.4b, V1.7.5 are mainly just compatibility fixes so you won't loose anything by running the older version for now. When V1.8 comes out with the increased system ram (801MB up from 721MB) I'm afraid it will have to be for CM10 only since too many changes were made to make the kernel CM10 compatible that making a stock and CM version would require a bit of creative reworking of my build script which I don't have time to do right now. Probably if it was still the summer holidays I would rework the build script (which is included in the sources) but with midterms, and lab reports I don't really have time to do that.
[Galaxy Tab 10.1 Android Development] CazeW:
Like you suspected, the memory you're lowering is the GPU memory (used for textures and video decode buffers). The other two values seems to be for two framebuffers.
[Galaxy Tab 10.1 Android Development] ren2008:
Maybe the first post should be Edited so we can read a notice that V1.7 is the last version compatible with stock ROM. The changelog is kinda confusing when you get to read it for the first time so i flashed 1.7.2 and 1.7.5 without knowing it wasnt fully working on stock.

Still V1.7 is amazing, Zero problems so far with toldo's deo zip aligned ROM. Thank You AA!
[Galaxy Tab 10.1 Android Development] AAccount:
I did put **check compatibility** in the title and it is written but ill make it more obvious in the first post with blue bold text or something that catches peoples's attention.

Sent from my GT-I9300
[Galaxy Tab 10.1 Android Development] AAccount:
So, do you think the proposed GPU memory shrinking is ok? I've had no problems running GLBenchmark, taping 720p, playing back that 45second 720p recording, playing Bad Piggies. I got the same bnechmark results on GLBenchmark before and after shrinking the GPU memory so I'm assuming there's no performance loss to the GPU. I thought I would give the new change a week's time to evaluate through everyday use.

I got the number 801MB from looking at my SGS3 which has 832MB available. I figured the SGS3 can get by with 168Mb reserve, the GT10.1 should be able to do 201Mb. If the other 2 reserves: 16Mb and 9Mb are frame buffers I'm assuming one frame buffer is for the main screen and the other is for HDMI out. I don't think I'll mess with those.
[Galaxy Tab 10.1 Android Development] zerong:
Is it compatible with AOKP JB rom ? i think yes like my aokp is based on cyanogen kernel 3.1 .... ?!?

[ROM] [JB] [P4--P4WIFI--P4VZW] 4.1.2 AOKP for the Galaxy Tab 10.1 with pershoot kernel 3.1 10 cyanogen .
[Galaxy Tab 10.1 Android Development] hanspampel:
Yes it works on AOKP.
[Galaxy Tab 10.1 Android Development] Ostrich Egg:
Since you're not supporting stock anymore, have you thought about using the CM10 kernel as your base instead of the Samsung kernel? Maybe I'm wrong (and I don't mean to step on any toes), but it seems like you'll automatically inherit a lot of Pershoot's good work by doing that.
[Galaxy Tab 10.1 Android Development] CazeW:
Unless you play games with very big textures or watch videos with very high bitrates, it shouldn't make a difference (other than having more free memory). That said, I don't know for sure what it would take to use all that 256MB.
[Galaxy Tab 10.1 Android Development] AAccount:
It's a good idea but then I'll have to either constantly sync in the new changes or do a rebase quite frequently. Both of those are a lot of work right now. I know this isn't the best policy, but right now I just copy in the changes that I can actually understand what exactly they do and also understand what benefits those changes bring.

And no worries about hurt feelings. I'm not that sensitive or easily offended. Actually, as a beginner I'm quite open to suggestions because I KNOW for a fact there's a lot I don't understand.
[Galaxy Tab 10.1 Android Development] satoto01:
Dear aacount thanks for this super kernel. Could you also be kind sharing your cm10 build so that we can have the same experience. I believe that would be the best combi.
[Galaxy Tab 10.1 Android Development] AAccount:
My cm10 build is out of date. I was just bored last thursday and wanted to see if i could do it. Pershoot has newer builds available.

Sent from my GT-I9300
[Galaxy Tab 10.1 Android Development] meanhacker:
can someone verify if veetle HD works with this kernel and this rom?

meaning when you press the HD icon in the app, does it FC or actually play in HD and great sound quality? thanks!
[Galaxy Tab 10.1 Android Development] androg421:
New TWRP

How does one flash this new version of TWRP on the Tab?
[Galaxy Tab 10.1 Android Development] pathuri97:
1.8 - Working fine on TAB 10.1

1.8 is working fine and got lot of RAM now.

Kudos to all the efforts of AACOUNT!!!:)
[Galaxy Tab 10.1 Android Development] zerong:
Is Aaccount 1.8 kernel CM10 and AOKP compatible ? I actually have triptosyll AOKP JB 4.1.2 rom and 1.7.5 kernel .