yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] nikolas1274:
After the installation of new kernel I had my screen to pixelise, I don't know how to describe it, it happen 3 times, and after I reboot and install again boot script that stop NT settings and kernel again, if it happen again I will try to take screenshot and I am log
[Galaxy Ace II Android Development] ace2nutzer:
u can forget this table. From Sources the max. is for GPU and CPU: 1,3625 V But noboby knows the real Voltage on the GPU or CPU .. for that we need to open the Phone and do real Voltage measurements. Actually nobody did this, therefore it's a unknown thing.

But what we know:

For GPU your posted table is right.... but the Voltages unknow. There is no bug in the Algorithm.

For CPU, Voltages are also unknow, but there is a bug in the Voltage Regulator or just in sources.. maybe it's only a wrong definition of max. Voltage and so on. Till 0x38 seems everything OK... but the next higher Voltage is not on 0x39 etc... but it's on 0x3D , then 0x3E, and max. Voltage is on 0x3F ... But for fail safe i can suggest to ignore these Voltages:

0x39; 0x3A; 0x3B; 0x3C; 0x3D; 0x3E

For VBBX:

According to the Sources (even on Stock Samsung) max. Vbbx is on 0x8F = vbbp -400mV and vbbn 400mV

As u can see it's reverted polarity.. on vbbp --> positive (+) it's negative (-) and so on...

U can also use this settings: vbbn and p @ both 400mV positive and also viceversa both negative -400mV

and of course also correct vbbn -400mV and vbbp 400mV

Be sure that i've treid all combinations of Vbbx .. and for me, and probably also for all other phones.. the best choice is for lower Freqs: 0xDB = 300mV with reversed polarity and for OC (high freqs) 0x9F = vbbn 400mV and vbbp -400mV.

As u can see here is also a bug in the Sources or Regulator.. max. Voltage of Vbbx is not as expected on 0x8F but on 0x9F .. 0x8F should 400mV .. but nobody know what is the difference between 0x8F and 0x9F ... the fact is: it's more stable with 0x9F ...
[Galaxy Ace II Android Development] fluffi444:
Feel free to correct the list...:D

I thing your findings (what you wrote recently) is hardly to understnad for some...
[Galaxy Ace II Android Development] ace2nutzer:
What do u not understand ? :D

As i already wrote:

For CPU:

ignore just these Algorithm:

0x39; 0x3A; 0x3B; 0x3C; 0x3D; 0x3E

That means: from low- to high: 0x00 - 0x37, 0x38, 0x3F.

Anf for GPU your posted table is OK.. there is no bug in 0x3A etc ... but the Voltages are unknow..
[Galaxy Ace II Android Development] crisis_trustee:
When will be r3.0 kernel?
[Galaxy Ace II Android Development] fluffi444:
omg ace2nutzer... not for me for others :)

Some ask for table and I gave it - which is still 90% correct...especially "in the middle" which is of most interest.. nevermind...
[Galaxy Ace II Android Development] ace2nutzer:
oh sorry.. i misunderstood u :)

btw: i found also out that's possible to use the Phone in low freq.. totally without Vbbx Voltage :D

But i've don't test this for long time.. just some minutes.. and it worked.. really strange.. but i don't use it because the power consumption between 300mV and 0mV was max. 1mA .. this is nothing :) but decrease stability. I believe the Vbbx is just an buffer like an CAP .... if any freaky users like to experiment with this, the code is: vbbx=0x00 ;)

@ Chrono

do u actually using the new GPU OC Algorithm by me ? I mean without the 01 bit for half freq ....
[Galaxy Ace II Android Development] fluffi444:
R2.9.1: Have this also! Pixeled screen. Happen quite reproducilbe while on quickstart screen and switching to notification screen (with button in right top corner) - If I do this switching repeatedly in a short time screen stuck or get corrupeted.... After that pone lost responsivness and hangs sometimes and sometimes not... With some whilte pixels somethimes... And sometimes not... Especially after screen off and on there are such corruptions... And if I'm in enhanced restart menu while switching the options (reboot, reboot to recovery etc)...
[Galaxy Ace II Android Development] ChronoMonochrome:
:/ I removed this build as it was very unstable. If you want, redownload 2.9.2.

I don't use it completely, actually used some PLLs(by the way, thanks :) ), just to avoid its manual calculating :) I don't know if without 0x01 bit it work better, but I decide to leave exactly 0x0005..... pll values. Tried several variants of PLL (0x0105...., 0x0003..., 0x0005... etc, but nothing of these solved errors after boot - this was due to APE_OPP messing).

Anyway, the main idea isn't in that bit - it's in changing only multiplier, that I introduced in commit https://github.com/ChronoMonochrome/Chrono_Kernel/commit/b8ae16ce4feda2336ab59f82b7c5c5622bc95d11 even on November 2.

Omg, why it should be exactly r3.0? It might be 2.10 -> 2.11 ... 2.17 etc. If something great will happen(something like LiveOPP 2.0) then I will name it R3.0. (okay, actually R2.0 was named because LiveOPP 2.0, not because of same number, but due to it was greatest change for all Ace 2 development history since LiveOPP was written, ofc.)
[Galaxy Ace II Android Development] ace2nutzer:
Yeah.. i think it's the same if u have all at 0x0105xxx or all at 0x0005xxx ... the only important thing is to let this @ Stock:

https://github.com/ChronoMonochrome...cedrv/mali/platform/ux500/mali_platform.c#L51

I not completely sure... but that caused reboots on my latest Kernel.. .. actually i've build the kernel without changing this Value.. but the table all at 0x0005xxx and it looks like it's stable now.. but i'll test for 2 Days if it can run stable, then i must tell this @ cocafe .. because he has implemented my new Algorithm in his cocore Kernel ... :-/
[Galaxy Ace II Android Development] ChronoMonochrome:
This value used only as init for PLLSOC0, it might only hang at boot (but as it turned out, all mali errors was due to messy MCDE APE100 <--> APE50 changing at boot - probably it's better to run it with APE100 or APE50, but don't change it, otherwise it'll cause mali errors).

p.s. this is only my experience, but since I added APE100 requirement for first 35 sec after mali being initialized and removed MCDE requirement, mali errors at boot never happen to me.
[Galaxy Ace II Android Development] ace2nutzer:
okk... i've removed your commits for APE 25 only for suspend and also every APE 25 commit... therefore i can't say what happened.... for me: i never had problems during boot by changing this SOC0 init ... hmm

It creates only problems with CPU freq higher than 1Ghz ... very strange.. but this is the fact. :)

Now i hope it's fixed.. by reverting this Value to stock.... but to have all CPU and GPU Steps with the same Divider is a nice thing.. is much more stable and smoother :D
[Galaxy Ace II Android Development] ChronoMonochrome:
Probably this happened to me and some users precisely because of APE_25_OPP - originally APE50 was used as default (except APE_50_Partially_25_OPP), but now it's APE25 and when setting APE25 with screen on some unexpected things may happen... or at least it seems that it took place to be.
[Galaxy Ace II Android Development] ace2nutzer:
Yeah... i've used many days the APE25 with the commit for only for screen off.. but i've faced that sometimes @ screen OFF the APE_OPP was stucked @ APE 100 or APE 50 (don't remember correctly..) .. many times i see this... this is the reason why i've removed it completely.. and since them.. never had problems with wrong OPP on screen OFF.

Just for info: I've checked this states under /debug/prcmu/ape_stats and so on ...
[Galaxy Ace II Android Development] ChronoMonochrome:
Have you seen /d/prcmu-qos/ape_reqirements ? There should be reason for APE stucking, maybe MMC or wlan cause it.

By the way, have you tried to use it https://github.com/mkaluza/i9070_kernel_CoCore-E/wiki/Undervolting-janice#extreme-undervolting ?

I'm currently using extreme undervolting with screen off. I set 200 MHz static clock with screen off, and seems that it can work stable with as low varm as 0x05. I know, this is a little tricky way, but anyway :D
[Galaxy Ace II Android Development] ace2nutzer:
@ extreme Undervolting: To be honest i didn't test it.. it's just too creazy for me.. but anyway amazing work / idea ! Actually i'm satisfied with my battery lifetime :)

I believe wlan and mmc it was in all cases @ 400Mhz ... and on 400Mhz i've DDR25% and APE50% in Voltage Table.. but in past i had APE and DDR @ 25%...

This Infos in the Files isn't not clearly for me.. can u explain it pls ? I did screenshot of all 3 Files ... Thanks :o
[Galaxy Ace II Android Development] ChronoMonochrome:
Some modules (like mmc, wlan etc.) can itself require some DDR or APE state. Maximum of these value will be used as DDR/APE_OPP.

Normally with screenoff I've this (but probably I edited some requirements, to avoid stuck with APE50/DDR50, don't remember, which exactly):

root@codina:/ # cat /d/prcmu-qos/ape_requirements
wlan: 25
mmc: 25
cpufreq: 25
ux500-msp-i2s: 25
bt404_ts_device: 25
mali: 25
root@codina:/ # cat /d/prcmu-qos/ddr_requirements
wlan: 25
mmc: 25
cpufreq: 25
bt404_ts_device: 25
mali: 25
mcde: 25
[Galaxy Ace II Android Development] avithohol:
2.9.2 extremely unstable the phone is rebooting even on 800 mhz.
[Galaxy Ace II Android Development] ChronoMonochrome:
Haven't had even one reboot :/ Post your avs data (/sys/kernel/liveopp/prcmu_avs) or last_kmsg.
[Galaxy Ace II Android Development] ace2nutzer:
Thank u very much for good explanation ! Do u think my Values from the Screenhots are OK ? With screen ON ...

If think a bit strange is the pri_lcd_ws2401: with 50 why ?? when mali have 25 :-/
[Galaxy Ace II Android Development] ChronoMonochrome:
I think, pri_lcd DDR requirement is unneeded. That will cause forcing DDR @50OPP with screen on. About APE - IMO, it's unnecessary to set APE100 via LiveOPP... since mali and bt404(needed partially enabled touchbooster) can require APE100 itself, when it's needed.
[Galaxy Ace II Android Development] ace2nutzer:
Wow... u're great, Thanks ! Now i understand it right :D, Then actually everything OK .. if i like this configuration. :)

I'll think about it, if it's better to use DDR25 even with screen ON and so on.. Thanks again :o
[Galaxy Ace II Android Development] lars85destroyer:
Guys, can you explain me how to use all the tricks in the latest builds to get more battery life without loosing smoothness ?
[Galaxy Ace II Android Development] fluffi444:
Cannot confirm that - R2.9.1 was xtremely unstable - But R2.9.2 is faar better.

Running 10 hours (with normal use) without any issue. The rest will tell the (usage-)time.
[Galaxy Ace II Android Development] nikolas1274:
I confirm, R2.9.2 is very very stable, no reboot, no freeze, no lag for me

Edit: I also manage to switch to art without lags for first time.

At dalvik I had 1G free at data but at art left only 300M, is it normal?
[Galaxy Ace II Android Development] fluffi444:
Again... Today in the morning (after aprox 23-24 hours ontime) I got blackscreen-freeze. I have two alarms setted for the morning. First was OK. Second rings also. But after that phone gone to blackscreen-freeze out of sleep mode. No respont on the keys. Only long pressing power button helped.

This is all very strange...:confused:

Do you think logcat will help?
[Galaxy Ace II Android Development] ChronoMonochrome:
R2.9.3 is out :).

Changelog:

- screen flickering fix (thanks [MENTION=3329816]mkaluza[/MENTION])

- added interface to adjust minimal DDR/APE OPP states with screen on

cd /sys/devices/pri_lcd_ws2401.0/
echo apeopp=50 > mcde_screenon_opp
echo ddropp=25 > mcde_screenon_opp

If you've s6d, then use path /sys/devices/pri_lcd_s6d27a1

It's experimental setting, DDR_25_OPP might cause screen flickering (I never encountered this, but since I got few reports, I changed default value DDR25 -> DDR50).

- LiveOPP: added interface extreme_oc for attempts to OC upto unstable freq. Make sure that your phone can work stable at this freq with Performance (if not, then even theoretically this interface won't help). Command list:

1) boost_step=xx

overclocked freq step.By default -1245 MHz (arm_step15), but it's possible to change pll that way:

echo pll=0x501a0 > /sys/kernel/liveopp/arm_step15 # 1230 MHz

2) unboost_step=??

max freq step, that you usually use - 1200 MHz by default.

3) delay=??

delay before switching to boost_step, ms

4) uv_latency=??

delay between setting voltage and PLL, us.

It's recommended don't change this value

- changed deepest sleep state 4 -> 3. It seems our u8500 platform can't work stable with sleep state higher than 3.

https://drive.google.c…U0VFE/view?usp=sharing

http://xda.mister-freeze.eu/XDA-files/ChronoMonochrome/kernel/chrono_kernel_r2.9.3.zip
[Galaxy Ace II Android Development] manthes:
With all 2.9.x builds i have freezes in a minute after boot. I can't even use the phone. Probably because of s6d?
[Galaxy Ace II Android Development] ChronoMonochrome:
Can you post /proc/last_kmsg ?
[Galaxy Ace II Android Development] manthes:
Because it was impossible to post the file directly i made a reboot to recovery with buttons after latest freeze, change kernel to previous one and after that i copy the file. I hope it isn't a problem
[Galaxy Ace II Android Development] ace2nutzer:
Can u simply try my new Build (if the latest Chrono-Kernel didn't help) from Today if all your problems are gone then ? Just to make sure that's not hardware failure ;)

I'm Curious to know if your problem with broked CM Bootlogo disappear ... :)

Link: http://xda.mister-freeze.eu/XDA-fil...inap_kernel_cm11_20141219_f2fs_ace2nutzer.zip
[Galaxy Ace II Android Development] Devel0per95:
Always rebooting with release 2.9.x :/
[Galaxy Ace II Android Development] nikolas1274:
R2.9.3 is good as R2.9.2 for me, stable.

For the deep sleep, can we change it from NT? Cause i have setting it at 4 there and i have no problem, i set it at 5 now for test3

thanks
[Galaxy Ace II Android Development] Kiras_PL:
2.9.2 and 2.9.3 were not stable for me at all. Laggy, lots of freezes and reboots . Im still on 2.8
[Galaxy Ace II Android Development] ChronoMonochrome:
Thanks, now I see possible reason for freezes. Don't know, although if it related to s6d display, but will revert LCD freq change for s6d.
[Galaxy Ace II Android Development] vacziferi:
This is totally the same in my phone (with ws2401 screen driver)

after several hours after boot (20-24) there are freezes, or not turns on the screen (first press on power button: no screen on, just button backlight on; second press: no screen on, button backlight off; after no response but restart for long press of power button)

(but -it seems- now it became better after some days, the time since last boot is 41 hours right now.)
[Galaxy Ace II Android Development] fluffi444:
Could you please give us/me a hint were to look at what the freezes can occur? btw I have WS2401 driver...
[Galaxy Ace II Android Development] ChronoMonochrome:
Probably mali sometimes running at half freq (APE_50_OPP) when it's in boost state. I reworking this part of code, then will see how it'll work.
[Galaxy Ace II Android Development] Devel0per95:
Thanks man , we are counting on you :)
[Galaxy Ace II Android Development] ChronoMonochrome:
R2.9.4

- fixed error in mali boost logic(APE50 OPP in boost state)

- rewritten APE/DDR using logic

new interface /sys/kernel/mali/mali_opp:

Now we set APE/DDR OPP taking into account current mali load.

cd /sys/kernel/mali
echo ape100opp=??? > mali_opp
echo ddr100opp=??? > mali_opp

If you feel that your phone lagging, then decrease these values. If with default values battery drains too fast, then increase thresholds above.

- reverted lcdclk interface (I believe it's broken)

- reverted LPA changes

UPD. New poll is added. Just out of curiosity, how much users can use 1200 MHz or maybe even higher CPU freq.

Feel free to report your uv settings, if you use custom uv settings :)
[Galaxy Ace II Android Development] avithohol:
With this build 3d performance is slower even than stock JB.
[Galaxy Ace II Android Development] vacziferi:
some minutes ago again got a freeze, no response for any key but long press of power button.

for me, it seems that something messed with data transfer that couse freeze. In that time, wifi was on, so maybe something broken with wifi driver???

anyway, there is a message: [169490.267027] mcde mcde: Could not set lcd freq to 62400000

so, maybe you are right with lcd freq.

(a strange thing here: in NT app, the max freq. is 600 Mhz)

tomorrow I'll try the new build and we will see :)

kmsg: https://www.dropbox.com/s/7x9kbmx33m8a9p9/last_kmsg1219.txt?dl=0
[Galaxy Ace II Android Development] S.AMU:
For me there is a problem with all 2.9 kernel.

Its two (or three??) since I installed a new kernel (2.9.1 or .2 or so) and some time after that I found out that my phone went crazy.

-changed the CPU values from itself, especially after a reboot

-sometimes it was just impossible to quit recovery. It always booted again in recovery (sometimes after flashing cwm and then twrp it worked to exit, sometimes just trying 10 times helps and so on)

- and sometimes my phone went just really slow. And with really slow I mean so slow that it was unusable and it was just there with the screen on until I pressed the power button for 10sec.

-also sometimes the phone was just a little bit more laggier than with a 2.7 or 2.6 kernel.

-I don't know if it is due that in kernel 2.6 zram is still enabled, but here after a boot I'm using not more than ⅓ of the whole ram (cache not counted) while in the 2.9 kernels my ram was almost full after boot.

First I thought something went wrong with the kernel but I had this problem also with all never version (didn't test 9.4).

Because when installing the new kernel I also updated the ROM, I restored the backup of the old rom and only used the new kernel, but still the same.

So three days ago I decided (or had too, because the phone was only booting to recovery again) to format all and start from scratch with a clean system and the latest kernel.

But it was still the same.....

So today I got some time again and installed an old version (2.6.x) over the 2.9 kernel and now all is OK again.

After that I reflashed 2.9.3 and my phone went crazy again.

So now I'm writing this with the 2.6.x kernel...

I know that you will kill me chrono, but I'm sorry I don't have any logs. But as soon as I have time I can reinstall a new kernel and extract some logs.

PS: i cant participate to the poll because I'm on Tapatalk, but for me 1200 is rock solid.

Edit: I just saw the post above. I always have WiFi enabled and most of the time I'm using the phone I'm connected.
[Galaxy Ace II Android Development] ChronoMonochrome:
The GPU frequency has nothing to do with MCDE one.

So guys I give up. I really don't know what is cause any weird consequences, that were described in latest posts. I've nothing of that.

Maybe the next build will be based on 2.6.x or 2.7.x.
[Galaxy Ace II Android Development] zizoumadrid:
please based in 2.6.1 it's stable and smooth and i'm use it till now
[Galaxy Ace II Android Development] nikolas1274:
From the other hand I have no problems with any kernel from R2.9.1 till now, for me the latest 3 versions are the best and I am running at 1200Mhz.

I am using the carbon Rom and the bootscript that override the NT settings for mali
[Galaxy Ace II Android Development] monstro78:
I'm running 1200 - 200 interactive sioplus kernel 2.7.6

Fast and smooth. Sometimes after charging or after airplane mode CPU doesn't get to deep sleep so I must reboot.
[Galaxy Ace II Android Development] S.AMU:
Please help me. What is wrong with this script?
[Galaxy Ace II Android Development] Devel0per95:
please make the new build based on 2.6.1 :)
[Galaxy Ace II Android Development] nikolas1274:
I believe that anyone how have problem should try to install new kernel with this way:

1.format system

2. Flash Rom

3. Flash apps

4. Flash new kernel

Make cwm back up first
[Galaxy Ace II Android Development] Devel0per95:
It will work 100%? Or u r not sure?
[Galaxy Ace II Android Development] nikolas1274:
I have made a lot of times, but you always can restore your back up
[Galaxy Ace II Android Development] Devel0per95:
Iwill try this after the CM12 is out
[Galaxy Ace II Android Development] fluffi444:
[MENTION=5695278]ChronoMonochrome[/MENTION]

Besides all this freezing/reboot reports - something good to mention:

Starting R2.9.3 (i guess) and R2.9.4 the app drawer (Nova here) do NOT restart once anymore on fresh reboot.

Also some apps are closing now correctly. It happens to me that Antutu did not close correctly (everytime).

It was needed to closed it 2x or even more! Also during closing an other app it happens that webbrower starts for some reason...

But as I said: This behaviour is away on new builds.

Besides this R2.9.4 is extemly fast! Rest time will show. I did not change any of those new values.

Do you thing that Dynamic FSyny Mode could have an influence on that freezes etc? Setted it for test to activated (standard)....
[Galaxy Ace II Android Development] ChronoMonochrome:
Is it still freezes on 2.9.4?

This happened because of new DDR/APE OPP setting algorithm. It is dependent of mali utilization now (and independent of boost state - now it can require APE100 much earlier than it'll switch to boost state). However, requesting DDR100 OPP redundant in this logic, as it probably will drain battery like hell.

It never happened to me with enabled dynamic fsync mode.
[Galaxy Ace II Android Development] monstro78:
I'm testing 2.9.4 is better than previous 2.8 builds but is slower from 2.7.6.
[Galaxy Ace II Android Development] fluffi444:
Until now - not - But normally "problems" occur not during first hours of use.
[Galaxy Ace II Android Development] manthes:
Probably 2.7.x is the faster and without any problems. I am using 2.7.3
[Galaxy Ace II Android Development] crisis_trustee:
There is already r2.9.5 kermel for Ace 2.
[Galaxy Ace II Android Development] fluffi444:
Again an issue... This time not completly freeze right away...

Screen looses response.

Then only left right swipe works.

Short after that nothing and screen went off.

Light on button works still for a few time - then nothing.

After that only power button helped.

R2.9.4 with very conservatioe settings:

CPU 1100 (lowered it for tests from 1200)

Max GPU high2 540 (lowered it from Kernel-stock 600)

DDR 798
[Galaxy Ace II Android Development] ChronoMonochrome:
If it looses response, then probably something bad with latest changes of touchscreen. Maybe touchbooster cause it. Gonna to compile kernel from 2.6.x sources with some critical fixes :)
[7" Kindle Fire HD Q&A, Help & Troubleshooting] rb2tfm:
Good day to all and I do apologize if this post is not in the proper forum but I am limited to where I may post.

I have what I believe is a Kindle Fire HD 2 ? I do own and have rooted and cyanogenMODed my kindle fire 1st

gen, 2nd gen and my kindle fire HD, this one I believe is the HD 2 running version 11.3.2.3.2_user_323001620.

I have been a member here for sometime and have learned a lot and I very well may have stumbled across

something a few minutes ago. From what I gather this version kindle has not yet been rooted or at least that I can

find any proof of ( my apologies if I am wrong ). I was just tinkering with it and downloaded a root app from here

named Root_with_Restore_by_Bin4ry_v35 I also downloaded and installed the Kindle Fire HD 8.9 ADB

drivers from here also and downloaded a file called pwn.zip too.... Anyway....

Under Windows 7 these are my procedures....

1. Extracted pwn.zip to the z2root folder

2. Right clicked RunMe.bat and chose run as administrator

3. Chose option 0

4. Then chose option 0 again.

5. Then connected the kindle to the USB cord

6. Hit Enter and allowed Root_with_Restore_by_Bin4ry_v35 run it's course following the onscreen instructions

and it seems as tho I am rooted.

Again, I apologize if I am posting to the wrong forum and I am also sorry I do not have all the steps for instructions...

to be honest...Im about to piss myself ;) ... Sorry

Can anyone else try this and confirm it please?

Take~Care!!!
[7" Kindle Fire HD Q&A, Help & Troubleshooting] rb2tfm:
screenshots

Sorry they are not the best pics.