yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Android Development] AAccount:
Yes, 2.2 is based on XE and the ram disk can now only enable 3G on 3G tablets. Enabling 3G on wifi only tablets causes it to panic OCD style and it will never go in to offline mode.

Ram disk is like a super mini rom that Linux based operating systems load to get things going. After the ram disk gets things going, it will then load the rom. This applies to all Linux based systems including my laptop and salvaged desktop that run Fedora 17.

If you want to return to 1.5.9, the only thing different between that an 2.1 is that 2.1 has my customized ram disk which allows boot scripts. 1.5.9 doesn't come with a ram disk but pulls the current one you have and merges it with the kernel I provide. Therefore, flashing 1.5.9 on top of 2.1 will be pointless without flashing the stock kernel first.

You could flash it from the PC in download mode but why bother? su and dd are very convenient and don't require a reboot.
[Galaxy Tab 10.1 Android Development] AAccount:
Is your battery low? My tablet was racing at 1.6GHz this afternoon without problems, but now that it is down to 25% it just doesn't want to any more. Low battery makes it not smart to flash, so I can't really fix this problem. Therefore, it has to be pulled :crying:
[Galaxy Tab 10.1 Android Development] danielsf:
May I ask why not try a version with a slightly higher voltage for 1.6ghz?
[Galaxy Tab 10.1 Android Development] AAccount:
Well, ok. I'll try it but I'll just do personal testing first. With each new feature I add, I figure out that more and more tests have to be done. Unfortunately, this usually happens after a release or when situations I didn't think matter, actually matter.

Just out of interest, what do people think is too high for voltages? I'm extremely hesitant to do any more than 1400milivolts.
[Galaxy Tab 10.1 Android Development] danielsf:
From what I have seen on the s2, s3 (I know completely different SoC's, but similar architecture) Is that you avoid going over 1400mv. I remember reading something on the s3 forums saying that anything over 1400mv could cause electron migration and degrade the chip. So when overclocking for me, I always try to stay ~1400mv max. I would say anything over 1400mv is too high, that's just my opinion anyway :) What are you currently using for 1.6ghz please? Also, if it is working stably for a few minutes which it seems to for some of us, I am pretty sure that means that we are close to the voltage it needs to be stable. And, if we can't get to 1.6, maybe 1.5ghz could be an option.
[Galaxy Tab 10.1 Android Development] scoffyburito:
I was running on 1500mv for a week on my nexus and nothing wrong short term.
[Galaxy Tab 10.1 Android Development] The Root:
Nope, just locks when I activate 1.6 ghz. That's fine. Not all devices can handle.
[Galaxy Tab 10.1 Android Development] zerong:
Hello !

I am on 1.5.9 SE with my p7510 wifi galaxy tab and all is ok ! now i would like the choice beetween oc 1.2 and 1.4 with setcpu soft ! so can i flash A1 kernel V2.1 directly with cwm ? stable version ?

Thanks

ps : what is kernel 2.2 source ?!?
[Galaxy Tab 10.1 Android Development] hanspampel:
Yes you can flash it over 1.5.9. 2.2 Source is imho the source code, its not a flashable zip.;)
[Galaxy Tab 10.1 Android Development] zerong:
Yes but why 2.2 source if last release is 2.1 ?!?
[Galaxy Tab 10.1 Android Development] hanspampel:
Beta of 2.2 was up, but AAccount took it down.
[Galaxy Tab 10.1 Android Development] jaswinky:
Ok, so, with my 7510 i don't have to worry about the ram disk because i'll never enable 3G, just I must to flash 2.1 and enjoy, my tablet will enter in offline mode... right? If I decide to back 1,5.9, I must flash stock first and then 1,5,9.

About su commands, I know this is offtopic but, how do you do it? from PC? which program are you using? Thanks.
[Galaxy Tab 10.1 Android Development] jayceebee23:
You can do it from the device itself using terminal emulator or from pc using adb.
[Galaxy Tab 10.1 Android Development] jayceebee23:
Anybody having issues with netflix on a stock ICS with the 1.5.9XE kernel? Video always freezes after just a few seconds of playback with audio still working. I'm also using setcpu to OC ondemand between 150-1400.
[Galaxy Tab 10.1 Android Development] Judgement5:
most people have that netflix problem on any variation of the stock 4.0.4 you have to go to your netflix settings on a computer and change it to better quality, the video freezes when it goes to hd on the best quality setting.
[Galaxy Tab 10.1 Android Development] jayceebee23:
Thanks for the suggestion but unfortunately it's still the same regardless of the setting. It was working fine on the HC 3.2 as well as CM10 preview. It's no big deal. I don't watch netflix on the tab anyway (my daughter though uses it to occasionally watch her cartoons). Just wondering if there's any resolution to this issue.
[Galaxy Tab 10.1 Android Development] Jay Rock:
Sweet thanks for the stable 1.4 Ghz :D

Will flash shortly.
[Galaxy Tab 10.1 Android Development] indira19:
sorry for my ignorance , how can i enable 3g on wifi only tablet? i have a 3g usb dongle can i make it to work on the tab using usb port??? i am on task ICS ROM which kernel version should i flash to make it possible?.

i just need the 3g usb working on my tab i am afraid to overclock it. so any flashable zip that can enable or i have to flash the kernel? kindly help
[Galaxy Tab 10.1 Android Development] RavenY2K3:
You can't, no other answer than that I'm afraid.
[Galaxy Tab 10.1 Android Development] Akitohk:
hi,

im using p7510 wifi with A1 kernel v1.52

i would like to upgrade the kernel to v2.1

but i don't quite understand about the ramdisk

should i open terminal enter the command "su

dd if=/sdcard/bootwifi.img of=/dev/block/mmcblk0p3"

before flashing V2.1 or just flashing V2.1 is ok?

thank you!:o
[Galaxy Tab 10.1 Android Development] Toldo:
I don't know if it was mentioned earlier but I think there is a bug with usb charging. The Tab doesn't turn off while plugged into usb. Normally it should shut down and show the battery chaging animation, but instead it performs a normal reboot.
[Galaxy Tab 10.1 Android Development] XTeK2:
...new kernel - available soon.;)
[Galaxy Tab 10.1 Android Development] blademetal:
it's know bug.. bat if you before switch off... and after put the charger ..work fine and don't switch on
[Galaxy Tab 10.1 Android Development] jayceebee23:
OC's at 1640Mhz. How long can you sustain that without lock-ups? Which kernel is that?
[Galaxy Tab 10.1 Android Development] Toldo:
It doesn't lock up. Works stable at 1,6 now for like 2 hours? 1.7 is, and will be, possible with higher voltage. Kernel is yet to be released. Still it's a work in progress and highly confidential.

My screen, so you won't think it's a fake.
[Galaxy Tab 10.1 Android Development] danielsf:
I am just wondering whether the GPU could be clocked higher as I remember in the xoom forums a few people could get to 512mhz and a lot could get to about 450mhz. So maybe we could give ~420-450 GPU a shot? Also, Aaccount my galaxy tab 10.1 p7510 wifi isn't my primary tablet anymore, my nexus 7 is, so I am happy do beta testing for you if you would like. :)
[Galaxy Tab 10.1 Android Development] Toldo:
This can be done but also our tab has FPS lock (vsync), and that's why when antutu shows the knights animation one wouldn't get more than 50FPS while without the lock one should have there like 60FPS. I don't know yet if this can be unlocked but GPU OC can be easily done. On Transformer they do like 425 and I think it would work quite nicely, and why not more ;)
[Galaxy Tab 10.1 Android Development] danielsf:
I know about vsync and it shouldn't be disabled you should just use a benchmark that never gets to the cap to show the performance difference between the frequencies. My Favorite is basemark es 2 which I use to test the overclock on the s3 and nexus 7 both never hit 60fps once and it really shows you the performance difference. Like stock on this tab on basemark es 2 I got about 6fps and at 400mhz I got about 9fps. I am a fan of vsync as for the most part as any frame drawn over 60 with a display that has a refresh rate of 60hz is wasted frames. So any overclock extra on the gpu may not be noticeable in quadrant which hits the cap but games that had a low frame rate on a lower frequency will show a improvement. I am just a fan of GPU overclock over CPU overclocking as it shows a user noticeable difference straight away when playing certain games which would struggle on the lower gpu clock frequency. :) I would love to push the gpu to the max in this tab :D
[Galaxy Tab 10.1 Android Development] AAccount:
Hello everyone,

I am still trying to get a more stable 1.6GHz working with a 1.5GHz step in there too. I'm hesitant to do 1.7GHz considering that I do not want to do more than 1375mV CPU and 1450mV core. I am testing the 1.6GHz+1.5GHz kernel right now on my tablet. I just didn't have any time yesterday to tinker. Getting the voltages right is really difficult because (as I've seen), you can get hours of usage and then when the battery drops, the tablet refuses to do more 1.6GHz.
[Galaxy Tab 10.1 Android Development] steveman29:
Thank you for your efforts! Is there any chance to try higher GPU OC in the near future?
[Galaxy Tab 10.1 Android Development] AAccount:
Sure, I'll try it right now and see how it goes.
[Galaxy Tab 10.1 Android Development] steveman29:
Thank you :good:
[Galaxy Tab 10.1 Android Development] AAccount:
For everybody following this thread, please know that my Galaxy Tab 10.1 is my only tablet and still has a long "service life" ahead of it for now. Unlike my SGS1 which was recently replaced by the international SGS3, I have no intentions of buying another tablet. Therefore, I am hesitant about cranking up the voltages so high to cause unforseen long term damage. This is the main constraint on OC for GPU and CPU.

I hope you can understand.
[Galaxy Tab 10.1 Android Development] steveman29:
Ok we understand and thanks for all your efforts.
[Galaxy Tab 10.1 Android Development] danielsf:
Thanks for all your efforts mate :D That's completely understandable you not wanting to go to 1.7ghz, tbh I doubt you would notice any difference between 1.6 and 1.7 anyway especially when it could cause long term damage on 1.7. :)
[Galaxy Tab 10.1 Android Development] AAccount:
The GPU doesn't seem to want to push 450MHz. I made the same changes that I did for getting 400MHz, but I'm getting the same fps in GLBenchmark 2. To do the 400MHz, I just changed the 3D sku and added 400MHz in the tegra2_dvfs.c. Any suggestions?
[Galaxy Tab 10.1 Android Development] danielsf:
This may be stupid of me to say, but could the frequency be found invalid and so reverts to 400mhz, as in only certain frequencies will be found valid and then used. If I remember somewhere someone said that they thought the transformer tegra 2 could do 425mhz. Maybe 425mhz is worth a try?
[Galaxy Tab 10.1 Android Development] steveman29:
You are right, it's in this post:

http://xdaforums.com/showthread.php?p=24489191&highlight=gpu#post24489191
[Galaxy Tab 10.1 Android Development] Svid:
dosen't work on cm9 p7500.

installing stock ROM and testing this kernel again.
[Galaxy Tab 10.1 Android Development] jaswinky:
Of course... you should read the name of this thread: "...[StockICS]..."

Enviado desde mi GT-P7510 usando Tapatalk 2
[Galaxy Tab 10.1 Android Development] AAccount:
I'm interested to know what happened when you tried it in CM9? But, yes: this is only intended for Stock ICS.
[Galaxy Tab 10.1 Android Development] AAccount:
Thanks for the suggestion. I will try it in a few hours. So, GPU OC is maxed at 425, or is it trial and error to find anything else it will take?
[Galaxy Tab 10.1 Android Development] spitzaf:
Should be some common multiple into 333 and 400, similar to multiplier OC on a computer CPU. I'd guess that 467 would work (but not likely stable considering the level of OC) or more likely 433.
[Galaxy Tab 10.1 Android Development] AAccount:
Looking at tegra2_dvfs.c and pairing that with a greatest common factor online tool, the base appears to be 9500. I put all the clock speeds shown into my calculator and got a nice whole number multiplier. However, even after putting in nice multiples of 9500 like 427.5MHz or 456MHz, I still can't get more fps on the GLBenchmark test. Is it possible the multiplier is locked?

Oh, and by the way, 425MHz is not a multiple of 9500 and didn't work either. However, 400MHz is not a multiple of 9500 either but works...???
[Galaxy Tab 10.1 Android Development] spitzaf:
Interesting. We'll, it was a thought but apparently the same rules don't apply with these chips. I wonder if there is some kind of lock in the chip to prevent OC beyond the Nvidia spec. It'd be smart to prevent people burning out the chips...
[Galaxy Tab 10.1 Android Development] steveman29:
xoom

There is a thread in the motorola xoom section that the developer claim to have overclocked the gpu by 33%, that makes it to about 442,89 Mhz. Maybe you can get some ideas from him.

http://www.xda-developers.com/android/xoom-now-zooming-along-at-1-7-ghz-thanks-to-tiamat-kernel/
[Galaxy Tab 10.1 Android Development] Toldo:
Did you fix that usb charging bug I mentioned couple posts earlier?

Wysyłane z mojego HTC Desire HD With Beats Audio za pomocą Tapatalk 2
[Galaxy Tab 10.1 Android Development] danielsf:
Beta 3 seems to be working well. I have set max frequency to 1.6ghz and it is flawless. No rebooting, lock ups or any other instability issues. I have been testing it with numerous stress tests and bench-marking apps, so far everything is great :) Thank you :)

Edit: I have to say that at 1.6ghz the tab isn't getting partially hot at all when bench-marking. :)
[Galaxy Tab 10.1 Android Development] blademetal:
Boot script support (put yours as /data/local/a1init.sh) <-- new to V2.0

i don't understand..What should I do? :)
[Galaxy Tab 10.1 Android Development] Duvel999:
V2.2 Beta 3 runs well with JB v5.1 on my P7500:good:

312mhz & max frequency to 1.2 ghz just testing
[Galaxy Tab 10.1 Android Development] AAccount:
According to their kernel sources, that kernel runs the gpu @ 400mhz.
[Galaxy Tab 10.1 Android Development] AAccount:
If you want your tablet to run a shell script automaticly when it boots, name your file a1init.sh and put it in /data/local. If you dont want to, you can ignore this.
[Galaxy Tab 10.1 Android Development] steveman29:
I guess he didn't know how to calculate percentage correctly. So probably this is the max tegra 2 can achieve.
[Galaxy Tab 10.1 Android Development] AAccount:
Well, according to Wikipedia the Xoom's Tegra 2 GPU came clocked at only 300MHz. The Galaxy Tab 10.1 came clocked at 333MHz so for the Xoom, 300MHz to 400MHz is a 33% increase. This is also the same Wikipedia page that I came to the conclusion that 400MHz was acceptable to NVidia since it shows a Tegra 2 device was shipped with a 400MHz GPU.

Note: I actually didn't look at the Timat Xoom kernel to do the OC for our GPU. I just followed approximately the same template that CPU OC does. It's nice to know I got the method right after looking at the Timat source.
[Galaxy Tab 10.1 Android Development] djmatt604:
Buddy this kernel is kicking ass. About to throw it on the wife's tab too :)
[Galaxy Tab 10.1 Android Development] AAccount:
Just a side note, it is possible to use some CM9 apps like browser, email, keyboard on stock ics. I personally think the stock ics email app is much uglier than the cm9 one and the samsung keyboard doesn't work with terminal emulator. I also think the cm9 browser looks more modern. Obviously, you must download a CM9 nightly. Apks come from the zip file's /system/app. To get the browser: use titanium to uninstall the stock browser, restart, use adb to install browser.apk. For email: use titanium to uninstall email AND exchange services, restart, and use adb to install email.apk and exchange.apk. For the keyboard: just use adb to install latinime.apk. I removed the samsung keyboard through titanium, but it's not necessary. Trebuchet installs too, but I like the touchwiz launcher better.
[Galaxy Tab 10.1 Android Development] AAccount:
Not to sound arrogant, but does it work? I downloaded that rom and took apart the ram disk and didn't find any changes made to use the boot animation binary /system/bin/bootanimation in the start up script. I checked my SGS3's initial start up script and saw that it does call a binary in there.
[Galaxy Tab 10.1 Android Development] tektus:
My tablet fly.......
[Galaxy Tab 10.1 Android Development] AAccount:
I tried to put A1 Kernel on CM10. As a summary, everything but wifi works. Below are the details of how I tried it. Suggestions would be welcome on how to make it work.

First, you cannot use V2.2 since the samsung ramdisk is incompatible with the current CM10. Second, you need to edit a file in the CM10 ramdisk called "init.p3.rc" and change all instances of eth0 to wlan0. The interface name of the wifi "thingy" has changed. Second, you need to copy in the firmware files found in the stock /system/etc/wifi. Those are the .bin files as well as nvram_net.txt and wpa_supplicant.conf. You also need to copy libhardware_legacy.so in /system/lib. After that I got an unpleasant issue. I tried to enable wifi which did work BUT after 2 seconds, it would start bootlooping. Yes, that's right, it would start bootlooping at the cyanogenmod portal animation AFTER it booted. To make matters worse, adb would not let me in saying I had insufficient rights. At this point, I cannot diagnose the issue and attempt to bring A1 to CM10. Any help would be appreciated.
[Galaxy Tab 10.1 Android Development] Svid:
The process com.andrpid.phone has stopped working

after pressing ok it keeps poping up the error.

Nvm flashed stock ICS with the kernel = FLYING LIKE A BOSS.

Voodoo sound works too

You did a great job.
[Galaxy Tab 10.1 Android Development] XTeK2:
Wonderful!!

And that's just mine.;)
[Galaxy Tab 10.1 Android Development] tektus:
which kernel have you?

1700 mhz ????
[Galaxy Tab 10.1 Android Development] Toldo:
He just keeps sabotaging the thread:) That's a test kernel in the making by our friend. It will be released soon.
[Galaxy Tab 10.1 Android Development] AAccount:
Yes, once again can we AVOID the advertising. This thread is for feature requests and bug reports. Also, to my followers, A1 kernel will not be getting a 1.7GHz OC because I've already maxed out the voltages. Any more, and I'm afraid of causing long term damage.
[Galaxy Tab 10.1 Android Development] Toldo:
+1 to that. And keep in mind that overclocking isn't fun. It can harm your device in a way you may won't recover it. And remember that each and every cpu is made out of different piece of silicone waffle, thus one may work on 1,7 with no problem, while the second one will freeze on 1,5.
[Galaxy Tab 10.1 Android Development] djmatt604:
Thanks AA for looking out. Sign of a responsible dev and we all really appreciate it :)
[Galaxy Tab 10.1 Android Development] AAccount:
So, should V2.2 be made final and not beta? How is it working for everyone? Also, any more ideas. It looks like V2.2 may be forever final since I'm out of new ideas. Undervolting is still out of the question.
[Galaxy Tab 10.1 Android Development] Toldo:
Maybe some more governors? Also, two bugs are present. 1. Tab restarts instead of powering down while connected to usb. 2. Same as the first one but without cable connected.
[Galaxy Tab 10.1 Android Development] HansiHusten:
*cough* also the deep sleep bug when WiFi setting is set to "always on" *cough*
[Galaxy Tab 10.1 Android Development] AAccount:
That might come from some app that is running when your wifi is always on. Maybe a weather app or news app?
[Galaxy Tab 10.1 Android Development] AAccount:
Quick news flash: I tried installing the A1 kernel V2.2 (just the kernel and not the ramdisk) on pershoot's newest CM9 builds and it boots and works! One minor flaw: you cannot boot with the USB connected or you get the old boot bug present in A1 V1.4 but for a completely different reason. ADB does work, but you need to enable mtp mode first.

Will post screenshots later.

PS: do not flash the A1 V2.2 zip on this cm9 build. You must disassemble it first to just get the kernel zImage and copy over the kernel modules too. Or, you can try V1.5.9.
[Galaxy Tab 10.1 Android Development] tissot:
It's a shame to say it, I feel dirty and greedy to just mension it. I dont want to be demanding and needy :) But I have to ask.

Have you put bootanim in the grave for now? Can't no one help, some guru? Can I perhaps buy you a beer? :)
[Galaxy Tab 10.1 Android Development] scaryshark:
Hmm, I think pershoot listed a recommend recovery & bootloader for his newest CM9 build otherwise you will encounter problems. It might be worth a try checking it out.

*I would love to test for you but I've got some important skyping with my mum to do :D
[Galaxy Tab 10.1 Android Development] Svid:
Nice update gotta test it on cm nightly
[Galaxy Tab 10.1 Android Development] blademetal:
which are the benefits of "cifs utf8 kernel module" ???
[Galaxy Tab 10.1 Android Development] AAccount:
I tried the camera app in this cm9 nighly and both cameras work. I also installed xda's modded skype and it shows 2 cameras.
[Galaxy Tab 10.1 Android Development] sc00ter98:
Where can I get the modded Skype?

Sorry for OT.

Gesendet von meinem GT-P7500 mit Tapatalk 2
[Galaxy Tab 10.1 Android Development] ThehypnooToad:
Can confirm on ics with 2.2 getting freezes so have to boot tab straight back into another freeze thats been tested on 1.4 1.5 1.6 screen gets very hot at left hand side near top
[Galaxy Tab 10.1 Android Development] AAccount:
I uploaded a wifi only kernel for CM9 since I got some kind of kernel hsic wake lock when I used the 3G kernel. The modded skype has nothing to do with the Galaxy Tab 10.1 or CM9 but lets you disable that very annoying start up noise.

As for the boot animation, I've tried every possible combination of bootanimation binary possible. I've tried pulling it in /sbin and /system/bin. I've pulled the binaries from my SGS3 CM9 (which works perfectly), my SGS1 CM9 (which also works perfectly), and an older CM9 nightly from the summer (which also worked perfectly). That's 2binaries * 3 roms makes 6 attempts I've made to get custom boot animations working. Unfortunately, every binary pulled from /sbin causes a freeze after the custom animation runs, black screen delay, and finally the lock screen where you get a notice that systemui has stopped responding. In total, that's a 10-15second extra delay. Pulling the binary from /system/bin causes the boot animation to run indefinetly and must be killed using adb. Seeing that it works on all CM9 roms makes me think that the source for bootanimation must be changed to adapt to stock ICS, which I'm not sure how to do.

To be honest, I actually erase the cyanogenmod boot animation and just let it run the really old android 1.5 built in boot animation to shave a few seconds off boot time.

PS: I'm not the US legal drinking age yet.
[Galaxy Tab 10.1 Android Development] Toldo:
I also spent some time on figuring that out and I got similar results. Also editing init.rc inside the boot to values that worked on HC doesn't work. I guess something has changed.

Anyway, again did you fix that bug in v2.2 that I reported with the tab rebooting instead of powering off?
[Galaxy Tab 10.1 Android Development] tissot:
Ahaaa.. you tried everything i see. Good work anyway. Some time you run into the solution.

PS. I send you a Root beer instead :D
[Galaxy Tab 10.1 Android Development] AAccount:
Well, this is a good news bad news moment: the good news is that this bug doesn't appear to be present in CM9 through no change of my own. The bad news is that when the tablet boots into charging mode, it will freeze loading the green battery picture and must be forced to restart (again through no change of my own). I also had this freeze problem in a CM9 July nightly.

Another side note: When I flashed the 9/01 nightly, I did it using TWRP recovery and am still using HC bootloaders to no ill effect so far.