yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] fluffi444:
Do we have a trigger to set this mannually? If yes in which file?

Not for setting it down to 700 now - I want to be prepared if you lower this value by default - I want to set it back to 1000 Hz :o

I just love how my phone reacts with that 1000 Hz... No reboots up to now here....

And I have also an 300 ms minus on boottime... aprox 8100 to 7800
[Galaxy Ace II Android Development] ChronoMonochrome:
There's no way to adjust it from userspace. In the meantime I'll probably try make it accesible via sysfs, but I'm afraid that it may even didn't boot(I didn't mess with it so far only because of this thought), so no promises for now.
[Galaxy Ace II Android Development] ace2nutzer:
i think adjustable HZ Value will not work at least properly because after changing this Value, rebuilding from scratch is needed ... :)

For me i never had reboots with HZ=1000 .. so if u really think it's related to higher HZ, what is of course possible ... because the CPU freq will switch much faster and this decreases Stability.... then u've to increase CPU Voltages a bit.... That's it !

@ all

btw: HZ=1000 is the correct Value for Desktop systems and of course Smartphones.. and HZ=100 is for Servers and this was painfully the default for Stock GB and JB Kernel xD
[Galaxy Ace II Android Development] borkins:
I didn't understand it either. If it's floating point capacity level - then the capacity, and the energy values (mAh) must be based on it.

But actually they are based on the rounded capacity level (%).

I know only that at 0% (capacity_level_raw), the capacity_level is still at 1%, and at 100 % (level raw) - the rounded level is still at 99%.

Another thing:

I tried to lower the 'termination_voltage' to 4250 mV, but on charging it's still reaches 4336 mV max voltage. :?

But as far as I know, it's not so bad to charge it to 4350 mV. Our original batteries are designed for that voltage.

For

3.6 V Li-ion cells max voltage is 4.1 V

3.7 V - max 4.2 V

3.8 V (ln our case) - max 4.35 V

So, I think, if we charged the battery with lower Voltage (~ 4.3 V) from the beginning, today we

wouldn't see the 96% "bug". I think it's appeared, because our batteries was charged with voltage above 4.35 V.

Before 2 years I wiped my SD card by chance and now I don't have the logs to show how the voltages reached 4.404V. Maybe the

termination_voltage of 4.35 V never worked.

Soon, after JB appears ( in the summer of 2013, the max Voltage dropped to 4.368 V), and today it's max to 4.334 V on charging.

Drop of 30 mV only for 6 months on charging it's a huge drop, because in the next 24 months it's dropped only with 35 mV.

I recharge my battery every day, so for 2.5 years, that means around 900 discharge cycles so far.

Which is not bad for device, that is meant to be replaced after 2 years of usage. :]

P.S.

I found my battery voltage at 100% of the capacity level gauge and 150 mA 2nd termination current - by next calculations:

4.404 V ( max on charg.) - 4.334 V ( now) = 0.070 V drop (lost) on charging

4.404 V - 4.350 ( max for battery) = 0.054 V drop ( for new battery, when unplug the charger)

0.054 + 0.070 = 0.124 V drop now - unplugged charger

4.350 - 0.124 = 4.226 V (at 100% capacity level) now - with unplugged charger
[Galaxy Ace II Android Development] ace2nutzer:
[MENTION=5151049]borkins[/MENTION] [MENTION=1130928]doctormord[/MENTION] [MENTION=3329816]mkaluza[/MENTION]

is one of u able to measure the max current flow from the original AC Charger here with printed output current 700mA ??

I'm asking u guys because i don't have the needed parts to make this test:

I need to know how much current max. it can drawn at 5V stable voltage... for this is an adjustable high capacity Resistor needed.. or potentiometer or what ever :) (pls don't measure the current with the Phone, it makes no sense with an old battery)

Actually i'm using 700mA default charging current and i'm planning to change it @ 750mA ... but i don't want to burn the original AC Charger :D
[Galaxy Ace II Android Development] ChronoMonochrome:
Yes, I know what you mean. There are some dependant on HZ kernel headers(one of such is arch/arm/include/asm/param.h - this is where to HZ being assigned CONFIG_HZ value), and this is why normally rebuilding from scratch is required. It would require awful lot of changes just to allow HZ to be changed at runtime, but they're can be done semi-automatic way. As I said, I won't wonder if that modified kernel with adjustable HZ won't even boot, but I think it worth trying :)
[Galaxy Ace II Android Development] ace2nutzer:
Yes of course try it :)

But i think changing this Value is not needed.. just let it @ 1000 and check your CPU Voltages....and also wait if someone else will report reboots.. but even such reports.. the user also need first to check cpu voltages.. and see if the reboots are then gone... so no need to use lower HZ Value IMHO. The difference in Battery lifetime is not much .. and just because of this.. i did (again :D) new Charger Driver to increase battery lifetime .. but now double charge cycles life are lost :p Max. capacity possible... of course without overcharging (it's not worth)
[Galaxy Ace II Android Development] ChronoMonochrome:
I doubt if changing CPU voltages would make any difference.. Even if they(timer frequency and Varm) are somehow connected each other, I wouldn't liked to touch CPU voltage at all. Changed HZ to 700 and so far there are no reboots.
[Galaxy Ace II Android Development] ace2nutzer:
Just trust one time older people than u :o

i don't think that increasing cpu voltage of +12.5-25mV will hurt ;)
[Galaxy Ace II Android Development] bebolint98:
Hi.Please somebody write how can I disable the button notification when the battery charged to 100%.I know there is a file in /sys/module/abb_chargalg/parameters/eoc_blink and in it write "1" I write "0" but after reboot it's rewrited to "1"

Thanks for everybody help.
[Galaxy Ace II Android Development] borkins:
1.Create a file ( for ex. 00Disable_EOC_BLN) with 0755 permission in /system/etc/init.d folder.

2. Copy and paste this in the file & then save it:

#!/system/bin/sh

echo 0 > /sys/module/abb_chargalg/parameters/eoc_blink
[Galaxy Ace II Android Development] ChronoMonochrome:
R3.3.2

Uploaded a new R3.3.2 build, with two small fixups, changed timer frequency(HZ) to 700 and fixed bugs introduced in volume rocker playback control feature.
[Galaxy Ace II Android Development] manthes:
Something about voltages that you may probably know. Undervolting cpu and gpu ( i made the undervolting the same time) causes lockscreen black screen to my s6d lcd. That's the first and last time i tried to change this values
[Galaxy Ace II Android Development] xo.en:
Which version? There's no such issue with 3.3.

There's slight in-call screen wake-up delay, but zero lockscreen delay there.

I am undervolting cpu and gpu on s6d together.
[Galaxy Ace II Android Development] PolishVodka:
Chrono

Wanna ask for something.

CONFIG_BCMDHD_FW_PATH="/system/etc/

firmware/fw_bcmdhd.bin"

CONFIG_BCMDHD_NVRAM_PATH="/system/etc/

wifi/bcmdhd.cal"

First file isn't in etc/ , but in vendor/ . Do you know for what's exactly it is?

About next file. We doesn't have it even in vendor sources, but it is in TUNA device_source, this is the same BCM4330, so can we use it? And the same question, for what is it?
[Galaxy Ace II Android Development] ChronoMonochrome:
First file is wlan firmware binary.

I don't know much what for is used second file - after searching a bit it turned out, it's wlan calibration file:

https://android.googlesource.com/device/samsung/toro/+/e870abd3735368493b47b54a24c1897356e39d2b

I think this file depends on wlan firmware and kernel module dhd.ko. Do we have exactly same wifi module as on tuna? It's interesting, maybe we can use fw_bcmdhd.bin/bcmdhd.cal from tuna with appropriate changes made in kernel.

UPD.

[MENTION=5151049]borkins[/MENTION], you mentioned about inaccurate power_supply_capacity_level_raw value calculation. Today I looked at sources and did some changes, which hopefully will fix this issue. This commit https://github.com/ChronoMonochrome/Chrono_Kernel-1/commit/623464d0a9a614e98ac19a371ec5a0ff0fd7b961 depends on assumption that power_supply_capacity being calculated correctly (like it was on both screenshots).

http://xda.mister-freeze.eu/XDA-files/ChronoMonochrome/misc/chrono_kernel_r3.3.3.zip

P.s. build above doesn't contain bootscripts/recovery, install only over previous kernel versions.
[Galaxy Ace II Android Development] manthes:
I am not very sure. It was 3.3 or 3.2 but most likely 3.3

I have a very "sensitive :p " s6d so i am telling it because with this undervolting it is the first time that i saw again blackscreen after about a year
[Galaxy Ace II Android Development] borkins:
I'm still testing it, but so far I saw that the raw level drops with whole percents ( ex. 11.4%, 10.4%, 9.4% ).

I suppose that it will stop at 0.4%, and then the phone will be turned off.
[Galaxy Ace II Android Development] ace2nutzer:
@up

what is the main problem ??

The Battery level indicator is just an approximation and secondly it'll not show u the real battery level in real time.. otherwise it'll drop up and down like creazy ... i think nobody like to see this :) There are some counts and timeouts till the battery level wil change the state.. this is to prevent drops when the phone is in idle and suddenly high load is there and the voltage will drop.

This Battery has 3.8V nominal Voltage... that means on FULL load the voltage is @ 3.8V stable.. of course if the battery was before fully charged. But in this case the indicator will NOT show u an drop from 100% @ 50% .. because the driver knows that the battery is actually under load ... and so on ....

On 100% battery, the

idle

voltage is 4.25V without plugged charger.... but with plugged charger, battery full state = 4.35V

Shutdown Voltage is 3.30V and it can be adjusted up to max. 2.8-2.7V ... lower is not possible because of battery self-protection ;)

And there is also an special tunable for 1% to 0% (poweroff) .. it'S called: #define LOWBAT_TOLERANCE	0 i'm using here "0" so no tolerance. Stock it was @ 40mV .. that means only if the voltage is

below

3.26V, the phone will shutdown.
[Galaxy Ace II Android Development] BlackAfghan:
[MENTION=5695278]ChronoMonochrome[/MENTION] (and also [MENTION=5840412]ace2nutzer[/MENTION])

Two important security related requests:

Could you please rebuild CM11 with latest sources? There is still one Stagefright vulnerability left (see http://blog.exodusintel.com/2015/08/13/stagefright-mission-accomplished/ and http://www.cyanogenmod.org/blog/more-stagefright).

And another question: why did you disable SELinux? It's an very important security feature, especially when there are unknown/unfixed vulnerabilities..
[Galaxy Ace II Android Development] ChronoMonochrome:
I'm aware of this issue, but I've heard that it isn't such easily exploitable like recently fixed CVE's, and is only MP4-related, so there's no big emergency. Of course, someday I'll fix it.

As for selinux, I don't need this stuff.. It's quite useless when is in permissive mode, since it only captures policy violations, and doesn't deny it. Personally, I wouldn't used it with enforcing mode, it makes many things too tricky.
[Galaxy Ace II Android Development] BlackAfghan:
1. Good, and yes it isn't an emergency. Just thought I mention it, since you wrote you stopped offering new builds..

2. Permissive mode is still better than completely disable it, since one could at least enable it, again.. But that makes only sense, if you keep the original rules from the CM ramdisk. Alternatively you could add your own rules, or if it's just troubling your config app, it could simply set SELinux to permissive if needed, apply the settings, and enable it again (as long as you don't upload it to Google Play).

Just my two cents.. Thanks for your work, by the way!
[Galaxy Ace II Android Development] ace2nutzer:
@up

actually i'm trying to enable SELinux ... actually it stuck @ CM logo .. hmm maybe i've deleted some SELinux Stuff in the ROM ??

any idea chrono ??

btw: Some time ago i've enabled in defconfig buffer overflow detector .... i think this is an good security option:

https://github.com/ace2nutzer/Samsu...1c9249/arch/arm/configs/codina_defconfig#L478
[Galaxy Ace II Android Development] BlackAfghan:
Check CM's ramdisk sources for updates, since it used to work with older versions of your kernel and your last year's CM builds..

BTW: Why you guys maintain two seemingly similar ROMs and Kernels? Wouldn't it be easier to combine forces? ;)
[Galaxy Ace II Android Development] ChronoMonochrome:
Sorry, it makes a less sense to me. IMO, without a crapware installed in a phone, there's no need in security enhancements such as selinux.

There reverse of the medal, once kernel compiled with selinux, there's no way to compeletely disable it. Why disabling instead of enabling? Nothing, just my preference - than less code in kernel, the less troubles with it.
[Galaxy Ace II Android Development] ace2nutzer:
okay, u're right ;) I've reverted all changes again.. but i'll maybe enable an default security level.. + that overflow buffer .. i think this is enough for security.
[Galaxy Ace II Android Development] BlackAfghan:
There are many of reasons for SELinux, like:

1. Google requires it officially (doesn't apply for us), but some apps require it

2. My mother uses the phone (she likes installing crapware very much...;) )

3. Most people here like to install apps, which are not supervised by anybody else (i.e. not from any store or market), often closed source or even need root (doesn't mean I don't trust you guys..)

4. Any app could turn into crapware, if it gets hacked

5. Potential future security holes (like recent libstagefright), especially since end of support is near..

IMHO, completely disabling it, is surly not optimal and even kind of a security risk. I think it is just fair to mention that fact.. :)

Your kernels are nice and fast, but unfortunately less secure, than the original ones!
[Galaxy Ace II Android Development] xo.en:
Nobody can teach you to think, even selinux.

Do not BEG and go teach your MUM some logic.

If you are guys gapps users, so how you can get crapware/viruses?

Whose fault is this then?

I am using TON of hacked/cracked apps from unknown sources(pure curiosity what tested app is, i am not user, since 99.9% of android appd is just bs) and had ZERO issues for >2yrs.

I never had facebook/instagram/whatsapp/twitter/gmail/another bs/gapps EVER, effect:

ZERO problems.

some of you may consider my post as rude, but...read it again then.
[Galaxy Ace II Android Development] BlackAfghan:
Do not BRAG about using tons of WAREZ... better check your credit card bills.. lol

EDIT: That's the same reason I don't believe in seatbelts. Although required by law, I ever needed them, despite I'm driving mostly drunken.. ;)
[Galaxy Ace II Android Development] xo.en:
Better start to choose proper sources...

Dude, do not talk like this when you have no experience.

You have NO idea what you are talking about.

If your knowledge relies on bs made by ridiculous sites etc, then let's skip this talk.

Now let's stop this OT.

Ok, logout for today...
[Galaxy Ace II Android Development] ace2nutzer:
Cool down guys .. :)

it's true what Chrono said, it's really useless to use SELinux when it doesn't denied the attack !

Selinux makes the kernel image bigger and with the result for lesser RAM.

As i said Buffer overflow which denied the attack + the default linux security level and seccomp is enough .. it's not Windows Phone ;)

Here quoted from the help text about buffer overflow: (CONFIG_CC_STACKPROTECTOR)

And this: (CONFIG_SECCOMP) --->

to safely compute untrusted bytecode

and the default security by linux:
[Galaxy Ace II Android Development] mkaluza:
I can't because mine died a long time ago (and it was rated at 800mA)

It's not that simple (and it's very simple at the same time). Short-circut current will probably be more than 700mA, but what you want to know is the max current that can still supply correct voltage. So the obvious measurement method is to increase charging current (using the phone) and watch the voltage (via sysfs). If it drops, its too much (and contrary to your opinion both current and voltage sensors in the phone are quite accurate - I measured it).

As for burning - I wouldn't worry too much about it. What I would worry about however is the battery - they don't like to be charged quickly...

---------- Post added at 09:31 AM ---------- Previous post was at 09:01 AM ----------

Guys! First thing - don't feed the troll :)

[MENTION=481796]blacka[/MENTION]fgan - you're partially right - as a general rule selinux helps and if google didn't require it we'd probably have more exploits for android. But in this specific case you're not right. Exploits are written by someone, and since most phones have selinux, any 'serious' attacker would assume it's there and act to disable/bypass it (like latest stagefright bug). Nobody will target custom distros and kernels hunting for those with selinux disabled - it's probably 0,0001% of the market and just doesn't pay off. So it's a bit like with vacccines - as long as majority uses them, the minority not using them is quite safe.

The other thing is - you overestimate it. It's not _The_ security measure - it's just a helper. _nothing_ can protect you from yourself. The fact that android phones became so common doesn't imply that they became idiot-proof! they are still computer systems connected to the wild internet and if you can't handle it, go play with wooden blocks... Contrary to marketing and engineering efforts it's still a very complicated device and if someone is too stupid to use one, it's not the device fault, but his own.

And the last thing - maybe most important. Those are all community projects. You get them _for_free_. So you are _not_ entitled to _anything_. Devs create them on a best effort basis, which means that given their limited time they choose to implement things that will benefit the most (or themselves in the first place). Of course you can ask the dev for something, but if they refuse, all you can do is say "oh, well..." and be on your way. To have demands you need to have money - it's that simple..
[Galaxy Ace II Android Development] TheLiquidGuy:
I am super pissed. I can't install this kernel and I don't know why. Before I had this problem too but I just waited to be released new version. When I install TC's CM11 and gapps (with temporary CWM) then I install chrono kernel r3.1 I am stuck at samsung galaxy ace 2 logo. Please help me! 1 month ago I was with exactly the same ROM and kernel version and it worked properly.
[Galaxy Ace II Android Development] ChronoMonochrome:
Install anything lower than R3.0 first, cause later versions has newer genfstab that seem to not work on a temporary CWM.
[Galaxy Ace II Android Development] TheLiquidGuy:
Yeah, I tried this and it worked. Thanks. :)
[Galaxy Ace II Android Development] ace2nutzer:
Thanks for answer, then it can't make sense :)

Hmm okay good idea :) But this i only possible since i've it "unlocked" from max. 900mA to 1500mA ... i thought it'll not drawn so much current because of old battery ... .. because if i set 700mA in NovaThor App .. then it only charges at 470mA ... btw: in sysfs: /sys/kernel/abb-charger/charger_curr it can show if the Voltage dropped ...

So maybe i need to make so hardcore tests ;)

U understands me wrong :) I was just meaning due to the old battery .. that it can't drawn the desired Current .. because of too big resistance :)

About accuracy: in kernel the termination Voltage is @ 4.35V .. and the Phone itself shows me always: 4.362V (on 100%) .. i know this is not really much difference .. i think there are some tolerances in the electronic parts .. but anyway i can't understand why the phone uses +0.012V. with the own sensor. But if i set in kernel 4.34V then it shows correctly 4.352V ! Now the question: what is the real Voltage ??

Also i don't know if this little diff is only on my phone here ... so what can say other users ??

btw: i just forget to mention: if Vbus dropping is detected, then the driver automatically set an lower current.. till the Voltage is stable.

Can u define what is quickly ? U know that Li-Ion Batteries are designed to charge up to max 1C, yes the "normal" ones ... so 1C has nothing to do with Quick-Charge ... Fast Charge begins with 2C and ends with 8C.

:good::good::good::good::good: perfect ! no comment needed :)
[Galaxy Ace II Android Development] ChronoMonochrome:
R3.4

New build is up!

Changelog:

reworked genfstab (should work with whatever recovery)

updated twrp to 2.8.7.0

applied aggresive optimizations

If you have issues with installation(booting), make and attach last_kmsg log(reboot to recovery -> make log via adb:

cat /proc/last_kmsg > /sdcard/last_kmsg.txt

And attach here).
[Galaxy Ace II Android Development] manthes:
It didn't boot for me again as with all the latest kernels.

later i will try it again just to give a log but i know that i have to replace all the folder osfiles from an older kernel to work
[Galaxy Ace II Android Development] shaqman89:
Worked perfectly for me. Both on vanir and aicp.

Say, is it normal for the recovery to still be philz?
[Galaxy Ace II Android Development] ChronoMonochrome:
Yes. I never liked idea to force any recovery. Changing recovery is still up to user(it only should replace twrp 2.8.6.0 if installed).
[Galaxy Ace II Android Development] matthias1976:
installation works fine for me !!
[Galaxy Ace II Android Development] manthes:
After installation twrp can't see internal, external sd and it didn't find any OS installed. So i can't provide any log
[Galaxy Ace II Android Development] ChronoMonochrome:
Fixed(uploaded as same kernel version). To fix this issue, extract recovery/twrp.fstab to /ramdisk.
[Galaxy Ace II Android Development] dixee:
i'm stuck on boot when installing latest kernel R3.4, unfortunately i can't see last_kmsg log file when i checked through twrp file manager after stuck or i should use adb to get this file?

the latest working version that work properly in my phone is R3.2
[Galaxy Ace II Android Development] miryn:
<delete pls>
[Galaxy Ace II Android Development] xo.en:
..seems ok, so far(vanir).
[Galaxy Ace II Android Development] ChronoMonochrome:
Not needed anymore - have found one more problem with genfstab, or rather saying, every binary running on android - dependence on /system/bin/linker. So, running genfstab without this file or with /system unmounted always resulted fstab file to be empty... Lol, it took for me almost 6 hours to understand it :eek: But, hopefully, in next build it will be finally fixed.
[Galaxy Ace II Android Development] matthias1976:
someone test this !?

i like to test those cause i want to prevent whatsapp from getting killed from RAM. i got notification problems.

want prevent google my tracks from getting kicked outa ram too cause sometimes tracks arent recorded completly.

bummer i didnt understand right how to do those things.

can someone write examples ?

do this settings in 00autoload ?

for me i dont like new battery recalibration table.

ok the drop from 100 to 95 in some seconds was strange but ok for me.

now it stays longer in this area 100 to 95. i think now the losses are bigger when battery under 50 %

so wheres the pro ?
[Galaxy Ace II Android Development] ChronoMonochrome:
su
ps | grep "whatsapp"
echo *process* >> /sys/module/lowmemorykiller/parameters/donotkill_proc_names
echo 1 > /sys/module/lowmemorykiller/parameters/donotkill_proc

You can don't like it, but so far it's better solution IMO. There are no bigger losses under 50% since only top half of the battery table(50-100%) was rewritten.
[Galaxy Ace II Android Development] matthias1976:
type this in terminal !?

wont work typing this in 00autoload ?

only my own opinion. just wanted to say
[Galaxy Ace II Android Development] ChronoMonochrome:
Search name of needed process in terminal, then write it to an init.d script as in an example above.
[Galaxy Ace II Android Development] matthias1976:
ill try !!

thx chrono