yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9500 Original Android Development] cmd512:
Instead of attacking people who have proof on their own devices Philz is working fine, how about you spend your time actually providing EXAMPLES of these "problems with 4.3 update?"
[Galaxy S 4 i9500 Original Android Development] jujuburi:
Lol. Have Philz installed, flash a custom ROM, give me audio. Jeez :eek:
[Galaxy S 4 i9500 Original Android Development] cmd512:
lukair didn't flash a custom ROM, he said he flashed WanamLite which is odexed like stock ROM, and his audio is working fine. Try again.

"Jeez."
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
What the **** does audio even remotely have to do with what a recovery does? You stop posting nonsense.
[Galaxy S 4 i9500 Original Android Development] jujuburi:
Lol.
[Galaxy S 4 i9500 Original Android Development] cmd512:
Seriously? You come in here, attack someone who has actually contributed this thread with credible finding / feedback, and the best you can cough up as proof of your claims is this?

I'll file you under "How to look like a jackass online."
[Galaxy S 4 i9500 Original Android Development] Vurda:
Andrei, will your kernel support MIUI? tried 14.1 but did not succeeded.
[Galaxy S 4 i9500 Original Android Development] cmd512:
Just confirmed the easy 4 steps you posted (courtesy of Andrei) worked beautifully, running Perseus 14.1 on 4.3 + latest Philz recovery perfectly, direct no-wipe flash upgrade from 4.2.2!

*Cheers*
[Galaxy S 4 i9500 Original Android Development] ivanchin99:
On a 4.3 with Philz. What problem??
[Galaxy S 4 i9500 Original Android Development] cmd512:
Apologies if this has been reported already, but you guys notice 4.3 is using 100 and 150 MHz CPU scaling frequencies? I just checked Synapse, and my lowest frequency is set to 200 MHz.

(There isn't even a way to adjust 150/100 MHz voltages it seems...)
[Galaxy S 4 i9500 Original Android Development] lukair1983:
Maybe I have the same problems, but just didn't notice them. If you were more specific I might check them.

However, I did 2 nandroid backups already, and I didn't notice any problems while doing that, or afterwards.

Just to confirm, no problem with audio over here whatsoever, since I flashed Wanams' 3.2 and that was almost 2 weeks ago.

Awsome. I would just wish someone posted those Andrei steps, with some big letter info in the i9500 section on top, so that people would not post all this conflicting information since 4.3 was released, as it made a person really, really confused.

It was like that since the beginning. All the A7 frequencies are shown as doubled, so if you have a voltage for 200 MHz, it's really for 100MHz. If you have on the list a voltage for 1400MHz (A7), it really is 700MHz, so on and so on.

ps. Andrei, please keep in mind this favour we asked for (setting the reset after reboot option on/off).
[Galaxy S 4 i9500 Original Android Development] skivnit:
I think it's not kernel related but since 4.3 update the biggest battery drainer is Android os. Anyone else experiencing this?
[Galaxy S 4 i9500 Original Android Development] cmd512:
Ah right, totally forgot about the doubled frequency, duh. My apologies, been away for far too long. :)

And agreed, those simple flash instructions need to be stickied, all these people doing hokey stuff and flashing pit files, complete waste of time.
[Galaxy S 4 i9500 Original Android Development] iba21:
Hi andreilux, please could you explain me what are these 2 sysfs values?

http://www.imgur.com/66mPw8A.png

I undersand that the maxfreq is the real maxfreq, if i force it to 600mhz, maxfreq of all cluster will be of 600mhz!

But, what's the minfreq? In normal condiction it's at 1800mhz, in batterysave the minimal value is 650mhz..

Is it the minfreq of the A15 cluster?
[Galaxy S 4 i9500 Original Android Development] susmitpatil:
4.3 download

Guys, a noob here.

Is Perseus Kernel compatible with 4.3? My GT-I9500 is not rooted and i want to flash Perseus, but i am on stock 4.3 (MJ9 build).

Someone please tell whether i can flash it on 4.3 version and also the steps on flashing a kernel.

Thanks..
[Galaxy S 4 i9500 Original Android Development] ktouy:
Yes its compatible until v14.

First you need to root your device, then install a custom recovery, i dont know the last one or the best, im using the old cwm but you can look on this treads for that. Then on the recovery just flash it.

Im on omega rom v11 based on mj9 over there are some tutorials to flash it if you want.

Take in mind that the guarranty will be avoid an all that stuff. And please read!!

And backup all the things while you can.

Good luck!

...the tiny italic text...
[Galaxy S 4 i9500 Original Android Development] cgvelmax:
[MENTION=5026489]susmitpatil[/MENTION] flash through odin Perseus 14.1 the .tar version of course.

Enviado desde mi GT-I9500 mediante Tapatalk
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Never tried MIUI, no idea.

They're the frequency range for all clusters. No idea why you have those values for the minimum.
[Galaxy S 4 i9500 Original Android Development] iba21:
Do you have 250000 in minfreq sysfs? :what:

EDIT: i tryed to put a value of 800mhz, and, real the minfreq changed to 800mhz!

So, it works, but, even if i write 250000, value doesent change in sysfs value, but minfreq will be 250000

Absolutely strange.. well nvm.. thankyou!
[Galaxy S 4 i9500 Original Android Development] ktouy:
Here the tread to root it

http://xdaforums.com/showthread.php?t=2292615

And here for the recovery

http://xdaforums.com/showthread.php?t=2489234

...the tiny italic text...
[Galaxy S 4 i9500 Original Android Development] susmitpatil:
Thanks dude... N cf autoroot will worl with 4.3, right?
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
The kernel will root your device, you don't need CF. Also as mentioned, you don't need that specific recovery neither.
[Galaxy S 4 i9500 Original Android Development] cmd512:
^ I second everything mentioned above by Andrei, this has to be the easiest upgrade to a new version of Android... ever. No factory resets / wiping, no reinstalling, just go to the same recovery you probably already have and clear out the caches, flash WanamLite, and then flash Perseus. Upon the initial boot, everything is just like you left it and auto-rooted.

It's so damn disappointing there are so many bad instructions floating around involving hokey pit files and recoveries, flashing stock first, blah blah blah... I almost hate to think about the many unnecessary hours some people have spent on this endeavor. But I digress...
[Galaxy S 4 i9500 Original Android Development] wooptarik:
MIUI is based on 4.2.2, you need o install Persus 12.2

haven't tried, but good luck
[Galaxy S 4 i9500 Original Android Development] mw86:
It was incredibly easy uograding to 4.3 im even using the old chinese pit file to give me a few more gb on internal sd. System is reduced to 2.2gb and cache to 500mb and the space is partitioned into the internal sd. Works just fine on 4.3 with any recovery and of course Perseus :D

If someone did say you needed to flash pit to properly upgrade that is indeed bull.
[Galaxy S 4 i9500 Original Android Development] truden:
Fail to boot

Hi everybody.

I've flashed countless ROMs and kernels and this is the first time a kernel failed to boot my devise (there is always first time) :laugh:

I'm with Galaxy S4 (i9500), Arrow 8.0 ROM and flashed the latest Perseus, downloaded from its official website.

On boot, the phone goes black (looks like it's off) and that's it.

Is it something known, or I'm the first to experience it?
[Galaxy S 4 i9500 Original Android Development] NoobieUser:
The latest perseus kernel only supports 4.3 roms not 4.2 roms :)

Flash an older version of perseus kernel to make it work.
[Galaxy S 4 i9500 Original Android Development] truden:
Thank you, [MENTION=5303860]NoobieUser[/MENTION] :)

I checked after your answer and I see that in the change log it says that the kernel is only for 4.3 upwards.

I think that the information about the kernel should be in the OP.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
You seem to have plenty of time and interest to whine and doing pointless rants.

The sound issues have no relation with the recovery as proven by the countless people still having it in Wanams thread, it has been an issue since July and you can look that up if you want.

You can continue spreading non-technical nonsense you deducted by your own flawed causation and correlation or you can indulge us by shutting the hell up.
[Galaxy S 4 i9500 Original Android Development] lukair1983:
The only time I had problems with audio (no audio, until a reboot) was with an old version of Perseus. It is not the case in probably like 7-10(or more) previous Perseus iterations.

Well you can believe it or not, but I'm telling you, all I did was what Andrei told me in pm, just to reiterate what he said in this thread some time ago. I did so, and I didn't have ONCE any sound issues for almost 2 weeks now, since I flashed Wanams.

And yes, I still have Philz recovery AND root AND Perseus, along with 4.3 Wanams Rom(3.2). I can provide you couple screenshots if you don't believe us, so maybe then you will loose your over-arrogant attitude over here.

Personaly... I was waiting patiently for weeks until I saw Andrei posting himself what to do (and I take his word over any other guy here, not that I'm his fan or anything... but obviously as we all know Andrei knows what he's doing/talking about in all instances). I followed his instructions to the letter (first asked him to confirm it), and it works flawlesly without any problems since. Others instead went ahead, and removed the bootloaders, did the "pit fixes", I even saw instructions 20+ steps long, telling people to flash a different rom PRIOR to flashing 4.3. That's most likely where the problems came, and why you and others have sound issues.

BTW I didn't do factory reset either (as Andrei confirmed is not needed). No problems with it either. Just saying, but you can believe what you want.
[Galaxy S 4 i9500 Original Android Development] cmd512:
Not worth the effort, he's already admitted he did a completely different process, which virtually negates any point to his nonsensical rants towards OUR PROVEN method. At the end of the day, our original point stays the same:

The simple 4 steps Andrei proposed is ALL that is needed to successfully upgrade to 4.3 + root from stock 4.2.2 and should be sticky-ed. None of these ridiculous factory reset / wipe / new pit / install stock ROM first / etc etc instructions should keep floating around, it is absolutely unnecessary.
[Galaxy S 4 i9500 Original Android Development] kenn7:
+1 on this..

i can confirm c.pit working extremely well with both crash 11 and arrow 9...
[Galaxy S 4 i9500 Original Android Development] cmd512:
Recommended? If we cared about what was recommended, we wouldn't be flashing ROMs in the first place. Bottom line: Andrei (the OP of this thread) provided a clear 4 step path to easy upgrade to 4.3 from 4.2.2 with his kernel Perseus (the point of this thread). Many have proven it to work with no issues. As have I.

What exactly is your point again?

Wait, was it, you wanted to let us know what is recommended? Ok, thanks, we don't care because we have a method that works just fine and is much easier. Or wait, was it your initial angry post towards lukair when you strongly disagreed with his claim that "Philz recovery works fine with 4.3"? Nope, wrong again, we're using it Philz just fine with 4.3 as well.

You happy? Have you gotten all of your useless points across now? Anything else to add?

I'm making a point here because there ARE bad instructions being posted everywhere on the 4.2.2 to 4.3 upgrade. In fact, I've put off upgrading to 4.3 for so long because I didn't want to mess with reinstalling all the Enterprise software I needed. When we went down the path of discussing this much easier upgrade, this halfwit decided to show up in this thread and go on a rampage about how our claims are false (feel free to look back to his initial foray against the "Philz recovery works fine with 4.3" claim).

There is NOTHING worse than false claims. So, let me be clear:

1) To successfully upgrade from 4.2.2 stock to 4.3 Wanamlite does NOT require a wipe.

2) To successfully upgrade from 4.2.2 stock to 4.3 Wanamlite does NOT require installing the stock 4.3 ROM first OR flashing any pit files if the non-wipe method is used.

3) To successfully root 4.3 only requires the install of Perseus after a non-wipe flash of 4.2.2. CF-root is not required.

4)

Philz recovery works perfectly fine on 4.3

if above steps are taken.

This is essentially what the halfwit has decided to take time to argue against. He has no point, cannot disprove any of it, end of story.
[Galaxy S 4 i9500 Original Android Development] wooptarik:
Thx for clarifying, Let's get over this already
[Galaxy S 4 i9500 Original Android Development] lukair1983:
Just finished my 3rd nandroid backup of 4.3 with Philz. Still works like charm :good:

Ok, back to the main topic of this thread, otherwise Andrei will kill us all :P
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
If somebody recommends you to jump off a bridge, will you do that too? Ever cross your mind Wanams recommendations are maybe wrong? Ever cross your mind how OTA updates don't wipe?

I suppose your answers to the above are yes, no and no.
[Galaxy S 4 i9500 Original Android Development] jujuburi:
If Wanam's recommendations are wrong, so could be yours. Bringing the bridge factor is childish. [MENTION=3562083]wanam[/MENTION]: Don't post false instructions in your topic. You are wrong. :p
[Galaxy S 4 i9500 Original Android Development] wooptarik:
Fyi, miui not compatible with perseus, ditching miui right away :p
[Galaxy S 4 i9500 Original Android Development] Towle:
Most of the argument - the parts that didn't contribute anything other than flaming - has been cleaned. Flaming other users in the forums is against the rules and is just not needed. It is disrespectful to the developers and takes up a lot of space in their threads. If you feel the need to argue a point, feel free to fight it out over a PM, just don't disrespect the rest of the community by making them scroll through it.

[MENTION=4167023]AndreiLux[/MENTION] let me know if you need anything else cleaned up.

Towle

Forum Moderator
[Galaxy S 4 i9500 Original Android Development] cmd512:
Gents, I'm seeing more frequent WiFi disconnects after going to 4.3 + Perseus 14.1, just checking in to see if you guys are seeing similar behavior.

(If not, I'll double check my router settings.)

UPDATE: No combination of router settings seemed to help, WiFi just kept disconnecting and reconnecting every few minutes. Found a thread on another forum regarding same issues on the Note 3 / 4.3, and toggling WiFi Power Save Mode OFF fixed the issue. After turning it off (Phone keypad -> *#0011# -> Menu key -> WiFi -> Power Save Mode OFF (default was ON), no more reconnects for over an hour already. If confirmed, looks to be 4.3 / not Perseus related, I'll keep monitoring and report back.

UPDATE #2: 3 hours later, not a single WiFi disconnect / reconnect, pretty sure the issue is addressed. That WiFi Power Save Mode is bad news and should be disabled. Disappointing Samsung didn't make it available in the advanced menu under WiFi.
[Galaxy S 4 i9500 Original Android Development] Degrated Shadow:
You are correct. actually very correct. but about recovery

you either need twrp 2.6.3.x or cwm 6.0.4.x.. i dont know why they include something in changelog that is fixed path for 4.3 or something like that.

This is the only reason 6.0.4.4 was recommended by me. even i am a fan of philz recovery but it isnt yet updated to 6.0.4.x so havent tried it.

I may be wrong or maybe have done some bad flashing which led me to no boot problem when using that recovery so i use 6.0.4.x just because it has updated few thing even though lacks some features.
[Galaxy S 4 i9500 Original Android Development] cmd512:
Thanks for the sensible feedback, but honestly, the latest Philz recovery for i9500 is working perfectly fine for many of us on 4.3 if you follow the no-wipe method suggested by Andrei / discussed here. Key here is we never reflash the recovery, only WanamLite ROM + Perseus... that's it. ROM boots fine, everything works perfectly, and system is rooted. In fact, I just rebooted into Philz recovery today and flashed some flip fonts for 4.3, no issues.

If you do a full wipe, repartition with a new pit, install stock ROM, etc first... and then try to flash the latest Philz recovery, all bets are off.
[Galaxy S 4 i9500 Original Android Development] skivnit:
Guys do you have sec-battery-monitor wakelock as well?

Sent from my GT-I9500
[Galaxy S 4 i9500 Original Android Development] jaidev.s:
Do u have any battery monitoring

apks like BBS installed in ur phone?
[Galaxy S 4 i9500 Original Android Development] skivnit:
I do have bbs but never gave me this wakelock until i updated to 4.3

Sent from my GT-I9500
[Galaxy S 4 i9500 Original Android Development] mw86:
+1

Worked perfect for me thanks CMD512. I was having inconsistent performance on wifi as well and no longer. THANKS!
[Galaxy S 4 i9500 Original Android Development] cmd512:
Cheers, doesn't seem to have any negative impact on battery life so far. In fact, I was having more Wi-Fi related wakelocks with it ON, so battery life has settled down.

I'll be enabling it with subsequent new ROMs in hopes Samsung fixes it, they clearly intended it to be defaulted ON.

(Apologies to Andrei for initiating this discussion in his dev thread, couldn't be sure at first given the new WiFi drivers. I hope it helps other Perseus users.)
[Galaxy S 4 i9500 Original Android Development] lukair1983:
Would you guys mind telling (if you know), what this "Power saving" feature is all about, and most importantly what is it's purpose? From the name of it, it would indicate it is something benefitial, so there must be (in theory) some negative effects of setting it off.
[Galaxy S 4 i9500 Original Android Development] cmd512:
No idea, something newly implemented by Samsung for 4.3 I would assume. Exact same setup on 4.2.2 saw zero issues with my router, but after upgrading to 4.3, WiFi would not stay connected.

Power save stuff for WiFi will probably bring additional signal power, scan interval, etc controls. Properly implemented, it shouldn't impact WiFi performance with some battery gains. Poorly implemented, your WiFi performance goes to crap, which I assume is what we're seeing. Interesting as when I was researching solutions, tons of posts in the past few days about Verizon / AT&T pulling their 4.3 updates "due to WiFi issues."
[Galaxy S 4 i9500 Original Android Development] lukair1983:
Well, I did some quick testing, and I get a 1% drop every 7 minute, with screen turned on, and wifi turned on and connected.

When I switched power saving off, I got 5 minute, for the same 1% battery drop. That's almost 30% difference, so I would suggest to anybody who doesn't need it off, to keep it on. I don't have such issues so I can leave it on (lucky me :] ).
[Galaxy S 4 i9500 Original Android Development] cmd512:
Agreed, if you're not having WiFi issues, best to leave it on.

UPDATE, may have found the issue: My router WiFi was set to 40 MHz channel width with sideband set to Upper. JB 4.2.2 had no issues with my router with these settings, but JB 4.3 + WiFi Power Save Mode simply does not like this. Since switching to 20 MHz channel width, no more disconnects even with Power Save Mode ON.

Could be the extra range you get with 20 MHz channel width, but this may explain the WiFi issues people are seeing with 4.3, probably something Samsung needs to fix.
[Galaxy S 4 i9500 Original Android Development] alawadhi3000:
I have a router running Tomato firmware, the WIFI is set to 40MHz channel as well, can't try 20MHz since I need 300Mbps throughput.

The S4 connects and reconnects a lot, and I get lots of WIFI related wakelocks, basically my phone stays awake like %75 of the time with WIFI on. :cyclops:

I'm going to try turning the WIFI power saving off, thanks cmd512.
[Galaxy S 4 i9500 Original Android Development] mw86:
That's what I had. Except I never lost the connection according to the phone just had no data transfering for long periods in between and would seem to catch up. Almost like a glitched form of fast dormancy. Been more consistent power saving off. Agreed if no issue on leave it. Sorry Andrei for offtopic. I also noticed it had a tendency to make my isp perhaps kick the connection off perhaps the power save feature was causing some erratic drain/impact on their network. An ota update may fix it eventually.

I think my wifi is on 20mhz so that may or may not be related.
[Galaxy S 4 i9500 Original Android Development] cmd512:
Interesting, I'm running Tomato as well. 20MHz for sure resolves the issues though, zero reconnects afterwards.
[Galaxy S 4 i9500 Original Android Development] tabish84:
There is a little lag while using the xda application but when I installed wanam 3.5 lag was gone but that made my phone hot so I switched back to perseus. Can u do something about the lag? Great work by the way
[Galaxy S 4 i9500 Original Android Development] wooptarik:
Priceless info. Thanks a bunch mate
[Galaxy S 4 i9500 Original Android Development] mw86:
Lag is a term can mean different things to some people. Try raising cpu mhz in qos maybe the touch screen option... other than that nothing to improve and nothing really different in perseus to cause you lag.
[Galaxy S 4 i9500 Original Android Development] mw86:
Thanks for the update to Synapse Andrei. I didn't see a change log. Keep up the great work.
[Galaxy S 4 i9500 Original Android Development] bala_gamer:
I can feel my screen heating up after 10 to 15 mins of continuous screen on time, it was not like that before. THe only change i made on the customization part is uv cpu to -75 mv and oc gpu to 640 mhz, any opinion?
[Galaxy S 4 i9500 Original Android Development] core720:
the latest version does not support stweaks?
[Galaxy S 4 i9500 Original Android Development] hotheabilly:
Duuuuuuude pls.

Use synapse from playstore

kitkatted ???
[Galaxy S 4 i9500 Original Android Development] kdh2834:
There is a application called "Synapse" which can be downloaded from the playstore and the fuctions are almost same as stweaks. Stweaks doesnt work with perseus as Andrei has given support to only Synapse.

U can easily read a few pages back and get your answer. This question has been asked many times.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Just a minor update for other another dev (Changed button actions to not be executed at boot). I keep the sources updated regardless of change log though so you can check there if really curious.

I'll do a minor update in a few days to the kernel because this thing / bug with Synapse not installing itself on boot is a bit annoying.
[Galaxy S 4 i9500 Original Android Development] core720:
Install Last kernel and alternatives freeze and reboots

Enviado desde mi GT-I9500 mediante Tapatalk
[Galaxy S 4 i9500 Original Android Development] cmd512:
Given you've shown a propensity of not being able to read basic instructions in your initial posts about STweak, let me guess: You flashed the latest kernel on a 4.2.2 ROM?
[Galaxy S 4 i9500 Original Android Development] Socotroco:
cmd512, what you have found is what was causing my WiFi to disconnect every few minutes. After making this small adjustement to the router I haven't had any disconnection for the last 3 days. I didn't touch any of the WiFi configuration on the phone, only in the router.

THANK YOU!

Regards.
[Galaxy S 4 i9500 Original Android Development] cmd512:
You're very welcome. Question though: Are you using Perseus kernel as well? I'm starting to wonder if the new Wifi drivers in 14.1 may be the culprit as I had no issues with 4.2.2 + Perseus 12.x and another user said he resolved his Wifi issues after flashing a different kernel.

This issue is very easily reproduced, so I'll try to grab a log for Andrei when I get home next week from Thanksgiving break.