yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Android Development] Kyle005:
This kernal seems to be working great for me, im keeping it at 1.2 GHz though because it froze at 1.4 while trying to watch 720p on youtube in the browser.
[Galaxy Tab 10.1 Android Development] pershoot:
ya will get back to you.

will be on vaca in a few days, but will followup with you in the folowing weekend where we can sit down and work on it.
[Galaxy Tab 10.1 Android Development] pershoot:
yea your particular device needs more volts @ 1.4, then im willing to give, at this stage.

1.2 is good. 200mhz, you probably won't notice.
[Galaxy Tab 10.1 Android Development] tmaurice:
Have been running at 1.4 since release of updated kernel last night. No freezes, excellent bench results, no heat issues, nice and smooth. Wifi is strong, BT working for both external keyboard and mouse. Still testing battery life. Only unrelated problem I have with my unit is the buffering issue with YouTube. Keep up the excellent work pershoot!! It's greatly appreciated.
[Galaxy Tab 10.1 Android Development] Grommish:
I am trying to load the Dnla.apk and .odex file onto the table and getting the

Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY]

Any have any idea WHICH lib is missing?
[Galaxy Tab 10.1 Android Development] pershoot:
no idea. not familiar with dlna.apk.
[Galaxy Tab 10.1 Android Development] Grommish:
Was worth a shot. its a samsung app for 2.2, but wanted to try. Streaming movies over my network on the 10in would be fantastic.
[Galaxy Tab 10.1 Android Development] skrowl:
My tablet is dead after a day on the second kernel release from yesterday.

Won't turn on even after an hour on the charger.

The voltage might be to high or something. Use with caution!
[Galaxy Tab 10.1 Android Development] pershoot:
the voltage is definitely within predefined limits (it is only increased .075 more then what it was previous, to one of the nominal system core). not any higher.

every other device is using much much higher.

could be coincidence.

i'll decrease it further if you feel this was a result.

take it off the charger and let it sit. there is no way it wont turn on (unless the device was seriously overheating; which i doubt).

then hold power (dont let go). you should see something.
[Galaxy Tab 10.1 Android Development] mannequin:
youtube videos above 480 in the browser while mostly smooth with an occasional chop are always slightly out of sync. if you have an example of a 720 youtube video that's actually in sync, please provide a link. hulu is choppy no matter what. it's not much of a difference at 1.4Ghz which is quite discouraging.
[Galaxy Tab 10.1 Android Development] ericc191:
pershoot, is Tegra2 really picky about being OCed? My G2, for example can go well past 1.4GHz. Probably because it is only one core to deal with? This makes me wonder how the quadcore chips will react. Good results, I hope!
[Galaxy Tab 10.1 Android Development] SellswordShev:
Ah ok, I haven't used youtube in a browser (will do, have this running at 1.4 now), was just using the youtube app. By out of sync do you mean the audio is off sync ?
[Galaxy Tab 10.1 Android Development] pershoot:
not really. goes pretty high actually.

my gtab (viewsonic) was pulling 1.6. t8 (malata) i never tested the limits. this tab im sure can do 1.6 as well (with enough voltage).
[Galaxy Tab 10.1 Android Development] pershoot:
it also could be dropping to APX mode. plug it in to usb and validate that.
[Galaxy Tab 10.1 Android Development] pershoot:
ya, the dim issue is known.

it should be further reduced with what is currently committed. i myself can no longer reproduce it. this is after 40+ hours of runtime (used to happen after ~15h).

if it does happen, there are 2 ways out:

1. plug in usb

2. hit power, screen will dim, wait for it to go blank, power, and unlock.

This is an old issue actually. It has happened on HC to various people/tabs, but has become more exarcibated in ICS. but currently, it should be down to a minimum from my testing equipment and others that are testing.
[Galaxy Tab 10.1 Android Development] twa_priv:
I'd love to build it from source ... if I knew how to (besides checking out your repo).

I looked at the README but already got lost on the make config step...
[Galaxy Tab 10.1 Android Development] pershoot:
git clone git://github.com/pershoot/galaxy-2636 -b ics galaxy-2636_ics

you can use this toolchain, http://droidbasement.com/androidTO/arm-2010.09.tar.gz or arm-eabi-4.4.3 from AOSP

if using codesourcery's:

export CCOMPILER=PATH/TO/TOOLCHAIN/bin/arm-none-eabi-

export PATH=$PATH:PATH/TO/TOOLCHAIN/bin

cd galaxy-2636_ics

make ARCH=arm CROSS_COMPILE=$CCOMPILER pershoot_samsung_p4wifi-ics_defconfig (for gt-7510)

make ARCH=arm CROSS_COMPILE=$CCOMPILER

copy arch/arm/boot/zImage in to the anykernel zip under the kernel folder (we're using gt-p7510 in this example) zip (you can find this at droidbasement for galaxy tab 10.1)

copy drivers/net/wireless/bcmdhd/dhd.ko to anykernel zip under /system/lib/modules/

sign the .zip (you can use stericon's tool here: http://droidbasement.com/androidTO/signing.zip for windows; for linux you can sign via x509)

transfer to tab and flash in CWM.

Note: You can specify -j[NUM] for the number of concurrent threads to run, to make. I use 12 (-j12) for a 6 core development base.
[Galaxy Tab 10.1 Android Development] twa_priv:
Thanks for the instructions perhoot. It is very much appreciated.

I can't seem to find a donate link for you...
[Galaxy Tab 10.1 Android Development] SergioBigred:
I had the same issue with my second 7500.

I tried also to install ICS Kang guessing when to press the keys in CWM but the issue was still there.

Problem is you need Pershoot CWM to install ICS, Overcome don't allow that.

So I had to Odin back to HC 3.2, then I installed Overcome Kernel, Bindroid Rom and updated to latest Pershoot kernel.

I don't have issues with CWM but now during loading of Rom I have flicker that disappear during a screen off/on. (not big issue).

Anyway all solution are for 7510 and not for 7500, anyone can help?

Pershoot can I provide you more info about my HW (two Italians 7500, the oldest one didn't have any problem).

Thanks!
[Galaxy Tab 10.1 Android Development] twa_priv:
Cool, the kernel build and modifying the anykernel zip worked like a charm. Running my own compiled kernel now :) Thanks again pershoot.

One last question - can the resulting arch/arm/boot/zImage just be copied to android_device_samsung_p4wifi/kernel and used as the prebuilt kernel in the device repo?
[Galaxy Tab 10.1 Android Development] pershoot:
Tw priv,

Correct. When in line kernel building is brought in, then the kernel binary will be used as a fallback.

Sergio,

To rid the rolling screen permanently youll need to flash a bootloader and let the rom set csc from a supported region (that this kernel supports). To do this, you can odin over 7510 rom (found in general section in the rolling screen fix thread), then come back up to your rom.
[Galaxy Tab 10.1 Android Development] MapleSyrup:
If you're building the ROM from source, you can build the kernel at the same time: Integrated kernel building

Add the kernel repo from pershoot to your .repo/manifests/default.xml

<project path="kernel/samsung/p4wifi" name="pershoot/galaxy-2636" />

Change the content of device/samsung/p4wifi/cm.dependencies to:

[
{
"repository": "galaxy-2636",
"target_path": "kernel/samsung/p4wifi",
"branch": "ics"
}
]

Add this at the end of device/samsung/p4wifi/BoardConfig.mk

TARGET_KERNEL_CONFIG := pershoot_samsung_p4wifi-ics_defconfig

And build like you always do (repo sync, . build/envsetup.sh, brunch p4wifi)

---

For linux users with a p4wifi tablet (git, java, wget, zip, and unzip are required), here is a very crude bash script (for example, if something goes wrong with the downloads, the script will continue, so check the wget output) to build the kernel (from nothing to flashable zip) following pershoot's instructions.

Just change the workdir variable to the desired directory and make the script executable:

chmod +x buildkernel.sh

buildkernel.sh
[Galaxy Tab 10.1 Android Development] twa_priv:
Thanks, I was about to do that :)

But what about the dhd.ko, which is also part of the kernel build? Shouldn't this be taken care of in BoardConfig.mk as well somehow and moved to system/lib/modules?

Maybe by doing something like that:

PRODUCT_COPY_FILES += kernel/samsung/p4wifi/drivers/net/wireless/bcmdhd/dhd.ko:/system/lib/modules/dhd.ko
[Galaxy Tab 10.1 Android Development] MapleSyrup:
dhd.ko is in out/target/product/p4wifi/system/lib/modules (it builds with everything else), unless I'm doing something wrong, but I don't think so.
[Galaxy Tab 10.1 Android Development] twa_priv:
Well ... I think it is taken as a prebuilt from the device tree: android_device_samsung_p4wifi/modules/dhd.ko
[Galaxy Tab 10.1 Android Development] MapleSyrup:
No, when the kernel is compiled along with the ROM, dhd.ko is compiled instead of being pull from the prebuilt. Try it and you will see.
[Galaxy Tab 10.1 Android Development] pershoot:
galaxy-2636 ics is now in CM repo as android_kernel_samsung_p4

ill get the in-line kernel stuff going...
[Galaxy Tab 10.1 Android Development] twa_priv:
You're absolutely correct, dhd.ko is taken from the integrated kernel build. I guess one has to do-it-yourself and then see what's going on during the build.
[Galaxy Tab 10.1 Android Development] kaiserlein:
@pershoot: what kind of logs can I provide for this? The last thing shown in the attached logcat is that the vpn connection got established.
[Galaxy Tab 10.1 Android Development] katestar:
Please pershoot correct me if I am wrong, but I read somthing in the past that said that the lag asociated with all tegra 2 device is due to the bus speeds, not the gpu or cpu clock speeds by them selfs. I have been reading up on Clocking and overvolting the BUS speeds in the nexus s & galaxy s forums, and aparently it can dramticly increase performance on the nexus s & galaxy s. We may have a very diffrent SOC, but have you tried overclocking the bus please? From what I have researched, it can allow uws to have dramticly better speeds & make overlcoking the cpu more stable & whilst making it faster. All for very little voltage increase. If I have understood what I have read, overclocking the bus could have a larger impact than overlcoking the cpu. I hope you don't mind me asking about this, I searched the thread and found no mention of overlclocking the bus. :)

One of the sources I used to research is here: http://xdaforums.com/showthread.php?t=1419274
[Galaxy Tab 10.1 Android Development] pershoot:
There is no bus, per se, that can be overclocked, to my knowledge. Nexus s is an entirely different soc (omap vs tegra2).
[Galaxy Tab 10.1 Android Development] pershoot:
Kaiser, the only way i can take a bug report is if you put your tab in a state which is controlled. The rom is in a constant state of flux (its alpha).

I myself cant even do vpn over wifi. Many others cant either. Theres a big thread on code.google regarding it. Not sure how you're even able to do that. Over 3g it works without issue. That's confirmed for a while now.

Hop on gtalk (pm me) and we can go through it, but not really promising anything since theres current big issues regarding vpn operability on ics.
[Galaxy Tab 10.1 Android Development] SergioBigred:
Pershoot,

thanks for the feedback.

Are you confirming I can Odin a 7510 rom over my 7500 with no issue and then install your cwm and an ics ROM with no risk of bricking it?

Thx
[Galaxy Tab 10.1 Android Development] pershoot:
Should be ok. Isimobile has done this (he has a 7500).

Check the thread in QA for his feedback and/or reach out to him for detailed steps.
[Galaxy Tab 10.1 Android Development] goldlocke:
Thx pershoot for your Kernel work! Very much appreciated.

Could you plz elaborate on the May 3rd Kernel on your blog? Especially about the touchscren driver changes?

Thx alot.
[Galaxy Tab 10.1 Android Development] pershoot:
Just fully sync'ing from the driver located in gs2's ics kernel source, which should remediate many if not most of all the issues that were experienced.
[Galaxy Tab 10.1 Android Development] twa_priv:
Hmmm ... I know some people have reported the same issue (spread across a few other ICS threads I believe) ... came home and my tab was stuck on the CM boot animation.

It sat there probably a few hours because the tab felt pretty warm and the battery was almost empty.

This is the second time this happened to me - the first time a few weeks back when I started running your CM9 builds.

pershoot - how would I go to debug this in case it happens again. I tried to use adb to get some logs but adb didn't see the tab.

I'm running my own build (including kernel) based on yesterday's sources (CM + your probably now retired galaxy-2636 repo) - but I don't think this should matter.

Thanks
[Galaxy Tab 10.1 Android Development] pershoot:
you most likely have corruption. check dmesg.. do you see lot of errors on mmcblk? check last_kmsg, what does it indicate?

you should odin back to 3.2 (the whole tab is now wiped), then come back up to cm.

it happens when you flash this thing a zillion times, ha. it was much worst in honeycomb.

ive never experienced any issue on cm9, but in HC alot.
[Galaxy Tab 10.1 Android Development] pershoot:
you should post a log for me to see before you do the flash back/forward. i have yet to see this issue in all of its glory (no one has posted a log for me at all that I can see).

logcat of it looping, dmesg during that time, and last_kmsg.

thx.
[Galaxy Tab 10.1 Android Development] twa_priv:
Attached the last_kmsg and the current (after restart) kmsg, dmesg and logcat.

I can't see any last_kmsg log entries related to mmcblk. But there seems to be quite a lot of interesting other messages in there (not that I know what they mean:).

Also, since I have odin'ed back to 3.2 maybe about a week ago (after flashing your boot.tar.md5) to get rid at the triangle at boot, I'm going to wait a little and see if this issue happens again.

And lastly - sorry for bringing this up again:

I got the attached logs by changing to root in an adb shell and did something like "cat /proc/last_kmsg > /sdcard/last_kmsg.txt".

After that I connected my tab to my pc but these files weren't shown in explorer. I needed to reboot the tab in order to see them on the pc. Any idea why this would happen?

Thanks for your help

Edit:

I tried using adb while the tab was looping on the CM boot animation but adb didn't recognize my tab.
[Galaxy Tab 10.1 Android Development] pershoot:
Ill look at your stuff a bit later.
[Galaxy Tab 10.1 Android Development] pershoot:
The dim issue came back for me after being up for 92hours (used to be 15 before)

Not perfect but shouldn't impact the majority of users. Ill keep digging in to it.

Note when this happens wifi will be frozen. Just hit power (it will dim). Let screen turn off. Turn back on (mxt will recalibrate). You can unlock now and wifi will reset, turn back on and reconnect.
[Galaxy Tab 10.1 Android Development] SlakWReX:
Can I know what the updates are for. There are is change log.
[Galaxy Tab 10.1 Android Development] pershoot:
droidbasement.com

github.com/pershoot
[Galaxy Tab 10.1 Android Development] RustyNailz:
Just encountered another instance of the screen becoming unresponsive on the latest version of the kernel. I was able to plug in usb and capture the dmesg log.

Had to long press the On/Off switch to regain control...
[Galaxy Tab 10.1 Android Development] vibecatalin:
So this last version of kernel is only for ICS Roms only. Am I right?
[Galaxy Tab 10.1 Android Development] pershoot:
Only ics from this point.

Last hc was 01/09, for 3.2
[Galaxy Tab 10.1 Android Development] twa_priv:
hey pershoot,

Just had another incident...

First my lockscreen became unresponsive (didn't accept any input) and while I tried to get some logs the tab rebooted and ended up sitting at the bootanimation again.

This time however, I was able to use adb to collect some logs. Attaching it here in case they might be helpful.

Thanks
[Galaxy Tab 10.1 Android Development] pershoot:
Im changing things around this wknd which should make this phantom bootloop situation a bit better.

The lockscreen dim issue will probly be there (as it has been since hc). Still need to investigate that and try and get it near perfection.
[Galaxy Tab 10.1 Android Development] goldlocke:
I got no issues at all with the may 3rd kernel so far . Touchscreen performance almost on par with tuning app.
[Galaxy Tab 10.1 Android Development] katestar:
I read that you said you had tried to overclock the gpu in the past, may I ask if any progress has been made as the comment was a very long time ago please? I have been reading up on gpu overclocking and apparently most tegra 2 t20's gpu's can be oc'd to 384mhz and quite a few can get to 512mhz (which sounds far too good to be true) As playing decent games on the gtab is like hitting your head of a wall, everything just laggs a little bit. If you want to test gpu overclocking, I would be more than happy to test for you, to see if it actually increase frame rate, as your tab may not be able to overclock gpu but someone else can. To choose GPU clock speed, maybe you could use EXTweeks app for the interface, or teraks OC. Gpu's are starting to get more, and more important and having a faster gpu would probably be better than oc'ing cpu by any amount. I really don't want to spend £400+ (That I could never afford anymore, double dip recession in the UK has hit me hard) on a new tab to play games at a higher fps, as the cpu and CM9 (thank you by the way) make my tab more than fast enough. I would be more than happy to test, if you would like :)

Edit: I would never normally ask for gpu overclocking on phones for battery reasons, but as your tab has a great battery life, I am not so bothered about battery anymore, I actually underclock my s2 Mali-400 MP from 267mhz to 200mhz even though it can be oc'd 400mhz to show that I am not an overcloing junky, and I only would like gpu overclocking on our tab for purely practical reasons, I don't care about benchmark result :)
[Galaxy Tab 10.1 Android Development] pershoot:
feel free to pull my sources and play.
[Galaxy Tab 10.1 Android Development] katestar:
I really wish I had the skills to change Gpu clock speed, but I'm afraid I don't. I have tried to find the relevant information without much success. I would love to be able to compile my own kernel with oc'ing to 1.5ghz (default set at 1.2ghz though) with gpu overclocking capabilities, all of which could be controlled with a single app interface, but I am just not good enough at all. I am afraid that by the time I have the skills to do it, no one will even own the tab anymore. I am learning about kernel development, a friend is giving me his galaxy s in a 4 months, which I plan to learn to develop on, so when I am learning I wouldn't break my tab. That's why I was asking you with the overclocking of the gpu as I just am not good enough at kernel development to do anything apart from compiling a kernel from source, and making some very, very basic changes, sorry to have asked about it I know there is much more important things to be done. I would just love to play decent games on the tab, and with decent hardware acceleration in ice, maybe oc'ing the gpu would have made the tab a couple of fps smoother. Anyway, thank you :)
[Galaxy Tab 10.1 Android Development] danielsf:
Same here, I wish I had the skills too, but I don't. I would love to try to overclock the Gpu in our dear old tab. I just wouldn't know where to start :)

Edit: I thought a direct quote from the famous movie 'Star Wars A new hope' was fitting, "Pershoot you're my only hope" :D

Edit 2: Sorry pershoot, I don't want to sound unappreciative, thank you so much for all your work on this, it really does mean a lot :)
[Galaxy Tab 10.1 Android Development] kehlan:
Why does the DB blog say not to use the 05/03 kernel? I understand that it's "for development," but nothing specifies if it's actually safe for end-users.

I'm going to download it but I'll save the install until somebody can confirm this.
[Galaxy Tab 10.1 Android Development] pershoot:
because the rom contains the current development kernel already. do not flash 0503 over snapshot 0508. you will break stuff.
[Galaxy Tab 10.1 Android Development] kehlan:
Holy **** that was a fast reply, I was about to edit my last post. I noticed that 05/08 was out right after I posted that, my bad. Thanks though, I'll just use 05/08.
[Galaxy Tab 10.1 Android Development] kehlan:
Attempting to flash 0508 gives me a "Status 7" errror. Bad download? It took forever to download, too...

Damn.

EDIT: I started the download again and it's going about (literally) 5x faster than it was before. I'll report back if I have further issues.

EDIT 2: I downloaded it again and still get the same error.

EDIT 3: Forgive my persistence, but I'm just wondering what I can do to get this kernel running. I'm sure it would please me more than the stock kernel in AOKP 5.2.
[Galaxy Tab 10.1 Android Development] Duvel999:
use the overcome 2.3.1 rom for p7500.

tried to flash this kernel by cwm recovery..

got stuck in a bootloop..

flashed the rom again.

what am I doing wrong?

(which one do I need from the download page of p7500?)

(I used the first one)

why got the bootloop?

:cool:
[Galaxy Tab 10.1 Android Development] sendan:
It sounds like you're on a Honeycomb ROM? Everything is labeled very well on droidbasement, just make sure you're not flashing an ICS kernel.
[Galaxy Tab 10.1 Android Development] real77055:
can you upload your latest kernels so we can download ?? and try with different ics roms?
[Galaxy Tab 10.1 Android Development] pershoot:
They will not be compatible with anything else (other then what I'm providing). That is why I'm rolling up roms for testing while I wrap up and work towards getting this in to cm mainline.
[Galaxy Tab 10.1 Android Development] itrice:
I can not find the version of pershoot kernel for P7500 rom overcome to enable usb charging, can you help me?

thanks
[Galaxy Tab 10.1 Android Development] Duvel999:
I have the p7500 (wifi&3G)

could you point me to the right/good kernel?

* do I need a full wipe etc for it?

* takes it a long time to boot?

* I believe I used the right one of 12/09/2012.. (p7500)

I only have to flash it.. need no PC?

I´m used to flashtool etc for my phone etc.
[Galaxy Tab 10.1 Android Development] voncrane:
Hi, follow the steps listed out here.

---------- Post added at 09:32 PM ---------- Previous post was at 09:28 PM ----------

Here u go... 10.1 3G, Touchwiz UX (HC 3.2 (stock); GT-P7500):

Just reboot to recovery and flash...
[Galaxy Tab 10.1 Android Development] Penguin_be:
Anyway to make it support EU tabs running on HC? Is this pure a PAL/NTSC problem?

thx
[Galaxy Tab 10.1 Android Development] MapleSyrup:
Pershoot, if I want to keep building your kernel with all the latest experimental modifications, should I keep using galaxy-2636 or are you going to switch completely to android_device_samsung_p4-common (in your repos, not cyanogen's)
[Galaxy Tab 10.1 Android Development] jiri.hlavacek:
Problem with WIFI connection after kernel flash

I have (or better to say I had before) GT-P7500 (XXLA1) 16GB with latest official HC3.2 firmware

I installed su_busybox_misc-sam_tab_10.1-061611.zip & boot-cm_2636.4_p4_ux_hc32-oc-xtra-vfpv3-d16_fp-010912.zip

via CWM 5.5.0.4

After that, WIFI cannot connect to any WIFI AP (3 different routers in my home and company).

It always stop at Getting IP address and start searching WIFI AP's again.

Before kernel flash it was working.

3G is working and I have no problem with internet or network connection thru internal modem.

I do not want to use ICS, just need HC3.2 and OC to 1.2 or 1.4 GHz (I don't want ot install kernel for ICS with missing functionality/camera bugs).

Is there kernel which does nto have this problem?

I made Dalvik cache wiping & uninstalled Callmeter 3G & Watchdog 3G . Still problem with WIFI, 3G modem still working.

Any idea what's wrong

UPDATE:

I replaced kernel back to stock by writing boot.img and now is WIFI working again.

dd if=/mnt/sdcard/boot.img of=/dev/block/mmcblk0p3

Maybe problem was with dhd.ko kernel modul on this EU version of tablet.