yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Android Development] AAccount:
The tablet OK, but by moody I mean it doesn't have the boot up freeze anymore. Sort of personifying the tablet where moody is whether it feels like booting or not. Is it even worth trying to continue overclocking? I read in the SGS1 forums that overclocking in ics was nowhere near as stable as when it had gingerbread. Does the same apply here too?
[Galaxy Tab 10.1 Android Development] jaswinky:
I don't really think it's even worth to overclock to 1.6GHz. I don't know any P75xx kernel to 1,6GHz in HC, so this whould be for any reason... The experiences I have been having with overclock is that you can do it safetly with good brands and devices, because the design is oversized to sure the people will not have any problem. Cheaper devices could not be too oversized. Example: my SGS2, with siyah kernel, I can put from 1,2GHz to 1,6GHz (33%), that's all. I tried 1,4Gz with no problem (I have clocked it to 1,2GHz because I don't need yet 1,4 or 1,6, so that I save battery); our tab, to 1,4GHz (40%) with no problem. However, I also have a LG Optimus Black overcloced from 1GHz to 1,1GHz, because 1,2GHz had a problem with apk installations from market :confused: . You cannot predict the effects of a bad overclocking... this booting bug is the same thing... maybe the voltage differences are in the limit and small difference in temperature (note that in those small voltages, the amperage is more sensible to small temperature changes because the impedances) may cause a insufficient suply...
[Galaxy Tab 10.1 Android Development] AAccount:
Ok, I'm cancelling it. It seemed to work OK in preliminary tests but the tinkering with voltages is getting annoying.
[Galaxy Tab 10.1 Android Development] kordellas:
Anyone can give me a guide on how to flash a kernel ?
[Galaxy Tab 10.1 Android Development] blademetal:
from recovery
[Galaxy Tab 10.1 Android Development] jaswinky:
Consider that it was only my opinion about it... I think now, it is more important to improve more and more 1,4GHz than start with a 1,6GHz project some inestable... Maybe in some moths when all tablets will be quad at 1,5GHz, and the apks will be made for them, it would a great idea to start or continue this project...

That what happen for me with my SGS2, now I don't need 1,4GHz or 1,6GHz, but I know in some monthes when most apk will be design for SGS3, then these apks will go perfect for me in my SGS2 at 1,6GHz... so I prefer to wait for that...
[Galaxy Tab 10.1 Android Development] AAccount:
Making a tmobile version would make it impossible for me to test since I don't want to risk messing my wifi only tablet testing it. I want to at least do a few basic tests before releasing it so I know it works. However, the sources are all there and I did put sort of step by step instructions somewhere in this thread.

What are the hardware differences between the TMobile Galaxy tab 10.1 and the international P7500 anyways?
[Galaxy Tab 10.1 Android Development] AAccount:
Good idea. My own SGS3-I9300 is non OC'd at 1.4GHz anyways. I'm sort of getting stumped by all the boot issues anyways.
[Galaxy Tab 10.1 Android Development] blademetal:
difference between SE and XE ?

ps: sorry I had not read :D
[Galaxy Tab 10.1 Android Development] AAccount:
After further investigation, you need to put your swap file in /data/local. The /sdcard directory is a fake sd card and is really /data/media. Something about the faking does not allow swap files to be put there. Check out my terminal example. Swap is enabled but needs to be in /data/local. The faking of the sd card is probably the same reason why you can't just move the swap file to /data/local and why it must be copied then erased from its original location.

root@android:/sdcard # mkswap swap.disk
Setting up swapspace version 1, size = 33550336 bytes
UUID=94658bfe-a265-4aed-afaf-d2de1fc485f2
root@android:/sdcard # swapon swap.disk
swapon: swap.disk: Invalid argument
1|root@android:/sdcard # ls /data/local
tmp
root@android:/sdcard # mv swap.disk /data/local
failed on 'swap.disk' - Cross-device link
255|root@android:/sdcard # cp swap.disk /data/local
root@android:/sdcard # cd /data/local
root@android:/data/local # ls
swap.disk
tmp
root@android:/data/local # mkswap swap.disk
Setting up swapspace version 1, size = 33550336 bytes
UUID=bdf56bf0-7311-4d4c-a852-430cc6753198
root@android:/data/local # swapon swap.disk
root@android:/data/local # free
total used free shared buffers
Mem: 738984 726600 12384 0 97964
-/+ buffers: 628636 110348
Swap: 32764 0 32764
root@android:/data/local #
[Galaxy Tab 10.1 Android Development] jaswinky:
I think where could be the reason why still happen the freeze boot issue a few people (I read one here and one in htcmania):

Sorry, I don`t know how to insert code as you do...

Again the init function where initial voltages are assigned:

void __init tegra_soc_init_dvfs(void)

{

...

BUG_ON(speedo_id >= ARRAY_SIZE(cpu_speedo_nominal_millivolts));

tegra2_dvfs_rail_vdd_cpu.nominal_millivolts =

cpu_speedo_nominal_millivolts[speedo_id];

BUG_ON(speedo_id >= ARRAY_SIZE(core_speedo_nominal_millivolts));

tegra2_dvfs_rail_vdd_core.nominal_millivolts =

core_speedo_nominal_millivolts[speedo_id];

tegra2_dvfs_rail_vdd_aon.nominal_millivolts =

core_speedo_nominal_millivolts[speedo_id];

...

}

Here is assigned the nominal voltages from the array due to the speedo_id. Ok, the problem is that tegra2_dvfs_rail_vdd_cpu.nominal_millivolts, tegra2_dvfs_rail_vdd_core.nominal_millivolts and tegra2_dvfs_rail_vdd_aon.nominal_millivolts were created with a default value at begining of the file. This mains that in any instant, even with a reduced probability, it could coexist a cpu nominal value assigned from speedo_id array and a core nominal default value. If so, see this:

static const int cpu_speedo_nominal_millivolts[] =

/* spedo_id 0, 1, 2 */

{ 1100, 1225, 1125 };

static const int core_speedo_nominal_millivolts[] =

/* spedo_id 0, 1, 2 */

{ 1225, 1275, 1300 };

...

static struct dvfs_rail tegra2_dvfs_rail_vdd_cpu = {

.reg_id = "vdd_cpu",

.max_millivolts = 1250,

.min_millivolts = 900,

.nominal_millivolts = 1175,

};

static struct dvfs_rail tegra2_dvfs_rail_vdd_core = {

.reg_id = "vdd_core",

.max_millivolts = 1300,

.min_millivolts = 950,

.nominal_millivolts = 1225,

.step = 150, /* step vdd_core by 150 mV to allow vdd_aon to follow */

};

Nominal values in bold and red could coexist... It is difficult, I know, but maybe because this reason only one or two people are still reporting the problem...

Maybe decrease first bold value from 1225 to 1175 as cpu default nominal value?, or increase second bold value to 1275 as nominal core array value?
[Galaxy Tab 10.1 Android Development] decatf:
Can I make a request that the first post also detail what voltage changes were made from the stock settings? That's pretty important when it comes to overclocking.
[Galaxy Tab 10.1 Android Development] AAccount:
I moved the cpu_speedo_nominal down to 1175. I prefer a decrease, rather than increase in voltage. Then I tried to have all cpu nominals and all core nominals the same so I lowered the core_speedo_nominal down to 1225. Now this way all the cpu nominals are 50mV under the core nominals. Surprise! I got the boot bug with that. A quick reflash solved that and it booted. That's really weird since everything fitted the 50mV rule.

I thought the speedo nominals were "jumpstart" values. I also thought the rail values were the "operating" values. I had the jumpstart values a bit higher because after some trial and error setting the jumpstart values a bit higher than the operating values seemed to work better. I personally call that "jumpstaring it hard". I guess there is no getting around checking every single cpu nominal against every single core nominal value.

Why weren't these inconsistencies a problem in the honeycomb overclock kernel??

PS: to mark something as code put "[ C O D E ]" before and "[ / C O D E ]" after.
[Galaxy Tab 10.1 Android Development] AAccount:
All changes can be found inside the thread. They're usually suggested by jaswinky so look for his longer posts (which should be easy to spot).
[Galaxy Tab 10.1 Android Development] radiobicho:
Hi all. Im using 1.4 OC but i cand play hd videos. Any can suggest,me a player that do it? Thanks in advance.
[Galaxy Tab 10.1 Android Development] AAccount:
Mobo player is what i use to play my stuff. Has hardware decoding options too.
[Galaxy Tab 10.1 Android Development] jaswinky:
You get boot freeze after moving cpu_speedo_nominal down to 1175? Then, don't release this change :D

Then, what if you change the order for settings initial values? it is, instead of cpu, core and aon, better core, aon and cpu:

In the void __init tegra_soc_init_dvfs(void) funcition, just move:

BUG_ON(speedo_id >= ARRAY_SIZE(cpu_speedo_nominal_millivolts));
tegra2_dvfs_rail_vdd_cpu.nominal_millivolts =
cpu_speedo_nominal_millivolts[speedo_id];

after this:

tegra2_dvfs_rail_vdd_aon.nominal_millivolts =
core_speedo_nominal_millivolts[speedo_id];

---------- Post added at 03:53 AM ---------- Previous post was at 03:50 AM ----------

Anyway, if you got the boot issue after changing that initial value, with only this minor change, it means we are moving exactly around the problem and its solution... isn't it?

---------- Post added at 04:05 AM ---------- Previous post was at 03:53 AM ----------

Ey my friend... version 1.5.4XE gives allways me the boot freeze issue!!! But previous 1.5.4 allways works fine for me... It is suposed that 1.5.4XE and 1.5.4 are exactly the same version but... you sure??? I've checked it several times... Maybe you got the freeze after my last suggested change because you used a incorrect version with XE?
[Galaxy Tab 10.1 Android Development] AAccount:
The only thing that has been changed between 1.5.4XE and 1.5.5XE is that cpu_speedo voltage has been moved down to 1175. I meant another change that I made caused it to get the boot freeze when it shouldn't have theoretically because the 50mV rule was followed. That other change did boot after a reflash but that defies all logic. Specifically in the other change I tried to make all cpu nominals (rail and speedo) 1175 and all core nominals (rail and sppedo) 1225. This way I won't have to do a 4 way check to make sure cpu speedo, cpu rail, core speedo, core rail all follow the 50mV rule.

To be honest, my tablet seems to be pretty flexible with voltages.so it's hard for me to fix a problem I don't see. Perhaps by moving the cpu speedo from 1225 to 1175, your tablet isn't jumpstarted hard enough? See a few posts back for what I mean by jumpstarting.

Oh yeah, any guesses as to why copying and pasting the exact voltages from the honeycomb kernel isn't working? I mean, it worked like a dream in honeycomb.
[Galaxy Tab 10.1 Android Development] cpope-11:
On the newest one ex boots up then freezes and es works for about 5 minutes the freeze that only build that really works with my tab 1.1
[Galaxy Tab 10.1 Android Development] jaswinky:
1.5.5 worked for me perfect! This was my results:

1.5.4: never freeze at boot

1.5.4XE: allways freeze at boot

1.5.5XE: never freeze at boot

Thanks!

Enviado desde mi GT-P7510 usando Tapatalk 2
[Galaxy Tab 10.1 Android Development] AAccount:
Do you still have V1.1? I'm really at quite a loss as to why seeing as my tablet has never given me attitude when flashing a kernel that did 1.2GHz OC. 1.4GHz and 1.6GHz OC yes, my tablet was not always happy but it's been pretty cool with 1.2GHz.

Sorry about that.
[Galaxy Tab 10.1 Android Development] Philx64:
Whats the difference between Xe and Se ?
[Galaxy Tab 10.1 Android Development] AAccount:
Difference is in the very first post but I'll give you a hint: SE stands for standard edition, XE stands for eXtreme edition.
[Galaxy Tab 10.1 Android Development] Philx64:
Thanks, Xe means more powerfull - more performance ?
[Galaxy Tab 10.1 Android Development] AAccount:
Yes more performance but the 1.4GHz OC is harder to get working than the 1.2GHz OC. I recommend SE unless you have time to burn. After you have SE working you can try the 2 XEs listed.
[Galaxy Tab 10.1 Android Development] AAccount:
For me, I need the 1.5.4XE. Weird isn't it...
[Galaxy Tab 10.1 Android Development] Hulzer:
One simple question: Is 1.5.5 compatible with P7500 3g version?

Great job, thanks!
[Galaxy Tab 10.1 Android Development] robo116:
7500

One short answer yes read the first post.
[Galaxy Tab 10.1 Android Development] Hulzer:
Sorry, but there's is nothing mentioned about P7500 or 3G. This part is removed from that post, I think.
[Galaxy Tab 10.1 Android Development] hanspampel:
What do you think what 75XX is?;)
[Galaxy Tab 10.1 Android Development] kordellas:
After flashing this kernel, anyone noticed battery drains because of the l2_h2sic wakelock ?
[Galaxy Tab 10.1 Android Development] steveman29:
1.6 oc

I have never had any problem with overclocking. I believe that there should be 1.6 oc version for some people that can achieve this.
[Galaxy Tab 10.1 Android Development] Hulzer:
Ok, ok ;)

Earlier versions just were for P7510 and one for all.

I'll try it - thanks.
[Galaxy Tab 10.1 Android Development] saintsinner25:
works nicely on stock XXLQ8 :) thanks
[Galaxy Tab 10.1 Android Development] KePTeiN:
"2 Edition" good idea, i prefer SE
[Galaxy Tab 10.1 Android Development] kordellas:
Can anyone share me a how-to flash this kernel ?
[Galaxy Tab 10.1 Android Development] hanspampel:
Through Recovery? Go into CWM an go "install zip from sdcard". Maybe you can wipe "cache" and "dalvik cache" before.
[Galaxy Tab 10.1 Android Development] kordellas:
Silly question, but where do I found the Voodoo Sound Plus?

I have just flashed A1 but I can't find it.
[Galaxy Tab 10.1 Android Development] CazeW:
Download it from market.
[Galaxy Tab 10.1 Android Development] kordellas:
I can't hear any difference on the sound. Anyway.
[Galaxy Tab 10.1 Android Development] steveman29:
I think it is for headphone usage only.
[Galaxy Tab 10.1 Android Development] XTeK2:
Please 1.6GHz.

Why do not you put a clock on the 1.6GHz., if someone does not want to use can be set lower.

AAccount if you could please supply a clock to the kernel.

Sorry for my english.;)
[Galaxy Tab 10.1 Android Development] jaswinky:
AAccount, I'm sorry to read you are going to terminate XE project. For me 1.5.5XE works perfect, so I'll stand here with this version.

Anyway, It could not me a bad idea to post 1.5.4XE, 1.5.5.XE and 1.6GHz files advising that those project are some inestable, so that people could choose by their risk to install it or not, and clearly advertising that these versions are unsupported and so, any bug or error in these version will not depured any more for you... So this, you finish these projects, and people choose if they want to take the risk and use them or not...

Thanks anyway for your great job!!!!
[Galaxy Tab 10.1 Android Development] ker_:
could be possible to flash it on a custom rom or only in a stock?
[Galaxy Tab 10.1 Android Development] hanspampel:
You can flash it on Stock ICS or Stock Custom ROMs. But not on CM9 or CM10.
[Galaxy Tab 10.1 Android Development] Taransworld:
Thanks...

Just flashed your latest version and it is running great at 1.2. Thanks very much. :)
[Galaxy Tab 10.1 Android Development] blademetal:
How setting your governor and min frequency?
[Galaxy Tab 10.1 Android Development] CazeW:
Use SetCPU or NSTools.
[Galaxy Tab 10.1 Android Development] blademetal:
yes..i know..I wanted to know your settings :) (governor and min frequency)
[Galaxy Tab 10.1 Android Development] AAccount:
Here's what I found out last night from doing more rigorous testing on the 1.4GHz (XE) version last night. First of all, I tested by doing MANY MANY flash, turn on, turn off, cycles and combinations in between like only turning on and off. What I found out is that after several on/off cycles the 1.4GHz started to become unreliable. It was fine at the beginning though. This lead me to the conclusion that I "might be playing with fire" and as the saying goes "those who play with fire, get burned". I do not want to burn the CPU by accident, nor would any of you.

The files for a 1.6GHz OC have been included in the source so if you're feeling like you want to try it, you will have to do it yourself. Sorry for the inconvenience. I do not even use the 1.4GHz version, myself, anymore.
[Galaxy Tab 10.1 Android Development] blademetal:
how is it possible?... stock kernel @1000 (antutu score 5150)... this kernel @1200 (antutu score 4600) O.O
[Galaxy Tab 10.1 Android Development] PookiePrancer:
No matter what I change in No-frills CPU, the cpu is pegged at 1.2 min and max.
[Galaxy Tab 10.1 Android Development] kordellas:
AAccount thank you for this great kernel.

I have noticed a bug and I would like to share it.

Firstly I am in stock 4.0.4 rooted. Before flashing the kernel ( SE) I did Dalvik clean and wipe. I did not do a wipe after the installation of the kernel.

What I noticed is that

1. when the tab is turned off and plug it to the AC, it opens automatically ( before it was just showing the battery) and the home screen freezes.

2. When you have the device open and plugged it in AC, if you try to turn the device off, it will open again.

Of course, this may be something that my device does only. If so, do you know a fix or something? Thank you again!

---------- Post added at 06:33 PM ---------- Previous post was at 06:31 PM ----------

I noticed the same thing. :eek: I was expecting a quicker boot also...
[Galaxy Tab 10.1 Android Development] The Root:
I have the bug as well, but my antutu scored 6200.
[Galaxy Tab 10.1 Android Development] AAccount:
Thank you for the report. A fix will be uploaded within minutes. That bug is actually from a change I copied over from pershoot's new 3.1 git. Originally batt_lp_charging was set by samsung but pershoot changed it to charging_mode_booting. I'm not sure why he changed it, but undoing this fixed it for me.
[Galaxy Tab 10.1 Android Development] blademetal:
My min frequency is 1200 .... is normal?
[Galaxy Tab 10.1 Android Development] AAccount:
Use setcpu to change min to 216MHz and max to either 1GHz or 1.2GHz.
[Galaxy Tab 10.1 Android Development] blademetal:
ok tnx... and governor ?
[Galaxy Tab 10.1 Android Development] kordellas:
Thank you AAccount for the fix (I havent flashed it yet).

Do you have a clue why we get lower benchmark score than previous?

Also, -noob question- does the overclocking causes more battery consumption or it depends on undervolting?
[Galaxy Tab 10.1 Android Development] AAccount:
You mean frequency scaler? Also use setcpu. Disk io scheduler? I think ns tools does that.
[Galaxy Tab 10.1 Android Development] The Root:
Voltage control also works. I prefer it because the dev is very accessible.
[Galaxy Tab 10.1 Android Development] blademetal:
I wanted to say ondemand..conservative..interactive ..ecc..ecc..
[Galaxy Tab 10.1 Android Development] The Root:
At stock voltage for the highest frequencies it will consume battery faster since it's running faster and with more power, though processes get completed quicker. Be careful with undervolting as it often seems like Samsung tries to keep the voltage at the lowest settings for the chip without causing hangs or wakelock on stock. Some devices I have couldn't be undervolted at all. I find the exchange in battery versus performance and stability achieved by overclocking to be worth the price.
[Galaxy Tab 10.1 Android Development] AAccount:
Maybe because the ondemand frequency scaler is the default. Try changing to interactive.

Also, there is no undervolting available. The voltage configuration file is extremely unpleasant to work with.
[Galaxy Tab 10.1 Android Development] Ackoman:
I must be blind - where do you find the option to change the governer and the min and max frequencies?
[Galaxy Tab 10.1 Android Development] CazeW:
You need an app for that. I personally use SetCPU but there are others like NSTools and Voltage Control.
[Galaxy Tab 10.1 Android Development] XTeK2:
Set cpu, voltage control? Market......
[Galaxy Tab 10.1 Android Development] Ackoman:
Ah, ok thanks. I was thinking you did it from the rom settings.
[Galaxy Tab 10.1 Android Development] grac:
After flashing i have only 1.2ghz not 1.4ghz :(

Is this normal ??
[Galaxy Tab 10.1 Android Development] sc00ter98:
Yes, it is normal because playing with fire is danger. You can read it in OP.

Gesendet von meinem GT-P7500 mit Tapatalk 2
[Galaxy Tab 10.1 Android Development] darkstar107:
So is there any changes to the SE version aside from removing the 1.4GHz option? Is there any reason for me to re-flash it if I set it to 1.2Ghz rather than 1.4?
[Galaxy Tab 10.1 Android Development] sv2bzq:
Hi the version 1.5.6SE is not charging in P7510 ....
[Galaxy Tab 10.1 Android Development] cpope-11:
No need to be sorry the 1.5.6SE is working great for me now!!!no freezes or anything weird thanks man
[Galaxy Tab 10.1 Android Development] jaswinky:
Has anybody checked that if you use default interactive governor, the frequency before greatest (1Gz if you are using 1,2GHz SE version or 1,2GHz if you are using 1,4GHz version) never is used? You can see in CPU times from System Turner app or other similar... If you ser ondemand governor it will use all frequencies from min to max, but, as you maybe know, the performance is a bit poorer... Does anybody know if it is normal with this governor (to not use the second max freq)?

Thanks in advance.
[Galaxy Tab 10.1 Android Development] CazeW:
Checked on mine, it has used 1.2GHz (I'm OC'ed to 1.4GHz) but only for about 1% of the total time. I'm guessing it's normal behaviour for the interactive governor as nothing about the governor itself has been changed.
[Galaxy Tab 10.1 Android Development] kordellas:
Another one bug found, when using 1.5.5, I plugged it in the usb to charge having 95% and in one minute it showed me 100%. I removed the usb and it was 95% again.
[Galaxy Tab 10.1 Android Development] PookiePrancer:
You guys are getting cpu scaling? Once again, on 1.5.4 SE and 1.5.6 SE, all I get is 1.2 max AND min, no matter what I set with SetCPU or No-frills CPU. I'm all for performance, but that's a bit much :)
[Galaxy Tab 10.1 Android Development] engaz:
good improvement

nice work ... kernel used with JellyBeanRom ICS v5 :good:
[Galaxy Tab 10.1 Android Development] jaswinky:
I don't think this is a bug, I think this is a pershoot programming for safety, so that the current could cut off before get the bat full and so not damage it...

Enviado desde mi GT-P7510 usando Tapatalk 2
[Galaxy Tab 10.1 Android Development] grac:
Hello :)

Where i find v.1.5.xx XE A1 Kernel+ versions ?? :)
[Galaxy Tab 10.1 Android Development] AAccount:
Unfortunately, i took them down after a startling discovery that the 1.4GHz reliability decreased with an increase in tablet temperature. I do not want to raise voltages on top of what it already is to compensate for te temperature. Too much voltage is bad for the cpu which can make a literal example of "playing with fire gets you burned".
[Galaxy Tab 10.1 Android Development] pathuri97:
TAB working with 1.4GHz OC!

I'm using 1.5.4 with OC'ed to 1.4 GHz.

TAB is working fine and there is NO HEAT AND NO REBOOT.

Only thing is that when TAB is OFF for long hours (say night),

TAB is getting into boot loop.

In that case - press POWER + VOL DOWN and

enter into RECOVERY MODE and select REBOOT SYSTEM NOW.

TAB boots again without any problem.

This to be done only once in a day.

Only thing is that once in a day REBOOT to be done from RECOVERY mode.

I also had similar problem in GALAXY I 9000 with SLIMROM + SEMAPHORE.

Whenever new ROM or KERNEL is flashed - it is used go to RECOVERY mode and used to ask whether to FLASH RECOVERY or NO.

If NO is selected it will REBOOT normally.

I used to do this ONLY once per new ROM/KERNEL flashing.

I hope the above info is useful in fixing 1.4 GHz problem.
[Galaxy Tab 10.1 Android Development] dillfever:
AAcount does your kernel allow custom boots? Thanks dill