yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Android Development] Entropy512:
I think the problem is some people outside of the US are unable to download it to their devices - not available on market for whatever reason (see some of the responses to posts).

BTW, great work so far with the rework. My unlock problems are fixed (most likely by that touchscreen timeout commit) - I have a guess why they were worse with my own kernels, I will have to investigate further - probably the timeout was more likely to hit with conservative governor. I haven't synced and built your latest tree, but your release is great. Compared to 8/9:

Unlock issues still fixed

WiFi "wake up braindead" issues are still gone

Inability for the device to wake itself up (alarms, calendar, emails, etc) is now gone

It's great!

I see you've also got a fix in for CurrentWidget - I was going to start looking into that myself. However, voltage reporting in CW seems to still be broken (Edit: batt_vol seems to be reporting the value in millivolts fine... CW may just be misdisplaying.). I think I've found my weekend project...

Also - do you know if there's a map for the various ADC channels of adc_get_value() used by check_samsung_charger() of board-p4.c somewhere? If there are separate ADC channels for USB D+ and D-, then it should be possible to allow charging from unmodified iPad chargers.
[Galaxy Tab 10.1 Android Development] pershoot:
done

....
[Galaxy Tab 10.1 Android Development] pershoot:
im unsure at the current moment. my brain is foggy currently with a re-re-work against 'master', but i'll look when i get near those files.

pls remind me if i forget.
[Galaxy Tab 10.1 Android Development] FillTheVoid:
I love it! Thanks for dropping your knowledge on us pershoot!
[Galaxy Tab 10.1 Android Development] pershoot:
i tried this. made things worst. leaving it in.
[Galaxy Tab 10.1 Android Development] pershoot:
its ok. ill knock -5 away from default level, if this will help things for those that feel this is an annoyance.
[Galaxy Tab 10.1 Android Development] wlighter:
Some things to report here (jst my 2 cents):

I've been checking the power usage on this kernel (pershoots latest ux) vs starburst stock kernel (2.6.36.3 se.infra@SEP-52 #1)

The later kernel is really good in power saving on idle with screen off. In the course of 2 hours, battery usage is 1%. Battery usage decreasing slowing from 68mA - 31mA

Pershoots kernel stays around constant 66mA +/- which translate about 1% per hour
[Galaxy Tab 10.1 Android Development] pershoot:
depends on what you use in the BG.

i get 2-3% drop in 8 hours idle.

battery life is always subjective.

you cannot extrapolate that kind of data over the course of 2 hours. it takes 2-3 days of different useage patterns, and taking in to account android useage in and of itself.
[Galaxy Tab 10.1 Android Development] wlighter:
wow~ that is excellent. anyway i didnt install anything extra except for battery monitor widget. its a fresh install for the rom. may i ask what rom you are using? i see there is many background services that i may not need. i'm still looking around which is safe to terminate.
[Galaxy Tab 10.1 Android Development] pershoot:
i use the stock UX rom.

use autostarts to disable startup of certain apps (it wont prevent them from relaunching themselved tho). phone related, samsung account, the media apps, etc., etc.

turn off certain syncs if you dont need them.

get rid of the battery widget monitor. you dont need it, and it will eat cycles.

keep an eye on android.process.media. it can eat cpu cycles. system_server should be ok, but keep an eye on that too.

ill write a daemon to watch it one of these days, so you dont have to stick a .nomedia file in place.
[Galaxy Tab 10.1 Android Development] wlighter:
Thanks pershoot for that usefull info
[Galaxy Tab 10.1 Android Development] pershoot:
pls notify me immediately, should any battery issues creep back up, and/or other oddities.

thx.
[Galaxy Tab 10.1 Android Development] Flashmaniac:
Sorry if this question has been asked before but, is that kernel also working for P7500 Devices with Android 3.1?

I am confused because there is no sourcecode available for the 3.1 Kernel :confused:
[Galaxy Tab 10.1 Android Development] ivarson_swe:
Unable to boot with your latest P7500 kernel. Restored your previous and all okay.

Edit: ether it didn't run on broodcomb or I just shouldn't flash from rom manager anymore, sorry
[Galaxy Tab 10.1 Android Development] funky81:
Works fine here GT-P7500 3G UX ..all works great

Testing battery now
[Galaxy Tab 10.1 Android Development] :
Working good the little i tested. P7510 UX with Starburst rom.

With setcpu set to min 1400mhz max 1400mhz I get around 6050 to 6100 in Antutu Benchmark.

And Quadrant standard gets 2800 to 3010
[Galaxy Tab 10.1 Android Development] jvs60:
Will this kernel work with Bonsai rom?
[Galaxy Tab 10.1 Android Development] drae52:
Read the thread.

Search the thread.

Use the thread.

Don't expect people to hold your hand; the information is there and it doesn't need to be regurgitated for every person to lazy to read it. Sure the thread is long, but it's long for a reason... all these silly questions are already answered.

Now, repeat after me.

Read the thread.

Search the thread.

Use the thread.
[Galaxy Tab 10.1 Android Development] pershoot:
Ivarson, this works fine on 7500.

Use clockwork mod to flash.

This is only for your stock touchwiz ux based rom.

No idea what broodcomb contains.
[Galaxy Tab 10.1 Android Development] SeanHacker:
and another awesome job pershoot! Nothing wrong with this so far. Best my tabs been yet.
[Galaxy Tab 10.1 Android Development] pershoot:
Flashmaniac, read the blog post.
[Galaxy Tab 10.1 Android Development] ivarson_swe:
I know, you're right. I posted too soon. It seemed to work better when I flashed from recovery. With booth stock and broodcomb. When I flashed from rom manager it froze on samsung logo.
[Galaxy Tab 10.1 Android Development] Silenus21:
I don't know why people are lazy with Rom Manager.

Just use Quickboot from the market and restart to recovery and flash it that way.

It's always better to take the best method when flashing because is a delicate process.
[Galaxy Tab 10.1 Android Development] nakedninja42:
New kernel is running great, thanks pershoot!
[Galaxy Tab 10.1 Android Development] Flash1960:
The new Kernel runs great with Broodcomp and SPB Mobile Shell 3D on a P7500.

Thank you, pershoot
[Galaxy Tab 10.1 Android Development] Entropy512:
I haven't seen anything in the sources that I've been able to find, wasn't sure if you knew if someone had mapped things out. This weekend I might throw some code into check_samsung_charger to loop through all the ADCs and printk the results - see what's on those other channels.

If we can get separate monitoring of D+ and D-, we can safely add detection of iPad chargers.

ROM Manager is evil - I've seen it cause too many problems in the Infuse community (It always starts a different CWM version than what the rest of the Infuse community uses that has limitations that cause a LOT of bad flashes). IMO, if you aren't able to use CWM (it isn't that hard), you have no business running custom ROMs.

One of these days I want to see if the power menu can be altered to add recovery like it can be on phones.
[Galaxy Tab 10.1 Android Development] mabalito:
Had my Tab completely freeze on me a few minutes ago.

I was listening to music on Spotify through my earphones and browsing this forum using the Tapatalk app. Also had an ongoing conversation on Talk.

I am using the latest kernel (081911) on my GT-P7500, with no overclocking (maxfreq 1Ghz @ ondemand)

Here's my /proc/last_kmsg:

http://dl.dropbox.com/u/194238/android/last_kmsg.txt
[Galaxy Tab 10.1 Android Development] pershoot:
I'm surprised u can even run tapatalk. It always bombs out and causes havock.

Ill look at the log, but that app is known to have badness on HC.
[Galaxy Tab 10.1 Android Development] kiowahawk:
Same here!.....using starburst rom with pershoot kernal.

Thanks
[Galaxy Tab 10.1 Android Development] winhwah:
The new kernel + starburst ROM = Awesomeness!

Thanks pershoot!
[Galaxy Tab 10.1 Android Development] K Rich:
starburst and pershoot 08/19/11 running just fine this way :cool:

i think a lot of problems are user error.... dont shoot me haha
[Galaxy Tab 10.1 Android Development] Grommish:
Same with the Epic. Reboot via recovery sends it to a redirector typically, not the bml8 partition. So the cwm you install isn the same. Our motto over there is 3-finger or gtfo..
[Galaxy Tab 10.1 Android Development] Entropy512:
Tapatalk Pro has always been good for me. The XDA-specific version of Tapatalk is ancient and FCs all the time on HC.

Same here. ROMManager takes Infuse users to "green" CWM which doesn't understand ext4. Since it doesn't, it tends to hose up devices when you flash anything on a system that has ext4 partitions.

This is BAD considering that one of the first mods anyone does is Voodoo Lagfix, aka RFS to ext4 conversion.

We always use "red" CWM on Samsung-derived ROMs (Voodoo-aware CWM 2.5.x) or "orange" CWM on CM7 (CWM 4.x)

Oh and when one of our ROM devs pulled his stuff from RM, our dev threads got cluttered with a "I got this error from ROM Manager" every 2 pages, even though the first post said he pulled it from RM.
[Galaxy Tab 10.1 Android Development] ehe12:
Dear Entropy512, I would love to know what the difference is between different CWMs. I'm using a CWM from the topped thread:"look here first...", it's color is orange. Before I flashed from stock rom and the starburst rom with this CWM and my screen turned snow and dead. today I reflashed to stock Arabic rom with TW, went into recovery mode, I noticed it turned into original blue one. I flashed this kernel once and didn't see any change. So I reflashed the orange CWM, rebooted into recovery and flashed the kernel again. This time I did it! I can see how good this kernel is now!

I wonder if the CWM I used is the reason to cause the screen dead?

Also THANK YOU OP for your great work!
[Galaxy Tab 10.1 Android Development] Ettepetje:
After a disaster earlier today (link) I am really looking for a CWM kernel for my GTB 10.1 3G. All the tips and tricks topics in this forum seem to hint using Rom Manager for this particular model. Now I read that ROM Manager should not be used for this kernel, which is one of the only kernels that works. I am confused.

Is there a kernel I can flash that can get me this Pershoot kernel (and allow me to make nandroid backups)? And a procedure that leaves my stockish rom intact so I can backup?
[Galaxy Tab 10.1 Android Development] SeanHacker:
always make a nandroid backup in cmw to be safe. you can flash pershoots kernel via cmw bro
[Galaxy Tab 10.1 Android Development] ehe12:
report back about 360 wireless controller. On this kernel it's working great with FPSE, all buttons work. I use this app called "usb joystick center", which claims to support all kinds of controllers: normal wired PC controller, 360 wireless&wired controller; bluetooth ps3 controller& wired controller, etc. Costed me 1.3 euro but worthy.

I tried a little FPSe, FF9 is working, but the resolution of the game isn't perfect, with a lot of sharp edges, so are other games. I don't know if I set up something wrong? if not it's really disappointing.
[Galaxy Tab 10.1 Android Development] jzen:
Thanks Pershoot! Seeing nice increase in performance :-)

3124 quadrant
[Galaxy Tab 10.1 Android Development] Ettepetje:
If you read my post then you would notice I ask for a way to get CWM, preferably with my current setup intact. I just spend 8+ hours setting it up again from scratch.

The "Galaxy TAB 10.1 3G" appears to be lacking an Odin flashable kernel containing CWM. My hope is that someone can help me (and other owners) out.
[Galaxy Tab 10.1 Android Development] wlighter:
finally with this new kernel I am getting a good power usage, even better then stock. On idle screen off it takes only 18-21mA. I haven't had a chance to test it longer than 5 hours idle. But in tht 5 hours it drop 0%!!
[Galaxy Tab 10.1 Android Development] paratox:
read this thread.

there is all the info you need.
[Galaxy Tab 10.1 Android Development] Ettepetje:
I did, most of it at least. It suggests using 'Rom Manager', which from what I've read sofar is no use for flashing kernels like the one in this topic.

I'm thinking to Odin flash a Wifi kernel, immediately enter recovery and from there make a backup and flash this topics kernel. I'm unsure if this works.

This forum and especially the topic you mention is only half helpful for 3G owners, unless you're willing to read hundreds and hundreds of posts, which is no fun seeing 95+% of the posts are about the wifi version without that fact (Wifi) being mentioned.

I will see if I missed something in the topic you mentioned somewhere buried in the middle.

I would be grateful however if someone could point me to a post, kernel and/or procedure to flash a proper CWM kernel in my device. :)
[Galaxy Tab 10.1 Android Development] paratox:
read the steps carefully!

at first you flash the root.zip in stock recovery .

reboot.

install rom manager from market.

open rom manager and flash the CWM recovery directly in the app.

after this you have rooted tab with CWM.

then flash pershoot kernel in CWM recovery.

done!
[Galaxy Tab 10.1 Android Development] patomas:
You can install Rom Manager from market and use it to install CWM. Its a feature of rom manager.
[Galaxy Tab 10.1 Android Development] Ettepetje:
Thanks! In all the hours and hours of reading this forum I misread that one line... :o

B.t.w. is it normal that all 13GB of the internal storage is wiped after a data/Factory reset? Standard recovery did that to me twice now, fortunately I backep up everything to my laptop this time. On this forum it is suggested as crucial without much fuss, elsewhere on xda it is vaguely suggested and the impact is much less severe.

I will flash this kernel immediately when I return home! :D
[Galaxy Tab 10.1 Android Development] Grommish:
Tab died overnight. Though it might be batt because it was low, came back up with 12% (I do not have the calibration issue, tab was under mod use for more than 2 days off charger)

Last_kmsg attached, tell me what I screwe up. :D
[Galaxy Tab 10.1 Android Development] pershoot:
yup, ill remove this completly, 'too much work'. i ratelimited it (so it wouldn't flood i/o causing a hang), but it still is apparent in some rare cases (usually when plugged in).

it'll be in the next release.
[Galaxy Tab 10.1 Android Development] Entropy512:
This is getting offtopic as far as this thread, but my experience was that FPSe's defaults give very blocky pixelated graphics. There's a setting that makes things look MUCH better, but also makes the game lag too much on the Tab. I've basically given up on PSX emulation on the tab - maybe when the quad-core NVidias come out it'll be doable.

If you think this is impressive, you should've seen his last release pre-rework. It could go days only losing 1-2% - but it would also not wake up for alarms or anything. (sleeping a little too well...) The post-rework kernel drains a little faster, but not extremely so, and worth the fact that the tab can now be a reliable alarm again. :)
[Galaxy Tab 10.1 Android Development] :
The initial version worked well with me, I'm on StarBurst ROM, then after I did the 3.2MB update from Samsung, I had to go to back to stock kernel, I tried to install pershoot kernel 8/19, but when the device boots up, I get scrambled colors only and nothing can be visualized clearly. Did this happen to anyone? What's the solution?
[Galaxy Tab 10.1 Android Development] pershoot:
They may have removed inverse display in the update.

Flash p4wifi instead of p4wifi-ux, and see if that works.

Flash stock boot.img first from the update, before flashing p4wifi kernel (non ux).
[Galaxy Tab 10.1 Android Development] ehe12:
according to previous posts this has something to do with CWM and rom manager. try flash using CWM.
[Galaxy Tab 10.1 Android Development] TimOster:
XDA is no longer worth my time.
[Galaxy Tab 10.1 Android Development] Grommish:
You have a unlocked bootloader, which menas you can flash cwm via nvflash to the recovery partition. Better in my mind than a redirector.

Stock recovery (on unlocked anyway) can flash unsigned .zip files.. your sdcard sounds hosed, reset to factory default under stock recovery and it will format it out. Then nvflash cwm (save the backup), boot to cwm, nandroid backup, flash rom, then kernel. Reboot.

You can also ODIN to 3.01 to get the system up and running, then flash the new 3.1twux and kernel, as stock recovery factory clears sdcard and cwm's usb mount doesn't work.

EDIT: where did you get the tab from. Someone has already screwed with it (no cwm from samsung!) and most instructions here are based on a stock tab, which you don't have. Resetting everything to stock and going from there is my recommendation. Certain things (like bonsai) can screw up other things even after you switch roms.
[Galaxy Tab 10.1 Android Development] Kiwi187:
A quick observation from my tablet;

Running the previous kernel with starburst was great. I was getting fantastic battery life.

After flashing this version of the kernel, I first noticed it was no longer overclocking to 1.4. I restored back to the previous version then reflashed again. Overclocking started working, but now battery life is pretty bad.

I havent tried calibrating yet.
[Galaxy Tab 10.1 Android Development] :
I did that, I'm on CMW 4.0.0.4
[Galaxy Tab 10.1 Android Development] :
First I was flashing the non-ux kernel (by mistake, I didn't notice there are ux and non-ux versions), then I tried the ux version it didn't work. the strange thing is that the initial version of the kernel works so fine, and I'm using it now, but the updated version keeps giving me the scrambled-color screen.
[Galaxy Tab 10.1 Android Development] pershoot:
Then your not flashing something properly and/or flashing the wrong file, currently.

Scrambled screen is indicative of that, when working with ux.

If they updated the kernel, and took out what current ux base needs, then try the non ux kernel on the new update they sent.

I haven't seen it, so can't amend things until they finalise it and send it across.
[Galaxy Tab 10.1 Android Development] :
I tried flashing these files:

10.1-Wifi (GT-P7510):

boot-cm_2636.4-oc-xtra-vfpv3-d16_fp-081911.zip

10.1-Wifi, Touchwiz UX (OTA, GT-P7510):

boot-cm_2636.4_ux-oc-xtra-vfpv3-d16_fp-081911.zip

the kernel "boot-cm_2636-ux.zip" is working fine with me.
[Galaxy Tab 10.1 Android Development] pershoot:
That is exactly what u should be using for touchwiz ux.

Your posts earlier suggested otherwise (that they changed something in this update they pushed, rendering this incompatible).
[Galaxy Tab 10.1 Android Development] :
so I guess it is just the device doesn't want to have this kernel. anyway i'll enjoy the initial version of the kernel
[Galaxy Tab 10.1 Android Development] pershoot:
Huh?

What initial version.

No idea what your doing over there, but I would start from scratch, reread everything, and u won't have an issue.
[Galaxy Tab 10.1 Android Development] :
I mean by initial version of the kernel this file: boot-cm_2636-ux.zip
[Galaxy Tab 10.1 Android Development] pershoot:
The current ux version of this kernel works fine on the ota touchwiz ux rom.
[Galaxy Tab 10.1 Android Development] :
ok thanks, I'll try to figure out if there's something wrong that I'm doing
[Galaxy Tab 10.1 Android Development] Super-S:
Works great on ux.. Thx a lot pershot :-)

No Battery probs here...
[Galaxy Tab 10.1 Android Development] :
Anyway I can change it to NOOP?
[Galaxy Tab 10.1 Android Development] pershoot:
check under sysfs/block

you can echo noop to 'scheduler'
[Galaxy Tab 10.1 Android Development] ittihad:
posted this in the StarBurst ROM topic and they advised me to post in this thread:

i really like this room but i have a problem with it, i cant use the 30 pin connecter for anything other than charging? my usb connection kit doesn't work with the rom and my pc Don't recognize my tab so i cant transfer files from my pc.

am using preshoot kernel and didn't have this problem with stock?
[Galaxy Tab 10.1 Android Development] pershoot:
This is not a rom; just a kernel is supplied in this .zip

No issue with usb debugging or mtp, and none reported from other users. Check your drivers.
[Galaxy Tab 10.1 Android Development] ittihad:
i tried 2 other computers and non recognize my tab? all this after i installed this kernel! even kies doesn't recognize my tab?
[Galaxy Tab 10.1 Android Development] pershoot:
i just tested this against UEKME. no issues.

im working against windows 7, so for that, do this:

plug in usb. uninstall samsung mobile phone. refresh. it will search and install. once done, unplug tab, re-plug tab. youll see MTP initialisation on tab -> connected, then youll get a popup on your client.

for kies, after launching the app then plug it in.
[Galaxy Tab 10.1 Android Development] pershoot:
and latest kies works without issue.

unplugged, replugged, it reinstalled driver, connected, sees rom version, i get options.. all is well.
[Galaxy Tab 10.1 Android Development] Flashmaniac:
Wanted to say thanks for the freaking cool kernel :)
[Galaxy Tab 10.1 Android Development] neonflx:
Which of the two roms should I use if I'm using starburst rom? Thx
[Galaxy Tab 10.1 Android Development] EmryX:
hello everyone!

I have a little problem. I flashed my Samsung Galaxy Tab 10.1 20minutes ago and everything is okay: NTFS, Mouse, Keyboard, my tab is a little smoother, etc...

BUT! I can't use my 360controller with the usb adaptator...

I have the 16GB Wifi White version (euro because i'm french :p so... with touch wiz ux). What can i do?

Thx a lot!
[Galaxy Tab 10.1 Android Development] jvs60:
From the date of the update there is no mention of Bonsai, smart ass
[Galaxy Tab 10.1 Android Development] Grommish:
This is the first android device community I've seen that expects a kernel to fit a rom. Roms are expected to tailor to a kernel, not the oher way around. Want bonai to work for sure? Get bonsai to adopt the kernel.
[Galaxy Tab 10.1 Android Development] Entropy512:
USB adapter is working fine for me here, same with ADB.

Stock 3.1 + Pershoot kernel.

The problem lies with StarBurst ROM, either the ROM itself or an incompatibility with the kernel. I know that Bonsai ROM was breaking USB host capability a few weeks ago. Seems to be a common thing with the hacked userland stacks.

I suspect StarBurst itself is broken. Any ROM that markets itself as the "fastest and most complete TouchWiz experience" is probably going to have a lot of brokenness in my opinion. Developers that care about quality don't market heavily, and developers that are prone to breaking things tend to market a lot.
[Galaxy Tab 10.1 Android Development] wojmzy:
One small issue i discovered after few days on new kernel (using stock deodexed TW rom) - setcpu ondemand after a reboot is set to 1200 but cpu itself is running at max 1000. I need to move slider back and forward and it catches 1200, but without that its stuck on 1000.

After few hours on inactivity (for instance during a night) tab is stuck on black screen and pressing power button doesnt toggle it on. Pressing power for a few seconds turns him off tho. I removed all software regarding lockscreen and will test it again.
[Galaxy Tab 10.1 Android Development] pershoot:
Not an issue. If u don't have onboot selected, then yes this will ocurr once u enter the app. You must slide it up/down. Its been like that for a while (from what I can remember).

Post logs of this lockscreen issue. I am reluctant to increase the delay more to attenuate for recalibration of mxt.
[Galaxy Tab 10.1 Android Development] K Rich:
This kernal + KME = one smooth and fast Tab!

---

- Sent from your mothers house.
[Galaxy Tab 10.1 Android Development] wojmzy:
Set on Boot toggle button is big enough i didnt miss to check it :)

Regarding lockscreen - i used hard reset to see if its my problem since no one posted similar experience. Will update if it happends again.

Yet again thank You for developing this !