yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Android Development] rickyq12:
This kernel is only for ICS builds.

Task 14 is based off of Honeycomb.

So the answer is no.
[Galaxy Tab 10.1 Android Development] pershoot:
The last hc32 kernel was Jan 9 2012. That is compatible with task14.
[Galaxy Tab 10.1 Android Development] RustyNailz:
Tablet was non-responsive when I took it off the dock this morning. Only thing I did different last night was to turn the screen off while docked by pressing the power button. Last_kmsg attached.

I'll update to today's version and report back if I encounter any additional issues.
[Galaxy Tab 10.1 Android Development] pershoot:
try that, but i think this is the best i can do for your specific tab at this current time. its really always the same 2 or 3 people with the same issue. you must have some hw variance that is needing to be rectified through a sw workaround that i haven't found yet. for 99% of the people this is solid (including myself; testing also with a dock and someone else with a dock also).

this same behavior was also noticed with honeycomb and a very small group of users. stock too.
[Galaxy Tab 10.1 Android Development] RustyNailz:
It happens so infrequently, that it's not really a big deal. I was only trying to assist you in identifying the underlying issue.
[Galaxy Tab 10.1 Android Development] pershoot:
ya. ill keep it on the list and keep on it as we go along. its tegra2 thats plagued with this issue. not sure on tegra3. ive done my best to workaround few scenarios so most are good, but there's always the odd ended one that give me a run for my money, hehe.
[Galaxy Tab 10.1 Android Development] spippo:
This kernel(in first page) is for honeycomb (with recovery mod) or ICS rom?

Tx :P
[Galaxy Tab 10.1 Android Development] pershoot:
last honeycomb kernel was jan 9 2012. everything else after is for ICS only.
[Galaxy Tab 10.1 Android Development] pershoot:
wifi is very good. fast. i just hit 23.5mbps down (speedtest.net app).
[Galaxy Tab 10.1 Android Development] Judgement5:
06/13 is boot looping on my wifi tab on aokp m5, had to go back to 06/10.
[Galaxy Tab 10.1 Android Development] pershoot:
this is for CM9. no idea whats in AOKP. speak with the author.
[Galaxy Tab 10.1 Android Development] fusionjack:
Hit 26.8 Mbps from 32 Mbps...nice pershoot! :D
[Galaxy Tab 10.1 Android Development] exxpired:
this works fine on aokp b38
[Galaxy Tab 10.1 Android Development] Pablo87:
Ok. So first time after I bought this tab in this morning I found it in bootloop. I'm running CM nightly 13.06 with 13.06 kernel. I put it on charger around 02:00h and when I woke up at 08:30 my tab was in bootloop. It wasn't exactly on boot animation but it was on screen that come after the boot animation - black backround and text in the middle that said: starting applications. Only difference between now and every other night is that this night i left my tab connected to my home wireless. It was frozen on that text so i long pressed power button and restarted tab to cwm using volume up and down buttons. But when i connected tab to my pc and run adb and type adb devices there is no devices listed. In hardware manager there is GT-P7500 under "Portable devices" but there's no Adb Interface. So I can't pull out last_kmsg. But my tab is normally recognized when I enter download mode - I flashed cwm recovery and stock ROM trough odin many times. It must be some problem with drivers.

Can someone help me solve this problem ?
[Galaxy Tab 10.1 Android Development] pershoot:
Boot loop means you had corruption. Not necessarily an issue with this release. Its an issue on this tab. Happened on hc too. Although I haven't seen this in a while now.

Pull your media off /data/media. Odin back to 3.2, then come back up.
[Galaxy Tab 10.1 Android Development] Pablo87:
You mean to completely restock my system with pit file and erase /sdcard or just install stock rom and left my /sdcard intact?
[Galaxy Tab 10.1 Android Development] pershoot:
Odin back to 3.2 will wipe the whole tab. That's the recommended course of action in this scenario to achieve best results.

Backup your stuff in cwm using adb to pull it off.
[Galaxy Tab 10.1 Android Development] pershoot:
6/14 is up (wifi update). this should allow you to see 5GHZ channels when selecting auto.
[Galaxy Tab 10.1 Android Development] Kayak83:
Not sure if it's the boot loop I've been reading about in this thread, but mine has been rebooting during the night and getting stuck on "Android" booth screen until I power it off. It's done it with AOKP, Coffebean's build, and pershoot's snapshot. The common denominator being pershoot's kernel, so I am assuming that might be it. I've been doing a full wipe for every install as well. I understand it might be a bad app as well.
[Galaxy Tab 10.1 Android Development] pershoot:
not from a recent kernel. this has been well tested throughout the month. you have corruption. odin back to 3.2 and come back up, then use latest cm9 nightly and latest kernel.
[Galaxy Tab 10.1 Android Development] RustyNailz:
On 6/14, I'm back to having to toggle wifi on the tablet to get the wifi working again after the screen has been off for a period of time.
[Galaxy Tab 10.1 Android Development] pershoot:
Clear /data/misc/wifi

I've toggled/slept/woken/thrashed wifi. No issues at all from what I can see.
[Galaxy Tab 10.1 Android Development] RustyNailz:
Done... I'll report back if I encounter any additional issues.
[Galaxy Tab 10.1 Android Development] vibecatalin:
Few moments ago found my tablet in the same situation. Not charging, I left it on

my desk an after two hours found it like that. This is the first time. And last night I upgraded to latest CM9 and latest kernel.
[Galaxy Tab 10.1 Android Development] RustyNailz:
Unfortunately this didn't resolve the issue. I'm rolling back to the 6/13 version to see if the problem goes away.
[Galaxy Tab 10.1 Android Development] pershoot:
I'm reluctant to roll back. It fixes a bad bug with wifi. I can't reproduce your issue at all. My tab has been idle for 10+ hours now. Wake up and wifi is strong and connected.
[Galaxy Tab 10.1 Android Development] pershoot:
Vibe, no idea. I guess your issue goes in to the unknown pile. I cant reproduce your issue if your getting a bootloop. Has to be something isolated on your side. You'll have to troubleshoot in pieces. Scroll up for some hints on how to do that.
[Galaxy Tab 10.1 Android Development] RustyNailz:
I understand. Anything I can do to help troubleshoot the issue?
[Galaxy Tab 10.1 Android Development] pershoot:
youll have to see why your AP is kicking out the connection and your client (tab) is not able to reconnect. you can see this in the log.

im also running this same driver on my phone (gnex). no issue at all.
[Galaxy Tab 10.1 Android Development] pershoot:
you should not be running AOKP if that is what you are testing against. this is not tested against nor intended for that rom base.
[Galaxy Tab 10.1 Android Development] RustyNailz:
I'm running a version of CM from earlier this month. I can update to see if that affects anything.
[Galaxy Tab 10.1 Android Development] pershoot:
update to latest nightly and download 0615 (i just uploaded it), and flash that over. clear /data/misc/wifi after flash, then reboot. if you use gapps, ensure it is the latest.
[Galaxy Tab 10.1 Android Development] pershoot:
6/15 is up. just reverting one thing and will revisit sometime in the future.

please ensure you are on the latest nightly (CM9).
[Galaxy Tab 10.1 Android Development] zerong:
is it ok with task 14 ?!?
[Galaxy Tab 10.1 Android Development] ProfEngr:
Nope ics only
[Galaxy Tab 10.1 Android Development] jimh1999:
Mine is great after latest refresh running at 1.2, no lockups. Off charger for 12 hrs, used it a little and sitting at 90% battery.

Thanks for your work pershoot.
[Galaxy Tab 10.1 Android Development] ghylton:
I'm loving this. Running smooth at 1.2 with no problems
[Galaxy Tab 10.1 Android Development] mannequin:
yes, the audio is off sync. i think hulu is slightly better synced now with the OC but that's not saying much. pretty much every flash HD video in the browser is slightly off sync for me.

the vimeo HD video gave me a reboot with the latest kernel but i need to test more.
[Galaxy Tab 10.1 Android Development] pershoot:
galaxy tab 10.1 - 2.6.36.4 - 6/27 refreshed (filename has not changed) - please flash; http://droidbasement.com/db-blog
[Galaxy Tab 10.1 Android Development] SellswordShev:
Just watched a bunch of freddiew high action scenes @720p in browser (http://www.youtube.com/user/freddiew). I didn't notice any audio sync / choppiness (some lag when the google ad popup came up, but closing it fixed that immediately).

I am running this kern at 1.4 now (on demand govern). Seems good and stable for the last hour in which I have run youtube + linpack. No note-able heat / sleep of death issues either. Will flash the new refresh shortly.

Edit: I am running autokiller on a 250,275,300 profile by the way, maybe your sync issues are from low memory ?
[Galaxy Tab 10.1 Android Development] Itaintrite:
Is SetCPU still needed to set clockspeed? I already flashed back to stock.
[Galaxy Tab 10.1 Android Development] pershoot:
this refresh is only to reduce voltage to the second nominal slot, after hearing of the previous user account of the tab not coming back on normally, after being idle.

please let me know if there is any instability as a result (for users who determined that they were stable prior).

if there is, report back, and i will fine tune things further.

setcpu is never needed (its just easier and more convenient). scroll up, and you will see my suggestion of alt. methods.
[Galaxy Tab 10.1 Android Development] skrowl:
pershoot messaged me and got me fixed up. If you can't boot, try holding volume up plus power or both volumes and power. I'm not risking it since my best buy return window is up Sunday. This puppy is going back tomorrow!!
[Galaxy Tab 10.1 Android Development] nakedninja42:
I flashed the previous build this afternoon and did not have problems, but then again did not have it installed very long. I installed this evenings update and launched xda about half hour of it in stand by, it frooze and did a soft reboot when the xda app was mid rotation from portrait to landscape. Could've been a fluke but wanted to report it. Let you know if anything else happens.
[Galaxy Tab 10.1 Android Development] pershoot:
are you positive you are stable at the freq. your trying to run at?

i will bring back up the voltage at any rate.

will refresh once more.

and ill also increase the low-end a bit.
[Galaxy Tab 10.1 Android Development] pershoot:
refreshing once more shortly.

sorry guys. last one for the night.. promise! hehe.
[Galaxy Tab 10.1 Android Development] nakedninja42:
I have setcpu set at max 1Ghz. Not planning on overclocking the cpu. The soft reboot is the first one I've experience since getting the tablet last week.
[Galaxy Tab 10.1 Android Development] pershoot:
ok.

the refresh should fare you better.

pls standby.
[Galaxy Tab 10.1 Android Development] G1_enthusiast:
Trying this thanks!
[Galaxy Tab 10.1 Android Development] pershoot:
galaxy tab 10.1 - 2.6.36.4 - 6/27 refreshed (once more); sorry about that! - http://droidbasement.com/db-blog
[Galaxy Tab 10.1 Android Development] nakedninja42:
getting a 404 on the download link :(
[Galaxy Tab 10.1 Android Development] pershoot:
yea have to rebuild and reup. few mins.
[Galaxy Tab 10.1 Android Development] spirit32:
I just cleared my dalvik cache and I haven't had a freeze now on 1.4, just my 0.01
[Galaxy Tab 10.1 Android Development] jm6001:
Pershoot,

I was wondering if there will be some sort of RAM hack for the tablet? I have been keeping an eye on how little RAM we have access too.. Aren't we supposed to have 1gb of RAM? I never seen more than 500mn..any information would be great!
[Galaxy Tab 10.1 Android Development] pershoot:
no ram hacks. userspace gets ~750 or so. the rest is reserve.
[Galaxy Tab 10.1 Android Development] mcgoo99:
pershoot, i got a sleep-of-death on your 6/14 experimental build. tried pulling the last_kmsg but there was no file found in /proc. is there something else i can pull off to aid in troubleshooting?

EDIT: ps, thanks for all your hard work!
[Galaxy Tab 10.1 Android Development] pershoot:
614 is gone. Flash 615.
[Galaxy Tab 10.1 Android Development] pershoot:
as i previously stated, its always the same 3 or 4 people with the same 1 or 2 issues. i bet if those people went back to honeycomb, the same issues would occur (maybe worst). not sure what to think in regards to this. ive seen the same during HC development days though.

not discounting a defect here and there in the hardware, im unsure if i can drum up SW workarounds for these wierd/odd scenarios in a timely fashion. the data ive collected is not really conclusive. for those people, you may have to bear with it while we go along.

in regards to sod:

remember, tegra2 is known for SOD. ive done my best to workaround alot of it, but there is some rare instances were it could still be prevalent.
[Galaxy Tab 10.1 Android Development] mcgoo99:
ok will flash 615 and report back.

as for this being an existing condition, i never had a SOD or wifi outage on the stock HC 3.2 ROM that i ran from Dec through April. i had previously odin'd and re-hacked three weeks ago per your direction in the CM9 thread.

the only thing that might be different about my tab? it was bought refurbished from woot back in early December. i'd be curious to learn if my fellow xda users with the same issue are in the same boat.

all-in-all, these are nuisance faults, and worth living with to have CM9 on the tab. thanks once again for all your effort!
[Galaxy Tab 10.1 Android Development] Trv06kviper:
Flashed on tab AKOP build 38 no issues thus far.
[Galaxy Tab 10.1 Android Development] GalaxyNinja:
I have the SOD and did not have it prior to a few changes:

-Updated my recovery to 5.5.0.4

-Started using Nightlies from CM9 server

-Change OC from 1.2 - 1.4 (prior to the new ICS kernels my tab would crash at 1.4 but be ok and 1.2)

If I have the the SOD with 6/15 I will go back to OC 1.2 and see if that stops the SOD.

Thanks for all the hard work Pershoot
[Galaxy Tab 10.1 Android Development] pershoot:
Yes I'm aware of your tab. Its one of those special cases I lumped in with the same handful of people.

U shouldn't OC until u confirm your tab is healthy with the current software. Post a log if u have issue.
[Galaxy Tab 10.1 Android Development] pershoot:
Rusty, did u get to the bottom of the wifi disconnects?
[Galaxy Tab 10.1 Android Development] pershoot:
all ok with 6/15, aside from the 3 or 4 people that have had issues for a while (which ill investigate seperately as we go along)?
[Galaxy Tab 10.1 Android Development] RustyNailz:
Yes and no. Seemed to work fine while at the office. Got home and within a short period of time has the disconnect issue. I just checked it after being idle for several hours, and its working fine ATM.

Only difference between the two locations is that one connects at 2.4GHz and the other at 5GHz. I just switched from Auto to 2.4 GHz only to see if that makes any difference.
[Galaxy Tab 10.1 Android Development] pershoot:
Yea I'm sure once Sammy releases ics and I get some new firmware in my hands it may make the slight wonkiness better. All this stuff is a work in progress tho. Alot of this stuff has progressively gotten better and will continue to do so as we go along.

Wifi is pretty solid for me here though.
[Galaxy Tab 10.1 Android Development] pershoot:
you might try to relax some settings on your AP. it could also be inadvertently closing the channel out due to no inactivity (and the client (tab)) not sending a im alive in time or at a frequency not fast enough for your AP, etc.
[Galaxy Tab 10.1 Android Development] mcgoo99:
I've been running it all day. No SOD's as of yet, and one brief pause at the lockscreen while the wifi disconnected and reconnected. Good so far!

EDIT: spoke too soon; got a bootloop overnight while on the charger. tried to pull the /proc/last_kmsg but adb says the file was not found. sorry.
[Galaxy Tab 10.1 Android Development] pershoot:
No idea on that bootloop. I don't know anyone who can reproduce that (aside from the same 3 or 4 tabs reporting issue out of maybe thousands at this point).

Sounds like corruption though.

Sanitize your tab to look for the culprit. This means Odin back to 3.2 and come back up in steps.

Make sure you don't have massive errors on emmc.
[Galaxy Tab 10.1 Android Development] pershoot:
however, with that being said, ill work on updating that subsystem for the next round of changes.
[Galaxy Tab 10.1 Android Development] SlakWReX:
Does anyone have the link to the honeycomb kernels. I can't find them on the website. All I see are the ics ones.
[Galaxy Tab 10.1 Android Development] Jay Rock:
Go further to the older pages.
[Galaxy Tab 10.1 Android Development] m_gl:
So after doing all steps the problem seems gone.

No SOD after charging anymore.

If it comes back, w´ll report.

Thanks Pershoot!
[Galaxy Tab 10.1 Android Development] BillShepp:
Updating to final HC3.2 kernel

Sorry for engaging the time machine, but I'm running 3.2 on my 7510 and prefer not to go to ICS yet. I'm running your 091311 kernel and would like to update to the final (010912) update. Is the cleanest way to do this to install the full OTA update from 112311, then the 010912 update, or does the 112311 not qualify as a stock kernel? My confusion lies in 010912 (http://droidbasement.com/db-blog/?p=2479) saying "If you

were not

running the previous version of this kernel, then please flash back to the stock kernel, prior to upgrading to this kernel.", while 121111 (http://droidbasement.com/db-blog/?p=2448) says the opposite, "If you

are

running a previous version of this kernel, please flash back to your stock kernel, prior to upgrading to this kernel." This is a bit counter-intuitive, since usually it's OK to upgrade from the previous version - perhaps the word "not" was inadvertently dropped here?

Bottom line, what's the best way to get from 091311 to 010912?

Thanks!

- Bill
[Galaxy Tab 10.1 Android Development] pershoot:
reflash your rom (this will replace the kernel), boot in, then back to recovery and flash the jan 9 2012 kernel.
[Galaxy Tab 10.1 Android Development] pershoot:
putting out a update in a few. please let me know if this behavior is cured/better with it.
[Galaxy Tab 10.1 Android Development] teddybaerd:
Thanks pershoot. One question, what does this mean:
[Galaxy Tab 10.1 Android Development] RustyNailz:
Will do.
[Galaxy Tab 10.1 Android Development] thamajam:
Every time I try to download a sizable file (including nightlies from get.cm) wifi cuts in and out multiple times, many times killing the in progress download. Driving me nuts since I've been trying to download Max Payne for like 3 days and it never goes more than a minute or so without wifi cutting out. I've tried Auto and 2.4ghz (my router seems to be 2.4). Tried clearing wifi settings in system and rebooting. No luck. Anyone else still having this issue?

I'm on a 7510, 6/15 kernel, 6/18 CM nightly.
[Galaxy Tab 10.1 Android Development] pershoot:
update your kernel, and no issue with wifi cutting out over here for long downloads (just downloaded temple run a day or so ago which is about 29mb i believe).
[Galaxy Tab 10.1 Android Development] pershoot:
look at github for the actual change.
[Galaxy Tab 10.1 Android Development] pershoot:
how is it?
[Galaxy Tab 10.1 Android Development] pershoot:
testing this change on the gnex.. it appears reconnections are faster. can still fake it out in real low signal, where its half/half on its way being out, but i think that probably may always be the case.

another tester for tab, reports good success. re connections are faster if it does drop it.
[Galaxy Tab 10.1 Android Development] RustyNailz:
So far so good, but truly too soon to tell based upon my past experience.
[Galaxy Tab 10.1 Android Development] thamajam:
still having the issue after updating the kernel. it usually bails out after 30 seconds or so of continuous downloading. maybe i should try a clean install.
[Galaxy Tab 10.1 Android Development] pershoot:
Can't reproduce. Just downloaded latest nightly from get.cm straight to tab. No issue. Came down fast.
[Galaxy Tab 10.1 Android Development] Panos_dm:
Actually I had this problem earlier. Tried to download 19/6 nightly, with 19/6 kernel already installed, but it failed. It downloaded ok on the computer though.Anyway, I restarted the router 2 times because the signal was highly unstable and in the meanwhile I accidentally erased the nightly from my pc. After one hour tried the download from the tab and it went smoothly. So maybe it was cm server or router or both....I can't really tell, but I have no problem since.

Sent from my amazing 10.1 galaxy tab :)
[Galaxy Tab 10.1 Android Development] thamajam:
thanks for the feedback, went the direction of a router problem; updated the firmware on the router and she's been solid as a rock since.
[Galaxy Tab 10.1 Android Development] RustyNailz:
Just happened again. Dmesg output attached. This is what shows in the logcat:

I/wpa_supplicant( 261): eth0: CTRL-EVENT-DISCONNECTED bssid=00:14:bf:e8:4e:c7 reason=0

D/CommandListener( 112): Clearing all IP addresses on eth0

D/ConnectivityService( 186): ConnectivityChange for WIFI: DISCONNECTED/DISCONNECTED

D/ConnectivityService( 186): Attempting to switch to BLUETOOTH_TETHER

W/NetworkManagementService( 186): Unable to remove route on interface eth0

W/NetworkManagementService( 186): Unable to remove route on interface eth0

D/NetUtils( 186): android_net_utils_resetConnections in env=0x1ab07d8 clazz=0x66a00001 iface=eth0 mask=0x3

D/ConnectivityService( 186): resetConnections(eth0, 3)

W/Smack/Packet( 333): notify conn break (IOEx), close connection

D/NetUtils( 186): android_net_utils_resetConnections in env=0x1ab07d8 clazz=0x68100001 iface=eth0 mask=0x3

D/ConnectivityService( 186): ConnectivityChange for WIFI: DISCONNECTED/DISCONNECTED

D/ConnectivityService( 186): Attempting to switch to BLUETOOTH_TETHER

D/ConnectivityService( 186): resetConnections(eth0, 3)
[Galaxy Tab 10.1 Android Development] pershoot:
doesnt really tell me why it disconnected, although it looks like it was forced to disconnect.

it could still disconnect (for various reasons), but now it should reconnect quite fast. i can confirm this behavior along with another two other testers (one who had the same issue as you).

the change added to 6/19 has made things better from what i can see, thus far.

are you on the latest firmware for your router?

is your wifi sleep policy set to never?

do you have a low signal situation that is forcing a disconnect?
[Galaxy Tab 10.1 Android Development] luke05dee:
Just updated to your newest kernel and I am sure that games are a bit smoother. Just to test gpu performance I ran nenamark 2 and I got 20.9fps where I was only getting 18fps before the update. May I ask if you have done something, or it is all in my head please? What ever has happened I am happy, thank you :)
[Galaxy Tab 10.1 Android Development] pershoot:
i updated BFQ I/O scheduler to v3r1.
[Galaxy Tab 10.1 Android Development] RustyNailz:
Does dmesg log help at all?

Router is an older Linksys running a version of dd-wrt. Wifi sleep is set correctly. No low signal issues afaik. Once the connection is severed, it will not reconnect on its own. I have to cycle wifi off then on to get things working again.
[Galaxy Tab 10.1 Android Development] pershoot:
are you running the latest version of dd-wrt on your router?

i too run dd-wrt, but on an e4200.

i'm suspecting a local issue, since i really cant find anyone with your specific issue and with such extremity at this point in time. those that had it, seem to be ok now (for the most part).

you can certainly try to manually select 2.4GHZ, but i think the end-result may be the same.

try to have your tab connect to another AP that is fairly strong (and known good) for a long duration and see if this occurs. if it does not, then the AP may be having an issue, etc.
[Galaxy Tab 10.1 Android Development] pershoot:
refresh coming. just want to add 2 network related changes. want it to supersede the one from this morning.