yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9500 Original Android Development] Hans Kruger:
Will u please tell us how did u manage to avoid new bootloaders when u updated to 4.3 and managed to avoid know flag. Thx
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
I simply didn't flash the bootloader via Odin as everybody else did, duh.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Here's a version with SELinux flat out disabled. If the TIMA user-space entity is still misbehaving, please report so.

Edit: Well that's interesting. Disabling SELinux basically shaved the Synapse loading time almost in half:

(Was in the 3.5s range before)

I guess that was one of the TouchWiz lag sources.
[Galaxy S 4 i9500 Original Android Development] a9402169:
I have noticed that the 4.3 stock kernel was integrated with a Zram.

I wonder if it can be also integrated to Perseus kernel.
[Galaxy S 4 i9500 Original Android Development] hypergamer1231:
Sorry but I am on official 4.3 and after flashing raw 2 even cf root doesnt work at all!!!
[Galaxy S 4 i9500 Original Android Development] bala_gamer:
Any specific reasons why the selinux enforcing the lag?
[Galaxy S 4 i9500 Original Android Development] Technecium:
no

http://www.securelist.com/en/blog/9175/Android_4_3_and_SELinux

This is an interesting/important read. SELinux policies on Android are not enforced. From my understanding it just logs security violations of the policy but does not enforce them. That is why Samsung came up with KNOX.

The lag could be due to additional, and even excessive log activities.

This next theory I'm not sure about and I don't want to put out bad info so please correct me if I'm wrong.

If SELinux is enforced along with ROW scheduler it might explain the lag. SELinux would look for and possibly log violations before the app is allowed to load.
[Galaxy S 4 i9500 Original Android Development] gp545:
Tried all possible way, Still can't get root permission after flashing Raw kernel version 13 :( Don't know why :(
[Galaxy S 4 i9500 Original Android Development] mw86:
Guys im on 4.3 and I am rooted again and on a custom recovery with Andrei's raw kernel above.

Try this

Flashed perseus, reboot, flashed root, reinstalled su in play store, opened it and it installed when asked and I rebooted and worked. Then finally flash philz again. Wait till now or recovery is gone again anyway

Key point for you guys witg troubles: super su and synapse need to be installed from playstore. The su reinstall is necessary I releaized maybe from it existing and being updated before installing perseus... after install needing root , when you root super su disappeared from app drawer on boot... just reinstall it from playstore the older version in cfroot is infact reinstalled and installing from playstore works. Make sure to now open su and let it update as asked I hit normal install. Reboot and your good to go after boot. But use my steps above for the right order
[Galaxy S 4 i9500 Original Android Development] Xphoid:
Thanx mw86... This way works also for odexed custom rom....

My no touchwiz - odexed rom is now fully rooted on raw 2...
[Galaxy S 4 i9500 Original Android Development] mw86:
Anyone having an issue of after sometime of having your profile set in synapse like I had it successfully apply on boot and I run a few benches and the scaling seems messed up. I reboot it goes away. After time it comes back but faster if I enter synapse and leave it and bench. Just using quadrant atm. But not sure if this is related to user space.

I had root on se linux on stock with set to permissive. The above method got me rooted on Raw2 so I wonder if se linux disabled was necessary vs permissive. I don't fully understand how it works so it maybbe a stupid question.
[Galaxy S 4 i9500 Original Android Development] bala_gamer:
[MENTION=4745870]mw86[/MENTION]

strange, after flashing the last tar file andrei posted im not able to achieve root regardless of whatever method i try. any btw just noted my cpu temp is idling around 40 C, never seen such low temps in my device till now , wondering if selinux is causing some persistent cpu usage in the background

Edit : none
[Galaxy S 4 i9500 Original Android Development] Beny The Kid:
Just flashed on the latest Halogen build. Nothing but black screen after the I9500 splash screen. Used ODIN 3.09 and put in the AP slot.
[Galaxy S 4 i9500 Original Android Development] iamsachin:
The last uploaded HaloGen build doesn't have 4.3 blobs
[Galaxy S 4 i9500 Original Android Development] Beny The Kid:
RAW build

Should have mentioned that I was using his RAW build that he posted in the thread at the end of the day yesterday, not 12.2.
[Galaxy S 4 i9500 Original Android Development] iamsachin:
It's mentioned there. Also there is a discussion there about the newer 4.3 blobs being tested by me.
[Galaxy S 4 i9500 Original Android Development] Beny The Kid:
Apologies, thought I read that he wasn't sure how it would run.....figured i would test and report.....and i can't believe you're still awake!
[Galaxy S 4 i9500 Original Android Development] bala_gamer:
because its 2 PM here in India ;)
[Galaxy S 4 i9500 Original Android Development] tabenf:
this doesnt work for me what bootloader you on?
[Galaxy S 4 i9500 Original Android Development] cgvelmax:
Hi bala_gamer try this steps works for me

install es file Explorer as root mode

flash Perseus

wait until reboot

freeze super su

reboot on download mode

flash cfauto root

wait until reboot

reboot on download mode again

flash S.a.M.e.R_d cwm 6.0.4.4

reboot

go to es file explorer in this point su ask grant access su for all rooted apps grant access

go to the playstore and update super su

open super su and update binaries
[Galaxy S 4 i9500 Original Android Development] lukair1983:
Hi guys

Andrei pretty much ordered us couple pages back to not talk about knox, root issues and so on, so... I hope he won't shoot us. Not yet, at least.

I got one inquiry to someone who would be kind enough to confirm it.

I have to say the topic of bootloaders was pretty new to me, I did research it and learned a bit about it. From what I understand (correct me if I'm wrong) bootloader often does not have to be updated when flashing newer stock (or even custom) ROM's. In fact many custom ROM's either flash the older (stock) bootloader, or don't flash bootloader at all. The point is, the new firmware can be flashed, without updating the older bootloader (correct?) and everything should work just fine. Andrei's post pretty much made me aware of it for the first time, when he said he just ignored flashing the new bootloader, and that's why he doesn't have to deal with this KNOX stuff.

Also, KNOX module in 4.3 with the 0x1 warranty flag is only being "installed"/activated with the new bootloader that is in 4.3 update. And this is exactly why I don't get it. There are so many laments on many threads from many people about this flag, and the reason (that I got) is not that they can't use KNOX along with custom roms / rooted phone, but that the KNOX is there to begin with while they don't want it at all. So the thing that I don't get is why just everybody omit from updating the newest bootloader, and while flashing 4.3 updates to either 9500 or 9505, they just untick the bootloader checkbox in Odin? Won't that "fix" the issue people are having with all this KNOX drama?

I must be missing something here... Can someone straighten me out?
[Galaxy S 4 i9500 Original Android Development] tabenf:
How did u freeze su
[Galaxy S 4 i9500 Original Android Development] cgvelmax:
go to application manager find super su and turn off
[Galaxy S 4 i9500 Original Android Development] tabenf:
Hi guys opened a new thread in discussion about root problems please post feedback and solution's there!

http://xdaforums.com/showthread.php?p=46767503#post46767503
[Galaxy S 4 i9500 Original Android Development] astoncheah:
hi Andrei,

flashed RAW2, using it for half day, my phone no able to go deepsleep, checked with BBS, shows TimaService waking all the time.
[Galaxy S 4 i9500 Original Android Development] NBruderman:
Its a Raw release, problems might occour.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
That's the TIMA issue I was talking about, trying to figure out where it is in the ROM and if it's possible to kill it.
[Galaxy S 4 i9500 Original Android Development] Xphoid:
i am also on raw2 since morning... when i look at the bbs i dont see any major wakelock... fyi...

really debloated custom rom... odexed without tw but nova instead...

only problem occured was, could not get root until i flash CF root through odin...somehow SuperSu apk can not find Su binary and dont update or install itself if you dont use CF root.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Are you on a Knox bootloader? The TIMA libs are I think trying to communicate with the trustlet which simply doesn't exist on the old BL.

The TimaService is something deep in the services framework so it can't be easily deleted. Still need to check under what conditions it fails or not. Please post what you've cleaned out and what not on your ROM.
[Galaxy S 4 i9500 Original Android Development] Xphoid:
Since i flashed stock Indian MJ5 with adonis.pit through odin... i guess i am on new bootloader... did not do anything to prevent it... will post all apps removed folder screnny... but especially all KNOX related apps and related files like /system/container and others with related subfolders under lib or vendor...etc...

tough nothing touched at services framework.

Edit: Removed apps list is attached..
[Galaxy S 4 i9500 Original Android Development] Xphoid:
txt file attached...
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
I'm not able to reproduce your setup, still getting the TimaService wakelock.
[Galaxy S 4 i9500 Original Android Development] Xphoid:
if you wish i can upload the rom and can send you but most probably tomorrow early in the morning.... upload will take some time.

Edit: just checked again after a manual reboot some time ago... for the first time i can see 28m tima service wakelock... :(

only difference is i put livewallpaper since morning... changed to static and rebooted... will observe again.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Ah good. At least I know I'm chasing the impossible. I'll try other things then to track it down.
[Galaxy S 4 i9500 Original Android Development] Xphoid:
one question, you get that wake lock asap? or after some while?
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Don't know what's getting triggered. Right now it seems to behave for now.
[Galaxy S 4 i9500 Original Android Development] AL_IRAQI:
I don't have tima service wakelock I check it in BBS and WakeLock Detector

I'm using the new BL.

Sent From my i9500 With ☆★Crash Rom★☆
[Galaxy S 4 i9500 Original Android Development] sergioortegac:
Hello :DO, i install 4.3 android version, is Perseus compatible? :D
[Galaxy S 4 i9500 Original Android Development] cgvelmax:
Yes, find Perseus 13.0 raw2 a few pages back.
[Galaxy S 4 i9500 Original Android Development] bala_gamer:
Having tima service wakelock with raw2 and old bootloader.

I could see three tima based lib files under system/lib/

libtlc_tima_***. so

If someone has necessary backups, try removing those three files and see if it solves the issue. I'm still looking to root back my device after raw2 is installed and hence cannot remove those files. Damn thats embarrassing
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Removing the lib files will cause failure to boot.
[Galaxy S 4 i9500 Original Android Development] bala_gamer:
How about changing permission?
[Galaxy S 4 i9500 Original Android Development] Xphoid:
After a 7 hour sleep... full of wakelocks... :( wished my yesterday's without wakelocks experience was still valid.
[Galaxy S 4 i9500 Original Android Development] Xphoid:
After I charge a little bit... gonna backup and try... change to only r for the owner maybe?

Edit: Changed permissions to non and don't boot...
[Galaxy S 4 i9500 Original Android Development] bala_gamer:
[MENTION=4611832]Xphoid[/MENTION]

thanks for the quick check

[MENTION=4167023]AndreiLux[/MENTION]

tried flashing wanam 3.0 kernel to see how it reacts, and surprisingly there is no single wakelock from tima service, its almost an hour. May be the wakelock is related SELinux status ? FYI im using old bootloader with stock mj5 rom ,knox related apps frozen via TB.

Edit:

One more request,

can you fix the abnormal gpu usage shown in "sgx_gpu_utlization" in sys/module/pvrsrvkm/parameters ? It looks weird to see usage going beyond 100% . Its not that critical for time being but may be you can add it to your todo list
[Galaxy S 4 i9500 Original Android Development] gp545:
Yes! I can confirm that. Wanam 3.0 Kernel will not break root, may be because Wanam included SuperSU binary files inside of flashable Zip :D
[Galaxy S 4 i9500 Original Android Development] NBruderman:
I can confirm that too (With the old bootloader)
[Galaxy S 4 i9500 Original Android Development] mw86:
Is this build prop related. Does this help anyone with the wake lock if set to 0?

ro.config.tima=1
[Galaxy S 4 i9500 Original Android Development] Alberto96:
[MENTION=4167023]AndreiLux[/MENTION] : Waiting for your CM Kernel :) I finally switched to latest available CM (TouchWiz was sooo laggy) and i miss your kernel features.

Thanks a lot

P.S. : This isn't an update request. For me you can release CM Kernel also on 2014 xD
[Galaxy S 4 i9500 Original Android Development] Alberto96:
[MENTION=4167023]AndreiLux[/MENTION] : Waiting for your CM Kernel :) I finally switched to latest available CM (TouchWiz was sooo laggy) and i miss your kernel features.

Thanks a lot for your work, im a Perseus dependent now :P

P.S. : This isn't an update request. For me you can release CM Kernel also on 2014 xD
[Galaxy S 4 i9500 Original Android Development] anasnemer:
is it working with 4.3 ???
[Galaxy S 4 i9500 Original Android Development] lian_diary:
it works for me, thanks!:good:
[Galaxy S 4 i9500 Original Android Development] matheus_sc:
I think v13 raw2 is compatible as recommend for halogen build.
[Galaxy S 4 i9500 Original Android Development] mw86:
So on 4.3 on perseus raw 2 build your not getting the Tima wakelock under the system category of kernel wakelocks? Great if so. This working accross the board guys?
[Galaxy S 4 i9500 Original Android Development] lian_diary:
sorry i don't know much about it, I just follow your tip, edit the ro.config.tima=1 to 0

than the wacklock problem saved :D

do you know what does this tima service mean?
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Yep, I haven't encountered the wakelock since ro.config.tima=0 (The service is disable-able through "Disable Serivce" on the Play store but the wakelock still persists, which means it's triggered in the framework itself).

I'll leave it be until tomorrow to confirm it's not a fluke, if it causes no more problems then I'll release a proper version, and I'll disable everything related to it on the kernel side.

TIMA (TrustZone-based Integrity Measurement Architecture) is the whole security shabang which KNOX runs on, it's the whole TrustZone + Bootloader + Kernel mechanisms.
[Galaxy S 4 i9500 Original Android Development] mw86:
Well I am obliged to have been involved. I will hope it stays in check for the remainder of the day as well. :good:
[Galaxy S 4 i9500 Original Android Development] alawadhi3000:
I don't get wakelocks anymore also, I'll test it more though. Thanks MW86.
[Galaxy S 4 i9500 Original Android Development] mw86:
Andrei, would you kindly include root in your next update if this is in fact resolved I am guessing you will merge the rest of your kernels planned updates and fixes since the wakelock was such a showstopper. I figure you may have planned this anyway but doesn't hurt to ask.
[Galaxy S 4 i9500 Original Android Development] bala_gamer:
I'm about to edit the build.prop, but wondering why I didn't get tima wakelock with adam 3.0. Inn the last 16 hours, the time wakelock has occupied just 48 secs. Is this thing directly related to selinux status or what? Apart from that I didn't notice any changes between raw2 and adam 3.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
I'll see tomorrow what needs to be done. The kernel should be able to root and disable TIMA and any other nonsense.

Just wondering if I should kill the Knox suite / apps with the kernel, probably since anybody who wants Knox shouldn't use the kernel in the first place.
[Galaxy S 4 i9500 Original Android Development] AL_IRAQI:
Add Script to remove all knox files in CWM Zip

They Can Download .tar file to flash only the kernel without removing anything

Sent From my i9500 With ☆★Crash Rom★☆
[Galaxy S 4 i9500 Original Android Development] Xphoid:
I found out more Knox related garbage in the rom that l removed... If you wish I can share only those ...

BTW I am also now on adam kernel, but build.prob line about Knox is untouched, stock...

And after a night sleep, there is not even a TIMA log in my BBS... FYI..
[Galaxy S 4 i9500 Original Android Development] djigane:
Just for your information, I've Flashed v13-raw2 via odin3-v1.85 provided in the CF-Auto root package for i9500 and I DIDN'T LOST ROOT.

Cheers
[Galaxy S 4 i9500 Original Android Development] alawadhi3000:
I get wlan wakelocks now. -_-
[Galaxy S 4 i9500 Original Android Development] lukair1983:
+1 from me.

From what I see in the threads, users who do root the phone, or flash custom roms, don't seem to want the KNOX module at all. At least that's the notion I get mostly.
[Galaxy S 4 i9500 Original Android Development] KPOCAB4EG:
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=XXUEMJ5
[Galaxy S 4 i9500 Original Android Development] iamsachin:
Good one :P
[Galaxy S 4 i9500 Original Android Development] darixtorento:
first of all, you are doing great work! thank you so much for perfect kernel :D

hoping to download and install your brand new kernel for 4.3 once it will be out in your website

just thanks for everything! :)

I dont know if you need/care but i will say it anyway.. doesnt hurt to say :D

In my opinion, I think you should kill all the Knox suite and whatever related services to that.

most of the people who use custom rom and kernel, dont even need all that Knox thing..

until now people got used without it (cuz its a new useless feature). so it will be the same as now- without knox.

all those services just make the device slower.

you can make a poll in your thread so we all can know what people really want/need.
[Galaxy S 4 i9500 Original Android Development] gio_b:
Quote:

Originally Posted by KPOCAB4EG View Post

http://opensource.samsung.com/recept...hValue=XXUEMJ5

Hi,i flash over the stock rom 4.3 ,wanam 3.0 :

my i flash this one ?

tks giovanni.
[Galaxy S 4 i9500 Original Android Development] jujuburi:
Lol you couldn't find a post to quote other than that? :what:
[Galaxy S 4 i9500 Original Android Development] RonenAyash:
Hi guys.. I want to overclock with this kernel I need the voltage to OC and little guide to OC my i9500.. tnx

★☆ Sent From CrashRom V8.8 GS4 ★☆
[Galaxy S 4 i9500 Original Android Development] omvir:
Accidnelty liked your post. Oops. Um but yeah for that you'll need to experiment with your phone and what voltages/speeds it can or cannot handle. We can't pull data like that out of our asses for every phone. Every phone is unique in its build quality.
[Galaxy S 4 i9500 Original Android Development] acidmoder:
So, I believe I am the only one that has a rooted device with custom Kernel that does like KNOX. With KNOX I don't have to encrypt my whole phone to access my company's exchange server. With KNOX I just have a separate native Samsung email set up without having to touch the rest of my device. And that really rocks for me. Anyway, I had already spent several bucks on the TouchDown email app. If Andrei decides to remove all KNOX stuff I definitely can live with that! ;)
[Galaxy S 4 i9500 Original Android Development] jujuburi:
Could you elaborate this part? What email settings? Is it for your company or like normal email servers like GMail and all? Push enabled?
[Galaxy S 4 i9500 Original Android Development] acidmoder:
KNOX provide a separate encrypted environment and it has its own apps such as Camera, Galery, Email, Calendar, Contacts, etc. That includes a KNOX-specific home screen too.

My company uses Exchange email server. Before KNOX, if I wanted to configure that email on my S4, I was forced to accept a policy that obliges me to set a password-protected lock screen and encrypts the whole phone storage. This makes the phone run slower and also prevents me from fooling around with some stuff I like. :angel:

With KNOX I don't have that problem anymore, as it is a completely separate environment and it is already encrypted by default. So, when I want to check on my corporate emails I just start KNOX, type in the KNOX password and open the KNOX-specific email app. The rest of the phone is untouched.
[Galaxy S 4 i9500 Original Android Development] jujuburi:
Thanks, I thought it would somehow help me enable push mail for Gmail. No good for me, glad deleted every bit of it.
[Galaxy S 4 i9500 Original Android Development] zenosteam:
Hi, i flashed a a latest version of kernel but I have always this wake lock can someone explains me what it is thanks

Envoyé de mon GT-I9500 en utilisant Tapatalk
[Galaxy S 4 i9500 Original Android Development] matheus_sc:
This is about mobile signal.
[Galaxy S 4 i9500 Original Android Development] clavicle:
Timaservice wakelock for me

Editing build.prop did the trick!

Editing build.prop did the trick!
[Galaxy S 4 i9500 Original Android Development] zenosteam:
ok thanks for the info, i have an incredible battery drain and the phone don't go to deep sleep how can i solve this iam on legend rom 4.3 version
[Galaxy S 4 i9500 Original Android Development] dragon135:
I think you should check partial wakelock or alarms

Sent from my GT-I9500
[Galaxy S 4 i9500 Original Android Development] zenosteam:
There is nothing special on it. I think

Envoyé de mon GT-I9500 en utilisant Tapatalk
[Galaxy S 4 i9500 Original Android Development] zenosteam:
The second screen shot with Adam kernel

Envoyé de mon GT-I9500 en utilisant Tapatalk
[Galaxy S 4 i9500 Original Android Development] Glen:
same here, timaservice wakelock keeps my device awake all the time.

hope andreilux has a new kernel soon enough :D

anw, thanks a lot for the kernel. beside the wakelock problem it's really good :)
[Galaxy S 4 i9500 Original Android Development] mw86:
How many of you posting of tima wake lock read my post or any of Andrei's posts? There is a slew of these posts which were uneeded. If you set the build prop we mentioned you will not have the tima wakelock on the current raw 2 build of the kernel. Besides that Andrei already mentioned all his plans to us that included qll that continues to be inquired about. Perhaps no one has answered because the answers were in the posts not far before all of these. Simply please read guys. If you've bwen away from thread for awhile catch up on what you have missed before posting questions.
[Galaxy S 4 i9500 Original Android Development] Glen:
hi mw86, sorry I must've missed your post.

I will be more thorough another time.

thanks.
[Galaxy S 4 i9500 Original Android Development] Shrey14:
Guys, whenever I overclock my cpu and gpu using synapse, the phone becomes very unstable keeps rebooting. Is there a fix or is it just my phone?
[Galaxy S 4 i9500 Original Android Development] HassanM:
Whats your A7 frequency set at??
[Galaxy S 4 i9500 Original Android Development] mw86:
Which kernel version are you using including is this on 4.3 or 4.2.2 android version?
[Galaxy S 4 i9500 Original Android Development] MATHReX:
Thanks A Lot For The Perseus Kernel !!

HUGE IMPROVEMENT In The Phone With It !!

But Just 1 Problem I'm Facing Is , When I'm Playin Games Like Dead Trigger 2 ! The Game Works For A Moment !

And At A Instant The Phone Crashed With Yellow And Green Lines.. !!

Any Way To Fix It ?