yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Android Development] pershoot:
how's 11/19 running?
[Galaxy Tab 10.1 Android Development] sag7392:
Battery life so far is outstanding

Smooth

Fast w/no lag (edit- OC'd to 1400 using interactive/noop)

Does a very good job with Adobe Flash in the native browser

No issues with WiFi or tethering

Cameras work...haven't tested recording

No FC's so far

No reboots

Sound is good, using Vodoo from the Play store

Edit- YouTube plays without issues

Paired with 11/19 Nightly

That's all I have to report right now...I hope this helps.
[Galaxy Tab 10.1 Android Development] twa_priv:
Running great - latest official 20121120 nightly + your 111912 kernel.

Thanks
[Galaxy Tab 10.1 Android Development] kashortiexda:
yes, working great

as I mentioned a page ago in this thread !

http://xdaforums.com/showthread.php?p=34393734

sent fron my 4.1.2 SGS 3
[Galaxy Tab 10.1 Android Development] decatf:
I haven't used CM since the Samsung 4.0.4 release. Root permission doesn't seem to be available for 3-4 minutes after booting up. Anything that tries to get root permissions just hangs for a while after the device has finished booting up. Then suddenly root becomes available and all the apps start running and I can see the super user toast messages popping up. Is this normal?

I am running cm-10-20121120-NIGHTLY-p4wifi.zip amd p4wifi-boot-111912.zip.
[Galaxy Tab 10.1 Android Development] pershoot:
This has nothing to do with this kernel.

You must explicitly allow root access in developer settings. Inquire with others in the cm10 thread for help on root.
[Galaxy Tab 10.1 Android Development] pershoot:
And/or check your superuser app.
[Galaxy Tab 10.1 Android Development] jazzespresso:
using file explorer, re-install superSU (delete from system/app folder), and re-install superSU, and give the right permission superSU.apk, reboot your tablet. once reboots, open superSU so it can update binaries, first run it may ask permissions for other apps, let's grant the permissions.

it no longer prompts permission, then again reboot your tablet. and see iif you still have issue.

---------- Post added at 01:12 PM ---------- Previous post was at 01:10 PM ----------

very good:good:
[Galaxy Tab 10.1 Android Development] pershoot:
11/19 has been merged in to mainline. will be in next nightly.
[Galaxy Tab 10.1 Android Development] jlokos:
The 11-19 kernel with the 11-19 CM10 running great on LTE version; keep up the great work.
[Galaxy Tab 10.1 Android Development] angiotell:
Can I install this kernel on jellybeanrom, v7?
[Galaxy Tab 10.1 Android Development] pershoot:
Did you read droidbasement?
[Galaxy Tab 10.1 Android Development] jazzespresso:
nice...so I don't need to worry to flash this kernel after the nightly ROM flash going forward, right?
[Galaxy Tab 10.1 Android Development] pershoot:
Correct.
[Galaxy Tab 10.1 Android Development] djmatt604:
Dude that's so awesome. Not only do we have a kill rom, now he's saving us time in setting us up! :) sweet.

Sent from my T989D bleeding CM10 inverted awesome
[Galaxy Tab 10.1 Android Development] zerong:
I will try to flash next nightly because i have draining battery issue since last flash, and i dont know why (1% hour), perhaps wifi setting?
[Galaxy Tab 10.1 Android Development] ole12:
Anyone here having problem with viewing YouTube app in HD?

Lags like crazy, can only view non HD clips.

I'm using latest CM10, and OC to 1.4.
[Galaxy Tab 10.1 Android Development] zerong:
No , perfect for me !
[Galaxy Tab 10.1 Android Development] aelsharawi:
Yester nightly has the old kernel
[Galaxy Tab 10.1 Android Development] notfaded1:
11/21 doesn't have pershoot's kernel yet?

We have to flash 11/19 kernel till next nightly after 11/21? Confirmed above...

Also what's the default number of background processes? You can set none, default, or 1-4 but what's the default or is it dependent on something?

Also I saw someone say they were changing I/O scheduler from cfq to noop... is this recommended with interactive governor? Why would u do this?

---------- Post added at 10:57 AM ---------- Previous post was at 10:41 AM ----------

Better Battery Stats

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

Chamonix's app helps figure out what is happening :^}
[Galaxy Tab 10.1 Android Development] sag7392:
That was me. I've been using pershoot's ROM/kernel since the beginning. In the early stages, he suggested using interactive because of it being developed. I wish I had the thread this was said in. Anyhow, I always decided to go with interactive because of that, testing, research, and what works best on my Tab (every device plays differently). I did some extensive research on I/O schedulers found here and around the web. I found that SIO (which isn't offered in this kernel) and noop do very well. Now I know that CFQ is set by default, but I prefer noop. I'm always open to different opinions, so if anyone sees something I don't see...please let me know.
[Galaxy Tab 10.1 Android Development] jazzespresso:
would be nice if you post a print screen how you all set up :)
[Galaxy Tab 10.1 Android Development] sag7392:
^^ This why I love Android and Android based operating systems...options.
[Galaxy Tab 10.1 Android Development] neonflx:
can i flash this kernel if Im using the latest TASK650 rom?

i been reading but cant seem to find the answer thanks
[Galaxy Tab 10.1 Android Development] ipnekgs:
No, this is only for CM10.
[Galaxy Tab 10.1 Android Development] jazzespresso:
what can I say, this is probably one of the most detail answer ever, very informative indeed.
[Galaxy Tab 10.1 Android Development] notfaded1:
pershoots new mainline 3.1.10 kernel rocks!

Thanks jazzespresso... it's definitely an area of interest to me. Imagine what pershoot deals with in some of these low level kernel level coding decisions... tiny changes can have drastic affect on entire function... much to his dismay I'm sure sometimes... :^}

Semper fidelis
[Galaxy Tab 10.1 Android Development] jazzespresso:
I always trying to make my galaxy tablet better. Considering this tablet is over 18 month old, and with 2.5 year old hardware specs (yes, quite outdated), what we are doing here is pushing the limits, and surely it is good enough for daily drive, and can take some small work, but it is still not up for heavy work if you ask me because of hardware. Yes it has Nvidia Tegra 2 dual core processor, but it was the first release of this kind processor, since then Nvidia did a lot of improvement with next releases. Developers, like pershoot, bringing JB ROM to our tablet, and it is so far the best JB ROM you can get our 18 month old galaxy tab 10.1. However, still it suffers when it comes to performance, that's probably what Samsung found out and decided to not release JB for galaxy tab 10.1. I remember when this first come out, it was the one of the fastest Android tablet on the market. Like every other technology, it eventually becomes absolute. And tablets are not like laptop or desktop to open it and throw extra RAM or better processors, so we are limited with software improvements, and see how much developer can improve it.

So far with Nightly CM10 and latest kernel from pershoot, our tablet is as good as it can get; with considering it is over 18 years old, and with 2.5 year old hardware specs. Needless to say, there are some budget tablets (range $150 to $200) out there that has better specs than our galaxy tablet, and performance is much better of course. Again, as pershoot outlined in one of his post, it all comes down to 2.5 year old hardware specs.
[Galaxy Tab 10.1 Android Development] kbluhm:
lol, 18 years, it sure feels like it, right?

Despite your accurate analysis of the processor's poor performance, which has been addressed countless times prior, I doubt that had much to do with their decision. Samsung is famously known for their lack of long term upgrade support. They typically release new devices with newer software in lieu of updating existing devices.

Were it not for pershoot's hard work I would undoubtedly own a Nexus 10 today. Don't get me wrong, I will own one eventually, but his work has kept me infinitely more patient and will save me $$$ in the long run... some of which will end up in his pocket. ;)
[Galaxy Tab 10.1 Android Development] ole12:
You are so god damn right.

With task previously up-to-date roms, and pershot fast kernels, there isn't any need for an device upgrade.

The difference between an stock tab 10.1 and CM10 or any rom with pershot kernel for that matter, is so huge.

I'm still wondering how the hell sammy would release an device with an UI so laggy out of the box.

It is useless without any modifications.
[Galaxy Tab 10.1 Android Development] jazzespresso:
heh heh heh...you guys know that I meant 18 moths:silly:

---------- Post added at 04:29 PM ---------- Previous post was at 04:14 PM ----------

I agree 100%, but again it still comes down to hardware specs, processors, RAM,.etc. Keep in mind that; now 4.2 up, and many apps, games are start utilizing for 4.2, and for faster processors. For example, most of gameloft games runs much better and smooth on my Nexus 7 then my galaxy tab 10.1. I have the same games and apps on my both Nexus 7 and Galaxy Tab 10.1, and you know there's big differences when it comes to performance. I know it is quite stupid to compare two tablets, but my point here is the app/games performances and they run better on newest devices.

Nexus 10 will be my next 10' tablet for sure, it is just I need 32GB, which is quite pricey for me ($499 + shipping + tax), I will wait and hope Google will cut the price (like they did for Nexus 7), and I don't think price cut for Nexus 10 going to happen anytime soon, so I am sticking with my Galaxy Tab 10.1 for now.
[Galaxy Tab 10.1 Android Development] daniel_fm:
I am not having as much deep sleep with this kernel + pershoot rom image. The tablet spends at 250mhz almost as much as deep sleeping and I have it to disabe wifi and all when it is not being used, I have no sim card in it either so no data usage, battery stats shows after the screen the inactive device and inactive tablet are the ones more consuming. Battery last hardly two days with little use while with jellybeanrom by toldo and a1 kernel it could last over 5,6 days even more with no use and wuth this is ckeary not the case.

As much as Im loving the performance here and persoots work, there`s always the will to improve so:

Is it a rom issue, a kernel issue, any tips, clues? Thanks in advance
[Galaxy Tab 10.1 Android Development] zerong:
parameters, battery, wifi, advanced wifi options : actif wifi in sleep : "NEVER" for me !

So disable all google synchronisation service ! now no more drain battery for me !
[Galaxy Tab 10.1 Android Development] mcmb03:
Damn, I didn't know my tablet was almost as old as I am! :P
[Galaxy Tab 10.1 Android Development] Leogp:
Im having the very same problem with my tab. Battery stats showed that my tab went from 99% to 14% in 2 days, while the screen was on for less than 40min....

I have a P7500, but never used a SIM card. I'm on the latest nightly so far, 26/11

As mentioned above, love the performance and really thanks Pershoot for the work, otherwise would prob still be on Honeycomb. Just dont understand why battery drains so quick, without even use it.
[Galaxy Tab 10.1 Android Development] mcmb03:
Correct me if I'm wrong, but could this simply be because our device wasn't made for jb?
[Galaxy Tab 10.1 Android Development] damngood98:
haven't touched my tab in 4 days since getting a nexus 10....tab is still at 54%. not seeing issues like this at all. likely you have an app causing problems. try using cpu spy or doing a full wipe.
[Galaxy Tab 10.1 Android Development] Leogp:
Did a full wipe and a factory reset couple for times already, still the same. What does cpu spy do, that will help me with this issue?

Thanks

Leo
[Galaxy Tab 10.1 Android Development] muzzy996:
I haven't used CPU Spy but if it's anything like Better Battery Stats the intent is to rank processes and applications in order of usage so that you can determine what's keeping the tablet awake.

One thing's for certain; if you completely format system and data and then install CM10 clean without installing any other applications the tab will deep sleep reliably. Its when you start loading up applications that the wakelocks start.

For me I keep some things disabled using Titanium Backup shortcuts on my desktop to freeze/defrost them. Things I disable include Google+, Google Talk, Google Maps. I do not have Facebook or any instant messaging apps but if those were things I used then they'd be on the list as well. Finally I keep location services turned off unless I intend to use it.
[Galaxy Tab 10.1 Android Development] jlokos:
CPU Spy provides data on your cpu state, not what apps or processes are running. It's helpful to show how your kernel is operating.
[Galaxy Tab 10.1 Android Development] muzzy996:
In that case perhaps Better Battery Stats is more useful in determining wakelock issues, though I don't know for sure. It gives you actual cpu times for applications/processes and wakelocks as well as wakeup calls per application from given events like since unplugged or since screen off etc. CPU state is included as a reporting option within BBS as well.
[Galaxy Tab 10.1 Android Development] kbluhm:
Unplugged mine about 9.5 hours ago after crawling out of bed. Just picked it up after it's been sitting all day doing nothing. Battery's strong at 98% :)
[Galaxy Tab 10.1 Android Development] notfaded1:
better battery stats xda edition...

Try this to see what's going on with you're 7500... Better battery stats-

http://xdaforums.com/showthread.php?t=1179809
[Galaxy Tab 10.1 Android Development] Leogp:
I'm actually using battery stats for a while now, and that's what shows me (attached). Any suggestions?
[Galaxy Tab 10.1 Android Development] tiny4579:
Here is my last_kmsg if you think it will help. I posted earlier where I think I had a sleep of death issue last night.
[Galaxy Tab 10.1 Android Development] G1_enthusiast:
i dont see how this is benefit to our tablet though as we dont use SD card...
[Galaxy Tab 10.1 Android Development] pershoot:
ya i set it to 1024 (from 128).

https://github.com/pershoot/galaxy-2636/commit/92c311d85be4da2979bd92d198ec34d501bd1eed
[Galaxy Tab 10.1 Android Development] zedomax:
80MFLOPS!

Thanks dude, my tab is running near 80MFLOPS from 50MFLOPS, keep em comin, I would one day like to see 2.8Ghz or even 3Ghz! :D

I took a video (as usual) while I did it:

[YOUTUBE]E2H4s3rsfRg[/YOUTUBE]
[Galaxy Tab 10.1 Android Development] G1_enthusiast:
lets get to 2.0 first lol
[Galaxy Tab 10.1 Android Development] katlimaal:
Pershoot

Where's the new refresh which you did on 06/29 12:30am est.

The last update on the below website I see is 06/23

http://droidbasement.com/db-blog/
[Galaxy Tab 10.1 Android Development] PhantomHacker:
Running smooth on the latest.
[Galaxy Tab 10.1 Android Development] G1_enthusiast:
no its not, it was pull down...he's doing further tweaking
[Galaxy Tab 10.1 Android Development] pershoot:
ive PM'd a few of you a test image.

the max mv is now 1.2 (it was 1.225).

please let me know if this is effected your previous max stable overclock.

please report back to me in pm.

thx.
[Galaxy Tab 10.1 Android Development] concept0:
last_kmsg for sleep of death from about 2 days ago...

Thanks for all your hard work on this!
[Galaxy Tab 10.1 Android Development] pershoot:
thx.

ive pm'd u a test image. pls thoroughly test and report back in pm.

thx.
[Galaxy Tab 10.1 Android Development] jm6001:
Pershoot ,

I tried to get the kmsg but the command was saying it didn't exist.. I tried the other command you posted and it worked.. here it is!

View attachment file.rar
[Galaxy Tab 10.1 Android Development] pershoot:
thx.

ill be rereleasing, and things should be much better.

please flash back to the stock kernel for now.
[Galaxy Tab 10.1 Android Development] LetsGoToWarr:
Hey per shoot any chance at a volume increase?
[Galaxy Tab 10.1 Android Development] pershoot:
i dunno as of yet. once i merge in the vodoo stuff, you may have more control over things.
[Galaxy Tab 10.1 Android Development] pershoot:
Testing is going good so far.

Will probly get something out tomorrow if all stays well.
[Galaxy Tab 10.1 Android Development] danikristijan:
10.1v Android 3.0.1

Is it also possible to oc this device? if not, getting android 3.1 and than oc?
[Galaxy Tab 10.1 Android Development] tonm156:
Had a freeze today. Here is last_kmsg.

I am using boot-cm_2636.4-oc-xtra-vfp_fp-062311.zip
[Galaxy Tab 10.1 Android Development] SellswordShev:
I think pershoot said he hasnt added 10.1v support yet, but its on his todo list
[Galaxy Tab 10.1 Android Development] Itaintrite:
I'm pretty sure he released a 10.1v version before but before the refreshes.
[Galaxy Tab 10.1 Android Development] GalaxyNinja:
Is your gps on? Just noticed that gps killed 30% battery today in my bag searching for a signal.
[Galaxy Tab 10.1 Android Development] Leogp:
Nope. Always leave it off for this reason. I'm really going nuts with this battery, nothing seems to make it last longer.
[Galaxy Tab 10.1 Android Development] ole12:
I have no idea how to understand a logcat.

But I went through it, and saw ALOT of connectivity / network / adress change lines.

Are you connected to wifi all time? It might be your router bombarding your tab.
[Galaxy Tab 10.1 Android Development] Leogp:
Yes, I never switch off my WiFi. I will do a test and switch off whenever i'm not using it, and check if there's any difference

thanks for the tip
[Galaxy Tab 10.1 Android Development] djden:
wifi

Ill check settings wifi and in the richt corner advanced.. wifi keeps in sleeptime i check never,and my battery is fine
[Galaxy Tab 10.1 Android Development] muzzy996:
I'm no expert in chasing down wakelocks and it is somewhat inappropriate to be addressing this here in this thread because it has little to do with the kernel but what I think you should be doing with better battery stats is drilling down through the various logs (not the logcat itself) and paying heed to the amount of usage or wakes the top ranked processes have.

As an example I did not freeze/disable maps or location services this afternoon on my tablet so on the alarms log in better battery stats I see 420 wakeups in the past 4 hours. A handful of maps related processes rank near the top of my partial wakelocks log as well. This tells me that disabling maps will have a great impact on battery life.

Pershoot my apologies for taking things a bit off topic.
[Galaxy Tab 10.1 Android Development] scaryshark:
I'm on the newest kernel and I had another lock at 450mhz. I don't have a pc to give any logcat or anything but ill try to outline what happened

Battery was full and I spent a whole lot of time ~6 hours catching up on Homeland :D

Anyway after that the battery was at about 9% at which point I put it away (still on but locked)

I come back, ~10 hours later when the battery is at 4d% and I plug it into my friend laptop at mtp to copy some songs over

After that I unplug it and after about 1min I realise its REALLY slow and I found d that the max frequency has changed to 450mhz (was at 1.4)

Now I stick it back to 1.4 and it's still VERY laggy I.e typing is laggy and homeland keeps freezing :( even after sticking it on performance

After a reboot everything is fine and snappy.
[Galaxy Tab 10.1 Android Development] pershoot:
no logs, nothing can be done for you.

this kernel is already in the latest nightlies. update your build.
[Galaxy Tab 10.1 Android Development] scaryshark:
I know sorry about that! :D

What log do you need if it happens again. Last kmsg?
[Galaxy Tab 10.1 Android Development] Leogp:
Did that already. Still the same for me.

---------- Post added at 12:48 PM ---------- Previous post was at 12:45 PM ----------

I did not mean to take the conversation out of topic, simply stated my tab functionality with the kernel.

neither I am criticising Pershoot's work and effort as without it we would all be on Honeycomb still. I'm just helping reporting some issues that could be related to the kernel, or not.

Thanks for your tips above.
[Galaxy Tab 10.1 Android Development] Serpentene:
YOU WANT HD VIDEO? YOU WANT the ULTIMATE p4VZW CM10????

What needs to be applied for the GREATEST GT 10.1 JB CYANOGENMOD 10 EXPERIENCE is as follows:

1) Pershoot 11/19 kernel applied.

2) The last CM10 Nightly as of (12/8/12)..the last update smoothing out the CM10 boot logo...(this is the unofficial "stable" build for VZW IMHO)

3) CM10 settings: CPU PROCESSOR / Governor INTERACTIVE (kernel is optimal @ this setting choice.)

MIN speed 456MHZ (analysis of optimum idle wait state)

MAX speed 1400MHZ (1200..conservative battery +gain. -performance loss)

I/O SCHEDULER : DEADLINE

MEMORY MANAGEMENT: zRAM 26%

check allow purging of assets

check Kernel same page merging

16 bit transparency OFF

SURFACE IMPROVEMENT DITHERING DISABLE

4) ZEPPELIN ROX V6 SUPERCHARGER SCRIPT BUNDLE:

V6 SUPERCHARGER (Requires a patched Services.jar...recommend using ZeppelinRox script automation sequence..)

LET the SCRIPT SET OOM values using auto calculated algorithm..

set Launcher to ROCK HARD

install ALL EXTRAS including ALL TWEAKS

KERNELIZER

3G TURBO WIFI AFTERBURNER (must use TIWLAN.ini (add to ETC/WIFI)

WIFI script settings ..set to #4 (conservative battery gain) or #5 Experimental (full power radio)..set AFTERBURNERS (TIWLAN.ini required) ON

**NOTHING can compete with these performance tweaks...Performance APPS are a WASTE of download time..storage space..and consume resources!!**

SD CARD READ SET 2MB..(will auto install using the 3G Bundle Enhancement options.)

TouchscreenTune app install

set sensitivity to 40 for finger swiping...set to 15 for light touch stylus

SET the AIRPLANE MODE ON!!!!

Leave it on..

USE Manual override wifi radio and/or Mobile radio andor Bluetooth

Set wifi scanning off if using well known SSID..

A BIG SHOUT and THANK YOU to the Cyanogenmod team, Pershoot, ZeppelinRox.

Necromancers of the Samsung GALAXY TAB!!!!...I am in utter AWE of your programming Wizardry!!!!

You're WELCOME.
[Galaxy Tab 10.1 Android Development] rihui:
the latest cm10 build (22/1) is awesome! thanks pershoot
[Galaxy Tab 10.1 Android Development] k1mu:
Pershoot,

I have a patch that I'd like you to consider for your kernel builds.

There's a problem with the touchscreen chip in the Galaxy Tab where a firmware update fails. This leaves the chip in firmware update mode, meaning that it's not responding to screen updates. When this happens, you can recover from the problem by restarting the firmware update.

It's a simple fix to the mxt1386 driver - patch is available from http://www.rickmurphy.net/atmel_mxt1386_diff.txt

There's unfortunately a very easy way to get the chip broken - a simple

# find /sys -exec grep foo {} \;

command triggers the firmware update to start, then almost right away powers off the tablet. When you power it back on, the touchscreen is dead. Samsung claims that fixing this requires the main board to be replaced.

Would you please consider including this change in your kernel builds for the Gtab? It's a harmless change that could allow people to fix their broken tablets easily. Thanks.
[Galaxy Tab 10.1 Android Development] pershoot:
Are you certain this is reproducible on the touchscreen driver/setup/fw I include in cm10/10.1?

I've done finds before without issue.

Please validate if the issue is still present with the upgraded driver set.

Thx.
[Galaxy Tab 10.1 Android Development] pershoot:
please check pm.
[Galaxy Tab 10.1 Android Development] pershoot:
correct.

no 10.1v support yet. will work with someone with the actual device to discern why there is a no boot situation.
[Galaxy Tab 10.1 Android Development] pershoot:
thx. thats the preview, so there were issues there.

a rereleased version will be put up soonish.

should sort most of all these issues for the masses.
[Galaxy Tab 10.1 Android Development] JeffR714:
Guys don't get mad but I cant find the update (stock kernel) I'm somehow missing the file I just want to have the kernel just in case. Anyone know which post the stock kernel is in?