yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9500 Original Android Development] mw86:
Your very welcome I also greatly appreciate cool tool as you do. Glad to share info :D

Nice also very cool, thank you.

I guarantee these kernel provided temps will be more accurate then any other cpu temp app. :good: again thank you so much AndreiLux and sorry for the obtrusive sig pic :)

Team Kernelizers SPH-L710 KT747 * GT-I9500 Perseus
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
They are not the same / updated differently. Temp is the one which is used for throttling.
[Galaxy S 4 i9500 Original Android Development] Jeshter2000:
Panel 1 also here ....

Sent from my Octaaaa! GT-I9500
[Galaxy S 4 i9500 Original Android Development] gun@id:
My panel also "I"
[Galaxy S 4 i9500 Original Android Development] HassanM:
No problems here.... Try wiping cache and dalvic and reflash....

Hopefully it should work....
[Galaxy S 4 i9500 Original Android Development] mashaal95:
Still Doesn't work [MENTION=4818927]HassanM[/MENTION] :(
[Galaxy S 4 i9500 Original Android Development] HassanM:
Try reverting back to v12 and see if its ok???
[Galaxy S 4 i9500 Original Android Development] kdh2834:
I full wiped and flashed the rom and the kernel later still same problem...

Ill try reverting to v12..
[Galaxy S 4 i9500 Original Android Development] mashaal95:
[MENTION=4818927]HassanM[/MENTION] v12 works properly :)

Are you on Touchwiz? I think its not working for me because Im on AOSP!

---------- Post added at 02:28 PM ---------- Previous post was at 02:21 PM ----------

[/COLOR [MENTION=4818927]HassanM[/MENTION] v12 works properly :)

Are you on Touchwiz? I think its not working for me because Im on AOSP!
[Galaxy S 4 i9500 Original Android Development] mw86:
Hassan uses Omega rom so it is touchwiz yes
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
12.2 fixes boot issues and the touchscreen on first boot on AOSP ROMs.

Also [MENTION=4818927]HassanM[/MENTION] and others. If you want to help out, at least read people's issues properly.

Edit: Dropbox seems slow so be patient for the downloads.
[Galaxy S 4 i9500 Original Android Development] HassanM:
Got it mate.....
[Galaxy S 4 i9500 Original Android Development] kdh2834:
Thanks for the fast update Andrei :D

But.. Is there exfat support for AOSP ROMs..?

My 64 GB sdcard does not get mounted..

Any solution for this one?
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
That's a problem of the ROM.
[Galaxy S 4 i9500 Original Android Development] Degrated Shadow:
solution for synapse crashing on pening was on kernel side?

its working after flashing 12.2

fix was this:

/system/xbin/busybox mount -t rootfs -o remount,rw rootfs

And then put in

ln -s /res/synapse/uci /sbin/uci

i posted this earlier in runedrune's thread.

however the synapse was crashing again after rebooting phone
[Galaxy S 4 i9500 Original Android Development] HassanM:
Just flashed 12.2...

Running fine....
[Galaxy S 4 i9500 Original Android Development] cmd512:
Andrei, just flashed to 12.2 (even though I didn't need to). For both 12.1 and 12.2, Synapse is uninstalled after flashing and reboot. Is this normal behavior?

For reference, under recovery, I only flashed the CWM version and rebooted.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
I don't have any such behaviour. On the last page you said you hit cancel to revert your settings back. But if the app were un-installed that means that you couldn't revert settings back.
[Galaxy S 4 i9500 Original Android Development] cmd512:
Strange, I figured I was the only one as no one else has been reporting it, thanks. It was in fact uninstalled, I had to go to the Play Store, re-download & install it, run it, and all the previous settings were still there. Just had to hit the cancel button to revert everything back.

Puzzled... :eek:
[Galaxy S 4 i9500 Original Android Development] omvir:
Hello Andrei, I was thinking about flashing the 4.3 leak for our device and I was wondering if your kernel will function on the 4.3 leak? If not then I shall wait till it is functional on 4.3.
[Galaxy S 4 i9500 Original Android Development] robertobsc:
There's no 4.3 leak to our i9500, only for i9505.

Enviado de meu GT-I9500 usando o Tapatalk
[Galaxy S 4 i9500 Original Android Development] lukair1983:
@Up

http://xdaforums.com/showthread.php?t=2488155
[Galaxy S 4 i9500 Original Android Development] Degrated Shadow:
please repack the 4.3 stock kernel with selinux set to permissive permanently
[Galaxy S 4 i9500 Original Android Development] skivnit:
There's a leak and an official 4.3. Not gonna flash until Andrei releases a compatible kernel. Too used to Perseus
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Things don't work that way.
[Galaxy S 4 i9500 Original Android Development] Degrated Shadow:
Umm.. then how??

You will need kernel sources for doing that?
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
The policy enforcing is hardcoded into the kernel, yes.
[Galaxy S 4 i9500 Original Android Development] Degrated Shadow:
Alright..

However I freezed all knox apps in titanium backup and now evey app is getting su permissions perfectly.
[Galaxy S 4 i9500 Original Android Development] lukair1983:
Andrei, quick question. Is the new version of TW (4.3 update) requiring a different perseus kernel, or does the kernel work by default with any android released by Samsung on i9500?
[Galaxy S 4 i9500 Original Android Development] HassanM:
The current Kernal is based on 4.2.2... Supposedly it wont work on the 4.3 update until Andrei comes up with an update....

I hope he does.....
[Galaxy S 4 i9500 Original Android Development] Cleverfish:
err, can you list down what apps that are related to knox?

Sent from my GT-I9500
[Galaxy S 4 i9500 Original Android Development] Degrated Shadow:
Freeze everything that has knox in the name.

See the attached image. Although after freezing u will have to reboot to make su grant other apps access.
[Galaxy S 4 i9500 Original Android Development] astoncheah:
hi Andrei,

screen stuck/hanged just happened and rebooted it self after testing 12.2 for one day. here the latest log. let me know if i missed something.
[Galaxy S 4 i9500 Original Android Development] Choucko:
A bit of help

Hello,

I recently installed this kernel and it's really nice, especially the control app.

I think everything is great, but I need some help:

I know everyone's phone is different, but what is a decent average to set the Cpu,Gpu and QoS for a snappy phone that doesn't get too hot?

I could do this by myself but I'm worried that I'm gonna mess something up since i'm not the most knowledgable in this department :P

I must say,though, the sound quality has increased by leaps and bounds after tweaking it a bit

Regards,

Wiliam
[Galaxy S 4 i9500 Original Android Development] HassanM:
[MENTION=4167023]AndreiLux[/MENTION]

Mate why does Synapse after a reboot (at times) lose its set values... They revert to defaults although it shows Synapse Boot Completed....

Thanks in advance....
[Galaxy S 4 i9500 Original Android Development] Cleverfish:
same here, it happens when i changing settings on xposed module. trying to trace with logcat, will post my logs later :D

Sent from my GT-I9500
[Galaxy S 4 i9500 Original Android Development] skivnit:
The battery wakelock is draining my battery

Sent from my Perseus powered octa
[Galaxy S 4 i9500 Original Android Development] hathara:
oficial android 4.3 for those intereste

http://xdaforums.com/showthread.php?t=2488601&page=9
[Galaxy S 4 i9500 Original Android Development] zenosteam:
It's happened to me too sometimes and I have an force close after reboot the setting go to default but by tapping the x button I revert to my custom setting

Envoyé depuis mon GT-I9500 avec Tapatalk
[Galaxy S 4 i9500 Original Android Development] lukair1983:
Thanks man.

I guess seing Andrei is nowhere to be seen means he is working feverously on the perseus kernel for 4.3 ;) We can only patiantly wait.

I have one more question to someone who dig around this topic for a bit. From what I understand, the AMOLED works by lighting up the pixel with the given color. Since each pixel has it's corresponding subpixels, it will light the subpixels it needs to achieve the target collor.

So, for 100% black pixel, all subpixels will be turned off. For 100% red, only red subpixel will be turned on. For 100% green, only green supixel will be turned on, and for 100% blue only blue subpixel will be turned on. For other collors, depending on the mixture of subpixels, the desired subpixels will be light up. For example for white color, all subpixels will be turned on.

Did anybody study it a bit more in terms of power consumption (especialy the difference in power consumption from say whole screen with only red color vs, whole screen with white color)?

Also, if I leave the screen on, but I will open a full screen picture, which is filled with only full black color (#FF000000), does it mean, the phone will be awake (since the screen is turned on - theoreticaly), but the screen will take 0 mW in terms of battery consumption, since all subpixels are turned off? Or maybe even with all subpixels turned off, the screen hardware will still take some power (would be great to know about what kind of values we speak here) nevertheless?

Anybody kind enough sharing his finidngs (if he did dig around this subject)? I'm really curious about it.

Also side question: Is there any test I can do to see if the black pixels are indeed causing the subpixels to be completely turned off? The reasoning is that, even if the black pixels are treated by hardware as #FF010101 it will keep the screen to be draining a lot more power, than it suppose to.
[Galaxy S 4 i9500 Original Android Development] iamsachin:
He will need kernel sources. The updated blobs for PVR are incompatible with kernel drivers of 4.2.2
[Galaxy S 4 i9500 Original Android Development] lukair1983:
HassanM already confirmed it by a response to mine, but thanks anyway iamsachin. I appriciate it.

...

Question in relation to my previous post:

The above still stands, and I'm interested to get some info on above (if someone is kind enough to share it), but in relation to the smearing problem, as it's all related.

As far as I understand this problem and the fix to it, currently the default settings in Perseus are that the smearing is still there, but on the other side of the coin, pure blacks are pure blacks (#FF000000), which means less battery drain for black backgrounds. Correct?

To fix the smearing issue, all we have to do is tick the register hook checkbox, and up the smearing fix slider, to fix the smearing problem. The other side of the coin is that by doing that, it is now impossible to achieve pure black, which means, when the screen is on, all the pixels are constantly turned on, even if we set a pure black wallpaper. So far so good?

If so, I was wondering, how big of a battery usage difference are we speaking, between smearing fix ON vs smearing fix OFF?
[Galaxy S 4 i9500 Original Android Development] sorg:
It depends on usage scenario. If you are so curious, then do test by yourself. Why someone else should do it for you??

Use one day with smearing fix on, and another day with this feature off.

And then you will get the answer.
[Galaxy S 4 i9500 Original Android Development] lukair1983:
@Up

sorg, I wasn't telling someone to do it for me. I was asking if someone ALREADY did that for themselves, or found out about it from other source and would be kind to share that information. Don't put things in my mouth I did not say ;)

Trust me, I'm the last person to tell someone to do something for me over the internet, because I'm lazy.

ps. Yes, I'm already testing it bit by bit, but asking won't hurt, would it? Having 2 sources of information is deffinetly better, than having one.
[Galaxy S 4 i9500 Original Android Development] gio_b:
after flash 12.2 from 12 ;in setting i see version 12 ,is it normal?

tks gio.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
I have new kernel sources, but I'm just too lazy to screw around with just to get a few days lead over the official release next week which might have more changes.
[Galaxy S 4 i9500 Original Android Development] HassanM:
Way to go..... :thumbup::thumbup:

Im sure as and when ull come up with one for 4.3, it'll be great (as usual)....
[Galaxy S 4 i9500 Original Android Development] lukair1983:
Ok, if someone is interested I'm posting here a little (not very accurate, but with some vague idea) feedback about the tests I took.

Basicaly, I just made about 7 1080x1920 bmp's with one color in them and left the screen on for 30 minutes. White, Black, Red, Green, Blue, Purple, Black with #010101 and Black with #0F0F0F.

I was basing the percentage values based on the whole phone usage, so take that into account. My phone based on the conditions I created (Wifi on and connected, no other stuff turned on) used about 1% over 2 hours if the phone had screen off and was unused. Tested this twice.

First I did couple tests with 100% white and 100% black depending on the brightness.

With 10% brightness, I had ~3.5% drop with white and ~3% drop with black.

With 50% brightness, I had ~4.5% drop with white and ~3% drop with black.

Rest of the tests I did with 100% brightness.

With 100% white the battery dropped by ~9%. Did that test twice, same result.

With 100% black I had ~3.5% drop

With Black #010101 I had ~2% drop (as odd as it was)

With Black #0F0F0F I had ~2.5% drop

100% Red - 4.5% drop

100% Blue - 6.5% drop

100% Green - 7.5% drop

Purple - 7.5% drop

I'm running on 100MHz minimum, set in Synapse, with undervolting. That frequency was probably on 99% of the time (at least) during the tests.

Seems the black is pretty consistent no matter the brightness (which appears to prove the black is indeed achieved by turned off the pixels, and works). The one thing that is strange to me though, is that it would suggest the phone consumes 2-3% over 30 minutes with no pixels lit on. Obviously the phone itself is not asleep completely at the time, so it will take more power, but if that's the case, it would seem the screen takes much less (white with 10% brightness took roughly 0.5-1.0% over the nominal amount) than the rest of the battery consumption, and I'm not sure if that's based on the facts we know.

I know these are not results from a laboratory experiments in controlled environment so please don't shoot me. If someone wants to draw some conclusions from it, feel free. It would be nice though to get some substantiated info from samsung technician, as it would appear the screen brightness is not as damaging until we reach 50% of it, and I tended to be so far pretty aggresive about the brightness setting to extend battery life. Also I'm curious to know how much exactly (if any) the screen takes (so the whole screen segment that is shown under the "Screen" usage in battery info) when the whole screen is covered with 100% black picture. Does it take 0 mW or close to 0, or does it take some set amount (to keep the screen reaction fast in case the color of the pixels will change in a second).
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Interesting. I'd want to confirm that.

It's correct. The whole "screen takes most of the power on a phone" is complete BS and only valid if you're blasting the brightness way up.

As expected. The power scales quadratically to the voltage, and brightness controls the voltage.

I suspect the smearing is a side-effect of a power saving technique on the PWM regulators for the screen, with minimized power as the goal, but you'll probably never hear any concrete facts on this since it's mostly proprietary industry secrets.
[Galaxy S 4 i9500 Original Android Development] Vurda:
I have deleted Better Battery Stats and now everything is fine. No more battery drain. Strange :what:
[Galaxy S 4 i9500 Original Android Development] jujuburi:
Maybe you had Watchdog enabled in BBS.
[Galaxy S 4 i9500 Original Android Development] lukair1983:
The tests obviously weren't deterministic, and also I was measuring percentage based on the whole phone battery usage, so some margin of error is to be expected.

Thanks Andrei for correction. I will remember that.

It might very well be.
[Galaxy S 4 i9500 Original Android Development] HassanM:
Yes..... Same here.... I assume since it a variation of 12, its showing as 12
[Galaxy S 4 i9500 Original Android Development] gio_b:
i see.but now i m on 4.3 so i hope in a omega update.any previsions?

Tks giovanni.
[Galaxy S 4 i9500 Original Android Development] ama3654:
Official 4.3 rolling out, can't wait for your awesome kernel, thanks
[Galaxy S 4 i9500 Original Android Development] lukair1983:
Andrei, I have a quick question over here. Any reason why the current applied to the phone while on AC charge was lowered by you to 1600 mA, from default 2000mA (that your Synapse is showing)? Is it just a mistake on your part, or was it deliberate?

BTW Andrei, today I had a chance to tweak notification LED more to my liking thanks to your kernel. Again, awsome work.
[Galaxy S 4 i9500 Original Android Development] iba21:
someone could teach me the freq steps of A7 A15 cores?

i'm on note3, and, it has the cluster migration (as i see).. it uses the interactive governor as stock (??? not so logic) but i rooted it and change to ondemand, witch has the same ondemand as you have in s4

so, i'd want to fix it, but, as i could understand, 600mhz loaded by kernel are 1200mhz of A7 core? :confused:

it means when cpu is at 600mhz A7 is always used?

many thanks for answer

p.s. use tech explanations :laugh:
[Galaxy S 4 i9500 Original Android Development] alawadhi3000:
Anybody with charging issues using the latest version, my phone sometimes charges slowly, it used to be fine using older versions.

I'll try removing unstable power detection.
[Galaxy S 4 i9500 Original Android Development] gdonanthony:
as what i know 100-600mhz are the A7.... 700-above are the A15

the A7 freq is double meaning when it is in 600 it means 1200mhz of A7 while A15 remain as is of its freq...

if im wrong could someone correct me XD
[Galaxy S 4 i9500 Original Android Development] silvercat:
What cable do you use to charge your phone, is it the S4 cable which came with it or a different one ? Because I had this same issue I was using my old s3 cable which puts out only 500mA max then I change it to S4 micro usb cable which put out around 1200mA and it charges much faster now. Try changing the cable
[Galaxy S 4 i9500 Original Android Development] AL_IRAQI:
New Source For MJ5 Available Now :D:D

http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=i9500

Sent From my i9500 With ☆★Crash Rom★☆
[Galaxy S 4 i9500 Original Android Development] nhariamine:
When i flashed perseus on my S4 I9500, i didn't find STWEAKS ?? is this normal
[Galaxy S 4 i9500 Original Android Development] AL_IRAQI:
There's No Stweaks Any More

You Will Find

Sent From my i9500 With ☆★Crash Rom★☆
[Galaxy S 4 i9500 Original Android Development] zenosteam:
it's available on play store too
[Galaxy S 4 i9500 Original Android Development] Crash:
Nice hope that Andrei can released soon. . To start testing Crash v9

Hugs

Sent from my GT-I9500
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Here's a raw build with the new stuff. Need to fix the action-bar highlighting in Synapse for 4.3 in general, but everything else seems to work.

I uploaded a blob commit with the changes for GPL's sake, but I'll follow up proper commits later on and a proper changelog, I'm just not in the mood for it now.

4.2.2 users should obviously not touch this, and AOSP 4.3 users may need to copy over the SEC4.3 PVR blobs. Didn't test any of these yet so you're on your own for now. I'll follow up with a proper release tomorrow.
[Galaxy S 4 i9500 Original Android Development] Crash:
Thanks andrei is time for me to test if my rom (deodex) now to se if it works....

Hugs bro ;)
[Galaxy S 4 i9500 Original Android Development] dragon135:
Dear Andrei,

Could you make screen mirroring works on custom kernel?

Sent from my GT-I9500
[Galaxy S 4 i9500 Original Android Development] tabenf:
Flashed on stock works great thnx andrei
[Galaxy S 4 i9500 Original Android Development] dibartolodroid:
On stock 4.3 ????

Envoyé depuis mon GT-I9500 avec Tapatalk
[Galaxy S 4 i9500 Original Android Development] alawadhi3000:
Original charger with original cable that came with the S4.
[Galaxy S 4 i9500 Original Android Development] Degrated Shadow:
lost root:crying:

flashed cf root and update supersu .zip to check.

did not work
[Galaxy S 4 i9500 Original Android Development] AL_IRAQI:
can you please set selinux to permissive :confused:
[Galaxy S 4 i9500 Original Android Development] ghost02:
Hi, sorry if this has been answered but is this knox free? I'm still on 4.2.2 but waiting for a rom to use a 4.3 kernel that works with the old bootloader so I don't have to set knox status to 0x1.
[Galaxy S 4 i9500 Original Android Development] chapruk:
i had 4.3 on my s4 and flashed cf autoroot..but i cant open supersu it said "there is no SU binary intalled".. anyone can help?

and if i flash perseus 13 raw.. will it root my s4 properly? thx..

---------- Post added at 12:47 AM ---------- Previous post was at 12:47 AM ----------

i had 4.3 on my s4 and flashed cf autoroot..but i cant open supersu it said "there is no SU binary intalled".. anyone can help?

and if i flash perseus 13 raw.. will it root my s4 properly? thx..
[Galaxy S 4 i9500 Original Android Development] Seyaru:
Installed and work amazing thanks [MENTION=4167023]AndreiLux[/MENTION] i know not is really import but the score in Antutu suck :P i got 11429
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
You're doing it wrong then.

I don't really see what the advantage of that would be, everything works even in enforcing mode.

I didn't touch my bootloader and everything is running fine with the old one.

And with that, I'd like for root, Knox, and any other such discussions to be held in a separate thread, it's up to you or your ROM provider to solve any problems.
[Galaxy S 4 i9500 Original Android Development] gp545:
As Andrei stated it's just a raw file. Lots of squashing and changes to be made. Score will be higher once furnished one arrives ?
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
That is absolutely not what I have said and please do not claim things like that out of thin air. Performance won't change.

I'm getting 27450 while limited to 1.4GHz, so I don't see any issues with performance.
[Galaxy S 4 i9500 Original Android Development] Degrated Shadow:
Even crash lost the root
[Galaxy S 4 i9500 Original Android Development] tabenf:
yes trough odin
[Galaxy S 4 i9500 Original Android Development] gp545:
Sorry, Sir :)
[Galaxy S 4 i9500 Original Android Development] Seyaru:
thanks both for the clarification, now i wipe chache and dalvik and the new score in AnTuTu X is 22000 and AnTuTu is 27500 :victory::victory:
[Galaxy S 4 i9500 Original Android Development] Crash:
[MENTION=4167023]AndreiLux[/MENTION]

Yes friend i lost root since i don´t care much on warranty this is what i do

Flash stock 4.3 via Odin PC usin a pit file too. Then

Install root via odin (root works fine on stock rom)

Install same red CWM

Full wipes

Install my new Crash Rom v9 with your kernel and them lost root y even try to re root via Odin without success.

My rom is deodex but i don´t now if users who run stock rom have the root problem ...

Thanks for your work my friend
[Galaxy S 4 i9500 Original Android Development] djigane:
Flashed v13-raw

Lost root

Flashed cf autoroot

Regained root

Everything running fine

Et voilà...

One Kernel to rule them all...

Thanks [MENTION=4167023]AndreiLux[/MENTION]

Edit : and don't forget to reflash custom recovery...
[Galaxy S 4 i9500 Original Android Development] ewerthon_jp:
hi friend, may i ask only if your knox flag is 0x0 or 0x1? thanks.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
It doesn't matter what my knox flag is because I don't have one. I didn't blindly update to the new bootloaders so I don't have any of these problems.

I'm more concerned with the TIMA wakelock from userspace right now, it seems to disagree with Knox not being there anymore.