yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9500 Original Android Development] hypergamer1231:
exactly the same issue as i have and have given up moving back to stock kernel.......also the changed settings are gone after a reboot.....i am on omega 14.1:(
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
I can't help with such issues if you can't go through the effort of posting the error log.

I updated Synapse;

0.7:

- Proper handling of UCI non-support

- Improved start-time and speed

- Fixed race-condition in shell dispatcher causing command failures

The last point may fix some crashes people had.
[Galaxy S 4 i9500 Original Android Development] AladdinZ:
Sorry Andrei I'll learn how to take a log and post next time. I don't wanna bother you by asking how to do it ;) until then I'm on alpha9 with STweaks.
[Galaxy S 4 i9500 Original Android Development] Cleverfish:
download catlog at play store. with it you can search for error in logcat, record your log and many more. so easy to use :)

Sent from my GT-I9500
[Galaxy S 4 i9500 Original Android Development] mw86:
Running great on Alpha10.4 with Synapse 0.8 release. Everything is running great so far. App opens right up and all opening issues solved in last version 0.7. You have put together the app very well Andrei.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
0.8 introduced a boot crash detection. I decided for now to forego individual boot flags for different things and just have a single global one. Every time you change a setting it'll give you a 20 second grace period, if you phone didn't die in that period then the boot flag is set. At boot it sets the settings as usual, and after a 120 second grace period if it didn't crash, it'll keep the boot flag deactivated and the next boot will remain clean.

The last known problem in terms of stability I know of is that when you leave the app open for too long (Or gets kicked out of memory), it'll crash when resuming it. I'll look into that.
[Galaxy S 4 i9500 Original Android Development] Alberto96:
For [MENTION=4167023]AndreiLux[/MENTION] : I have just a request for future kernel versions. USB Fast Charge. Also changing mA in Synapse app for USB ports phone still charges slow like with stock roms. I had USB Fast Charge on my old Galaxy S 1 and it was working great.

Thanks a lot :)
[Galaxy S 4 i9500 Original Android Development] mw86:
Great I've noticed it is nearly stable for a full release. Excellent work! Sounds good.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
There is no such thing as USB fast charge. If you want unstable power detection removed then I'll look into that.
[Galaxy S 4 i9500 Original Android Development] Alberto96:
Maybe add an option to enable/disable it. Seems to work really bad :(
[Galaxy S 4 i9500 Original Android Development] lukair1983:
Hey Andrei. God one question (I'm on latest kernel, and latest Synapse).

While testing the stability of CPU with StabilityTest, the frequencies get altered without a freeze or restart of the phone. What happens is for example I set the phone to 1.4 GHz max/min cpu frequency, I run StabilityTest, I come back half an hour later to see the StabilityTest now shows the max frequency is 1000MHz. I open the Synapse, and I see the sliders that are pushed back to 1000 MHz.

Now, it happens even after just 2 minutes of StabilityTest. I didn't notice it before. Would you mind telling me what is happening here? I guess I must have missed some failsafes.
[Galaxy S 4 i9500 Original Android Development] mw86:
If you set min and max to 1.4ghz thats possibly why. It might have hit secondary throttle temp that drops it further down from 1.4 ie like 1200(a15)/1000/800/600(a7). In this scenario if min is set to max it cant reset to higher mhz the way the throttle works and therefore stays at the lowest throttle mhz it needed to go to to stay under the secondary throttle temp. To test if you did test like that leave min mhz at a normal range.
[Galaxy S 4 i9500 Original Android Development] lukair1983:
Thanks a lot mw86. I will do that and report back, to confirm what you said.
[Galaxy S 4 i9500 Original Android Development] kirabyte:
V11 is here!!

-Sorry for my bad english.
[Galaxy S 4 i9500 Original Android Development] lukair1983:
Affermetive sir!

Thanks a lot for the tip.

...

I have a technical question to anyone who specializes in this field. I've read some people saying that it's better if you charge the battery using USB port vs wall outlet, because the current is lower (500 mA vs 2 Amps) and if the battery will be charged slower, it will discharge slower (the main argument is it will discharge slower, not how much slower it will discharge, so if it's just 0.1% slower, they are still correct as weird as it sounds).

Seems kinda weird and strange to me, but hey, what do I know. So I thought to ask people who know their stuff. Is this true, and do these reports have any science behind them?
[Galaxy S 4 i9500 Original Android Development] Technecium:
if you heat up soup on a stove vs in a microwave, will one be eaten more slowly?

seems like nonsense to me.
[Galaxy S 4 i9500 Original Android Development] jujuburi:
Not seems, it's a fact, I've heard that nonsense before though.
[Galaxy S 4 i9500 Original Android Development] cmd512:
Current version will boot up at times with all default values even when there wasn't a crash, so I'm assuming it's the "kicked out of memory" bug you've mentioned. When opening up Synapse, I can see everything's on default, but the sliders still show the "ghost" of my custom values. Sounds like the way to get things back to my device's custom setting is just to wait the full 120s and the reboot?
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
The memory crash should have nothing to do with the boot settings. You either just rebooted too fast within the 120s or you changed a setting and quit the app earlier than the 20s. I might just remove that last delay since it doesn't make much practical sense.

You can just hit cancel to revert to the "ghosted" saved settings.
[Galaxy S 4 i9500 Original Android Development] bala_gamer:
audio is lost when a headphone is plugged in, but this happens randomly. Only a full restart give back the audio, im using alpha 11
[Galaxy S 4 i9500 Original Android Development] kirabyte:
hi, anyone could share your best QoS settings?

Thx

-Sorry for my bad english.
[Galaxy S 4 i9500 Original Android Development] sorg:
I'm not sure if it possible to check from application, but if yes, then you can check if Device has been booted in "Safe mode" and disable tweaks if so. In this case you don't need to make any tricks to detect hangs.

Safe mode can be activated by holding Volume Down button while you see startup animation. Hold it till lock screen appear. And then u will see "Safe mode" watermark on the left bottom corner of screen.
[Galaxy S 4 i9500 Original Android Development] HassanM:
Happened to me as well... According to Andrei its concerning some issue with Custom Kernals which still needs to be pinpointed....
[Galaxy S 4 i9500 Original Android Development] hathara:
Zram and zswap

andrei lux any news on zram and zswap ?

and thanks for your kernel in version 11 my phone is incredyble fast!!!!! love this qos services!!
[Galaxy S 4 i9500 Original Android Development] hotheabilly:
Whoa good feature of QoS in v11, it feels like my phone faster than iphuck now yay!

Sent from my iPotato
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
I hope you guys enjoy the placebo as long as it lasts.
[Galaxy S 4 i9500 Original Android Development] NBruderman:
Sarcasem Win
[Galaxy S 4 i9500 Original Android Development] hotheabilly:
Wut? Really a placebo? I think boosting up frequencies at first touching the touchscreen isnt placebo at all -.- but then whyyyyy you made that QoS option, Sir? Just asking out of my curiousity.

Sent from my iPotato
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
My point is that those things exist on the stock kernel, I didn't do anything at all in the last version other than making them configurable and exposing them.

You claiming it's smoother = placebo.
[Galaxy S 4 i9500 Original Android Development] cmd512:
Hah, I was wondering how QoS would affect speed after seeing those posts...
[Galaxy S 4 i9500 Original Android Development] mw86:
Honestly its pretty smooth with most of it off even :) So it has it's effects but they don't make it a new device :)
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
That last Synapse crash is fixed in 0.9.
[Galaxy S 4 i9500 Original Android Development] matheus_sc:
Maybe is placebo, but for me is more smooth too, only wakelocks is my concern now.
[Galaxy S 4 i9500 Original Android Development] Alberto96:
It's true. Also for me is a bit smoother (not so much) and this isnt a placebo :)
[Galaxy S 4 i9500 Original Android Development] onukomer:
Hi! who can share the best synapse config?
[Galaxy S 4 i9500 Original Android Development] mw86:
Well depends on user I guess. See Default touch boost on old Perseus kernel was and is 400(800mhz) a7 and it will not feel smoother unless you choose higher values. Vs stock kernel now you can even set it to higher than 600(1200mhz) a7 so if you overclock a7 and set this to that value or increased minimum ram or internal bus speed for those it will feel smoother. Overall it's a small boost over the stock setup of a stock kernel. Just the same though to save energy we can also lower some of these if they use resources that may not be needed at all times. The internal bus, ram and cpu will still scale based on corresponding workloads with the boosters disabled or lowered.

This is what makes Andrei's kernel so great. He gives us the options to make it our own. Keep in mind guys if you type all day and you set touch boost really high you are shooting yourself in the foot, as it may be boosting well beyond what is needed to sufficiently render or complete the workload of these simple typing actions or selecting items on screen. Therefore wasting energy even at the highly efficient power draw of a7 constant jumps to max a7 or near will still bring potential battery life down.

---------- Post added at 10:44 AM ---------- Previous post was at 10:41 AM ----------

Best is relative to opinion. Your better off describing a usage pattern and asking what options may aid in that type of setup :)
[Galaxy S 4 i9500 Original Android Development] fierce_brake:
Hello there mates !

has anyone had any issues installing the latest perseus kernel on Omega 14.1 ?

I tried last night, but right after installing everything, in the first time configuration screen, my touch screen was unresponsive (had to force shutdown); i re-installed the rom with perseus 9 and it worked as usual.... any has experienced the same issue ??
[Galaxy S 4 i9500 Original Android Development] Vurda:
I can suggest you to try exDialler or else because default dialer is a pain. This will solve some of your problems
[Galaxy S 4 i9500 Original Android Development] tabish84:
Synspse forse closes
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
My opinion is you should move this discussion out of this thread.

A bit more descriptive please? Seriously, what do you guys expect from such posts?
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
I won't repeat myself. Now stop please posting here and move your concerns out of the thread into the general forum.
[Galaxy S 4 i9500 Original Android Development] cooldoc007:
hi andrei.. after all the dust settles in this synapse development, will u please consider developing for note3 N900.. missing ur kernel since i left my S3.. jus a wish... do consider.. pleaseeeee.....:fingers-crossed:
[Galaxy S 4 i9500 Original Android Development] gdonanthony:
give him note3 he will develop something for it :)

regards
[Galaxy S 4 i9500 Original Android Development] jaidev.s:
hhow to fix screen smearing using synapse?

i tired to fix screen smearing by increasing GreyScale addend value to 1.95% white but i still have smearing. how can i fix this? should i tweak some other values?>
[Galaxy S 4 i9500 Original Android Development] gp545:
Enable Master Sequence and Register Hook. Smearing will be gone then.
[Galaxy S 4 i9500 Original Android Development] dragon135:
Enabling master sequence is not related with fixing smearing.

Just enable register hook and smearing slider

Sent from my GT-I9500
[Galaxy S 4 i9500 Original Android Development] acerdroid:
Can anyone tell me how this kernel runs with omega 14.1. Does it make things snappier and how is the temperature of the device mine currently is getting a bit hot by the speaker area.
[Galaxy S 4 i9500 Original Android Development] HassanM:
Runs amazing... No temp issues whatsoever
[Galaxy S 4 i9500 Original Android Development] gio_b:


Try lidroid kernel.

Gio.
[Galaxy S 4 i9500 Original Android Development] bala_gamer:
Can you people check the minimum clock speed? Looks like mine is always running @ 1.2 ghz for minimum clock
[Galaxy S 4 i9500 Original Android Development] alandd86:
no sound after flashing this kernel !! any1 knows why plz ?
[Galaxy S 4 i9500 Original Android Development] HassanM:
Switch off your phone and switch it on again after couple of seconds.... Hopefully u should have the sound back....

Good luck!
[Galaxy S 4 i9500 Original Android Development] alandd86:
i did that and wiped cacth and dalvic reflashed kernel,, still the same !!
[Galaxy S 4 i9500 Original Android Development] HassanM:
Which Rom r u using??? Other than that, any framework (3minit, Xposed etc)???
[Galaxy S 4 i9500 Original Android Development] alandd86:
just omega 14.1 with no framework
[Galaxy S 4 i9500 Original Android Development] HassanM:
Try reflashing the Perseus again.... Grant root access to Synapse ... Switch off your phone... Try do a battery pull... Put it back it and boot it up... Make sure after the boot u see a small message popping up on your home screen showing "Synapse Booted..."

Now try the sounds under the settings/my device/sounds...

Hopefully it should work...

Good luck!
[Galaxy S 4 i9500 Original Android Development] alandd86:
thanks solved issue,, i think the problem was synapse cz i did deny root access !! BTW what is synapse ?
[Galaxy S 4 i9500 Original Android Development] HassanM:
Glad to hear that... As for Synapse, its a Kernal tweaking Utility...
[Galaxy S 4 i9500 Original Android Development] sak500:
If you're using wannam xposed module maybe you have checked CPU boost. That's what i had done and this always screen on 1200mz was driving me crazy until one day i just remembered this setting.
[Galaxy S 4 i9500 Original Android Development] bala_gamer:
bang on target, i tested it few days back and forgot to turn that off :)
[Galaxy S 4 i9500 Original Android Development] Grarak:
Lastest kernel is working on AOSP ^^
[Galaxy S 4 i9500 Original Android Development] gdonanthony:
with no problem ? :)
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
I didn't do anything on the kernel side. If the touchscreen works now, then good, I guess.
[Galaxy S 4 i9500 Original Android Development] hazri1974:
Why my pc cannot connect my phone wifi tether when using this kernel, but in stock kernel it can?...tq
[Galaxy S 4 i9500 Original Android Development] Anakha56:
[MENTION=4167023]AndreiLux[/MENTION] what are your thoughts about Battery Life Extender/BLX?

http://xdaforums.com/showthread.php?t=1257497
[Galaxy S 4 i9500 Original Android Development] Grarak:
On first boot touchscreen is working after lock and unlock touchscreen stops working.
[Galaxy S 4 i9500 Original Android Development] gdonanthony:
maybe the touch bug before is reverse when using in CM ?

[1st boot touch doesnt work and after lock and unlock touch will work]
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Irrelevant.

That's a different behaviour than a few weeks ago, I didn't had access to the touchscreen at all at boot.
[Galaxy S 4 i9500 Original Android Development] iamsachin:
I think we might need to alter some permission in init rc
[Galaxy S 4 i9500 Original Android Development] jujuburi:
Don't know if it's related to kernel (guess is yes because never noticed this with stock) but when I connect the phone to my desktop via USB it takes two try each time to establish a successful connection! First time the 'connected as a media device' notification does appear in the notification panel but nothing on PC.
[Galaxy S 4 i9500 Original Android Development] Alberto96:
[MENTION=4167023]AndreiLux[/MENTION] : is screen undervolting possible on our board?
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
There's a voltage slider in the notification area with a sun next to it.
[Galaxy S 4 i9500 Original Android Development] Alberto96:
So via software isnt possible?
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
The brightness slider is a direct voltage control of the display AMOLEDs.
[Galaxy S 4 i9500 Original Android Development] Alberto96:
Oh, my fail :eek: For Galaxy S 1 is a bit different :/
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
I really doubt it's different.
[Galaxy S 4 i9500 Original Android Development] Alberto96:
Check my kernel sources. On Galaxy S 1 we have "mV" values that can be changed without any problem, like other type of screens. On Galaxy S 4 sources i haven't found any "mV" values about screen. This is why i asked u
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
LDO28 is the panel voltage regulator here, and there's no point in changing that value because you're undervolting the controller feed. The controller will simply suck more current to drive the AMOLEDs at their configured PWM cycle and voltage.
[Galaxy S 4 i9500 Original Android Development] Alberto96:
Thanks for your detailed explanation.
[Galaxy S 4 i9500 Original Android Development] HassanM:
Hi friends. ..

Im on Omega 14.1/Perseus 11...

Ive been noticing after a reboot the Synapse Values go back to default... Moreover when I try modifying QoS values my phones hangs and reboots... Kinda strange...

Can anyone plz shed some light on it... Am I doing anything wrong here???

Thanks in advance
[Galaxy S 4 i9500 Original Android Development] zenosteam:
Same issue here losing my saved setting after reboot

Envoyé depuis mon GT-I9500 avec Tapatalk 4
[Galaxy S 4 i9500 Original Android Development] mw86:
I helped Hassan with the setup and its working for him now. Make sure anything from stweaks is erased. Check system/app folder and data/ folder for hidden folder .perseus after he removed that it was working for him. I think also the issue he had on qos is he was setting the a7 max in qos higher than his a7 max in cpu section. I wasn't sure on that for him exactly and he has retired for the night. But it worked on boot for him after that recommendation.
[Galaxy S 4 i9500 Original Android Development] zenosteam:
Will do this thanks a lot

Envoyé depuis mon GT-I9500 avec Tapatalk 4
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
STweaks is neutered, the app and data folder don't do anything on >=10.
[Galaxy S 4 i9500 Original Android Development] HassanM:
Thanks bro....
[Galaxy S 4 i9500 Original Android Development] lukair1983:
Andrei, thanks a lot for adding to the newest perseus:

That theoriticaly could be a life saver for mine (and others probably too) mhl charging problem. But before I will try and actually use it on a constant basis, would you mind asking you 2 things from technical nature about it?

Please bear in mind, I'm no electrician, so if I make some blunder, please be easy on me.

1. "This will fix charging problems people have been reporting, as long as the charging source indeed is able to provide the given currents."

What if it isn't? Say I set the max current limit to 2000 mA, and the charging source can provide only a 1500 mA current? Does it simply mean, the phone will TRY to drain up to 2000 mA current, and if the charging source cannot provide it, it will drain as much current as the charging source will provide (1500 mA in this case)? If that's the case, can there be some pottential damage (speaking from electrical point of view) to either the phone (battery / usb port), or the charger, or the port the charger is plugged into (wall outlet / usb port in PC) ? The phone indeed will be looking to take 2000 mA current, the source will only be able to provide up to 1500 mA, and because of that it could lead to some unexpacted behaviour (some strain on the charger that is enforced from the phone that is requesting 2000 mA current) ?

2. "Use at the risk of frying your charger/charging port."

Would you be able to say specificaly, what would be the conditions, that COULD (I know it's not a 0-1 issue) pottentialy make any damages? Ofcourse I understand that if we set the limit over 2000 mA (that is the current phone drains when connected to the wall charger, so I guess that's the safe max limit), like to for instance 4000 mA, that will apply here, but are there any other conditions that would also imply that? Say if we set for example 1000 mA as the current limit, and we plug to the phone the wall charger (that is able to provide 2000 mA)?

Basicaly what I would try to achieve here, is set the max current to a range somewhere from 1500 mA - 2000 mA, and thanks to that I would like to bypass the mhl 2.0 adapter limitation, which in itself is charged from the wall charger (2000 mA), but the adapter itself is being recognised by the phone as USB charger, hence the phone is draining only 500 mA current. So if I would set through synapse a limit to this 1500 mA - 2000 mA, that would in effect make the phone draining more current while connected via the mhl adapter.

I would appriciate some info if the above solution is safe (in theory).

Sorry in advance if those are really a very simple questions.

Seemed to me as well, but thought I ask you guys who know more about it that me, to just confirm what my senses told me. So thanks for that.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
MHL has its own current values which bypass the exposed settings and they're not changeable.

Cheap chargers can break if you suck more current than they're rated for.
[Galaxy S 4 i9500 Original Android Development] lukair1983:
Thanks Andrei for a response.

So how does that translate into my/our situation?

You're saying, that even if I bypass the charging protection through synapse, and set the limit to say 2000 mA, the phone will still drain only 500 mA from the mhl 2.0 adapter? Do I understand you correctly?
[Galaxy S 4 i9500 Original Android Development] ice.modding:
I have an incredible battery drain with this kernel, I definitely prefer to stay with the adam kernel. :/
[Galaxy S 4 i9500 Original Android Development] HassanM:
Absolutely no issues with battery at my end... Actually doing very well.....
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
It depends on your adapter, but yes. https://github.com/AndreiLux/Perseu...ach-exynos/board-universal5410-battery.c#L240

Thank you for sharing your thoughts with us, goodbye.
[Galaxy S 4 i9500 Original Android Development] astoncheah:
hi Andrei,

been using latest Perseus alpha11 for few days with Omega 14.1, encountered few times that the screen hanged more that 10 seconds, then back to normal, but some times it rebooted it self after the hang. here is the latest log, i took it after it rebooted it self. no uv/oc, all settings are in default exception the screen and sound mod.

the camera opening delay seems disappeared.

hope that helps.
[Galaxy S 4 i9500 Original Android Development] gp545:
Have you set Saturation weight to maximum? Once I had set it to max for a day just for curiosity and faced this kind of screen hang with black and green color grids for few seconds and Reboot. I set it back to default and have no issues afterwards. :)