yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] PolishVodka:
Chrono

I wanna ask about OTG support.

It is not supported at all for our phone? So, codinalte (Meticulus) was used same hacks like Novafusion in golden and didn't support OTG?

And maybe this is because outdated musb driver? When I plugged cable then status in /platform/musb-ux500.0/musb-hdrc/mode is changed to "otg", but " vbus" state isn't changed, so maybe this is a reason...

And as I know Sony STE devices has OTG support even in Gingerbread, maybe some stuff from this devices will help us to got OTG support.
[Galaxy Ace II Android Development] ChronoMonochrome:
I'm afraid, it's not supported at all. U8500 has a several revisions, and it's most likely that codina/janice uses that one which doesn't support OTG. It's just my guess.

Isn't codinalte has u8520 board, like golden? If so, then we can't count on this, since u8520 basically just a later version of u8500.

This is also possible. I myself tried to use stuff from sony u8500 devices, but unsuccessfully. Afaik, cocafe said sometime ago, that our devices doesn't have write access to musb registers(when sony devices has) - when you're trying overwrite them, you'll get reboot.
[Galaxy Ace II Android Development] ace2nutzer:
Today i was thinking exactly the same .. i can't believe that we don't have full OTG Support .. at least Vbus on the mini-usb port is working...

The rest is just Kernel + ROM missing driver.

I've seen in kernel there are many OTG Options .. they are all disabled ... maybe i should build an test build with all OTG Stuff enabled..

Up to now i never tried this because i don't have an OTG Cable .....

EDIT:

check this:

http://xdaforums.com/showpost.php?p=37454572&postcount=9
[Galaxy Ace II Android Development] Alex_Gamer:
But you don't know if there something that I can do? Maybe another format or someone else. :/

Enviado desde mi GT-I8160 mediante Tapatalk
[Galaxy Ace II Android Development] ChronoMonochrome:
This might be due to sdcard with exfat partition.

Personally I don't use exFAT, so I can't check it. But I can recompile kernel with exFAT built-in, but no promises that it'll solve a problem.
[Galaxy Ace II Android Development] Alex_Gamer:
Please Chrono, if you have time recompile the kernel with exfat built-in

Enviado desde mi GT-I8160 mediante Tapatalk
[Galaxy Ace II Android Development] ChronoMonochrome:
I was testing some liveopp stuff, and just enabled exfat at one.

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

Beware, this is a test build and it doesn't contain any bootscripts/recovery - flash ONLY from r3.x.
[Galaxy Ace II Android Development] PolishVodka:
Yes, I know is it little bit dangerous to working on OTG if you are not 100% sure what's you do...

But why even on stock firmwares (GB and JB) we have some stuff from Samsung to OTG support like in framework.res/storage_list_xml, vold binary, vold.fstab (mount point to musb)...I thinking in stock Roms we have everything except kernel to support OTG.

Golden has even older U8420 board as I remember, but Novafusion's done some workaround (maybe dangerous) for OTG and phone must be restarted after using OTG because of battery drain.

About options in kernel for OTG, I was trying almost everything (after comparing to Xperia U) but without luck.
[Galaxy Ace II Android Development] manthes:
I copied the folder osfiles from 2.23 kernel to 3.2 because it was the only way to install latest build. It will affect the kernel? I see that it boot ok with this solution
[Galaxy Ace II Android Development] jiguan:
64 GB SD card works SanDisc @10 tested default format Loading takes longer time of course.
[Galaxy Ace II Android Development] Alex_Gamer:
Chrono, the test release won't worked and I see that my sd card is vFat
[Galaxy Ace II Android Development] Nargacuga-XDA:
Flash

Could someone teach me how to install this kernel.. Because i dont really understand the explain in the first post.. About the terminal section and osfiles section, could someone explain to me more detailed??
[Galaxy Ace II Android Development] Noxialis:
Update on my heat up situation:

Amusingly, r3.2 didn't have the heating problem that r3.1 had.

Earlier, I was trying to figure out why the phone was heating up so much, even when I left it alone.

It shut itself down a number of times, those being when the heat was way above-average (feels too hot to touch at first).

Everytime I power up the phone after having it cool down, it always optimizes apps.

When I got tired of that situation, I flashed 3.2.

So far, phone's heat is normal, doesn't go beyond average.
[Galaxy Ace II Android Development] S.AMU:
I wanted to say a big thank you to ChronoMonochrome, ace2nutzer, PolishVodka, TeamCanjica (Rox) all the other developers here and also to all the users, testers, feedbackers and bug-finders to make our loved Ace2 a better phone.

For me this will be one of the latest posts here in this section, because after 2 Samsung phones and 8 years Samsung I changed to another brand.... I just bought an amazing LG G3 32gb :)

Also I don't have enough time anymore (studying, working to pay my studies and real-life) to go and follow the development of two phones.

I will still use my Ace 2 sometimes, especially for working because it was always with me the last 3,5 years, even in extreme situations (from -40 degrees up to +55 degrees) and I don't want to break my LG immediately :D

So from now on, you will find me more in the LG section and - [MENTION=5840412]ace2nutzer[/MENTION], [MENTION=5695278]ChronoMonochrome[/MENTION], [MENTION=4881398]PolishVodka[/MENTION], [MENTION=4947931]Rox[/MENTION] - If ever you buy a new phone, buy an LG G3. We need good developers there to support Android M, N, O and perhaps Q when its released. :)

Thank you for this great time :)
[Galaxy Ace II Android Development] xo.en:
Thanks man, for everything you did.
[Galaxy Ace II Android Development] PolishVodka:
[MENTION=5382590]S.AMU[/MENTION]

Thank you, G3 will be my next phone too.
[Galaxy Ace II Android Development] xo.en:
Another sad day....

Have fun, gl. So much fun awaits you...thank you for a2 dev'ing(temporary term, sorry - dev'ing, devvin'g, yeti, hm)?.
[Galaxy Ace II Android Development] slake84:
Is there any changelog for R3.2?

In the http://xda.mister-freeze.eu/XDA-files/ChronoMonochrome/kernel/changelog/changelog.html there is only for R3.1
[Galaxy Ace II Android Development] ChronoMonochrome:
Search here in topic for changelog. I had no PC available when releasing to write changelog in that file.
[Galaxy Ace II Android Development] manthes:
Can i change cpu voltage from chronokernel app? I have set it to -100V without any reboot but i don't know if is working the app or not
[Galaxy Ace II Android Development] borkins:
You can check it.

Open the file "/sys/kernel/liveopp/arm_summary", after setting the voltage with the app.

Or try with my script.
[Galaxy Ace II Android Development] PolishVodka:
Chrono

Just wanna say, this commit for system rebooting when charger connected, this doesn't work as I expected (does this sound like is made special for me?Hope no.)

Because now phone do shutdown (that's OK of course), but it shouldn't turn on in LPM (offline charging) now? It should.
[Galaxy Ace II Android Development] ChronoMonochrome:
Yes, for now it just prevents phone from being to be rebooted. Ideally, it should reboot phone(rather than shutting down) with passed to the command line parameter lpm_boot=1. I've described a possible implementation of this, but it appeared to be a pain to implement it.
[Galaxy Ace II Android Development] PolishVodka:
So, better revert this?

Anyway, S6D driver working smooth here, without any modifications.

PS. Do you know where is commit for this network data indicators (on signal icon)?

I doesn't see it in TC sources..
[Galaxy Ace II Android Development] ChronoMonochrome:
I thought that the phone reboots to LPM when was submitting that patch, but apparently, it just reboots to the system. I think both options are bad, but IMO shutting phone down is more logical than just rebooting.

Did you mean that it works better with https://github.com/ChronoMonochrome/Chrono_Kernel-1/commit/0d5b0f64c3b498f663121415e6101a421aa1fcec ?

It should probably be these commits

https://github.com/SlimSaber/framew...stemui/statusbar/policy/NetworkStatsView.java
[Galaxy Ace II Android Development] ace2nutzer:
Nope, i think he mean it works also good with stock freq 30,7Mhz and Stock video_modes = 63/63 on Jelly Bean.

In my kernel it's 36,3Mhz and video_modes 5/5 because otherwise it's not really lagfree when playing games on CM11 (2D)

But, if the user will select in NT-APP 30,7Mhz with the S6D LCD... then it's not smooth like with stock video_modes .. that's the problem for PolishVodka because he is using Jelly Bean :)
[Galaxy Ace II Android Development] PolishVodka:
Yes, generally it is smooth like it should on stock frequency. On CM12.

No, I mean on kernel side. I know some of Roms doesn't even have it, but it was fixed in kernel sources from CM10.2 where indicators wasn't visible.
[Galaxy Ace II Android Development] ChronoMonochrome:
I might be wrong, but AFAIK, from kernel side is required this commit https://github.com/ChronoMonochrome/Chrono_Kernel-1/commit/084db04772e331f2fdc803e8c105b64dac6f8bd1 .
[Galaxy Ace II Android Development] ChronoMonochrome:
R3.3

New release R3.3 is up!

Changelog:

compiled exfat driver built-in (so that probably there are now less problems for exfat users, but not tested by me)

adjusted HZ for more responsive UI

enabled LED on End of Charge ( [MENTION=5840412]ace2nutzer[/MENTION]'s idea) - use /sys/module/abb_chargalg/parameters/eoc_blink to enable/disable this feature.

lcdclk: set S6D default frequency in kernel, not via script

ws2401: allowed to change videomode parameters on-the-fly via interface /sys/devices/pri_lcd_ws2401.0/mcde_chnl

for details, read https://github.com/cocafe/i9070_Kernel_CoCore-E/commit/691be773031b563bc53768f8de89f771f1bbcc33

beware, that some parameters might cause graphical glithes. Make any changes only if you know what you do!

allowed forcibly disable accelerometer in kernel level (yup, some annoying apps was using it even if you disable it in ROM settings)

echo 1 > /sys/module/alps_input/parameters/disable

added in-kernel support to skip tracks by pressing volume rocker

This is added only for ROMs which doesn't have it, and most likely will interfere if this feature is enabled in ROM.

Module parameters ( /sys/module/gpio_keys/parameters/...):

- volkey_press_skip_track - enables this feature. Usage:

echo 1 > /sys/module/gpio_keys/parameters/volkey_press_skip_track

- volkey_long_press_delay_ms - long volume key press delay before track will be skipped

- volkey_do_volume_key_press_delay_ms - next/previous track emulated key press delay

- volkey_skip_tracks_in_suspend_only - set to 0 if you'd like to skip tracks not in suspend only

Full changelog
[Galaxy Ace II Android Development] Ave_Hornet:
Phillz Recovery is still in use with R3.3.
[Galaxy Ace II Android Development] ChronoMonochrome:
Forced recovery change is reverted in R3.3, forgot to mention. Hopefully, new changes in genfstab will no more cause problems on some recoveries.
[Galaxy Ace II Android Development] dixee:
i had a bootloop when installing R3.3 kernel in your CM build 2015-7-30, revert back to R3.2 kernel version
[Galaxy Ace II Android Development] matthias1976:
no problems for me installing 3.3

codinaP + Chrono`s latest CM 11 + twrp
[Galaxy Ace II Android Development] shaqman89:
No problem here with codina, using vanir and latest cm, both built by [MENTION=5695278]ChronoMonochrome[/MENTION]
[Galaxy Ace II Android Development] dixee:
i try installing R3.3 kernel two times with bootloop, also with wipe cache/dalvik, no luck.

revert back to R3.2 boot normal again.

mine is non P codina with latest chrono cm11 too

---------- Post added at 03:44 PM ---------- Previous post was at 03:41 PM ----------

i'm using latest cm11 chrono, with twrp, i tried two times installing R3.3, after success install, reboot recovery (twrp) then reboot system resulting into bootloop,
[Galaxy Ace II Android Development] ChronoMonochrome:
Post last_kmsg, please.
[Galaxy Ace II Android Development] matthias1976:
i got camera app fc when opening with 3.3

revert to 3.2 still got cam app crashing.

but before on 3.2 it worked !?!?

codinaP + Chrono`s latest CM 11 + twrp
[Galaxy Ace II Android Development] ChronoMonochrome:
Latest CM11 builds has this bug(this is not kernel related), and I still haven't found fix so far.
[Galaxy Ace II Android Development] matthias1976:
i came from 3.2 kernel and cam worked !!

installed 3.3 cam fc.

reverted to 3.2 and still dont work.

i didnt change cm11 build !?
[Galaxy Ace II Android Development] ChronoMonochrome:
The fact that is how this bug appears is random.
[Galaxy Ace II Android Development] matthias1976:
bummer its now every cam start !!

never had before.

any idea ? can i use other cam app ?

what about this !?
[Galaxy Ace II Android Development] fluffi444:
http://www.apkmirror.com/apk/cyanog...a-2-0-004-5fa8c79c0b-30-android-apk-download/
[Galaxy Ace II Android Development] dixee:
Now, i can't open Gmail, it say Unknown issue with Google Play Services, but i can open google play store and download apk.

Before trying installing R3.3 kernel i didn't get this error.

this log file correct? currently i'm using R3.2 kernel

last_kmsg

https://drive.google.com/file/d/0B5k9mywc9HICempoRzlrZWN5eEE/view?pli=1

log_cat

https://drive.google.com/file/d/0B5k9mywc9HICcDlhS1lEaUJGR28/view?pli=1

i think, there is left over script or something from R3.3 kernel when i return to R3.2 kernel ?

thanks before :D
[Galaxy Ace II Android Development] matthias1976:
i know this app, thx fluffi !!

i used on 3.2 kernel and it worked.

standard app worked too.

but now standard app, cyanogen cam and google app wont work anymore.

just updated to 3.3 and revert to 3.2

---------- Post added at 01:28 PM ---------- Previous post was at 01:03 PM ----------

Installed ur latest cm11 again an camera app working again.

So kernel 3.3 overwrite something that 3.2 doesnt undo !?
[Galaxy Ace II Android Development] manthes:
And with this kernel as with every latest kernel i have the same problem that it stucked at samsung logo.

I copied osfiles folder from kernel 2.23 to 3.3 to make it work
[Galaxy Ace II Android Development] ChronoMonochrome:
It was meant that you make log once you faced bootloop(and rebooted to recovery). This log is captured from successfully booted r3.2, unfortunately it won't help with fixing installion issue.

Are you still using JB liquid smooth? On some JB ROMs(I faced it on 4.2.x slimbean) it was needed to use original ROM fstab to make it boot.
[Galaxy Ace II Android Development] manthes:
I am using liquid smooth 4.4 but the installation problem started with 2.41 kernel if i am not wrong.

Not a big deal just replacing the folder from older kernel to latest. Just mentioning it. And no camera fc problem for me
[Galaxy Ace II Android Development] dixee:
like this ?

last_kmsg

https://drive.google.com/file/d/0B5k9mywc9HICdFMyejBfdHpMbms/view?pli=1

logcat

https://drive.google.com/file/d/0B5k9mywc9HICRGFhYURiOEhfb3M/view?pli=1

i generate this log using Syslog apk, after first time boot with R3.2 kernel (previously try to install R3.3 kernel again and bootloop again). this is correct ? or you can guide me the right way to create log file for bootloop?
[Galaxy Ace II Android Development] fluffi444:
Thx for this update.

No problems at all here - No bootloop - No FC of camera or any other app. Updated from R3.2.
[Galaxy Ace II Android Development] shaqman89:
[MENTION=5695278]ChronoMonochrome[/MENTION] actually has explained it quite well.

When you got the bootloop, go back into recovery, and from there take the logcat.

Using adb should be the easiest way like it is mentioned in op.
[Galaxy Ace II Android Development] dixee:
ok i'll try later, cuz i'm busy now. mksh. :D
[Galaxy Ace II Android Development] xo.en:
0 problems when upgrading from 3.2 and vanir, overall gui/2d fluidity fluidity on s6d seems to be better now, i wonder how it will affect battery lifetime...

now, only drawback of that machine is a bit low screen resolution, imho.

Btw - why call volume is LOW? I thought, that this issue was solved some time ago...

pps: chronokernelsettings is not able to add custom gov/schedulers anymore(it occurs since 3.2) :(

TWRP - i am not fan of twrp, but let me say, Ave_Hornet's themes for twrp seem to work(but, there is totally missaligned swipe to unlock, kinda weird :) ).

http://xdaforums.com/galaxy-ace/ace-2-apps/twrp-materialised-t3066650
[Galaxy Ace II Android Development] ChronoMonochrome:
Try freeze/remove system/app/CallService.apk. CM11 doesn't have and I doubt if it's needed at all. This apk contains probably not working low-incall volume fix which might interfere with another one. I didn't remove it so far only because I thought it wouldn't be a problem.

Will check it when I have time..
[Galaxy Ace II Android Development] dixee:
finally succesfull install R3.3 kernel, after some trial install with error bootloop, wipe dalvik/cache, fix permission, also delete last_kmsg file when on R3.2 kernel

chrono, can i use built-in file manager in TWRP recovery menu to copy last_kmsg file (from /proc folder) into ext memory card?

(if get into bootloop again)

because i just know that, i can see/browse last_kmsg file from file manager recovery menu. :D

thq :)

it
[Galaxy Ace II Android Development] ChronoMonochrome:
Why not? I don't see any reason why it wouldn't be possible.
[Galaxy Ace II Android Development] dixee:
ok great, I just found out now. it would be the easiest way. cause i never fetch any log file from my phone before :D .unfortunately i can't get kmsg log for previous bootloop issues again.

so far R3.3 kernel running well, only google play services issues when opening gmail still exist , maybe it caused by bootloop problem yesterday....:(
[Galaxy Ace II Android Development] manthes:
So all ext4 versions now have twrp?
[Galaxy Ace II Android Development] biggstreet:
thank you for sharing !

what the date of the bluid did you use !

Thank you again !
[Galaxy Ace II Android Development] RootPegasus:
if I use kernel, whether my SDCard must repartitioned?
[Galaxy Ace II Android Development] Alwer:
No
[Galaxy Ace II Android Development] zizoumadrid:
i use 9 08 2014 build ;)
[Galaxy Ace II Android Development] fluffi444:
Next report for codinap 12082014 ext4

- NFC works (tested with real NFC chip... reading... writing.. etc)

- Boottime: 8333 (fast!)

- Nothing else to mention up to now...

GOOD WORK! :good::highfive:
[Galaxy Ace II Android Development] biggstreet:
Thank youu ! i will test it now
[Galaxy Ace II Android Development] dv6661:
i see many good review in here, so i decided to try this kernel,

but what should i choose if i come on standart 4.4.4 PA

ext4/f2fs ?

thanks before
[Galaxy Ace II Android Development] fluffi444:
Ext4 normally.

For f2fs you will need the partitions Data and Cache formarted acorrding to this.
[Galaxy Ace II Android Development] xo.en:
Hmm, with 4.3.x kernel i had 8093ms on liquid.
[Galaxy Ace II Android Development] fluffi444:
Than be happy... on Rox's CM11 4.4.4 I have normally aprox 8700... and 8300 ist fast... For me...

Maybe ROM dependent.
[Galaxy Ace II Android Development] farru1981:
A2DP suttering :(

Hi, for some time I thought that this kernel fixed my ad2p stuttering problem when a notification arrives, but it wasn't true. The problem came back :crying:

I have been messing around with some settings (turning wifi off, silence notifications...) without success.

It seems to be that it only happens when the screen is off while the player is streaming music using ad2p (maybe related to some deepsleep state and bt priority?).

So I tried OnDemand Governor and Interactive but also without success. I am using sioplus i/o scheduler.

The min cpu freq I have is 200Mhz and max 800, increasing min to 400 seems to be more efficient and decreases the stuttering (not totally dissapear), but it causes a much faster battery drain :(

Tried 04082014 and 12082014 kernel versions, the behaviour was the same. BTW this is the only issue I have, everything else is working OK.

Any suggestions?

--

Regards,
[Galaxy Ace II Android Development] Rox:
Last few releases boot time on stock cm kernel is decreased to 8300
[Galaxy Ace II Android Development] fluffi444:
OK - Than I should say for cm-11-20140706-UNOFFICIAL-codinap, the Boot time was/is aprox 8700 :D
[Galaxy Ace II Android Development] manthes:
With latest build i have problem with the screen while i am scrolling a page. I don't know if this is screen tearing.

I went back to previous build with TWRP
[Galaxy Ace II Android Development] jadega:
Can u make this kerenal for s advance its almost same as Ace 2 in all aspects!!!
[Galaxy Ace II Android Development] ChronoMonochrome:
I can not understand why this problem appears only for some users. I have never got this problem. I tried to decrease PRCMU_DPI_CLK_SMD_FREQ to 49920000 (according to this post http://xdaforums.com/showpost.php?p=51294416&postcount=47 ) and only then I started to notice screen tearing.
[Galaxy Ace II Android Development] manthes:
I have s6d driver. With previous build with TWRP i didn't noticed it
[Galaxy Ace II Android Development] biggstreet:
This kernel is really awsome

i use it with a stock jb rom ! it's verry smoother and no reboot until now

Thank's man
[Galaxy Ace II Android Development] muxa1980:
Which firmware use and which version of chronokernel?
[Galaxy Ace II Android Development] borkins:
[MENTION=5695278]ChronoMonochrome[/MENTION], look at this screenshots, if you have time.

1. On first sc-shot, If:

'power_supply_charge_now=803848'

then

'power_supply_capacity_level_raw=636' - actually must be ~ 536.

( 803.848 mAh / 1500 mAh ) x 100 = 53.589867 %

2. And is this correct:

'power_supply_voltage_max=606' :?

'power_supply_voltage_min=3784000'

Later, on the next sc-shot:

'power_supply_capacity_level_raw=394' - now it's accurate.

Once I mentioned about this [URL="http://xdaforums.com/showpost.php?p=61908428&postcount=3270]here[/URL], and looks that it's old hidden thing ( bug, issue or whatever).

This shots are taken on latest kernel r3.3, after reboot.

Well, maybe this is not so important thing now. I needed that mostly for my battery monitor script. :)
[Galaxy Ace II Android Development] shadow252:
Thanks [MENTION=5695278]ChronoMonochrome[/MENTION]! With ChronoKernel r3.3 OmniLP works better. :)
[Galaxy Ace II Android Development] fluffi444:
Not only on Omni - CM11 as well :o - General response and UI look'n'feel is faar better!

I thing this frequency change to 1000Hz (?) made the trick!

I got no noticible battery drain because of this or Kernel 3.3.
[Galaxy Ace II Android Development] xo.en:
Ok, i'll check this.

upd: callservice removal seems to work fine. Call volume is much louder..i think.
[Galaxy Ace II Android Development] PolishVodka:
https://github.com/ChronoMonochrome/Chrono_Kernel-1/commit/651d5ce54b20202e2765bc92548d9176793ff341

Chrono

This higher HZ really makes a big difference for responsive?

Personally I didn't feel any difference between stock 100 and 500,700 or 1000. Only visible changes is faster kernel booting, but this is the same time for 200 and 1000 in my case. So, why is so high?
[Galaxy Ace II Android Development] ChronoMonochrome:
For me it makes UI much responsive, with a cost of a bit increased CPU usage(CPU freq is a bit higher than usual). But I think HZ=1000 was too high.. Had a two HZ-related crashes - will set to 700 in the next build.

I don't know why for you there's no difference in boot time between 200 and 1000 HZ. From what I remember, than higher was HZ, the less was boot time for me. However, I never understand this "mystical" boot time reduce and I considered this just as an extra bonus.

Maybe it's due to wrong formulae.. Need to look at sources, because so far I don't know what the difference between power_supply_capacity_level_raw and power_supply_capacity calculation - besides of that the latest is rounded to the whole.