yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] ace2nutzer:
ok thx for testing ! I'll start new build without that commit at all ... seems that it serves nothing on devices with HWMEM.
[Galaxy Ace II Android Development] Karut:
I have the same problem: video recording does not work (only creates temp files)....taking photos works just fine. Clean install with the newest kernel, rom etc..

--

Also what do you guys use to move apps to the sd-card? App2sd or link2sd?

Thanks, great rom! Just revived an i8610 :)
[Galaxy Ace II Android Development] btb55:
Regarding no WiFi after soft reboot...

I do have latest ROM and kernel, but just to try and fix this I have done a factory reset, reflashed again with ROM cm-11-20160428-UNOFFICIAL-codina and kernel ace2nutzer.kernel.4.4.x_20160827_codina.p.l.

I still have no Wifi after soft reboot, is there anything else I can try?
[Galaxy Ace II Android Development] dr@xxon:
Thanks It's work now, Can I create file with this commands in init.d?
[Galaxy Ace II Android Development] ace2nutzer:
Sure ! .. but let me know after 3 Days if it's still OK without issues at all ... thx !

use File 99_user ... and then rename it smthg like "lcd" or what so ever u want. because after an kernel update it'll override 99_user file with a empty version like always.

Again, why do u use such a old ROM with buggy features ?!

Latest ROM is cm-11-20160822 and not cm-11-20160428.

Also there is no fix so far, that's why i've removed it, so use normal reboot instead, or flash latest ROM.
[Galaxy Ace II Android Development] dr@xxon:
rare mistake but how will it occurs many times. Is it problem with my screen or with drivers?
[Galaxy Ace II Android Development] Dr360r:
What's new with 160829 kernel?
[Galaxy Ace II Android Development] ace2nutzer:
It was a driver issue that caused problems on some WS2401 lcds.

On latest kernel there is this lcd fix included.

That means maybe some of u can move from lcd.fix kernel to normal kernel which is more smooth.
[Galaxy Ace II Android Development] Szaby59:
Hi, just installed this rom + 29th kernel. is it normal that I only have 150 MHz and 800+ MHz CPU states ?
[Galaxy Ace II Android Development] shaqman89:
Yes, it's been like that from the 22nd version. Refer to its Changelog and you'll see what I mean.

You could over clock it, or use performance profile to get higher frequencies.
[Galaxy Ace II Android Development] Szaby59:
Not interested in higher freqs, but removing the 400,600 mhz power state will not increase the battery drain ?

Also with enabled BLN the phone doesn't go to deep sleep and if I switch between apps parts (text/image) of widgets are disappearing:

Don't care about the BLN I have it disabled anyway but this widget bug is annoying is this a common issue ?
[Galaxy Ace II Android Development] ace2nutzer:
Yes as it turned out that anything lower than 800Mhz caused lags ... at least with the actually LCD Config.

But on idle it'll stay on 150Mhz ... once u touch the screen or scrolling or a simply 2D Game is running without to touch the screen, it's running @ 800Mhz in order to be smooth.

Not very much ..... because we was using input touch boost 800Mhz ... so 400 and 600Mhz steps was not used very much ... removing them results in more responsive phone .. because of less delay from idle to 800Mhz :)

btw: use for now ROM build 20160802 .. because latest build camera rec is broken (latest cm commits are not compatible with our device)
[Galaxy Ace II Android Development] Szaby59:
Thanks will try that one, maybe the widget bug also related to some CM stuff.
[Galaxy Ace II Android Development] ace2nutzer:
Yes BLN uses Wakelock by default and is enabled by default.. but can be disabled in NT_APP like u did.

But wakelock is only active during blinking ... otherwise the phone can go to deep sleep without problems ... that's why it's on by default.

as for the widget issue: i never heard about this. ... strange :)

EDIT: Found the commit to revert for camcorder by dev golden-guy .... so now it's recompiling :)

https://github.com/ace2nutzer/android_frameworks_av/commit/e54a1bb9a9d6d87d824b0f8c8dac54814f46eab8
[Galaxy Ace II Android Development] Szaby59:
The widget issue was caused by a conflict between the rom's nova and the one I restored with titanium. Installed without the old settings and works fine now.
[Galaxy Ace II Android Development] Dr360r:
[MENTION=5840412]ace2nutzer[/MENTION] No. Still 1 second, then crash.
[Galaxy Ace II Android Development] Szaby59:
Is there any way to disable the button lights when fully charged ?
[Galaxy Ace II Android Development] ace2nutzer:
Actually not ... but i'm still wondering why so many users was asking this :)

There is no option to disable it, because there is no reason for it.

Nothing can happen, no battery drain or what so ever.

btw: to disable it: turn screen off ... or just unplug the cable
[Galaxy Ace II Android Development] lace_hvc:
I felt like many other people here regarding the BLN turning on once battery was full. But I have to admit that I changed my opinion in the past months. I actually prefer now that it notifies you when you can unplug the cable without having to turn on the screen to check the actual battery level. You dont have to keep in mind that you are still charging your phone.

In the other thread about CM10.2 you wrote that losing a lot of battery % after reboot means the battery needs replacement soon. I lose ~10% every time i reboot, but then the battery level stays the same for quite some time. Wondering if I need to replace my battery. Currently I get 4h screen on time and ~ 10 days stanby time (with <1h screen on time).
[Galaxy Ace II Android Development] ace2nutzer:
Well, with an new original battery it should loose approx 3% for every reboot.

If u've with time more and more .. it's just a sign that the battery don't have anymore the full performance. ... and this doesn't mean u should replace it ... it's just a confirmation that it has lower capacity ... then with time the capacity is lower and lower .... till u've only 30 minutes of SOT ... then u're forced to by new battery if u don't want to charge the Phone 10 times per day ;)

I know, u'll see then same level for long time ... but this is because u're not overloading the battery with high load of current ....

on idle or with low cpu load .. it'll stay ... that's right ... but once u do high load task like playing a 3D gam, high brightness, Browsing on 3G ... low signal ... then i'll decrease very quickly.

The Battery level is according to the peak of lowest voltage.

That means on high battery load .. the Voltage will decrease a bit .... but on old battery the voltage will decrease much more on high load ... but later when load is low, the voltage will increase by itself .. then it's able to hold the higher voltage on idle ... but only as long there is no high load again ... .. that's why u see for long time same Battery level.

Also forgot to mention: once the Voltage was decreased due of high load ... then later when voltage is higher because load is low, the battery level will still show the state of lowest voltage ... theoretically it should show always the proper state .... but if so programmed then the battery level would jump up and down like creazy ..... On the other hand, it's not technically correctly to determine a battery level only by Voltage... The Voltage says nothing about batt. level.

The Proper Level is always measured under load .... and that's why it stays after the reboot on low level instead to show again an higher level according to the Voltage.
[Galaxy Ace II Android Development] Dr360r:
[MENTION=5840412]ace2nutzer[/MENTION] Anyway the camera still doesn't rec properly on 160830 (1 second, then crash).

By the way i had another battery become bloated. The bloated battery also caused some cracks in the back cover. What happened with the bloated battery? One time i was on the beach, and the battery level was going down normally. Once it reached 26% the screen (on max luminosity) started flickering and then the phone turned off and never turned on again until i recharged it. I soon replaced that battery with the first one that came with my phone.
[Galaxy Ace II Android Development] IAmLucky:
pretty normal, i have genuine ace 2 battery still havent replaced after all those years, and yeah, sometimes i am scared when i see this, it makes me think that my phone is done and its dead lol. It happens to me when i havent rebooted phone for a long time, and when i never disscharge phone fully, when my phone has 20 % left, i charge my phone. And sometimes when i reach down to 5% i see screen starting flickering and then display just fades out, but when i put my phone to charge after few minutes i can turn it back on.
[Galaxy Ace II Android Development] Culateralligator:
That had also happened to me twice in the last 2 months when battery =2% and using maximum screen brightness (both days we had >35°)...

When plugged and charged the phone, everything went back to normal.

In addition, I was recording several videos and the two last ones, just two minutes before powering off, sounded like there was a bee hive around the phone...

Battery=10 months old 1700 mah Polarcell in good conditions.
[Galaxy Ace II Android Development] ace2nutzer:
ok thx for testing .... yeah probably overheated ....

same for the others of u ... and when the screen starts to make problems already on 5% .. then this isn't o good sign .. that means it's not anymore powerful ... anyway if u know that .. just don't go that down with batt. level .... it's not very well for the battery ... even if it's already broken ... so u can prolong it's life a bit if u don't discharge that deep.
[Galaxy Ace II Android Development] c.y.b.o.t:
The reason is quite simple. If you are charging your phone over night and have it in a dark sleeping room, once it is fully charged, it will actually illuminate the room more than it should. ;)

Also, if I'm turning BLN off, I would expect it to be off completely, not only for messages.
[Galaxy Ace II Android Development] ace2nutzer:
Well, the solution is even more quite simple ... just put the phone on the display side instead of back-cover side ... and it'll not disturb anymore.
[Galaxy Ace II Android Development] c.y.b.o.t:
Obviously I have to and I do, but that sounds a bit like "put tape on your phones speaker to mute it because there is no setting to do so". ;)

It would be a nice-to-have feature, but that is of course up to you to decide. :)
[Galaxy Ace II Android Development] Dr360r:
You should never leave appliances connected to the mains when they can't be attended (unless necessary, such as running a server or NAS).
[Galaxy Ace II Android Development] heml0ck:
what's new in 0830 rom and 0829 kernel? if i update to 0830 rom do i need to install 0829 kernel? or it is included in the rom?
[Galaxy Ace II Android Development] ace2nutzer:
New Kernel is Up !

Changelog:

20160829:

LCD: WS2401: fix grey lines after wake up

Fix merged on both Kernel Versions

PS: Rom 30/08 deleted .. still camcorder is broken like 22/08 ROM .. so use for now 02/08 ROM + 29/08 Kernel and latest NT-APP + Recovery package till we'll fix it.

[MENTION=6902149]Dr360r[/MENTION] check from time to time FTP Server .. i'll upload sometimes new test-build for camcorder... maybe more than one per day is possible ... so check also the time ... Thx ! ;)
[Galaxy Ace II Android Development] c.y.b.o.t:
There are many devices that need to be connected to the mains 24/7 nowadays. So I'm willing to take the "risk" of charging my phone over night. But thanks for the advice. :)
[Galaxy Ace II Android Development] Oğuzhan1907:
latest kernel installed.Not see sd card.Why?
[Galaxy Ace II Android Development] ace2nutzer:
New Kernel is Up !!

Changelog:

20160831:

crypto: lz4, lz4hc, zram - fix decompression

increased CPU OPP FREQ delay from 10 to 20 for better stability

re-enabled all supported crypto options for better performance

Enjoy ! :)
[Galaxy Ace II Android Development] Dr360r:
Apps still optimizing at startup with 160831 kernel.
[Galaxy Ace II Android Development] ace2nutzer:
hm strange .. i don't have that issue ... i think smthg is fcked up with your phone ... maybe u can try to make cwm backup ... then wipe data, format system and restore the backup ... this will fix filesystem errors if there are any.
[Galaxy Ace II Android Development] Dr360r:
What you suggested didn't work. Can reparting again be of help?

[MENTION=5840412]ace2nutzer[/MENTION] Ok, now Camera properly records without crashing on ROM 160831. If we could find the commit (pretty surely in ROM 160718, but i can give it a try to confirm it) that messed up the viewing of the first Google Images it could be perfect.

[MENTION=7114432]galac44[/MENTION] There's more. I rebooted. I installed two apps. I rebooted again. It didn't optimize. I installed Opengapps, latest version with Google Play Services 9.6.73 and rebooted to system. It optimized. I rebooted again. It optimized 3 apps. I then installed an old Opengapps version with Google Play Services 9.4.52. I rebooted and it optimized. I rebooted again and it stopped optimizing. So it's the latest Opengapps which are causing the optimization issue. Use Opengapps Pico 160802 for now (if you want the latest Google Play and Google Play Services, of course).
[Galaxy Ace II Android Development] ace2nutzer:
Very good !

I'll rebuild again with an possible working webp repo .. Maybe will fix all images issues.

So it was caused by pico gapps the optimizing issue ?

Yes u can try reparting again ... It can't hurt.

First stock repart then the latest , like mentioned on post #3
[Galaxy Ace II Android Development] Dr360r:
Yes, definitely pico gapps. Once i flashed the old pico gapps, it optimized only for one reboot then it stopped.

I'm installing 160616 again to check if Google Images was properly behaving then.
[Galaxy Ace II Android Development] ace2nutzer:
Don't use them at all .. Completly buggy.

Use better latest gapps from dev mardon
[Galaxy Ace II Android Development] Dr360r:
I was right. On ROM 160616 Google Images works properly. So some commit from 160718 onwards messed things up.

Hmmm... not so right. It still blurries up with the first images... checking with even older ROMs (160604 and 160526)

UPDATE: it's not working properly even with 160604. If you press the button to recall more than one page, the correct picture shows up, just like with Amazon. I'm starting to think it's due to something Google changed in the mobile site.
[Galaxy Ace II Android Development] ace2nutzer:
No problem ... now it's compiling again 31/08 ....

this time with only one reverted commit ... instead of 2 ... so pls test camcorder again later ...

it's up in approx 20 minutes.

Also it's compiling with an possible working webp repo .. so pls test Amazon pictures :)

Maybe we've luck .. this is a good chance.
[Galaxy Ace II Android Development] galac44:
I confirm that installing older opengapps 20160802 solved the optimizing issue for me too.
[Galaxy Ace II Android Development] Dr360r:
ROM 160831: camera recorder works, Google Images and Amazon not working properly.
[Galaxy Ace II Android Development] Dr360r:
On 160901, camera recorder works regularly. Google Images still doesn't show the first pictures. This happens even with 160510.
[Galaxy Ace II Android Development] heml0ck:
how do i install 0831 kernel? do i need to repart again like in post 3?
[Galaxy Ace II Android Development] ace2nutzer:
if u already reparted like on post #3 and at that time it was with reparted_v1.2.zip, then u only need to flash latest kernel package .. and recovery package in a row ...

Recovery because i've re-uploaded new version.... otherwise kernel only is enough. ...

btw: it's not worth it to flash only kernel now ... in approx 1 - 2 hours new CM11 FULL package is up .. which include all latest packages !

(so later u only need to flash ROM ,gapps (if not already installed from previous rom update...) and I8160P support if your Phone is 8160P with NFC functionality :) )
[Galaxy Ace II Android Development] ace2nutzer:
New ROM is Up !!

Changelog:

20160901 ROM:

Fixed Camcorder, thx [MENTION=6902149]Dr360r[/MENTION] for testing

Revert: Mediaserver: ram usage 65 @ 25%

Incl. ace2nutzer kernel 20160831

Incl. NovaThorSettings.apk V1.7.8

incl. latest cwm recovery package

AUTO wipes except factory reset

Status: "uploading" ... and it's up when u see "ROM ---> uploaded" on File: "latest" on FTP Server.

Works somehow really good now ! :)
[Galaxy Ace II Android Development] r0x0r1998:
I have random reboots on 1100mhz. A month ago, I had no problem with 1250.
[Galaxy Ace II Android Development] Culateralligator:
Right now testing last build... I'll comment how it's going.

Before this I was still having reboots... I was on 22-08-2016 ROM and had to install 13-08-2016 kernel, which was the last one with no reboots for me [MENTION=4867107]1100[/MENTION] MHz.
[Galaxy Ace II Android Development] dr@xxon:
Gray stripes appear rarely but appear.
[Galaxy Ace II Android Development] ace2nutzer:
with which kernel ?

Try pls both latest kernels .. normal + LCD.FIX.
[Galaxy Ace II Android Development] dr@xxon:
Gray lines appear with newest kernel LCD.FIX on my phone.
[Galaxy Ace II Android Development] ace2nutzer:
Ok, try pls the normal kernel .. and report how it goes :)
[Galaxy Ace II Android Development] dr@xxon:
With normal kernel appear too, but I think rarely than in older kernels.
[Galaxy Ace II Android Development] shaqman89:
Confirmed that I have reboots on latest ROM + kernel.

I think it's related to swap.

Here is last kmsg after a reboot https://www.dropbox.com/s/q1sm8dhil3o0fov/log--(Sep-2-2016)--(8h-00m-55s-PM).txt?dl=0
[Galaxy Ace II Android Development] ace2nutzer:
Thx, i'll check later...in the maintime can u pls post:

Used cpu config.

Content of all files in sys/kernel/liveopp/arm_step*
[Galaxy Ace II Android Development] shaqman89:
Sure, here you go:

u0_a40@codina:/ $ cat /sys/kernel/liveopp/arm_step*
[LiveOPP ARM Step 0]

Frequency show: 150000 kHz
Frequency real: 145920 kHz
ArmPLL: 0x00050113
Varm: 1000000 uV (0x18)
Vbbx: 0xdb
DDR_OPP: 25
APE_OPP: 25

[LiveOPP ARM Step 1]

Frequency show: 800000 kHz
Frequency real: 798720 kHz
ArmPLL: 0x00050168
Varm: 1162500 uV (0x25)
Vbbx: 0xdb
DDR_OPP: 100
APE_OPP: 100

[LiveOPP ARM Step 2]

Frequency show: 1000000 kHz
Frequency real: 998400 kHz
ArmPLL: 0x00050182
Varm: 1325000 uV (0x32)
Vbbx: 0xdb
DDR_OPP: 100
APE_OPP: 100

[LiveOPP ARM Step 3]

Frequency show: 1100000 kHz
Frequency real: 1098240 kHz
ArmPLL: 0x0005018f
Varm: 1387500 uV (0x3f)
Vbbx: 0x8f
DDR_OPP: 100
APE_OPP: 100

[LiveOPP ARM Step 4]

Frequency show: 1150000 kHz
Frequency real: 1152000 kHz
ArmPLL: 0x00050196
Varm: 1387500 uV (0x3f)
Vbbx: 0x8f
DDR_OPP: 100
APE_OPP: 100

[LiveOPP ARM Step 5]

Frequency show: 1200000 kHz
Frequency real: 1198080 kHz
ArmPLL: 0x0005019c
Varm: 1387500 uV (0x3f)
Vbbx: 0x8f
DDR_OPP: 100
APE_OPP: 100

[LiveOPP ARM Step 6]

Frequency show: 1250000 kHz
Frequency real: 1251840 kHz
ArmPLL: 0x000501a3
Varm: 1387500 uV (0x3f)
Vbbx: 0x8f
DDR_OPP: 100
APE_OPP: 100

[LiveOPP ARM Step 7]

Frequency show: 1300000 kHz
Frequency real: 1297920 kHz
ArmPLL: 0x000501a9
Varm: 1387500 uV (0x3f)
Vbbx: 0x8f
DDR_OPP: 100
APE_OPP: 100

u0_a40@codina:/ $
[Galaxy Ace II Android Development] ace2nutzer:
Looks like nt-app issue.. Will fix it later ...

For now u can delete nt-app and reboot.

Or:

Set permission for steps 3 - 7 to:

chown 0:0 (root:root)

Then set for steps 3 - 7 correct voltage:

echo varm=0x37 > arm_step03

Same for 04, 05 and so on.

and report if it fixed reboot on 1100mhz
[Galaxy Ace II Android Development] dr@xxon:
If the phone is longer locked the gray lines will more frequent .
[Galaxy Ace II Android Development] betagenius:
Problem with charging my phone

First of all, thank you for your good job on CM11. I have two problems:

1. When I turn off my phone and connect it to power for recharging, after several minuets it reboots and continue charging in sleep mode. This happens most of the times.

Does any one have this problem? I didn't have this problem before installing CM11 20160718. I used to have CM11 about two years ago without this problem till then.

2. After these unwanted reboots, most of the time I don't have any connectivity with whether wifi or phone network. I have to power off and turn it on again to solve this problem.

Any suggestion for solving these problems?
[Galaxy Ace II Android Development] shaqman89:
Noted. I’ll freeze nt app and see whether it'll occur.

It does happens rarely though so it might take time for a result.
[Galaxy Ace II Android Development] aggounAmine:
Yes[emoji8]
[Galaxy Ace II Android Development] ace2nutzer:
ok, if it sucks u can test different video.modes with LCD.FIX kernel ...

1. Combination: open file "mcde_chnl" .. there u can see current video.modes ... now just make echos to this file like mentioned before .. and try to set ALL video.modes values to "8"...

everytime u edit video.modes, to make them effect .. u'll need at the end to write:

echo update > mcde_chnl

then test how it goes.

Variant 2:

u can try with SAMSUNG Stock Values .. taken from JB Kernel:

https://github.com/ace2nutzer/Samsu.../arch/arm/mach-ux500/board-codina-mcde.c#L463

or if they will also not work properly .. u can test with SAMSUNG Stock GB Kernel Values:

https://github.com/ace2nutzer/Samsu.../arch/arm/mach-ux500/board-codina-mcde.c#L151

If all variants doesn't work well, then your LCD is most probably broken ...

anyway there is still a chance to workaround this malfunction by finding a set of video.modes + maybe also a different LCD Freq that simply avoid your issue .. but it will be very difficult ... also u'll see that with SAMSUNG Stock Values your LCD will lagg + screen glitches like hell ... :)

do u mean u change your phone in low-power-mode (completely off) and then after some minutes it just start to boot to the system by itself ?

So far nobody had this issue ... .. dunno whats wrong with your config.

ok, but make anyway sure that the mentioned steps03 and higher are running with varm 0x37 ... otherwise it's not stable.
[Galaxy Ace II Android Development] shaqman89:
Yes, it's running with Varm 0x37 for steps 3 and above. So far, no reboots yet. I'll give it a day of two though before making it a final conclusion.

u0_a40@codina:/ $ cat /sys/kernel/liveopp/arm_step*
[LiveOPP ARM Step 0]

Frequency show: 150000 kHz
Frequency real: 145920 kHz
ArmPLL: 0x00050113
Varm: 1000000 uV (0x18)
Vbbx: 0xdb
DDR_OPP: 25
APE_OPP: 25

[LiveOPP ARM Step 1]

Frequency show: 800000 kHz
Frequency real: 798720 kHz
ArmPLL: 0x00050168
Varm: 1162500 uV (0x25)
Vbbx: 0xdb
DDR_OPP: 100
APE_OPP: 100

[LiveOPP ARM Step 2]

Frequency show: 1000000 kHz
Frequency real: 998400 kHz
ArmPLL: 0x00050182
Varm: 1325000 uV (0x32)
Vbbx: 0xdb
DDR_OPP: 100
APE_OPP: 100

[LiveOPP ARM Step 3]

Frequency show: 1100000 kHz
Frequency real: 1098240 kHz
ArmPLL: 0x0005018f
Varm: 1387500 uV (0x37)
Vbbx: 0x8f
DDR_OPP: 100
APE_OPP: 100

[LiveOPP ARM Step 4]

Frequency show: 1150000 kHz
Frequency real: 1152000 kHz
ArmPLL: 0x00050196
Varm: 1387500 uV (0x37)
Vbbx: 0x8f
DDR_OPP: 100
APE_OPP: 100

[LiveOPP ARM Step 5]

Frequency show: 1200000 kHz
Frequency real: 1198080 kHz
ArmPLL: 0x0005019c
Varm: 1387500 uV (0x37)
Vbbx: 0x8f
DDR_OPP: 100
APE_OPP: 100

[LiveOPP ARM Step 6]

Frequency show: 1250000 kHz
Frequency real: 1251840 kHz
ArmPLL: 0x000501a3
Varm: 1387500 uV (0x37)
Vbbx: 0x8f
DDR_OPP: 100
APE_OPP: 100

[LiveOPP ARM Step 7]

Frequency show: 1300000 kHz
Frequency real: 1297920 kHz
ArmPLL: 0x000501a9
Varm: 1387500 uV (0x37)
Vbbx: 0x8f
DDR_OPP: 100
APE_OPP: 100

u0_a40@codina:/ $
[Galaxy Ace II Android Development] ace2nutzer:
@ up

ok, that looks great :)

so now i've uploaded new NT-APP ....

NovaThor Settings v1.7.9

Fixed CPU Voltages for 1100 - 1300Mhz
[Galaxy Ace II Android Development] shaqman89:
Thanks. That was fast :)

Should I directly try that or just let it be for now?
[Galaxy Ace II Android Development] ace2nutzer:
it's more convenient to continue testing stability on 1100Mhz .. for another day ... then u can flash latest NT-APP .. it just sets correct voltage like in kernel ---> 0x37 .. nothing more :)

https://github.com/ace2nutzer/andro...mmit/dbb878371931f621a758e0020356c18d7c22b2a3