yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] :
Just rename download.php to kernel.zip. You don't really need to put kernel, just rename the extension, but renaming to kernel will make your life easier.
[Galaxy S II Original Android Development] remorema:
hey guys what are the best preformance config in gpu settings?
[Galaxy S II Original Android Development] AvRS:
I don't think it's right to re-create something that is already here, it only clutters up the forum with duplicate threads and confuses people having multiple threads for the same thing. I've already offered to help, if he's no longer got the spare time to maintain it but he's just away that's all so give him a chance and he'll be back.
[Galaxy S II Original Android Development] bajee11:
Well I noticed that you just got involved in this thread recently. He usually updates the OP regularly but he's just away for a few days, that's all. ;)
[Galaxy S II Original Android Development] :
The best you find. There isn't a "best config" for every one. But ME, I'm using 160[850mV]-267[925mV]-267[925mV]. Please, do not try those UVs. Use stock, and if you know how to undervolt very well, undervolt. :) PS: use the frequencies you think you need to use.
[Galaxy S II Original Android Development] myfluxi:
Kernel Update Fluxi ICS XX.02-beta2

OTA or direct download:

CWM ZIP: fluxi-kernel-sgs2-XX.02-beta2.zip

Odin TAR: fluxi-kernel-sgs2-XX.02-beta2.tar

Update xxTweaker v0.3.9_beta4

OTA or direct download: fluxi-xxTweaker-0.3.9_beta4.zip

Changelog:

kernel: Update to Linux 3.0.34

kernel: mach-exynos: cpufreq: Align with Samsung i9300 Update 1

ramdisk: More CM9 changes (fix charging gfx)

xxTweaker: Change backup directory to {internal SD-Card}/xxTweaker, to make it accessible via MTP or mass storage

xxTweaker: Kernel compatibility check on startup, if not ask to download (i.e. after ROM update)

xxTweaker: Check for changed Exynos sensor HAL, if yes ask if user wants to switch back (i.e. after ROM update)
[Galaxy S II Original Android Development] :
I actually can agree a bit with him. I can't not thank xator, he brought us this amazing kernel. But fluxi is the owner of all this. If fluxi wants to create his own thread, the mods could merge them. I really don't care about it, I just want to xator update it [don't need to be everyday, but now it's 10 days late], but as bajee said, he's away right now, so, no problem :)
[Galaxy S II Original Android Development] bajee11:
Right on time for my ROM update as well! Thanks!
[Galaxy S II Original Android Development] :
Wow, thanks a lot. Linux 3.0.34 already? damn...
[Galaxy S II Original Android Development] myfluxi:
I will open a new thread once I have the time. Everything will be merged, nothing will be lost.

It's just the thread, kernel and satellites are what matters.
[Galaxy S II Original Android Development] :
Sure. Well, now it's showing the charging animation, but it's normal to have the backlights on? It's like the device was turned on.
[Galaxy S II Original Android Development] AvRS:
From what I remember the first and only time I charged the phone while off it does turn the backlight on as the phone is still on in a low power state in order to charge just not powered up into the system that's all so this is normal.
[Galaxy S II Original Android Development] superleeds27:
Does 'Triangle Away' work if im using this Kernel

Edit: Works fine. Although after doing it, the app doesn't want to uninstall! ah well!
[Galaxy S II Original Android Development] AvRS:
I've just tested the charging animation and after a small pause it does kick in. One thing I noticed after unplugging the phone (using USB to PC) the screen switched off then back on and continued the charging animation which was strange. Was possibly because I literally had it plugged in a few seconds just to test it works for Slim which it does so doubt people would do this and reproduce it but thought I'd let you know.
[Galaxy S II Original Android Development] Honusnap:
It was just a suggestion.. :), i've nothing against the thread creator. I was guessing that it would be easier if the thread was maintained by someone that is involved like AvRS / Fluxi. In general i'm looking at the hilfe.de website cause it's the most up to date.
[Galaxy S II Original Android Development] yahyoh:
ya it will be better idea :rolleyes: cuz the op here gone :D
[Galaxy S II Original Android Development] remorema:
I do know how to undervolt/overclock. was an overclocking freak back in the old intel prescott days ;)

the thing is about tweaking thresholds. by default the medium thresholds are configured 80 up 89 down !?!?!?

that leaves me kind of confused how can the down value be higher than the up?!?!?! this way it will never use step 3 right?
[Galaxy S II Original Android Development] :
I think it's like this. When it goes a step up, the load goes down, as a higher frequency loads less and a lower frequency is much loaded. Let me try to explain to you. If i'm on 160mhz, when it load gets to 80%, it will go a step up, to 267. On 267, the load will reduce, like to 40%. If the load gets lower than 40% on the 267 frequency, it will go back to the 160 step, and the load will be 80% again. Someone correct me if I said anything wrong, my english also didn't go out very well this time...
[Galaxy S II Original Android Development] bajee11:
Fluxi XX.02-BETA2 Giving out Status 7 error if you try to install any ROM. Do not flash until fixed by myfluxi.
[Galaxy S II Original Android Development] powermax91:
WTF? are you sure? :eek:

if i flash a another kernel, will this error appear, or its only when flashing rom?
[Galaxy S II Original Android Development] :
No problem here buddy... Installed a CM9 update and it's perfect. Try downloading again, flashing another recovery.
[Galaxy S II Original Android Development] shadowblade330:
so just stick with beta 1 after we flash RootBox 1.1?
[Galaxy S II Original Android Development] bajee11:
Okay guys. This is the issue.. If you reboot into recovery, you cannot flash any another ROM anymore, you will get status 7 error. At least, any AOKP rom.

Fluxi XX.02beta2 is the one responsible for the Status 7 error because I flashed Resurrection Remix ROM 2.2 and then Fluxi XX.02beta2 and I'm still getting status 7 error if I try to install any other ROM. I tried flashing the same thing with Siyah Recovery, and it works.
[Galaxy S II Original Android Development] remorema:
i get the point. but since we are talking about the medium frequency that has a higher and a lower value, the lower value should always be lower than the higher. otherwise it will never go to the following and last step. Im either right or confused :p
[Galaxy S II Original Android Development] :
The lower value should be always lower than the higher. Hahaha, don't tell me :P I think I was a bit confusing.
[Galaxy S II Original Android Development] bajee11:
Fluxi XX.02-beta2 Recovery Issue

If you boot intro recovery, you will not be able to flash roms (Apparently works for CM9)

Solution:

Download XX.02-beta1 or any other kernel

Reboot into recovery

Flash XX.02-beta1 or any other kernel

Wipe Cache/Dalvik

Reboot Phone

You should now be able to flash any rom without Status 7 error.

** Can anyone else running XX.02-beta2 confirm this Error Status 7 as well? I tried flashing different Roms and even downloaded XX.02-beta2 three times. (So it is not a bad download)
[Galaxy S II Original Android Development] :
Confirm. Recovery isn't recongnizing the

assert(getprop("ro.product.device") == "galaxys2" || getprop("ro.build.product") == "galaxys2" ||

getprop("ro.product.device") == "GT-I9100" || getprop("ro.build.product") == "GT-I9100" ||

getprop("ro.product.device") == "GT-I9100M" || getprop("ro.build.product") == "GT-I9100M" ||

getprop("ro.product.device") == "GT-I9100P" || getprop("ro.build.product") == "GT-I9100P" ||

getprop("ro.product.device") == "GT-I9100T" || getprop("ro.build.product") == "GT-I9100T");

from the script. Just take this off and you are fine.
[Galaxy S II Original Android Development] bajee11:
Yea mate, we both know that.. But an everyday/unexperienced user wouldn't dare do that, that's why I posted the warning. ;)
[Galaxy S II Original Android Development] :
They can do this to use the beta2: flash beta1, reboot to recovery, install the ROM with this unrecongnized code from script which beta2 can't process, flash beta2 and done. I won't downgrade to b1 just because of this.
[Galaxy S II Original Android Development] shadowblade330:
how do you remove script if someone was to do this is it as easy as going into file explorer and deleting those lines in the a certain config file?
[Galaxy S II Original Android Development] bajee11:
Did you understand what I said?

Unexperienced

user will have a hard time if they want to upgrade their ROM later on while using beta2 unless the dev takes care of it. I'm not doubting on your capacity of using beta2, because I was using it as well until I decided to flash something else. It is a hassle to go through the trouble of changing kernel or getting rid of that stretch of code.

---------- Post added at 10:21 PM ---------- Previous post was at 10:20 PM ----------

He's talking about the updater script located in the zip file.
[Galaxy S II Original Android Development] shadowblade330:
ok yea i always have a hard time during the compiling part only know how to decompile lol
[Galaxy S II Original Android Development] :
Relax dude... Just posting here a solution :) If you posted the problem, post a solution. For sure they will come here to complain about this, so we already have a solution.
[Galaxy S II Original Android Development] bajee11:
Hm really? I posted the solution last page and you even quoted my solution :)
[Galaxy S II Original Android Development] :
You have posted a solution, and it was flashing b1, haha. My solution finishes using b2.
[Galaxy S II Original Android Development] bajee11:
I give up, you don't get it mate :) Your solution finishes with the b2 recovery that has the issue. Congratz for that. If someone wants to flash again, they'd have to redo all these steps again? I don't care personally for myself.. but it will be troublesome for all others. ;)
[Galaxy S II Original Android Development] :
I don't see why someone is going to flash a ROM so many times... At least one time per day, it doesn't take long... but dude, you need to relax a little bit.
[Galaxy S II Original Android Development] bajee11:
Lol I'm not tensed mate.. I flash 2-3 roms a day as I support them through mods and fixes for several things, so this issue is disturbing for me. And I have my own rom to manage as well, and I already got a few users complaining to me about the issue. So it is my duty to come here and tell everyone to avoid it until the issue is fixed. Unless they're willing to go through the trouble of doing that solution. Am I right? ;)
[Galaxy S II Original Android Development] nehalem176:
Proud that i know you since hydro, mate. Your title recognized contributor not for nothing. Thanks mate.
[Galaxy S II Original Android Development] :
For you. But for those who don't need to flash 3 roms a day, just 1 or even 3 per week, they can stay on b2 and it won't be disturbing :) Glad we got in a agreement.
[Galaxy S II Original Android Development] twirtle2:
I'm having this issue as well. I'm guessing xeigen like me has the LED lights set to always off and only turn on for BLN notifications. The problem doesn't seem to occur when conducting a one-off test in xxTweaker.
[Galaxy S II Original Android Development] bervin:
what a douche:rolleyes:
[Galaxy S II Original Android Development] kalpik:
And I hit the infamous "slow-motion" bug with with Beta 2. It was more pronounced on some siyah kernels. But just now got it with Fluxxi.
[Galaxy S II Original Android Development] pro.aggro:
Any zip file or just roms?

I can flash other kernel. but i don't try a rom.

It also does not occur, when BLN shows a missed call. LED's only stay on, when a message (SMS, Whatsapp etc) is received.
[Galaxy S II Original Android Development] sakindia123:
what is the "slow-motion" bug?
[Galaxy S II Original Android Development] kalpik:
The UI becomes SUPER slow.. Can't do anything but a hard reboot via keeping the power button pressed.
[Galaxy S II Original Android Development] pro.aggro:
Regarding to status 7 error: I can flash Roms without having this issue!

I made a backup and tried some files. Everything works.
[Galaxy S II Original Android Development] myfluxi:
1. The "Status 7" error is not a direct kernel issue, since it happens with backups of XX.01 as well.

2. Flashing other Zips works.

3. And edit: CM users on plain CM with a stock CM kernel report the same issue.

CM changed something and we have to find out what it is.
[Galaxy S II Original Android Development] Honusnap:
It have no sense for me neither

As an example, what should be my threshold Down if my Threshold Up is 80% ? :

State 1 : 100Mhz (threshold Up : 80%)

State 2 : 200Mhz (threshold Down : ?)

If threshold up is 80% (80% cpu charge or more is held for the sampling interval) THAN (for me) threshold Down from the second state should be less than 80/(200/100) = 40% or it could instantly ramp up again if it goes down to state 1.

THRDD = THRDU / (PISNB / PISNA) - OVER

With :

PISNA : Performance Index Step n => let's say same as the frequency here = 100

PISNB : Performance Index Step n+1 => let's say same as the frequency here = 200

THRDU : Threshold Up = 80%

THRDD : Threshold Down

OVER : Overlap % (I use 5% to 10%)
[Galaxy S II Original Android Development] lyndonguti:
Im planning to buy 2000mah battery...just asking if that will change something....and if this kernel is compatible with?

sent from my lovely phone....hmmm wait its a tablet...waaa i dont really know.....im PARANOID NoW!
[Galaxy S II Original Android Development] ram3n:
Lolz, I guess your batterylife will get improved by +25% better :rolleyes:

Plus, I can't believe that one battery isn't compatible with a kernel.

You made my day bro ! :D
[Galaxy S II Original Android Development] lyndonguti:
Booya! XD cheers

sent from my lovely phone....hmmm wait its a tablet...waaa i dont really know.....im PARANOID NoW!
[Galaxy S II Original Android Development] pro.aggro:
Instead of a bigger battery buy a Flux capacitor.

Sent from SGS II powered by PARANOIDANDROID
[Galaxy S II Original Android Development] Honusnap:
Majority of so "2000mah" batteries do not really have this capacity, worse .. they can have less than an original one. The only way to have a higher capacity in the SAME size package is to wait for a new technology...

Li-ion as far as i know got the best capacity's density, Li-Poly is lower... but lighter.

In one word ... stay with the original one or get an oversized extended battery if you really wants capacity.

---------- Post added at 02:31 PM ---------- Previous post was at 02:25 PM ----------

Take care when using this, your phone can be sent back to the future .. :D
[Galaxy S II Original Android Development] superleeds27:
So you're saying the official 2000mah battery is pointless :s
[Galaxy S II Original Android Development] lyndonguti:
But its samsung made...do they really gonna mke a battrey that has less duration?

sent from my lovely phone....hmmm wait its a tablet...waaa i dont really know.....im PARANOID NoW!
[Galaxy S II Original Android Development] Honusnap:
Read carrefully .. i said "SAME" size, the original 2000mah is bigger than the stock one, reason it comes with a new back.

Let's say that energy density is directly connected to the technology

- Li-Ion (110-160 Wh/kg)

- Ni-Mh (60-120 Wh/kg)

- Ni-Cd (45-80 Wh/kg)

=> There is no Li-Ion battery being the same size of the stock one that is capable of having 2000mah.

=> A bigger battery can have a higher capacity at the same technology or higher.

=> The original 2000mah is bigger and certainly have the claimed capacity.

=> Chinese low cost having the same size as the original DO NOT have a higher capacity, most cases it's lower.

=> Chinese low cost having a bigger size as the original GENERALY have a lower capacity than the original.. being builded with low quality material.
[Galaxy S II Original Android Development] f100cleveland:
I have the Samsung 2000mah battery that came with the bigger back and it works great with this kernel or anyone I've tried. The extra battery capacity was very beneficial.
[Galaxy S II Original Android Development] remorema:
got the first part. second part confused me.

Ill try to example:

low step 100 mhz

mid step 200 mhz

high step 400 mhz

if low step threshold up is 80% it means it will ramp up when you reach 80 mhz.

so in mid step when 100% equals 200mhz you should have a down threshold of aprox 40% (give or take) that will equal the same 80mhz that were needed for low step ramped up in first place.

now comes the confusing part. how can I set a up threshold lower than the 40% mentioned above???

in my pov the logical configuration to complete the example is a mid step up threshold of 80% so it can ramp up to step 3 at aprox 180mhz, and a high step down threshold of 45% so it can revert back to mid step at aprox the same load that it went up (180mhz)

please can someone take the time to clarify this. because if this works as I think using XX.01 final, the gpu with the default settings will never go higher than step two that is 160mhz
[Galaxy S II Original Android Development] PieR:
Yep

Had this error too. I downgraded kernel, flashed rom and upgraded back :-)

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Original Android Development] Honusnap:
State 1 is fixed at 100Mhz, 80% do not mean 80Mhz. It ramp up when CPU AT 100Mhz is used at more than 80%.

You've got a one litter bottle, you'll need a second bottle (state 2) when the first one is filled at 80% => 80cl.

The Cpu charge is calculated at each frequency, let's take this for true :

- 100 Mhz means PerfIndex of 100

- 160 Mhz means PerfIndex of 160

- 267 Mhz means PerfIndex of 267

A good setup would be :

Threshold Up : 1->2 : 80%, 2->3 : 90%

Threshold Down : 2->1 : 80/(160/100)-5 = 45%, 3->2 : 90/(267/160)-5 = 45% = 49%

Or something that ramp up more easily :

Threshold Up : 1->2 : 60%, 2->3 : 70%

Threshold Down : 2->1 : 60/(160/100)-5 = 33%, 3->2 : 70/(267/160)-5 = 37%
[Galaxy S II Original Android Development] superleeds27:
Well yeah thats obvious really. Like the Ankher 1900mah battery. Same size as the Standard battery. I highly doubt its 1900Mah at all!
[Galaxy S II Original Android Development] bervin:
I've been using my anker batt's for almost a year now and i rotate my 3 batteries (2XANKER, 1XSAMSUNG 1650mah) never plugging in my phone and i can say that the anker always gives my phone a longer mileage even after a year's usage.. They may not be 1900's but they sure are more than 1650
[Galaxy S II Original Android Development] yahyoh:
but downgrading to beta1 and flashed ok no error 7 :rolleyes: on cm updating
[Galaxy S II Original Android Development] :
Well, I can't see any changes on the getprop part. The binary is also the same. Did you make any change on the recovery part from b1 to b2? If you flash b1 it will flash the ROM perfectly, and i've never got this error. I really can't figure out any small changes besides the "retouch_binaries".
[Galaxy S II Original Android Development] rashidkhan:
Its definitely an error with "Fluxi XX.02-BETA2" Kernel.
[Galaxy S II Original Android Development] pro.aggro:
Here is a workaround from myfluxi posted on android-hilfe.de.

Just delete the following part with Notepad++ from /META-INF/com/google/android/updater-script
[Galaxy S II Original Android Development] Honusnap:
Yes it is but not for everybody .. ;)

---------- Post added at 07:03 PM ---------- Previous post was at 07:01 PM ----------

Perhaps your stock one is not a good sample
[Galaxy S II Original Android Development] rashidkhan:
Re: "UnicornPorn.apk" in "System\app", after reading on forums apparently its a live wallpaper called "Phase Beam" but its apk is called "UnicornPorn.apk" but the Phase Beam Live Wallapaper from Play is not called "UnicornPorn.apk". Why is this live wallpaper included and why is its name "UnicornPorn.apk" ? Isn't this strange?

I do sometimes suddenly get a spam web page in Chrome Beta while browsing through XDA & its always the same page. I have checked my phone for any addons etc but its clean.

What could be causing this web page to suddenly popup on XDA (it only happens while on XDA) ?

Anyone?
[Galaxy S II Original Android Development] bajee11:
First of all, this is a kernel thread. Unicorn porn is a Live Wallpaper made by AOKP, and it is not Phasebeam. Phase Beam has its own apk.
[Galaxy S II Original Android Development] yahyoh:
thats not the solution bro cuz beta1 has no problem i think there is something with recovery :rolleyes:
[Galaxy S II Original Android Development] AvRS:
It's not intended as a solution but just a workaround until the cause is found, hence workaround ;)
[Galaxy S II Original Android Development] :
It's a solution, but not the best. Taking this off from the script will "fix" the status 7.
[Galaxy S II Original Android Development] AvRS:
I'm not sure if it helps but I've just tested a kernel built from your sources (compiled by krarvind) and the problem is not there as I was able to flash Slim ICS which uses an assert script so could it be the changes that were made to ramdisk? Maybe reverting those changes might get it working again till you can work around whatever's changed? Just an idea.

Thanks
[Galaxy S II Original Android Development] THE RED BLUR:
LMAO!! Best back to the future reference yet. :D

Using Resurrection Remix AOKP ICS version 2.2 powered by Siyah 3.2.7.2
[Galaxy S II Original Android Development] remorema:
yeah I know it doesnt mean mhz. I just used it as an example thr same way you used cl and bottles :p

I agree with your example. so. how can it by default in this kernel the second step gpu threshold down is 89 and the threshold up has a lower value like 80?

thats what confusing me in first place. :s
[Galaxy S II Original Android Development] myfluxi:
Kernel Update Fluxi XX.02-beta3

OTA or direct download:

CWM ZIP: fluxi-kernel-sgs2-XX.02-beta3.zip

Odin TAR: fluxi-kernel-sgs2-XX.02-beta3.tar

Changelog:

Ramdisk: Hotfix /system mounts, an error in CM? Why different mounts mounts in lpm.rc and recovery.rc?
[Galaxy S II Original Android Development] AvRS:
Good to see you managed to fix it, we knew you would of course ;) Obviously one of those things that just slipped through.
[Galaxy S II Original Android Development] Honusnap:
:)

There was a problem with older version of xxTweaker, it swapped values from Up threshold / down threshold .. perhaps it is the reason you've got these strange values.
[Galaxy S II Original Android Development] myfluxi:
I have taken an errorous CM commit, which I should have tested before. But I rarely flash ROMs, maybe once a week or two...

https://github.com/CyanogenMod/andr...mmit/ef6da568af61d1ee479ba0b4f52c38a39ec2527c

Oh, and while looking for workarounds in recovery I implemented a user request, a shutdown option in Advanced menu and corrected a nice typo. Will update my repos soon. :)
[Galaxy S II Original Android Development] bajee11:
It's not your fault. Thanks for the fast fix though, it is very much appreciated by everyone
[Galaxy S II Original Android Development] remorema:
that makes sense. I was going crazy on these values. lol. heres a screenie.
[Galaxy S II Original Android Development] :
Anyone is getting fcs while opening System on xxtweaker?
[Galaxy S II Original Android Development] Honusnap:
I know, was having the same problem.. was mad with these value no sticking to the one i fixed, than reported the bug to Fluxi who corrected it.

---------- Post added at 11:28 PM ---------- Previous post was at 11:27 PM ----------

Cwm => reset xxtweaker settings.. well i did not found a better way of fixing fc in xxTweaker..
[Galaxy S II Original Android Development] myfluxi:
It's hard to be more unspecific - logs or it did not happen, especially from peeps who seem to hang around here all the time ;)

Why did I implement the easiest method of all methods to generate a full set of logs if nobody appears to make use of it? Anybody know?