Related
06-19-2011
The above has a max clock of 1.6ghz.. It has all the regular features included prior to this release - underclocking when it gets too hot.. various non-cpu overclocks and so on.. and unlike previous kernels.. its pretty damn stable.. I've tried to crash it. I can't.. Help me crash it. Don't help me crash it if you're on 3.1 - because this won't work with 3.1.. Ok? alright then.
#older stuff below
This lovely little kernel has a max of 1.646 (because 1.7ghz will run for about 30 seconds). But it also has been setup to set the max clock to 1.2ghz (temporarily) when temps get above 42 deg C.. For people using setcpu, I do not know if it sets only cpu0 to the desired freq (and presumes cpu1 will follow).. but it seems that you need to set both to the desired freq, otherwise it'll use the higher of scaling_max_freqs (cpu0,cpu1 - thus two scaling_max_freqs) and ignore the value you just set.. doesn't make sense? yeah.. ok..
if you set cpu0 to 1504
then you set cpu1 to 1504
then you set cpu0 to 1000
... scaling_max_freq is set to 1000 for cpu0, yet cpuinfo_cur_freq will show higher than that (under load obviously)..
just based on my experience.
Just because the max is 1646... doesn't mean you should complain when/if its unstable.. Well, you can.. but you really don't have to.
This is for 3.01.. Im not sure I trust 3.1 yet. ..
Here.. this has sys/avp/vde/gpu/pclk and of course cpu, overclocked. I ls'd the modules directory for you and got this..
bcm4329.ko cifs.ko ntfs.ko scsi_wait_scan.ko tun.ko
I don't know what it means.
If you have problems with netarchy's kernel and you don't with this.. You're probably insane and making stuff up...
This not my first compile. I run my own custom kernels on Gtab, xoom, G2, and HD2.. All pretty spicy with the overclocks..
This may cause some incontinence.. only some.. its ok tho. perfectly natural.
this is the first time I've posted any kerzanels..
http://www.github.com/ibladesi/
get your ultra verbose changelog there buster.
order
order
order
Omg this **** is smoking hot
Sent From My Evo
I'll give it a go.
Right after I nandroid.
And flash the new CWM >_>
Have you got a link to your source code ?
DAMN!!!! very nice
would love to see some benchmarks and improvements reviews
Well, I flashed this on my TF earlier today (running Prime 1.3r2)
I got Linpack scores of 63.3+ and a first run Quadrant of 4339. However, my device froze 3 times within half an hour of flashing it. I cleared the cache several times pre and post flashing. My device even froze on the initial boot after flashing the kernel, so I guess it isn't a thing of speed instability. There must be something else. I will try to reflash it later and see if this behavior continues.
egzthunder1 said:
Well, I flashed this on my TF earlier today (running Prime 1.3r2)
I got Linpack scores of 63.3+ and a first run Quadrant of 4339. However, my device froze 3 times within half an hour of flashing it. I cleared the cache several times pre and post flashing. My device even froze on the initial boot after flashing the kernel, so I guess it isn't a thing of speed instability. There must be something else. I will try to reflash it later and see if this behavior continues.
Click to expand...
Click to collapse
Not really. The init.ventana.rc script within the ramdisk sets the max frequency to 1.4 - so if there were freezes in android, there could be freezes when android starts to boot - roughly around the time adbd starts... Are there any kernel logs (ramdump files on your internal "sd")
Strange how it would run thru benchmarks, yet be unstable. Was this at 1.504?
Blades said:
Not really. The init.ventana.rc script within the ramdisk sets the max frequency to 1.4 - so if there were freezes in android, there could be freezes when android starts to boot - roughly around the time adbd starts... Are there any kernel logs (ramdump files on your internal "sd")
Strange how it would run thru benchmarks, yet be unstable. Was this at 1.504?
Click to expand...
Click to collapse
Yup, I set it at 1.504 and it allowed me to run Linpack a few times before crashing. Quadrant allowed me to go 1 full run and about 1/3 of the next before it crashed. I found a ramdump.log file in there. Is this the one you need?
@Blades,
Here you go...
Definitely will try this after work today! thanks for the new kernel!
HTC Thunderbolt & ASUS Transformer Rooted!
wow, what a crazy kernel
Thanks I'm going to give this a go with the modaco rom
Is there a way we can schedule the 1.5ghz to kick in? seems like it crashes few minutes after boot because some other app are still loading. I've set my setcpu to 1ghz max and reboot, everything loads perfectly then after 5 minutes i revert it back to 1.5ghzl, overnight my TF doesnt have any problem.
This morning i restarted my asus just to experiment if it will boot normaly while im in 1.5ghz max and 200+mhz min. It crashes few minutes after reboot.
45 minutes of Pocket Legends and no signs of slowing down at 1.5GHz!
Sent from my Transformer TF101 using XDA Premium App
@hurrpancakes: Pls try 1080p mp4 high bit rate, hope that it'll stable as well
kenblat said:
@hurrpancakes: Pls try 1080p mp4 high bit rate, hope that it'll stable as well
Click to expand...
Click to collapse
I believe high profile HD video performance is more an issue of HC 3.0 not taking full advantage of Trega2 hardware acceleration and until HC 3.1 we won't see much improvement. Overclocking will only help so much...
plz delete
new kirnizial up
Blades said:
new kirnizial up
Click to expand...
Click to collapse
Reserve 128mb of ram insted 256mb. You mean now we have more user ram avaiable for app?
Just a quick question for you guys: I recently purchased an Infuse from the marketplace here, and so far I've gotten an absolute TON of lag using the device. I've flashed Infused 1.5 and Bionix with the Infusion kernel, and so far the lag has gotten better, but it's not totally cleared up. I'm definitely not new to Android, but I haven't seen anything like this before. I know that Quadrant isn't a reliable benchmark, but I'm scoring about 1900, OCed to 1.5Ghz.
Just to give an example: I'm using desktop visualizer to add some custom icons to my screen. When I go to select an icon image, it's fine, but it freezes for about 90 seconds when a list of my apps comes up.
Anyone experience this before? And if so, how did you solve it? If this was widespread, I'd imagine there would be complaints all over here.
Which app are you using to set your overclock settings, how many clock speeds do you have enabled, are you under or over volting, and *which governor* are you running?
I have seen some similar problems here when I was using conservative governor with poor choices of clock speed. Right now Infusion 1.5.2 kernel has some issues with not liking the ondemand governor, so I reduced my number of available clock speeds so it would jump to the top more quickly while using the conservative governor.
Also, did you use either the return to stock, or the ultimate unbrick flash before you flashed your ROM? If it was a used Infuse, I would do one of the above before I start looking anywhere else, then reflash your rom/kernel of choice.
I'm using SetCPU with the OnDemand gov (400/1500), no undervolting. I have a profile set to underclock it to 300/700 on conservative when I'm charging, but that's about it.
I think I'm going to use GTG's unbrick/return to stock and root the thing myself, I figured I'd ask before I did anything drastic. My UI is a ***** to set up every time, and I hate wiping because of it.
Just a quick note, I've had some serious lag using the oc kernel... Like real world usage got worse after oc'ing
Sent from my SAMSUNG-SGH-I997 using XDA App
Although it is counter intuitive to the way governors should work I have seen less lag on Infusion 1.5.2 when I use conservative. The ondemand governor seems to be having some issues with the most recent update. If you flash back to 1.0 Infusion you get a max overclock of 1.4, but it is much more stable IMHO. Also FFC is presently broken in 1.5.2 and will hard freeze the phone (battery pull).
I'm debating flashing back to community kernel, but I am going to wait and see how long it takes my battery to drain because I am using some undervolting. You might try using conservative governor and only enable 100, 400, (800 or 1000), (1200 or 1300) and 1500. Honestly the infuse is my first smartphone, but I've tinkered with desktop hardware the last 15 years. It literally amazes me everytime I pull the battery out of this phone and feel how light it is.
I also used the desktop vis app and yes it lagged when chosing apps however it seemed to get better after three or four times but that seems to be the only place it lags for me im using the oc-uv kernal 1.0 clocked to 1.4 seems bulletproof compared to later versions im getting great speed and batt life with this kernal but i had the same lag in the same event as you
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
I'm going to try bringing it back to stock and re-rooting it myself, if only because I trust myself with adb//scripts/rooting, and I'm hesitant to trust someone I don't know. Lag has gotten a lot better since switching to conservative, OCing to 1.6 and undervolting a tad, but it still lags when opening apps or scrolling through long lists. Desktop Vis is of course, still a nightmare.
Oh well, I'll report my findings tomorrow I guess. Hopefully I'll be scoring higher than the 1700 I just pulled in quadrant.
entropism said:
I'm going to try bringing it back to stock and re-rooting it myself, if only because I trust myself with adb//scripts/rooting, and I'm hesitant to trust someone I don't know. Lag has gotten a lot better since switching to conservative, OCing to 1.6 and undervolting a tad, but it still lags when opening apps or scrolling through long lists. Desktop Vis is of course, still a nightmare.
Oh well, I'll report my findings tomorrow I guess. Hopefully I'll be scoring higher than the 1700 I just pulled in quadrant.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I997 using XDA App
Do you use spareparts?
usually yes, but I dont believe I installed it yet on the infuse. Why?
lag on stock also
I'm 100% stock & get lag also. Definitely in the situation you describe, when the app list comes up for adding shortcuts to any homescreen. Takes forever for that list to come up. Secondly, simply from running for a while, i have to kill all the apps using the built in task manager in order to get it to run smoothly again. It's like it never closes an app. I'm new to android, but guessing this is a problem inherit to android. Can't see how samsung or at&t could have screwed this soo badly to cause it to never close an app. Hoping memory management is better in Gingerbread.
Blario, you're new to Android, so you need to read up on how memory management works with Android. It's not SUPPOSED to kill apps, and that's not what's lagging your phone. In your case, I'd think it was more of a case of WHICH apps you were running.
yeah, the longer I have the phone the more it lags it seems
probably going to push me towards the Evo3D
If you're on stock and after a week or two your phone gets slow as hell (mine did), install a Voodoo lagfix kernel. All the current ROMs include it.
superweapons said:
If you're on stock and after a week or two your phone gets slow as hell (mine did), install a Voodoo lagfix kernel. All the current ROMs include it.
Click to expand...
Click to collapse
I did
I still have random slow downs when it gets bogged down with stuff
I'd give a left nut to have this phone with dual core
entropism said:
Blario, you're new to Android, so you need to read up on how memory management works with Android. It's not SUPPOSED to kill apps, and that's not what's lagging your phone. In your case, I'd think it was more of a case of WHICH apps you were running.
Click to expand...
Click to collapse
I don't do much. Twitter, "Web" (some mozilla stock ish), SMS, phone, Android Market app (browsing), and Maps. I've had it lag up using only those. Far less often, I use Yelp... that's about it.
Not supposed to kill apps? When I kill them it fixes the problem. Maybe it *should* be killing apps?? If its supposed to flush their state to disk... it seems to be doing a poor job at it.
I would be suspicious of your microSD card (if you have one). Do you know what class it is? Have you tried removing it and performing the same functions in which you see lag?
hydrogenman said:
I did
I still have random slow downs when it gets bogged down with stuff
I'd give a left nut to have this phone with dual core
Click to expand...
Click to collapse
I'd more readily assume the 512MB RAM is the issue. Looking forward to SGSII
SolusCado said:
I would be suspicious of your microSD card (if you have one). Do you know what class it is? Have you tried removing it and performing the same functions in which you see lag?
Click to expand...
Click to collapse
It's the stock card that came with the phone. Any way to check? The apps are installed to it... so removing it I wouldn't have the apps available anymore.
A little update: I returned back to stock and re-rooted. I installed 3E, then CWM, then threw on Infused 1.5 and Infusion, OCed to 1.6Ghz and slightly undervolted (about 25-100mv along the range) using SetCPU.
As of right now, it still lags on occasion, but not as bad as it did. Quadrant is giving me a whopping 1300 average score, with a low of 800 and a high of 1600. This is just pathetic.
i experience alot of lags and hangs in menu. how can this be fixed. i just bought it and i wanna throw it away!?
hard reseted it.....and the problem appears again afer 1 day of usa. soft reset works well for 1-2 hours then the same!
shi**y phone!
just upgrade to 2.3.4 , i think this will clear ur problem...
We would use lagfix if the devs made it
Sent from my GT-I9001 using XDA App
gangstar said:
i experience alot of lags and hangs in menu. how can this be fixed. i just bought it and i wanna throw it away!?
hard reseted it.....and the problem appears again afer 1 day of usa. soft reset works well for 1-2 hours then the same!
shi**y phone!
Click to expand...
Click to collapse
You realy have 2 options :
1. Go to warranty with it (if you have one)
2. If you don't have warranty just flash android 2.3.4 and I assure you that this will be fixed
larry200ro said:
You realy have 2 options :
2. If you don't have warranty just flash android 2.3.4 and I assure you that this will be fixed
Click to expand...
Click to collapse
Bulls**t.
From the 5 SGS+ users I know, every single one of them (including me) has the sceen/menu lag problem, and we all have different Android versions, 2.3.3, 2.3.4, not to mention different branding.
I contacted Samsung and they can't (or won't) fix it.
Mikolak28 said:
Bulls**t.
From the 5 SGS+ users I know, every single one of them (including me) has the sceen/menu lag problem, and we all have different Android versions, 2.3.3, 2.3.4, not to mention different branding.
I contacted Samsung and they can't (or won't) fix it.
Click to expand...
Click to collapse
can you describe what do you mean by screen/menu lag?
Mikolak28 said:
Bulls**t.
From the 5 SGS+ users I know, every single one of them (including me) has the sceen/menu lag problem, and we all have different Android versions, 2.3.3, 2.3.4, not to mention different branding.
I contacted Samsung and they can't (or won't) fix it.
Click to expand...
Click to collapse
All using TWLauncher? Have you tried another launchers (GO Launcher EX runs smoothly in my phone)?
Mikolak28 said:
Bulls**t.
From the 5 SGS+ users I know, every single one of them (including me) has the sceen/menu lag problem, and we all have different Android versions, 2.3.3, 2.3.4, not to mention different branding.
I contacted Samsung and they can't (or won't) fix it.
Click to expand...
Click to collapse
A reason might be a underclock of the processor in order to increase the battery life. You might want to install ROM Toolbox and check at what frequency is the processor working (the device will need to be rooted)
You can also check if the processor is getting hot >43 degrees(battery booster on the market can help you with that)
Please reply with response and if my post helped press on thanks
I tried using different launchers - didn't help.
As to the processor frequency thing - it might very well be the case, since the screen wakes up instantly when I'm listening to music (so using more processor power).
I'll check that out as soon as I figure out how to flash 2.3.4
Mikolak28 said:
I tried using different launchers - didn't help.
As to the processor frequency thing - it might very well be the case, since the screen wakes up instantly when I'm listening to music (so using more processor power).
I'll check that out as soon as I figure out how to flash 2.3.4
Click to expand...
Click to collapse
I'l advise you on how to flash it...give me a PM when you are available
2.3.4 not yet available ota
After Upgrading to 2.3.4 rooting and removing twlauncher I have no lag problems any more, ADW, Launcher Pro and Zeam are all working just fine. I know of others that have upgraded to 2.3.4 and still have a 2s lag when waking the phone so IMHO removing twlauncher may be key....
Yeah, but by removing TW, won't Kies stop working?
ETA:
After rooting my phone and installing CPU Master, I can honestly say it is, as mentioned before, because of the CPU.
It's usually down to 250mhz ondemand when sleeping, and when i bumped it up to 800 performance, it instantly turned on, no delay.
Well I personally don't see the need for Kies apart from providing the USB drivers so that doesn't really bother me...... but if you were a big Kies user then I guess that would be a show stopper .....
Mikolak28 said:
Yeah, but by removing TW, won't Kies stop working?
ETA:
After rooting my phone and installing CPU Master, I can honestly say it is, as mentioned before, because of the CPU.
It's usually down to 250mhz ondemand when sleeping, and when i bumped it up to 800 performance, it instantly turned on, no delay.
Click to expand...
Click to collapse
Personally I didn't remove TWLAUNCHER but just froze it(in case I need it later). I also made a backup with it and installed go launcher. I am very satisfied.
Edit : application is Titanium Backup (I think the best application there is for android)
I did what you said, and it still hasn't changed the screen sleep lag.
It might be a tad bit quicker, but not a lot.
This is a duplicate thread with http://forum.xda-developers.com/showthread.php?t=1284850
Basically there is nothing you can do except increase your cpu frequency which will decrease (drastically) your battery life.
I'm afraid that I can't agree with it being a CPU frequency scaling issue. My CPU frequency is also going down to 245Mhz on no or low demand and I have no lag...
igor_999 said:
I'm afraid that I can't agree with it being a CPU frequency scaling issue. My CPU frequency is also going down to 245Mhz on no or low demand and I have no lag...
Click to expand...
Click to collapse
Mikolas is refering to the delay the phone has when trying to unlock it. It takes about 2.5 seconds for the screen to turn on.
I also have no lag when waking up the phone .... after pressing home or power I get the lock screen in under a second. BTW if I monitor the current CPU frequency with setCPU then I can see it scale the frequency down to 245 while the screen ist still on and experience no lags when resuming phone use ..... if your experiencing lags of 2.5s then IMHO it must have another cause.
Sorry being a new member I could not reply directly to this thread under developers but I wanted to let people know that this rom should be avoided. The default clockspeed is downgraded from 1.5ghz to 1.2ghz with this and even when overlocked back to 1.5ghz it's still not as fast as before. Linpack hardly even hits 150 now when before was around 200. Quardrant scores is also very low now, the memory and IO scores were significantly lower than before.
As for those who are having the wifi issue, i discovered that the problems started happening after the one click root. Right before I rooted this new rom i was able to connect to my wifi just fine, after the root it started having problems connecting.
gtung99 said:
Sorry being a new member I could not reply directly to this thread under developers but I wanted to let people know that this rom should be avoided. The default clockspeed is downgraded from 1.5ghz to 1.2ghz with this and even when overlocked back to 1.5ghz it's still not as fast as before. Linpack hardly even hits 150 now when before was around 200. Quardrant scores is also very low now, the memory and IO scores were significantly lower than before.
As for those who are having the wifi issue, i discovered that the problems started happening after the one click root. Right before I rooted this new rom i was able to connect to my wifi just fine, after the root it started having problems connecting.
Click to expand...
Click to collapse
What proof do you have of this? I don't see any difference in performance. I guess I'll just wait for the next update.
Sent from my HTC One X using Tapatalk 2
gtung99 said:
Sorry being a new member I could not reply directly to this thread under developers but I wanted to let people know that this rom should be avoided. The default clockspeed is downgraded from 1.5ghz to 1.2ghz with this and even when overlocked back to 1.5ghz it's still not as fast as before. Linpack hardly even hits 150 now when before was around 200. Quardrant scores is also very low now, the memory and IO scores were significantly lower than before.
As for those who are having the wifi issue, i discovered that the problems started happening after the one click root. Right before I rooted this new rom i was able to connect to my wifi just fine, after the root it started having problems connecting.
Click to expand...
Click to collapse
Wowsers! That's good to know. I haven't updated yet as I'm on Rogers, but I'll keep that in mind when a Rogers version comes around.
As for the WiFi issue, I've had it the whole time. I went 9 days before rooting, and it's been maybe 15 days since I rooted. It existed pre- and post-root for me.
mobilehavoc said:
What proof do you have of this? I don't see any difference in performance. I guess I'll just wait for the next update.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Mine seems to be running at 1.5ghz fine. I'm on the new version. I smell FUD.
Sent from my HTC One X using Tapatalk 2
same as above, no issues here.
Also have the update no issues
Sent from my HTC One X using Tapatalk 2
I went from the full detox to 1.82 and after start up i ran both quadrant and antutu benchmarks. I noticed that quadrant score was only 4k when it used to be 4.5k. antutu was also lower and thats when I noticed the clock speed being listed at 1243 mhz (something around there). I downloaded the antutu cpu master free and it allowed me to move the slider back up to 1512 mhz.
Only sharing what I expierenced, now i'm trying to go back to 1.73 and having trouble...seems like it doesn't want me to move back down.
gtung99 said:
Sorry being a new member I could not reply directly to this thread under developers but I wanted to let people know that this rom should be avoided. The default clockspeed is downgraded from 1.5ghz to 1.2ghz with this and even when overlocked back to 1.5ghz it's still not as fast as before. Linpack hardly even hits 150 now when before was around 200. Quardrant scores is also very low now, the memory and IO scores were significantly lower than before.
As for those who are having the wifi issue, i discovered that the problems started happening after the one click root. Right before I rooted this new rom i was able to connect to my wifi just fine, after the root it started having problems connecting.
Click to expand...
Click to collapse
Ok, im curious, what program is reporting to you that your clockspeed is 1.2? Im not doubting what you are saying....at least not completely. I ask because when i was researching the phone before it was released on ATT, i was reading reviews and reports of people benchmarking the ATT demo phones and how the clock speed was 1.2 compared to the 1.5 of the tegra 3. So, im curious if its maybe just that the actual app you are using is reporting it wrong OR, if this is even possible, that maybe there is a different kernel with the clock set differently that somehow slipped through the cracks.
I have done the update already, and all my benchmarks are almost identical to what they were before and my clock speed is still 1512 as it was before.
As far as the wifi issue, most people were reporting that issue before root was even possible on this phone so to point there as being the culprit cant be right.
cloudraker said:
Ok, im curious, what program is reporting to you that your clockspeed is 1.2? Im not doubting what you are saying....at least not completely. I ask because when i was researching the phone before it was released on ATT, i was reading reviews and reports of people benchmarking the ATT demo phones and how the clock speed was 1.2 compared to the 1.5 of the tegra 3. So, im curious if its maybe just that the actual app you are using is reporting it wrong OR, if this is even possible, that maybe there is a different kernel with the clock set differently that somehow slipped through the cracks.
I have done the update already, and all my benchmarks are almost identical to what they were before and my clock speed is still 1512 as it was before.
As far as the wifi issue, most people were reporting that issue before root was even possible on this phone so to point there as being the culprit cant be right.
Click to expand...
Click to collapse
Antutu benchmark listed it at 1.2ghz. Previously it was at 1.5ghz on 1.73. I was stupid and tried to run full detox after the upgrade and root and got some kind of error saying memory full. Now the phone is soft bricked. I just tried the stock 1.73 RUU and its giving me a boot 140 error saying bootloader mismatch.
Any ideas?
gtung99 said:
Antutu benchmark listed it at 1.2ghz. Previously it was at 1.5ghz on 1.73. I was stupid and tried to run full detox after the upgrade and root and got some kind of error saying memory full. Now the phone is soft bricked. I just tried the stock 1.73 RUU and its giving me a boot 140 error saying bootloader mismatch.
Any ideas?
Click to expand...
Click to collapse
Im guessing that like the only other HTC phone ive owned, downgrading wont happen without s-off. So the only thing i can suggest is to instead try going back to 1.82 and get the phone functional so at least its not a brick and if its still showing an incorrect clock speed maybe you can get an exchange.
gtung99 said:
Antutu benchmark listed it at 1.2ghz. Previously it was at 1.5ghz on 1.73. I was stupid and tried to run full detox after the upgrade and root and got some kind of error saying memory full. Now the phone is soft bricked. I just tried the stock 1.73 RUU and its giving me a boot 140 error saying bootloader mismatch.
Any ideas?
Click to expand...
Click to collapse
Yea you can't go back down.Have to wait for the official ota and see if its any different.
My phone runs much smoother with the new update...almost like a different phone. I could care less what the benchmarks say...I'm a real world guy.
Sent from my HTC One X using Tapatalk 2
I was lucking, using the 1.82 RUU again I reflashed it and now the phone is back up and running. Running antutu I see the clock speed is now defaulted to 1.5ghz again.
I really don't know what screwed up with my clockspeed before, but hopefully this will work nicely now.
1.73 here...
5,013 -- Quadrant Standard
So perhaps something is just wrong with you're phone. Also, I thought you couldn't modify your clock speed without unlocked bootloader + root/s-off or whatever. I know the basics, Just not the full technical explanation of it all. Sounds to me like you have a problem though from the beginning to have <5K of a quadrant score.
Just removed everything I dont need. De-oxed and removed bloatware + added a couple games. Cleared "multi-tasker" and used task manager [not the stock] widget to free up memory... Which made it go to 4,760. So doing all this stuff to "help" somewhat backfired. Im wondering if its the task manager widget/app always running :b Idk. Point is, I think its your phone. Even if i'm not at 1.8~.
gtung99 said:
I was lucking, using the 1.82 RUU again I reflashed it and now the phone is back up and running. Running antutu I see the clock speed is now defaulted to 1.5ghz again.
I really don't know what screwed up with my clockspeed before, but hopefully this will work nicely now.
Click to expand...
Click to collapse
good to know. and FYI, though it's not my forte, i was reading either the "Update 1.82" thread or the thread with the title named the same as the 1.82 patch (can't recall which one) and I remember someone mentioning that to roll back to 1.72 after upgrading, you need to edit a certain .apk file, which, if done improperly, will totally brick the device. glad you were able to get 1.82 to run properly. I've decided to wait for the full OTA from ATT since my wi-fi issues are generally minimal.
Scores are lower on the 1.82 but same clockspeed I'm fairly certain. Dont know why. Quadrant drops about 500 points. Still seems faster.
ThisWasATriumph said:
Scores are lower on the 1.82 but same clockspeed I'm fairly certain. Dont know why. Quadrant drops about 500 points. Still seems faster.
Click to expand...
Click to collapse
The IO score is lower now. Can't wait until Franco or someone else releases some kernels that will really make this phone rock. I had a galaxy nexus before with the stock rom but running Franco latest kernel that boosted the Quadrant score from 2200 to 3600. Mostly it was due to enhancements that dramaticlly increased memory and IO performance.
I installed the leaked update and my wifi still doesn't work right. It is extremely slow and crashes my entire network and brings it to its knees. Wifi will not work on a single device when my one x is connected to my wifi network. Ideas? Has anyone else experience this?
I hadn't thought of this being the cause but I have noticed that my wifi at home, specially when watching netflix is way slow. I always have my wifi on my HOX turned on when at home. I'm on 1.82 and running Clean ROM 2.3. Are you saying that this could be causing my slowness on all my devices that are also hooked into my wifi at home?
To keep Andrei from going crazy with non-development related questions, I've opened the following thread. That way we keep the development thread for development topics and this for general discussion.
Good deal.
First feature request: Fading in/out LEDs! I've pinged the dev for LightFlow, and while he can implement it on a software level, it would be supremely inefficient and probably drain the battery like crazy.
cmd512 said:
Good deal.
First feature request: Fading in/out LEDs! I've pinged the dev for LightFlow, and while he can implement it on a software level, it would be supremely inefficient and probably drain the battery like crazy.
Click to expand...
Click to collapse
Actually that's something which belongs in the dev thread. If anything you can just post on the issue tracker on Github, I've grown vary of XDA.
There's a new TI LED controller so I can't port the old Philips controls from the old phones. I'll rewrite it eventually but I got other things to do now.
AndreiLux said:
Actually that's something which belongs in the dev thread. If anything you can just post on the issue tracker on Github, I've grown vary of XDA.
There's a new TI LED controller so I can't port the old Philips controls from the old phones. I'll rewrite it eventually but I got other things to do now.
Click to expand...
Click to collapse
Done, posted on Github!
just got my s4 one day ago. rooted immediately, flashed omega7.0 and the latest perseus. did not touch anything on the u/v in stweak. no o/c as well. but the antutu score is so low 21000+, i thought it at least supposed to be 27000+?
i tried adam kernel, had the same result. is that normal? did i miss anything?
astoncheah said:
just got my s4 one day ago. rooted immediately, flashed omega7.0 and the latest perseus. did not touch anything on the u/v in stweak. no o/c as well. but the antutu score is so low 21000+, i thought it at least supposed to be 27000+?
i tried adam kernel, had the same result. is that normal? did i miss anything?
Click to expand...
Click to collapse
Congrats, you win the award for the first post about useless benchmark scores in this thread.
cmd512 said:
Congrats, you win the award for the first post about useless benchmark scores in this thread.
Click to expand...
Click to collapse
thanks for you response. as i mentioned i got it only one day, without touching anything on u/v & o/c. i guess this is considered lower score than the stock one? i merely care about bench mark, i just want to know is this normal? or i need few days to let it settle down? fyi, i tried more than 10 times and it only score between 20k-21k. perhaps you can be kind enough to give me some idea rather than congrats me.
astoncheah said:
thanks for you response. as i mentioned i got it only one day, without touching anything on u/v & o/c. i guess this is considered lower score than the stock one? i merely care about bench mark, i just want to know is this normal? or i need few days to let it settle down? fyi, i tried more than 10 times and it only score between 20k-21k. perhaps you can be kind enough to give me some idea rather than congrats me.
Click to expand...
Click to collapse
It is normal for benchmark to be lower than on stock kernel all devices differ. Following the development of this kernel it has been stated that the kernel is not intended for high benchmarks but more for overall stability, smoothness and better battery life.
Benchmarks is just a number and a high benchmark does not always mean your phone is smooth and performs very well under normal user conditions.
Hope this answers your question and should I be mistaken about anything anyone welcome to rectify me on those points.
Sent from my GT-I9500 using Tapatalk 2
xtacy1 said:
It is normal for benchmark to be lower than on stock kernel all devices differ. Following the development of this kernel it has been stated that the kernel is not intended for high benchmarks but more for overall stability, smoothness and better battery life.
Benchmarks is just a number and a high benchmark does not always mean your phone is smooth and performs very well under normal user conditions.
Hope this answers your question and should I be mistaken about anything anyone welcome to rectify me on those points.
Sent from my GT-I9500 using Tapatalk 2
Click to expand...
Click to collapse
i never meant that perseus is running low on benchmark, in fact, it's the highest between chainfire's cfroot, wanam's adam. i tried all these 3 kernel, all score only between 19k-21k. i just wonder if i have accidentally limited my cpu speed? i will do a factory reset and re-test it.
again, i dont or merely care about benchmark, i just care if my s4 is running normally.
astoncheah said:
i never meant that perseus is running low on benchmark, in fact, it's the highest between chainfire's cfroot, wanam's adam. i tried all these 3 kernel, all score only between 19k-21k. i just wonder if i have accidentally limited my cpu speed? i will do a factory reset and re-test it.
again, i dont or merely care about benchmark, i just care if my s4 is running normally.
Click to expand...
Click to collapse
I have kanged Andrei's response with respect to benchmarks.
Originally Posted by AndreiLux
Samsung cheats during benchmarks by enabling a thermal boost mode which raises the throttling temps by 10°C (90° -> 100°C). I disabled the permissions to this. Practical effects is things like Antutu will give lower scores. This is more realistic of actual performance and I will leave it as such. Benchmark freaks can enable the boost mode manually: /sys/class/thermal/thermal_zone0/boost_mode .
The first throttling speed is 1400MHz and that's why it spends a lot of time there during benchmarking.
Effectively, overclocking on this device makes very little sense unless you can achieve more thermal headroom with undervolting. I personally couldn't get over 1.8GHz on random loads, and couldn't get over 1.7GHz on benchmarking (Antutu 31300).
Nevertheless, the option is there for people who want to stick their phones into their freezers. For everybody else, stop being concerned about numbers.
This seems to affect only a rare number of people and I still don't know the cause. Just cycle the screen once and be done with it.
jlevy73 said:
I have kanged Andrei's response with respect to benchmarks.
Originally Posted by AndreiLux
Samsung cheats during benchmarks by enabling a thermal boost mode which raises the throttling temps by 10°C (90° -> 100°C). I disabled the permissions to this. Practical effects is things like Antutu will give lower scores. This is more realistic of actual performance and I will leave it as such. Benchmark freaks can enable the boost mode manually: /sys/class/thermal/thermal_zone0/boost_mode .
The first throttling speed is 1400MHz and that's why it spends a lot of time there during benchmarking.
Effectively, overclocking on this device makes very little sense unless you can achieve more thermal headroom with undervolting. I personally couldn't get over 1.8GHz on random loads, and couldn't get over 1.7GHz on benchmarking (Antutu 31300).
Nevertheless, the option is there for people who want to stick their phones into their freezers. For everybody else, stop being concerned about numbers.
This seems to affect only a rare number of people and I still don't know the cause. Just cycle the screen once and be done with it.
Click to expand...
Click to collapse
"This seems to affect only a rare number of people and I still don't know the cause" guess i am one of them:silly:
did you guys note the download link for perseus alpha 4 rc1 on andrei github? , dont flash it unless you know whats in there
edit: just flashed it (couldnt resist). based on the newer sources it seems, camera works fine with latest cam firmware
lets wait for Andrei release......build seems to be a release candidate....so its should not be for long....
bala_gamer said:
did you guys note the download link for perseus alpha 4 rc1 on andrei github? , dont flash it unless you know whats in there
edit: just flashed it (couldnt resist). based on the newer sources it seems, camera works fine with latest cam firmware
Click to expand...
Click to collapse
Thanks for sharing bro but i'm too stupid to find the link would you mind sharing more please?:victory:
update: found it: deleted. sorry
astoncheah said:
just got my s4 one day ago. rooted immediately, flashed omega7.0 and the latest perseus. did not touch anything on the u/v in stweak. no o/c as well. but the antutu score is so low 21000+, i thought it at least supposed to be 27000+?
i tried adam kernel, had the same result. is that normal? did i miss anything?
Click to expand...
Click to collapse
I received mine yesterday, rooted, flashed doc rom to remove bloatware, flashed perseus kernel.
I ran a few antutu and I was getting 27-28k without changing any setting.
Sent from my Nexus 4 using xda premium
@GSeeker
Pls remove the link since we dont know the nature of the version or lets wait unitl andrei unveils it.
bala_gamer said:
did you guys note the download link for perseus alpha 4 rc1 on andrei github? , dont flash it unless you know whats in there
edit: just flashed it (couldnt resist). based on the newer sources it seems, camera works fine with latest cam firmware
Click to expand...
Click to collapse
@Power, What rom are you running? I suspect it's rom related.
I'm using omega 7, one of the user experienced the same as mine. Going to flash new rom.
Sent from my GT-I9500 using xda app-developers app
astoncheah said:
just got my s4 one day ago. rooted immediately, flashed omega7.0 and the latest perseus. did not touch anything on the u/v in stweak. no o/c as well. but the antutu score is so low 21000+, i thought it at least supposed to be 27000+?
i tried adam kernel, had the same result. is that normal? did i miss anything?
Click to expand...
Click to collapse
With Omega / Perseus, is your camera still working????
Sent from my GT-I9500 (Hassan Khalid Malik) using xda premium
HassanM said:
With Omega / Perseus, is your camera still working????
Sent from my GT-I9500 (Hassan Khalid Malik) using xda premium
Click to expand...
Click to collapse
From recovery flash Perseus kernel + Camera Fix https://www.dropbox.com/s/20kyqg154h8w198/camera-ISP-fw.MEAplusFix.zip
Then reboot. Your camera should be working.