yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] reggaemanu:
That is ! First is for AC, second for MISC (car charger or unknow sources), thirs is for USB.

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

Yes.

Also, that's strange that it fails only if flash is initiated from booted os, if i enter recovery and flash the file manually (even with my external sdcard inserted) it works just fine.

So what the difference between entering recovery manually and

flashing auto from the os ? Does it change something about mounting points in fstab? (there is a lot of people that have fails from the kitchen app and from darky's rom tool or any other similar app with cwm5 and an external sdcard)
[Galaxy S II Original Android Development] kokoskokis544:
b16 with userspace profile and cpu 200-1000mhz is awesome..dont know about battery but look promising. not a single lag..
[Galaxy S II Original Android Development] olifee:
I found something :).

Google told me about it after some jumping around (danger, code ahead ^^):

https://github.com/CyanogenMod/android_bootable_recovery/commit/30a937a954e78ac600cae97ae86f0a9bc6481ab8

Long story short, the sdcard-marker is the file

/sdcard/clockworkmod/.salted_hash

I do not know (yet) when it is created, but I guess it is generated by CWM when you take a nandroid-backup with CWM 5.

To see the file in terminal, use "ls -a" (files with . in front are hidden normally).

Try to take a nandroid-backup and check if it is generated. If not, create it and put something random in it, it should fix the kitchen (I guess).

:)
[Galaxy S II Original Android Development] reggaemanu:
Yeaah, that's it, I created an empty /sdcard/clockworkmod/.salted_hash file and now it works ! I did make a nandroid backup with cwm5 before flashing the rom but initiated with cwm app, I guess we have to initiate it in recovery mode. Let me try, i'll delete the file and do a backup...
[Galaxy S II Original Android Development] olifee:
Perfect :). That's good news.

In the CyanogenMod-Code I linked, I can not find any other place where this file is accessed *confused*.

Mine says it was created a month ago, I just checked, so before my last backup.

In case the file is not created for you after your backup, I suggest this might be a bug in CWM (maybe some earlier version created it, and now the current one relies on it, and nobody noticed?).

EDIT: Maybe it is created by CF-Root, could be around the time I first rooted my device. Did you ever format your SD or delete the complete clockworkmod-folder on it after rooting?
[Galaxy S II Original Android Development] reggaemanu:
Just finished to backup and there's still no file.

Anyway, we now have narrowed the problem and can point the dev to it and finally we have a workaround. Thanks again !

---------- Post added at 12:05 AM ---------- Previous post was at 12:04 AM ----------

I never directly installed cfroot on this device, just flashed a pre-rooted rom with odin the day I bought it and since I never had to flash cf-root again.
[Galaxy S II Original Android Development] CA3iR0:
Its not necessary to reboot after updating the rom. You can flash siyah (wich wipes cache and dalvik automaticaly) and then reboot.
[Galaxy S II Original Android Development] reggaemanu:
I guess gokhanmoral could add a script to create this file when flashing siyah kernel to make sure cwm5 works fine for everyone.
[Galaxy S II Original Android Development] crypticc:
Good luck then..definitely had boot to logo when I skipped a step. strangely flashing cfroot via Odin fixed it
[Galaxy S II Original Android Development] CA3iR0:
I dont need luck, I always did this way and always worked. I just did it again and guess what? Worked flawlessly :p

And I got notifications working again :D
[Galaxy S II Original Android Development] LockeOn:
What is this FTDI module? Will this enable using USB keyboard/mouse via OTG cable on AOSP based roms (MIUI/Cyanogenmod) as it is enabled in Stock Samsung roms?
[Galaxy S II Original Android Development] olifee:
Guess that's the explanation then. I used CF-root the first time.

As far as I understand from the CVM-sources on the linked page, the externalSD+SD-situation is the only moment when this file is checked for, and this only happens starting CWM 5. This explains why it might go unnoticed for many people, and especially why it hits many CheckRom Revolution users (first post advises to format SDCARD or at least remove all android-related stuff from it).

As I read somewhere (but did not check), CyanogenMod treats SD and external SD differently from stock (which I guess was one reason why this marker was introduced).

So maybe, it is the job of a kernel to place that file if CWM 5 is packaged with it. I think this should be documented in CWM5-package, but I guess it is not (otherwise gokhan would have included it).

@gokhanmoral: Can you look into this? If CF-root really generates this file (/sdcard/clockworkmod/.salted_hash), it might be simple to add the generation to Siyah-kernel and 'fix' all the complaints about CWM 5 in one go, especially for a final release / rc ;-).

In case this is really different for CM7, Siyah can then be even more unified (:P) by creating the file on the correct device for AOSP and stock.

---------- Post added at 12:30 AM ---------- Previous post was at 12:25 AM ----------

No, as I did not use AOSP up to now, I did not even know that it does not work there (and I do not understand why it does not ^^).

The FTDI-module allows you to connect FTDI-chips to USB-OTG (at least on stock, where I tried it). Thost FTDI-chips are in most USB-serial-converters.

The module usbserial is also needed to provide the device in dev-tree.

After that, you can connect serial devices to your phone, as mostly used for data acquisition, programming microcontrollers etc.

So this is not for the masses (unless somebody finds a mass-application for it), but will not hurt performance as it is a module you have to use manually ;-).

If you search this thread, you will find a picture where I connected a digitizer (something like a digital oscilloscope) which included an FTDI-chip straight to my phone and accessed it in a debian-chroot.
[Galaxy S II Original Android Development] chadouming:
@Gokhanmoral, You think you might add lulzactive governor ? I always loved it on lulz kernel and would like to try it on yours :D

http://tegrak2x.blogspot.com/2011/07/lulzactive-governor.html

http://xdaforums.com/showthread.php?t=1118918
[Galaxy S II Original Android Development] CA3iR0:
F*CK YEAH!
[Galaxy S II Original Android Development] chiggah:
Where can i download the stock kernel for CM7 as I want to try out other kernels (Siyah) incase I want to switch back to stock
[Galaxy S II Original Android Development] sunwee:
i am seeing higher battery temps with the 2.1x kernels.

usually it runs about 34C but i am seeing 37C-39C on normal operations. and coming out from deep sleep, in an aircon room, it can go as low as 25C but i've not seen it below 30C at all with 2.1x.

i've no other problems with battery life, nor does the back casing feel particularly hot.

could it be temp reading bug?
[Galaxy S II Original Android Development] chiggah:
Which is the best version for CM7 ?

latest 2.1 beta or 2.0 official ?
[Galaxy S II Original Android Development] mikebike20:
Gokhan : this is my report after using beta16 about 10 hours approx on miui 1.10.21 with a 2000 mha battery with stock voltages, conservative, sio , 100 - 800 mhz . Battery draining is excellent, i lost 28% only using sms, a little games, internet hspda, changing theme... battery temp at 30 deg C max...Launcher is totally smooth, really pleasant, no issues at all. Well !!! Your beta 16 is just awesome for me at daily use...thanks a lot
[Galaxy S II Original Android Development] Reno_kun:
It should be a great idea !
[Galaxy S II Original Android Development] SignalX:
guys

in SiyahKernel v2.1 Beta16 gokhanmoral said:

i'm using 2.1 beta 16 now on my MIUI 1.10.21 rom! but every time i connect and disconnect my USB to phone, this notification "USB debugging connected" is still there even when i disable usb debugging!

and i have to reboot my phone!

i checked my build.prob using Root Explorer BEFORE flashing Siyah v2.1 b16

there was no persist.adb.notify

after flash, this line was added to end line of build.prob automatically: persist.adb.notify=1

and in changelog of SiyahKernel 2.1 b16 gokhanmoral said: persist.adb.notify=0

i changed it to persist.adb.notify=0 manually using Root Explorer

but every time i reboot my phone it will change to persist.adb.notify=1 automatically!!

what can i do now?

thanks

SX
[Galaxy S II Original Android Development] chadouming:
change persist.adb.notify=1 to persist.adb.notify=0 -_-'
[Galaxy S II Original Android Development] SignalX:
thanks mate but,

i changed it to persist.adb.notify=0 manually using Root Explorer

but every time i reboot my phone it will change to persist.adb.notify=1 automatically!!

what about now?
[Galaxy S II Original Android Development] chadouming:
hmm, you mounted system as R/W, before chaging this ? I use Rom Toolbox or RootTools to change thing is build.prop usually.
[Galaxy S II Original Android Development] SignalX:
yeah! i checked build.prob after edit/save to ensure!

it seems Kernel change it automatically after each reboot as it a kernel function!

i think its wrong function unlike gokhanmoral said in changelog: persist.adb.notify=0
[Galaxy S II Original Android Development] chadouming:
hmm, that's strange since it's ok with mine. Try to add the same line, right after the one automatically added. like

persist.adb.notify=1

persist.adb.notify=0

So you will either get

1-0, try remove first line and reboot to see.

1-1, Kernel problem

1-1-1 Should not since you would have a lot of lines.

0-0 This should not happen since it's supposed to not touch it if there is already something.

If you have 1-0 then you should not ahve the icon in your status bar since the last line should overwrite the first one. Tell me your results ^^

---------- Post added at 08:58 PM ---------- Previous post was at 08:56 PM ----------

2.1Rc1 there but link not yet working :P
[Galaxy S II Original Android Development] xuxuzao:
what about that black screen problem when receiving a call? solved in b16?

tks
[Galaxy S II Original Android Development] chadouming:
you are with miui ?
[Galaxy S II Original Android Development] gokhanmoral:
what is the first version you had that problem?
[Galaxy S II Original Android Development] gokhanmoral:
miui guys: try rc1
[Galaxy S II Original Android Development] :
I just noted this as well; 5C warmer than usual under the same conditions. 2.1 beta 16. Other than that, the kernel feels great.

Sent from my MicroTAC 9800X using speech to fax modem
[Galaxy S II Original Android Development] chadouming:
Trying to download but getting 404 code xD
[Galaxy S II Original Android Development] joeyfong:
The download link is broken.
[Galaxy S II Original Android Development] SignalX:
Thanks mate

solved! :-) here is what i did

- removed persist.adb.notify=1 line

- XCell kernel flashed

- now every things are ok with XCell [during using XCell there's no persist.adb.notify in build.prob]

- Siyah 2.1 b16 flashed again

- persist.adb.notify=1 added to build.prob automatically

- again, i changed it to persist.adb.notify=0 manually! after this again and again i checked build.prob to ensure!

- rebooted and bump! o___O its persist.adb.notify=1 again!

- changed it to persist.adb.notify=0 manually

- rebooted and wiped cache and dalvic cache + fixing permissions

- now life is nice :-)

i dont know what happened on my phone but i fixed it!

thanks again mate :)

cheers

SX
[Galaxy S II Original Android Development] gokhanmoral:
strange... I did not change anything related with the temperature readings..

maybe having no compiler optimization flags cause that difference.

you can try rc1. I re-enabled the safe optimization flags, the ones that I used in beta14
[Galaxy S II Original Android Development] SignalX:
i can confirm this! it happen randomly

SX
[Galaxy S II Original Android Development] gokhanmoral:
it's 4am, and I uploaded it to scripts directory :)

try it again...
[Galaxy S II Original Android Development] chadouming:
Link fixed, thanks :D

---------- Post added at 09:19 PM ---------- Previous post was at 09:17 PM ----------

Don't worry xD I made worse thing at these hours xD
[Galaxy S II Original Android Development] Vahidmoby:
i can't Download kernels from www.Gokhanmoral.com

i live in Iran and Filtering Sucks

can anyone give me a Mirror OR Upload kernel (2.1 RC1 or Beta 16 which one is Better?) Here ?
[Galaxy S II Original Android Development] chadouming:
There you go, i know what you live xD
[Galaxy S II Original Android Development] final90:
I have flashed the 2.1rc version and i`ve tryed to run some tests with quadrant standart and set the max and the min frequency to 1600Mhz(via SetCPU) but after i hit 'run full benchmark' in quadrant i get frozen and had to take out the battery.Why?I did NOT make any changes in the voltages.
[Galaxy S II Original Android Development] peachpuff:
Anyone got ntfs for otg usb working with this kernel on miui?
[Galaxy S II Original Android Development] knightnz:
@gokhanmoral are the pictures on your web-page yours or just ones that came with the hosting?

Something you did since b14 seems to have made it a lot snappier, of course it could just be that 100Mhz isn't available at the moment.
[Galaxy S II Original Android Development] dave_p_b:
If I lock my phone, wait 15 or 20 seconds and then try to unlock, my phone freezes and I have to force it to switch off (reboot).

I can reproduce this behaviour each time. Stops when I flash back to kernel version 2.0.

Sorry if you already discussed this.
[Galaxy S II Original Android Development] sesamee:
Use Voltage control application.
[Galaxy S II Original Android Development] yoplaboum:
All siyah kernels are on my server : http://aideadsl.com/sgs2/kernel/
[Galaxy S II Original Android Development] gokhanmoral:
They come with default wordpress installation.

In b14 i changed a lot but none of them should prevent the usage of 100mhz. Just dont use uv. You will gain much more than using uv if you use 100mhz. Some people were saying that they prefer beta2 because 100mhz is more stable at 800mv. I said that it was a bug and i fixed it. Ask yourself this: do you want me to make a change in the code that makes you think you use low voltages while using stock or do you prefer to readjust your uv values to the changes in the source code?

I will not make the first choice ever. Those who cannot live with having undervolting while having difficulty to accept that their device cannot handle it should use either stock or speedmod kernel.
[Galaxy S II Original Android Development] jdmcivic:
what is the command to echo new values to change sampling rate and up threshold for ondemand governor. ever since 2.1,

echo 85 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold doesnt work anymore.. has the locarion been changed?
[Galaxy S II Original Android Development] BoneMo:
wifi problems

DELETE POST: REFLASHING NIGHTLY96+Siyah 2.1rc1+gapps SOLVED PROBLEM
[Galaxy S II Original Android Development] inferno17x:
Hi Gokhan,

I agree with you with the real voltage instead of masking it to a lower mv.
[Galaxy S II Original Android Development] bandit79:
Did i understand it correct, if i want to flash something with CWM Recovery i have to use the 4.0.0.2 and not the 5.0.2.6 which comes with the rc1?
[Galaxy S II Original Android Development] BoneMo:
nooo, 5.0.2.6 comes with the rc1 but you can flash 4.0.0.2 through 5.0.2.6.

the http://www.gokhanmoral.com/public/files/siyahkernel/scripts/cwm4002.zip is CWM flashable olderCWM
[Galaxy S II Original Android Development] bandit79:
ok, so it' not a must have. i can but i don't have to?

the 5.0.2.6 gives also the flash support like in the betas?
[Galaxy S II Original Android Development] :
what do you mean by heavily undervolted? and why don't you try yourself?
[Galaxy S II Original Android Development] ebliss:
Is there any settings required to make cwm 5.0.2.6 backup to external sd instead of the internal sd? I tried doing a backup from recovery and it only backup to internal sd.
[Galaxy S II Original Android Development] :
I always thought that it is like if you have external sd it will make backup there and if not it will make backup on internal, but I have never tested it. don't think there is a way to change it in cwm (maybe someone can submit a change to cwm with changed functionality)..
[Galaxy S II Original Android Development] karlesg:
and what is the point of that?

maybe you should ask him how much he raised his uv settings (if he uses any uv) compared to the old sources to make his device stable again. This should have more meaning to you than simply reading plain uv values which is pretty much something worthless.
[Galaxy S II Original Android Development] ebliss:
From the cwm thread, I think there are 2 versions of 5.0.2.6. One of which will back up automatically to the external sd if it is inserted. The other one will backup to internal sd only.
[Galaxy S II Original Android Development] bvannier:
:)

It's what I did, and everything seems OK so far
[Galaxy S II Original Android Development] Zanr Zij:
You mean people should not uv from b14 ? Gain battery or performance?

My phone uv 100MHz @ 775mv stable. Is it bug? B14 and RC1!

Sent from my GT-I9100
[Galaxy S II Original Android Development] bvannier:
It's what I did, and everything seems OK so far ...:)

The script is available on the first page
[Galaxy S II Original Android Development] rauschkugl:
This is not asked too much but too often. Every day there are at least 5 posts with uv values and people asking for them. And it's everyday the same answer. Try it yourself.

Sent from my GT-I9100
[Galaxy S II Original Android Development] viscocesco:
USB Host & HDMI

I'm running 2.1 (beta 13) but Usb Host & Hdmi not working.

Running Checkrom Revolution v1.0.
[Galaxy S II Original Android Development] extract1:
Hi can someone please tell me how to install this zip file? Set AC and MISC charging current to 1000mA - CWM flashable (keeps USB charging current at 450mA) Not sure exactly what im supposed to do.
[Galaxy S II Original Android Development] lambstone:
On 2.1 RC1, using battery monitor widget pro, it seems that my battery drain is ~40mAh.

3g and sync is on.
[Galaxy S II Original Android Development] spaxx24:
Then dont do it, you might mess upp your phone.
[Galaxy S II Original Android Development] extract1:
why would it mess up my phone if i install it the right way?. I want to be able to charge the phone quicker since it takes like 4hours to charge. Just want the directions on installing it. Am i supposed to update it via CWM ? or extract the folder and put the files in /system/etc? or some other way? would really appreciate any help.
[Galaxy S II Original Android Development] spaxx24:
Yes, but since you cant do it the right way, or aint sure wht to do, dont do it
[Galaxy S II Original Android Development] yoplaboum:
If you want I can give you an access in my ftp you can contact me by pm

For free !!! ;)
[Galaxy S II Original Android Development] amapi:
Hello guys,

i have a problem.

I use a Samsung galaxy S2 with stock rom XXKI4 root by flashing CF-Root-SGS2_XX_XEO_KI4-v4.4-CWM4.tar with odin 1.85

Each time a try to flash siyah kernel 2.0 (via odin 1.85 or CWM) i'm stuck a boot with yellow triangle.

Someone have an idea or a solution

thanks
[Galaxy S II Original Android Development] extract1:
Well how can i do it the right way if i don't ask to be sure? anyway just flash updated it via CWM so thanks for your help!
[Galaxy S II Original Android Development] droidphile:
Put the file in your internal sd. Reboot into recovery.

Install zip from sdcard>select chargecurrent zip.

Not that setting AC current to 1000 can make your phone really hot especially if you are using hspa while charging. You can try lowering the values just to be on safer side.

Open the zip (in winrar or whatever, don't unzip), navigate to /system/etc/initd.d. Open "98chargecurrent" file in notepad or something. Change the line

NEW_CHARGE_CURRENT="1000 1000 450" to

NEW_CHARGE_CURRENT="800 800 450" or something.

Save and now flash using recovery.
[Galaxy S II Original Android Development] datakill:
WOW! "aideadsl" brings me back to very old times (8-10 years) of the mule :)

Thanks for the links buddy ;)
[Galaxy S II Original Android Development] extract1:
Thanks for the tip will reflash it with the new values as soon as i finish the current charge with the original settings. Setcpu is showing the battery at 48 degress:eek: What is the average battery temp supposed to be around on stock settings?
[Galaxy S II Original Android Development] janreiviardo:
B15 to RC1 is buggy. My phone always ends up not opening and I have to restart it again either by holding the power button very long or by removing the battery. I have not changed any settings and my UC and UV have always worked on B14 and earlier.

My settings:

Clock-Voltage

100-825

200-825

500-850

800-950

1000-1050

1200-1150
[Galaxy S II Original Android Development] BoneMo:
try not use 100Mhz or increase 825 to 850....

My settings:

1600MHz 1325mV

1400MHz 1250mV

1200MHz 1150mV

1000MHz 1075mV

800MHz 1000mV

500MHz 925mV

200MHz 850mV

i use rc1, also had beta 13,14,16

no problems with this settings and without 100mhz
[Galaxy S II Original Android Development] janreiviardo:
I restored the original voltages and will see if it will still occur. Btw, for those who have been using this kernel for long. What do you suggest is the best I/O Scheduler? I am using VR right now, I have read the explanation about these but there is none for VR and sio. Thanks
[Galaxy S II Original Android Development] h20pt:
I'm using RC1 with these settings and i have no problems at all :)

1600 - 1350

1400 - 1250

1200 - 1150

1000 - 1050

800 - 950

500 - 900

200 - 850

100 - 850

I could try to lower the 100Mhz's voltage to 825mV to see if it remains stable and wakes up from sleep, but this settings work just fine and i'm tired of experimenting :p

Also, i'm using Ondemand governor.. From my experience, the governor's choice plays a really important role when undervolting.. It can keep your phone stable at the same voltages that used to be unstable with other governor.

Hope this settings are helpfull to someone.
[Galaxy S II Original Android Development] xuxuzao:
gokhan, still facing black screen when receiving calls

miui 1.10.21

2.1rc1

tks
[Galaxy S II Original Android Development] nerotix:
@gokhan

Check PM :)
[Galaxy S II Original Android Development] the^one123:
Hi gokan!

Very nice build rc1. With rc1 i got my old uv settings back. With beta15 i have big Problems with uv but i think the problem was the 100mhz step. If i dont use 100mhz step it ist working fine.

Here my settings stable for me.

100 @825

200 @875

500 @875

800 @975

1000 @1075

1200 @1175

1400 @1275

1600.@1400

Governer ondemand. Screen on 100-1200 off 100-500. OcDaemon.

Theone
[Galaxy S II Original Android Development] DobermanS:
for some reason had my first reboot ever during a call with rc1 on miui 10.21... :(
[Galaxy S II Original Android Development] GDT:
Here too. I tried to raise up voltages but it's very unstable for me. Stick to b14, the last one that really works for me.
[Galaxy S II Original Android Development] hausmanis:
thx for sharing, those worked for.net to in rc1
[Galaxy S II Original Android Development] nikzDHD:
RC1 requires the higher voltages compared to what we were able to get on 14, I've just -25mv for now on RC1 and working. Not too bothered about uv much more until next version :)
[Galaxy S II Original Android Development] the^one123:
Since 2.1 you have to raise up voltage for 200mhz.875mv is stable.

Try my settings two posts ago.

Theone
[Galaxy S II Original Android Development] jim-bo:
Don't try other people's settings. Every CPU is different. Start at stock voltages, drop a step, stability test, rinse, repeat. It is the only way to find what voltages this phone can run at.