yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9500 Original Android Development] lukair1983:
Thanks Andrei for checking it out and for this information. If you would be so kind as to look into it (if the adapter can accept more current and do something about it) in some spare time (nothing urgent), I'm sure many people would appriciate it, not only me. It's really a pain to use the MHL adapter, if it drains the battery even though it is connected to the power outlet. It's ridiculous on Samsung's part :/

Thanks for the info Andrei. I see that with flashing new kernel synapse is there. Is it safe to uninstall the STweaks now, or is Synapse dependant on STweaks?

(I tried to uninstall STweaks, but it tells me it cannot uninstall it - should I stop some service that is corresponding with it or sth?)

The Synapse app crashes on my device every other start. No big deal, just asking if others have the same expierience?
[Galaxy S 4 i9500 Original Android Development] Cleverfish:
on my device it booted completely but force close when i tried to open it.

Sent from my GT-I9500
[Galaxy S 4 i9500 Original Android Development] lukair1983:
Same here, flashed ok, booted ok, and what's more important (don't know it it's just a fluke) :), my headphones were connected during restart but the sound is there after complete reboot (before when I left my headphones connected, the sound was gone after reboot :/)!!! Very happy.

As for the Synapse problem, same here. It crashed on first run, but on second it loaded up with no problems. Third time crash, fourth time ok, fifth crash... you know where I'm heading with it :>
[Galaxy S 4 i9500 Original Android Development] Cleverfish:
i'm still looking for the cause. uninstalling few apps, also disabling wanam xposed but the problem was still there. but i found this error on catlog:

09-26 03:21:48.837 E/runCommand->flushError (8933): /res/synapse/actions//colour[39]: printf: not found

09-26 03:21:48.842 W/dalvikvm(8933): threadid=15: thread exiting with uncaught exception (group=0x40f6e930)

09-26 03:21:48.842 E/AndroidRuntime(8933): FATAL EXCEPTION: Thread-657

09-26 03:21:48.842 E/AndroidRuntime(8933): java.lang.StringIndexOutOfBoundsException: length=0; index=0

09-26 03:21:48.842 E/AndroidRuntime(8933): at android.graphics.Color.parseColor(Color.java:211)

09-26 03:21:48.842 E/AndroidRuntime(8933): at com.af.synapse.elements.SColourPicker.getLiveValue(SColourPicker.java:183)

09-26 03:21:48.842 E/AndroidRuntime(8933): at com.af.synapse.elements.SColourPicker.getView(SColourPicker.java:123)

09-26 03:21:48.842 E/AndroidRuntime(8933): at com.af.synapse.MainActivity$tabSectionFragment.prepareView(MainActivity.java:238)

09-26 03:21:48.842 E/AndroidRuntime(8933): at com.af.synapse.MainActivity$SectionsPagerAdapter.buildFragment(MainActivity.java:140)

09-26 03:21:48.842 E/AndroidRuntime(8933): at com.af.synapse.MainActivity$SectionsPagerAdapter.access$300(MainActivity.java:130)

09-26 03:21:48.842 E/AndroidRuntime(8933): at com.af.synapse.MainActivity$SectionsPagerAdapter$2.run(MainActivity.java:173)

09-26 03:21:48.842 E/AndroidRuntime(8933): at java.lang.Thread.run(Thread.java:856)

i don't understand what it means.. :confused:

Sent from my GT-I9500
[Galaxy S 4 i9500 Original Android Development] djigane:
Here my installation steps for new kernel:

Reflashed rom w/ wiping cache and dalvik only

Removed stweaks from system/app with root Explorer.

Reboot into recovery and flashed new kernel.

Everything's working fine. No problem with synapse, even updated it from play store.

[MENTION=4167023]AndreiLux[/MENTION], thanks for the improved Grey scaling in screen settings, now black is really black!
[Galaxy S 4 i9500 Original Android Development] cmd512:
Gents, quick question as I don't see it addressed on Andrei's github or here:

Will Synapse auto-import your current settings from STweaks? Or, will that have to be setup from scratch?

(Lots of custom voltages & other settings...)

Cheers!
[Galaxy S 4 i9500 Original Android Development] Grarak:
Not sure but I guess command string is not defined

https://github.com/AndreiLux/Synaps...m/af/synapse/elements/SColourPicker.java#L180

https://github.com/AndreiLux/Synapse/blob/master/src/main/java/com/af/synapse/utils/Utils.java#L130

Andrei will fix this and do not report any bugs anymore

"This is the first public release. I'm not interested in bug reports or things alike, I'm aware of them."

https://github.com/AndreiLux/Perseus-UNIVERSAL5410/wiki/Changelog
[Galaxy S 4 i9500 Original Android Development] jujuburi:
I see that the speaker band gains are enabled by default, was it the same on the previous version?
[Galaxy S 4 i9500 Original Android Development] NBruderman:
Yes it was
[Galaxy S 4 i9500 Original Android Development] alijee:
no, you have to reset everything..

btw I dnt have any crashes in synapse or anything... everything is running really smoothly, only I m not able to edge enhancement in screen settings in synapse... otherwise synapse feel much faster than stweaks.
[Galaxy S 4 i9500 Original Android Development] NBruderman:
For those who have problems with synapse, to go back to alpha 9, remove synapse as system app, then install it from the play store and then flash alpha 10 again, it worked for me
[Galaxy S 4 i9500 Original Android Development] jujuburi:
What problems are they? I mean it's working okay for me, I think, but when I click on the ✓ or ☓ nothing happens, same with you?
[Galaxy S 4 i9500 Original Android Development] lian_diary:
I have no problem with synapse, I just have wiped the cache and everything works :good:

but I still have a question: can I direct edit the synapse profile with a notepad just like stweaks?I feel that should be easier as edit it in itself,but I don't find the file. if somebody know that, pleas tell me.
[Galaxy S 4 i9500 Original Android Development] cmd512:
I don't see why not, just edit one setting, reboot, and check. If it works, then it should work for all of them...
[Galaxy S 4 i9500 Original Android Development] carlosm15:
no luck for me with your procedure, nor wiping cache, nor wiping appdata, nor disabling wanam xposed, so i have to wait for the fix:crying:

when i open the app see the loading circle and then, i get an FC...
[Galaxy S 4 i9500 Original Android Development] Cleverfish:
what is your rom version? i'm on stock rom XXUBMG1.

Sent from my GT-I9500
[Galaxy S 4 i9500 Original Android Development] carlosm15:
UBUBMH1
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
There is no file, it's stored in a database.

And no I don't import STweaks values because they're incompatible, you'll have to move manually.

As for the bugs, I'll figure them out slowly in due time.
[Galaxy S 4 i9500 Original Android Development] omvir:
Idk if its just me or if this is a known issue. But when I check the "enable edge enhancement box" and press apply it will enable the effect BUT the box will become unchecked.
[Galaxy S 4 i9500 Original Android Development] mw86:
Left a 5-star review on Play Store for the new awesome that hit the store. Thanks Andrei, excellent work on the new alpha thus far and I love the new app Synapse. I will be glad to pay for the premium version when it is finished.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
You seem to be missing a ROM-side busybox. (Thanks for log)

I recompiled the kernel included one with printf support, it should fix this particular issue. Download 10pre3.
[Galaxy S 4 i9500 Original Android Development] Cleverfish:
it's working! Thanks AndreiLux :thumbup: :D

Sent from my GT-I9500
[Galaxy S 4 i9500 Original Android Development] Caspersky83:
Hi AndreiLux, thanks for a great work!

I and some of my friends have a bug in Synapse: the first launch is ok, but the second launch leads to a crash. Solution is a long press of the home button and remove it from the list of tasks, by doing so, Synapse runs every time.
[Galaxy S 4 i9500 Original Android Development] hussam1988:
all good flashed it yesterday
[Galaxy S 4 i9500 Original Android Development] beatsmaster0510:
Supercurio just released his own kernel to achieve full root to i9500. Hope to have that integrated to Perseus.
[Galaxy S 4 i9500 Original Android Development] drziddo:
LOVING IT

Hello OP and everyone.

Using the kernel since 3 days ago.

Very very good so far, maybe a little overheating.

One thing: Tring to find if the overheating is kernel related, I flashed back the rom I am using (Wanam's) and when the phone boot up it was all muted.

No sounds at all.

I had to reflash this kernel again.

Is that a known issue or is just me doing things wrong?

Sorry if this is too n00bish.

Thanks in advance.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
You're asking for something which has no point in being in this kernel; cofface achieved that 2 weeks ago as did Wanam with his kernel, and I've stated that I'll include a root method in the first proper release once it comes.

As predicted, the uninformed and blind followers are eating up the misinformation and PR nonsense around Supercurio's root method.

[MENTION=2660441]drziddo[/MENTION], I wasn't able to reproduce the sound thing people report; clean out your Dalvik if it arises, might be due to the upstreamed sound drivers. I also did some mods to the real release so that might fix it too.
[Galaxy S 4 i9500 Original Android Development] drziddo:
Drooling in advance. :laugh:
[Galaxy S 4 i9500 Original Android Development] jlevy73:
I've had this problem before and here's what I did to resolve it:

1. Flash a stock FW through Odin http://samsung-updates.com/device/?id=GT-I9500

2. Hold down volume up, menu button and power to enter stock recovery

3. Wipe data and cache and let the phone reboot

4. Sound is back

---------- Post added at 04:25 AM ---------- Previous post was at 04:24 AM ----------

Unfortunately, Dalvik doesn't seem to resolve it.
[Galaxy S 4 i9500 Original Android Development] beatsmaster0510:
I am currently using cofface' root and Perseus since the release of both programs. Sorry if I appear uninitiated but I'm glad you will include a root method on the proper release. Also, I haven't flashed Supercurio's kernel since I will only gain root which I already have and stability Perseus offers right now.
[Galaxy S 4 i9500 Original Android Development] a0007:
when flashed kernel from recovery was sound gone but when flash it from odin sound back :confused:
[Galaxy S 4 i9500 Original Android Development] yahyoh:
:confused::confused:

Andrei what do u think ??

BTW its not mine :p
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
^ Bullshít applications. While it's wishful thinking they might have IKS fixed, it's not possible to have a) three frequency planes b) two frequency planes beyond or below the cluster frequency barrier (900 & 1200).
[Galaxy S 4 i9500 Original Android Development] razer1224:
i have a doubt

stock kernels are running in IKCS rite?
[Galaxy S 4 i9500 Original Android Development] dragon135:
Dear AndreiLux,

So will it be possible to implement core migration instead of cluster migration?

I hope it is not HW limitation.

Sent from my GT-I9300
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
I don't know at this point; we won't have an answer for that for another 2 or 3 months.
[Galaxy S 4 i9500 Original Android Development] razer1224:
Calm Down, and Take Some Time to Think Mate :)
[Galaxy S 4 i9500 Original Android Development] wanam:
I can't reproduce the sound bug too, but it was reported by some users on my kernel as well, and it's built from official Sammy sources (update1) with no sound changes!
[Galaxy S 4 i9500 Original Android Development] yahyoh:
O_o

sorry for LOW quality pics :/

edit : the phone running MDK firmware BTW
[Galaxy S 4 i9500 Original Android Development] Socotroco:
AndreiLux,

I installed your kernel, working fine for the last 2 days(no freeze, no app FC). I'm wondering if this is the same kernel as the Samsung stock but tweaked? I'm asking this because I have no idea how you build it, I would like to know and because I also noticed some minor lag when scrolling ni apps like Twitter and FB, something that wasn't happening with the stock kernel, I hope it's just because of the alpha version and later versions will not have this minor glitch.

So far, for the last 2 days that I've been using it the battery life has been great, I got 3h45m screen on time and went to bed & plug it with 30% still remaining (this is a big improvement over my almost 2yr old SGSII with CM10.1).

Keep it going, your project is great !!! Good work!!!

Regards.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
All of this is pointless, there are no apps who can reliably read out the clocks in synchronicity, they're all reading them in sequence so one core is read out at a different time than the others. The second screenshot is physically not possible, just as all the reports of the S3 or N2 running any kind of asynchronous clocks.

If IKS will ever appear again then max_eagle_count control will come with it in the sysfs.
[Galaxy S 4 i9500 Original Android Development] jinosong:
Sorry if this has been posted before, but I came across an article that features AndreiLux and his thoughts on the Octa processor. Pretty neat. :victory:

Samsung's Exynos 5 Octa Functions as a Quad-Core Processor, Says Developer
[Galaxy S 4 i9500 Original Android Development] adyscorpius:
http://wccftech.com/galaxy-s4-i9500-exynos-octa-core-running-sub-optimal-firmware/

I had made a similar post on the implementation of IKS. What it really means is that the CPU was never 8 cores running together, and never would be atleast in the Big.LITTLE implementation. What [MENTION=4167023]AndreiLux[/MENTION] meant was that even in the two sets of CPUs, they switch cluster wise between each other and not core wise...
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
I'm aware of this one, it'll be fixed. The su process times out when the app lies in the background. It also only happens if the app is killed out of memory.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
I pushed a new APK to the play-store which should fix all known crashes and speed up the loading time. I'm aware of the rotation bug.
[Galaxy S 4 i9500 Original Android Development] djoevan:
May be just a stupid question of me, but i felt when i open the camera it have delay sometimes but sometimes don't. Is it only me or any other feel the same as me?

Means that it takes a several seconds to open the cam, but after that it fast to open it again. But after long not open and want to open again it has the same problem.

And i got a problem delayed too in path camera.

Is it only me, or any others feel the same?

I use wanam 2.0 with perseus kernel 10

Sent from my GT-I9500
[Galaxy S 4 i9500 Original Android Development] matheus_sc:
I test coming from adam kernel, but battery drain more fast, need full wipe to work corret?
[Galaxy S 4 i9500 Original Android Development] fierce_brake:
Hav you checked with BBS what process is consuming the battery ?
[Galaxy S 4 i9500 Original Android Development] matheus_sc:
Same Apps are install, but with perseus drain more, only change kernel return normal, full wipe can help?

New version is work with cm 10.2?
[Galaxy S 4 i9500 Original Android Development] fierce_brake:
wipe on dalvik/cache before and after installing the kernel might help you avoid issues.

I would still consider using BBS to track what is draining your battery.

If you feel confident doing a full wipe, my bet is it will do the trick...
[Galaxy S 4 i9500 Original Android Development] venorme:
Is this possible to implement slide to wake (or double tap to wake) feature into kernel?

Its really handy one on my nexus
[Galaxy S 4 i9500 Original Android Development] Crash:
Thanks [MENTION=4167023]AndreiLux[/MENTION]

Just a small question ...

How did you guys Restore defaults with Synapse ? simple clear app cache ? or?

Have some of my users in Spain forum asking about it

Hugs
[Galaxy S 4 i9500 Original Android Development] Cleverfish:
every settings had it's default value. just pull the sliders to default (D)

Sent from my GT-I9500
[Galaxy S 4 i9500 Original Android Development] Crash:
ok thanks i will install and check to let my users now with some screenshots

Edit. Now i see how to default but i guess is a good idea to have an option like stweaks a general restore to default instead of going individual just an idea ..

if the user have a lot of config going default 1 by 1 is complicate

Hugs
[Galaxy S 4 i9500 Original Android Development] clavicle:
Will synapse programme work with earlier data/.persus/ folder and settings, I seem to be getting fc with synapse while restoring earlier u/c settings?

Btw, no great issues with latest kernel pre3, thanks.
[Galaxy S 4 i9500 Original Android Development] farid993:
My cpu freq can not get lower freqs than 1200. If i set min freq any value lower than 1200 it did not work but if i set it higher than it is work. Cpu freq stuck at 1200 and higher all of time.

pre3 and synapse 0.5
[Galaxy S 4 i9500 Original Android Development] lukair1983:
I'm feeling like discoviring a whole new universe with Andrei's kernel (undervolting, overclocking, audio settings and so on). Amazing, simply amazing.

I did a lot of reading today mainly on XDA, I put around 5-6 hous, and I learned a lot, but I would appriciate if someone correct me on my understanding (if it's wrong), and answer just a couple questions.

1) Overvolting - Making the frequency more stable (till some threashold), but also making the battery drain more power, and also making the phone warmer

Undervolting - Making the battery drain less power, making the phone colder, but also till some threshold (where the phone becomes unstable); In case the stable undervoltage found, the core for this frequency will work exactly the same as in the case of default voltage (no change in work speed of the core)

2) As I understand the A7 frequencies we have to divide by 2 in Synapse, per the way Samsung implemented their stuff. From what I found (Andrei post), the samsung standard range for the frequencies is 800MHz-1.6GHz for A15 and 250MHz-600MHz for A7. The reason there are more options in Synapse is due to Andrei kernel and unlocking those options (so overclocking from 1.6 to 2.0 covers the added range for A15's, and pushing the minimum frequency to 100MHz pushes that range of 100-200MHz for A7's. So far so good? ;)

Now to the 2 of my questions:

3) I understand now how to test the CPU Stability. Simply set the max frequency in Synapse to the one I want to test, and run a stress test(s) for some number of minutes (like 10-20), and if there are no errors or freezes, or reboots, it means the voltage is (most likely) good enough.

But what about the GPU Test? Do I have to run a GPU benchmark like say Nenamark and stare at the screen in order to find artifacts? Or maybe there is some easier way, more deterministic aside depending on my eyesight? :P

4) I see some people underclocking the max frequency of A15 to 1.2 GHz (for example), but overclock the max frequency for A7 to (I see a general rule, as many say 750MHz is unstable) 700MHz from 600MHz. My problem with understanding this, is that underclocking obviously is going to help with the battery drain, but when I see "overclocking" I instantly think (bigger battery drain). How overclocking (in this mix) comes into the overal picture? Is it also (by some way) helping with the battery drain in the long run?

5) How I can test the half-frequencies. Say, I want to test 100MHz frequency, I can set that as my max, and run stress test. But the next step is 200MHz in the max frequency slider, so how can I set the 150MHz frequency for the A7 core?

I have couple more questions, but I don't want to throw everything in order to keep it relatively short.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
That's problematic since we have a value range with 100MHz steps over 750 and 50MHz steps on the lower range.

It will have to wait until I implement a new type of slider with pre-fed values instead of calculated ones, until then use another generic app.

As for GPU, it will begin to stutter and hickup when unstable. I recommend 3DMark for testing.

Keep in mind that with Synapse I also display the A7 frequencies as their real frequencies, besides the min/max policy because of the above mentioned issue.
[Galaxy S 4 i9500 Original Android Development] droidphile:
Just a heads up to everyone. After updating Synapse from playstore to get today's version, press menu button to find two options: Reset section (per tab reset) and Reset Globally. Two very very useful feature in case you want to start setting up from the scratch or just want to reset only one tab which you messed up.
[Galaxy S 4 i9500 Original Android Development] Crash:
[MENTION=4167023]AndreiLux[/MENTION]

Thanks for update the app with reseat defaults

hugs
[Galaxy S 4 i9500 Original Android Development] farid993:
Ok i disabled wanam xposed and it is ok now. But it is Wanam Xposed problem and i should tell him or it is kernel/synapse problem?
[Galaxy S 4 i9500 Original Android Development] HannibaL_kk:
disable boost mode in wanam xposed and thats it!
[Galaxy S 4 i9500 Original Android Development] Anakha56:
So this is more than likely a issue with me being on a older release than a problem with the kernel but I thought I would ask anyway...

My camera no longer launches with the new kernel. ROM Build is MDK (one released for my country) and the error I get is "Warning. Camera failed." any ideas? Pretty sure I need to download and flash a updated ROM & modem oh and I flashed the kernel through Odin if that would make a difference.
[Galaxy S 4 i9500 Original Android Development] bobdoblo:
There is a camera fix on the download page that might work? https://www.dropbox.com/sh/l9iwbpelw3fz1d6/lwwcWk8UHO

Sent from my GT-I9500
[Galaxy S 4 i9500 Original Android Development] Anakha56:
Thanks but I flashed to Wanam's last build (had it downloaded already) and installed kernel and all seems good now :). So to answer my question, it was being on a older ROM :).