Hello everyone,
I was wondering if anybody else had any experience (good or bad) with enabling the debug.sf.hw = 1 setting (use hardware acceleration).
I installed "Blade Buddy" to enable it, and i'm getting the impression the whole phone just got a tremendous boost...
Is it just me and the blinding euphoria I get from installing a ARHD update, or does that setting actually do something?
I read somewhere (googled) that the Desire HD has an Adreno 250 GPU and that it can be used by enabling that debug.sf.hw = 1 setting so I went on and tried it.
So... anybody has any experience with that?
Thanks in advance,
sstm
Hi, I tested that Build.prop change but I guess it's all about placebo I'm affraid
I did following, first of I made the line in the build.prop and set it to 1 rebooted.
scrolled around a bit.
Edited the build.prop again and set it to 0 rebooted. And now the UI became terrible slow. So I guess the GPU is already active by default in GB ROMs.
I guess this tweak isn't for Desire HD. Maybe some other device.
Do you have a link to the source?
Edit; One possible thing is that by enable HW=1 you will force GPU to stay on all the time. Like ondemand and performance scaling in SetCPU. This is just a wild guess. And I hope I'm wrong with all this Because if we can make our devices even faster this found is awsome!
I just spent some time doing some miscellaneous tweaks to the smartassv2 gov on the new Lionfish kernel. I am extrememly battery conscious with this tweaking as i will soon be giving this EVO to my father who has to rely on in for business. I followed the info in a few other threads and thought I had what i needed to make the correct changes so I made them. I've noticed that after the changes I've made, the cpu scaling seems to be rather erratic, meaning it never really settles at low frequency. I don't know if this is due to the stock setting of the gov as i didn't check the scaling before hand or if it has to do with my changes.
my current settings are as follows
768000= awake_ideal_freq;
245000= sleep_ideal_freq;
499200= sleep_wakeup_freq
85=max_cpu_load;
70=min_cpu_load;
38400= ramp_up_step;(left at stock)
38400= ramp_down_step;(left at stock)
10000= up_rate_us(left at Stock)
20000= down_rate_us(left at Stock)
I didn't touch the rampup/down of the scaling intervals or anything, so i don't really understand why this is happening. And sugestions out there?
shameful bump....
If you're running Sense I wouldn't recommend that low of a main clock, and honestly if your dad knows nothing of rooting I'd unroot it, leave everything stock, and let him fair with it, wouldn't want the device bugging out on him after all.
SavocaFTW is right, you are way under, just use on demand it will be just fine, if you set the evo values to low the system gets whacked out bad.
I've been using newest lionfish 1.2 and V6 supercharger with setting #8. Tried it just for kicks and its been working great for battery life. Use System Tuner Pro. Don't use Set CPU. I use ondemand 768-245. One other you thing to do is use a file manager to navigate to the system/etc folder and scroll down until you find the init.post_boot.sh file and either delete it or move it to your sd card. This is the cause of most of problems i'm sure.
Hello,
I'm reactivating this thread since I cannot talk with samm every now and then to update the OP from this thread here.
What works:
It is stable for a daily driver but there are definitely things that doesn't work. For starters, the Hero is too small for ICS since we don't have any GPU posibility. Adreno 130 drivers are oh, too small and too bad for animations on ICS, they suck even in GB and Froyo. Still, the statusbar and fling are much smoother than other android releases because that's how ICS is built. It is more RAM friendly and it looks, well, sexy!
Will try and update this rom when it will be possible. We might jump on the bandwagon of 4.0.4 if I can make it to move faster than it moves right now (yes, I have an experimental build).
If one of you want to join me to develop this rom further, send a PM and I will send you some details about what is in the works, how far it is. I know there are few people that can work on builds here on Hero thread but if we work together, we can pull this out one more time.
FLASH THIS AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR:
- YOUR BRAIN
- YOUR HOUSE
- YOUR PHONE!
ON with the ROM. What has been changed:
Added:
Code:
- Google Music apk (yes, official google music app);
- Explorer.apk
- Latest and greatest LV Kernel 1.2+
- Revert to Evtoolbox back from 4.0.3 builds
- Set the cpu to scale at 352-672 from startup
- Tweaked the build.prop a little (added some experimental lines)
Why this is v3?
Because the memory management inside the kernel (remember, INSIDE THE KERNEL) is tweaked and fixed to nice values in order to allow our hero to better multitasking (you can find these values in my other rom called 1ceCream BEAST Flavor). No need for tweaks in init.d to do the job, no bull****.
Just plain and simple!
If you are texting someone, sending an email, playing a game, doing something, and you are locking the screen, after unlocking you will find that the application is ON the screen, and is not closed how it is in many other roms for hero. The multitasking with my values is so much better, you will definitely like it!
Click to expand...
Click to collapse
The rom moves fast, even if it is ICS, I have the animations on and no force GPU in Developer settings and it is still moving so much fast than the older builds.
Overall, I am happy with this release and I hope you will be too! Post me some of your opinion and tell me if it is fast or am I dreaming!
Some user's feedback:
Loxxy said:
wow 'HeroICS v3' is running on rocket power !!! what the hell
amazing job
Click to expand...
Click to collapse
Carrier Internet connection issue:
- Create Manual APN for provider's internet connection.
DOWNLOAD HeroICS v3
If you make these changes maybe you'll see better performance, the hero can't handle dithering on anything higher than stock GB or Sense froyo and doesn't have enough RAM for 48mb of dalvik heapsize. I may be wrong but these always worked for me in the past altough ICS is supposed to be better on RAM.
dalvik.vm.execution-mode=int:fast
dalvik.vm.heapsize changed to 24m or 32mb
persist.sys.use_dithering=0
Good work. Flashing now.
How about keeping this as lite as possible, only the absolute essentials pre-installed, everything else as optional zips / apk. For instance, I personally have no use for the music player.
I would really like to see a bare bones, fast and stable ics rom where you just add what you need.
---------- Post added at 03:56 AM ---------- Previous post was at 03:16 AM ----------
Unexpected reboot just as I was about to install Opera Mini. Followed by: "New Sim Detected, reboot required." Never seen that before.
I've applied CSL00's values.
Wonder if V6 Supercharger or Auto Memory Manager can improve things.
Play Store is noticeably faster. Unsure if was CSL00's values or the introduction of AMM.
Regarding the error message: 'No more room on this home screen.'
In Play Store app. Menu > Settings > Deselect Auto-add widgets.
Second unexpected reboot, otherwise things are getting faster. No wifi issues, BT still won't pair.
Running AMM on 'Aggressive.'
CSL00 said:
If you make these changes maybe you'll see better performance, the hero can't handle dithering on anything higher than stock GB or Sense froyo and doesn't have enough RAM for 48mb of dalvik heapsize. I may be wrong but these always worked for me in the past altough ICS is supposed to be better on RAM.
dalvik.vm.execution-mode=int:fast
dalvik.vm.heapsize changed to 24m or 32mb
persist.sys.use_dithering=0
Click to expand...
Click to collapse
dalvik execution mode was on fast until I changed it in the last second to "jit".
vm.heapsize was changed to 48 because I was testing 32 mb and I saw that it takes a little while to enter in one application. With 48 mb the time is reduced somehow. Please feel free to change it to 32 mb if you want. Dithering, well here is a mistery, I don't know if this works in ICS. It does look a little better than with it changed to 0 and my phone can suport dithering pretty well.
About the reboots, please install set cpu and set your max cpu frequency to a respectable value such as 691 or lower. I suggest using governor smartassV2.
The whole rom does feel a little snappier but we have an issue when someone calls you and after 20 seconds the call gets interrupted. I'll look into that today after work and see if I can fix it somehow.
I've tried Supercharger, the V8 doesn't wanna start on ICS and when applied V6 with option 6, the phone just got stuck on bootloop.
The reason that I've made it like this with apk.s that you can easly uninstall is that I didn't want you guys to have to flash any other optional zips or anything. But as I said, feel free to do what ever you want and uninstall those unused apps.
Oh, If you want to try supercharger yourself, you have to first delete these scripts from /etc/init.d:
03tweaks
04netspeed
05fixsdcardspeed
06loopy_smoothness_tweak
15cleanup_init_ram
16sqlite_optimize
17speedy_modified
Just to avoid any unexpected issues.
L.E:
CAN SOMEONE PLEASE, make a LOGCAT while you are in a call and save it to a txt? I want to see if we can narrow down the problem of disconnecting. I am unable to make a logcat atm.
1ceb0x, back to using your original build.prop, and Setcpu. Things seem more stable.
I'm looking for a notification toggle (cm-style) that has no icon when running (or only hides it, leaves a space.)
I will make a logcat, but I've tried aLogrec and all it seems to produce is an empty file. Should it not be dumping info on any activity I do?
lost101 said:
1ceb0x, back to using your original build.prop, and Setcpu. Things seem more stable.
I'm looking for a notification toggle (cm-style) that has no icon when running (or only hides it, leaves a space.)
I will make a logcat, but I've tried aLogrec and all it seems to produce is an empty file. Should it not be dumping info on any activity I do?
Click to expand...
Click to collapse
Seems stable than samm000's build.prop?
Glad to hear this.
As for the logcat, you cannot use any of the readers on the market because they will not work on ics. I've tried to make a log using android sdk but it seems that we need a file called 'main' in /dev/logs. I tried to make the file manually but then I've encountered an EOF read error on cmd. I forgot to make permissions for the respective file. Will make it again now and see how it goes.
As for cm notification toggle, I don't know what are you talking about. The notification toggle on ICS is nicer than any other available .
Tell me if you have calls issue (your call is disconnected after some seconds)?
Well it is probably more stable because I reduced the cpu speed.
In a voicecall now, 2mins+. Call lost around 3 mins.
6mins+ this time and still going...
lost101 said:
Well it is probably more stable because I reduced the cpu speed.
In a voicecall now, 2mins+. Call lost around 3 mins.
Click to expand...
Click to collapse
Did you checked the box "Force GPU rendering" in Develop Options?
Is it stable because I've added graphical tweaks and some tweaks to speed...
Yeah, 'Force GPU rendering' is enabled. In a voicecall now, 10mins+.
I ended the call myself at 22mins.
lost101 said:
Yeah, 'Force GPU rendering' is enabled. In a voicecall now, 10mins+
Click to expand...
Click to collapse
10 minutes without disconnecting? What's your settings on network? GSM ONLY, or WCDMA preferred?
(to see this, please go to dialer and dial *#*#4636#*#* , then go to Phone information, scroll down and you will see the value above the button "Turn Off Radio").
as default the version is WCDMA preferred. What Radio firmware are you using?
also, did you installed Habarug's tweak to hide the end button call during a call? (it's in samm000's thread).
this information will be helpful! cheers
WCDMA preferred. Radio: 63.18.55.06PU_6.35.15.11
I have not installed Habarug's tweak.
lost101 said:
WCDMA preferred. Radio: 63.18.55.06PU_6.35.15.11
I have not installed Habarug's tweak.
Click to expand...
Click to collapse
and you had 10 minutes without disconnecting? you were able to end the call normally?
1ceb0x said:
and you had 10 minutes without disconnecting? you were able to end the call normally?
Click to expand...
Click to collapse
It was 22mins when I ended the call myself.
Regarding notification toogle this is what I mean: 15 toggle status bar as implemented in this rom. Check the video.
Very ODD.
I have 63.18.55.06OU_6.35.15.01 on my device with WCDMA preferred but I keep getting call disconnected after 10 seconds or so.... regarding the notification status bar power widget, I don't know what to say. I'm not a dev so...
i'm trying to find a way to make a log cat of the calling issue because I don't really want to change my radio because my version seems to be battery friendly...
thank you for your support
Obviously the notification thing isn't even important right now. I shouldn't really have mentioned it.
I thought this radio was considered one of the best to be using, and find the battery life to be good on it.
Don't know if its the best really. But I've flashed it anyway. Since this will end my calling interrupt, it will be a small price to pay if the battery doesn't play well.
Will test the voice calling. Btw, I am maybe working on RC2, with some new tweaks and fixed latinime.apk keyboard..
can confirm right now that the latinime.apk is fixed.
@Habarug: are you using my mod or sam's rom?
Thanks lost, will try your radio, im on .14 atom
Just to clarify, the radio I am using still has calls dropping with ics. It seems to happen at random times. 1 minute into a call, 3 minutes or not at all. Maybe it's because of the numbers I am ringing. I can't be sure they would not drop anyway. But it sounds like it is doing better than some other radios.
Also, what about having a build based off ics 4.0.4?
lost101 said:
Just to clarify, the radio I am using still has calls dropping with ics. It seems to happen at random times. 1 minute into a call, 3 minutes or not at all. Maybe it's because of the numbers I am ringing. I can't be sure they would not drop anyway. But it sounds like it is doing better than some other radios.
Also, what about having a build based off ics 4.0.4?
Click to expand...
Click to collapse
we have to fix this issues first and then talk about another version. anyhow, 4.0.4 is much laggier than this version. i saw a bit of logcat and some awkwardly errors regarding the "animations" but i was unable to save the log for future use.
I've asked Maclaw, a dev from Galaxy Gio/Fit/Mini who made CM9 possible on those device to look at our build and maybe with some luck he can see something that make this calls drop...
managed to past 3 minutes in call with your radio version lost101. cheers
L.E: I am unable to send PM's. so i cannot ask Maclaw for help.. too bad! I'll just have to post on their op!
Come on people.. test the build!
So I have found that recently every kernel I try to over clock with will cause bad performance on my phone. I am judging this based on benchmarks which should improve when you over clock (I know benchmarks aren't everything, just using them to compare). Every time I over clock to 1.89 it automatically reboots no matter what kernel or rom I am running. No one else in the kernel thread has this issue. If I run benchmarks with the max clock anything above the stock 1.5Ghz makes my benchmark performance absolutely drop. I have tried:
-multiple kernels and ROM combinations
-multiple CPU managers (ROM toolbox to CM performance control)
-multiple bench markers
Did I somehow destroy my CPU on higher clocks somehow?
And I know I don't need OC for good performance, I am just wondering what's up here. It wasn't always like this.
It's not necessarily anything you did. Not all devices are created equally. Some phone can run at 2.1GHZ and get amazing battery life. You just got dealt a bad phone that doesn't over clock well.
Sent from my SAMSUNG-SGH-I747 using xda premium
Yes, if you go over 1890Mhz your phone will restart or get stuck in a bootloop. As the person above said is right. Some phones can go up to 2000MHz and some can't. My Gs3 can overclock to 1890 but I keep mine at 1809.
1. Benchmark apps have no use at all.
Its literally just numbers thrown at you. They have no reflection on real world performance.
2.No one phone is the same. Your phone maybe able to go up to 1.8 with out an issue, but other phones might not even make it past 1.7 I even know of a GS3 that runs at 2.1Ghz with out a problem.
3.OC isn't really needed on an S3 if you're having lag issues or anything Odin back to stock and start again.
I personally run my S3 at 1.1Ghz.
I use custom kernels to under clock and not over as over clocking can drain your battery. Your phone will always reboot past 1.8 regardless of the kernel. That's just how your phone works.
Galaxy S3 / AoCP / V4A / Turbocharged
Not sure if this is the right thread to talk about it, but recently I flashed the 5.4 version of this kernel http://forum.xda-developers.com/showthread.php?t=2775998 and so far so good, it fixed the 4.4.2 S Pen problem. However, I've noticed that, when I use multitask mode (2 apps open at the same time stacked on top of each other), there is some light stuttering(?). Not laggy, but when I scroll it kinda stutters a bit. Strangely enough, this only happens during multitask mode, not if I have a lot of apps open in the background. This isn't the real problem though, the real problem is that the kernel seems to cause the S Note app to lag so much that it's almost unusable. Another problem i've found was that SOMETIMES when listening to music when the screen is off, the music lags so much that it's inaudible. Not often, though, and I dorn know what specifically causes it, other than the low GPU speed. The kernel specifically states this:
"GPU settings are:
Step0 54MHz = new Idle step = when in browser mode and no gaming this low GPU speed will help save power
Step1 266MHz
Step2 350MHz
Step3 533MHz = new speed foe step3 for better performance in drawing
Step4 700MHz = New OC speed for the better gaming performance
GPU settings are not editable and hard set in the kernel"
I'm taking a guess here but I think that the low, non editable GPU settings are causing the slowdowns.
Is there any way to somehow increase the GPU, even though it says that it's uneditable? Has anyone used this kernel before and found out how to fix it? Would downgrading to a lower version of the kernel fix the slowdowns? This is the only kernel I found that fixed the slowdown for my device, I can't really install a different one, but I can downgrade this specific kernel, which I think could fix it but I'm not sure. Are there any other fixes?