yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] zacharias.maladroit:
ok - could those seeing that reboot issue please post a little more in detail

what you did shortly before and while the accident happened ?

several posts indicate that it's the approximation sensor but others don't

so I need more input

did "core" (not the low-latency) work for you ? I'm sure you didn't see that kind of reboot issue with it, right ?

thanks !
[Galaxy S I9000 Android Development] xdaalmar:
Yes, core was working perfect for me, and I didn't observe this with two face and miui rc5b (but it was a short time of that combination). With twoface and miui rc6, during a call, the phone reboot, I tried several times and all the times it reboots. Also, after turning off usb storage the phone was blocked for a long time.
[Galaxy S I9000 Android Development] currydude:
My hypothesis is that the people have unstable overclocks which incurred a reboot during a call. I did not have any reboot problems during a call and my overclock is 100% stable.
[Galaxy S I9000 Android Development] g00ndu:
I have the reboot problem after calling and receiving using twoface kernel. There wasn't any things in particular that I have done. In fact, I hard reboot each time when I try. The conditions which I have done:

Hard reboot

Key in sim pin

press lock and unlock to get 3g signal

use home phone to call

sgs rings and pick up (screen is still on)

place sgs near ear

proximty sensor works (screen now is off)

test on conversation

both parties can hear

move sgs away from ear

screen is still off (proximty sensor now not working)

can still hear both sides communication

hang up home phone

sgs does not have screen on (still black)

pressing any buttons doesn't help

finally sgs reboots

goes into a bootloop (miui animation)

reboot again

phone goes pass the miui animation and works as normal

I reverted back to tk-glitch kernel (v5a) and use the above method to test. Proximty sensors works and doesn't have reboot after hanging up.

Hope the above helps.

I'm on official miui (not rc6 but from miuiandroid.com). overclock and undervolted as follows

1.3ghz - 0

1.2ghz - 0

1.0ghz - 25

800mhz - 50

600mhz - 75

400mhz - 75

200mhz - 100

100mhz - 100

using pimp my cpu.
[Galaxy S I9000 Android Development] currydude:
Hmmm... I'm using RC6 + Two face and I do not have this problem.

Okay I jsut tested it again and everything is working PERFECTLY.

I have tried calling my other phone with my SGS, picked up, 5 minutes later, turn off call from other phone. SGS still works (no reboot) and proximity sensors were working.

I have also tried calling my SGS with my other phone, picked up, 5 minutes later, turn off call from other phone. SGS still works (no reboot) and proximity sensors were working.

I do not a have a key for the sim, so maybe this is the problem?

Does TKGlitch's kernel have any special scripts? It seems that people moving from TkGlitch's kernel back to zach's kernel has been causing reboot problems. Maybe TkGlitch's kernel is causing damage to people's devices and people do not realise it? LOLS

My overclock:

Mhz/UV

1200 -025

1000 -050

0800 -075

0600 -100

0400 -100

0200 -125

0100 -125

Maybe try removing the 1300Mhz?
[Galaxy S I9000 Android Development] Bonta768:
I had twoface on for 12 hours and not a problem. Then I install and use Pimp My CPU for the very first time and in half an hour I had several FCs and spontaneous reboots just trying to use Google Reader. I did not OC or change any voltages at all. Very weird.
[Galaxy S I9000 Android Development] mobilescooby:
Is anybody else getting problems with two-face when in call and the sensor deactivates the screen it not reenabling the screen when the sensor is no longer blocked?

Have tried 10 sec reset and clearing of dalvik and cache!

Any ideas anybody?

Many thanks

Edit: no overclock or undervolting running
[Galaxy S I9000 Android Development] currydude:
Many people are having problems (I do not have this problem) I recommend you go back to the core kernel and wait for zach to address this.
[Galaxy S I9000 Android Development] mobilescooby:
Yea thought that's what I'd have to do unfortunately!

Apart from this little hiccup my galaxy s has grown wings! Cos this mother flies now!

Oh well! Off to find core kernel!
[Galaxy S I9000 Android Development] currydude:
http://www.ponack.net/zachariasm/test/core/SGS/ I had problems with core "chameleon" but this core kernel is the most stable CM7 kernel available at the moment.

For me, twoface is working perfectly (including calls)
[Galaxy S I9000 Android Development] mobilescooby:
Your a prince and a gentleman!

Many thanks
[Galaxy S I9000 Android Development] currydude:
Haha, no worries mate (you should really be thanking zach for his excellent kernels), please report back if it's working for you now :)
[Galaxy S I9000 Android Development] mobilescooby:
Yep just flashed and made quick test call to orange! Screen now reactivates when sensor is unblocked!

Shame about twoface but know that it will get fixed so next time I will be a little less cocky when I go ner ner mine works! Lol
[Galaxy S I9000 Android Development] mobilescooby:
Oh yes! I haven't forgotten! Zach your hard work and commitment is a credit to android and the community!

Now does anybody have a fire extinguisher? Cos my phone is smoking! Lol
[Galaxy S I9000 Android Development] currydude:
Haha :P Yea I'm confident zach will be able to fix this issue.
[Galaxy S I9000 Android Development] mobilescooby:
I was actually being serious my battery is overheating and this thing refuses to charge lol

Guess working in a lighting shop when the temperature is 95degrees wont be helping!
[Galaxy S I9000 Android Development] currydude:
LOLS I thought so :P Did you overclock? Try undervolting.
[Galaxy S I9000 Android Development] mobilescooby:
Nah no oc on this thing! Never really liked the idea or a mobilephone with built in leg warming / arson function :-)

Yea suppose I could UV it a bit to drop temp (hopefully)

Failing that I may have to replace the beer in the fridge with my phone for a while :-)

Hey any excuse is welcome at the moment for a cold ONE!
[Galaxy S I9000 Android Development] currydude:
Haha it's easter :P Why not?

Use Pimp My CPU and try these settings

Mhz/UV

1000 -50

800 -75

600 -100

400 -100

200 -125

100 -125

You phone should run cooler and the battery life should be better.

Stress test your phone by playing a game such as Asphalt 5, NFS or Dungeon Defenders. If your phones crashes/reboot, try lower UV settings (lower values in MAGNITUDE LOLS)
[Galaxy S I9000 Android Development] mobilescooby:
Once again many thanks

Will give those a whirl in a sec!

Was hoping that ondemand guv would've helped but then realized I'm sat on xda at the moment so kinda defeats the whole idea lol

*thinks will I get 3g signal from within the fridge, best of both world's then*

Hmmm
[Galaxy S I9000 Android Development] joe169999:
I actually experienced this last night with RC5. Today, It happened again on RC6. I reverted to Apr 13 version, runs as smooth as before.

Thanks ZM for contuniual efforts n updates.

Cheers.
[Galaxy S I9000 Android Development] Bo$s:
In newest version (2204) phone doesn't use 400MHz step. It mailnly stays at 800 MHz (conservative governor).

Info taken from time_in_state file.
[Galaxy S I9000 Android Development] zacharias.maladroit:
Hi guys,

a few more questions concerning the reboot issue & potential other issues with "twoface":

what network are you suing (GSM/UMTS) and which modem ?

what programs are running in the background ? [only of the UI is laggy for you]

reboot-issues after talking also happens when NOT using the latest nightly from CM7 ? [CM7 only]

any OC/UV (Pimp my CPU, VoltageControl) ?

I prepared a battery of test-kernels:

1) the new GSM (only ?) Fix only is disabled

2) change to ondemand governor

3) old conservative governor settings

4) ondemand governor with revert of the fast timings and more friendly scheduling

5) conservative governor with revert of the fast timings and more friendly scheduling

Each one of those addresses exactyl one or more issues

1) reboot while/after phone talk [please give this the most testing if you're having reboots in association with calls]

2-5) laggy UI

6) Toolchain ? <-- if all else doesn't help - it might be the new toolchain (which, btw, gives a nice boost & supposely stability)

Download Link <--

md5sums of the kernels:
[Galaxy S I9000 Android Development] lljkpugna:
I'm having the same rebooting problem on Twoface. I've never installed any other kernels on this CM7 install. It's not consistent either - some calls can go on indefinitely while others reboot after a minute or so.

Edit: It behaves fine apart from that, and works fine on stock CM7. Also I'm on GPRS.
[Galaxy S I9000 Android Development] zacharias.maladroit:
Hi freshprince_776,

glad you like it - thanks for using !

what additional thing do you mean :)

the battery drain problem is not perfectly fixed to our liking yet - teamhacksung is working hard on it - give them some time

sammy has interwoven lots of energy-saving stuff into the kernel

it's literally everywhere

this takes time to figure out, implement test and implement & test again

it also needs to be stable ;)

Hi arcardinal,

sure, I'm currently busy with troubleshooting the issue the guys on the SGS have,

Vibrant seems to work fine,

I've currently no idea what might have caused it but I guess I'll compile a "core"-test kernel with the new toolchain - that should show in the fastest time if it's caused by that or not

Thanks !

Glad you like it Mercury0660 !

Could you please share some info from your phone ?

what network type (GSM/UMTS), Modem are you using ?

ok thanks for the report - so it's not MIUI-caused (only)

Hi Bonta768,

thanks for your report

Pimp My CPU in the past has showed some of that behavior also with Samsung kernels - so the reboot issue could be related to some changes in OC/UV

Hi mobilescooby

are you running MIUI, CM7 or Sense ?

Thanks !

ok, thanks for the report !

EVERYONE having the reboot or other issues with "twoface" please test the test-kernels I created for this issue

Link to Post & Downloads

Thanks !

Thanks a lot to g00ndu & currydude for your extensive help !
[Galaxy S I9000 Android Development] Rezou:
I don't know if it can help you Zach to fix 2-5) issues, but I'm testing right now the latest TkGlitch kernel (v6pre-u3) with NO OC/UV, and concerning the UI/launcher smoothness, it is noticeably smoother/snappier with TkGlitch's kernel. With your great featured kernel, I was happy with everything, except the smoothness which is great, but I've experienced a better smoothness.

Hoping it helps you :P.
[Galaxy S I9000 Android Development] Kame_boy:
Had reboots during calls with twoface. It rebooted somewhere between 1 min to 2:30 min into a conversation (checked the log on the other phone i called).

One thing i noticed is that while i watched the phone several times during a call (i.e. i removed it from my face to see the screen light up), the last couple of seconds before reboot the screen would not turn back on (even if the call was ongoing).

So the call went fine until one or two minutes into a call, then the screen wouldnt turn back on, and a about 10-15 seconds later it would reboot midsentence.

I am running the latest nightly (04172011) with JVK modem. The reboots happened before and after: wifi on/off, UV on/off some CM7 setting about staying awake during a call on/off and auto-brightness on/off.

Trying out the fixed twoface kernel as we speak.

UPDATE:

Tested fix 1 non-gsm and same problem there. Once exactly like before, and the second time it was only one or two seconds into the call before the black screen of imminent death ensued.

UPDATE 2:

Updated to later nightly (04212011) as i was unaware of this update (where's the changelog btw?). Problem was gone until i changed kernel to twoface. Problem was still with the updated twoface (1) and problem was gone with core low latency.
[Galaxy S I9000 Android Development] lippol94:
:D First review of new testing kernels :)

Since I was affected by two problems (reboot after calling and lags) I've decided to try the number 5. One word?

Perfect!

It fixed both reboots and lags. Now scrolling is smooth as Tk.Glitch kernel.

If can help.. i think that reboot problem was related to many kernel switching so I've applied your cleaning script and everything is working so fine :)

ROM: MIUI RC6

Modem: JQ1

OC: No

UV: 1000mhz -50 ; 800mhz -75 ; 600mhz -100 ; 400mhz -100 ; 200mhz -125 ; 100mhz -125

Network: 3 Italy (UMTS)
[Galaxy S I9000 Android Development] Mercury0660:
I had one black screen while listening mp3. I could hear music but wasn't able to bring screen back to life until 10 sec reboot.

Infos

Modem jvk

Umts vodafone germany oc 1200

Uv 100 -125

200 -100

400 -75

800 -75

1000 -50

1200 -50
[Galaxy S I9000 Android Development] lippol94:
Seems that you need more volts for 100mhz (frequency during screen off). Try with -100/75
[Galaxy S I9000 Android Development] BL4zD:
I recompiled with the new toolchain and the soft keys still don't work on my captivate.
[Galaxy S I9000 Android Development] zacharias.maladroit:
you checked out specifically at commit ed242b663d91d6309fd6 ?

also which toolchain did you use ?

thanks for trying it out & compiling ! :)

I need to know if this also happens with earlier kernels or this just got introduced recently
[Galaxy S I9000 Android Development] BL4zD:
It started happening with core. It didn't happen earlier than that.

I reverted to the arm-2010.09 toolchain.
[Galaxy S I9000 Android Development] mobilescooby:
Hi Zach

Firstly thanks so much for you support and excellent work!

Currently I'm running the latest nightly on cm7. No Oc but am running a slight UV to help a slight battery overheat I had at work!

Have gone back to core for the meantime but have noticed some slight hiccups using it!

Once again thanks for your support and excellent work!
[Galaxy S I9000 Android Development] mobilescooby:
Okay initial results from version 1 of your modified kernels Zach.

Instant results regarding sensor locking screen off fixed but now have the reboot during call issue! Couldn't say for sure the length of the call as the display was off! But I'd say around 2 minutes.

Have flashed back to core and gonna give my phone a bit of a charge as only 7% now so will test other kernels in the morning!

Thanks again
[Galaxy S I9000 Android Development] zacharias.maladroit:
ok thanks mobilescooby :)

for giving those test-kernels an extensive test

currently I'm rebuilding the android system to get an up-to-date base (if anything changed at all concerning the initramfs)

Tk-Glitch is also seeing reboot issues with his kernels and he also has switched the toolchain

so it can clearly said (not with full certainty though) that most of the issues (but also the speedup !) are most probably caused by the toolchain switch

I'll see what I can do to still get a fast but also rock-stable kernel to begin with :)
[Galaxy S I9000 Android Development] currydude:
no worries mate, I will try my best to assist others with their basic problems and I'll leave the coding and addressing of larger issues :P

I shall test all 5 kernels now (I'll use each for about 5 hours).

But then again, I never had any issues with the previous two face kernel. LOLS

Kernel Test Progress:

1) GSM (only ?) Fix only is disabled: Not tested yet

Report

2) ondemand governor: Not tested yet

Report:

3) old conservative governor settings: Not tested yet

Report:

4) ondemand governor with revert of the fast timings and more friendly scheduling: Test in progress

Report:

- EDIT: nvm, placebo effect: this kernel is actually slower than kernel 5), scrolling is not as smooth as conservative kernel 5)

- Is faster than kernel 5) with opening lockscreens though

- No problems with calling reboots

- Autorotation/ExtSD/Camera is working

- Music also does not stop :P

5) conservative governor with revert of the fast timings and more friendly scheduling: Test finished

Report:

- Smoother/Faster than previous kernels - Overall scrolling is smooth, game performance is good as always.

- No problems with calling reboots

- Battery life: cannot comment on yet

- Initial boot: Phone initially could not connect to "Network Operator" but after about 1 minute, the problem resolved itself. Wifi took about 10 seconds to pick up - Subsequent reboots did not have this problem, probably just due to clearing dalvik cache/cache

- Autorotation/ExtSD/Camera is working

- OMFGGG WOOT :P Music appears to be fixed now, does not randomly stop when listening to my music now (for previous kernels, after a song or two, the music would stop)

Comment: overall kernel is stable, no problems.
[Galaxy S I9000 Android Development] suntzu123:
Battery going down 10% for 7h ( much for me on JVB is 1-2% at that time), Radio JVK, last miui with your kernel integrated (21.04.2011 22:42:06)

conservative scaling
[Galaxy S I9000 Android Development] runedrune:
that's good battery time. You shouldn't compare it to Samsung roms.
[Galaxy S I9000 Android Development] currydude:
LOLS 10% for 7h is what I would consider very good battery life for MIUI/CM7 but yes I agree with JVB/Any Samsung ROM I lost about 1-2% every 10 hours.

EDIT: Damn beaten by runedrune LOLS
[Galaxy S I9000 Android Development] suntzu123:
Nooo. it was ondemand. Conservative suck.... Zach set it to go downscaling at 12%, nad up-thershold as I rember is 75%... better in that case is ondemand that stay at lowest possible....

Much better would be conservative UP thershold at 75-85% for 100-200MHz, down thershold 60% for 100-200MHz, and up_thershold around 90% for 400MHz<x downthershold aroung 80%....

Easter time now and not much free time I got... EDIT post because my english is poor.
[Galaxy S I9000 Android Development] Mortify1:
I am getting the phone call reboot bug as well, happens when I'm already using my phone or when I get a call and its locked. I am on GSM network and connected to 3g.

This didn't happen on core kernel, also I do not hear someone hang up, like it freezes right as the call ends. Happened while OC with no UV and without OC.

Changed the awake governer to ondemand with the same result.
[Galaxy S I9000 Android Development] lippol94:
Must say.. Kernel number 5 provides the best experience on MIUI since I've flashed it :)

Congratulation Zach! Hope this will be the base (or the model) for your future release!

E.V.E.R.Y.T.H.I.N.G. WORKS PERFECTLY! :)
[Galaxy S I9000 Android Development] lljkpugna:
The 1st test kernel didn't fix the reboot-during-call problem for me.
[Galaxy S I9000 Android Development] Mortify1:
Trying out #5 and will report back tonight.

With conservative and on demand as my awake governor, my phone still restarts after a call.
[Galaxy S I9000 Android Development] damianza:
Hi Guys,

When ever I flash a Kernel I get no WIFI. It always says error unless I go back to the CM7 stock kernel.

Also with the modem I always see '3G' for the connection I never see the 'H' anymore. Should it be like this or should I try another modem?
[Galaxy S I9000 Android Development] currydude:
With the wifi issue, you just need to hard reboot (hold power button for 10 seconds) and as for the 3G I'm not sure for CM7 but for MIUI, it is normal to see "3G" when you have "H" connection because MIUI does not have the framework icons for the "H" connection.
[Galaxy S I9000 Android Development] pcboyy:
While i was struggling to UV on 'another kernel' ... i found zach's kernel is more stable and oc/uv-friendly (i just made up that term).. but i still cant uv more than -25 on 1200mhz but its no big deal.. i love this kernel ! (Twoface)

/nik on MIUI
[Galaxy S I9000 Android Development] zacharias.maladroit:
kernel stable (?)-release

Introducing "What's its name ?" release

04/25/2011 (release name: "Whatitsname"

already containing parts of Samsung's GB source (thanks teamhacksung !));

Semi-Testing/Stable (for new integrated code from Samsung) and other exciting new stuff )

kernel:

What's its name ? Vanilla without scripts (ondemand governor)

[without all the goodies]:

1st Mirror / Host

: [recommended]

"Whatsitsname" (thanks a lot to Roland !)

2nd Mirror

:

this thread (XDA) (attachment)

3rd Mirror

:

CM7_SGS_platypus-kernel_20110425_03_whatsitsname.zip (5.22 MB)

md5sum:

c61713564dd50f23adb60f463cba8e07 CM7_SGS_platypus-kernel_20110425_03_whatsitsname.zip

What's its name ? with scripts (conservative governor)

:

1st Mirror / Host

: [recommended]

"Whatsitsname with scripts" (thanks a lot to Roland !)

2nd Mirror

:

this thread (XDA) (attachment)

3rd Mirror

:

CM7_SGS_platypus-kernel_20110425_03_whatsitsname_scripts.zip (5.23 MB)

md5sum:

dab7d1272fa987f201dc18870566a6f3 CM7_SGS_platypus-kernel_20110425_03_whatsitsname_scripts.zip

Changelog:

additional optional features:

* bigger Dalvik VM heapsize (64 MB - like on Samsung's Gingerbread)

adb shell setprop dalvik.vm.heapsize 64m

to check if it's enabled:

adb shell getprop dalvik.vm.heapsize

* semi-fix for GSM/UTMS data signal outage (longer intervals):

adb shell setprop ro.ril.enable.dtm 1

to check if it's enabled:

adb shell getprop ro.ril.enable.dtm

Installation steps:

Auto-Rotation related

:

Generally no special steps should be required -

you could also leave out clearing of /cache & Dalvik Cache but this is to be sure - consequence is significantly slower 1st & 2nd (?) boots

following boots should be way faster than before (!)

Troubleshooting:

Please test specifically for the following sticking points:

enjoy ! :)

FYI:

for your convenience the kernel zip-files are also attached to this post

Thank you A LOT for your feedback on previous kernel releases

thanks !
[Galaxy S I9000 Android Development] currydude:
Yea same, If I try -50 for 1200mhz I get bootloop, but then again for other kernels (including Samsung Kernels, I was never able to get 1200mhz stable, so I'm very happy :P)

This kernel's performance is very good (better than anything I've tried before, including Samsung ROMS) but my battery life is still horrible LOLS yesterday, my battery died in 2 hours watching flash content on Miren Browser (Was able to get around 4-6 hours with Samsung ROMS) but oh wells :P Other than flash content, kernel seems to last about 12 hours, enough for a day :)
[Galaxy S I9000 Android Development] currydude:
awesome I shall test this now LOLS, sadly I did not have enough time to test all 5 other kernels.

LOLS first boot up and my screen is stuck upside down LOLS I guess I'll have to clear cache and dalvik cache

OK seems to be fixed LOLS

The "Galaxy S " screen, Cyanogenmod, bootanimation and homescreens were all flipped upside down at first :L

Everything is working fine.

Will now test various situations related to phone calls.

Also, it appears that the scheduler is still "sio" will also try a reflash if it fixes this. (After reflashing and clearing /cache and dalvik cache, sio scheduler is still used)

New special voodoo sound app is out, I just tried loading the Voodoo Sound v8 modules and phone crashed :(
[Galaxy S I9000 Android Development] suntzu123:
.... I got IDEA....

When I test your kernel I always close any aps running, and run SystemPanel

https://market.android.com/details?id=nextapp.systempanel&feature=search_result

It show you % load system, and CPU MHz....

When I see my system is load at 10%... And I see 200MHz on CPU... I said that is really wrong. ...

Now gooverner is much better at conservative. It-s around 120MHz-250MHz.... JUMPS around 250-300MHz scare me... You set down thershold at 12% it is too low.

But interactive? got creazy I set it by setCPU and it goes around 200-400MHz at IDLE....

----------------

I set with setCPU to ondemand gooverner where I got the longest time the lowest CLOCK....

But that's not everything. I also chanhe sampling rate to 280000 mikco second. The lag is not big, but I got CPU almost all the time at 100MHz-> lowest possible.

What do you all think about it?
[Galaxy S I9000 Android Development] silitek:
What about video?..Boz rom/kernel i have that working..now anymore.

Sound, but no screen at all!!!

Only issue 4 the rest..works good

EDIT: video work!!...its a miracle