yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Yom:
Home button not working anymore and other woes

Hi all,

I am sad to report an apparent huge set of bugs in this 1.3 here kernel:

1- Yesterday my home button seemingly stopped working. Not in the ROM or in Recovery. However, the Key test function did return a numeric value (102) when hitting the home button. It did not, however, perform any other function.

2-In an effort to fix this, I wiped data and re-flashed the ROM (6.1.17). I immediately proceeded to flash Pongster's MattedBlack surgeon. I found then that the APKs being themed by it were all 0KB in size. Home button still not working.

3- Home button works as expected in RedPill 1.2 and NEAK kernels. It also works OK in Resurrection ICS. So this seems to be a bug with the 1.3 Kernel as flashing it again renders the home button inoperable again.

4- No surgeons flash OK under any kernel (themed apks end up as 0KB files)... wondering if this signals a hardware failure?

Anyone else experiencing this?

Thanks!
[Galaxy S II Original Android Development] D.O.C:
Yom, I have 0 issues of the ones you describe here. Surgeon flashes ok, kernel and home button is working as expected.

Nevertheless, I remeber that, in early dev days, modding certain framework files caused that home button failure, but fixed itself after a reboot. Tha issue has not happened since about 4 months ago (to be more specific, it was while re odexing the files using a script)

Since its release days ago, no one has reported that.

What I would do in your case, considering the information given, is

Restock

Reroot and wipe all partitions (jep including internal sd)

Flash redpill kernel and then flash hyperdroid base, no surgeons.

Pray that your issue is not there (could be hardware failure)

Keep us posted bro, good luck. I know you will eventually figure it out ;)
[Galaxy S II Original Android Development] mbutandola:
Wouldn't he lose redpill 1.3 if he flashes the base afterwards as it comes with an older version ?

Envoyé depuis mon GT-I9100 avec Tapatalk
[Galaxy S II Original Android Development] D.O.C:
No idea, there are sooo many variables that could cause that sort of bugs.

For instance, lately I have been having trouble with bt and gps, only to find out that partition formating was the issue, and not libraries as I suspected. I have said it before, android is just a too noble OS, even with corrupted partitions it boots and tries to work.

That is why my suggestion to restock. There are some partitions we dont ever touch, that could vary amongst our devices when flashing roms through odin.

Restocking and starting from scratch is the only way I know that we can start from point 0 to somewhere.
[Galaxy S II Original Android Development] jermitano:
would flashing kernel a lot or doing kernel abuse cause efs corruption?
[Galaxy S II Original Android Development] Yom:
Thanks, hermano!

Well, I tried what you suggested:

1- Re-stocked to the ROM that came with the phone

2- Flashed CF Root Kernel

3- Backed up and formatted my internal SD (full format, 32KB clusters)

4- Formatted all partitions

5- Flashed RedPill 1.3 via ODIN (home button stopped working, again :()

6- Flashed HD ROM. Home button still not working.

Funny thing is that the button does work an all other kernels, but what really bugs me is that the surgeons and themes end up writing a 0KB APK to the system, no matter what surgeon or theme are flashed under what kernel.

I am thinking that maybe I should do a restock but re-partition the phone as well. Do you know where I can find a PIT file for the SGS2?

Gracias!
[Galaxy S II Original Android Development] pongster:
Home button works here as expected. My surgeon disables home button from waking phone though as I like using the power button only.
[Galaxy S II Original Android Development] veyka:
EFS corruption is seemingly random, I have had it once during a kernel flash, but I had tons of backups, make sure you have backups.

People have had it corrupt during rom flashes, or modem flashes, its unpredictable.
[Galaxy S II Original Android Development] Must2r4h:
Agreed. I've lost it once after reboot. Tons of backup of your efs is highly recommended.
[Galaxy S II Original Android Development] jermitano:
never had it though but sometimes you cant tell, seeing someone have it sometimes gives me a wake up call that im doing sometimes is risky...but hey with the precautions...seems like cancer the cause of it is idiopathic:D

---------- Post added at 11:15 AM ---------- Previous post was at 11:14 AM ----------

yup...got one in my pc, my lappie, my netbook, 2 memory cards, in my other galaxy phone hahaha...scary to lose it...:p
[Galaxy S II Original Android Development] pongster:
What for? Did you read the 1st page, specifically the FAAAQ?

My download server deleted the file as it was generating too much traffic. :)

Updated OP and we're now using veyka's Mirrors as the main Link. (Thanks veyka!)
[Galaxy S II Original Android Development] Yom:
Hey... Could it be possible that my issues are being caused by a corrupt EFS? What are the symptoms of that? How do I diagnose it?

Posted via my hacked, rooted, bad-ass SGS2
[Galaxy S II Original Android Development] Must2r4h:
Caused are hard to determined.

If you loose your efs. Your phone will go into flight mode. No phone signal. Your baseband version will be unknown. you will lose your imei number.
[Galaxy S II Original Android Development] qureyoon:
Looks like a corrupted theme there.

Probably open the theme .zip and see if the .apk are not 0KB.

Re-download the theme .zip and re-flash it.

If you didn't flash the theme, is everything ok?
[Galaxy S II Original Android Development] coloxim:
Yes..but there isn't a instruction for modification them..so I use conservative that I know what Change( up/down_ threshold etc...)

Where can I find more information about your governor?

Thank you so much..

And sorry for my English..
[Galaxy S II Original Android Development] pongster:
Read the commit log and the actual commits from the source.
[Galaxy S II Original Android Development] coloxim:
OK thanks...I ll search it ..

Anyway very nice kernel..

Just one thing in stan by sometime my phone stay wake..I don't have processes.. but in battery start I've seen it:

By the night my phone stay awake for few minute..
[Galaxy S II Original Android Development] noke955:
You could try to disable "fast dormancy" with *#9900#
[Galaxy S II Original Android Development] coloxim:
OK..this night I ll try again with fast dormancy off..
[Galaxy S II Original Android Development] culbuto:
Thanks for your reactivity.
[Galaxy S II Original Android Development] Lownita:
What governor/scheduler would give the best performance, regardless of battery life? I think hyper as governor, but what should be the scheduler of choice? :)
[Galaxy S II Original Android Development] coloxim:
For me all of this governor use too much 1200 ...the only one that use all freq is Conservative..
[Galaxy S II Original Android Development] qureyoon:
Because this kernel lean toward performance more, with battery life in mind.

The concept is to have the phone fast and smooth when in use. And not drain battery when in idle.
[Galaxy S II Original Android Development] Inovator:
I migrated from Siyah to RedPill, and so far I'm satisfied. Only thing I'd like to mention is freq levels, we have 100, 200, 500, 800 etc. Why devs don't implement 100MHz incremental levels like 100, 200, 300, 400 etc?

tnx
[Galaxy S II Original Android Development] veyka:
Because it takes time and "costs" performance to jump between freq steps. When the cpu is swapping state, it cant do "work", so the more steps there are, the more time it spends jumping, and less time working. So you want steps that fit different workloads.
[Galaxy S II Original Android Development] pikachu01:
It'll scale slower leading to lower performance?
[Galaxy S II Original Android Development] Entropy512:
Yup, and since the CPU can shut off the clock (and sometimes the entire core) when idle, dropping clock speed at partial load saves less power than you might thing.

In every single test I've run, allowing 100 MHz operation actually consumed more power than 200 - this seems counterintuitive, but since it's not possible to drop the voltage for 100 much lower than for 200, it is, for example, better to spend 30% of your time running at 200 and 70% in AFTR or LPA than to spend 60% of your time running at 100.

(It's especially bad to have extra steps with Conservative, even tuned conservative. Also, the CPU has some limiters that prevent jumping more than 2-3 steps at a time with other governors.)
[Galaxy S II Original Android Development] leongzxc:
used to use redpill v1.0, but battery life wasnt good,

switched to speedmod, battery life was average..

but then decided try redpill 1.3 again..

and wow, since 3am till (now around 8pm, battery lost is only about 27% compared to the usual almost 60% after 8 hours!)

Thank you very much for this kernel! :D :D
[Galaxy S II Original Android Development] Lownita:
The touch recovery is a bit hard to use sometimes. Because when I touch a button, it gets triggered 2 times in a row.
[Galaxy S II Original Android Development] It_ler:
No problem for me with touch recovery.

Alternatively you can use buttons to navigate (Volume UP + DOWN) and select items (Power button).
[Galaxy S II Original Android Development] coloxim:
sorry pon...i love your kernel....but not your governor...

i'm sorry...

please...add more...
[Galaxy S II Original Android Development] qureyoon:
Well I'm sorry too. But this is stupid request.

What governor are you asking?

Did you not know how to be specific when asking?

If you don't know what governor, find some other kernels.

RedPill is not for you.

Simple?
[Galaxy S II Original Android Development] Steven6489:
It's the best alternative for me which having problem with the home button.. :D
[Galaxy S II Original Android Development] GalaxyFan88:
I agree, the touch sensitivity seems to be too high, most of the time im also facing this problem, so im ending up making interactions with the menu which i actually don't want to trigger.

Other than that everything works just fine.
[Galaxy S II Original Android Development] coloxim:
hey...you are a funny boy...

tell me

I want smartassv2 ...or Lulzactive...or lazy..

tell me why my request is so stupid "funny boy".I love this kernel but i love a customizable phone too...

and i don't know why i can't put the Sampling rate under 100000 in conservative governor...it's only my problem?
[Galaxy S II Original Android Development] jermitano:
please read first posts and posted logs by the dev concerning scheds and governors
[Galaxy S II Original Android Development] coloxim:
I've read but I didn't understand very well...

I said that now all things are more easy..but not for me..

I can't set conservative like I want..and the others governor use the CPU to much..my CPU stay too much at 1200 when there is not need..

Inviato dal mio GT-I9100 usando Tapatalk
[Galaxy S II Original Android Development] qureyoon:
There you go Uncle :) Be specific.

Say, "can I have smartassv2, lulzactive, lazy?"

If you just mentioned, "I want more governor"

Who in the world would understand what u want? Hence the 'stupid request' there.

If you want more customizations you can always go with other kernels ;)
[Galaxy S II Original Android Development] coloxim:
Ok..traditional governor, Is better? OK..ill try another kernel..but I love this one..

It was only the request..and other person think the same thing..never mind..

Thank you.

Inviato dal mio GT-I9100 usando Tapatalk
[Galaxy S II Original Android Development] Hgshgs:
Hi pongster,

This is my dmesg log when trying to connect an Fiio E10 USB DAC to my SGS2 using RedPill 1.3 and a powered HUB

<6>[ 233.099870] otg_dbg: in otg_handle_interrupt()::00087
<6>[ 233.100303] => Port Interrupt
<6>[ 233.101056] otg_dbg: in process_port_intr()::00259
<6>[ 233.101756] => detect connection
<6>[ 233.274638] otg_dbg: in root_hub_feature()::00493
<6>[ 233.275443] => case SetPortFeature -USB_PORT_FEAT_INDICATOR
<6>[ 233.307779] max17042 9-0036: max17042_get_soc : soc(0ea5)
<6>[ 233.308203] max17042_need_soc_recal: HW(0xe)
<6>[ 233.308936] max17042 9-0036: max17042_get_soc : use raw (14), soc (14)
<6>[ 233.399527] otg_dbg: in root_hub_feature()::00483
<6>[ 233.400235] => case SetPortFeature -USB_PORT_FEAT_RESET
<6>[ 233.461103] otg_dbg: in otg_handle_interrupt()::00087
<6>[ 233.461802] => Port Interrupt
<6>[ 233.462530] otg_dbg: in process_port_intr()::00271
<6>[ 233.462924] => port enable/disable changed
<6>[ 233.534333] usb 2-1: new high speed USB device using s3c_otghcd and address 2
<6>[ 233.555713] hub 2-1:1.0: USB hub found
<6>[ 233.556778] hub 2-1:1.0: 7 ports detected
<6>[ 233.784657] usb 2-1.6: new full speed USB device using s3c_otghcd and address 3
<3>[ 233.785290] usb 2-1.6: device descriptor read/64, error -71
<3>[ 233.889676] usb 2-1.6: device descriptor read/64, error -71
<6>[ 234.024472] usb 2-1.6: new full speed USB device using s3c_otghcd and address 4
<3>[ 234.025052] usb 2-1.6: device descriptor read/64, error -71
<3>[ 234.129811] usb 2-1.6: device descriptor read/64, error -71
<6>[ 234.244673] sec-battery sec-battery: sec_bat_check_vf: Battery Health (1)
<6>[ 234.264521] usb 2-1.6: new full speed USB device using s3c_otghcd and address 5
<3>[ 234.674459] usb 2-1.6: device not accepting address 5, error -71
<6>[ 234.704858] usb 2-1.6: new full speed USB device using s3c_otghcd and address 6
<3>[ 235.114454] usb 2-1.6: device not accepting address 6, error -71
<3>[ 235.114801] hub 2-1:1.0: unable to enumerate USB device on port 6

I´ll try without the USB HUB but I need to make a special cable to power my DAC. I tried with ZOOM H2 recorder with the same results.

Great kernel and thanks for developing this feature, there are a lot of people looking for this,
[Galaxy S II Original Android Development] jermitano:
as a disclaimer posted they made the rom and the kernel as they saw fit for their use so it is your personal discretion if you want to use it yourself...if you want a tweakable kernel that can suit your taste you can use those with the govs/scheds you need...no disrespect meant just communicating what i guess needs to be addressed...:)
[Galaxy S II Original Android Development] dankeanke:
Tested the Rev1.3 for one day now,

I also would say, that the touch sensitivity seems to be too high.

But thats not the point why I'm going back to Rev1.2.

-> the Point is, that my I9100 started to heat up all by itself;

I got it in my trouser pocket and thought "what the hell..." because it was so hot.

I attempted to turn on the Screen, but nothing happend, take out the battery was the only chance to stop it heating-up.

When the phone rebooted i could see, that it lost about 50% of battery in a few Minutes...

Anyone else got similar problems?
[Galaxy S II Original Android Development] It_ler:
Oh you got a pocket heater ;-)

Try to wipe cache and Dalvik cache in recovery mode.

This may help.

If not, try to flash the kernel again.

Good luck !
[Galaxy S II Original Android Development] cruzargel:
Im using hyper sio 1ghz max 100mhz min. Is that a good combo? And when I uninstall setcpu, then what would be the default scheduler and governor be?

________________________________

GT-I9100

CheckROM V6

Red Pill 1.3

ICS Domination V2
[Galaxy S II Original Android Development] hp13:
Doc is right. Just follow his method. It should fix it. I experienced it but then it worked flawlessly after.
[Galaxy S II Original Android Development] dankeanke:
... a really expensive pocket heater ;-P

seems like this works for me,

wiped the caches and since that the system is up and running as a Smartphone and not as a heater!
[Galaxy S II Original Android Development] tendan:
50°C using mhl connector (hdmi+ charging). I don't remember exactly the temperature with others kernels but a bit lower sure, 42-45. I think it's too much. Excepting this problem the kernel works very nice. Thanks for your work.
[Galaxy S II Original Android Development] d3l1:
Is there a setting I'm missing so Tapatalk can show me what's inside the first post? My Tapatalk just shows an empty post because it seems like it can't show those CODE (or whatever they are) segments, just like when you try to quote the first post it only quotes some text and two links (falsified the tags so you could see what is being quoted from the first post, the rest is left out):

[Q.UOTE=pongster;18115851][.B]Kernel Source: [u.rl]https://bitbucket.org/sarcastillo/ultimate-kernel-sgs2[/u.rl][./B]

MatrixPills Image by Corinne Wilger. Visit her site [.B][U.RL="http://www.wix.com/cwilger/photo"]HERE.[/U.RL][./B][/Q.UOTE]

SORRY for the offtopic post but tapatalk can't handle the first post thus it can't tell me when an update is out, I always have to go to this thread via the browser.
[Galaxy S II Original Android Development] stylez:
Must be the code as same here.

Sent from the valley of the shadows....
[Galaxy S II Original Android Development] cruzargel:
what's the default min and max freq? also the governor and scheduler. I would really appreciate your replies.
[Galaxy S II Original Android Development] malhor:
Yes it is a issue with tapatalk. However, pongster always update the post title when there is an update and That you can see in tapatalk ;)

Send from Androidmeda with Tapatalk at hyperdroid speed
[Galaxy S II Original Android Development] jit_devil2:
hoping for someone with a fiio e7 or battery powered dac to try out connectin it to da s2 using redpill.

as far as i know dacs without batteries have trouble using the usb host in smartphones.

e.g the n8 works well with the e7 but not the e10
[Galaxy S II Original Android Development] d3l1:
Pongster doesnt accept PMs so I cant ask him to "fix" the first post. Maybe he reads it here.

Gesendet von meinem Transformer TF101 mit Tapatalk
[Galaxy S II Original Android Development] It_ler:
Default settings for RedPill rev1.3 are partly described in the fourth post (kernel changelog):

min freq = 200 MHz

max freq = 1200 MHz

i/o sched = deadline

governor = ondemand
[Galaxy S II Original Android Development] apeatan:
is there a way to manually return the screen tweak sharpness back to stock?
[Galaxy S II Original Android Development] cruzargel:
thanks It_ler

didn't know there was! lol
[Galaxy S II Original Android Development] jermitano:
thats what first posts and logs for the rom/kernel are for...not just technobabbling
[Galaxy S II Original Android Development] apeatan:
yeah i didn't see the feature at 1st post but i noticed my screen changed after flashing it on a stock rom and i noticed most of custom roms come with it so i assume the feature is built in the kernel.

i'm still at it (screen) eh?:))
[Galaxy S II Original Android Development] pongster:
I would need to change it in the source. No manual way of doing it now. When supercurio releases his screen tuning app, I may revert to all stock so his app can do its thing properly.

@all

Re: code post not being read by tapatalk, ask tapatalk to fix that feature as I'm not changing the current post structure anytime soon.
[Galaxy S II Original Android Development] pongster:
Not getting this issue here. If you don't remember exactly, how are you sure its lower?
[Galaxy S II Original Android Development] veyka:
Scratch this, I had my Visualization technology mixed up, sorry for the noise, no downtime today :)
[Galaxy S II Original Android Development] tendan:
Well.. I never see temperatures over 45°C on my device. It's the reason why I'm sure but I don't remember the degrees.

I wiped cache+ dalvik and reflashed kernel yesterday. I will try again today with mhl.
[Galaxy S II Original Android Development] apeatan:
-ah, thanks boss! so there is one.:p:D
[Galaxy S II Original Android Development] It_ler:
Results for SpeedMod / Phenomenal / N.E.A.K. / Siyah / RedPill / stock kernels

Everything is specific to my phone, my "normal" usage and my home location. Most values are exact results, but some are rounded. I usually have wifi, synch (three email accounts, calendar and news), Google Talk and Skype on.

For all custom kernels, I was running on Frankenstein XWLA4 ROM (Modem: XXKL1).

For stock kernels, I was running on the corresponding stock ROM.

Always using the Samsung's standard / stock 1650mAh battery.

For Siyah, as it has many, many configurable settings, I have changed nothing - just default settings.

For N.E.A.K. I tested VR schedule, Lulzactive governor, only enabled sched_mc and the rest unchanged defaults.

For RedPill kernel, I tested completely default settings (deadline / ondemand) without any change.

For RedPill (MC, noop/conservative), I tested geko95gek's MagicConfig v0.3.1 settings with noop / conservative on 200-1200 MHz (no UC or OC, only recommended/safe UV).

For RedPill (MC, dealine/sleepy), I tested geko95gek's MagicConfig v0.3.1 settings with deadline / sleepy on 200-1200 MHz (no UC or OC, only recommended/safe UV).

For RedPill (sio/conservative) kernel, I tested completely default settings, only changed io sched to sio and governor to conservative.

Just tested RedPill rev1.3 with different io sched / governor combinations (and geko95gek's MagicConfig), and added its results.

Here are my current results:

Benchmarks (in Performance governor if available)

Battery stats

RedPill rev1.3 has got best battery savings with sio/conservative on my phone, even without any additional UC/UC, etc.

Subjectively, it feels a little bit laggy/not as smooth as in other combinations (e.g. sio/hyper).

So, my first impression of this kernel was proven: Very stable kernel which is highly configurable to fit every demand - for performance and battery life.

Thanks again pongster for that great kernel.

And thanks to geko95gek for his MagicConfig which gave me enough confidence to test out some UV, io sched and governor changes.

Looking forward to test new versions of that kernel ...
[Galaxy S II Original Android Development] gorillaCF:
+1 to lt_ler.

i'm having superb performance and long battery life (sometimes a lil bad due to some bad apps causing wakelocks) with redpill 1.3, on sio/conservative.

its just that like what lt mentioned, performance is slightly off-ed, esp on the lockscreen where the homescreen would be flashed for a sec before going to the lockscreen.

nevertheless, great kernel, thanks pongster.
[Galaxy S II Original Android Development] d3l1:
Just had my display not waking up after a call. I could use the volume button but despite that it was like a SOD. After about falls a minute the display woke up again.

I reverted my Voltage	Control settings to default before flashing the kernel but strangely the min CPU frequency was 100, changed it to 200 maybe that was the reason.

Gesendet von meinem GT-I9100 mit Tapatalk
[Galaxy S II Original Android Development] ziroxs:
I use sio/sleepy with deactivated fast_start option. I saw never such a better mix between performance, battery life and possibility for adjustments than RedPill.
[Galaxy S II Original Android Development] d3l1:
Can Voltage Control disable the fast_start option?

Gesendet von meinem Transformer TF101 mit Tapatalk
[Galaxy S II Original Android Development] ziroxs:
No. Bur i create two cwm scripts to flash it or delete it.

First cwm script turns off fast start, doesnt matter which governor you use. The second delete the settings within the init.d folder.

If you want i can provide you the scripts.
[Galaxy S II Original Android Development] af974:
Forum runner ftw :p
[Galaxy S II Original Android Development] d3l1:
Yes please

Gesendet von meinem Transformer TF101 mit Tapatalk
[Galaxy S II Original Android Development] jermitano:
please do share it...thanks
[Galaxy S II Original Android Development] It_ler:
Could be a good idea to add this option into RedPill recovery menu.

What do you think ?
[Galaxy S II Original Android Development] ziroxs:
CWM script to turn off fast_start. Creates a init.d file for all governors except conservative.

http://db.tt/c3wmrwfX

CWM script to delete the created init.d file

http://db.tt/gEE7X9vs

I used sleep 5 in the script. When i am on tuesday at home i will change it to 30 in order to boot perhaps faster and to be sure the variable fast_start is overwritten correct.