yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9500 Original Android Development] Xphoid:
Feels awesome to be able to on Perseus again...

Thanks Andrei...
[Galaxy S 4 i9500 Original Android Development] Rahulrulez:
Alpha14 is one heck amazing kernel. Memory utilization is reduced by almost 20-25% which is simply amazing. Stock ROM + Persues is the best thing right now..
[Galaxy S 4 i9500 Original Android Development] MrGamerUser:
Thanks Andrei :victory:
[Galaxy S 4 i9500 Original Android Development] rebel1735:
Just flashed the update... its amazing :)
[Galaxy S 4 i9500 Original Android Development] mashaal95:
Crazy Update!!

Thank you so much Andrei! Just one problem though :(

The MTP Connection still doesnt work on AOSP :(
[Galaxy S 4 i9500 Original Android Development] jaidev.s:
Hope Andrei will add save and restore profile functions in Synapse soon.
[Galaxy S 4 i9500 Original Android Development] pierrep56:
Thanks Andrei !! I have just flash it with enthousiasm.... Great to be on Perseus and CM
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
I thought it worked? I'll look into it in the future.

I'll continue on Synapse after I update the S3 and N2.

And by the way, this is just a rant about the whole 4.2.2 to 4.3 upgrade shenanigans:

I have absolutely no idea why people / other devs recommended pit file flashing/CWM updating/full wiping/stock ROM through ODIN flashing. I trusted that there were indeed some issues arising from not doing all of that, but I just reverted to my 4.2.2 backup (I ran a bare-bone 4.3 for two weeks because I was too unmotivated to re-configure anything), cleaned cache and dalvik and just plainly installed a MJ8 zip on my outdated CWM (WHY does CWM have anything to do at all with 4.3????) without the slightest issue at all.

Learned that nonsense still continues to be posted here, and best is to just do things your way...
[Galaxy S 4 i9500 Original Android Development] Mr.Ghosh:
[MENTION=4167023]AndreiLux[/MENTION]: What's your opinion on this?

http://xdaforums.com/showthread.php?t=2500128 OR

https://code.google.com/p/android/issues/detail?id=59020
[Galaxy S 4 i9500 Original Android Development] Fishawy:
Excuse me .. Will Alpha14 work on 4.2.2 custom ROMs, or it's only for 4.3? Furthermore, if it's compatible & I flash it, will I notice the same memory consumption enhancement?
[Galaxy S 4 i9500 Original Android Development] AL_IRAQI:
Alpha 14 Only For 4.3 Roms :)
[Galaxy S 4 i9500 Original Android Development] kdh2834:
Alpha 14 is not compatible with 4.2.2.

Pls read the change log.. little reading will help u and our devs. If u want to use 4.2.2 u can continue using alpha 12.2
[Galaxy S 4 i9500 Original Android Development] skivnit:
I was about to flash with wiping adn everything and now i read this. as i'm in same boat as you, don't have a lot of patience for all the reconfiguration.

EDIT: i just did it wiyhout full wiping and all that stuff and device is up & running. Thanks Andrei once again. Don't have Knox anywhere though, was is disabled through the kernel?
[Galaxy S 4 i9500 Original Android Development] StoneRoses:
I know this is a bit off topic.

Which 4.3 rom do you guys recommend for using with latest Perseus?
[Galaxy S 4 i9500 Original Android Development] Xphoid:
Kernel removes it, if already not removed by your Rom Chef...
[Galaxy S 4 i9500 Original Android Development] jujuburi:
None.
[Galaxy S 4 i9500 Original Android Development] farid993:
I think they recommended pit flashing for people that have chines pit (11GB) because 4.3 did not boot on that pit.
[Galaxy S 4 i9500 Original Android Development] Degrated Shadow:
Its recommended only for people that have 11gb pit or 9.12 gb feom ota update. For non debloated roms 8.94 gb one is recommended
[Galaxy S 4 i9500 Original Android Development] mw86:
The way I installed it worked for me fine, I am on the old chinese 11gb pitfile which I installed after 4.3. I wiped all before. Installed pit then installed rom with modem and the rest included and restored my 4.3 Nandroid. Booted right up and been working great since. I wrote what I did in the expanded storage thread. Im on TW 4.3 not AOSP if that makes a difference I doubt it.

Excellent work on the kernel Andrei. The time you have devoted is clear when you load up your kernels and this nee update is no exception.

4.3, 11gb+ internal storage and Andrei's kernel... couldn't ask for more if I tried.. phenomenal combo

---------- Post added at 12:38 PM ---------- Previous post was at 12:36 PM ----------

Xphoid is a debloated TW rom keeps most Sammy apps and functions.
[Galaxy S 4 i9500 Original Android Development] Degrated Shadow:
I was talking about non debloated roms. That range from 1.3 gb to 1.5 gb even sometime 1.2 gb.. anything below 1.1 works just fine.. I am using crash.. and its good enough
[Galaxy S 4 i9500 Original Android Development] REVERSiN:
Not entirely it preferable I had issues with my asphalt Game as a start and I thought it's more like a compatibility thing turns out it's caused by Philz recovery seems it's mechanism of wiping is a little different than standard CWM any way I tried everything several of us had sound issues on Wanam's kernel and we had nothing to do with pit re partitioning it's as said before for the guys with the Chinese pit.

The sound issue was fixed after wiping, I can say the ROM runs better I don't get any weird messages or bad ram usage, everything works now and I am still on 6.0.4.4 version why? Cause everybody said after a little search that it's recommended to use the new version rather than the old.
[Galaxy S 4 i9500 Original Android Development] tabenf:
alpha14

Thanks for 14 [MENTION=346281]Andrei[/MENTION] Ram usage is now much less on odex rom thanks for your time and effort
[Galaxy S 4 i9500 Original Android Development] skivnit:
L2_hsic wakelock is draining my battery. How can i fix

Sent from my Perseus powered octa
[Galaxy S 4 i9500 Original Android Development] muhammadshais:
This is the best perseus I have used so far two thumbs up great job Andrei...... Such low ram consumption and rom feels super smooth now
[Galaxy S 4 i9500 Original Android Development] skivnit:
Which in turn is making android os the biggest drainer

Sent from my Perseus powered octa
[Galaxy S 4 i9500 Original Android Development] ktouy:
Great update!

Still having the same issues

-synapse change the values after reboots.

-yellow with black screen freeze randomly.

-also i've notice that im having lowest scores on benchs however the phones feels faster so doesnt matter.

Great kernel! By far the best i used.

Many Thanks Andrei for your support and time!

Sent from the past...
[Galaxy S 4 i9500 Original Android Development] mw86:
Try waiting 5minutes after setting synapse before rebooting and checking. If you reboot soon after it assumes what you set caused a crash/failed boot
[Galaxy S 4 i9500 Original Android Development] ktouy:
Yeah ive notice that but what im saying is while im using it, for example i notice that on benchs (with an app i dont remember the name, that shows what cores are in use Big. Or .Little) the gpu i put it on 640mhz for example and after the test is on 177mhz and and the cores that use are the littles. Understand what i mean? Its like the gpu its linked to the little cores or something like that or is there i dont know. But that happends to me in a lot of apps.

Sent from the past...
[Galaxy S 4 i9500 Original Android Development] mw86:
I had that on Raw 2 kernel I was thinking it was some of the basics Andrei may have been addressed in his full release. He mentioned working on Synapse after he can Take care of GS3 and Note 2 kernel. He does a few devices so it's expected from such a great Developer.

Perhaps this is part of the Synapse work mentioned for after he has time to update the other device kernels...

I seen it triggered at time perhaps of throttle or qos calls but I am not sure which or if at all those are related. It could be something basic in Synapse related to the move to 4.3 that would be addressed soon enough.

If it is something one of us can send a log of any sorts I would be glad to or I am sure any of us. Let's see what Andrei can say on the behavior.

It could cause some bad behavior dropping to a 177mhz max in some workload situations.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
That's not an issue of the kernel or synapse. Their cheating thingy is triggered and resets to the wrong frequency since the table is different from stock. I can't really do much about it. You can remove all permissions from /sys/devices/platform/pvrsrvkm.0/sgx_dvfs_max_lock to avoid it but then the control in Synapse won't work either as long as it stays like that. Also why benchmarks are crashing since Samsung is boosting then to 700MHz.
[Galaxy S 4 i9500 Original Android Development] mw86:
Typical Samsung, I could tell some major bull was going on this time around but this is even worse. I have not had it trigger to be honest Andrei on your new kernel. So would you say it might not trigger if no benches or ran and gpu is set to stock mhz? Or because the gpu table available is as full as it is over stock mhz the phenomenon is likely to reoccur regardless of mhz we set in Synapse? I will tinker with the permisson of that file perhaps I could set the file permission some time after boot once the gpu clock is set by synapse I guess. Since it would be reset at boot before synapse starts it would have permission to be changed by synapse then locked out.

Thanks Andrei, much appreciated info as always.

---------- Post added at 08:16 PM ---------- Previous post was at 08:08 PM ----------

What if Synapse at boot when it applies the gpu removes permission for it after? As well as a toggle of that in the gpu section of synapse. When toggled users choice in Synapse is locked until turned off. One could adjust as needed and retoggle the permission setting. The permission toggle could be read what it was set to in synapse and upon boot when applying settings if it was being used while booted applies the lock at boot after all synapse applied. I don't know if coding even allows for such a setup but that would be amazing Andrei if you could make that possible instead.

In any case thanks for the info how to lock the file down.

---------- Post added at 08:23 PM ---------- Previous post was at 08:16 PM ----------

Okay ill have to see if I can have this triggered again as I havent had this on the latest build. I tried the permission and I noticed in the least I need to keep read permission on that file or it seemed atleast I could no open Synapse otherwise so I guess just removing write permission is sufficient to lock the file. That I guess is an obvious one I should of known.
[Galaxy S 4 i9500 Original Android Development] ktouy:
Ok thanks for the comments, now i have a simple question, why it crash the OS ( yellow and black lines) if the frequency its supported by the device?

Something similar happend to me on an older device but when i put the min at 100mhz and when the phone reach that freq. It crash in the same ugly way... After a reaserch i saw that my older device crash when it jump from 100mhz to another above 800mhz, and then i fix the issue changing the parameters of the governor to step up 1 by 1.

But anyway i dont know much about it. So...

Thanks !

Sent from the past...
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Didn't really check but it triggers on the camera as well if they kept it as in 4.2.2, which is problematic.

I just renamed the sysfs node for the max lock, it got an added underscore. 14.1.
[Galaxy S 4 i9500 Original Android Development] clavicle:
Just installed 14.1, things seem to be perfect! Thanks.
[Galaxy S 4 i9500 Original Android Development] mw86:
Yes all fixed Andrei. I found Antutu X from Play store was able to trigger it as well. That app uses a different process name so it doesn't launch samsung boost :D interesting to compare boost ran in antutu normal edition and antutu x where samsung boost is never called...

The gpu max lock is no longer reset on heavy gpu workload on apps that do not trigger samsung boost. Antutu plain did not cause the gpu reset so I can think after samsung boost reset it didnt have the same effect as Antutu X. Just used bench since it was like a game or the camera workload.

The overclocked max gpu sticks to what was set and is unaffected by the same situation. I noticed actually when this happened it was no longer for example 640 in the max gpu lock and when the reset happened 0 was actually displayed yet I saw it was still scaling gpu. Nonetheless this solved it as that no longer happens.

Excellent work Andrei!! 14.1 is a gem, quite a masterpiece.
[Galaxy S 4 i9500 Original Android Development] Arjav23:
Is the l2_hsic wakelock persistent in v14.1 ?
[Galaxy S 4 i9500 Original Android Development] Rahulrulez:
Wakelock is constantly draining battery.. Android OS is using a lot.. Even on idle mode.. I am using Persues Alpha 14 with stock ROM. Did you fixed it in 14.1?
[Galaxy S 4 i9500 Original Android Development] skivnit:
So I'm not the only one with l2_hsic wakelock

Edit : flashed adam kernel, the wakelock is gone. Can you check into this?
[Galaxy S 4 i9500 Original Android Development] Rahulrulez:
Adam is not compatible with 4.3 I believe... This is the only 4.3 compatible kernel as of now.
[Galaxy S 4 i9500 Original Android Development] jujuburi:
Lol, Adam 3.0, 3.1, 3.2 and latest 3.3 all are made for 4.3! Very good kernel but I found the audio on the lower side, haven't checked 3.3 though, my opinion based on till 3.2.

www.wanamlite.com
[Galaxy S 4 i9500 Original Android Development] gp545:
Adam v3.1, v3.2 and v3.3 Kernel supports 4.3 stock firmware :)
[Galaxy S 4 i9500 Original Android Development] skivnit:
i wouldn't have said the wakelock is gone if it wasn't compatible
[Galaxy S 4 i9500 Original Android Development] Arjav23:
It is suprisingly fixed in the 12.2 version uploaded by [MENTION=4648515]AL_IRAQI[/MENTION]
[Galaxy S 4 i9500 Original Android Development] ktouy:
On 14.1 it seems to be fixed the issue with the gpu lock also it feels even smoother for me so, Andrei you're AWESOME! THANKS A LOT!

Sent from the past...
[Galaxy S 4 i9500 Original Android Development] mw86:
For the l2-hsic wake lock here is a good info about it. http://smartphone.usofttech.com/t17997.html
[Galaxy S 4 i9500 Original Android Development] skivnit:
Yes but that is unrelated since flashing another kernel solves the problem

Sent from my Perseus powered octa
[Galaxy S 4 i9500 Original Android Development] Arjav23:
Which kernel?
[Galaxy S 4 i9500 Original Android Development] taylorhmatos:
Adam kernel
[Galaxy S 4 i9500 Original Android Development] Spartan199:
No stweak support?
[Galaxy S 4 i9500 Original Android Development] taylorhmatos:
No, only synapse
[Galaxy S 4 i9500 Original Android Development] HassanM:
New version doesnt support STweaks.....

Synapse is the new interface which is more comprehensive and has more parameters to play with....
[Galaxy S 4 i9500 Original Android Development] ktouy:
Also synapse its developed by Andrei.... Thats the main reason...(i guess)

Sent from my GT-P3110
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
STweaks hasn't been really updated since it pretty much was released. Synapse solves some problems (start-up time, usability, problems in its design and how it works) and I want to update it further in the future.

I'm disappointed that no devs showed even the lightest bit of interest in it till now, but I plan to push it through (Also S3/N2) even if it's on my own.
[Galaxy S 4 i9500 Original Android Development] medoooooo:
Hi [MENTION=4167023]AndreiLux[/MENTION] any updates on usb bug its to annoying but i did find an app usb mass storage mounter but it needs to restart the device every time you want to use it and after many times it stops working
[Galaxy S 4 i9500 Original Android Development] tabenf:
What usb bug?
[Galaxy S 4 i9500 Original Android Development] medoooooo:
Cant connect your phone to your pc
[Galaxy S 4 i9500 Original Android Development] tabenf:
Oke was not aware I will test and report back

Edit: I cannot reproduce your issue im on perseus 14.1 what pc do u have and do you have all drivers. Also try a different usb cable as this is not a kernel bug!

PLEASE HIT THANX IF I HELPED
[Galaxy S 4 i9500 Original Android Development] mw86:
If I developed anything I wouldn't hesitate to use Synapse for the controls Andrei! :)
[Galaxy S 4 i9500 Original Android Development] Aijazji:
check your windows driver

Everything work Perfect :)
[Galaxy S 4 i9500 Original Android Development] NBruderman:
1. Go to phone and press *#9090#, set log to hsic

2. Go to phone and press *#0808#, set AP, MTP

Fixed it for me
[Galaxy S 4 i9500 Original Android Development] Grarak:
AFAIK all kernels devs have their own app or the users use trickster mod.

May they just cannot handle with json.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Now that's just stupid. If anything it's easier than the XML markup of STweaks. Plus I wrote an actual documentation to begin with.
[Galaxy S 4 i9500 Original Android Development] xdamami:
after flash kernel opening my stweaks there show me no kernel support Why_?
[Galaxy S 4 i9500 Original Android Development] medoooooo:
Persus is not supported by stweaks but its supported by synapse its like stwaks download from google store
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
I really don't want to deal with these things anymore...
[Galaxy S 4 i9500 Original Android Development] tabenf:
NOTICE

NB NB NB NB NB NB NB NB!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

PLEASE EVERYONE STweaks is not supported in Persues kernel anymore Please use Synapse downloadable from google play

Thank You
[Galaxy S 4 i9500 Original Android Development] Degrated Shadow:
Maybe just post in ypur op that stweaks is gone forever? And now you support only synapse
[Galaxy S 4 i9500 Original Android Development] alawadhi3000:
Shake your phone about ten times back and forth and it'll be supported.
[Galaxy S 4 i9500 Original Android Development] sorg:
I've tried Synapse on I9500. It looks good, but still has some UI flaws, like current values covered by finger while adjusting. So, you need to change value then remove finger to see what current value is and then repeat if not what you desired. Solution is to put current value above slider. I don't understand how current value under slider can be more convenient than if put it above.

But the main issue is database as storage! With STweaks, some times i can open profile an any text editor on PC and change some values or even delete obsolete options. With Synapse i cannot do this. I have to open Synapse or some DB editing tool.. Not convenient, and I don't see the reason of database storage over sharedpreferences settings.

Another issue is hard-coding of setting screens into Synapse code, which makes it not so universal. Yes, i can use old STweaks-style scripts, but the trend of hard-coding isn't just right, IMHO. With STweaks I can grab old scripts and create new one.

Another minor issue - i prefer some settings (like colors) applied before lock screen appear, not after.

While Synapse provides some better setting screens, it losts something "in the middle of road". If it's not used for Perseus kernel then it doesn't provide significant benefits over STweaks (yet). Thus for my own kernels i still prefer to use STweaks. If you would pull STweaks sources and continue to develop it, then I would share my patches as well. If/when i will switch to Synapse, sure i will contribute my patches if there will be ones.

---------- Post added at 04:28 PM ---------- Previous post was at 04:15 PM ----------

Weird... cannot make Perseus 14.1 work with I9500XXUEMJ8 ROM.

Just decided to move to Android 4.3 finally. Grabbed this ROM, deodexed, compiled Perseus kernel from sources as usual.. And it doesn't work. libsurfaceflinger.so crashes at boot. I even don't see the boot animation.

I've tried precompiled binary of Perseus 14.1 - the same problem...

Hmm.. going to download MJ5 ROM and test again.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
It doesn't matter. Nothing is stopping you from dragging your finger outside the slider touch area to move it, this is a basic core Android design cornerstone. And I added granularity buttons for fine-control.

Because of profiles. When application and global profiles will be integrated a database key-value store is much easier to handle than the alternate methods because it will be able to query it. I already demonstrate this on the on-boot appliance of setting where the boot service simply queries the "global" context and uses nothing else but the key and value to set the settings. It's extremely simple and effective.

For power-users like you; you're making a nonsensical argument. The same way you open a text editor you can simply just open an app like SQLite Debugger, and as I've mentioned, it makes a thousand times more sense for profiles.

I have no idea what you're talking about. There is no hard-coding at all? The whole interface is dynamic as dictated by the config which is external to the app itself.

That's just something you have to deal with to avoid boot-loops caused by other settings like voltages, no way around it.

I can't continue developing something which is not mine (Play store), it still ends up with as a separate entity, which is Synapse already is, so I don't see your point here. STweaks needs a complete re-write to fix the issue of the load-up times because it's a design problem in how the app works.

Running MJ8 without problems.
[Galaxy S 4 i9500 Original Android Development] zetlaw:
I think Synapse is way more comfortable than stweak was. i just think that you need to add to every line of voltage what was the orginal value. and the math between the orginal - new value = How much we reduced or added.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
The original values shows up any time you change a value that isn't committed. As for the delta you're suggesting, it's a bit too single-purpose to voltage, the sliders are programmed as a generic control. Deltas don't make sense everywhere, but I'll keep it in mind as an option.
[Galaxy S 4 i9500 Original Android Development] ll_r1d0_ll:
formatted SYSTEM and cache and wiped davlick cache and installedf wanam 3.2 and flashed persus 14.1 kernel..one complete battery cycle but still the battery is draining...it is not going to DEEP SLEEP..always on 100MHZ freq ...any solutions ?
[Galaxy S 4 i9500 Original Android Development] sorg:
In my android apps i just use this: mPrefs.getString(Profile+".MyVar", defaultValue). I don't know what can be easier.

I didn't tell i don't know how to edit. I've used different SQL editors on PC and Android. I've just told it's not as convenient as pressing F4 in Total Commander, edit what you need and close with auto-save. TotalCommander will automatically download before edit and upload after. Also i can copy paste as many lines at once as i like which is not straight-forward on SQL editors.

Anyway, i didn't tell i won't use Synapse. When i will think that i can handle settings with Synapse better than in STweaks, i will switch :)
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
And if you needs are vars from a profile you need to code around it. Same for add/delete. What's the point in emulating a DB structure with prefs if you can just the DB.

But please answer that thing about hard-coded settings since it bothers me.
[Galaxy S 4 i9500 Original Android Development] xdamami:
I can write my english is not good as I can. Both despise bi people do not know, not knowing is not a shame shame not learn Sory yung;) Working snypse Good
[Galaxy S 4 i9500 Original Android Development] sorg:
Color picker.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Color picker what? There is nothing hard-coded about it.